Starship Krupa

So, Jerry, is thy Staff View once again a comfort to you? ?

This was a suggestion from the manual, they said if the DAW has the ability to do per-core plug-in load balancing that multiple instances will probably be less expensive. This has piqued my curiosity: if Omnisphere is able to use multiple cores and Cakewalk is able to do load balancing, I wonder how those two things affect each other. I mean, does Cakewalk's load balancing affect Omnisphere's engine's ability to access cores other than the one it gets assigned to, is Omnisphere going to use only that core?

Cakewalk by BandLab has no payware plug-ins, but this is a fine idea, especially when it comes to text legibility.

Yeah, that's what I picked up. After parsing it some more, it looked more like what he was trying to accomplish was a multitimbral setup. Was I correct on how to do a multitimbral setup? I only ever tried it once, with Xpand! and I couldn't get the second channel to make a sound. Out of curiosity I looked at Omnisphere's manual and they say that with DAW's that support multicore processing for plug-ins, it's actually a better strategy to just slap an instance on every channel where you're using it because the DAW will load balance more efficiently. So a multitimbral approach can be more expensive in a well-designed DAW like Cakewalk. That single instance of Omnisphere will be working twice as hard and on one core rather than cruising on two. Ah well, it's surely a useful thread for someone looking to get MIDI out from their plug-ins!

Lots of solid advice on how to enable MIDI output from plug-ins. I hope that it helps the OP achieve their goal of having sound on another channel without having to open Omnisphere again, and thereby conserve CPU resources. I'm not sure how merely enabling MIDI output is going to further either of those goals, though. Were it me, I would be investigating Omnisphere's multitimbral capabilities. That would satisfy the one criterion of not having to open another instance of Omnisphere, and it would allow for having notes on 2 channels. To do that, wouldn't they set up a single instance of Omnisphere on an Instrument Track, with 2 MIDI Tracks, each set to a different MIDI channel, and outputs set to the Omnisphere?

Background: There is a situation I find myself in on just about every project I do: when recording in Loop Mode, more than one guitar or vocal takes are keepers, and can be used for doubling, or in the case of vocals, sometimes the singer decides to have some fun and starts singing harmony lines, or whatever. Also, sometimes when comping and editing I want to "park" alternate takes for possible use later, and the most resource-friendly way to do that is to move them to another track and Archive the track. This is because Cakewalk streams all audio files associated with any clips in the project, even if they are muted. The only way to stop that is to put them in a track and archive the track. Feature Request: Similar to how we already have "Send to Folder" for Tracks, it would be great to have "Send to Track" for Lanes. This would allow me to select the takes I want and Send to Track, with the option to send to an existing track or create a new track. Then I can comp them into a backing vocal or archive them or whatever. The lanes would be deleted from the source track. This would be a very nice shortcut to the drag and drop way I do it now.

First, a sample rate of 192000 is high for a novice recordist. Even 88.2K or 96K are considered by most to be for use in special circumstances. A system with a Ryzen 3700x is likely to include other components that make it so you will be able to track with low latency. You don't say anything about the complexity of your project, how many plug-ins, etc., but I'll presume that since you mention "playing guitar" that you're trying to record audio, not MIDI with a virtual instrument. So the "delay" you describe occurs between when you sing or play a note and when you hear it in your monitors (or, likely, headphones). Okay, the thing to do is to set Cakewalk up to use ASIO Driver Mode in the Playback and Recording preferences. In the control panel for the Focusrite, set your recording sample rate to 44,100KHz/24 and 4mS. That should be plenty low enough latency at the interface level. Then try the following steps without adding any plug-in effects: Set up a small test project and first make sure you can play back audio in Cakewalk. Just drag an audio file from somewhere on your computer onto the Track View, and see if it plays back okay. If that works, plug in a mic, or plug your guitar in to the interface, and set up an audio track, and set the audio track to have that channel of the interface as its input. Click on the Monitor button on the track and see if you can hear the signal coming from the interface. At this point, if everything is working okay, you should be hearing your voice or guitar nice and crisp, with imperceptible or barely perceptible delay. If you can't hear yourself, something went wrong. Your system is powerful enough to run one track at 4mS. Make sure you're setting the correct input channel, phantom power is turned on, etc. If you're hearing enough delay to call it "delay," then make sure you don't have your interface plugged into an external hub or something. Whatever else you do, ASIO Driver Mode is the preferred setting for most efficient operation, so configure your system that way if possible.

