MarianoGF

https://www.musictech.net/news/cakewalk-update-aes/

If I were not me, I'd write this post to say that the new version 1.32 is beautiful, but since I am the editor, this is just a message to put this thread back in your unread list. BTW, It's actually beautiful👌::.

More beautiful than ever! Give it a chance::.

Minor bug: When you do right click on a crossfade and open the old CLIP crossfade dialog, the checkmark is not showing the existing crossfade type between those clips, but indicating the same crossfade type selected in the new top right crossfade menu. There is some kind of uncorresponding visual synchronization between the clip crossfade dialog and the new crossfade menu, that can lead to confusion. Anyway, thanks a lot for the constant development and improving of Cakewalk. Now is a better DAW than yesterday. You are great::.

Thanks Noel. Yes, I'm talking about those spikes. They are not present when I edit in real time, but they appear after bouncing. Hope you take it under consideration for another update.

I know that the following is previous to the 2019.9 Early Acces, but it could be great you consider to adressing it for the upcoming release: When I edit real time stretched clips, everything sounds fine. But when I bounce them or the whole project, it appears clicks on the former edit points or crossfades between those time stretched clips. Here I attach a .cwp example file with audio. This issue occurs even if I choose Elastique Pro as the stretch method for both online and offline renders. And it happens with any kind of bouncing: bounce to clips, to tracks, freeze and even export (fast bounce or not). The workaround I can do in the meantime is to bounce those clips INMEDIATELLY AFTER stretch, and BEFORE any subsequent editing. If I'm not the only one experiencing this, hope you consider it for fixing. Thanks!

Dear staff, Thanks a lot for the constant effort you put in improving Cakewalk every day. Why don't you use the same existing crossfade dialog (for clips) in the new crossfade menu as shown below? It would be more graphic, summarized and intuitive. And, if possible, consider using the selected crossfade type icon for the button::.

Hello, and thanks for paying attention to this: When I edit real time stretched clips, everything sounds fine. But when I bounce them or the whole project, it appears clicks on the former edit points or crossfades between those time stretched clips. This issue occurs even if I choose Elastique Pro as the stretch method for both online and offline renders. And it happens with any kind of bouncing: bounce to clips, to tracks, freeze and even export (fast bounce or not). Here I attach a .cwp example file with audio. The workaround I can do in the meantime is to bounce those clips INMEDIATELLY AFTER stretch, and BEFORE any subsequent editing. If I'm not the only one experiencing this, hope you consider it for fixing. Thanks!

With "multiple mixers" he means that the inspector and the consolé expanded at the same time seem to be a confusing one. I agree on that. I think it shouldn't be able to see the inspector while the console is expanded, at least when docked. I think the 5th point regarding to "the quality of time stretching" being low, is old. It WAS low, but it has been improved a lot with the addition of elastique technology. Check that again.

Thanks forge622, but I'm talking about the Select, Loop and Punch Modules. In fact, I asked to the bakers if it's possible for them to change according to the display's selected time format (what you are talking about). Hope they do it someday.

Is there a way to change to H:M:S:F the time formats of Select, Loop and Punch Modules, as well as the "Go" menu? Thanks::.

Something to consider for the next update: Automation envelopes can't be seen well in a track or bus with waveform preview on. They seem to be "at back". Thanks!

Message deleted. Wrong thread🙏

Delta value error Not sure if this happens just after the last hotfix, but... In a project with tempo changes, the time (H:M:S:F) calculation of the difference between the selection start and end markers is wrong after the first tempo change on. In the example below you can see the start marker at 7:30:14, and the end marker at 8:30:14, which should result in a delta value of 1:00:00. But nevertheless, Cakewalk is calculating a difference of 1:50:12 (H:M:S:F). (click twice on the image to enlarge) - Also, it seems that the calculation gets worst after every new tempo change. - The same error seems to happen for the other time formats of the ruler (Millisecond and Samples) but M:B:T, on which it seems to calculate the delta value right.

Give it a chance!