Export MIDI has blank parts

Foolomon_ · Post by **Foolomon_** » Tue Dec 11, 2012 3:29 pm

Using Charlie for verses and Dave for choruses
Using Modern Funk for both
Using Standard Funk - Mini kit

I got an entire drum line that I like so I want to export to MIDI and have the MIDI file (played back in Cubase 6.5.2) drive JS as a sound module. I export the MIDI file but when I import it into Cubase I see that there are random measures (1 or 2) that are completely empty of MIDI events in spite of the fact that those measures are composed in JS and playback if I use JS in the normal fashion.

Incidentally, when I import the MIDI file it seems to reference a VST soft synth because it always causes Cubase to load Halion. :/

Foolomon_ · Post by **Foolomon_** » Tue Dec 11, 2012 3:48 pm

Okay I thought this next part may have been attributable to Melodyne but I'm not using Melodyne this time nor have I even loaded it for this project.

My project is now corrupted. Cubase hangs on load and requires a reboot of my computer.

This project is a rework of a song that got corrupted once before. But then I had Melodyne loaded so I wasn't sure where the issue may have been.

I started this rework yesterday. And even today everything behaved normally...until I attempted to import the MIDI file as described above. That's when two things happened:

1. The VST Halion SE was loaded after the import. This is extremely weird.

2. After submitting the previous post, I attempted to close Cubase. The project window disappeared but Cubase refused to close, requiring a reboot. After doing so, I attempted to open the project again, which was working 100% as expected just prior to the import and the open failed due to some form of corruption.

This is Cubase 6.5.2 64-bit with JS 3.5.0 64-bit. I'm using Guitar Rig 5, Padshop (that comes with Cubase 6.5.2), and the rest are stock plug-ins.

Foolomon_ · Post by **Foolomon_** » Tue Dec 11, 2012 4:02 pm

Hold the phone.

I tried to open an auto-backup of the project and waited it out. It took forever, but when it did open (successfully!) the JS GUI was open.

I thought I had read somewhere here on the forum that there were known performance issues when the GUI was left open. Am I going senile or is this a known issue?

Post by **Ralph @ Rayzoon** » Tue Dec 11, 2012 5:26 pm

"The VST Halion SE was loaded after the import. This is extremely weird."

Yes, that is weird. Not sure what's going on there but you may want to save projects with JS GUI closed to see if that makes a difference with the load time issue.

Blank MIDI fix: play the whole song through before exporting.

Foolomon_ · Post by **Foolomon_** » Tue Dec 11, 2012 7:46 pm

Well, I do have the MIDI file still if you want me to send it to you. Of course I personally think that's more of a Cubase issue, but you still may want to check the MIDI contents to ensure their correctness.

Out of curiosity, what's in the SysEx data? It looks like it's text data, so I'm assuming it's a "Generated by JamStix" statement or something like that?

Post by **Ralph @ Rayzoon** » Wed Dec 12, 2012 8:31 am

There is a 'Created with Rayzoon Jamstix' meta message in the MIDI file export.

The 'holes' should not happen if the project was played from start to finish, stopped and then exported.