Jamstix 3.6.0 Final Release Candidate Available

Use this forum for general discussions and questions about Jamstix
Post Reply
Ralph @ Rayzoon
Site Admin
Posts: 5851
Joined: Wed Jan 02, 2008 6:24 pm

Jamstix 3.6.0 Final Release Candidate Available

Post by Ralph @ Rayzoon »

Jeff, please send me rzdlog.txt from Documents\Jamstix3.
Ralph
Rayzoon Technologies LLC
max.noise
Posts: 43
Joined: Thu Dec 06, 2007 12:36 pm

Jamstix 3.6.0 Final Release Candidate Available

Post by max.noise »

Just updated to 3.5.1 Beta8, but the program window still shows Beta3.
Have I made some mistake?
By the way: I am currently using the 64bit version exclusively.
Ralph @ Rayzoon
Site Admin
Posts: 5851
Joined: Wed Jan 02, 2008 6:24 pm

Jamstix 3.6.0 Final Release Candidate Available

Post by Ralph @ Rayzoon »

Max, send me Documents\Jamstix3\rzdlog.txt
Ralph
Rayzoon Technologies LLC
craig_glenn
Posts: 116
Joined: Fri Dec 24, 2010 8:15 am

Jamstix 3.6.0 Final Release Candidate Available

Post by craig_glenn »

Ralph,

PM'd you but thought i would post here as well...beta 8 is working but my drop down menus still appear on my secondary monitor.
max.noise
Posts: 43
Joined: Thu Dec 06, 2007 12:36 pm

Jamstix 3.6.0 Final Release Candidate Available

Post by max.noise »

Ralph,
found the problem and solved it partially. I replaced the js3sl64.rtxc and the jamstix3.dll in my plugins folder, but now I found that the js3sl64.rtxc is loaded from the folder where the data is stored, which is on a separate samples-drive.
As I was not aware of that (and didn't expect it to be like that), it was still the old js3sl64.rtxc that was loaded on host start.
Tried to solve it by hand-editing the js.ini in \documents\Jamstix3 by putting in the correct path and deleting all the other files that are next to the data-folder in that very directory, but that didn't work, got a black GUI.

Any idea how I can correct the path, preferably without a complete reinstall?
Jeff
Posts: 47
Joined: Mon Jun 23, 2008 12:23 pm

Jamstix 3.6.0 Final Release Candidate Available

Post by Jeff »

Ralph [RZ] wrote:Jeff, please send me rzdlog.txt from Documents\Jamstix3.
Sent
Ralph @ Rayzoon
Site Admin
Posts: 5851
Joined: Wed Jan 02, 2008 6:24 pm

Jamstix 3.6.0 Final Release Candidate Available

Post by Ralph @ Rayzoon »

max.noise wrote:Tried to solve it by hand-editing the js.ini in \documents\Jamstix3 by putting in the correct path and deleting all the other files that are next to the data-folder in that very directory, but that didn't work, got a black GUI.
Unfortunately, I'm not sure what you deleted there. It's best to run the 3.5.0 updater, make sure to specify the same locations as before (the sample drive for the first location asked, the plugin folder for the second).
This will get JS running again. For Beta 8, replace jamstix3.dll in the plugins folder and js3sl64.rtxc on the samples drive, which is its correct place.
Ralph
Rayzoon Technologies LLC
max.noise
Posts: 43
Joined: Thu Dec 06, 2007 12:36 pm

Jamstix 3.6.0 Final Release Candidate Available

Post by max.noise »

Ok, then it was my fault, expected the js3sl64.rtxc to be in the plugins folder and didn't read the readme carefully enough.
So everything seems to be as it should be.
It's only strange that the js3sl64.rtxc was in both folders...
Sherz
Posts: 61
Joined: Sun Nov 27, 2005 8:25 pm

Jamstix 3.6.0 Final Release Candidate Available

Post by Sherz »

I'm a little confused with the .dll names. My current beta (3.51 beta3) has 'jamstix3[b:7853eb2813]5[/b:7853eb2813].dll' dated 8 Nov 2012 in my VST plugins folder.

This new .dll appears to be called 'jamstix3.dll' .

Should I simply delete the old 'jamstix35.dll'?
Sherz
Posts: 61
Joined: Sun Nov 27, 2005 8:25 pm

Jamstix 3.6.0 Final Release Candidate Available

Post by Sherz »

Jeff wrote:Getting runtime error # 216 at 0000000008F9E045 when closing reaper 64 bit with any project that uses the beta 8 version of jamstix
Similar thing in Cubase 7... and I wonder if it has something to do with my above post? My old .DLL and this new one have different names so by simply copying the new file into the VST folder I of course end up with two .dll files.

:?:
Post Reply