[CLOSED] Cakewalk 2020.04 Early Access 1

[winkpain]

1 hour ago, msmcleod said:

@winkpain - just to clarify with the resizing issue...

The resizing will now be clamped so that resizing the start cannot go beyond the end time.

However, part of what you're seeing is expected behaviour when using "Snap By" rather than "Snap To".

In your video, your snap settings were set to "Snap By 1/1"  -  so your start time would be changed in decrements of whole measures.

To better explain the difference between Snap By / Snap To, take a section that starts at 3.02.000  with a snap setting of 1/1 (whole measures)

Snap By will decrement the start time by whole measures as you move the start nearer to 0.... so you'll get 3.02.000, 2.02.000, 1.02.000

Snap To will snap the start time to whole measures, so as you move you'll get 3.01.000, 2.01.000, 1.01.000

 

Thank you for replying. Yes, understood.  I have understood the difference between Snap To and Snap By and have used them accordingly without confusion for a while now. Or.... Correct me if I'm wrong here in the following example: 

IF my section boundary is at the start of a measure,  for example at 3.01.000,  whether Snap is set to "To" or "By", the behavior expected would be the same if I drag it one or two bars earlier. That is, if I let go of it as I near the 2.01.000, it will snap to 2.01.00 (or by one measure). If I let go at 1.01.000, it will snap to 1.01.000 (or by two measures). Yes?

What I found, and what is shown in video, is that if I drag the boundary to 2.01.000 and let go, it snaps to 3.01.00. If I drag to 1.01.00 and let go, it snaps to 2.01.000. In other words, a bar after the expected snap to or by point. This what I don't get....

 

 

Edited April 14, 2020 by winkpain

[LarsF]

4 hours ago, foldaway said:

Hi Noel,

Sure, not for a single plugin but I'm talking about loading multiple plugins in parallel which would indeed speed up loading operation considerably.   In my case 16x faster!

When using a project with 100's of plugin instances this would make a huge difference.

If I follow - 16 instances of the same plugin on different tracks?

I'm thinking the quick grouping the tracks, and hold control when you do anything like that - and it duplicates to all selected.

But the same thing with multiple chains, have not tried that.

Or you talk about something all different....

[winkpain]

17 minutes ago, winkpain said:

Thank you for replying. Yes, understood.  I have understood the difference between Snap To and Snap By and have used them accordingly without confusion for a while now. Or.... Correct me if I'm wrong here in the following example: 

IF my section boundary is at the start of a measure,  for example at 3.01.000,  whether Snap is set to "To" or "By", the behavior expected would be the same if I drag it one or two bars earlier. That is, if I let go of it as I near the 2.01.000, it will snap to 2.01.00 (or by one measure). If I let go at 1.01.000, it will snap to 1.01.000 (or by two measures). Yes?

What I found, and what is shown in video, is that if I drag the boundary to 2.01.000 and let go, it snaps to 3.01.00. If I drag to 1.01.00 and let go, it snaps to 2.01.000. In other words, a bar after the expected snap to or by point. This what I don't get....

 

 

I do confirm that this behavior is only with "Snap by" chosen. Although I still don't get the logic of the one "snap unit" offset. As is further exemplified in this video, you see that as I drag the boundary to the preferred Snap by location, the visual change in the section moves as expected as I drag, but when I let go it snaps to a bar(or whatever snap unit is chosen) after that point. This offset is unique behavior not seen with dragging clips or notes with Snap by chosen.

[PawneeLou]

Thank you so much !!!

The Arranger Track seems to be very usefull and so powerful for EDM producers ?

May health be with you and your loved ones !!!

[foldaway]

7 hours ago, Noel Borthwick said:

@foldawayAh I see what you are saying. I'll look into the feasibility of this.

Thanks, that would be great

[foldaway]

6 hours ago, LarsF said:

If I follow - 16 instances of the same plugin on different tracks?

I'm thinking the quick grouping the tracks, and hold control when you do anything like that - and it duplicates to all selected.

But the same thing with multiple chains, have not tried that.

Or you talk about something all different....

Hi Lars,

I'm talking about loading a project & the possibility of using all available CPU cores to create whatever plugins are used in the project.  So that the project will load faster.

[Matthew Simon Fletcher]

On 4/13/2020 at 7:47 PM, Noel Borthwick said:

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.

Hi Noel,

Thanks for your comments.

