Hi,
I thought it is better to start a new topic than to mention it in another topic with a complete different headline.
I am on Windows 11 Pro and have the latest pre-release of VST Live installed. I have a little project in Cubase with 5 to 6 midi-tracks. And when direct exporting from Cubase to VST Live, I get wrong midi-notes in some midi-tracks. Those notes are much too long and the playback isn’t correct of course.
I read here in the forum, that also other people have this problem in the past. When I export the midi-track itself and than import it in VST Live with the import-button in the tracks-menu, everything is allright.
I have two pictures here, where you can see the differences in cubase and after the import in VST Live.
@fkalmus, is right. Every Detail willl help. And we would need your Cubase project file (*.cpr) to get it reproduced. Could you please give it to us? Drop it here or with a PM.
Hi,
I will upload it here this evening, when I am back at home.
Sorry for the missing details. English is not my former language, so sometime it is difficult to describe everything correct.
I have Cubase Pro 14 (latest release) and do the export/import via MediaProject. I thought this problem is already known in some situations, because it was described here in the forum in the past. But if not, I will give you more details when sitting in front of my daw.
Testprojekt Cubase-VST Live.zip (2.6 MB)
Hi,
here is now a simple example with only one midi-track in cubase, showing my problem. I have the cubase-project, the vstlive-project and the export-file from cubase. Also two pictures of the midi-notes in cubase before export and in vstlive after import.
I have Cubase Pro 14.0.30 and VST Live 2.2.36.366 under Windows 11 Pro (24H2). My interface is a Steinberg UR816C, if this information is necassary (I think not).
And by the way, another problem is, that the parts from the arranger-track in cubase are created in vst live, but the trigger point, the start point of the part is not transferred. You have to set all start points manually. Not a big problem, but it would be nice if it would be set automatically, just like it is in cubase. Thanks a lot.
Hi, something new with this case?
I did an export this weekend and have nearly the same problem. It was much better than last time, but not perfect. I exported and imported each track as a midi-file and it worked fine.
And of course the triggerpoints of each event in the arranger-track in cubase are not imported. The events were created, but the triggerpoints are all at the startpoint and I have to set them manually. Not a big thing, but a direct export should also include the correct startpoints (trigger points) of the events from the arrangertrack in cubase.
Hello everyone, if you export a dawproject with one time signature, I will give my example 12/8 and even with a variable tempo everything is imported into VST live correctly.
But if, for example, the beginning is 6/4 and then goes into 12/8, here again for some reason the errors are the same as they were, as examples have already been given many times.
If we talk about a simple export when you select VST Live in Cubase and export, then there are no changes here, it didn’t work and it doesn’t work.
Hi,
yes I talk about a simple export from Cubase direct to VSTLive. Here I have the problems mentioned above.
I will try the dawproject next time. Maybe this is a possible workaround.
And it’s not a Cubase problem that errors are introduced during export, you can load your exported file back into it and it will be perfect! Is the problem only in VST Live. Let’s hope that someday the developers will be able to overcome the export-import bug
With dawproject I seem to have found a solution now at least it worked for me.
My midi event started from the 20th tact and then I got this nonsense as in the picture in the post above.
I made an empty midi event from the 1st to the 20th tact and glued them together in Cubase and dawproject worked flawlessly
