Crash when trying to display waveforms

Discussion about: tracktion.com
anbz
KVRist
72 posts since 23 Jan, 2014

Post Thu Jul 18, 2019 1:08 am

Hello.

I've just realized why Waveform crashes sometimes on big projects.

For example, I'm mixing live shows with many edits (hundreds of cuts and regions) and I see that when I try to zoom in on where I created many regions, Waveform has many problems to handle this, blocks and crashes.

If I disable displaying of the waveforms, it's ok. What is especially inconvenient to work.
The same if I choose or not the Hi-Res waveforms !

I work on a PC, last version of Waveform but it happens since always on previous versions too.

FigBug
KVRist
368 posts since 3 May, 2005 from Victoria, BC

Re: Crash when trying to display waveforms

Post Thu Jul 18, 2019 6:52 am

Can you go to Settings > Maintenance and make sure "Send Crashes" is enabled.

If so, can you look in your log file for a line that looks like:

Code: Select all

Crash report uploaded: xxxxx.dmp as yyyyyy.dmp
If you send me that line, I can look up what's going wrong. Or just sent me your entire log file at roland@tracktion.com

anbz
KVRist
72 posts since 23 Jan, 2014

Re: Crash when trying to display waveforms

Post Fri Jul 19, 2019 2:51 am

Ok done !

Thanks

anbz
KVRist
72 posts since 23 Jan, 2014

Re: Crash when trying to display waveforms

Post Mon Jul 22, 2019 3:01 am

Hello.

I just wanted to precise a thing I've just noticed.

If I open an edit with hundreds of regions, etc.... and if they are all displayed (Zoom to fit), the edit won't open, it crashes just before displaying the edit.

If I turn off displaying of waveforms, the edit opens. Once opened and if it all fits the screen, activate the display of the waveforms crashes the software.

If I do that but just with a small area of regions displayed, it works but if I zoom to fit, it crashes.

Hope it helps and hope it will be fixed, it's really inconvenient. Thank you !

FigBug
KVRist
368 posts since 3 May, 2005 from Victoria, BC

Re: Crash when trying to display waveforms

Post Mon Jul 22, 2019 2:42 pm

If the edit isn't too huge (or you can create a small edit that recreates the problem), can you send that to roland@tracktion.com as well.

anbz
KVRist
72 posts since 23 Jan, 2014

Re: Crash when trying to display waveforms

Post Tue Jul 23, 2019 6:53 am

It's a pretty big project, 40Go approx.

Will try later to consolidate one edit and see if it's useful to send it to you.

Thanks

gerk
KVRist
48 posts since 27 May, 2019

Re: Crash when trying to display waveforms

Post Tue Jul 23, 2019 7:13 am

anbz wrote:
Tue Jul 23, 2019 6:53 am
It's a pretty big project, 40Go approx.

Will try later to consolidate one edit and see if it's useful to send it to you.

Thanks
40 GB?
24bit/48K WAV is ~1 GB an hour... you have 40 hours worth of DVD quality sound in your project?

anbz
KVRist
72 posts since 23 Jan, 2014

Re: Crash when trying to display waveforms

Post Tue Jul 23, 2019 8:43 am

A live concert of nearly one and a half hour...
34 tracks + ultra takes
;-)

FigBug
KVRist
368 posts since 3 May, 2005 from Victoria, BC

Re: Crash when trying to display waveforms

Post Thu Jul 25, 2019 7:58 am

I finally had a chance to look into this but haven't been able to reproduce it. (I also sent you an email). I'm guessing it's a memory usage issue with that much audio. I'll try and generate some huge wave files to see if I can reproduce.

anbz
KVRist
72 posts since 23 Jan, 2014

Re: Crash when trying to display waveforms

Post Tue Jul 30, 2019 2:31 am

Hello and thanks for your help.

I've been able to copy everything on my new MacBook Pro under Bootcamp and could test the same project copied from my older PC to this new unit.

No problem here with crashes while displaying waveforms.

For information, on the PC, I have 8Go RAM and a i5 3.2Ghz processor, 4 cores.

16Go RAM on the Mac and an i7 2.6Ghz 12 cores processor.

It looks like a memory problem effectively.

But does that mean it could arrive if I mix on the Mac a more bigger project than this one ?
It happens frequently in my case.

It makes me think of my older post concerning the difficulties of caclcuting waveforms in the DAW. Every time you lose focus on the app and you came back on it while waveforms are calculated, all waveforms are recalculated again from scratch.
I was told that it was not really a big problem enough to spend time on it.
But, it's really hard to work with when that happens with the client in front of the screen because calculation needs CPU and reading the project at these are time doesn't work well too.

Not the kind of thing we see on ProTools for example.

Just wondering if these two issues are not a bit linked ?

Many thanks for your help.

Return to “Tracktion”