If your 'revision" consisted of mix moves and edits, yeah, lesson learned, and now turn on autosave and versioning. If what you lost was recorded audio, all audio that Cakewalk records is immediately saved to disk no matter what else happens, whether it shows up as clips in the project or not, so you may be able to find your raw audio files if you look in your project's Audio folder.

Excellent. You're halfway home. Now install 64-bit versions of them and your system will be good to go.

You make a persuasive pitch. I'll help advocate for a worthy feature or bug fix even if it isn't that big a deal for me personally. I agree that Cakewalk should have a way to route to single I/O ports. If I have a dog in the fight, it would be my continuing bemusement regarding Cakewalk's delusion that, for instance, Input 2 on my interface is actually "Firepod 1 ASIO Input 1L/R." A designation you may notice doesn't actually carry the actual name of the input in it. I'm going to take a guess that "Right Analogue 5" is actually Input 6 of your Audient. This may seem like a trivial thing to some, but so far the confusing nomenclature has contributed to 3 instances of my failing to capture a track during drum tracking sessions (practice sessions all, so I wasn't being fully diligent, and it wasn't a critical performance), and then another embarrassing episode where I spent 5 very. long. minutes. tapping on a mic stand, clapping my hands, having the talent speak into a mic, cranking up the gain on the interface unable to figure out why the hell my mic sounded so thin and distant before realizing that it was the guitar amp mic on Input 2 (according to the paint on the front panel) not the vocal mic on Input 1 (according to the paint on the front panel) that I had assigned to the track's input and armed. Except for 1-2, and 9-10, the S/PDIF, none of the inputs or outputs on my interface is labeled or treated as a pair, but Cakewalk is like The Handmaid's Tale or something where all the inputs and outputs are divided up into pairs, and the odd ones define the pair's identity, and the even ones lose their identities. "You are not Input 2, in Cakewalk, you are Input 1R." So I'd settle for the darn things just being displayed correctly.?

Grr, I have interface envy. Much as I like my Firepods, got a heck of a deal on the pair of them, the original mixer software was written for Windows XP and is long abandoned. The next generation of the device came with the fancy software that would allow things like this to go on outside the DAW. So I must rely entirely on what the 'pods can do with their hardware, and getting low latency in the DAW, in order to monitor or use external gear. If PreSonus had ever made a program for it, or made the program backward compatible, it would be fine, but they didn't. At least the Windows 7 driver still works with Windows 10.

I appreciate that. I really do dislike it when people do that with the unspoken idea that I should suck it up because their pet DAW can "already do that." Yeah, if I stand on my head and tap dance with my elbows, sure. ? People make feature requests because they like the program and they want it to be better, they go to the trouble of writing it out. If they're polite, I try to be polite as well. Sometimes the program does actually have the feature already. BTW, my semi-hidden agenda here is to keep the dialog going so as to keep your topic up at the top. That's part of how feature requests get attention, is if they hang around for a while. The devs are busy devving, or if you please, the bakers are busy baking, so checking the forum is a secondary task. As chuckebaby says, your best hope is that altering the existing plug-in is a simple task. You mention "proper implementation." I'm not familiar with how it's done in other programs, I think I tried it out in Mixcraft and it wasn't done with a plug-in, it was similar to a hardware mixer insert. Is this what you mean? With all the high-powered routing that I can otherwise do in Cakewalk, it does seem kinda weird that the only way to get a signal out and back to an external processor while mixing is via a plug-in that assumes I want to eat up a stereo pair. It sounds like what chuckebaby says is true for pros who have interfaces with lots of I/O flexibility, but even my 8 input/8 output Firepods only have one pair that can be used for this purpose (I think). I know that there are plenty of home studio/bedroom producer people who are way into patching in funky old processors, even stompboxes for reamping and they may be using a 2 channel or 4 channel interface. Is this the issue with the people you know?

