RAYZOON

When JamStix is minimized and "playing" silent/silent, after one bar the software stops playing.

What happens is Ableton sends the VST request for processReplacing.

audioMasterGetTime it looks like is triggered by JamStix as part of the response to this.

Because there is no UI, there is no effEditIdle to trigger audioMasterGetTime, so after 1 bar of no replacing Ableton quits querying the plugin.

When the plugin is visible, there is a constant stream of effEditIdle which keeps the plugin alive, and if the plugin is creating a beat, processReplacing returns a valid buffer so I assume this keeps Ableton interested.

Also, when the play/stop/timebar edit in Ableton occurs, the dispatcher ProcessEvents request is sent to the plugin, which wakes everything up too. It's only when there are several bars of silence at the beginning of a song and JamStix is minimized that this occurs.

Personally I don't care too awful much, I have a constant stream of recompose midi requests going which also keeps the Ableton/Jamstix connection going, but I did want to report this as a bug.

I can see all this by running a plugin I'm building that acts as both a host to JamStix and a VSTi loaded by Ableton, and proxies all the calls b/w Ableton and JamStix so I can poke my own information into the object returned by audioMasterGetTime to fix the JamStix/Ableton behavior of live looping. My preference would have been a working livelooping, but the rest of the plug is so awesome that taking the long route to fix this is worth it! If you would like, I can submit the code when I'm done, maybe the logic can get rolled into JamStix as a patch for live looping.

Just thought I would chip in here with an observation and opinion with using JS4 and Live.
I don’t understand all the technicalities of the previous post but I do recognise the symptoms ie Jamstix doesn’t always play under certain conditions. As pointed out ( if I understand correctly) having Jamstix visible solves most of the problems - so no big deal but there again it would be better if there wasn’t this problem.
I’ve been running Jamstix with Ableton Live since JS 1 first came out and think the program is brilliant even with some of the minor ‘bugs’.
And you can always rely on positive and helpful responses from Ralph and Azimuth.

drk1 wrote:Just thought I would chip in here with an observation and opinion with using JS4 and Live.
I don’t understand all the technicalities of the previous post but I do recognise the symptoms ie Jamstix doesn’t always play under certain conditions. As pointed out ( if I understand correctly) having Jamstix visible solves most of the problems - so no big deal but there again it would be better if there wasn’t this problem.
I’ve been running Jamstix with Ableton Live since JS 1 first came out and think the program is brilliant even with some of the minor ‘bugs’.
And you can always rely on positive and helpful responses from Ralph and Azimuth.

Me too! If it wasn't awesome at being the drummer who always wants to play, never gets too drunk to hold their sticks, and remembers the songs, the right way, every time, I wouldn't bother. I'm of the opinion that bugs in general are bad, and sometimes a bug one place causes bugs in other seemingly unrelated places, so I report them as I find them. The level of detail here is because bug reports with lots of detail make reproducing/fixing the bugs easier. If this should go somewhere else, could the original post be moved?

chill_human,
Absolutely agree 100% with your outlook on bugs. That is all we, as users, can do is report when we find 'em. I do it all the time myself and Ralph truly appreciates it. Ralph may not reply to every report but I can tell you that he sees them all. If I feel it is a potential "showstopper", I will usually report what I find via the JS Manager app.

If this should go somewhere else, could the original post be moved?

No problem at all reporting things here.