Howard B

Thank for responding Amberwolf Sorry, I meant to say "close" the project windows...not delete them. Poor choice of wording. I guess I was kind of in Playlist Editor mode and was thinking in terms of adding and deleting songs from the playlist/desktop within Cakewalk. I just went through the entire thread and read every comment a little more closely. Regarding the asterisk showing up beside each played song rendering it "unsaved" while progressing through songs in the playlist: I see there is the option to "discard project changes during playback" which I am assuming is either supposed to stop that dialog box from popping up and asking the user whether they want to save each file during playback or to just ignore it in the background. I don't have a problem with this save dialog popping up while using the playlist but each song is still being rendered "unsaved" as soon as it loads as I go through them in the playlist. This isn't a problem while using the playlist but when I'm finished that song and want to close the project it's still popping up the dialog box. The easiest thing for me to do is just close each project before I start the next song in the playlist and click "no" when the prompt pops up. If I don't and wait until the set is over I'm met with a more time consuming issue. Each of my songs has sysex for my JV80 and Halion Sonic 7 as a plugin VST handler. It takes approximately 12 seconds for all this data to send and set up when a project is loaded. If I wait until the end of my set (playlist) to close all the loaded programs I have to wait 12 seconds to close each one because with each closure the song behind it becomes active on the cakewalk desktop and sends the sysex and loads Halion S7 for that song. This is not too big of a deal and I have been able to delete a couple at a time if I hurry while the sysex is sending and before the next one gets a chance to execute. Again, it's definitely better to just do it as I progress through the playlist and not wait until the end. I would like to know what "discard project changes during playback" is intended to do...ignore it or stop it. It would be nice if the dialog box didn't pop up at all in the Playlist Editor. I initially said that I do not touch the projects while in playlist mode but that's not accurate. Since I am using Halion Sonic 7 as a VST plugin handler I am making volume changes on my midi controller periodically while performing which would definitely cause a change in the program however each song is being rendered unsaved straight away before I even touch my controller. It might have something to do with the sysex echoing through my JV80 and signaling those changes. I'm going to look into that next.

Hi All...5 years later. c:\Users\<username>\AppData\Roaming\Cakewalk\Cakewalk Core\TTSseq.ini Make sure to add the line "SendLocalOff=0" under "Options" otherwise it won't work. I put it at the end and it didn't work so I moved the line to the first position above everything right under "Options" and now booting up Cakewalk no longer turns the local off in my keyboard.

Hi everyone...6 years later and I am having this issue now. I'm setting up for a live performance gig and each song stays open in the background as I progress through my setlist (playlist editor). My songs don't have any midi data. Only sysex to set up my Roland JV80 and I'm using Steinberg's Halion Sonic 7 to load patches. Everything is working great. The sysex gets sent to my JV80 setting it up for each song and Halion is loading up patches perfectly. I don't even touch Cakewalk as I progress through the playlist but each song project gets an asterisk beside it and sits in the background as I progress through the list. I used to use Cakewalk 3.0 back in the early 90s to play my *.wrk files for my solo act. Pretty much the same setup I am setting up with now minus the Halion Sonic 7 plugin. I remember this issue back then though I'm not sure if I found a fix or just got used to closing each song before the next one started. I might have just deleted them all at the end of my set since they were pretty small. Unfortunately Halion Sonic 7 uses more memory so I'm pretty sure it will not be a good thing to have a dozen songs with plugins sitting in the background during the last few tunes in my set. Has anyone come up with a solution for this conundrum? I guess I'm just going to have to get used to deleting each song as it finishes and before I start the next. I'm still hopeful there is a solution out there. I wonder if a CAL script could solve this issue? I really like Cakewalk. It was my first computer based music program after recording to tape all through the 80s and I just kept on using in my studio through the decades. I'm using again now because as someone mentioned above...it's the only DAW with a playlist. At least the only one I know about and that works for what I'm using it for. I hope you're all doing well and still playing.