I myself dislike when people offer clumsy workarounds when a feature request is in order, and I fully agree with the feature request. Apologies if I didn't make that clear in my reply. My purpose with the workaround suggestion is to help anyone temporarily while the problem is addressed where we think it should be addressed, which is in Cakewalk.

Let me see if I understand it correctly, because I haven't tried patching in any external processors. Let's assume I want to use it with my @Craig Anderton PAiA Hot Springs Reverb, which would actually be my most likely scenario, as the Hot Springs is a favorite external processor. The Hot Springs is mono in, mono out, so I only need one output and one return from my 8-channel Firepod. The Firepod only actually has two channels that may be used in this way, if I recall, so they are "expensive." You're saying that if I assign the first output to the plug-in, I can't do anything else with the other one? That it's grabbed by the plug-in and may only be used on that channel. That does seem like a big waste of I/O, especially in situations like mine, where I only have two in the first place. Now before I say this, I will mention that I dislike it when people offer clumsy workarounds when a feature request is in order (with the implication that your feature request is unnecessary), and I fully agree with your feature request. Assuming that all external processors are stereo in/stereo out is incorrect and should be remedied, especially now, when so many people are using interfaces that only have 2 channels to play with in the first place. So. If the devs don't think this is worthy of their attention, or even if they do, it will take them time to implement it, I think I may have a workaround for people like us who don't like it: use Aux tracks. You can make multiple Aux tracks with the inputs set to mono left and right. Try creating 2 Aux tracks, putting the plug-in on Aux 1 and setting the inputs of the Aux tracks to Aux 1 left and Aux 1 right. Then use hard panned Sends from your tracks to Aux 1, depending on which processor you want to use. They should be returned to Aux 1 Left and Aux 1 Right, which can be routed anywhere you want. I haven't tried it in practice, but it might help, or something similar might work using a Bus.

It can help to zoom in to the end of the clip you are trying to trim until you get a feel for it. And what Mark said about "hit zones." Drag the width of your track down a bit to make for a larger target, easier to hit. Sometimes when editing, I like to switch to the Edit Tool rather than relying on the Smart Tool to obey my wishes. I'm editing, so why not use the Edit Tool? It can eliminate ambiguity. Those other tools are on there for a reason.

Really, Mark? What constructive purpose does it serve to say that so bluntly after the guy's been told where to find what he's looking for? I put he chances that the bakers are going to read what he said and then try to convince their bosses that what Cakewalk really needs in order to take off is a bundling agreement with a piano and/or organ VSTi developer (those being highly personal choices in the first place) at somewhere less than the chances of the Lyrics View getting a major makeover. He's not wrong, it would be a "great feature," to him. But I think that if he combs through the Freeware Instruments thread or even just tries the ones I suggested he'll end up an even happier Fred than if Cakewalk came with a piano or organ.

Maybe they can get Blondie to play "Rapture." Have you heard the National Lampoon Radio Hour tribute where they recreate the bit using '70's band names with a rock promoter and a venue manager? Predictably, The Who are on first....