When I get some time i'll do some further testing for you and provide more detailed feedback.
I was testing the model 3 scheduling at one point but I believe I swapped back  as it wasn't performing quite as well - will double check.

Best wishes,
Matthew

[Matthew Simon Fletcher]

23 hours ago, Noel Borthwick said:

@foldawayAh I see what you are saying. I'll look into the feasibility of this.

Improving the multi-process loading of VST's during opening would deliver huge value to me also - so really supportive and grateful for any efforts in this area!

Edited April 15, 2020 by Matthew Simon Fletcher

[Peter Stiens]

On 4/14/2020 at 5:31 AM, Noel Borthwick said:

 @Peter Stiens thanks for the dump file. Its crashing when creating the step sequencer view which is odd. Did you change the Empty Project.cwt file accidentally in the templates folder? Its normally here C:\Cakewalk Content\Cakewalk Core\Project Templates

I can prevent the crash but it would be worth finding out why the template is referencing that view at all since its supposed to be empty.

@Noel Borthwick I have two PCs running cakewalk, a desktop and a notebook. 
I compared both Empty Project.cwt files with WINMERGE. They are identical. I cannot  reproduce the error on the desktop though I tried very hard ?

But (!), it must have to do with the workspace. I've had created my own workspace, that somehow managed to include the step seqencer view . When I switch to a factory workspace, like "Basic" I am able to create a new empty project without error. If you tell me the location where I can find my created workspace file, I could send it in for examination, if needed.

best regards

Peter

 

 

 

 

[Noel Borthwick]

28 minutes ago, Peter Stiens said:

@Noel Borthwick I have two PCs running cakewalk, a desktop and a notebook. 
I compared both Empty Project.cwt files with WINMERGE. They are identical. I cannot  reproduce the error on the desktop though I tried very hard ?

But (!), it must have to do with the workspace. I've had created my own workspace, that somehow managed to include the step seqencer view . When I switch to a factory workspace, like "Basic" I am able to create a new empty project without error. If you tell me the location where I can find my created workspace file, I could send it in for examination, if needed.

best regards

Peter

 

 

 

 

@Peter Stiens Indeed. I found the source of the problem yesterday and we have a fix. Its quite a bad longstanding bug related to applying workspaces (or screensets) referencing views to an empty project. In your case the workspace referenced the step sequencer view. Since a blank project cannot have a step sequencer this was running into an issue when loading the workspace and crashing.

This is already fixed for the next release but to work around your crash just remove the step sequencer from your custom workspace for the time being and it should resolve the issue.

Thanks for reporting this!

[Zirrex]

The long MIDI note is not cut.
Audio clips are split.
It would be convenient to make the option to automatically cut a long midi note.

[Noel Borthwick]

On 4/11/2020 at 11:54 AM, Jean-Philippe ROGER said:

Hello,
I have a problem with the arrangements. I created 3 sections with only Addictives Drums 2 like Vsti.
I organize the sections in one arrangement in ABCB.
In playback of the arrangement, the sound of the first section plays well and then cuts off just before the start of the second, playback continues but without sound even in normal playback mode.
I have to open the project again to find the sound.

Thanks for your help.

Thanks to help from @Jean-Philippe ROGER via a remote session, we were able to fix this issue. 
The root problem was this:
Arrangement does not preview properly when "Set Now Time With Full Restart" enabled in Track View options. 

A fix has been implemented for the next release.

[Noel Borthwick]

Just now, Zirrex said:

The long MIDI note is not cut.
Audio clips are split.
It would be convenient to make the option to automatically cut a long midi note.

 

This has already been addressed for the next release.

[Noel Borthwick]

On 4/13/2020 at 3:37 PM, RBH said:

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.

@RBH yes we plan on releasing rollback installers going forward with every release.

[Peter Stiens]

1 hour ago, Noel Borthwick said:

@Peter Stiens Indeed. I found the source of the problem yesterday and we have a fix. Its quite a bad longstanding bug related to applying workspaces (or screensets) referencing views to an empty project. In your case the workspace referenced the step sequencer view. Since a blank project cannot have a step sequencer this was running into an issue when loading the workspace and crashing.

This is already fixed for the next release but to work around your crash just remove the step sequencer from your custom workspace for the time being and it should resolve the issue.

Thanks for reporting this!

@Noel Borthwick You're welcome. I have to thank for this wonderful DAW. Greetings to the whole cakewalk team.

