Jump to content

Recommended Posts

Since the last update the marker line in the piano roll view stays in the location where it has been upon exiting the piano roll section with the mouse, even after moving out the cursor to entirely different UI elements.

It's only fading out if I move the cursor out of the piano roll section to the right or through the bottom. If I do it to the through the top (which is the most likely scenario), then the marker line will be drawn indefinitely or until I move the mouse into the piano roll section again.

Cakewalk-UI.thumb.png.1e7ab3edb6c650c7b070816aa510a1d7.png

Share this post


Link to post
Share on other sites

The update was the fastest, smoothest install experience yet. It was my first in-app install and less than 2 minutes to update and get working. the CA-2 in the Pro modules is perfect. Very nice work folks.

Share this post


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

The difference is seen in text rendering when you are running with display scaling set to something higher than 100% in Windows. Take a screenshot before and after the change and you will see the text rendered better if you zoom in.
Fonts are rendered much crisper. But with some plugin's not optimized you may see some perf issues. 

Interesting. I totally missed this in the EA release notes, but now I've set it to 1 to see what effect it has.

I run my monitor at 3840 x 2160 and Scale 125% and I definitely can tell the difference, to the greatest degree in the Track View dropdown menus (View, Options, Tracks, etc). Also the TOAST notification text is crisper. I have not noticed a difference in the "Add Instrument/Plugin" menu structure; it looks the same as it did with the value set to 0.

I haven't noticed any negative effects yet. I'll run like this for a while and see how it goes.

Share this post


Link to post
Share on other sites

New problem in Staff view display update.
To show :
1) select one or two measures
2) shift ("nudge") the selection to the right or left with menu or numpad
3) only the selection indicator above the staff is shifted
4) you have to click somewhere in the Staff view so that the notes are also moved !

  • Thanks 1

Share this post


Link to post
Share on other sites
Posted (edited)

I just applied the update and SHIFT +F doesn't work as before.  Instead of optimising the view of the project, which the key binding setup says, it equalises the track heights but only truncates the view to about half way across the screen as if there are invisible events after that, which I know there aren't.  I've loaded a few projects and the fault is the same.  I use SHIFT +F a lot - every few minutes when working on a project - so this is a big nuisance.

Edit:  All works as before in a new project, but all previous projects are affected.

Edit 2:  No, it appears random on previous projects, some load and SHIFT+F works and others don't, for no apparent reason.  I loaded one project and did the 'delete all to the right' (even though there is nothing there) and SHIFT+F then went into toggle mode:  do it once - full project as expected, do it again and the width of the project is truncated to under halfway, repeat ad nauseam.

There is something not right here!

Edit 3:  Explanation.  But still a bug?  When I opened the Tempo inspector in the offending projects, somehow a rogue tempo node had been inserted, in one project where the last tempo change was at bar 52, a 'new' tempo change appeared at bar 192!!  I checked my other projects and this is what has happened when loading each one - phantom tempo changes I couldn't possible have inserted, usually after bar 180 or thereabouts.

 

Edited by Skyline_UK
Expanded comments and added explanation of weird tempo track behaviour in pre-update projects.

Share this post


Link to post
Share on other sites

I have already had 2 dropouts at the opening of projects. Simply when preparing the projects for editing the application closed. Where can I get more information about these abandonments and provide support?

 

Share this post


Link to post
Share on other sites

The latest version of Cakewalk crashes everytime during load of a project with u-he Presswerk or Sating (both the latest available versions) in FX slots.
With previous Cakewal beta / preview everything worked fine.

Crash occurs on project load and only with VST3 versions of plugins. When I use VST2 versions, projects load without crash.
I also tried to create new project with these plugins - successfully added these VST3 plugins, everything works, project successfully saved, but anly project load attempt causes crash every single try.

Other VST3 plugins don't cause crash on project load. In other DAW (Studio One) projects with these VST3 pugins also load correctly.

Actually I'm unable to load my recent Cakewalk work where I use these u-he VST3 plugins.

I can provide minidump files from cakewalk.

I love other improvements anyway! Great work and keep going. :)

  • Like 1

Share this post


Link to post
Share on other sites

Não sei se é um problema de operação ou versão. Eu tenho uma faixa auxiliar que eu uso como um envio de outra faixa. Acontece que ele só está habilitado a funcionar conforme envio quando aciono o monitoramento da pista.

