W11 Beta's Up!

[mikoatkvr]

Can anyone post how to use Chord Companion?
I tried putting it in front of a VST instrument (AAS Lounge Lizard) and got nothing. I put MIDI Monitor ahead of it and can see notes coming in. I put MIDI Monitor after it and nothing is coming out. I tried clicking on the Chord Companion pads and the its virtual keyboard.

The pads and the virtual keyboard in Chord Companion are offset by 1 octave. C2 on the virtual keyboard triggers the C3 pad. Is there a setting for this?
Thanks for any help.

Pick your key and progression at the top of the GUI then the chords in that scale will be highlighted with a blue circle.... now drag this blue circle onto the desired pad. The corresponding midi key of the pad will now trigger the chord.

[Steve Bolivar]

Thanks, now it's working.

[spoontechnique]

With the chord companion and new midi tools, it brings up something that still seems like an oversight: no custom scales. The church modes are great but it's restrictive for anyone who makes world music, experimental, metal, techno, blues, jazz, etc. Not a huge deal but it would be a huge boon to many of us, I think.

Noticed some subtle improvements to the midi editor, those are nice.

[madrang]

Now JUCE allows to name the audio client. https://github.com/WeAreROLI/JUCE/issues/331
This should be added to Waveform.

Code: Select all

//Set JUCE Audio Client Name
#define JucePlugin_Name "Waveform"

Also tried to load RetroMod Fat.

Code: Select all

Waveform 64-bit version: 11.0.15 (Built: 11 February 2020)
Log started: 20 Feb 2020 1:43:52pm

20 Feb 2020 13:47:17  Attempting to load VST: /home/madrang/.vst/RetroMod/RetroMod Fat.so
20 Feb 2020 13:47:17  Creating VST instance: RetroMod Fat
20 Feb 2020 13:47:18  Crash Location: tracktion_ExternalPlugin.cpp:operator():720
20 Feb 2020 13:47:18  Maintenance took: 1 ms
20 Feb 2020 13:47:18  Crashed
20 Feb 2020 13:47:18  

20 Feb 2020 13:47:18  Thread 0:
20 Feb 2020 13:47:18    ** Plugin crashed: RetroMod Fat (VST)
20 Feb 2020 13:47:18    0: tracktion_ExternalPlugin.cpp:operator():720
20 Feb 2020 13:47:18    1: tracktion_AsyncFunctionUtils.h:handleAsyncUpdate:182
20 Feb 2020 13:47:18    ** Plugin crashed: RetroMod Fat (VST)
20 Feb 2020 13:47:18    2: tracktion_ExternalPlugin.cpp:doFullInitialisation:715
20 Feb 2020 13:47:18    ** Plugin crashed: 
20 Feb 2020 13:47:18    3: tracktion_ExternalPlugin.cpp:initialiseFully:481
20 Feb 2020 13:47:18    4: tracktion_ExternalPlugin.cpp:ExternalPlugin:436
20 Feb 2020 13:47:18    5: tracktion_AsyncFunctionUtils.h:handleAsyncUpdate:182
20 Feb 2020 13:47:18  Thread 1:
20 Feb 2020 13:47:18    0: tracktion_Track.cpp:initialise:59
20 Feb 2020 13:47:18    1: tracktion_AudioTrack.cpp:initialise:333
20 Feb 2020 13:47:18    2: tracktion_Edit.cpp:createTrack:1225
20 Feb 2020 13:47:18    3: tracktion_Edit.cpp:initialise:662
20 Feb 2020 13:47:18    4: tracktion_Edit.cpp:Edit:488

[dRowAudio]

Ok, I've added the client name now.
Will look in to the RetroMods next week hopefully.

[GoRhino]

Thanks to explanation by mikoatkvr and a bit more time, I have got the rudiments of Chord Companion. Indeed very impressive, well done.

However, shouldn't the "default" bottom left pad be set to C1(36) and increase from there UP rather than down from top left as currently? Also, I note pad triggers can be changed by "MIDI Learn" - but that is quite a bit of faffing around, why not just type the note you want?

Ability to add custom chords and voicings would be great too (not just inversions as now).

[FigBug]

With the chord companion and new midi tools, it brings up something that still seems like an oversight: no custom scales. The church modes are great but it's restrictive for anyone who makes world music, experimental, metal, techno, blues, jazz, etc. Not a huge deal but it would be a huge boon to many of us, I think.

