Noel Borthwick

Hi @Rostislav this isn't your fault. It's hard to say what let the project to get saved in that state. The edit filter is the dropdown in the track strip that by default says Clips. By changing it you can select what data you wish to edit in the track. See the help for this here. You can easily switch your track to clips if it happens again.

1 hour ago, SomeGuy said:

I own multiple DAWs, the changes for Cakewalk - even in the bug fixes, are miniscule compared to what I'm seeing with those other packages.  And now, it's not "because they're buggier."

I'm sorry you feel this way. There has been a huge amount of bug fixes just in the last year and thousands since the old article you quote. Just looking at our internal issue log we have over 500 issues resolved since we started. I don't see how that could be considered miniscule in relation to any other competitive DAW. Not sure if you have seen our public changelogs since we started last year: 
See prior release notes.
Check out all new features released to date.

While we do have feature work in our pipeline, we are focusing on workflow improvements and stability, not feature bloat. This is what the majority of our users want from us as opposed to shiny new toys. 

Weird corner case. The real issue is that somehow track 6 had its edit filter state set to show an envelope.
However the actual envelope data stored was not correct. As a result the code was not setting the edit filter state properly. Although the track view showed it as "clips" internally it was still "envelope".

There is a rule for copy (not copy special) to reject note data when copying with the edit filter set to envelopes. Likely because we don't want to copy and paste data for the wrong type when the edit filter is asking for envelopes. As a result you saw this behavior that copy was ignored.

I have fixed it for the next release so that when the project is loaded we ignore a spurious edit filter setting of envelopes and set it back to "clips". This fixes your project and when it loads up the edit filter will now show clips. It would be interesting to know how it got into that state in the first place. Perhaps you might remember if at some point you had set the edit filter to envelopes and maybe something went wrong after...

You can make your project work again by setting the edit filter manually to something else and then back to clips. Then save the project.

@Rostislav thanks for the report. I was able to reproduce it. We'll investigate your project and see why it happens.
On first looks I can see that the selection somehow thinks that nothing is selected even though the UI is showing it. We'll investigate further.

Thanks for the update . As I said we haven't made any intentional changes to the console 1 support. If anything syncing of selected track states should be more robust in the May release.

Let us know if you have any further issues.

We're pursuing all leads that might have any bearing on this. So far I've even had two live sessions with users but nothing has shown up as suspicious in diagnostics and the problem was not reproducible on the customers end. Are you sure this is not a demo plugin issue in this case? Many demo's intentionally do not retain settings....

@gargonknight please send us a crash dump. This will help diagnose what is crashing your system. You won't lose any data because of this.

There are some Instructions here

Can you be more specific what is messed up?

We haven't changed anything directly with console one but there are changes to how the selection logic works with ara2 that is similar to what happens with console one.

Also did it work in the prior release from March.

Haha yes I saw that. We had that numbering from 2016

https://www.pro-tools-expert.com/production-expert-1/2019/6/1/did-you-know-that-there-is-a-free-daw-that-has-ara-support-we-investigate-what-cakewalk-can-do

I don't think reinstalling is going to do anything. Why not check if someone else can repro your symptoms with the same project first?

If you resave the project after that dialog has been processed do the messages go away on next open of the project?

@SynthManDan If you share a link to your project file we can look at why the tracks are not showing. I'm sure others on the forum may also be able to assist. The tracks are likely hidden in track manager.

The bug where the original copied clip was being removed from the take lane has been fixed for the next release. We've also greatly improved general copy paste and drag and drop with take lanes, fixing many issues.

14 hours ago, Moving Air Productions said:

Could I get a little assistance on the string I should use?

@Moving Air Productions you can use the procdump tool to capture it like this from a command prompt:

procdump.exe -ma Cakewalk.exe cakewalkhang.dmp

Alternatively you can follow the instructions and capture the dump from task manager. The issue there is the file will be large since it captures a full dump.

Yes please list the version of Melodyne in all reports since they have different feature sets. The follow clips option is apparently not available in essential but I think its partly baked in for the latest release. As I mentioned earlier the latest Melodyne release has many bug fixes so I'm not surprised that it works correctly now. 
Let us know if you see any further problems.

