RAYZOON

jdockerty_1 wrote:Hi All, Not sure if this is a bug I've noticed, but what happens is the actual Visuals of the drumstick movement freezes up whilst the song is still playing, the way to get it going again seems to be full screening it then it happens again after that also.

I had the same problem happen.

Another thing i notice is that the 3D drum kit is lagged behind the actual sound by a noticeable amount, which is confusing.

I can't seem to find the SSD5 maps in the OS X beta. Did that update make it to the OS X version?

Some more general comments....

The same kits sound totally different in JS3 vs JS4. JS4 sounds like a transient designer has been used, the snares are tighter, actually sound a lot more processed, which is not necessarily a bad thing usually I end up having to do that kind of processing in my DAW with Jamstix to get it to sound more like that, so in essence JS4 sounds more like what I want to begin with. That being said, JS3 also had a very realistic unprocessed sound before with those same kits.

Care to comment about the sound processing in JS4 vs JS3....is it possible(optionally), to make JS4 have the same unprocessed sound like what comes out of JS3?

Dewdman,
Concerning the delay on the 3D kit, what latency are you running and what Mac do you have?

The SSD5 map is not in the Beta, yet.

For the sound sculpting, the main functional changes from JS3 to JS4 are in the EQ center frequencies and the new volume envelopes. If you want, you can manually create a folder in ~/Music/Jamstix4/data/kits and copy some JS3 kits into it. They should sound identical in JS4.

Just want to understand WHERE its changed so that I can deal with it in the future if I want the old sound.

The changes are all in the JS4 software as well as the presets (we even re-edited expansion Paks for JS4) but the source samples/recordings are identical.

Also, I think you're saying if I copy the JS3 kits into that location I would lose the new JS4 versions of the kits because they are named the same yes?
So what do you think would be the best way to have best of both worlds?

I would create a new folder in ~/Music/Jamstix4/data/kits, let's say 'JS3 Kits', and then copy my favorite kits from JS3 into it.

Dewdman42 wrote:I had no idea it was even possible to adjust the sound of the kits in those files, beyond what is possible in the UI. Or am i misunderstand that now?

The sound in the JS4 kits is done completely via the controls in the JS4 GUI: EQ, compression, volume envelopes.

roger that. For some reason your replies are coming onto the board as if they are from me. weird.

Anyway, thanks, I see now, all is clear. I do like the new kit settings, but I also like the old ones in their own way..

I may have hit 'Edit' instead of 'Reply'. Sorry about that

another thing that would be helpful is if you compile an AU-MFX version of the plugin, in addition to the AUi. My understanding is that this is literally as simple as changing one line of code that specifies the "type" and compiling it.

When used as an AU-MFX, then all audio is ignored, so a more ideal version of the AU-MFX would disable audio functions also just to avoid any unneccessary calculations or confusion.

This would make it very easy in LogicPro to route the midi output to other drum plugins such as SSD5, etc..

Right now, the only way it can be done that I can see is by using Plogue Bidule or some other plugin sub-hoster in order to get midi out from the VST plugin and send to next instrument.

another problem with the beta...when using JS4 inside BlueCatAudio Patchworks, (in order to route midi to another plugin), every click of the mouse causes the gui to go entirely blank (white), clicking again, brings back the gui. So if you click on a button, the gui goes blank, then you have to click on the white area hoping you aren't accidentally hitting a button, so that the gui will repaint itself.

This only seems to be happening inside BlueCatAudio Patchworks, which happens to be very useful for Jamstix inside LogicPro in order to route the midi.

Perhaps you and the author of Patchworks can figure out why. This used to happen with JS3 too.