RAYZOON

Thanks for the answer I'll try it out.

Regarding the installation of 3.5 I think it gets identified as a new plugin and keeps the old one. I moved my old v3 to a new path to be sure so I don't really know if the DLLs gets overwritten. This is what's mentioned during the install:


------- IMPORTANT NOTES BEFORE INSTALLING!! -------

--- [32-bit & 64-bit] ---
This installer includes all three versions of Jamstix: 32-bit VST, 64-bit VST and 32-bit RTAS. Make sure to only select the version(s) you need. If you check 32-bit VST AND 64-bit VST, you will be asked for TWO plugin locations. You should only need to do this, if you run 32-bit DAWs and 64-bit DAWs on the same machine and wish to use Jamstix in both.

--- [NOTES FOR BETA USERS] ---
IF YOU HAVE A CURRENT JAMSTIX 3.5 BETA installed, please note that any projects you may have created with the Beta will not load this release version. If you have important projects with the Beta version, please exit the installer now, open all such projects and do 'Save Song' in the song menu to create backups of your arrangements. After you install this release version, you can then replace the Beta in each project and load the saved arrangement.

If you have hand-edited rudiments or song builder presets, please make a backup copy of the files rudiments.ini and structures.ini from your current Jamstix 3 data directory to preserve those changes.

--- [IMPORTANT CHANGES FROM JAMSTIX 3.3] ---

1] Jamstix 3.5 does not support sub-hosting of 3rd party plugins. This was dropped due to the complexities involved as we move toward cross-platform (OSX) and RTAS versions of Jamstix. You can still use 3rd party plugins with Jamstix by sending the MIDI output of Jamstix to the desired plugin.

2] Drag-&-drop to the host is currently not supported, please use EXPORT BAR, EXPORT PART and EXPORT SONG instead.

3] The bar editor selection system now uses a left-click/drag scheme to select cells.

4] The rudiment generator structure entry box now uses double-clicking to load the preset menu.

5] The song builder structure entry box now uses a trailing menu button to load the preset menu.

6] 'Adding Cymbal Wash' and similar functions in the tick menu require you to specify the desired end tick by high-lighting a note of that tick before selecting the add function.

7] Audio outputs are fixed (8 stereo)

8] jamstix3.ini is now located in DOCUMENTS\JAMSTIX3

LKWRM_LKWRM wrote:Thanks for the answer I'll try it out.

As far as I've seen, there are no maps for the newer EZX, just did a download.
It could be, that using the DKFH mapping (more kit pieces than any other kit maps everything correctly, I would try that first.

If any mapping would be required for special stuff like articulations, I will try to sort that out and mail that to either Toontrack or Rayzoon for other users.

LKWRM_LKWRM wrote:Regarding the installation of 3.5 I think it gets identified as a new plugin and keeps the old one. I moved my old v3 to a new path to be sure so I don't really know if the DLLs gets overwritten. This is what's mentioned during the install:

Thank you for the input! Will have a look at it.

Peace,
B.

LKWRM_LKWRM wrote:Thanks for the answer I'll try it out.

Ok, had a look at it:

A standard mapping is not enough, since we have to tell JamStix what it can use...
But taking a rather "complete" kit from Toontrack and adjusting that to the kit you want to use is the fastet way.
Everything is more or less MIDI standard and you can check the mapping by licking a kit piece in JS an looking in EZD/SD.
Since some kits come in various sizes, there is not ONE mapping.

Still have to look at the HH stuff, that is a bit special as i remember.

I tested the above with the Roots kit for SD, worked great so far.
Will do mappings for my new SDX stuff as I need them (both Roots, Metal Foundry, Music City, Custom & Vintage).

LKWRM_LKWRM wrote:Regarding the installation of 3.5 I think it gets identified as a new plugin and keeps the old one. I moved my old v3 to a new path to be sure so I don't really know if the DLLs gets overwritten.

The DLL is still there (renamed), BUT 3.5.0 has serious memory loss in my old songs... Even the JS kits get not loaded, no style, no player.
Exchanging the DLLs fixes that, so I can live with it so far. Still strange...

Peace,
B.

The_B wrote: The DLL is still there (renamed), BUT 3.5.0 has serious memory loss in my old songs... Even the JS kits get not loaded, no style, no player.
Exchanging the DLLs fixes that, so I can live with it so far. Still strange...

Do I understand this right: if your old project used JS subhosting, it loads incorrectly in V3.5, such as missing style/player?

Ralph [RZ] wrote: Do I understand this right: if your old project used JS subhosting, it loads incorrectly in V3.5, such as missing style/player?

Jep, tried several songs. As I wrote, since changing the .dll back solves that, I can live with it. Nothing a batch file can't fix

Can provide further info if you want to investigate.

The usual suspects:

Win 7 64bit, Cubase 5.5.3 32 bit, JS old = 3.3.0, JS new = 3.5.0

Ups, while looking for logfiles I discovered that I was working with 3.3.1 Beta 2 for quite a while. Perhaps this explains it?

Contrary to 3.3.x I found no rzdlog for 3.5

Peace,
B.