Waveform 11.2.0 Beta Available (UI Cleanup)

[omannpro]

I would love to be able to drop a midi chord progression into the Chord track and be able to save it as a chord preset and allow it to be followed by pattern generator. Also the flexibility to save more chord structures as presets(7ths and 9ths). Also time adjustment in the chord track.

[Michl71]

Hey Tracktion team,

look what happened to my Waves Plugins AU-Versions doesn't show any GUI, VST Versions with mirrored Fonts.

Waveform 11.2.0 Beta
Mac OS Catalina 10.15.7
iMac late 2013, i5 Proc

Greetings Michael

[ForrestH]

Under 11.2 Linux, project/edits don't allow setting a track input: new project/edits show "Audio" and "MIDI" on the track input popup (as opposed to showing the name of the MIDI interface, as on 11.1.25), but neither is selectable, and existing project/edits don't even have that, just "No Input".

Possibly relatedly, some of the existing edits in the existing project have lost their input settability even after reverting to 11.1.25, even though according to the dates in the "all items" browser they are unchanged; I infer the project file itself was garbled somehow...

[Kott]

Under 11.2 Linux, project/edits don't allow setting a track input: new project/edits show "Audio" and "MIDI" on the track input popup (as opposed to showing the name of the MIDI interface, as on 11.1.25), but neither is selectable, and existing project/edits don't even have that, just "No Input".

Could you show the screen of that and MIDI/Audio settings?
I can select inputs as usual.

[ForrestH]

11.1.25:

11.1.25.png

MD11.1.25.png

11.2.0:

11.2.0.png

MD11.2.png

[Kott]

Weird. Is it Jack?
I don't know what is "Network" MIDI.
But for me it works with my MIDI keys and even with software keys like vmpk.

[dRowAudio]

Under 11.2 Linux, project/edits don't allow setting a track input: new project/edits show "Audio" and "MIDI" on the track input popup (as opposed to showing the name of the MIDI interface, as on 11.1.25), but neither is selectable, and existing project/edits don't even have that, just "No Input".

Possibly relatedly, some of the existing edits in the existing project have lost their input settability even after reverting to 11.1.25, even though according to the dates in the "all items" browser they are unchanged; I infer the project file itself was garbled somehow...

You probably don't have the audio engine running. Have a look just under the CPU usage meter in the top right, is there a rectangular bar there?

Can you go to the new "Advanced" settings page and ensure "Run audio engine when stopped" is enabled, that will keep it running even when you're not playing and inputs should then appear in the menu.

[Cheve]

I like the changes.
One problem on Windows 10: CTRL+S don't save. It send midi signal to the selected track.

[ForrestH]

[NetworkIn is an ALSA input provided by aseqnet; the newer machine has no PCI slots so I get my input by way of my older machine via the network.]

Yes, the bar was missing. Apparently I was playing with the settings on the Advanced page and turned Run off on 11.2.0, but it was still on under 11.1.25, hence some confusion. Since it's gone from the Options button¹, maybe you should put it on the track popup just above Record Enable.

Incidentally, the Help button still shows "Visit the Trackion Help Website...".
[wanders off for a nice cup of t]
____
¹ Apparently a removal not tagged in FigBug's change log.
But I do note
"- UI: Removed option 'Only Show Enabled Devices'"

[boomt]

I like the changes.
One problem on Windows 10: CTRL+S don't save. It send midi signal to the selected track.

That could be cause typing keyboard to midi has taken over. I've found a few times where I could not turn off the typing keyboard to midi.

[vitocorleone123]

I applaud the focus on fixing issues rather than versioning. I'm a fan of doing a major release, then doing a point release, then a major release, etc.

UI updates and fixes (I'm a UX Designer, myself), and, more importantly, stability. I see in a few forums the expression of liking Tracktion/Waveform, but people having moved onto other DAWs because it wasn't stable enough for professional use where people depend on their DAW to make a living.

Continuous major releases are a trap for small tech companies (even bigger ones), because you're trying to push new stuff to market new stuff to get new customers to keep the lights on. At some point, things start to break and more people are leaving and/or unhappy and no longer recommending things to people they know or meet and then you have to make the choice of either continuing to "juice" the market and discard your old users, or stop and focus on fixing things. It's tough out there.

Thanks, TSC, for enacting some tough love on our favorite DAW.

[boomt]

Found a crash if you remove the last section via the actions panel on a step clip it causes a crash. It seems to happen even if a step clip has 2 variations but only one is selected and you try to delete that section.

[boomt]

Found another bug. Removed

EDIT: It's not a bug I had left on preview in the browser tricking me into wondering where the sound that I was hearing came from even though it wasn't coming from a track

[jabe]

While Devs are tidying things up, here's a request to consider.

The latest beta always installs over the top of the current latest live version.

Instead of installing the beta into a Waveform11 folder, could you change it to LatestBeta instead so that we can have the latest beta but also keep the latest live version as well, please? Thank you.

[chagzuki]

This is the first beta that I might try; I'm also interested primarily in fixes and interface improvements. The one feature that I really want is automation clips so I can move automation around easily... besides that there isn't anything that's going to radically change or improve my workflow.