Weird Bug in Tempo View Mode

[MMP]

I am having an issue in SawStudio (on Win11) that is very strange. When in tempo view, SAW is crashing when zooming all the way in on a region, but only on certain tempo settings. For instance, 240, 120, 80 and 60 all crash. But, 130, 85, and 65 don*t. This behavior is consistent no matter the sample rate of the session or loaded file. Any thoughts?

[jmh]

Do you have a plugin that is common like a vst that syncs to tempo? Maybe on your default session.

Do you have grid enabled?

By tempo view, are you referring to multitrack with the timeline in tempo mode?

[jmh]

What else?

snap to grid?

Are you setting tempo in a map, or just the default set tempo?

I just tried 60 using default set tempo (in 32 bit - are you in 64?) zoomed with no issues. Are you linked to sac or mws?

Could you be using any common regions across sessions? If so try deleting the .wpd files (a long shot since this doesn't get used at full zoom). You can get weird problems it the audio file is edited where the region data refers to non-existent audio - for instance save while in record mode then a power failure after a delete to cursor. If you had edited audio offline and the file size was slightly different?

Just grasping at straws...

[MMP]

It happens with grid mode on or off.

No plugins.

Yes, multitrack view with tempo mode on. Doesn*t happen in other viewing modes.

[MMP]

No tempo map. SAW64.

No link to either MWS or SAC.

It happens with any single wave in any new session.

Thanks!

What else?

snap to grid?


Are you setting tempo in a map, or just the default set tempo?

I just tried 60 using default set tempo (in 32 bit - are you in 64?) zoomed with no issues. Are you linked to sac or mws?

Could you be using any common regions across sessions? If so try deleting the .wpd files (a long shot since this doesn't get used at full zoom). You can get weird problems it the audio file is edited where the region data refers to non-existent audio - for instance save while in record mode then a power failure after a delete to cursor. If you had edited audio offline and the file size was slightly different?

Just grasping at straws...

[jmh]

What do you have in timeline pulldown for

Tempo settings -> tick resolution

the 3 grid checks
grid-settings -> tempo
_______________

This happens with successive + key, numpad number, or both?

I tend to always use + & -

...or maybe mouse - is there a way to thumbwheel in?



What if you move home down the timeline, then move the cursor to the left of home, then zoom?

[jmh]

In windows (or the app shortcut?) you could try turning down or off border thickness. I seen to remember some having issues with that.

[MMP]

I have resolved the issue with a fresh SAWStudio64 install and saving a new default Mix template from there.

Hope to never run into this strange corruption again.

[MMP]

Not quite out of the woods. While new sessions don*t exhibit the bug, old ones do. I need to do more digging.

[jmh]

What do you have in timeline pulldown for

Tempo settings -> tick resolution

grid-settings -> tempo
_______________


I think these fields might be used to generate the tick spacing on the tempo timeline. Make sure they are set to the same value as the new default session in old edls.

[MMP]

Tick=240. Have tried others
Grid-settings= 1/16th note. Have tried others

They are the same in old & new sessions

What do you have in timeline pulldown for

Tempo settings -> tick resolution

grid-settings -> tempo
_______________


I think these fields might be used to generate the tick spacing on the tempo timeline. Make sure they are set to the same value as the new default session in old edls.

[jmh]

Maybe disable half the tracks, then the other half. If both do it it wouldn't be a track - otherwise you would be able to find the offender?


If that doesn't help maybe you can 'blend session' to recover your original work.

[Dave Labrecque]

...or maybe mouse - is there a way to thumbwheel in?

Sidebar: am I to understand that you don't use the mouse's scroll wheel to zoom? (Maybe you don't use a mouse?) Dude. I remember that function changing my life twenty (or more) years ago. Try it. You'll like it.

[MMP]

One track test session still fails.

Blend session does work, so there is a workaround.

I am curious to find the source of the issue, however.

Maybe disable half the tracks, then the other half. If both do it it wouldn't be a track - otherwise you would be able to find the offender?


If that doesn't help maybe you can 'blend session' to recover your original work.

[MMP]

I do use zoom with my trackball. Source of zoom doesn*t matter-trackball, keypad, + & - keys all cause a crash.

[MMP]

Here is a very small SAW64 session that exhibits the crash on my system:

https://www.dropbox.com/scl/fo/nvxsry2n ... 23dp5&dl=0

I would be curious if it also fails for someone else. Select tempo view mode and zoom all the way in. Does your session crash?

Thanks!

[Dave Labrecque]

One track test session still fails.

Blend session does work, so there is a workaround.

I am curious to find the source of the issue, however.

Could it be a single EDL corruption that got Save As'd into "child" EDLs down the line? If so, that would be sort of a one-off--not worth worrying too much about, no?

[Dave Labrecque]

Here is a very small SAW64 session that exhibits the crash on my system:

https://www.dropbox.com/scl/fo/nvxsry2n ... 23dp5&dl=0

I would be curious if it also fails for someone else. Select tempo view mode and zoom all the way in. Does your session crash?

Thanks!

Crashed confirmed over here. BTW, the Tempo Mode setting appears to have saved with the session; that's how it opened.

[MMP]

It has shown up during sessions with client present kind of randomly. I would like to find the root cause (if identifiable) so I can prevent the crashes. The blend session is a great way to restore after a crash. But, clients are more comfortable with an engineer that doesn*t have such issues.

Could it be a single EDL corruption that got Save As'd into "child" EDLs down the line? If so, that would be sort of a one-off--not worth worrying too much about, no?

[MMP]

Thanks for that. At least I now know that it*s probably not related to my system*s monitor or system settings.

Crashed confirmed over here. BTW, the Tempo Mode setting appears to have saved with the session; that's how it opened.