VSTL 3.0.10.88 crashes every time I try to load a certain project file. It was crashing the same under VST Live Pro 2.85, so I upgraded to hope for a fix.
The project file is not huge, just has more tracks than I’ve tried before. I have a dmp file, but it is 76MB and I don’t know where to upload it for review.
These dmp files are ALWAYS binary files. Nobody opens them in text editors. Developers open them with their own utilities to see the stack trace naming mapped functions they can identify in code. It’s smaller than I first thought, so I’m attaching a zip of the dmp in case it can successfully upload.
I should add, that VSTL is blowing up while the project loading Progress meter has just started to show “Apply Project”, so after it has read the project file and is trying to populate objects with the content. I have two project files that have grown by 30% over the last few days, one somewhat smaller than the latest, as it was a backup. Neither now loads, but other smaller project files load. All project files were created using 2.0.85 and earlier versions.
What is unusual about this project is that each of 7 songs has a tempo map and between 5 and 7 audio tracks. I needed to do this to get a click track for each. Since I noticed that the tempo map files. each made from drum audio files in Melodyne Studio 4.0 were taking forever to load, it made me suspicious that it might be causing the project file load failure too. These mid files load instantly in Cubase and you can edit the map or assign a VST to the drum midi.
I believe this is also a separate bug. That bug is: Importing the first file (a MIDI) for a song runs the import on the UI thread, freezing the UI and taking forever to load the file. Cubase doesn’t make that mistake.
Superstition – Time.mid
Size: 20.0KB
Run time: 00:04:27
VSTL3 Load time: 00:13:10
Cubase Load time: 00:00:02
Task Manager VSTL3: 0.3%, 208.3MB
Task Manager Peak during load: 11.8% CPU, 449MB memory
Note: The VSTL3 title bar indicates (Not Responding) during the load and the main menu is unusable. It seems that the UI thread is being used to perform the load, which ist verboten.
I’m uploading a simpler project file - it doesn’t even have any audio tracks in it, and only one song. I includes the imported Take A Letter Maria - Time.mid which installs the tempo map. (Plus a bunch of Global layers and stacks configured)
This makes me suspect that such tempo map or drums midi data is overwriting some project object boundaries during save that is causing the project load process to fault. However, this was also happening the same in VSTL 2.0.85 and earlier, so you don’t need to look in new code.
Also included below is the MID file I’m importing.
Since Celemony Melodyne Studio 4.0 is creating the *.mid files from drum audio stems, I’ll try to “clean” these first by importing them into Cubase and re-saving them before I load them into VSTL2.
