Waveform 13.5 Ongoing Bugs

[pough]

So, maybe the solution is to deselect "Autotempo"? or I'm wrong?

It's not selected in the first place, so I don't think that's the solution. For the record, the audio files I tested were rendered from within the same Edit so they don't have Auto-Tempo toggled on. If I drag those same audio files into the Edit from the Browser, Auto-Tempo is toggled on.

[mikoatkvr]

@pough have you unchecked all the auto tempo related setiings under >Settings --> General --> Editing section

[pough]

Yes, here are my settings:

[edrickblade]

So, maybe the solution is to deselect "Autotempo"? or I'm wrong?

It's not selected in the first place, so I don't think that's the solution. For the record, the audio files I tested were rendered from within the same Edit so they don't have Auto-Tempo toggled on. If I drag those same audio files into the Edit from the Browser, Auto-Tempo is toggled on.

Thanks, So what could be a temporary solution to avoid the clip effects sync problem?

[pough]

Thanks, So what could be a temporary solution to avoid the clip effects sync problem?

There's none that I'm aware of, apart from using Waveform 12. I think I went back to the oldest version of WF13 I have kicking around (13.3.6) and it already had this issue.

[dysjoint]

Waveform 13 (all versions) bug. Click on any of the draggable icons in an audio clip header (squares or triangles) and drag outside the arranger panel boundary. Waveform freezes and I get an apparent memory leak? which continues until I force quit. Not present in 12.

[talby]

This is really strange. I did not and do not see something like this, neither on Debian 12, Debian 13, Ubuntu Studio 24.04, Ubuntu Studio 25.10, nor on Windows 11 (always up-to-date).
There has been a lot of trouble with the arrival of 13.5.13beta, which was only solved by 13.5.18beta, which is now out as an official release as 13.5.19 for replacing the former official release 13.5.8, and there is a severe bug still present, audio content in a clip becoming out of sync when a clip FX is used, as reported above.

But what you describe does not appear to me to be the general experience which other users have.
For curiosity, it won't solve your issue, which OS and version of it are you using, and on which hardware? The first which comes to my mind, which could cause such issue, would be the graphics card and driver. Do you know which chip and driver you are using? What maybe could solve your issues is to confirm that you have in Waveform configured SETTINGS - ADVANCED - PERFORMANCE - Gui Rendering Mode = "Software Renderer". The latter is possible to configure like this for working around issues like the one you are reporting.

[edrickblade]

Thanks, So what could be a temporary solution to avoid the clip effects sync problem?

There's none that I'm aware of, apart from using Waveform 12. I think I went back to the oldest version of WF13 I have kicking around (13.3.6) and it already had this issue.

How can I install WF12 in Ubuntu Studio 24.04 ?, I've tried but it shows this message "waveform12 : Depends: libjavascriptcoregtk-4.0-18 but it is not installable".

[dysjoint]

Quick demo of the bug. Using 'software renderer' doesn't make any difference. Windows 11 always updated, i9 12900k, Nvidia 3060 ti, always latest drivers. Bug is consistent since W13. Doesn't occur in 12.

[pough]

How can I install WF12 in Ubuntu Studio 24.04 ?, I've tried but it shows this message "waveform12 : Depends: libjavascriptcoregtk-4.0-18 but it is not installable".

I haven't used Linux in about 25 years and back then I really only used it to run xtartan. Does that still run? Anyways, I can't give you any Linux help but maybe @mikoatkvr can.

[edrickblade]

I figured out on how to install Waveform 12.5.21, just downloaded the file libjavascriptcoregtk-4.0-18_2.43.3-1_amd64.deb from here extracted the .deb file, extracted the data.tar.zst archive and manually copied the two files from the data/usr/lib/x86_64-linux-gnu to my system's /usr/lib/x86_64-linux-gnu with administrative privileges,

Open the folder where you have the Waveform12 .deb file with Terminal and type

$ ar xv waveform12_12.5.21_amd64.deb
$ sudo tar xvf data.tar.gz -C /

and not sudo apt install because the system will avoid it because of the dependency problem. You can update system and it won't update that file because it was copied manually and isn't registered in apt.

[mikoatkvr]

Waveform 13 (all versions) bug. Click on any of the draggable icons in an audio clip header (squares or triangles) and drag outside the arranger panel boundary. Waveform freezes and I get an apparent memory leak? which continues until I force quit. Not present in 12.

I can reproduce this on Ubuntu 24.04 There is indeed some kind of memory remap going on as is confirmed by running Waveform in strace. I'll report this to the developers

[mikoatkvr]

The Clip effect timing offset has been fixed by the developers, so most likely will be in the next update guys

[talby]

Quick demo of the bug. Using 'software renderer' doesn't make any difference. Windows 11 always updated, i9 12900k, Nvidia 3060 ti, always latest drivers. Bug is consistent since W13. Doesn't occur in 12.

Undoubtedly a severe bug. Report it to Tracktion, of course. I would repeat the video but having no plugin (besides the WF volume/pan plugin and the WF meter plugin) on that track. Best would be to also not have any other track in the Edit. Then the forth and back in emails about this for sure upcoming points is right away avoided.

[Maarid]

I should probably use more files from other places. If there's one thing I'm sure of it's that you can get tripped up on things you never considered.

And I've never found any software that gives me the tools I wish I had when it comes to ACIDized WAV files.

I remembered that I had the key to the old version of sound forge lying around for a long time, the program itself allows you to directly manipulate metadata, but I also couldn't immediately find how.

SoundForge.png

I can try to help you make a set of test samples with different metadata contents, if you want.
As far as I understand, the absence of the acid block in the wave file is interpreted as a oneshot.