Great we can repro it. Will investigate

@pdkmusic if it is caused by a lens could you please send us a copy of the lens in question as well as the project file please?

You can find the by typing this into windows explorer:

%appdata%\Cakewalk\Cakewalk Core\Lenses\User

There should be a .lns file there with the lens you saved.

It sounds like you have multiple split instrument tracks all feeding the same synth audio track. In that scenario its normal for audio to come from the track that the instrument outputs is assigned to. All MIDI goes to the same synth instance as well.

Are these simple instrument tracks or split?

On 5/28/2019 at 7:41 AM, Antonio López Zambrano said:

Hi msmcleod

Thank you very much for your didactic help.

I believe that everything has been solved.

I have been doing tests since yesterday I have configured as "Elastique PRO" instead of "Elastique Efficient" and so far everything is fine.

I have also tried with "Radius Mix Advanced" and it is also good. Apparently my problem was in the default option "Elastique efficient". This problem was the only one that did not let me move forward with Cakewalk by BandLab. Now I'm happy.

Thanks again for your help.

Greetings  /Antonio

@Antonio López Zambrano Elastique pro will sound better than efficient. However you shouldn't be getting distortion on efficient. Could you please send us  a simple project or wave file that shows this problem? We can send it to the elastique developers for analysis. In our tests we don't see distortion or any visual issues using the efficient mode.

I'm sure @Pete Brown may have heard of this issue. Sounds like a Korg driver limitation to me.

@AxlBrutality maybe it's the sequence of operations. Well try it again but it may help if you note the steps you are taking starting with an empty project.

@AxlBrutality that's strange, I just tried it and its completely fine here no signs of anything going wrong. I wonder if its related to some settings in the compressor.

Could you please send me a link to the project in question so we can try and reproduce it? I tried both doing a send to the compressor as well as outputting to the compressor and it was fine.

On 5/28/2019 at 2:25 PM, HappyRon Hill said:

Really happy with the new ARA2 integration makes Melodyne and cakewalk working together better, this was one issue why people I know left Cakewalk when it went bust. 

Now if cakewalk could only solve the "not saving settings for plugins" bug I'll be singing it's praises .

 

@HappyRon Hill are you seeing this? So far all evidence of that issue leads to issues in plugins themselves where settings can get lost (potentially due to copy protection). I spent 3 days exploring every possibility when loading and saving projects or even editing or loading presets. There was nothing that CbB does that could lead to a full reset occuring on the plugin that I was able to find. The one case that was reported to us with a repro project had to do with it saved with Waves 9 and when I loaded it in the latest Waves version it loaded perfectly.
If anyone has more data on this we're happy to troubleshoot with them. I've added some defensive code that may detect errors reported from the plugin for the next release in case it helps.

29 minutes ago, HIBI said:

Improvements in the current Version 4.2.2
Melodyne 4.2.2 brings the following improvements and numerous minor optimizations all of which make your use of Melodyne more enjoyable, reliable and swift. (Starting from Version 4.2.1)

New functions and improvements

Better window management in Studio One 4: Melodyne’s zoom and other window settings now remain constant when you select a new audio region, instead of being displayed with individual settings as previously.

Bug fixes

Fixed: In Cakewalk, under certain circumstances, instead of new files being analysed automatically, you had to select an algorithm manually in order to trigger the detection process.
Fixed: In the stand-alone implementation of Melodyne, closing a project without saving sometimes led to a crash if other projects were open at the time.
Fixed: In Logic, validating the Melodyne plug-in sometimes slowed down the launch of the DAW.
Fixed: In the stand-alone implementation of Melodyne, opening or importing projects under certain circumstances led to a crash.
Fixed: In ARA mode, it could happen under certain circumstances that the monitoring during blob editing no longer functioned after starting and stopping playback.
Fixed: In Cakewalk, selecting a new clip sometimes led to a misalignment of the Melodyne position display.
 

Yes 4.2.2 is the version with several fixes for Cakewalk. Is this version live now? If so all Melodyne / CbB users should get it since it resolves many stability issues.