image.png.27f3c729acf71d7545258e4163b9d159.png ------------------------------------> 

image.png

Share this post


Link to post
Share on other sites
8 hours ago, Colin Nicholls said:

Interesting. I totally missed this in the EA release notes, but now I've set it to 1 to see what effect it has.

I run my monitor at 3840 x 2160 and Scale 125% and I definitely can tell the difference, to the greatest degree in the Track View dropdown menus (View, Options, Tracks, etc). Also the TOAST notification text is crisper. I have not noticed a difference in the "Add Instrument/Plugin" menu structure; it looks the same as it did with the value set to 0.

I haven't noticed any negative effects yet. I'll run like this for a while and see how it goes.

It was only done this week so it's after the EA.

I run at 2K (1440p) at 100% scaling and didn't notice a difference until I changed the scale to 150%. Since it's new we didn't enable this by default so any feedback is useful.

Share this post


Link to post
Share on other sites
2 hours ago, Milton Sica said:

I have already had 2 dropouts at the opening of projects. Simply when preparing the projects for editing the application closed. Where can I get more information about these abandonments and provide support?

 

Dropouts on opening projects are not something to worry about. Well look into masking these in a future update.

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, Štefan Gorej said:

The latest version of Cakewalk crashes everytime during load of a project with u-he Presswerk or Sating (both the latest available versions) in FX slots.
With previous Cakewal beta / preview everything worked fine.

Crash occurs on project load and only with VST3 versions of plugins. When I use VST2 versions, projects load without crash.
I also tried to create new project with these plugins - successfully added these VST3 plugins, everything works, project successfully saved, but anly project load attempt causes crash every single try.

Other VST3 plugins don't cause crash on project load. In other DAW (Studio One) projects with these VST3 pugins also load correctly.

Actually I'm unable to load my recent Cakewalk work where I use these u-he VST3 plugins.

I can provide minidump files from cakewalk.

I love other improvements anyway! Great work and keep going. :)

Look at the crash dialog does it say the plugin crashed? If so you should send the dump to u-he.  We're catching more crashes in plugins now so if the plugin does something bad it will be reported. Prior to this the application could randomly be shut down in this scenario.

About loading in another daw, please read the faq on diagnosing crashes. 

Please also send a link to the dump and we can follow up with them if necessary.

Share this post


Link to post
Share on other sites
41 minutes ago, Milton Sica said:

Não sei se é um problema de operação ou versão. Eu tenho uma faixa auxiliar que eu uso como um envio de outra faixa. Acontece que ele só está habilitado a funcionar conforme envio quando aciono o monitoramento da pista.

 ------------------------------------> 

 

An aux track is a patch point connected to the track input. Therefore aux tracks need to have monitoring enabled just like normal audio tracks.
Please refer to the signal flow chart

PS: Please translate to english before posting if you want replies since this forum is in english.

  • Like 3

Share this post


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

It was only done this week so it's after the EA.

I run at 2K (1440p) at 100% scaling and didn't notice a difference until I changed the scale to 150%. Since it's new we didn't enable this by default so any feedback is useful.

I won't be back in the studio for a couple of days to test this, but I'm running a 5120x1440 resolution monitor, essentially 2x 1440p monitors as one big wide behemoth. Is this something that would kick in for me or is it more something that factors in vertical resolution?

Share this post


Link to post
Share on other sites
15 minutes ago, Lord Tim said:

I won't be back in the studio for a couple of days to test this, but I'm running a 5120x1440 resolution monitor, essentially 2x 1440p monitors as one big wide behemoth. Is this something that would kick in for me or is it more something that factors in vertical resolution?

What is your windows display scaling set to? If its > 100% then you should see an improvement.
Let us know your findings.
BTW is it one monitor or two physical monitors with spanning enabled? If so each monitor would have its own resolution irrespective of whether you are spanning.

  • Thanks 1

Share this post


Link to post
Share on other sites

I really love the VST menu that you have implemented. So much easier to find a plugin.  

  • Like 4

Share this post


Link to post
Share on other sites

The waveforms are weird looking after the update, kind of out of focus looking.

Screenshot 2021-05-01 090145.png

Share this post


Link to post
Share on other sites

That was it, thanks! What is the purpose of that feature?

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...