Waveform 13.5 Ongoing Bugs

[pough]

I can try to help you make a set of test samples with different metadata contents, if you want.

I appreciate the information and offer. I might just get the latest SoundForge while it's on sale. I'm going to see if the basic version does what I want.

I already have a set of test files. As far as I know, they have the features that I want to test. However, nothing I own is very good at dealing with ACID files, so I don't know for sure.

https://drive.google.com/file/d/1P5-KKh ... drive_link
Four audio files in a ZIP archive.

This bug bumps up against another bug in Waveform 13: it doesn't actually include beats, tempo, and time signature any more. Version 12 exported with ACID info whether you wanted it to or not. Version 13 gives you the option, but it fails. That will be my next thing to report.

[Maarid]

I appreciate the information and offer. I might just get the latest SoundForge while it's on sale. I'm going to see if the basic version does what I want.

use the trial version, I went to the magic website for it and found that I have a library of programs on my account, and fotodelux and acid itself are of three types.

https://drive.google.com/file/d/1P5-KKh ... drive_link
Four audio files in a ZIP archive.

You didn't allow me to view these files.

[pough]

You didn't allow me to view these files.

Whoops! Sorry. I just changed it so that anyone with the link can access the ZIP file. Probably.

[Maarid]

Probably.

I tested and tested all four clips.
What I realized is that weaveform reproduces acid metadata fairly accurately, with the difference that it uses the heaviest and most expensive method, it immediately uses ACID Beatmapped mode, which, by the way, answers the question why large files in large numbers with tempo control simply destroys the processor, instead of the less expensive loop mode, which divides audio. the file is just a fraction of the tempo, but that's it.
I also tested the files in acid itself as ready-made files, and they fully correspond to their metadata, are used, and behave perfectly correctly.
I think the error lies in the engine itself attaching effects to a specific clip, there are a lot of glitches, for example, the effect of the start / stop of the record is applied only to the real beginning of the clip, if you select some small piece of the clip and turn on the effect, but you will not see the effect faders, because they will only be at the real beginning or the end of the clip, etc. I think it's one of the abandoned parts of the program at the moment.

https://disk.yandex.ru/d/U65xT6di7Jeuew
here are some files from the original sample library that comes with the acid pro program, they are in loop mode, try to test them.

[edrickblade]

I am putting this here just so that I can keep track of the bugs I have encountered. I often forget about the details. I have also made a project for this with edits that have instances of the bugs. This way I can quickly check to see if they've been fixed. If anyone wants to confirm that the bugs exist on their system, that will probably help to narrow things down. I am running Windows 10 and at this time have Waveform Pro 13.5.19 installed.

Clip Effects

There are two bugs in Clip Effects that I have encountered. In running tests I noticed that they actually seem to be mutually exclusive.

One is a time shift when applying a plugin clip effect to a stereo audio clip. To easily reproduce:

1. To a stereo audio clip add Clip Effect -> Plugin -> Volume and Pan
The time shift happens for any plugin that I have tested. It also happens for two of the basic clip effects: Volume and Mono.

WF13 Clip Effects Bug A.png

The second bug is that mono audio clips become stereo with the audio only in the left channel when you apply a clip effect to it. To easily reproduce:

1. To a mono audio clip add Clip Effect -> Volume
This happens for any of the basic clip effects that I have tried, as well as for plugin clip effects.

WF13 Clip Effects Bug B.png

I have submitted a ticket (73492) for the first one. I didn't notice that the time shift for stereo and stereo problem for mono were mutually exclusive until after I submitted it. So if the devs run their own test on a mono audio file I guess they won't see the time shift bug. That goes to show how important it is to include as many details as possible when describing a problem.

Just now the Tracktion Team released Waveform 13.5.21, they fixed the clip effects time shifting bug, but the clip effects make it left side only is still present, also some plugins like Sfizz, TX16wX Sampler and Sforzando presents a white background gui.

[pough]

