Terry Kelley

John's point is important but as far as transmitters what doesn't look promising? I've bought three different transmitters and they all work. Charge, input music, connect, listen. It is challenging to connect with devices that don't have a display so you know what you are connecting to. None that I have use a PIN though. I use one to listen to the output of Cakewalk via my headphone jack when I am doing other things. Works fine. I would never attempt to record with it unless I planned on doing a lot of time sliding. The delay is at least 50ms

That's something I noticed about the Casio - the huge about of data it dumps out when you are playing.

Latency Monitor never showed any issue even when the noise/glitching was happening. But certainly, if it's complaining, fix it.

Watch for Casio MG-500/510 Midi Guitars. I have one and it tracks pretty dang well.

Glad you posted this! I had been periodically having glitch/stutter issues using certain plugins like MUnison and MHarmonizerMB. Things would be fine and then go south and back to fine. I was going through Preferences looking for something else one day and noticed Read Cache was enabled. I don't recall setting it but I might have in frustration trying to fix a problem. So I disabled it. I haven't had an issue since. I read the manual and some comments from people about why it happens but never found a satisfying answer. I don't know if cache was taking too long to fetch, fetching the wrong stuff and having to flush or what ...

Sadly CW doesn't support that resolution!

One of the developers commented sometime back that the ASIO settings aren't always available to Cakewalk to allow you to set via Preferences/ASIO Settings. I can change my M-audio interface via Preferences but not the Presonus - I have to run the external program. So the "ease" of getting to the settings will vary depending on the interface.

That's what I would suggest. Transpose and check the Transpose Audio box. Raise it 1.

Thanks Noel, Looking at the dates for the versions, the first project version was on 11/05/21 and I added the side-chain on 11/08/21. I follow the EA's closely and I show I got EA 27.11.0. .034 on 11/1/21. I was definitely on an EA when I started. I am guessing .034 since I usually install the latest EA when it comes out. Any way you can tell me where this solo in the side-chain is? I'm looking at the project and I have the bass side-chained to the bass drum but nothing shows any soloing. Maybe that's what you mean by "internal" - I can't access it. I'm not sure I know enough to recreate it at this point. Since it works in 2021.11.018 I'm not sure what to try. But hey, I'll try anything once. I might just need to chalk it up to a fluctuation in the aether. Terry

Each note is 5.9463063094359295% (12th root of 2) above the last. That will give you a rough speedup percent.

That's why I don't report every single issue. I might toss out some observation (hey, anybody else notice this?) but just because it went goofy on me doesn't mean it's definitely Cakewalk. I just close the program, reboot or maybe change a setting and see what happens. More often than not the issue goes away or disappears until what ever combinations of things I did make it reappear. If I can narrow it down, then I might bring it up directly with the developers. Sometimes I actually find something but more often - I haven't. Real bugs will generally be reported by people with a diverse set of hardware/OS. At that point the developers jump on it.

Cakewalk can't accommodate every mood our computers get into. Sometimes a reboot is just needed and you move on.

Yeah! And thanks for pointing out I'm an idiot! I read the manual and never saw it but maybe it pays to browse the shortcuts and see if one describes what I am looking for - first. Where's Bdickens when I need him ...

I dunno but 2021.11 appears to be doing some weird stuff. They'll sort it out. I do get that a DAW is expected to deal with a lot of HW uncertainty. They can't account for every config we throw at it.

While I will whisper it's name (V-Vocal), 2021.11 is creating blank regions like bouncing the clip does. So does Vocal Sync.

Hi Noel, I sent you a link in an IM to a problem file. I notice two things: It will only play in older versions if you solo tracks and bouncing a clip gives an empty clip. This file was created with 2021.11 (015 and 018) Terry

Hi Noel, Yes, I sent him a bundle, he opened it and it wouldn't show any meter activity on any track that wasn't solo'd. At first we thought it might be some hidden track (as suggested here) or something with the master buss. He toggled the global solo button several times. He also rebooted a couple of times. After messing for around 30 minutes I told him to update since I knew he was behind a bit on updates. Bang, it worked. He was on the 2011.06 version. I'll pull up the trouble version.

Maybe it's the wording but the issue isn't solo'd projects it's that you can't play them without soloing the tracks. Still, I'll take the improvements of 11(015). Terry

I'm bumping this since it seems weird right up until it happened to me. Something is afoot at the Circle K.

I use the Sonitus delay a lot. I was looking through my Melda stuff and a delay isn't part of their free/limited package.

I notice that when I go to select measures for punch-in/copy, etc. , there isn't any highlighting in the tracks below until you set both markers. At that point the shadow shows up. It would be nice if just selecting a measure point (start or stop) would have a line that goes down through the tracks so we can accurate position the markers. Once the shadow does appear you check if you got it right but any adjust doesn't change the shadow position until you release the mouse button - if that makes any sense. I'll try a short video to demonstrate. It would be similar to the Now marker line that extends down through the tracks. I did read through the manual to see if there was some setting but didn't find anything in the marker sections of the various functions.

I am on the latest version ( 015.) A buddy tried to play a song I did on this newest version and just ran into this problem. He had to update to 015 to get it to play without soloing. His version was a couple of months old and I asked him to try and remember. All he remembers is is was a a June version. This implies the newest version is creating files the older versions can't read correct. He had the exact same issue as the OP.

Up above the track list is Options. In there is Track Manager.

My understanding is that CW will update recent only on a successful program project/ file close. A crash isn't a close. I recall reading they already understood this. Maybe I'll submit it as a feature change at some point. Edit, I should have said project/file close, not program.

Right, if I was using versioning I could do that. What I want is for any file that is save to be placed in the recent window and not be dependent on a successful exit of the program to show up. I can save the file, have Cakewalk crash and it won't be in the recent window. Minor and not worth pursuing.