Jump to content
Morten Saether

[CLOSED] Cakewalk 2021.06 Early Access [Updated to build 41]

Recommended Posts

53 minutes ago, noynekker said:

Hmmm . . . when I saw "improved VST3 support" I hoped the bug regarding inserting Fabfilter Pro-Q3 VST3 had been addressed. (a reminder . . . insert FabFilter Pro-Q3 VST3 into the FX bin, on a new blank project - - -> instant Cakewalk crash) It's been a year and a half, is this on the radar ? I launched a ticket with FabFilter back when it first appeared, but they have not addressed it on their end ? Yes, the workaround is use VST2.

Been working fine here for 2 years. 

Make sure it's in the correct path folder and that your 3.5dotNet is updated. 

Share this post


Link to post
Share on other sites
10 minutes ago, Will_Kaydo said:

Been working fine here for 2 years. 

Make sure it's in the correct path folder and that your 3.5dotNet is updated. 

Interesting you have it working ! My VST3 efx seem to all be in c:\program files\common files\VST3 . . . my 3.5dotnet is up to date, latest Win 10 update patched.

Share this post


Link to post
Share on other sites
1 hour ago, Noel Borthwick said:

I'll look into this. It is an oversight.

Thank you again and your team! 🙂

Share this post


Link to post
Share on other sites
Posted (edited)
3 hours ago, noynekker said:

Interesting you have it working ! My VST3 efx seem to all be in c:\program files\common files\VST3 . . . my 3.5dotnet is up to date, latest Win 10 update patched.

Then you have a serious problem on your system. No one on this forum ever complained about them. Maybe you should contact their support team. 

Fabfilter never give problems. 

Try to remove the VST 2 DLL file if you have it installed. If you would like to keep it . . . get the JBridge Software to convert it to 64bit. 

Edited by Will_Kaydo
  • Like 1

Share this post


Link to post
Share on other sites
10 hours ago, noynekker said:

Hmmm . . . when I saw "improved VST3 support" I hoped the bug regarding inserting Fabfilter Pro-Q3 VST3 had been addressed. (a reminder . . . insert FabFilter Pro-Q3 VST3 into the FX bin, on a new blank project - - -> instant Cakewalk crash) It's been a year and a half, is this on the radar ? I launched a ticket with FabFilter back when it first appeared, but they have not addressed it on their end ? Yes, the workaround is use VST2.

Works fine here. Must be a local issue on your end

VST3-PROQ3---Working.gif

Share this post


Link to post
Share on other sites
9 hours ago, noynekker said:

Interesting you have it working ! My VST3 efx seem to all be in c:\program files\common files\VST3 . . . my 3.5dotnet is up to date, latest Win 10 update patched.

Works fine for me too. Never had problems with fabfilter plugins

  • Like 2

Share this post


Link to post
Share on other sites
11 hours ago, Noel Borthwick said:

I'll look into this. It is an oversight.

I believe there is a window of opportunity at this point to let the user choose whether the text will be centered, left or right.

  • Great Idea 1

Share this post


Link to post
Share on other sites
10 horas atrás, Johnny Tsao disse:

Obrigado de novo e sua equipe! 🙂

Acredito que há uma janela de oportunidade neste momento para permitir que o usuário escolha se o texto será centrado, esquerdo ou direito.

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/17/2021 at 12:54 AM, Morten Saether said:

 

 

Improved input/output port naming for hardware and software ports

In Cakewalk all ports are grouped into stereo pairs of channels. In order to make it easier to associate these pairs with the physical channels exposed by the hardware or virtual instrument, the port naming conventions have been improved.

  • Audio and soft synth input and output ports now include a channel number prefix before the port name.
    Additionally, port names now always show the actual names of the referenced channels. (previously only the first channel name would be shown). Since many instruments have different names for channels or even dynamic names, the channel index can be used to identify a specific instrument output more easily.
  • When using user defined device names (Use friendly names to represent audio drivers) you can now specify both the left and right channels in the stereo pair by using the pipe symbol “|” to delimit the channel names. For example, entering a friendly name of “Guitar|Voice” may show 1: Guitar, 2: Voice, 1+2: Guitar + Voice in the menus.
  • Port names have been shortened to skip the device vendor name for greater legibility in the Track view, Console view and Inspector. The tooltip for the name will show the full form of the name.
  • Port names are no longer compacted. With the smarter port naming, in most cases there should be no need to use friendly names to shorten the strings, unless you wish to use instrument names for the ports.
  • Edit Filter values and MIDI channels are no longer compacted, which makes it easier to read parameter names in most cases.
  • In the Console view Hardware Outs section, hardware out names now show channel indexes as well as channel names in ASIO mode.
  • Sends now show shortened port names and use port numbering when applicable.

image.png

 

For me this is a big mess. The old format is much more intelligible to me, as it identified each mono output and could use mono or stereo as input and according to the idea of use.

I think that changes at this level of usability should pay attention to maintaining the knowledge obtained from using the tool, bringing it as an option for use and not determining it to be the only way to use it.

In the previous version it was fully possible to identify the left, right and stereo channels of the instruments.

Did not like !

image.png.1dbc68ad7e30ffef7560182609c332c3.png

 

Edited by Milton Sica

Share this post


Link to post
Share on other sites

There is no loss of information in fact there is a lot more information than before. 

