Waveform 14 Public Beta

[pough]

is CLAP support in the roadmap? is it a JUCE thing?

CLAP is expected to be added to the next major version of JUCE. I'm guessing it will be added to Waveform some time after that.

[Kodokushi]

What about Controllers?

Any new or reworked controller scripts?

[aMUSEd]

At least the bug where it couldn't record MIDI notes from my NI Kontrol MkIII keyboard is fixed and DAW integration is working again

[aMUSEd]

I like that it supports a proper menu bar on Mac now

[aMUSEd]

What about Controllers?

Any new or reworked controller scripts?

Looks like the controller script for NI Kontrol keyboards is still the earlier version and not supporting the firmware 2 integration which aded more sophisticated device support - that's a pity (although at least it's no longer broken)

[aMUSEd]

'No additional subscriptions, BYOK pay as you go with the model of your choice (OpenAI and Anthropic support initially)'

I don't understand this, what does BYOK mean? It sounds like they will be charging for use of the AI?

[aMUSEd]

Oh well the assistant doesn't seem to work anyway - it just says "Key missing" whatever that means

Would be good if the tab could be hidden

[sceyefeye]

Is the output channel non a new thing or a pro thing?

The what?

My bad, typo. None as output channel. In 13.5 I have a track only to trigger a side chain (yeah I am sure there are other options). I do not want the audio to to Master Output. So I've had to make a dummy track to receive the audio and mute that instead.

As I have not used Waveform 13 Pro, I am just wondering if this is a new option in 14 or a Pro thing

[talby]

(...)I will never be interested in AI features. Let me hide it and disable it. Assistant takes up wasted space in the panel if you don't use it. Let me disable it all. For me, this makes the update an immediate non-starter.
(...)

If you do not like AI, just do not fill in your access credentials to an AI provider. It cannot be easier to stay off from AI. How should Tracktion simplify this even more? You, as the user, stay in full control of this!

There will be here and there a function listed, by which you could ask AI to work for you.
But that is even less impacting you than any other function being present in the software which occupies its space in the User Interface although you might not be interested to click on it, because even if you would click it by accident it will not connect you to any AI, as long as you didn't explicitly configure this. Other functions in WF will do something if you by accident click on them!
Taking this into account, I find your reaction a little bit overshooting. Users who want AI can configure it to become accessible and click on it. And these users who have configured an AI access can still use the checkbox "Enable AI Assistant" to ON or OFF. So, they have the comfort not having to remove their AI access configuration when not interested to use it, but can simply deactivate it until they want to use it again. Other users, like you, are absolutely not affected, besides seeing that a function would be available, but is not even activated.

Waveform 14 now provides interfacing to AI providers, but does not obligate you or make you dependent of making any use of this interface.

[starflakeprj]

'No additional subscriptions, BYOK pay as you go with the model of your choice (OpenAI and Anthropic support initially)'

I don't understand this, what does BYOK mean? It sounds like they will be charging for use of the AI?

It probably means the API Key is missing. You need to have your own API Key to use the AI in Waveform, as far as I understand it. Might be there is a subscription model coming, or an subscription add-on, where you pay Tracktion each month for a number of requets.1

Edit: I answered on the wrong post, but to the right poster

[aMUSEd]

I’ve never heard of an ‘API Key‘ - what is that?

[starflakeprj]

I’ve never heard of an ‘API Key‘ - what is that?

O.K. I'm, slow, you got me

[talby]

If I understood correctly, then:

Tracktion Waveform provides you with interfacing to AI, and pre-selected some providers which got a special permission to access non-public documentation and code from Tracktion in order to become able to generate better answers. AI without this permission can only base its knowledge on publicly available information, like the answers found in this forum.
The Interface of Waveform then also cares, for instance in the case that you requested from the AI to generate you some MIDI pattern which fits to your own already edited music, to also give the permitted AI access to your Edit, so that the AI can see what you have done already, and then offering you the possibility to include the response of the AI right away into your project or not.
Using this Waveform internal interface will therefore allow some AI to generate a potentially better answer than a query to the same AI from outside of Waveform.

However, using the service of AI - and having to cover the costs which the AI provider charges for using its AI, is up to the user!
The API Key is your credentials by which you log in to your account, which you purchased from one of the AI providers of interest, one of those which Tracktion announces to be compatible with the Waveform interface usage and having got that special permission to make usage of additional information provided by Tracktion to them. There are cheap, fast and not so good answering AI models, which you could interface to, or expensive, slow and better quality models. You can chose between the various AI models from various pre-selected providers, according to your needs and financial efforts. Tracktion leaves such subscription completely in your hands, which is possible, because your API Key from your AI account with an AI provider manages your business directly with the AI provider.

Still, the quality of answers of the AI to a large extend also depends on you to query the AI by advantageous prompts.

All together, the decision to use AI and the quality and costs of the answers of AI is in the hands of the user. What Tracktion Waveform offers you is, that using the interface of Waveform for accessing AI has an advantage in terms of quality and comfort over using such AI disconnected from Waveform.

[pough]

My bad, typo. None as output channel. In 13.5 I have a track only to trigger a side chain (yeah I am sure there are other options). I do not want the audio to to Master Output. So I've had to make a dummy track to receive the audio and mute that instead.

As I have not used Waveform 13 Pro, I am just wondering if this is a new option in 14 or a Pro thing

That's new, and it's a cool feature.

Now I need to check sidechain to a submix. Or from a submix. One of those didn't work before...

You still can't use a submix as a source for a sidechain. But you can route a submix to a regular track and then use that track as a source.

There is something strange about level meters and... submixes? Possibly because the level meters are more complicated and they just give up when it's too complicated, like when it's trying to show multiple stereo meters in too-small a space. Although the level meters now show a sidechain signal if you're using one. That's a nice touch. If you set up two sidechain sources in one track it just combines both signals.

EDIT: It looks like only the built-in Drum Sampler and Multi Sampler have this issue. I think it's because their outputs by default are just Discrete #32. Setting the output to stereo results in functional level meters.

[pough]

Assistant takes up wasted space in the panel if you don't use it.

What are you seeing that I'm not? It's one tab of seven in the Browser Panel. I didn't even notice it until I read your post and then I had to search for it.