jkoseattle

All right, well I'm moving on, thanks for all the help. fwiw I followed a lot more closely to your video than you seem to think. BUT... I did NOT set the output channels. That was the problem. As is the case for 92% of all problems in my entire life, it turns out to be my screw up. However, constructive criticism: If you are going to scold someone for not following your video properly, might want to ask why that might be. This stuff is hard, man! I've been using CW as my DAW exclusively for 32 years, and I still only know what about half of the features do it seems.

@John Vere OK so I really am trying to get this multichannel e thing working, but I'm running out of patience. Now I've learned than adding an Audio FX to a track operates on all tracks associated with that instance, regardless of channel. So, how do I get around this?

Semi-related: In the Insert Soft Synths Options dialog, I have it set to Instrument Track Per Output. So - Why isn't there a way to name the soft synth right here, so I don't then have to go manually change every created track??? And why do the instances all HAVE TO HAVE a number after them, even when I rename it?

Well I can tell you that I was working on a new technique, wherein I load multiple instruments into a single Play instance, and assign them to different channels rather than load a bunch of separate Play instances. Having dismissed the Insert Soft Synth dialog long ago, I wasn't getting separate tracks for each instrument, so was making them manually by choosing "Append Instrument Track" off the track initially created with the synth, and just changing out the Midi channels. So there was probably a bunch of experimentation going on in that realm. I would strongly suspect something I did in that area would be the culprit, if that helps at all.

@Noel Borthwick No, I just started it last week. As it turns out, I've been re-recording the few parts I've gotten done and I like these new performances better anyway :-). But it sure would be nice to know what caused it so I can not worry about it anymore.

.

@Noel Borthwick Project file is included in previous post. I updated last week at some time, and after I was having the problems, updated to the latest again this morning. Same issue both versions.

@msmcleod I've only got a handful of instances, and have used many more than that in previous successful projects. What's different with this one is this is the first time I'm adding multiple instruments to a single EastWest Play instance and setting them to different Midi channels. I am trying to recreate my project atm because I wonder if this project is corrupt. Specs here, project file attached. Device name JIM-SURFACE Processor Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz 1.50 GHz Installed RAM 16.0 GB (15.6 GB usable) Device ID 0CE4C994-68F9-4C76-892D-5A40B403AF26 Product ID 00342-23734-03541-AAOEM System type 64-bit operating system, x64-based processor Pen and touch Pen and touch support with 10 touch points Variations on an End CORRUPT.cwp

Also, Cakewalk is not completely crashing and terminating ALL THE TIME when I start playing around in Console. Something is seriously wrong here. And yes, I just installed the most recent update.

@John Vere Perhaps you can help withSince I have determined that my problems were not multichannel-related, I have organized my ensemble into just a handful of soft synth instances, setting each instrument to a different Midi channel. All's well. HOWEVER< I'm seeing this bizarre looking thing in the Console, where this mysterious strip is in place of the actual track 4's strip. What is that, and can't I get my regular strip back?

Here is the solution from EastWest support. Like I said, not multichannel at all: The long sounds in the Hollywood Orchestra rely on Midi CC data to set dynamics/timbre - Cakewalk has a very strange default that resets CC data to zero on playback so it makes the instrument disappear. Go to Cakewalk's Edit >> Preferences >> Project >> MIDI. The options to uncheck are called “Zero Controllers When Play Stops” and “MIDI Event Chase on Play”. Then reload your project once and you shouldn't have that issue going forward.

The problem is with the EastWest Play instrument. Has nothing to do with multichannel stuff. I load the instrument, plays great. Hot space to playback, as soon as playback is paused, instrument stops playing. So a different problem entirely.

Yeah, well that gets me back to the question of how to bring that dialog back! I have no option to choose multiple outputs lol!!

@John Vere I do think your video is clear enough as far as it goes. I am actually an instructional designer in my day job, so I can provide a little feedback from that perspective. Listing 9 different ways to do something is overwhelming. If they are essentially accomplishing the same results but through different methods, it would be much more effective to limit yourself to the couple that cover all the bases. Where appropriate you can mention "Oh by the way you can also accomplish this by doing such and such". If one unchecks "Ask This Every Time", then they're not going to get the dialog again. Explaining how to bring it back would be useful, especially for those users who may have unchecked it a long time ago, maybe back before they completely understood what they were doing. Such is the place I find myself. Lastly, the option is called "Append Instrument Track". When I add a soft synth, I get the single instrument track including both Midi and Audio. Right-clicking on that track affords me the option of Splitting the Instrument track, and then right beneath it, Appending Instrument Track. Appending just makes a new instrument track, from which as I understand it (which may be wrong) allows me to have multiple tracks that use the same soft synth. And then I can change the input channel of each track. Here is the UI for my soft synth: You can see on the right that I have two patches loaded, Cello Sus and Cello Short, and that each is assigned a different Midi channel. Here is the main track I originally created when inserting the cello soft synth, "Vc Long". You will see that the input is set to Midi channel 1 (not "None") I the right-clicked on Vc Long and selected Append Instrument Track. This created the track immediately below it, which I named Vc Short. For this track I set the input to channel 2, corresponding to the midi channel selected for the corresponding instrument in the soft synth also set to channel 2. My issue is that while at first this works great, and each track only plays the instrument loaded for that Midi channel, after a few minutes, the first one (Vc Long in this case) stops playing. I can record into both tracks, so oddly this is not a Midi input problem, but only the second of those two tracks can be heard. I hope this makes sense. Let me know if it's still not clear.

