Jump to content

[CLOSED] Cakewalk 2020.04 Early Access 1


Recommended Posts

@msmcleod Ah, interesting, thanks for the explanation! Good to know it's there... :)

@winkpain Yeah, yesterday I suddenly "found" a bunch of tracks I'd hidden in my project and then forgot about it... So in lack of better memory, an indicator would be nice. 😂 (My life consists of reminders...)

Sorry, ending the off-topic stuff here. 😊

  • Haha 1
Link to comment
Share on other sites

On 4/12/2020 at 12:23 PM, msmcleod said:

The BitBridge processes may be the thing that is causing the hang - if you remove those plugins does the program exit normally?

If you do need to use 32 bit plugins, consider using JBridge rather than BitBridge. I've personally found this to be far more stable.

Thanks very much for the feedback mate.

Upon your advice I've swapped over to JBridge - although it took a little while to cross reference 32 bit plugins and change them to load.
It definitely feels like this has had a positive impact - Cakewalk now shows a consistent decrease in memory utilisation and gradually jbridge instances are closed. I'd say it now takes a minute to remove itself from task manager.

Is there any difference in latency and resource utilisation (CPU/Memory) between these in your experience?
I noticed that Cakewalk was up-to 25GB of RAM usage whilst closing! Although I do have some pretty big projects - 200 tracks with 4 instances of superior drummer and a few other VST's. I don't recall it previously getting quite that high although i've certainly gone up to 16GB.

Would you say this is expected behaviour given project size and resource usage?


Best wishes,
Matthew

Link to comment
Share on other sites

Couple issues with the new Arranger function for me:

  • Right-clicking or clicking menu dots and choosing Rename does not function (Double clicking the name in the Arr. Inspector or pressing F2 DOES work, however)
  • Re-sizing a Section by grabbing boundary edge has odd behavior and doesn't re-size to my chosen point but is offset awkwardly by a measure, it seems

Both these issues displayed in attached video....

Link to comment
Share on other sites

Hi everyone,

I'm seeing some little keybinding issues with EA 2020.04:


Inspector keyboard shortcuts:

Shift + I shows Clip Properties but doesn't hide it.

Ctrl  + Shift + I opens Track Properties but doesn't hide it.
(but it closes Clip Properties instead)

The other shortcuts for PC and Arranger Tab are fine.
 

Simple Instrument Tracks:

Using a keybinding for toggling "Input Echo" on/off doesn't visually reflect it's status in the Track View (but works in Console and Inspector View).

Maybe it's similar to one of the bug fixes you mentioned in the OP:

Bug fixes:

  • Instrument tracks mute MIDI channel when using ALT + M


which didn't work in 2020.01 but works now!

 

Thank you so far for this great update, very much appreciated!!
 

All the best,
Klaus
 

Link to comment
Share on other sites

The new functions bring up a little  issue  that concerns Keyboard Shortcut managing.

To exemplify with this new Arranger function:

CW has this new function and it is assigned the default key binding of A in order to display the Arranger as well as in the Track View - View menu showing as "Arranger Show/Hide  A ".  However, I have historically had A bound to a different function in my custom bindings set up. A remains "co-bound" to the new default function as well as my custom one, but only my custom one functions. - This particular point is an over-arching issue with CW's allowance of multiple Key Bindings, which I see as an oversight. Multiple bindings shouldn't be allowed, especially with default bindings. This situation creates serious confusion as I've discussed elsewhere here

But more the point here, and a minor one, really, but...

If I then bind Arranger view to the newly available E, it will function but the Track View - View menu item still reads "Arranger Show/Hide  A "

 

I would ask either

  • update the menu item Key Binding reminder text, or
  • Don't allow custom (i.e. multiple)bindings on default bindings

 

  • Like 1
Link to comment
Share on other sites

15 hours ago, winkpain said:

Couple issues with the new Arranger function for me:

  • Right-clicking or clicking menu dots and choosing Rename does not function (Double clicking the name in the Arr. Inspector or pressing F2 DOES work, however)
  • Re-sizing a Section by grabbing boundary edge has odd behavior and doesn't re-size to my chosen point but is offset awkwardly by a measure, it seems

Both these issues displayed in attached video...

