Jamstix4 Crashes with Click/Drag Midi Operation

[Elton_John]

Hello. I am running Jamstix4 within Cakewalk By BandLab (ver. 2022.112) under Win 10 64-bit.

Three times now I have watched CWBBL and JS4 crash when I tried to do a Click/Drag Midi operation within JS4. I can start either by Ctrl-Alt clicking on a Song Part, or by selecting Export Midi from the Song drop-down menu. When the widget appears, I click on the "Click/Drag Midi" button, and drag the cursor to the CWBBL midi track, release the mouse button, and CWBBL and JS4 both crash.

I also own a copy of Reaper, but have not yet tried to click/drag midi with JS4 hosted in Reaper.

Has anyone else had this problem? Can anyone suggest something I am doing wrong or can fix to make click/drag midi work without crashing JS4 or CWBBL?

Thanks.

[Azimuth (Archive)]

It works fine in Reaper for me. You might want to try saving it as a midi file and then importing it into Cakewalk and see if that works instead.

[Elton_John]

Update:

After further testing, I have learned that if I try to do a Click/Drag Midi operation to drag midi data to measure 1 or 2 of the midi track in CWBBL project, the Click/Drag Midi operation will crash JS4 and CWBBL. BUT, if I do the same Click/Drag Midi operation and try to drag midi data to measures 3 or 4 of the midi track in CWBBL, there is no crash and CWBBL and JS4 continue to operate normally.

I will continue testing and report further results.

[operandx]

Now that the new forum is up and running and Ralph is back in the building, I thought it appropriate to bump this issue, which for me is the No1 problem with JS4. The regular crashing on Midi drag and drop export has been reported for many hosts and it would be absolutely game changing for my workflow if this could be fixed. Yes, I know you can export as a file and reimport into the DAW but this is a time consuming extra step.

Most often the DAW just poof crashes, occasionally there is an error message before the crash indication a memory access violation.

[R Green]

I’d also suggest the export of a midi file to the desktop rather than dragging and dropping to host. It usually works for me (although I’m on osx and so don’t get any support now). For those lucky PC people who will enjoy JS5 I’d suggest a progress bar for the midi export operation as it can take a long time.

[Br_ndo]

Now that the new forum is up and running and Ralph is back in the building, I thought it appropriate to bump this issue, which for me is the No1 problem with JS4. The regular crashing on Midi drag and drop export has been reported for many hosts and it would be absolutely game changing for my workflow if this could be fixed. Yes, I know you can export as a file and reimport into the DAW but this is a time consuming extra step.

Most often the DAW just poof crashes, occasionally there is an error message before the crash indication a memory access violation.

This just bit me actually. I had Jamcussion ("PERC") active in the Jamstix gui, and clicked hoping to export the MIDI for my project. Everything froze at that point. Normally I can use the Drag/Drop option's Export to MIDI file option which works fine for me (as others have said in the forum). But with "PERC" as the active option for drumkit, it hangs and I have to kill my project. Extra aggravation as I haven't saved in a while so I'll be retracing my steps. (Nice to have you back Ralph - I agree with others that this feature could get some love. (Right after a VST3 version )

[Azimuth]

Just for your information Ralph when you look into this drag and drop crash issue, as I posted back in 2023 this issue did not occur with me while I was using my MS Surface 4. I no longer have the Surface and am now using a Lenovo laptop and this does occur on this computer intermittently but fairly often. It's not a function I use often so that's likely why I haven't noticed it until now that this has been brought back up. Perhaps it is hardware related, but that's just a guess.

[Ralph @ Rayzoon]

Definitely will have a look at this.

[Azimuth]

Hi Ralph,
I just emailed the support.zip file to support@ after recreating the crash to desktop.