He @Herbert_Schmitt,
it should be fixed with the next Pre-Release 2.2.32 coming later the day Give it a try and let us know if it working know. We also added the Option to Dissolve Format0 to Multi-Tracks.
See you,
Michael.
2 Likes
That sounds fantastic. Iām looking forward to testing the update today. Many thanks in advance.
I will report back.
Herbert
Test report
VSTLive pro 2: VERS_2.2.32.356_Fr_2025-05-23 Midifile Import.
Tested on a :
Processor Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz 3. 40 GHz
Installed RAM 32.0 GB
Graphics card NVIDIA GeForce GT 730 (2 GB)
System type 64-bit operating system, x64-based processor
Edition Windows 10 Home
Version 2009
Operating system build 19045.5737
- uninstalled VST Live pro 2 version 2.2.31.353.
- installed VST Live pro 2 version 2.2.32.356.
- new project created.
- midifile imported.
- all 16 midi tracks output set to MOTU midi expres XT Out Port 5.
- extracted lyric window and set font spacing.
- start and end marker set.
- transport start pressed.
Problems found:
1 The midifile tempo (94 bpm) is displayed correctly, but sounds at a faster speed.
~120 Bpm . Manually changing it to 94 bpm does nothing.
Switching the tempo track on and off is also useless. The midifile also runs bumpy.
-
Text is not synchronized with the sound.
-
after stopping with the space bar and pressing the space bar again, the midi file was partially reset and midi tracks had GM piano sounds again.
The midifile āReturn To Senderā song 3 is completely out of sync.
Herbert
Not necessary btw, just install the new one.
ā¦which one was that? Sorry, hard to keep track.
Tried multiple of Rolandsā, thanks for the project! But canāt find problems. It would be of great help if you could let us know āuse this file, select this Song, do this and that and then this will go wrongā, thanks!
The last one I āfixedā everything and saved it. The one before, last time Iād opened it, various track event sized had been ācut shortā by their own accord, despite knowing that they were correct before saving and shutting LIVE down.
Problem, sometimes the track event lengths inadvertently change. A MIDI track just stops half way into it. Open the tracks tab, drag or type in the proper length, and it still might cut short unless selecting a different song and returning first.
I have not had time to experiment with this weekās 2.2.32 release yet. Sorry.
@musicullum
I was aware that I didnāt have to uninstall anything. I just wanted to show a list of my working methods.
The example I have shown: Song 2, is the same Midifile that I had previously provided to M. Spork via PN and which did not work in VST Live Version 2.2.30.353.
The example in song 3, āReturn To Senderā, is a random midifile I picked from a professional midifile producer.
Actually, it doesnāt matter which midifile I used. VST Live must be able to import every professionally produced midi file without errors. This is not possible at the moment.
Please also allow me the following note. I have been trying since day 1 of VST Live to port my previous stage program to VST Live. Iāve spent so much time testing VST Live and Iām still no closer.
I know that you and your team are doing everything you can to make the software a success. You deserve a lot of credit for that. For my part, I am no longer willing to contribute to the success of VST Live. I will become a silent observer.
Herbert
1 Like
Thatās exactly what we want too, and it works well here with many files now, so Iāll try get that file (āReturn to senderā, correct?) from Micha and have a look.
@musicullum
Iām working on a report.
So much in advance. I have created a new project and randomly bought 10 Midifiles
imported. I would like to comment on this. Please be patient a little longer.
Thank you Herbert
@musicullum
@Spork
MIDI file import report
As described above, I imported 10 purchased MIDI files at random and yes, your revision imported the MIDI files correctly.
In this respect you have achieved an improvement in the import version.
Letās stick with the example of I Donāt Wana Loos You by Tina Turner, whose MIDI file I sent to you and Michael Spork via PN.
Test setup used:
- Lenovo notebook
- Yamaha GENOS2 Workstation
- VST Live pro 2
Unfortunately, there are still problems.
After starting VSTL2pro, the data from the first song was transferred to the connected Yamaha GENOS2 device.
I can see all the sound settings in the GENOS2 mixer.
After pressing the Start button, the transport starts, but no notes are transferred to the Midi device.
Something is stuck. Even repeated closing and opening could not get VSTL2pro to send Midi data (note values).
Only after booting the computer twice and starting VSTL2pro and loading the MIDI project was data sent to the connected device.
Interesting next scene. Every time I closed VSTL2pro, I was asked if I wanted to save the changes.
I had not changed anything except Start and Stop. After that there was no more interference.
Playing all 10 midi flies revealed further problems.
For your information. I have set the action for all Midi files: Start song at start marker, stop song at song end marker.
In the MIDI preferences, the option Tracking controller data was activated. Also the tracking at start.
Some of the songs I started in a loose sequence were played correctly, some were not.
In the current version 2.2.33.359 (at least on my system) VSTL2pro was not able to deliver a stable, always repeatable, expected result.
I think I have found the reason for this.
If you set the start points of the individual songs to bar 1, all the MIDI files saved in the song list are played correctly.
Stable and always repeatable. This means that all channel controllers, Prg-Ch are sent correctly.
If the start point is set to bar 2, the VSTL2pro should have already sent the controller data from bar 1 to bar 2 so that the device setting is available when the song is started. (Controller, Prg-Chg are set). This is exactly what does not work reliably for me. Sometimes the data is sent, but most of the time it is not. In addition, the start button quickly sends a GM reset. Even if the correct controller, Prg-Ch data is present on the Midi device, the setting is invalidated by the GM reset. This also leads to problems in the rehearsal room if you have to stop a song and want to continue at the same point.
As I have learned, Start performs a GM reset and sets all 16 keyboard chanels to GM sound. So you have to start the song from bar 1 to get all settings back. As far as I know, a MIDI file contains a reset command at the beginning. This reset command in the MIDI file makes a second reset on the start button superfluous. Unfortunately, I donāt have the technical ability to demonstrate this clearly in a video.
Thought experiment:
You might want to think about offering different āREST bodiesā.
This would allow the user to set what they need for their application.
A scenario for my application could be:
Send GM reset and XG reset on stop
| Send Reset: on Start | Send Reset: on Stop | Send on Midi Device Connection |
|---|---|---|
| No | No | ān/cā |
| GM (General MIDI Devices) | GM (GM Devices) | List of available Midi connections |
| GS (Roland Devices) | GS (Roland Devices) | List of available Midi connections |
| XG (Yamaha Devices) | XG (Yamaha Devices) | List of available Midi connections |
You can better judge whether this fits into your concept and brings about a solution.
Last but not least, a wish regarding the midi file import.
1. Convert Markers into Parts.
For me it would make sense to add the markers found in the midi file as song parts.
In the best case, you can set the MIDI option whether you want this or not.
2. Enter track controller data in the Inspector and Mixer
Is it possible to set the CC values #7 = Volme and CC#10 = PAN
to the Mixer and Inspector when importing the Midi file data and link them to the track data so that they are also saved permanently?
Or is this already possible and I just donāt know how?
Mixer:
Resume:
- Midi file import has been improved.
- The safe and stable midi file usage still needs to be improved.
- Not usable for me at the moment.
Please excuse the fact that this article has become so long and actually deals with two topics.
Thank you for your patience.
Herbert
1 Like
It certainly does not unless printed in the track. VST Live does not send any SysEx by itself.
Some may do that.
GM Reset is a SysEx message, and SysEx messages are not beeing chased.
That looks like a local problem, no reason why it should notā¦
As you repeatedly report things are sent (or not) on Start, what are your preferences for MIDI Chase, and Chase on Start? Maybe try to change and see if it improves?
We cannot reproduce this. But if you rely on GM Reet beeing chased, as said, it does not.
We like to help but need examples and instructions how to reproduce, including relevant preference settings, thanks.
Is he sending it directly to a MIDI device, or routing it through a Layer first?
Is he also entering a GM Reset in a layer?
Could it be that the imported MIDI file has it embedded, but heās also entered it manually as part of an instrument layer?
My understanding is that clicking a song part will have whatever is set up in layers get sent, and then if any tracks exist in the part they begin playing (Sysex, Bank, Program, Pan, Volume), plus start the sequencer playing, etc.
Iād need to run some tests to see exactly what happens, it could be confusing if layers are set to do one thing, and MIDI track data is sending something conflicting. If you do have sysex, program changes, pan, pitch bend, and volume entered manually as part of a layer, stop it, then start it again (by clicking the song part, or play in the transport), does it resend the layer stuff, or is that strictly a one time thing that only happens ONCE a song is activated?
Point to my post, for Herbert_Schmitt:
Check if you have any conflicting things on a ālayerā pointing to the same instrument that the MIDI tracks are transmitted.
@musicullum
Thank you for your explanation and for dealing with this.
Finally, I would like to say that my project does not contain any layers or stacks. Itās just a MIDI file project with a notebook, VSTLive2 pro and a connected Yamaha GENOS2 Workstation Keyboard. All data is sent from the respective tracks to the Yamaha GENOS2.
Please close this treat.
It was originally about the improved import.
I have marked this as solved with a check mark.
Many thanks Herbert
Translated with DeepL.com (free version)
No problem, I didnāt mean to imply user fault or that thereās not a Live problem. Iāve run into plenty of them with little actual use, and will probably find more. I only wanted to explore a possibility.