[Harry C.]

I have in this update display error when inserting synthesizer. (German Version).

[Jean-Philippe ROGER]

38 minutes ago, Harry C. said:

I have in this update display error when inserting synthesizer. (German Version).

Same problem with French Version.

Edited April 15, 2020 by Jean-Philippe ROGER

[Morten Saether]

46 minutes ago, Harry C. said:

I have in this update display error when inserting synthesizer. (German Version).

Localization is not complete in the Early Access build. This will be addressed before the final release.

[GreenLight]

1 hour ago, Morten Saether said:

Localization is not complete in the Early Access build. This will be addressed before the final release.

I think you should put that disclaimer up front with every EA download link, to save you some time.

[Noel Borthwick]

On 4/13/2020 at 3:37 PM, RBH said:

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.

@RBH I tried to contact you today by PM but didn't get any response. To get further with this we need to do some diagnosis on your system since we cannot repro on any Windows 7 systems we have. It appears to be system specific. I was able to extract some further information from the minidump which appears to indicate that the crash is triggered by Intel IPP software that is used by Cakewalk. See the stack below. When does it crash for you -  On app startup itself, when opening a specific project or when opening a blank template?

This could be caused by incompatible components. Keep in mind that other vendors are also not testing Win7 so it could be something else indirectly triggering the crash. I realize that everyone has their own constraints but please stop using Win7 asap.

 X64_APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ_d3d11!CCreateDeviceCache::CUMDAdapterCache::Load+bc

 

Quote

