Wow!
I’m not going to try to duplicate what is clear to see.
Have a nice day 
Hi @sergeantt67 ! first thank you for this tip, I have never ever tried this… also not sure if supported, although that is ultra cool @Spork
So finally understood, you’ve dragged the MIDI-clip in Cubase to VSTLive, right? I did a test and source and destination were exactly the same with:
- Drag&Drop between the two apps (super cool @Spork even I don’t know if’s supported)
- DAWproject
- MediaProject
Meanwhile I think Import / Export is focusing to preformatted file extensions, like MediaProject or DAWproject the complete song that you also tried I see. I’m doing such project exchange before via the preformatted filetypes only.
I think the best solution was that you’ve sent your files to developers inspect it deeply. I hope they will find the source of your problem.
1 Like
Thank you! Of course I sent everything to the developers, I wrote above, their knowledge is greater than mine and I am sure they will figure out the problem.
Yes and dragging from cubes to vst live works as you saw from my video and it’s great this is the way out at the moment.
And it seems like I could even drag and drop from Studio One to VST Live, I can’t say for sure, but I think I was able to do it, I just don’t have it on my computer right now, but maybe someone will find this experience useful, those who have it can try, but Cubase 13 Elements didn’t seem to allow this, and Cubase 14 Pro does
1 Like
Hi all,
please give us some time to get it all handled.
… and thank you, @sergeantt67, for all of your files and examples. That helped a lot. We could identify another bug with the DAWproject Importer. That one has been fixed. Please re-try the next Pre-Release (2.2.22) coming next Friday.
Now, we’ll analyse the Cubase VST Live Ex and Import routine. We’ll keep you in the loop.
Have a nice time and keep on your great activity in the forum. Thank you!
Michael.
2 Likes
And thank you very much for your work, and of course I will wait, I understand how difficult it is to do all this, the main thing is that you understood the essence of the problem
Hi,
tried to import a Cubase 13 arrangement into VL 2.2.36
Sadly enough the tempomap from Cubase is not imported into VL, which they call tempo track.
Only the first bpm is taken over and the rest has to be edited by hand, which can be time consuming!
Found another bug; the blue line in VL temptrack, indicating the tempo, disappears at some point and does not return at the next tempo changes, please fix this
no way… just did my last import 5 minutes ago (C14). Let’s find a solution!
The easiest: select a MIDI track in Cubase-» click export MIDI,
import that MIDI into VSTL:
question will appear, do you want to update tempo
YES
Delete unneeded MIDI tracks
Done
1 Like
The easiest way is to import the size and tempo track into VST Live, then open Cubase and VST Live at the same time and drag the MIDI file directly into VST Live to create a track for the MIDI instrument there, this is like a temporary solution until the developers find a solution to why the export does not work correctly
Or import via dawproject, but there may be errors on the midi tracks, so it is better to delete the ones already in the imported midi and simply drag them directly from Cubase to the open insert VST live on the desired track of the Cubase midi file
2 Likes
Thanks sergeantt67 and fkalmus for the work-around. Hope this gets fixed in the next VL version
Hi @steve_pin,
… could you please give me Cubase project file (*.cpr)? You can drop it here or send me a PM. Then I can analyse what is going wrong.
Thank you,
Michael.
Hi,
I have also now the same problems with additional notes or long notes as described above. I do my first steps again with VSL Live Pro 2 and test the export from cubase. My first song worked really good without the mentioned problems. But now I have a second song and after the import from cubase, I have in one midi-track additional or very long notes.
My version ist the pre-release 2.2.36.366.
Cheers,
Timo
1 Like
.cpr in your pm
Almost 2 months have passed since the problem was mentioned, but the result is 0, this is very disappointing, I wonder how much more time is needed, another 2 months or a year?)
Hi @sergeantt67 !
That is shaming, please, we like stay here relaxed and polite. Doing imp-exp projects in daily basis, …
This thread contains lots of enties. Is your problem this note-length overlap issue?
It’s a shame when, with the release of a program, functions are advertised that seem to work but on paper, but in fact, for 1 year and 2 months it hasn’t worked, or you bought a color TV, but when you get home and turn it on, it shows a black and white image, and you’re like, “No, it can’t be,” and the manufacturer tells you, “Wait a year, we’ll make a driver soon and you’ll have color,” so it’s not for you to blame me for anything and try to teach me how to write and what to do. I’m still speaking very politely.
You can raise your children at home if you have any.
There is no need for flaming - please keep it civil.
1 Like
Again:
Also as Spork wrote
there is updated Cubase in SDA, guess you’ve tried with that one?
fkalmus and CliveJ thank you but I don’t need your help or opinion relax further) and from today you both are ignored, Cubase 14 version 14.0.30 of course I updated and checked which I reported to the developer providing all the project files, the result is the same
Excellent!
Have a great day .
2 Likes
Sorry!!!
1 Like