With virtual instruments Cakewalk groups all outputs into pairs. However the mono stereo listing was arbitrary because there is no guarantee that a plugin output is stereo or not. The numbers now clearly indiscrete which output is being used unlike before. Most other DAWs do the same.

For your purposes you can assume 1 means left 2 means right and 1+2 is stereo. What are you missing?

 

 

Share this post


Link to post
Share on other sites
Agora mesmo, Noel Borthwick disse:

Não há perda de informação de fato há muito mais informações do que antes.

Com instrumentos virtuais, cakewalk agrupa todas as saídas em pares. No entanto, a listagem mono estéreo foi arbitrária porque não há garantia de que uma saída de plugin seja estéreo ou não. Os números agora claramente indiscritos que a saída está sendo usada ao contrário de antes. A maioria dos outros DAWs fazem o mesmo.

Para seus propósitos, você pode assumir 1 significa esquerda 2 significa direita e 1+2 é estéreo. O que você está perdendo?

 

 

Desculpa. É só minha humilde opinião. Acho que mudanças desse tipo devem preservar o conhecimento desenvolvido pelo usuário, sendo parametrizável.

Algumas aplicações tratam isso como "legado".

Como tal, não se trata de perda, mas de adaptação do conhecimento.

Share this post


Link to post
Share on other sites
On 6/17/2021 at 5:54 AM, Morten Saether said:

Misc.

  • Track templates ignore phase settings
  • MIDI input ports not assigned correctly after saving as track template

 

Thanks for fixing this issue I reported

Many thanks for your work to make CbB better and better!

Share this post


Link to post
Share on other sites
1 hour ago, Noel Borthwick said:

There is no loss of information in fact there is a lot more information than before. 

With virtual instruments Cakewalk groups all outputs into pairs. However the mono stereo listing was arbitrary because there is no guarantee that a plugin output is stereo or not. The numbers now clearly indiscrete which output is being used unlike before. Most other DAWs do the same.

For your purposes you can assume 1 means left 2 means right and 1+2 is stereo. What are you missing?

 

 

This comes back to what I have said earlier. It makes it a little confusing at first, but getting used to it. I think for a long time we were used to the Old Names. 

In fact it's good to slowly move to the language other daws uses in their routing. We just need to get that separate Mono and Stereo track insert strips on both Audio and Instruments now. 😅

  • Like 1

Share this post


Link to post
Share on other sites
On 6/19/2021 at 7:26 PM, noynekker said:

Hmmm . . . when I saw "improved VST3 support" I hoped the bug regarding inserting Fabfilter Pro-Q3 VST3 had been addressed. (a reminder . . . insert FabFilter Pro-Q3 VST3 into the FX bin, on a new blank project - - -> instant Cakewalk crash) It's been a year and a half, is this on the radar ? I launched a ticket with FabFilter back when it first appeared, but they have not addressed it on their end ? Yes, the workaround is use VST2.

Improved VST support doesn't mean we can magically fix preexisting bugs in plugins :) We added some VST3 features to support some upcoming new VST3 plugins based on feedback from the vendor.

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites
10 minutes ago, Noel Borthwick said:

We added some VST3 features to support some upcoming new VST3 plugins based on feedback from the vendor.

Are we getting new plugins? 😀

Share this post


Link to post
Share on other sites
On 6/16/2021 at 10:54 PM, Morten Saether said:

Reorder multiple tracks simultaneously

You can reorder multiple tracks simultaneously by dragging in the Track pane. To do so, select the tracks that you want to reorder, then hold down the SHIFT key while you drag any selected track.

Excellent !

Share this post


Link to post
Share on other sites

image.png.c85ad28b53e7cfb99a40066361c00f59.png

Today I've used freehand tool. New features are great, I really appreciate as you know. But we still need bezier curves for better control in automation. I've just wanted to remind that.

  • Like 1

Share this post


Link to post
Share on other sites
On 6/16/2021 at 10:54 PM, Morten Saether said:

Replace synth on a single Instrument track

It seem that I am really at a loss on this update. I cannot get this replace synth to work. I create the instrument per track out .. Lets say I make 4 tracks all the tracks are sine player that can do 16 outs. I replace the 3rd track with this Replace synth on this track only I select SI strings to replace the 3rd track. The SI Strings instrument does not make any sound for the one that is replaced. I see the midi meter moving when I press a key or if I just hit play on midi that is already on the track it makes no sound at all. I check the midi settings and change that to SI Strings midi 1 still no sound from that track . I try to change the instrument back with this same Replace synth and still no sound out of the track this track no longer makes any sounds at all. I have tried with other synths like kontact.. sine player.. sampletank same issue  this track no longer plays anything I put on it. Not sure what I am doing wrong?

 

Share this post


Link to post
Share on other sites
Posted (edited)

Hi, Xel Ohh

Please try to replace Synth on the Ch.1 (1/2 Output) track, you should be able to hear the sound of SI-String.

1889112077_1.png.d2da3698fba29ecc484070df2c5af873.png

Personally guess that after replacing Ch.3 (5/6 Output) of the original SINE Player with SI-String, it may be because SI-String does not have Multiple Output, resulting in MIDI signal but no sound signal output.

Earlier I used the Multiple Output function of TTS-1, and only when the 1/2 Output track was replaced with SI-String, there would be sound.

Pure communication and sharing, there may be Incorrect , please forgive me!

Edited by Johnny Tsao

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×
×
  • Create New...