Matthew Simon Fletcher

Cool - thanks as always Noel and team. I've just had a crash this morning but unsure if this pertains to this build or not - i'll share the .dmp with you via PM.

Thanks as always guys! Are there any known benefits to stability/performance of being on the latest VC redists? On the flipside any risks/things to watch out for these are they 100% backward compatible?

Thanks for confirming - I've got some more edits to do this evening so will test again and share the logs if I get a crash. Fairly sure that's what I would have done the otherday though, so definitely doesn't seem 100% reproducible. Best wishes, Matthew

Hi Andres Strange - I've been using the latest melodyne version in Cakewalk with a large number of tracks and haven't experiences any issues. Hope you're able to get it resolved. Matthew

https://www.bestservice.com/celtic_era.html Can highly recommend the Celtic Era library, which has Highland pipes and Uillean pipes.

For interest I decided to save a track template that included all tracks in the project (approx. 500) Following on from above, the baseline usage was 3.6GB Surprisingly the peak usage didn't appear to go above 5.5GB Post change I believe it was around 3.7GB. Given this had approximately 4-5 times the content of the initial one, I was surprised that it seemed to complete in a similar time frame (2 mins) and the resource didn't seem to go significantly higher, although it still exhbits the same issue of memory not being released and a long wait time. Looking at resource monitor there was no maxing out of CPU, RAM or disk, so I'm wondering what the limiting factor is to performance? Something that isn't multi-threaded? CPU was only around 10% so doesn't even look like any cores were being maxed out.

Hello! That was probably me - i'd been having some back and forth discussion with Noel and co about track template performance, but focussed more on moving tracks within them So I hadn't actually tested saving track templates in the latest build, but i've just given it a go now. Baseline RAM: 3.3GB RAM on saving a drum template (comprising 99 tracks across four instances of Vienna Ensemble pro): 4.0GB RAM having completed the track template save: 3.5GB That save activity took 2 minutes which seems like a worsening of performance versus a previous build, but can't say for definite. In any case, it seems long to create a file that's only 12MB in size. It also would demonstrate that the issue is occuring with plugins other than Kontakt and that something isn't being released, given the memory is higher versus baseline. I can also confirm that if save the same track template again, the usage will go even higher. New baseline: 3.5GB New peak: 5.5GB (very briefly, it was around 4.2GB mostly then shot-up in the last few seconds) New post change: 3.6GB Again this took approximately 2 mins to complete with Cakewalk frozen during this time period. You've already got my project template if you want to debug an example file Noel

I believe it's a logitech G500s.

That's very perculiar - I haven't got Axe Edit III but regularly use Axe Edit II/Calkewalk and haven't seen that behaviour.

Of course Noel - will drop you a message shortly Thanks as always.

Thanks Mark - now i've updated the master project all is good anyway Appreciate the track template improvements - I do use these in addition anyways.

I like fusing genres so there's a a few orchestral libraries, rock/metal layout, electronics (pads/leads/bass) and all sorts of other world instruments, the VST's are split across three mini-servers via Vienna Ensemble Pro. A lot of the tracks are drums given that up-to sixteen channels can be common for some libraries. I've also got some predefined tracks for people who I collaborate often with; again saves time and means I can keep mix presets. Originally i had a seperate layout for writing and mixing but i've kinda combined them together for ease. I'd say the actual number of active instruments/tracks will be probably a quarter of that; when I know I definitely won't use something it'll get removed. There are some professional composers though who's track counts run into the several thousands! Often because they have multiple different orchestral libraries for different moods, and these can be fiddly to set up each time from scratch so it's easy having things already there. In the interest of keeping this thread on track, if you want more details feel free to drop me a message The performance of my project in general is pretty good - hence why I was flagging that it seemed unusually slow to do the track moves into subfolders. This occured with both VST tracks and blank audio ones.