Yes, the time shift bug is definitely fixed as of the latest update (13.5.21) and the mono bug is still an issue. I have let TSC know through their support ticket system.

[jurij.es.a.szakkor]

Audio Clips with automation do not work properly in the Clip Launcher:

• Add an audio file to Clip Launcher slot
• Add automation to the clip, such as Volume or Pan automation
• Copy a clip to the next slot (shift will copy the automation as well)
• Set Next - Previous or Round Robin playback mode for clips
• Start the Scene or start any clip to play

The first clip usually plays fine, but the next or later part of the sequence doesn't, sometimes it doesn't even play the audio itself.

It appears as if the automation curve points/values are corrupted, shifted, or lost during playback.

Before I open a ticket, I would appreciate if someone could confirm the issue.

WF Pro 13.5.21 - Windows 10 Pro

[mikoatkvr]

@jurij.es.a.szakkor Running Waveform 13.5.21 on Linux on a simple test I am not experiencing your bug, although sometimes these bugs will only rear their ugly head as a project gets more complex.

I will keep a look out for this and report back with any findings .

[mikoatkvr]

ahhh there is a bug indeed where the automation stops working for a certain clip. I will dig a bit deeper and report it to the developers. You might as well open a ticket too as the more feedback they get the better.

[jurij.es.a.szakkor]

there is a bug indeed where the automation stops working for a certain clip ... open a ticket too as the more feedback they get the better.

I opened a ticket with additional findings (73897):

• When the clip is playing properly, the playhead is visible and the position is moving, the accumulated value of the absolute, relative and multiplicative automation envelopes and the current value are displayed in the background in the clip editor (mixer view)
• When the clip fails to play, the playhead is usually not visible, the accumulated automation envelope rarely display anything, and the current automation value is not visible at all

I see other errors related to this issue. I will continue testing and report back.

[jurij.es.a.szakkor]

wf-pro-135-clip-launcher-automation-issue.png

Even if I manage to create a simple Clip Launcher project with automation that launches and plays fine, after saving, closing, and reopening Edit, the automation no longer works.

The WF 13.5 Clip Automation video says that absolute clip curves take precedence over track curves, but this is often not the case. If I add track automation and then launch a Clip with automation, it doesn't take over, but continues to play the track automation curve.

If I return to the arranger track, where Launcher Clips shouldn't be a problem, the automation used in Launcher Clips often takes over the track automation for exactly the duration of the Launcher Clip.

Perhaps all of this contributes to the Clip Launcher automation problem as well.

[jurij.es.a.szakkor]

There are several overlapping problems with Clip automation in Clip Launcher, I have identified the following and can reproduce them 100%:

• After a Save/Reload operation, the (Audio, MIDI and Step) Clip automation no longer works

• On a Launcher track that contains at least one other Clip with automation, the audio from the first Clip will be heard with the automation curve from the second Clip when first launched. After first launch, on successive Clip playback cycles (2-3-4, etc.), the automation appears to be working fine (until you Save/Open the Edit, then the Clip's automation no longer works)

WF Pro 13.5.21 - Windows 10 Pro

[jurij.es.a.szakkor]

This problem seems to also affect the Arranger Track, I can reproduce the following 100%:

• On an Arranger track that contains a Clip with automation in Clip Launcher, the arranger Clip's audio is heard with the Launcher's Clip automation when playback starts from the beginning (Bar 1.1.0000). Once the Cursor crosses the length of the Launcher Clip, the automation appears to work properly (until the Cursor jumps back to Bar1, when the Launcher Clip's automation starts again).

WF Pro 13.5.21 - Windows 10 Pro

[talby]

You may want to report this to Tracktion, so that they become aware of it. They are usually not monitoring our posts here on this user-to-user forum. Ask on their support page the chat bot (bottom left) for the support request form.

[jurij.es.a.szakkor]

You may want to report this to Tracktion, so that they become aware of it.

Of course, I did and sent updates on new findings.

I'm cross posting here because I feel like being a WF user is one of the most frustrating/challenging things in my life.