RAYZOON

The RTAS Beta is currently limited to one stereo output. This will be fixed soon.

Same problem with Cubase 6.5 64bit and AudioM8. Input is pinned no matter what.

Have to chime in here:

Tested in Ableton Live Beta 8.4b4 64 Bit.

- AudioM8 does absolutely nothing. Audio Jam is sitting dead.

- Although the Ableton CPU meter stays at around 25%, I get a lot of bad crackle and dropouts. I have the Jamcussion - WestAfrica Jam Session loaded and it seems as if Jamstix can't keep up with the load.
Nothing else in the scene so it's Jamstix/-cussion only.
This is the more interesting as overall the 64 Bit Beta of Live seems to work better, faster and needing less CPU on my system with other VSTs.

Is this a case for another "send me the logfiles please" reply?

I already saved it ...

Cheers,

Tom

Edit: 64Bit Live crashes after each use of Jamstix 3.5 beta 10 -> hang on exit. Normally I found it very stable.

Hi Ralph,

This didn't work for me. However, if I mess with the Jamming Input Trim and ResponseRate knobs, the Audio-In will turn itself on and off. When it's on, the Power Knob is full over and when off it's at zero. I hope this helps.

Take care,
G

Ralph [RZ] wrote:Please delete the file jamstix35.dll in your VST plugin folder and then overinstall Beta 10 again. See if that fixes it.

hello

I got jamstix today !

I just loaded 3.5.0 beta 10(x64) in Sonar 8.5.3 x64 to try
the brain panel is not at its correct place, see image :

[url=http://pascaljamet4262.perso.neuf.fr/jambeta.jpg][size=18:4a306ba974]Image[/size:4a306ba974][/url]

sorry if this is a known issue

Thanks for the catch, we'll get that sorted.

Ralph,

Now that it's MIDI out only, how can we control things that were formerly set in the subhost section of the jamstix3.ini file, with a section named after the DLL? For instance, I had the following for BFD2 to set the MIDI notes of the cymbal chokes:

[BFD2]
CH_15=58
CH_16=15
CH_19=57
CH_20=14
CH_22=59
CH_23=16

It seems like we would need at least some kind of global [MIDI Out] section to control those things, although some people may use more than one drum module and still need multiple sets of options. Or maybe there's already some way to do it that I'm unaware of.

I think that the most flexible way to handle this would be to make it part of the kit definition in the GUI, along with the setting to control use of CC4 for hihat and any other settings that were previously per-DLL.

Bill

The solution is the new key map files that will come with the next Beta. They include choke settings etc that were previously stored in the ini file.

Ralph [RZ] wrote:The solution is the new key map files that will come with the next Beta. They include choke settings etc that were previously stored in the ini file.

Ah, cool, that should work well. I figured you already had a solution in mind for this, but I just wasn't sure if it was already there and I was missing it.

Are there any tutorials or threads out there that will jump start this switch from subhosting to MIDI out?