Great release! Delighted about nested folders. My only observation is that it seems to be a slow process to move existing tracks into the nested folders - Cakewalk keeps hanging and it takes a minute or so to do. Is that expected behaviour? I'd have thought this was only a simple cosmetic change but perhaps something more complicated has to go on behind the scenes to enable this functionality. Admitedly I have a large template project of approx. 500 tracks, but was only moving 20 or so at a time.

Immediately after the following error appears: Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Cakewalk Application because of this error. Program: Cakewalk Application File: The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C000000E Disk type: 0

Upgraded and can confirm that Cakewalk is functioning fine Edit: May actually have spoken too soon, have had three project crashes over the last hour. @Noel Borthwick- Cakewalk didn't capture a drump but if I go into the event viewer I see this each time: Faulting application name: Cakewalk.exe, version: 27.9.0.145, time stamp: 0x615660bb Faulting module name: Kontakt.vst3, version: 6.6.1.139, time stamp: 0x612f7036 Exception code: 0xc0000006 Fault offset: 0x000000000068b620 Faulting process ID: 0x26e4 Faulting application start time: 0x01d7bbaf7b79d470 Faulting application path: C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe Faulting module path: C:\Program Files\Common Files\VST3\Kontakt.vst3 Report ID: 1dc542e1-bd68-46b0-bba0-c9b9817ca41d Faulting package full name: Faulting package-relative application ID: Shoudl I report that to Native Instruments directly?

Hi Noel - can confirm that's repaired it! Fantastic work as always; i'm so grateful for your efforts on this! Was also delighted to see: "Optimizations to speed up project loading with projects containing high track counts." Is that anything to do with the fact that the test case I sent over had 519? 😆

Great stuff - thanks Mark, Noel and co! Will give that a test tommorrow.

Hi Jacques - I have several hundred tracks that aren't playing, it was only a small section of guitar tracks that were playing. Hence unfortunately that's not a viable solution here to delete either set. Thanks friend

I'm very grateful! apologies if I didn't sound as such. Chris.r - I personally haven't had this problem before this pre-release, but absolutely not to say that it isn't an older issue. Sailor55- I tried a number of things such as soling/unsoloing and reloading the project but didn't find a last fix, so hence was going to go back to an earleir project version.

I appreciate your thoughts I don't use the archiving functionality and couldn't see anything else obvious. I toggled the global solo button several times, so my expectation would be that that would clear anything anyway. To be fair I do doubt myself often, so hence not raising this immediately, but when other people mentioned a similar issue, it seemed beyond coincidence and hence was more likely to be triggered by something in the newer build.

Not that I could see unfortunately - also that would mean the global solo toggle button isn't working correctly.

Hi Noel - have dropped you a message. Many thanks!

Just confirming I've also experienced this, except strangely in mine, it's only guitar that will play unless soloed! I was wanting to do a little bit more testing given that i'd recently raised another bug that turned out not to be specific to this release! This isn't occuring on all projects, but on the project that I have encountered it, it seems to remain if I go back to pre-release build. I was going to work around it by opening up an older working version of the project and then copying across new changes. I can send over a project with this issue later that may help to diagnose this if you need another example?

Hi Noel, Thanks as always. I've just had the same issue occur now on the release build too, so as you say I think it can be ruled out. Apologies; as I say it was only occuring at first on the newer build and seemed to resolve when I went back, so hence raising it in here but that might just have been the tempremental nature of it. I thought it was unlikely given I couldn't see anything obvious in the patch notes. If I can reproduce this consitently i'll raise it as a general bug. Best wishes, Matthew

Hi guys, I've been experiencing a strange but very significant issue using this latest batch of pre-release builds. I have instances of Komplete Kontrol in an existing project, and for some reason I have to keep reloading these in order to hear sound. I.e. sound occurs if I play the midi, but then won't work unless I reload the presets again. This has to be carried out on every track. I went back to the stable build and loaded the project and this issue did not occur. What was perculiar though was that if I inserted the instruments into a blank project using the new build, there were no issues with playback. Could the new builds have caused some sort of change to the project file? Best wishes, Matthew