Waveform 11.1.25 Public Beta (Experimental engine fixes)

[dRowAudio]

Hi everyone, just a quick note that Waveform 11.1.25 is now available as public beta which addresses some of the issues flagged since 11.1.21.

Code: Select all

11.1.25:
- Playback:         Fixed a regression in the default audio engine which would cause the playhead to remain stationary

11.1.24:
- Engine:           [Experimental] Fixed a problem if "Run audio engine when stopped" is disabled where the playhead could flicker when starting playback

11.1.23:
- MIDI:             Fixed all MIDI notes snapping to time 0

11.1.22:
- Engine:           [Experimental] Fixed a problem with rendering and freezing where latency would be added as silence to the start of renders
- Engine:           [Experimental] Ensured level meters compensate for plugin latency so they stay in sync
- Engine:           [Experimental] Ensured the transport cursor compensates for plugins that introduce latency so it is in sync with what is being heard
- Windows:          Fixed a problem not being able to change sample rates for the "Windows Audio (Exclusive Mode)" device type

[imstre]

Great job! Thanks!

[mikoatkvr]

The bug fixes are coming in fast. Can any of the Devs look into why some Linux plugins no longer show their GUI, especially LSP which worked flawlessly in older versions. I understand this might be a JUCE issue, but it would be nice if this was sorted soon thanks guys.

[Kott]

The bug fixes are coming in fast. Can any of the Devs look into why some Linux plugins no longer show their GUI, especially LSP which worked flawlessly in older versions. I understand this might be a JUCE issue, but it would be nice if this was sorted soon thanks guys.

It's JUCE 6 bug.

[mikoatkvr]

Thanks Kott, hopefully a fix comes along soon .

[vitocorleone123]

Same Insert issue: Experimental engine enabled = no audio with an Insert routing out to hardware and back in. Disable the Experimental engine and it works normally.

[Paree]

Replacing any U-he vst3 plugin with another plugin crashes the DAW (Without plugin sandboxing on) in Linux. vst2 versions do not load UI like @mikoatkvr mentioned

[vitocorleone123]

Liquidsonics Reverberate 3 suddenly started crashing the whole DAW despite sandboxing. I literally cannot open my project anymore, despite having been using the plugin successfully all week without a problem. Good thing it only had some promising ideas in it rather than being an actual track, or I'd be rather upset instead of merely annoyed.

[Paree]

Liquidsonics Reverberate 3 suddenly started crashing the whole DAW despite sandboxing. I literally cannot open my project anymore, despite having been using the plugin successfully all week without a problem. Good thing it only had some promising ideas in it rather than being an actual track, or I'd be rather upset instead of merely annoyed.

I'd suggest you to revert back to stable version and check if everything works properly. Since this is a beta version, there is bound to be some bugs that will be fixed.
So far for me, 11.1.25 solved vst3 related problem i was facing in 11.1.10 in linux however, a JUCE 6 related bug makes most of my primarily used plugin's GUI disappear. So i reverted back to the stable version and it was solved. I'm pretty much sure that it'll be solved in the net stable release.

[vitocorleone123]

Liquidsonics Reverberate 3 suddenly started crashing the whole DAW despite sandboxing. I literally cannot open my project anymore, despite having been using the plugin successfully all week without a problem. Good thing it only had some promising ideas in it rather than being an actual track, or I'd be rather upset instead of merely annoyed.

I'd suggest you to revert back to stable version and check if everything works properly. Since this is a beta version, there is bound to be some bugs that will be fixed.
So far for me, 11.1.25 solved vst3 related problem i was facing in 11.1.10 in linux however, a JUCE 6 related bug makes most of my primarily used plugin's GUI disappear. So i reverted back to the stable version and it was solved. I'm pretty much sure that it'll be solved in the net stable release.

I did that (going back to released version) - no change. I'll have to wait until one or both are updated again in order to recover those ideas. Hopefully.

[Peter Widdicombe]

Sort of related to this thread...

1. I tend to work on a laptop for recording (mobile), but use my second license on a desktop, and always upgrade the desktop prior to the laptop - and verify functionality, try any new VST's, put the beta releases on...

2. Occasionally there are settings that get changed - either through new functionality, a test, etc. Occasionally when things "stop working" and you're tearing your hair out, installing the old release may not work. There are one or two key settings files (that tend to be common between releases), so if the setting got changed, going back doesn't work. Those files can be renamed (i.e. to waveform.settings_old); but any customization will be lost - but then you're starting fresh, and the functionality can be restored.
(I have assisted others in the past, and this has worked and the better alternative, when an uninstall doesn't work)
It appears to have moved? I'd guess under windows it is
c:\users\<user>\appdata\roaming\tracktion\waveform\waveform.settings.
Rename slightly while waveform is NOT loaded, and it will generate a new one with all new defaults. If it doesn't resolve the issue, then EXIT waveform, delete that new one, and rename the temporary one back.

3. (question for Dave ?) When a new release is installed, can there be an automatic copy of the settings file made, possibly with a version or timestamp in the file name, so that reverting to a prior release doesn't leave this kind of situation? I know this leaves a little bit of "junk" lying around in the users/home or users/roaming directories, but it will be small and assist in this kind of situation.

[mikoatkvr]

The Juce vst bug seems to have a fix upstream in tracktion_engine , looking forward to see this one finally solved

[spoontechnique]

Two issues I've noticed with the past few versions (both on and off the experimental engine).

1. When step clips are expanded to show the steps, there is a noticeable visual lag playing the edit.

2. When I zoom in to full resolution (or near full), Waveform crashes.

[spoontechnique]

Using the engine, I can't seem to render tracks within a submix.

[spoontechnique]

Also of note: Playing a sample in the browser plays the sample partway through. So for example, drum samples play after the initial transient, which makes it hard to determine what it sounds like.