Noel Borthwick

The free version will not do MIDI extraction. Celemony no longer allows it.

2 hours ago, Cezary said:

I dragged an audio clip to the instrument track and to the midi track. The result is the same every time.  Audio clip is a simple vocal melody.

If you are running the free version of Melodyne 5 or the player, MIDI extraction no longer works. You need to purchase one of the other products.

2022.02 has now been officially released. Thanks everyone for your feedback!

The issue is fixed if you download build 27 linked from the main post.

10 minutes ago, Keni said:

Thanks Noel...

 

I've attempted to isolate the issue but it's still eluding me. I've stripped projects down removing all plugins and the problem remains. I increased the ASIO buffer size to 4 times the size/latency and the problem persists.  I didn't try larger as it would be useless for me beyond 1024...

 

Please follow up via PM.

That is only a single data point and doesnt prove anything definitively. The cause could be any number of reasons. You haven't answered the question of whether it happens only on a specific project for one. it could be system load related, timing or a million other things that differ from one version to another.  Follow normal troubleshooting by isolating the problem if its project specific. If you can narrow it down to a plugin or something else and send us better repro steps then there might be more to follow up on. But for now there is not enough to go on.

1 minute ago, Keni said:

The dropout is all sound. It works fine in 2021.12 and before. Nothing in the project was changed prior to updating to the EA and rolling back proves it.

 

Something else changed...

That something else would be environmental. As mentioned there is nothing in the code that changes behavior of loop toggling.

Awesome thanks for verifying that.

Please refer to the dropout codes help.
Code 5 : Disk reading overloaded and could not keep up with playback pump : Increase playback I/O buffer size

This is completely unrelated to any work in this release. Try and breakdown your project and troubleshoot whats causing the load is the only suggestion I have.
There are literally no changes to how toggling looping works since 2012.

1 minute ago, Keni said:

Good find. That fixed the more serious issue. Melodyne is now performing as I expect.

...but the audio dropouts are now even more severe than in 23/25/26. If I enable or disable Loop during playback, the dropouts are sever enough to stop the audio engine repeatedly. This is on a piece that works fine when reverted to 2021.12.

 

Likely coincidental. There is zero change that would have impacted dropouts. What is the dropout code? Is it happening on a specific project?
Without details its impossible to follow up on such cases.

4 hours ago, Keni said:

BTW...

I also verified my so far un-commented upon report of delay/drop outs when clicking to enable/disable Looping... All is well in 2021.12, but not in either 23, 25, or 26.

 

Most uncomfortable...

 

Not seeing anything like that here. Multiple people have tried it. It is likely specific to your project. What drop out code are you getting?

@Keni please download build 28.02.0.027 which is linked from the top post in this thread. Let us know if it solves the issue.

1 hour ago, Keni said:

Thanks. That nailed it for me. I will locate the correct dump.

Do I then send it to Noel via attachment to PM?

Never mind. Read more of the above.

 

No need now. I've managed to locate the cause and we'll post an update shortly for you to try.

25 minutes ago, Keni said:

OK... Problem with 26

 

All was (mostly) well here with 25, but after updating to 26, Melodyne keeps causing bad crash.

 

Situation...

Copying a Melodyne clip from one track to another, then attempting to open the newly copied clip and up pops dialog reporting Melodyne crash and offering emergency save.

 

Now rolled back to 2021.12 and all is well again. I believe I still have the two previous updates (23/25) and will attempt updating to them now.

 

26 is a show stopper here...

 

Oh... I'm using Melodyne 4.x as I'm trapped with Windows 8.1 due to old hardware...

 

@KeniPlease send a mini dump file.

8 hours ago, Craig Reeves said:

So sorry about that! I'll be sure to test out the newest one! Thanks for the quick response!

@Craig Reeves can you please verify whether build 28.02.0.026 resolves the autotune issue? We don't have any way of verifying it since our license has expired.

6 hours ago, Will_Kaydo said:

So, the keybinding issue is just gona be ignored? 

There's absolutely nothing wrong with my system - as in NOTHING! I even went as far as to buy a new SSD just to test. Again on a brand new clean Windows 10 OS (this time on a brand new drive) with absolutely nothing on it, with Windows Defender disabled keys binding dont save unless that new VST3 guest path is removed and I wish I knew why. 

So I guess when theres a new Update i'm gona have to remove that path and manually save keybinding every time. 

This is something very specific to your system and nobody else has reported it. So without more information we have nothing to proceed on.
We’ll start a PM thread with you to collect more information so check your PM’s and provide more information.
@Will_Kaydo please respond ASAP since we are planning on releasing this update soon.

@Craig Reeves Please read the prior threads. I posted an update to try that may fix the auto tune issue as well.
The build linked in the first post in this thread is the latest.

The EA build has been updated (please redownload from the main post in this thread). This fixes the problem with Melodyne or any other ARA plugins that are used as track effects rather than region effects. Please verify that this fixes the issue.

13 hours ago, Max Arwood said:

Yes, that is what I am talking about. Autotune Pro with other plugins. Sometimes sounds like an octave down, other times just distortion. I thought I had trashed the file for some reason. What I opened another song, it was the same distortion.  Had to go back to 2021. Another note - my driver is set to 2048 buffer samples. Is yours high like that?

@Max Arwood @KWILD If you are running AutoTune Pro can you please check if its being reported as an ARA plugin? I believe it might be because of this: https://antarestech.force.com/s/article/Auto-Tune-Pro-ARA-Compatible-Host-DAWs

You can check this by looking for it in the clip region effects menu. If you don't see it there look in the registry under HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory
Under the record for autotune see if the isARA flag is set to 1 in any of the records for it. 

If its exposing itself as an ARA plugin and you are using it as a track effect then its likely to be the same cause as the melodyne issue that was reported. 
We'll be posting a fix for that shortly...

12 hours ago, Jonathan Wade said:

update seems to have broken melodyne. Plugin wont follow playback, read previous edits, or transfer audio. Rollback fixed the issue

There was indeed an issue with using Melodyne in an effects rack rather than a region effect. I've fixed that issue now.
@Laurence Levin are you also using Melodyne as an effect this way? I'm curious why anyone chooses to use melodyne as an effect when ARA is the proper way to do it.

9 hours ago, Jonathan Wade said:

update seems to have broken melodyne. Plugin wont follow playback, read previous edits, or transfer audio. Rollback fixed the issue

@Jonathan Wade which version of melodyne are you using and are you using it as a region effect?
We're not seeing any issues with follow playback in this release.
Are you trying to manually transfer audio in melodyne? That is not required since using it as a region effect clip automatically handles that.

@Scheffler what message? Please post a screenshot. You should be able to install the EA directly through help | check for updates.

1 hour ago, norfolkmastering said:

It's looks like the issue of the UI displaying incorrect audio port names on sends and inserts has been fixed but I don't see it on the list.  Could you confirm it has been fixed?

E.g. it used to the be case that if you allocated a send to the left leg of a stereo pair; after you save and close the project, then reload the project, the send allocation would show as to both L and R, even though the allocation was actually L only.

Regards

Robert

Yes this was fixed.

This thread is only to discuss issues related to the early access release. Please don't post unrelated topics here.

13 hours ago, sreams said:

I haven't found a way to reproduce this consistently... but after installing the EA build today (was on the latest release build before that), I have had three crashes to desktop during playback. Two times just pressing play, and once a crash just in the middle of playback... with Cakewalk just disappearing.

@sreamsCan you set exceptionhandlingseverity to 7 in preferences config and retest?