More than just views. Huh. I was going by the Ref. Guide, but it seems like there's more to know. I just took another crack at Workspaces, with....undesired results. What I wanted to create was a Workspace for mixing on my laptop, so a single screen paradigm where the Multidock dominates the lower half of the screen with just enough Track view to see where I am in the piece. Only Control Bar modules that matter to mixing. No synth rack, no help. So I set all that up, saved the Workspace, exited, called up a template, applied the workspace, and blooey, it looked nothing like my screen did when I saved it, my Browser and Inspector were suddenly expanded, Track View dominated the screen, and the Console was scrunched down at the bottom. It had exactly the opposite effect I wanted, which is to say that when I called my template up, everything was orderly and ready to start work, but after I applied my custom workspace, I would have had to undo a bunch of clutter to get it to look like I wanted. For a thing that's supposed to provide convenience, it frankly takes less trouble to just make everything look like I want and save it as a template. At the moment, it strikes me as programming a robotic arm to move my desk chair to the exact spot that I want as opposed to just grabbing the back of the chair and moving it myself. Maybe my expectations are off-base, but if so, what is this feature for? Sorry for the thread hijack, I should have tried experimenting with the Toolbar state while I was at it.

Yes, yes, 1000X yes. From this point forward, if I were you I would check to make sure that any plug-ins you acquire are in the 64-bit format. And don't start any projects using old 32-bit plug-ins. BTW, re-reading this thread, I love the "Who's On First" bit that I play the Lou Costello role in with scook and others taking the Bud Abbott part.

I agree wholeheartedly and am surprised that it's not. Also glad to be forewarned.

Even the guy making the suggestion isn't 100% sure which one it is.?‍♂️ Maybe I'll change my handle to "Workspace Screenset" because those are the scariest two words in all of Cakewalkery. Like "Keyser Sose" in The Usual Suspects. Well, maybe not as scary as "Drum Map." Seriously, I would really like to get better at Workspaces, because I know how useful they can potentially be for me. But I think the last time I tried it exposed a bug, which was later fixed, and I haven't goten back to them since. I finally sorted out the difference between the two; screensets are just saving whatever state your views are in when you saved it in the various slots (right?). Although you can copy those between two open projects. So I guess if you had your Tool set to the Edit tool, that would be part of a Screenset. But it seems like using screensets across multiple projects is a hassle. Workspaces are more heavy duty, they let you streamline the interface and environment, optimize it for single screen workflow vs. dual monitor, specific tasks such as tracking vs. mixing, etc. They work across whatever project you choose to use them with.

Sampletank 4 Free CS for an excellent piano and CollaB3 (and Martinic Model V and Model F) for organ(s) and you have it covered and then some.

In the meantime, there are many 3rd-party freeware instruments of that type available. I just posted a link to CollaB3, a Hammond B3 clone that is free with submission of a valid email address,

I'm really pleased to be able to bump the thread with that rarest of creatures, a freeware Hammond B3 emulation that comes in 64-bit form. It's specially issued by Sampleson and other sponsors to be of help to musicians who are shut in due to the big health crisis: https://sampleson.com/collab3-free-tonewheel-organ.html I also somehow stumbled across a company called Fanan Team Pro who make some virtual instruments including Stringya, a string machine, and Clarinetica, an "ethnic clarinet instrument" that have UI's that must be seen to be believed. Not since Terry West have I seen such apparent attempts to emulate the slot machines at an off-the-Strip Las Vegas casino. Check them out if you're into unintentionally weird virtual instruments. The string machine has a 3-band "Trance Gate" as one of its built in effects. So if you've ever yearned for a trance gate in your string machine, they have you covered.

It sounds like the OP is starting with a download of CbB? The thrust of Maxim's post is kinda odd, as if the only plug-ins there are are ones that either currently ship with Cakewalk or once shipped with SONAR. TTS-1 has very little in common with Square I, TTS-1 is a GM ROMpler and Square I is a subtractive synth. Maxim doesn't want to use the ROMpler, so the next best thing is Square I? My standard recommendation for people who are tired of TTS-1 is first to try the secondary sounds in it, then plunk down $14.99 for a 2-seat license for Xpand!2, which is, as of now, the best deal in software arrangers, IMO. If only there were still software engineers around at SONiVAIR to give it a scalable UI.... Y'know, I know of this cool guy who collects once proud, now dead in the water MI brands.?If he could get Jordan on loan from Fishman....