I just noticed that everytime WL crashes it doesn write to the event log, so maybe this will be usefull for Steinberg…
Everytime I start up WL 7.01 (this didn’t happen with the prior version) on win7 64 bit and I open a new wav file this WL crashes. When I open it again and then open the same file it works. I think this has to do with the *.mrk file creation
If I open a file that already has the *.mrk there’s no problem.
I have to kill the process in task manager and then restart.
mrtomcat: I don’t understand the reference to the .mrk file creation. I thought the .mrk file was only created when you create a Mark, but it doesn’t sound like that’s what you’re doing.
PG was very helpful and said he was fairly sure there was a bug somewhere - but he needed me to run some debug code on the PC which I wasn’t in a position to do. Recent WL updates haven’t fixed it but I’m still pretty much running v6 so not to concerned. Hoping the eventual move to 64bit will fix it.
Have you tried different locations for the peak file creation? Like c:\temp or make a new folder called gpks, something like that? (Options/AudioFileEditingPreferences/Create In Independent Folder - on or off). Unless I missed it, I don’t see any mention of that in the previous posts.
It does create the file before it crashes, that’s why it doesn’t crash the next time around because the file is already there.
it’s definetely related to the .mrk file that gets created first time a new wav file is being opened
NOTE once again this was NOT an issue with the initial WL7 release it started with the first patch.
I just played around with different folder locations, same results.
Here is the event viewer dump on the latest wavelab build:
these are standard broadcast wav files coming out of Nuendo.
And the moment I open a wav file in wavlab it creates a .mrk file
Is there maybe a setting that would disable that? I see a Markers tab in my workspace
ok, now ever since I started trying to change the location of the temp files it is no longer creating a mrk file (I reset everything the way I had it before…or so I thought…) and now wavelab crashes everytime I open a wav file without a marker and since it’s no longer creating one every new wav file is unuseble. SHOOT!
Back to wavlab 6 again. PLEASE help me figure this out, I finally got used to wavelab 7
Yeah…okay…here’s one of the first things found - on Google…
“The file QtGui4.dll is a legitimate component of Adobe Photoshop Elements. The file size is 5246976 with the MD5 signature of 5F46BBD36877300007A8CA46F9DEA3B3. Adobe Photoshop Elements is the consumer version of the Adobe Photoshop raster image editing product. It includes most of the features of the professional version. But it has fewer options. Besides they are simpler. The program enables users to create, edit, arrange and share images,…”
And a further investigation on the Adobe forms - does in fact point to this as a Quicktime component…
What exactly does this file have to do with Wavelab 7?
It’s fairly irrelevant to us, as end users, what the exact dll is doing as we don’t have access to the source - do you have this a problem with gpk/mrk file creation causing a crash ? or is this just a curious enquiry ?
For whatever reasons the mrk files are no longer being created when I first open a file, it’s down to the .gpk files
Things are behaving a bit different now ever since I did some settings changes even though I reverted back …
Anyway, here’s what’s happening now (maybe that was the problem all along and the mrk was just a side effect):
I open a wav file freshly exported out of Nuendo, Wavelab opens the file and on the top view of the wav file there is an error stating: “Cannot create Peak File”. If I now click anywhere within wavelab it crashes.
I have to kill the process, restart and open the file again and all works fine.
–before I restarted the process I checked in the directory and the peak file was created even though there was an error message–
I changed the path of the peak file creation with the same results.
Good news is that I can use wl7 again but I still would like to see a fix for the nasty crash
