♥ 0 |
I created a project yesterday using the trial version of the software running on a PC running Windows 10. The project translated text entered on the computer keyboard to raw MIDI outputted to the project’s MIDI port. It was working perfectly. Today I purchased MT Pro and installed it on a MacBook Pro. I opened yesterday’s project file, which looked the same as on the PC. I adjusted the MIDI out port for the MacBook. Problem is: the key strokes and text on the computer keyboard are not being detected properly. I assigned each lower and upper case letter (all single key strokes, no combinations). Nearly all the keyboard keys are not triggering. But a few odd keys on the keyboard do trigger: I noticed that holding down the shift key with these odd key strokes produces the upper case version of the letters entered above. Why are all the letter keys being ignored? Why do RETURN, DELETE, SPACE-BAR, and UP/DOWN ARROWS produce letters? Marked as spam
|
Thank you for the additional information. It seems to be a problem in your project file. If the Event Monitor shows that it detects keystrokes, then I’d think they are the correct ones, but maybe somehow your mapping does not work. Could you please post your project file with instructions how to reproduce the issue?
PS: “Ignore incoming keystrokes when focused” is nonfunctional in version 1.8.2 (always ignored). It’s fixed for the next version.
I’m not certain how to post the project file. Should I export it as a text file and just paste the text here?
Thanks. You can attach files when posting an “answer”… Anyway, by text is fine, too.
Have you tried using “Physical Keystrokes” instead of “Text” in the incoming keystroke actions?
I know that can be difficult for using uppercase letters, but for a test, it would be nice.
oh, and which language is your computer set to? Thanks!
MT works with Physical Keys input, so the project below works as expected. MT does not work with Text input on my MacBook Pro (2012 Retina, Sierra 10.12.6, language-English, keyboard-US). Is this due to a bug in the current version of MT?
MT does not work with Text input on my MacBook Pro (2012 Retina, Sierra 10.12.6, language-English, keyboard-US). Is this a known issue and if so, when might it be addressed?
Hi, we weren’t aware that Text Input had any problems (i.e., you’re the first person to report this). We’ll look into it as soon as possible — though unfortunately, right now we’re in crunch mode trying to finish a few exciting new features to be demonstrated at the NAMM trade show in 2 weeks.
PS: you can still evaluate upper case and lower case using physical keys. It’s just not so convenient. The way to go is to set a global variable to 1 if SHIFT is pressed down, and reset it to 0 when SHIFT is released:
Then define the translators so that they evaluate the SHIFT status (variable gs) in the Rules section. As an example for a and A:
Hope that helps as a workaround!
Florian