Page 1 of 1

Mouse Problem

Posted: Wed Jul 16, 2014 12:55 am
by Iron_Axis
I used to be able to hover my mouse and left click on the drum kit in the kit or mixer screen to produce a sound. When I click on the drum sound and then click on the anything outside of the Jamstix window the sound is then produced. Not sure what's happening here but if anyone has a solution I'd like to know.

Thanks.

Mouse Problem

Posted: Wed Jul 16, 2014 8:38 am
by Ralph @ Rayzoon
Sounds like you are using REAPER. Please uncheck the 'Close Audio...' options in the REAPER audio preferences to fix this.

Mouse Problem

Posted: Sun Sep 07, 2014 4:53 pm
by BitFlipper
Ralph,

I'm using Sonar X3e and I'm having the exact same issue. When I'm in the Kit tab and click on any drum element to audition it, it selects it visually but no sound is produced. Then if I click anywhere outside of Jamstix, the last sound I clicked on plays audibly.

Is there any solution to this issue?

JS 3.6.0 x64 in Sonar X3e

EDIT: I'm also seeing other weird behavior... For instance if I click on the bar loop preview button, the button gets highlighted (becomes a blue arrow), but doesn't do anything. Then if I click anywhere outside JS, it starts looping.

In fact it seems almost all of JS's functionality is having this issue. Yesterday I could not figure out why making changes in the brain had no effect. Now I realize that it was the same issue - nothing registers until you click outside of JS. This makes it basically unusable.

EDIT EDIT: More info that might help track down the issue... When I click on the preview loop button, it does not start looping. However when I click outside of JS (or on the JS window title bar), it starts looping. Then when I click somewhere inside JS again (like in a blank space), it stops looping. It is as if when JS has focus, the internal JS engine stops functioning until JS loses focus again.

I have no idea when this issue was introduced since I have not used it for a very long time, and yesterday downloaded 3.6.0.

EDIT EDIT EDIT: BTW I noticed JS acts weird in that it is the only plugin that makes its own title bar lose focus when you click inside of its property page. With all other plugins, when you click somewhere inside the plugin property page, it's title bar retains focus.

EDIT EDIT EDIT EDIT: When Sonar is stopped, clicking anywhere inside JS will actually disengage the Sonar audio engine. Click somewhere outside of JS and the Sonar audio engine engages again. This does not happen while Sonar is playing back, only when stopped.

Mouse Problem

Posted: Sun Sep 07, 2014 9:35 pm
by BitFlipper
Other Sonar users on the Cakewalk forum confirmed the same behavior. However someone posted a workaround - ensure that "Share drivers with other programs" is disabled.

I rely on having multiple music applications open at the same time, so it would be great if this issue can be fixed, but at least I can use the workaround for now.

This has to be related to Jamstix's weird behavior of taking focus away from its title bar when you click inside of it (no other plugin does that).

Mouse Problem

Posted: Sun Sep 14, 2014 9:26 am
by Ralph @ Rayzoon
BitFlipper, please 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.