Rayzoon Technologies LLC

[koala]

Hi folks,

I read all the topics that have been posting about the use of LM4-MkII in Jamstix. But nothing could help me.

Following problem:

I use Cubase SX 3 as host. Everything's ok when I use the internal sound engine of Jamstix. But when I decide to use my LM4-MkII as sound engine then there is a red writing in Jamstix' surface that shows 'disabled' and then Jamstix stops running (no sound). When I reload Jamstix in Cubase then everything's ok until I want to use LM4-MkII.
As I said I read the topics about that specific problem but all the tips and tricks couldn't help.

I think, I did all the things right.
1) Choosing the LM4-MkII-DLL-file in the mapping menu (external vsti).
2) Loading a drumset that works, e.g. when using LM4 without Jamstix
3) Verifying the right Mapping, so that it corresponds to GM-Mapping.

Only one time I was succesful and I could play the drums over my LM4. But after I stopped the song in Cubase then I had this 'jamstix disabled' sign again.

So is it a limitation in the demo version that you can't try Jamstix with other VSTis than the internal sound engine or is it a bug ?

I use the Jamstix 1.3 demo version I downloaded today.

Thanks in advance

[Ralph [RZ]]

The 'Disabled' shows up when Jamstix feels corrupted.

Please select at least 6 (stereo) outputs in the mapping tab of Jamstix since LM4-MkII needs that many. Remember to close/reopen your project after making the change so it can take effect.

If it still doesn't work, please try the latest beta here:
http://rayzoon.com/v-web/bulletin/bb/viewtopic.php?t=573
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[koala]

Hi Ralph,

thanks for your fast reply.
You're right, that's it , yepeeeeh.

Everytime I made changes in the mapping/sounds-area, I didn't close Jamstix after the new settings (I changed the number of outputs already before my post but didn't close the app.)

Furthermore I experienced that when I changed the sound engine, e.g. from LM4 to Halion, I also had to close the application after the change for not getting the 'disabled' sign.

Now all works fine.
Thanks a lot for this amazing product.
I will test it some days and then buy it.