Jamstix 4.4.3 Beta 3 (macOS) is now available

[Dewdman42]

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.

This also appears to happen when JS4 is used inside Image-Line Minihost modular, which is the only free solution I know of to connect JS4 to another drum plugin inside LogicPro.

[Nigo]

High Sierra is warning me that only 64 bit apps are supported in the future.

I might have missed a post on this, but will this be addressed?

For now and for me it’s working because I’m stuck with high Sierra because my Mac is too old to update to Mojave.

[Ralph @ Rayzoon]

We still have 32-bit code in the macOS version until about Summer 2019 when it will completely transition to 64-bit.

[Nigo]

This menu has two items saying insert new part after or before. Then below these there are several types of parts to select from.

I suggest that these are combined. Hovering over a part type in this list should unfold an “insert before”/“insert after” sub menu.

As it is now I can select a part type, but not where it goes. Or I can select a non-defined part and where it should go.

[Nigo]

We still have 32-bit code in the macOS version until about Summer 2019 when it will completely transition to 64-bit.

Great. Thanks

(No problem for me - I can’t afford a new Mac before that anyway)

[Dewdman42]

Thanks for letting us know about the 32bit code. I will hold off on upgrading from Sierra a little longer still

[robojam_]

We still have 32-bit code in the macOS version until about Summer 2019 when it will completely transition to 64-bit.

Is the 32-bit code related to the 3D lag that others have noted?

If so, would it be possible to compile a fully 64-bit version without the 3D representation of the kits until the third-party framework is updated?

I'm on Mojave already, so not sure what kind of issues I might get if I install the beta or the final release - have you tested on Mojave?

[thats_rayor]

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..

+1 to this request

Congratulations Ralph! I've been looking forward to this release since the Windows version was announced. Keen to get stuck in and see what this beast is capable of.

[Twist_1]

I've downloaded and installed JS4 through JSManager. How do I load it in Logic X?

I only see JS3 in my instruments section.

[Nigo]

I've downloaded and installed JS4 through JSManager. How do I load it in Logic X?

I only see JS3 in my instruments section.

I had to restart my mac. There’s a bug (feature?) in Logic so new plug-ins are not registered until you restart.