Yes, thank you, I just figured that out and was able to enable it (and just now realized it doesn't stay on). I'm trying to work out if there is a way to close previously played files in the playlist. I'm setting up for live performances so each of my projects only have sysex data for my JV-80 and has Halion Sonic 7 as a plugin. As I advance through my playlist it's leaving each song on the cakewalk desktop. Even though they are not fully open I'm assuming they are utilizing memory with every new song that gets loaded. That was why I wanted to check off the "allow only one project at a time" box. I seem to remember having this issue way back when I used CW 3.0 to play my backing tracks as a solo. I can't remember if I came up with a solution or just closed each song as they completed.

I am having the opposite of this issue. I am using the playlist editor for live performance but Cakewalk is keeping multiple projects open as I progress through my playlist. I have my songs set up with Halion Sonic 7 and there is no midi data or note data in my projects. They is only sysex data to send to my Roland JV-80 and the Halion Sonic 7 patches that I play with a controller. The songs are advancing correctly. All sysex data is correctly being sent to my JV80 at the beginning of each song and Halion Sonic 7 is setting up correctly as well but when a new song starts the previous song is remaining open in the background even though I've checked the box to only allow one project at a time. I've just started setting up my playlist so it may be that once I progress to the third song the first one might close but I'm kind of doubting that will be the case. I remember having this issue years ago when I was playing a solo act with WRK files but I'm pretty sure I fixed the issue. I don't remember what the fix was or if it would even apply to this version of Cakewalk (I was using version 3.0 back then)

How can I enable this option? I am running a playlist for live performance but Cakewalk is keeping every song in my playlist open which is a strain on my CPU potentially slowing down the advancement from one song to the next. Is there a way to enable this option? Any help will be greatly appreciated

For anyone still having this issue in 2025 (I did) the fix that worked for me was to... go through each Microsoft Visual C++ *.* Redistributable right click on each one and choose "Change" and then "Repair" Some require restarting windows. I restarted after each one. Probably unnecessary but that what my OCD told me to do 😉

I loaded Cakewalk Pro Audio 9 and it worked but I made the mistake of loading the Direct Show 5 and that messed up my system some. Luckily I was able to backup to the previous day and all was back to normal. So CW PA9 works and all but it would only recognize 4 of the inputs on the US-1800. That's pretty much a deal breaker so I just went ahead and loaded up Sonar X3 PE and it's working great so far. I'm actually right in the middle of seeing what this old W7 machine can do. I'm going to try and record 12 tracks at 24 bit 48kHz for 10 minutes and if I don't get any pops or dropouts I'll give 96kHz a try. I'll be happy with 48 but I gotta try 96 just to see

AThanks Giorgio When monitoring the Steinberg by having the mix knob all the way left it monitors input 1 & 2 as individual mono inputs so they're both centered since there's no panning on the UR22 mkII I found another post on the Steinberg forum page regarding the same issue and they also suggested monitoring through the daw to hear 1 & 2 as live stereo but to expect a bit of latency. I just bought an A&H zed-24 console to run all my synths, samplers and drum modules through so I think I'm going to try monitoring the Steinberg back through the board instead of directly from the interface. For years I just used a two channel interface to monitor my audio source and playback from my DAW but now that I have the board I guess it makes more sense to monitor my audio and playback from the interface all on the board.

5 years later but I'm hoping the OP or someone else might be able to help. I had very similar issue with the Steinberg. Same interface as the OP (Steinberg UR22 mkII). The problem I'm having is I actually can't monitor my gear in stereo. I can only hear mono while recording. The tracks play back in stereo as I'm recording to two tracks panned left and right but I can't hear the stereo until after I've recorded the track. In Cakewalks preferences the only choice under devices is "Yamaha Steinberg USB ASIO UR22mkII Input 1" for input and "Yamaha Steinberg USB ASIO UR22mk II Output 1/L" for output. I would have expected an Output 1/R but there is not. My older interfaces always had both. I'd really like to be able to monitor my synths in stereo. Any suggestions would be greatly appreciated.

Many Years Later... So I have set up an older Zotac computer with 4 GB of RAM & Windows 7 just for recording straight up tracks off the floor in a room away from my studio. I don't need any plugin effects. Just the ability to record twelve to sixteen 24 bit 48 kHz tracks so I can then transport the tracks back to my studio computer and continue working on the songs from there. My thought is that an older version of CW or bandlab might be a lighter program for this older 4 GB machine. So my question is, which of the past versions would be best suited for the job? Back in the 90s (I know...old dude lol) I was recording on a Pentium 1 with 128 MB ? of RAM using Cakewalk 9 (Windows 98 Second Edition). I mean I would just use CW9 to capture the tracks but I don't believe it will work on Win 7 (though I'm tempted to try it). If I was able to capture tracks on an old machine with such limited RAM and a light duty DAW then it should run like a top on a 4 GB newer system. As I said though it'll probably need to be a newer version. I'm just spit balling here so any input would be appreciated. Thanks in Advance