Jump to content
Noel Borthwick

[CLOSED] Cakewalk 2019.11 Hotfix Early Access 1

Recommended Posts

You're probably right, even though I almost certainly did not use exclusive in the end (I just get no sound whatsoever, which probably should not surprise me). I most likely remember fiddling with the slider after setting exclusive temporarily (and before reverting to shared after noticing exclusive does not really work for me).

Share this post


Link to post
Share on other sites
On 11/28/2019 at 9:21 PM, Apeirofobia said:

I've been experiencing some trouble with melodyne, everytime I create a FX region, the software displays the melodyne window but with no information. I need to close it and open it again so I can see the notes.

I'm seeing this too with the Hot Fix (don't have the release to test it with).  I load in a small audio bit and make it a Melodyne RegionFX and the Melodyne window doesn't show any notes.  If you close and reopen the window it does have the notes.

Share this post


Link to post
Share on other sites
5 hours ago, Matthew Sorrels said:

I'm seeing this too with the Hot Fix (don't have the release to test it with).  I load in a small audio bit and make it a Melodyne RegionFX and the Melodyne window doesn't show any notes.  If you close and reopen the window it does have the notes.

Same here. Using CbB latest release (2019.11-build 54), and latest Melodyne (4.2.4.001).

Share this post


Link to post
Share on other sites
4 hours ago, PeterMc said:

Same here. Using CbB latest release (2019.11-build 54), and latest Melodyne (4.2.4.001).

I'm running Win 7,   Latest release of CbB (2019-build 54).  { Melodyne (4.2.4.001 ) Studio version } and  I'm not noticing this issue. Maybe studio and essentials are operating a little differently? Just thought I'd try to add a bit to this.  I know that in the Studio version - I have to select the "blobs" in the track view properties of Melodyne when instantiating multiple tracks. I'm not too familiar with essentials version differences though.

Share this post


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

I'm running Win 7,   Latest release of CbB (2019-build 54).  { Melodyne (4.2.4.001 ) Studio version } and  I'm not noticing this issue. Maybe studio and essentials are operating a little differently? Just thought I'd try to add a bit to this.  I know that in the Studio version - I have to select the "blobs" in the track view properties of Melodyne when instantiating multiple tracks. I'm not too familiar with essentials version differences though.

Running Melodyne assistant here and not noticing anything bad PRE  hotfix install.

Share this post


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

@Matthew Sorrels are you sure that this is new to the .11 release? No changes in that area that I know of that could have impacted that. 

I'm not sure (and I haven't setup any way to roll back yet), but it certainly is a bug now.  I'm running the full Melodyne 4 Studio 4.2.4.001  (not sure that matters).  After testing it a bit, it looks like the "edit notes" icon isn't enabled/clicked on the track that is opened in Melodyne.  If you click on the little blob in the track list, the blobs appear.

Here's what the editor looks like when it's opened:

9BV3eD.jpg

Notice the little orange blob icon in upper left doesn't have a white outline.  If you click that, the notes then appear:

YAMkHE.jpg

It may be a problem Melodyne needs to fix, I'm not sure.  Cubase doesn't work this way (with it's new ARA features) though (the extent of my testing really).

Share this post


Link to post
Share on other sites
31 minutes ago, Matthew Sorrels said:

I'm not sure (and I haven't setup any way to roll back yet), but it certainly is a bug now.  I'm running the full Melodyne 4 Studio 4.2.4.001  (not sure that matters).  After testing it a bit, it looks like the "edit notes" icon isn't enabled/clicked on the track that is opened in Melodyne.  If you click on the little blob in the track list, the blobs appear.

Here's what the editor looks like when it's opened:

9BV3eD.jpg

Notice the little orange blob icon in upper left doesn't have a white outline.  If you click that, the notes then appear:

YAMkHE.jpg