STACK_TEXT:  
00000000`0012cb10 000007fe`e973e053 : 00000000`00000003 000007fe`e973df07 00000000`0012d570 00000000`0012cde0 : d3d11!CCreateDeviceCache::CUMDAdapterCache::Load+0xbc
00000000`0012cd80 000007fe`e973f3fb : 00000000`00000000 00000000`0012cf70 00000000`00000000 00000000`00000005 : d3d11!CCreateDeviceCache::CAdapterCache::ResolveUMDAndVersion+0x127
00000000`0012ce10 000007fe`e974047b : 00000000`00000000 00000000`77cfd444 00000000`00000000 000007fe`00000000 : d3d11!D3D11CoreCreateDevice+0x54b
00000000`0012d670 000007fe`e97400ec : 00000000`00000000 000007fe`fde16c2c 00000000`00000000 00000000`0012da00 : d3d11!D3D11CreateDeviceAndSwapChain+0x383
00000000`0012d990 000007fe`e1fd2d90 : 00000000`00000007 000007fe`e9740090 00000000`00000000 00000000`00000000 : d3d11!D3D11CreateDevice+0x5c
00000000`0012da00 000007fe`e1ee17a5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00250274 : d2d1!Displays::CreateDevice+0x17c
00000000`0012dab0 000007fe`e1ee0ce1 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000030 : d2d1!CD3DDeviceManager::CreateNewDevice+0xfd
00000000`0012dc90 000007fe`e1ee0fe3 : 00000000`00000000 00000000`00000000 00000000`004b20d0 00000000`00000001 : d2d1!CD3DDeviceManager::GetDeviceFromParameters+0x79
00000000`0012dd00 000007fe`e1ec6cb4 : 00000000`00000000 00000000`0012dda0 00000000`0012deb8 00000000`000716b8 : d2d1!CD3DDeviceManager::GetD3DDevice+0x77
00000000`0012dd50 000007fe`e1ec70e4 : 00000000`004b2080 00000000`1efa0cf8 00000000`00000000 000007fe`e1fa76b5 : d2d1!CDefaultRenderTargetFactory::GetInitialD2DDevice+0x58
00000000`0012dde0 000007fe`e1ec6bf4 : 00000000`00000000 00000000`004b2080 00000000`00000001 00000000`00000000 : d2d1!CDCRenderTargetFactory::CreateHardwareTarget+0x48
00000000`0012de70 000007fe`e1eac172 : 00000000`004cc9e0 00000000`004cc8d8 00000000`004cc968 000007fe`e9fc70ee : d2d1!CDefaultRenderTargetFactory::Create+0x17c
00000000`0012df30 00000001`4031bf44 : 00000000`004b2080 00000000`00001f01 00000000`1cf454f8 00000000`00000000 : d2d1!D2DFactory::CreateDCRenderTarget+0x166
00000000`0012e050 00000001`412dc356 : 00000000`1d0d00d0 00000000`1d0d00d0 00000000`ffffffff 00000000`00000013 : Cakewalk!l9_ippsCos_64f_A53+0x1a2a14
00000000`0012e130 00000001`412dc893 : 00000000`1d0d00d0 00000000`0012e1e0 00000000`00000030 00000000`1cf454e0 : Cakewalk!l9_ippsCos_64f_A53+0x1162e26
00000000`0012e1b0 00000001`41384ef8 : 00000000`1d0d00d0 00000000`77ce7b14 00000000`0012e2e8 00000000`1d0d00d0 : Cakewalk!l9_ippsCos_64f_A53+0x1163363
00000000`0012e210 00000001`413856b8 : 00000000`0012e458 00000000`0db83040 00000000`00001944 00000000`0012e2e8 : Cakewalk!l9_ippsCos_64f_A53+0x120b9c8
00000000`0012e250 00000001`4031a259 : 00000000`1d05a5f0 00000000`1d05a5f0 00000000`0012e309 00000000`1d0d00d0 : Cakewalk!l9_ippsCos_64f_A53+0x120c188
00000000`0012e290 00000001`412e351a : ffffffff`ffffffe0 00000000`0012e3c0 00000000`0012e458 00000001`00000000 : Cakewalk!l9_ippsCos_64f_A53+0x1a0d29
00000000`0012e370 00000001`412e2cc5 : 00000000`41800000 00000000`00000000 00000000`0dfb7558 00000000`0012e458 : Cakewalk!l9_ippsCos_64f_A53+0x1169fea
00000000`0012e3c0 00000001`413314c9 : 00000000`0000000a 00000000`1d059b19 00000000`00000000 00000000`00000000 : Cakewalk!l9_ippsCos_64f_A53+0x1169795
00000000`0012e3f0 00000001`4022f3a1 : 00000000`0dfb6ff0 00000000`0dfb7558 00000000`ffffffff 00000000`0012e520 : Cakewalk!l9_ippsCos_64f_A53+0x11b7f99
00000000`0012e420 00000001`40216f81 : 00000000`00000001 00000000`0dfb6ff0 00000000`1d05a530 00000000`1d059f00 : Cakewalk!l9_ippsCos_64f_A53+0xb5e71
00000000`0012e570 00000001`40386313 : 00000000`0012e648 00000000`00000103 00000000`00000000 00000000`0000018d : Cakewalk!l9_ippsCos_64f_A53+0x9da51
00000000`0012e5d0 00000000`77d116b2 : 000002b2`000000e0 46000000`000000e0 00000000`c0000080 00000000`00000000 : Cakewalk!l9_ippsCos_64f_A53+0x20cde3
00000000`0012e660 00000000`77aa5bba : 00000000`1d12d2e0 00000000`ffffffff 00000000`0dfb70a0 00000000`00000000 : ntdll!RtlRunOnceExecuteOnce+0xa2
00000000`0012e6a0 000007fe`edc16d2f : ffffffff`fffffffe 00000000`77ce7b14 00000000`00000000 00000000`00000000 : kernel32!InitOnceExecuteOnce+0xa
00000000`0012e6d0 ffffffff`fffffffe : 00000000`77ce7b14 00000000`00000000 00000000`00000000 00000000`ffffffff : msvcp140!__crtInitOnceExecuteOnce+0x3f
00000000`0012e6d8 00000000`77ce7b14 : 00000000`00000000 00000000`00000000 00000000`ffffffff 00000000`00000000 : 0xffffffff`fffffffe
00000000`0012e6e0 00000000`0dfb6ff0 : 00000000`0012e898 00000001`402cebe1 00000000`1d198270 00000000`00000000 : ntdll!RtlAllocateHeap+0xe4
00000000`0012e7f0 00000000`0012e898 : 00000001`402cebe1 00000000`1d198270 00000000`00000000 ffffffff`fffffffe : 0xdfb6ff0
00000000`0012e7f8 00000001`402cebe1 : 00000000`1d198270 00000000`00000000 ffffffff`fffffffe 00000000`00000000 : 0x12e898
00000000`0012e800 00000000`00000000 : 00000000`00000000 00000000`00000000 00000001`40230050 00000000`0012ea60 : Cakewalk!l9_ippsCos_64f_A53+0x1556b1