Jamstix & REAPER
-
Azimuth (Archive)
- Posts: 1675
- Joined: Fri Nov 19, 2010 2:16 am
Jamstix & REAPER
Hi taji,
First off I use Windows so I'm not sure if this applies but do you see "jamstix.exe" or "Jamstix Audio Plugin Server" listed in your running processes? I don't know how or where it displays in OSX but normally under Windows similar error messages indicates that the plugin server is not running. Try starting jamstix.exe first and then start Reaper and see if it makes a difference.
First off I use Windows so I'm not sure if this applies but do you see "jamstix.exe" or "Jamstix Audio Plugin Server" listed in your running processes? I don't know how or where it displays in OSX but normally under Windows similar error messages indicates that the plugin server is not running. Try starting jamstix.exe first and then start Reaper and see if it makes a difference.
Jamstix & REAPER
Thanks for the reply. 
Niether Jamstix.exe or the Jamstix Server Process is listed as running inside the Mac Activiity Monitor. Actiivity Monitor does show the JamstixManager when I launch it.
Did a clean vanilla install of Jamstix and Jamcussion using the Manager. I can see all of the installed files in the ~/Library/ApplicationSupport/Jamstix3/data folder (kits, groovemaps, etc). But I don't see an exe file or similar.
Do you need to launch the jamstix.exe process manually or is it automatically started when you load the vst plugin?
Niether Jamstix.exe or the Jamstix Server Process is listed as running inside the Mac Activiity Monitor. Actiivity Monitor does show the JamstixManager when I launch it.
Did a clean vanilla install of Jamstix and Jamcussion using the Manager. I can see all of the installed files in the ~/Library/ApplicationSupport/Jamstix3/data folder (kits, groovemaps, etc). But I don't see an exe file or similar.
Do you need to launch the jamstix.exe process manually or is it automatically started when you load the vst plugin?
-
Azimuth (Archive)
- Posts: 1675
- Joined: Fri Nov 19, 2010 2:16 am
Jamstix & REAPER
Hi taji,
IF OSX uses jamstix.exe, it should start automatically when loading Jamstix in Reaper. If someone else doesn't jump in here soon who knows more about JS in OSX than me (that would be anyone) then I would send an email directly to support@rayzoon and ask Ralph directly. He might be a little slow responding though with the beta testing that is going on at present but he will. Sorry that I couldn't be of more assistance.
IF OSX uses jamstix.exe, it should start automatically when loading Jamstix in Reaper. If someone else doesn't jump in here soon who knows more about JS in OSX than me (that would be anyone) then I would send an email directly to support@rayzoon and ask Ralph directly. He might be a little slow responding though with the beta testing that is going on at present but he will. Sorry that I couldn't be of more assistance.
Jamstix & REAPER
I've sent an email into support. Thanks for attempting to help. 
-
Azimuth (Archive)
- Posts: 1675
- Joined: Fri Nov 19, 2010 2:16 am
Jamstix & REAPER
Anytime taji, just sorry that I couldn't do more.
Jamstix & REAPER
I figured it out. I'm using a machine that was loaned to me by another company. They had locked down the location where the Jamstix application file should have been installed. After looking at the install logs, I figured out that I needed to Launch JamstixManager as admin. Once I did that, the proper files were successfully installed. Jamstix is working in Reaper. 
Thanks again for the help.
Thanks again for the help.
-
Azimuth (Archive)
- Posts: 1675
- Joined: Fri Nov 19, 2010 2:16 am
Jamstix & REAPER
Glad to hear that you got it working taji. Just for my own future reference, if you wouldn't mind, how do you run something with Admin rights on OSX? Just in case I need to point someone else to this solution. Thanks for following up and reporting the solution also.
Jamstix & REAPER
I use win 10 64 and JS 4.0.4 .when i press save to save a kit the requester for filename come, but there is no cursor see. i can type name and edit. not a big problem all other work good, but if this can fix or do other not see this problem ?
-
Azimuth (Archive)
- Posts: 1675
- Joined: Fri Nov 19, 2010 2:16 am
Jamstix & REAPER
I see that also (the missing cursor) but I'm used to it now.
-
Brother_Fats
- Posts: 12
- Joined: Sat Jun 04, 2016 10:22 am
Jamstix & REAPER
I use Jamstix 4 in REAPER. Just updated to the newest version of JS, v.4.2.0, 64-bit. And I am using REAPER v.5.961 64-bit, which is up-to-date.
I am having an issue with how slow Jamstix is in unloading when I close its FX window. Takes 20 seconds and all of REAPER is frozen until that is done.
Same issue (and time required) whenever I save the project in REAPER. The slowness also occurs when I exit REAPER or close the project, even if the project has just been saved. I see the message, "Removing 1 track..." on the screen until the project finally closes or REAPER exits.
Each of these takes 20 to 30 seconds minimum.
I only noticed this starting a few days ago. I had a song I was working on where I had developed the song structure and assigned the drummer and kit. I had done nothing to change the basic composition of the drums. It was all composed by Jamstix 4. Standard 1/8th note rock.
I then went in and updated the kick drum so that it matched my bass guitar. Nothing super sophisticated. That's when the trouble began.
Before I did this it would take about 1 second to close the FX window or to save the project in REAPER. After doing making that change, however, it takes 20 to 30 seconds to do those things, or to close the REAPER project.
I noticed also that after making the changes to the kick drum, the size of the .j2d file essentially doubled. It went from something like 68kb to 120kb.
Note that I save the different versions of the .j2d files when I make changes. So I know that this is happening due to that change, because when I load the old version of the file into Jamstix 4, the time it takes to close the FX window or save the project drops back down to about 1 second. When I reload the newer version, the processing time leaps back up to over 20 seconds.
I thought maybe something had gotten corrupted in the Jamstix song file itself. So I loaded another .j2d file from an old Jamstix 3 project. It is larger in size than the one I'm having trouble with now: 138kb. That song and its .j2d file were created in Jamstix 3.
Sure enough, that old song file causes the same problem in Jamstix 4. The same issue with slowness. So it's not a corrupted file issue.
Note that the actual playing of the song is not affected. It seems to play fine. It just slows me way down trying to save the project or close the FX window.
As a final test I created a new project and inserted Jamstix 3. I then loaded that old song .j2d file in the Jamstix 3. It has none of the slowness issues that it does in Jamstix 4. The FX window closes almost immediately and I am able to save the REAPER project almost instantaneously.
Any suggestions? Do I potentially have some Jamstix 4 setting that needs to be changed? I have not altered any of the defaults, that I can recall.
Thanks.
Chris
I am having an issue with how slow Jamstix is in unloading when I close its FX window. Takes 20 seconds and all of REAPER is frozen until that is done.
Same issue (and time required) whenever I save the project in REAPER. The slowness also occurs when I exit REAPER or close the project, even if the project has just been saved. I see the message, "Removing 1 track..." on the screen until the project finally closes or REAPER exits.
Each of these takes 20 to 30 seconds minimum.
I only noticed this starting a few days ago. I had a song I was working on where I had developed the song structure and assigned the drummer and kit. I had done nothing to change the basic composition of the drums. It was all composed by Jamstix 4. Standard 1/8th note rock.
I then went in and updated the kick drum so that it matched my bass guitar. Nothing super sophisticated. That's when the trouble began.
Before I did this it would take about 1 second to close the FX window or to save the project in REAPER. After doing making that change, however, it takes 20 to 30 seconds to do those things, or to close the REAPER project.
I noticed also that after making the changes to the kick drum, the size of the .j2d file essentially doubled. It went from something like 68kb to 120kb.
Note that I save the different versions of the .j2d files when I make changes. So I know that this is happening due to that change, because when I load the old version of the file into Jamstix 4, the time it takes to close the FX window or save the project drops back down to about 1 second. When I reload the newer version, the processing time leaps back up to over 20 seconds.
I thought maybe something had gotten corrupted in the Jamstix song file itself. So I loaded another .j2d file from an old Jamstix 3 project. It is larger in size than the one I'm having trouble with now: 138kb. That song and its .j2d file were created in Jamstix 3.
Sure enough, that old song file causes the same problem in Jamstix 4. The same issue with slowness. So it's not a corrupted file issue.
Note that the actual playing of the song is not affected. It seems to play fine. It just slows me way down trying to save the project or close the FX window.
As a final test I created a new project and inserted Jamstix 3. I then loaded that old song .j2d file in the Jamstix 3. It has none of the slowness issues that it does in Jamstix 4. The FX window closes almost immediately and I am able to save the REAPER project almost instantaneously.
Any suggestions? Do I potentially have some Jamstix 4 setting that needs to be changed? I have not altered any of the defaults, that I can recall.
Thanks.
Chris