RAYZOON

Ok, missed the UPPER CASE first time (why is that?).
I'm trying again. 8)

OK something else I noticed here. When adding in JAMSTIX in the IAC box, I can't run Jamstix regularly any longer ( when I click on a drum with the mouse)because Logic automatically picks SUM in the midi sequencer view in Logic X for the midi, and I get horrible loopback noises (inside Logic X). If I just do it Like Ralph shows in the video it does run SS Drums correctly (Jamstix is in midi out mode and so no more loopback noises), as it shows in the video. But in order to run Jamstix by itself again, I must remove the "Sum" virtual wire from the keyboard shown (in Logic X) and run it to another midi port there (Like to the port A from my midisport). Also, It seems to want to go back to the "Sum" when I start Logic X back up... If I remove "JAMSTIX" from the IAC driver box everything god back to normal (Thru the Sum link in Logic X) with Jamstix, but I can not then run SS Drums because the midi won't route correctly.... Hummmm... Do I need a 3rd party midi loopback ?

MIDI routing can get messy in LPX. I wish Apple would just support MIDI output from plugins like VST has done for the last 15(!) years.

Work-around: use the 'Device is online' checkbox on the IAC JAMSTIX port to turn it off and on as needed.

Thanks Ralph.

Yes this "work around" seems to work for Cubase 7.5x as well.

I need to look into this a bit more but it appears to me that when I route MIDI from JS to SD2, the overall output is lower than when I play a drum from within the SD2 GUI.

I would have assumed that since JS is just feeding MIDI to SD2 that the level would remain unchanged.

CudBucket wrote:I need to look into this a bit more but it appears to me that when I route MIDI from JS to SD2, the overall output is lower than when I play a drum from within the SD2 GUI.
I would have assumed that since JS is just feeding MIDI to SD2 that the level would remain unchanged.

Play with the song power knob position to see if it is just velocities.

Beta 32 is now out:

- improved MIDI import dialog
- fixed GUI issues with MultiTrack Studio
- improved GUI behavior when moving window

Ralph [RZ] wrote:

Doc wrote:I cannot record midi out of Jamstix.
Neither in Logic X, nor in Ableton Live 9 nor in Studio One 2.

That's because even though the AUi specification allows for MIDI output, there is no DAW that supports it (amazingly ).

When I enable midi output in EZ Drummer 2 in Logic (of course it's an AU) I actually can record midi.


Work-around is to either use a DAW that can use Jamstix as a VST or use IAC as described here:
https://www.youtube.com/watch?v=5gCcRzs9zPw[/quote]

When I use Jamstix in Ableton Live as VST (not AU) I still cannot record midi.

Thanks guys for the work.

In Logic X, Im getting a "System Overload. The audio engine was not able to process all required data in time. (-10011)" message at times, running JS in midi out, into EZD 2 software. Is this on my end or? Its not constant - only when I see a hiccup or delay for a second at random times....

spikey wrote:Thanks guys for the work.

In Logic X, Im getting a "System Overload. The audio engine was not able to process all required data in time. (-10011)" message at times, running JS in midi out, into EZD 2 software. Is this on my end or? Its not constant - only when I see a hiccup or delay for a second at random times....

I get this as well in Logic X.