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.
Jamstix4 Crashes with Click/Drag Midi Operation
-
Elton_John
- Posts: 29
- Joined: Thu Mar 31, 2011 9:16 pm
-
Azimuth (Archive)
- Posts: 1674
- Joined: Fri Nov 19, 2010 2:16 am
Jamstix4 Crashes with Click/Drag Midi Operation
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
- Posts: 29
- Joined: Thu Mar 31, 2011 9:16 pm
Jamstix4 Crashes with Click/Drag Midi Operation
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.
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.