Thank you!! At some point I must have deselected the Ask This Every Time option because now I don't get it. How do I turn that back on? Also, the video explains what is going on under the hood, but doesn't really give me an idea why I'm having the aforementioned problem.

I am using a plugin which lets me load multiple instruments into a single instance. I have done this, and set each instrument to Midi channels 1 and 2 respectively. In CW I then Append Instrument Track, set the original track's input to channel 1 and the appended track's input to channel 2. This way, I can play off the single plugin instance but switch between sounds just by using different CW tracks. I am currently using this for a cello. One channel is arco, the other is pizz. But I can really see how useful this would be for building a drum kit from scratch, for instance, so I'm keen to figure this out. Couple questions: First off, this works great when I set it up. Then I'm playing around with it and maybe going to other tracks too, and every time, after a few minutes the channel 1 instrument no longer plays. It receives input fine, so I can record, but no playback. This is also true within the plugin's own window. Simply reloading the errant instrument immediately fixes it, but again, only lasts a couple minutes. This is true regardless of the instruments I am loading. It's always the original instrument, which I set to channel 1, and the appended track which is set to channel 2, continues working. What am I doing wrong here? Second question, while it seems intuitive that this is a better way to build my sounds, what's really the difference between doing it this way vs just inserting two separate instances of the plugin and not messing around with channels at all?

Hey, when recording in a loop, creating many takes in a single recording, didn't there used to be a way to tell CW to not play back the takes you just recorded? I distinctly remember creating my loop, then trying all sorts of different improvisational ideas within that loop, and only hearing them all played on top of each other if I stopped the recording and played it back without muting any takes. Today I'm trying to do that, but while recording, I am hearing all the other takes right away.

Well no, cheating is cheating! But I slow things down all the time because it's faster than doing take after take until you get it perfect. I CAN play it, but I don't have all the time in the world either. But that is my rule for auto-tuning vocals. I use it all the time to prevent wasting my vocal cords on 20 takes. If I COULD sing it, I am permitted to auto-tune myself. If not, then foul!!

If there's audio in there, CW doesn't mess with it unless you explicitly tell it to in the tempo dialog. Which means the audio will not match whatever tempo you changed to. I should have mentioned that when I am slowing down for recording (Midi), I often have to mute all audio tracks so they won't confuse me. And then I have to make DARN SURE when I restore the tempo again it's EXACTLY what it was before.

This new Tempo Map thing, while taking a little getting used to, is very elegant, and I love how familiar the envelope editing options are. Very nice job!! Goodbye and good riddance to that old tempo window!!! I will often need to record a passage at a slower tempo than it will be played at. Years ago there was this convenient feature where you had tempo offsets you could enable temporarily, but that feature seems to be long gone. So I have resorted to inserting a tempo change just for recording purposes, and then going back and removing it when recording was done. I'm thinking that since the team built this whole tempo made thing, that there must be some new best practice for this use case. So how do people normally handle it when they need to slow things down temporarily to record, but that's not a "real" tempo change?

Thanks so much!!! I will check this out. What with Themes and Workspaces and Layouts and Multidocks and palettes and modules, things can get pretty lost...

The dialog for changing individual colors of things needs a great deal of improvement. Any time I need to change the color of something, I grab a scotch and open the preferences color dialog and hope to god I can find the one I'm looking for. There are way way WAY too many of them (I ask you, how many of us need to change the color of the Clips Pane Ellipse....?), and the only way to effectively search for them is to try and GUESS what the developers decided to call it. And the stakes are pretty high. If I can't see something because it's the wrong color, I could end up making dumb mistakes, Add to that this bizarre combination of choosing the color itself, and then ALSO being able to change the hue, saturation, etc. It's terribly confusing. We've got shit to do here, please make this easy on us. All I want to do is mess with the vertical lines in PRV. Search for LINE or BEAT or whatever, and then you have to guess which it is, the only way to know is to drag sliders around, which then changes whatever wrong one you just changed.... NIGHTMARE! And before someone responds with "Just choose one of their supplied color palettes", well of course. But everyone has their own personal must-have, and while those palettes are a great starting point, I'm talking about when something in the palette is wrong enough that one needs to go adjust something. Is there some handy guide somewhere that indicates what things are called in the colors dialog?

Exactly the conclusion I came to as well.

What I've discovered after spending a bunch of time with this is that indeed, the mouse button assignments come and go, and I definitely don't think it's a Cakewalk issue at all now. 100% of the time I've tried this over the past few weeks, simply focus on any application other than Cakewalk, then click back into Cakewalk, and you have reset something and the mouse buttons work as designed again.

Oh, so I WAS using a Workspace. It's now set to None. I've also discovered a couple other things: When the Show/Hide Multidock keystroke is failing, ALL my assigned keystrokes are failing. It's just that I use the Show/Hide Multidock one a lot. I also learned that this problem is easily fixed by simply focusing any application other than CW and then clicking back into CW again. Weird. I'm suspecting now it has something to do with how my mouse buttons are interacting with CW, because hitting the keystroke itself always works, it's just the mouse buttons that fail. I just can never remember the keystrokes, and the mouse buttons are right there under my fingers.