That's odd - I have used both of these functions quite a  bit today and it has worked fine here. I just tried them both again and they work as expected.
Isn't the second one because your snap settings are set to 1 bar?

One thing I have found is that if you ALT-Mouse Wheel to zoom horizontally it doesn't work if your mouse is within the Arranger track. 

Edited by ZincT
  • Like 1
Link to comment
Share on other sites

3 minutes ago, ZincT said:

That's odd - I have used both of these functions quite a  bit today and it has worked fine here. I just tried them both again and they work as expected.
Isn't the second one because your snap settings are set to 1 bar?

Yes, snap settings are set, as suggested for Arranger, to 1 bar. But one would assume that it would snap to the nearest measure boundary beneath the cursor, and not the measure after the nearest measure as you see it doing here.

And the Rename function simply doesn't work for me when right-clicking or menu dot clicking.

Dunno...

Link to comment
Share on other sites

Just now, Colin Nicholls said:

@winkpain,

>>Re-sizing a Section by grabbing boundary edge has odd behavior and doesn't re-size to my chosen point but is offset awkwardly by a measure,

 

You have snap to grid (1 measure) activated. Turn snap off and you should be able to resize the sections smoothly

Understood. But if I want to have snap enabled for measures, I just want it to snap correctly.

Link to comment
Share on other sites

1 hour ago, Matthew Simon Fletcher said:

Thanks very much for the feedback mate.

Upon your advice I've swapped over to JBridge - although it took a little while to cross reference 32 bit plugins and change them to load.
It definitely feels like this has had a positive impact - Cakewalk now shows a consistent decrease in memory utilisation and gradually jbridge instances are closed. I'd say it now takes a minute to remove itself from task manager.

Is there any difference in latency and resource utilisation (CPU/Memory) between these in your experience?
I noticed that Cakewalk was up-to 25GB of RAM usage whilst closing! Although I do have some pretty big projects - 200 tracks with 4 instances of superior drummer and a few other VST's. I don't recall it previously getting quite that high although i've certainly gone up to 16GB.

Would you say this is expected behaviour given project size and resource usage?


Best wishes,
Matthew

Its not expected. Something is likely consuming more memory than it should. Did you try removing some plugins and retesting it? Also make sure that you are not using scheduling model 3 since its still under development and there are some memory leaks.

Link to comment
Share on other sites

1 minute ago, winkpain said:

Understood. But if I want to have snap enabled for measures, I just want it to snap correctly.

Hmm. On closer examination of your video, I think I see what you mean. This isn't happening for me - snap to measure seems to work for section resizing as I'd expect it to.

  • Sad 1
Link to comment
Share on other sites

Noel - I've done what I can to  update all video drivers. I can't seem to find any other way to witness a crash outside of the EA install. I've also performed a couple of restore points to see if anything recent could be causing this. It seems consistent that this crash only appears after the EA install. The prior versions utilizing both existing and new basic template projects doesn't produce this. The EA utilizing existing and new  basic template project loads produces the crash. Not sure what to try from this point.  I'm hoping that the official roll out will also allow rolling back to 2020-01 version if it doesn't work?  I've done probably 3 installs and 2 roll backs of the Early access install.

Link to comment
Share on other sites

1 hour ago, Colin Nicholls said:

Hmm. On closer examination of your video, I think I see what you mean. This isn't happening for me - snap to measure seems to work for section resizing as I'd expect it to.

I think it's with snap set to By instead of To that this happens.   At least trying to move the Section start point backwards in time.

 

Link to comment
Share on other sites

3 hours ago, winkpain said:

Couple issues with the new Arranger function for me:

  • Right-clicking or clicking menu dots and choosing Rename does not function (Double clicking the name in the Arr. Inspector or pressing F2 DOES work, however)
  • Re-sizing a Section by grabbing boundary edge has odd behavior and doesn't re-size to my chosen point but is offset awkwardly by a measure, it seems

Both these issues displayed in attached video....

I can reproduce the sizing issue - we'll get this fixed for the main release.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

I've noticed that when loading a complex project only 2 cores are used for initialising VST plugins.   This can cause projects to take a very long time to load.     For this upcoming release would it be possible to increase the number of threads used to initialise the VST plugins?  If possible upto the number of cores available?

I ask as I'm now running a high core count CPU, which is feeling a little under used! :)

  • Like 2
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...