| View previous topic :: View next topic |
| Author |
Message |
Azimuth
Moderator & Beta Team
Joined: 19 Nov 2010
Posts: 2131
|
 Posted: Fri Jul 11, 2014 9:30 am Post subject: Keyboard control not passing through to Reaper? |
 |
|
Hi Ralph,
I noticed that using the keyboard to control Reaper is not working. Jamstix indicates that it keyboard focus is returned to Reaper in its status line, but I have no control until I click Reapers window to switch focus. |
|
| Back to top |
|
 |
Ralph [RZ]
Site Admin
Joined: 02 Jan 2008
Posts: 13332
|
| Posted: Sat Jul 12, 2014 8:39 am Post subject: |
|
|
Very odd, can't duplicate. Any specific key stroke(s) that do that?
Does the space bar start/stop REAPER after focus is returned?
Does the FX:Track header change color when focus is returned?
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com |
|
| Back to top |
|
|
Azimuth
Moderator & Beta Team
Joined: 19 Nov 2010
Posts: 2131
|
| Posted: Sat Jul 12, 2014 10:20 pm Post subject: |
|
|
Hi Ralph,
No keyboard commands at all get through to Reaper. After I click in the Reaper window to manually switch focus, everything works. When Jamstix status bar states that focus has been returned to Reaper, Jamstix window grays out, but focus never actually switches ie. the Reaper window title bar remains grayed out until I manually click inside Reapers window.
Don't worry about it if you're not seeing it, it's probably something flaky going on with my system. I'll let you know if I figure out what the problem is. |
|
| Back to top |
|
|
Azimuth
Moderator & Beta Team
Joined: 19 Nov 2010
Posts: 2131
|
| Posted: Sun Jul 13, 2014 2:27 am Post subject: |
|
|
Hi Ralph,
I'm not quite sure what the problem exactly was but it had something to do with Reapers configuration. I reset Reaper back to its default configuration, reinstalled all Python scripts, SWS extensions and reconfigured my action shortcuts and all is well. Something got corrupted I guess. Sorry for wasting your time. |
|
| Back to top |
|
|
Azimuth
Moderator & Beta Team
Joined: 19 Nov 2010
Posts: 2131
|
| Posted: Tue Sep 02, 2014 7:45 am Post subject: |
|
|
| Late follow up but I discovered that the actual cause of this was that I had Jamstix running as a separate process in Reaper. Just updating this in case anyone else finds themselves having the same problem. |
|
| Back to top |
|
|
Ralph [RZ]
Site Admin
Joined: 02 Jan 2008
Posts: 13332
|
| Posted: Sun Sep 14, 2014 8:27 am Post subject: |
|
|
Azimuth, please also try this: add the following line underneath [GENERAL] in Documents\Jamstix3\jamstix3.ini via NOTEPAD:
PopupMode=1
This should alleviate the need for audio driver sharing to be disabled and also help with focus issues. Drawback: it does not work if you have more than one instance of Jamstix loaded in your project.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com |
|
| Back to top |
|
|
Azimuth
Moderator & Beta Team
Joined: 19 Nov 2010
Posts: 2131
|
| Posted: Sun Sep 14, 2014 11:26 pm Post subject: |
|
|
| I'll give it a try. Thanks Ralph. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