When I initially did the scale stuff I assumed all scales had 7 notes. Painted myself into a bit of a corner there. I will look into fixing this in future. Let me know any particular scale you would like me to look at, no promise when I'll get it done.

[FigBug]

However, shouldn't the "default" bottom left pad be set to C1(36) and increase from there UP rather than down from top left as currently? Also, I note pad triggers can be changed by "MIDI Learn" - but that is quite a bit of faffing around, why not just type the note you want?

Ability to add custom chords and voicings would be great too (not just inversions as now).

The defaults were set on a pad controller I had.

I've added the ability to save presets for the pads in Chord Companion, and set a default. So you only need to do the midi learn once. (This also applied to sampler, drum sampler).

You can add custom chords in the waveform settings, then they'll appear in chord companion.

[GoRhino]

Fantastic response

[spoontechnique]

Most people who use the scales feature are probably fine with diatonic modes, harmonic minor, minor blues, and the basic pentatonics. People who want more exotic or obscure scales are probably already competent musicians/composers who don't care about the visual representation. It's probably only people like me who are in the middle who care. I don't have a specific scale I need added, I'd want to be able to define custom scales. I appreciate that it's considered, it's not a big issue at all.

Nitpick: I was taught that melodic minor is different descending vs. ascending. The ascending melodic minor is a major with a b3, and the descending version is natural minor. Having it the way it is (ascending version) is fine with me but I'm sure some classical composer would get their knickers twisted seeing the implementation.

[vitocorleone123]

If I turn plugin sandboxing OFF in the beta, then my plugins behave normally, in terms of remembering where they were on the screen last time they were edited... or even being able to be edited at all (perhaps those that I can't edit are actually just appearing somewhere off the screen entirely?). Of course, sandbox = off = more unstable and more crashing I suspect, but I need to use it more with it off before making that judgement. However, given Waveform 10 and how often it crashes due to plugins, I'm a little skeptical.

I'd love a way to enable sandboxing for only selected plugins (e.g., a right-click action). Adds complexity to the code and UI for sure, but that'd let users isolate things. When Waveform crashes it could ask if the plugins responsible should be put in the sandbox.

[jabe]

Most people who use the scales feature are probably fine with diatonic modes, harmonic minor, minor blues, and the basic pentatonics. People who want more exotic or obscure scales are probably already competent musicians/composers who don't care about the visual representation. It's probably only people like me who are in the middle who care. I don't have a specific scale I need added, I'd want to be able to define custom scales. I appreciate that it's considered, it's not a big issue at all.

Nitpick: I was taught that melodic minor is different descending vs. ascending. The ascending melodic minor is a major with a b3, and the descending version is natural minor. Having it the way it is (ascending version) is fine with me but I'm sure some classical composer would get their knickers twisted seeing the implementation.

The Studio version of Melodyne lists dozens of exotic scales. I've no idea whether they are all compatible with MIDI. I suspect not in all cases, especially where quarter tones are used.

[spoontechnique]

I think anyone who composes microtonal music probably has their own workflow for doing so. I don't think Waveform can really help out there. Not that microtonal support wouldn't be neat.

[dRowAudio]

If I turn plugin sandboxing OFF in the beta, then my plugins behave normally, in terms of remembering where they were on the screen last time they were edited... or even being able to be edited at all (perhaps those that I can't edit are actually just appearing somewhere off the screen entirely?). Of course, sandbox = off = more unstable and more crashing I suspect, but I need to use it more with it off before making that judgement. However, given Waveform 10 and how often it crashes due to plugins, I'm a little skeptical.

I've spent a long time looking in to this but it should be fixed in the next release.

I'd love a way to enable sandboxing for only selected plugins (e.g., a right-click action). Adds complexity to the code and UI for sure, but that'd let users isolate things. When Waveform crashes it could ask if the plugins responsible should be put in the sandbox.

You can do this from the Plugins setting page. You'll see a new column called "Sandbox" where you can selectively enable/disable individual plugins to run in the sandbox.

[Kott]

You can do this from the Plugins setting page. You'll see a new column called "Sandbox" where you can selectively enable/disable individual plugins to run in the sandbox.

By default all plugins are enabled. If I want just couple of plugins to be checked? I've started to clicking on every but tired on first dozens or two.
BTW, did you test sandbox in Linux? There no GUI (Ubuntu 18 official supported (kind of))