It may be a problem Melodyne needs to fix, I'm not sure.  Cubase doesn't work this way (with it's new ARA features) though (the extent of my testing really).

I behaved the same, but it was the same in the version before i think.

Share this post


Link to post
Share on other sites
1 hour ago, Matthew Sorrels said:

I'm not sure (and I haven't setup any way to roll back yet), but it certainly is a bug now.  I'm running the full Melodyne 4 Studio 4.2.4.001  (not sure that matters).  After testing it a bit, it looks like the "edit notes" icon isn't enabled/clicked on the track that is opened in Melodyne.  If you click on the little blob in the track list, the blobs appear.

Here's what the editor looks like when it's opened:

9BV3eD.jpg

Notice the little orange blob icon in upper left doesn't have a white outline.  If you click that, the notes then appear:

YAMkHE.jpg

It may be a problem Melodyne needs to fix, I'm not sure.  Cubase doesn't work this way (with it's new ARA features) though (the extent of my testing really).

Yes this has been happening for me, but not because of this update, but way back when Celemony fixed the Algorithm issue.

Share this post


Link to post
Share on other sites

I'm experiencing a problem with playback (and recording). When I start the transport (either playback or record) I hear a sharp transient and then nothing. Stopping and restarting just produces the same transient, followed by no sound. The current song position increments steadily as though it were playing back, but no sound is heard.

The only way to recover from this is to go into the ASIO panel and change the buffer size, either up or down. Then it works as expected for a few minutes more.  Note that "recycling the audio engine" by clicking on the icons in the transport module in Cakewalk is not sufficient.  I need to change buffer size in the ASIO panel.

Here's the kicker: This has happened with both my ECHO Layla 3G PCI and also my Focusrite 6i6 (2nd Gen) USB. 

I realize that I need to repro this behavior with the Focusrite exclusively, and demonstrate that it worked better in 2019.09 than in 2019.11, before I have a legit claim that some change in .11 has been detrimental, but I thought I'd post here. I'll be running more tests today.

Share this post


Link to post
Share on other sites

@Matthew Sorrels we were able to repro it when you create a region effect from the menu. The shortcut CTRL-M still apparently worked ok.
We think we have identified the cause and fixed it. It will be in the hotfix that we release soon.

  • Thanks 1

Share this post


Link to post
Share on other sites

Yes ARA 2 is aware of selection. There was a change that was deselecting the clip so that made the blobs not visible on execution of the command. 
If you select something else and then reselect the clip the blobs would be visible again.

Share this post


Link to post
Share on other sites

Yep, it's definitely a selection thing.  I can make the blobs visible by reselecting the clip.  So how does the keyboard shortcut know which Region FX effect to use?  Or is it just wired to Melodyne always?

Share this post


Link to post
Share on other sites
1 hour ago, Colin Nicholls said:

I'm experiencing a problem with playback (and recording). When I start the transport (either playback or record) I hear a sharp transient and then nothing. Stopping and restarting just produces the same transient, followed by no sound. The current song position increments steadily as though it were playing back, but no sound is heard.

The only way to recover from this is to go into the ASIO panel and change the buffer size, either up or down. Then it works as expected for a few minutes more.  Note that "recycling the audio engine" by clicking on the icons in the transport module in Cakewalk is not sufficient.  I need to change buffer size in the ASIO panel.

Here's the kicker: This has happened with both my ECHO Layla 3G PCI and also my Focusrite 6i6 (2nd Gen) USB. 

I realize that I need to repro this behavior with the Focusrite exclusively, and demonstrate that it worked better in 2019.09 than in 2019.11, before I have a legit claim that some change in .11 has been detrimental, but I thought I'd post here. I'll be running more tests today.

@Colin Nicholls Strange. is this a MIDI or audio project? When it goes silent, do you see meter activity on the Main outs in the console?

Share this post


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

@Colin Nicholls Strange. is this a MIDI or audio project? When it goes silent, do you see meter activity on the Main outs in the console?

Both. Audio and VSTi's. Fairly big project. Despite my best efforts,  I could not reproduce it, today. I'll post back with more info if it happens.

Share this post


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

×
×
  • Create New...