Matthew Simon Fletcher

So another observation. I fixed the waveforms by regenerating the images and then saved the project. I opened it back up again and the waveform is back to being glitched!

Here's an image with waveform disabled (still visible issue): I can confirm if the files are regenerated the spikes do disappear entirely at any zoom level. I guess the question is how could this data be getting corrupted? This a fairly old file, but not a complex one and I've seen the issue in a lot of different projects over the years. Also another observation - this is the same clip (now with the waveform image regenerated). You'll see that the line thickness remains thicker up until about the center of the image. Why is that? I checked the meters and the audio fades off almost immediately after the second line. There is no change that occurs when the line goes from thick to thin. That to me looks like another example of the waveform not generating accurately. Again I can confirm that happens with the waveform enabled/disabled.

Thanks Mark - I'll try those in a moment. One observation I have upon reopening the project is that the zoom level by which the issue is visible has changed! This time I didn't have to zoom in as much before it went / it's visible at fewer levels. No changes were made to the project and I closed without saving.

Zoomed all the way out. I was able to get it to disappear eventually by zooming right in, but that took five zooms until it happened. I could understand certain things appearing more/less obvious depending on zoom level but the key point here is that there is literally nothing on the audio meter. @msmcleod how do I change the waveform setting you mentioned? I thought that was only for bus/synth tracks, whereas this is the audio track itself.

Hi all - thanks for the discussion on this I've finally just been able to recreate it (see the mark on this track next to the cursor). There is no audio on the meters here. I'll try zooming and a few other things but just sharing whilst I have it to hand.

In the situation I'm describing there is no legitimate waveform detail to be highlighted as there is nothing on the audio track. It should be flat in the section at any zoom level, but spikes are visible. I'm fairly sure I've seen this both upon initial import of an audio track and after having done a bounce to clip.

Evening Jim - thanks for the reply. 100% visible not audible. I think zooming is a factor in it , however I've also seen it on occasions at any zoom level. I've been able to screenshot if previously, I've just simply been doing other things and unfortunately misplaced the files! Graphics / monitor drivers are very likely to be relevant in general though. I'd say I'm using a modern / reasonable spec / supported system and hence I'd expect that if it's not working for me then it's going to have reasonably wide impact!

Thanks John - yes I think you might be right around the zoom levels!

Thanks for the details - I think that's probably all the main things tried. I believe there is a bug fix in Sonar for midi notes not playing in busy projects, but can't be 100% certain that's the same issue.

Thanks - that's what I assumed,, but wasn't sure if also had another meaning. Unfortunately that's always worked fine for me and I can't think of what would be causing that behaviour to be different for you. I'll see if I can find a way of breaking it, but apologies I can't be more helpful. If you haven't already I'd try a full reinstall, resetting default preferences and repairing the visual C++ redistributibles as people have noticed odd behaviour with these becoming corrupted.

I think the method you've outlined is the best and I use it regularly - hopefully the advice you've got in the other thread will mean you can overcome instruments not working There are just certain things to watch out for but once you've done it a few times it gets quicker and easier

I've not encountered any where the guitar wouldn't play but often there is a lot of unneeded/messy midi data. I usually import onto a blank track that isn't routed anywhere and then gradually copy sections over to the live VST track, removing things as I go. It just helps me keep track of what I'm doing as often if I'm doing a cover I'll bounce between things.

Have you tried changing the buffer size? There's also a midi playback parameter worth increasing. When you export have you tried using the real-time playback method/changing rate? Does it happen if all other instruments are muted? What's your system load like? Any dropouts/overruns being displayed? Are all your inputs routed correctly? Does the note have correct velocity? Have you tried deleting/re-adding the note (seems silly but I've had to do that before now) Happy if you want to send me the project to see if I get the same result - I don't have EastWest currently installed but if you say it's reproducible on other VST's then should be fairly easy to spot.

Is the Musio file installed in Common Files\VST3? If so Cakewalk should pick this directory up. Go to Preferences - File - VST Settings and then press "scan" and then it should become available via the insert - soft synth list.

I've raised a case as my bandmate has just confirmed he's seen this before. If anyone else has seen it can confirm and add a screenshot that would also be super useful evidence as I still haven't been able to reproduce today. I'm not sure what the mechanism is behind the waveform being generated. I know there's the cache that you can delete files in to re-generate but in this case they're getting corrupted when they're first made rather than it being a gradual issue over time.

So just to be really specific this hang occurs if you either load up Cakewalk and navigate to the project or you're navigating via file explorer and opening the project/Cakewalk that way? I.e. you're not trying to open up the Cakewalk instance more than once? Can you try moving an example project to a different disk drive that isn't compressed? Do you have any extensions/addons to the file explorer? I find that it can be very temperamental in general on W11 unfortunately so try and remove any of these.

Only just discovered this thread and I'm really excited to try this out as I have use case for midiFX at the moment! Thanks for creating this

If you route that content to a different VST, does that also fail to play the note?

Yes this is common behaviour for all the cached content to be released over time. 15 seconds is about reasonable in my experience for how long it would take to release that much content. It would appear your Musio bug has been resolved, so I'd say this is now functioning in line with expectations

Can you give an example of what the tooltips are so I can confirm I'm checking the right thing?

Trying to get a screenshot of this but as is typical it's not doing it currently! Has anyone experienced the issue whereby an audio track appears to have content at point but it's silent? Often this will look like a single spike. When I've encountered this it's been a UI thing and there isn't legitimately content there - I most often see it when importing audio tracks and on one track the vocalist will have recorded the first verse for example and then it's visible in a section that's unrelated (e.g. much later in the song). It does lead to some confusion though because you've sometimes got to go digging to check, and/or risk deleting something that might be relevant. I've seen this a load of times over the years in Cakewalk/Sonar in different projects but don't believe I've raised it before (others might have).

I'm running on multiple machines and as far as i'm aware it's unlimited

If it's the W10/11 compression model then that is meant to be high performance, but there is going to be a larger overheard the more files it's doing. Maybe start by uncompressing the Cakewalk / OS directories, given those are what will be in use at the time of the issue. What happens if you navigate to the file and load it via explorer rather than in Cakewalk?

I believe it was a mixture of things - some of which were bug fixes (there was particularly activity that could take up a load of CPU due to threads being blocked), tweaks were made to how VST's were loaded which caused them show a reduction in load (guessing maybe stopping doing a process multiple times and/or caching results) and engine was stopped from running whilst project was still loading. I think there was also some finetuning of the plugin multithreading feature to change the logic of when it applied, which really improved things for low latency users particularly. The biggest impact for me was actually the fix for threads being blocked. I'm with you on loving to know the technical details, so perhaps Noel might share more in due course, if not confidential or super fiddly to explain :) Edit: He already has

How's the drive compressed exactly? Some algorithms can be not great for performance. I wouldn't have said compressing a whole drive was a good idea these days if it can be avoided. This tool however is one I find quite useful as it uses a lightweight mechanism and ignores files that wouldn't benefit: https://github.com/Freaky/Compactor Maybe if you're unsure or using another one I'd try and uncompress or swap to this as a lower cost impact. How long are you leaving the hang for? Are you unable to load any files?