Jamstix 3.6.0 Final Release Candidate Available

The_Dissonance · Post by **The_Dissonance** » Mon May 05, 2014 9:34 pm

well, found an older version that had the part thankfully and saved it as a song... phew. Gotta stop this from happening though,lol

Post by **Ralph @ Rayzoon** » Tue May 06, 2014 8:11 am

With the latest Betas, there is also a safety copy of the song data stored in \Documents\Jamstix3\Revisions when closing the song in the host.

The_Dissonance · Post by **The_Dissonance** » Tue May 06, 2014 9:50 am

ahh you're the man!

Azimuth (Archive) · Post by **Azimuth (Archive)** » Wed May 07, 2014 1:31 am

Hi Ralph,

I just loaded a Reaper project that I've been working on, the Song Wizard window opened, all the JS song data was gone,. I then tried reloading the song from Documents>Jamstix3>Revisions and the safety copy was blank also. I'm guessing that when I closed Reaper after the project failed to load properly, the safety copy was overwritten by the blank file. I noticed a lot of the j2d files in that folder are only 4kb in size and contain no data. The j2d files that are bigger than 4kb load and play fine but every 4kb file is completely blank. This is the first time this has happened to me. Would it be possible to institute some sort of safety check to prevent this from happening? Perhaps disallow a smaller size file from overwriting a larger one?

EDIT: I found another file in the folder dated a day earlier that did contain the j2d data. Does JS save multiple versions?

Another problem I found, and this may be exclusive to Reaper, if I close a project that contains JS, open a new project and try to insert JS I get an inconsistent error stating ERROR: Cannot communicate with core ID=0

Post by **Ralph @ Rayzoon** » Wed May 07, 2014 10:34 am

a_zimuth wrote: Another problem I found, and this may be exclusive to Reaper, if I close a project that contains JS, open a new project and try to insert JS I get an inconsistent error stating ERROR: Cannot communicate with core ID=0

Please duplicate, close REAPER and then send me apslog.txt and rzdlog.txt from Documents\Jamstix3. Thanks!

Azimuth (Archive) · Post by **Azimuth (Archive)** » Thu May 08, 2014 2:48 pm

Hi Ralph,
Been busy at real work so I haven't managed to recreate the error I reported above yet but here is an image of another thing that occurs pretty regularly the first time I open the JS GUI in Reaper. It is always the same , offset to the left, and only the first time I open the interface. If I close the GUI and reopen or switch to a different tab (Song, Kit or Mixer), all is fine.

[URL=http://s1207.photobucket.com/user/mephitis/media/Jamstix%20GIFs/JSGUIerror.gif.html][img:a540b09a68]http://i1207.photobucket.com/albums/bb471/mephitis/Jamstix%20GIFs/th_JSGUIerror.gif[/img:a540b09a68][/URL]

Click thumbnail to view.

reggae_greggae · Post by **reggae_greggae** » Sat May 10, 2014 5:17 pm

Not a bug as much as a question. I noticed while testing the AAX that after I exited Pro Tools I saw that there was a process called jamstix audio plugin server still running. Thought it might be restricted to that format but it's present in the Reaper VSTI as well. Is it normal for that to stick around? Don't have a 3.5 installation up right now to check for whether that was there before. Just struck me as odd when I saw.

Azimuth (Archive) · Post by **Azimuth (Archive)** » Sat May 10, 2014 10:32 pm

reggae_greggae wrote:Not a bug as much as a question. I noticed while testing the AAX that after I exited Pro Tools I saw that there was a process called jamstix audio plugin server still running. Thought it might be restricted to that format but it's present in the Reaper VSTI as well. Is it normal for that to stick around? Don't have a 3.5 installation up right now to check for whether that was there before. Just struck me as odd when I saw.

That is normal. It's new in v.3.6 and will allow intercommunication with future apps such as Jambassist and faster startup of JS, if running, among other functions.

Azimuth (Archive) · Post by **Azimuth (Archive)** » Sun May 11, 2014 12:42 pm

Hi Ralph,

I've tried recreating the "ERROR: Cannot communicate with core ID=0" problem and have not been able to do it. There have been 2 Reaper pre-releases and 2 release candidates since I reported it so it may well have been a Reaper problem. I know that Reaper changed something relating to vst handling when closing Reaper a few pre-releases ago, so that may be related somehow. If it should resurface, I'll send in the logs.

reggae_greggae · Post by **reggae_greggae** » Sun May 11, 2014 1:23 pm

a_zimuth wrote:
reggae_greggae wrote:Not a bug as much as a question. I noticed while testing the AAX that after I exited Pro Tools I saw that there was a process called jamstix audio plugin server still running. Thought it might be restricted to that format but it's present in the Reaper VSTI as well. Is it normal for that to stick around? Don't have a 3.5 installation up right now to check for whether that was there before. Just struck me as odd when I saw.
That is normal. It's new in v.3.6 and will allow intercommunication with future apps such as Jambassist and faster startup of JS, if running, among other functions.

Actually I was just going through the new user guide and found it explained. Probably should have done that to begin with, so thx both for replying and for not just tossing out a snarky RTFM.