Starship Krupa

The confusion usually comes when controlling things other than keyboard-style instruments with MIDI. MIDI doesn't know anything about musical notes. Its job is to send numbers. When those numbers are sent to pitched instruments, the sounds that come out by default to a standard set of pitches. But they don't have to, MIDI "note" 53 can be interpreted as "toggle that spotlight on and off," or it can be interpreted as "play a closed hi-hat sample." In GM drums, 36 and 38 are "bass drum" and "snare drum." It's this way because some people sat down and probably decided it would work pretty well with keyboard controllers. "Bass drum" and "snare drum" are not C1 and D1 or C2 and D2 or C and D anything. So, send a number, get a pitch. That's how two synthesizers can talk to each other without running into trouble with octaves: they are just sending numbers, they're not sending "C#" or any other note. Trouble starts to happen once we assign other names to a pitch, calling it "D2" or "C3," or whatever. MIDI knows the number for "the A above middle C" because "the A above middle C" is a pitch, 440Hz. So when I think about MIDI in theory, and when trying to control things that are not piano-like, I find it best to just think in terms of numbers. My sequencer puts out a 36 for a kick drum, so whatever's listening, I should set that up so that it, too thinks 36 is a kick drum. Breaktweaker switches gestures with certain MIDI notes (which are just numbers), so it's up to me to keep Breaktweaker happy by sending it the right numbers. In practice, what I wind up doing when I run into trouble is using Cakewalk's Transpose MIDI effect and setting it to either +12 or -12. First I try one, then the other. In the case of Breaktweaker, I think I had to set it to 24, because Breaktweaker was way off. I could sit down and figure it all out every time I run into problems, but it's way faster to just do trial-and-error and then possibly make a template or note as to which device or soft synth needs what transposition. Or just trial-and-error it every time. If I relearned it every time and and figured it all out I'd probably still have the same chance of getting it right. With the Transposer, I have a 1-in-2 chance of getting it right the first time, and a 1-in-1 chance of hitting it the second time, so it's much faster, and I can get on with making music rather than doing math. If there were a "culprit" and we figured out who it was, Cakewalk, Studio One, or Addictive Drums, we could post a message on the corresponding forum for their developers to ignore and still have to Transpose our way out of it. (Dr. Laurence Peter refers to this tactic as doing a "Peter Polka" around a problem: I realize that I'm not likely to understand or remember it using my usual methods of understanding and remembering things, and trial and error with Transpose takes about 15 seconds per incident, so the cost:benefit ratio is in favor of Transpose. Frees up my brain for other uses, and who knows, maybe the insight will come to me in the shower, as insights often do.) The other corrective measure would be to use a custom drum map. My struggles with Cakewalk's Drum Map are the stuff of legend, so I avoid it unless I'm up for a laugh. Another tried-and-true method is to put sticky notes or board tape above your controller keys.

Because that's the dominant color of the giant mecha whose color scheme inspired the theme, and I like purple, sometimes. It's not necessarily intended to be an everyday workhorse theme (unless that floats your boat). Rather it's something I switch to when I want exciting colors, same as my other "fun" theme, Yellow Submarine. When I want a theme that fades more into the background, I use Racing Green. What color(s) would you prefer?

As for solutions, I'll just go with the reminder to make sure that if you're coming in with a big sustained chord, that note-on for that pup better be inside your punch region. It seemed like there was something weird going on, but it was late and when I tried it in a brand new project it worked perfectly so whatever. For this task I'm more inclined to do it using other methods, like setting up a loop and hitting record and let the clips pile up, but in this case I thought I'd try the punch-in feature because it's something I rarely use. I wanted to make sure I knew how to use it, wanted to see if it's easier than doing it the way I usually do.

About an issue that's still an issue.

This forum is for Cakewalk by BandLab.

I can't afford Omnisphere, so I use Hybrid 3. It's about 1/100th the price.

You can still exchange your dollars for gold if you want to.

I'm now on day 2 of trying to punch in an organ part, an 8 bar chorus, one-handed block chords. Loop recording multiple takes of MIDI has been a fraught process for me since I first tried it with Cakewalk, but I figured I have a lot more experience with the program now, so I'd give it a try. This is a screenshot of part of the results of this attempt. I'm not going to talk about the territory around this clip looking like the aftermath of the Battle of Gettysburg, that's for another time, after the combatants have had a chance to heal. I just want to focus on this one clip, which is indicated inside the red ellipse: This clip is part of one of a dozen or so takes. It's in a "selected" state. none of the other lanes are solo'd, but the track itself is. Over in the Inspector, you can see that I've set the foreground to orange and the background to blue. My issue with this clip is that I can't get it to play sound no matter what I try. "K" or right-click to mute/unmute, no go. Soloing the lane, nope. It. Just. Won't. Sound. There's not another clip on top of it or underneath it, I know to check for that. It's just sitting there by itself, with notes in it that won't play. I can play the onscreen keyboard and my MIDI controller and it makes a sound, I can un mute the clips in adjacent lanes and they will play, but just not this one for whatever reason. Notice it looks weird for a non-muted clip in the Mercury theme: the background is correct, it's the light grey that indicates a selected clip, but the MIDI data/events are plain white. In its selected state the data should have the foreground color. Unselected, it should obey both color settings. If I hit "K" to mute it, it takes on the look of other muted clips, but in its (supposedly) un-muted state, the color ain't right. Any ideas, what may have caused this, did I put it in some known locked state by accident? This is unfortunately characteristic of my life with MIDI in Cakewalk: it usually goes smoothly (except for the weird loop recording/clip behavior), but about 33% of the time I lose an hour or more to "this one thing," which is sometimes a MIDI track and a synth track that have stopped communicating and nothing I do will bring them back together so I wind up saving the synth's settings as a preset, then deleting it and adding it back, or somehow during the process of recording and editing I end up with an extra clip entirely overlapping and hiding another clip, or I can't get the editing cursor to grab the edge of the clip or change to the tool I want, or something that brings my project to a halt while I untangle the ball of yarn. It could be 100% pilot error, but I'd at least like to know what I'm doing wrong.

That's strange, as if there's some spurious automation. Are you using an external control surface?

I've been writing up a list of suggestions for beginners, and I think defining a goal is important. What am I going for with this? That's why the pop culture vibe works for me: I want it to look like the dashboard of a sports car, or a favorite album cover, or an anime franchise. Picking something that already has a color scheme that I find appealing. Along with that comes defining half a dozen colors and making a note of their hex numbers. Racing Green is comparatively easy in that regard, it's 3 shades of green, Tungsten dark brown, and black. It was once I got away from my menus being light text on a virtually black background that things got way stickier. If your menu images and borders are light grey or dark, you can choose a single contrast color and be done with it. If on the other hand your menus are purple, blue, or yellow, then you need to find a color that's readable on that, which ain't always easy. You always want to have that list of colors at hand for when you find yet another UI element that needs to be changed to fit your theme. Otherwise, you wind up eyeballing it, which can result in inconsistency.

TBProAudio make a freeware loudness meter that is a powerhouse, dpMeter5. There's also one in the Meldaproduction FreeFX Bundle. I'm trying to understand this process. When you say you tried using the "W" feature, do you mean you tried to write automation for EQ and Maximizer parameters in real time, but your computer couldn't handle it? It sounds like you're doing might also be accomplished with track freezing? Maybe not, I'm not sure exactly why you need to take the files outside Cakewalk then bring them back in to do this.

(note: I'm not using the metronome and there are also 0 count-in measures set, so I'm pretty certain that's not the issue) Scenario is that I'm trying to punch in a chorus, recording a sustained block chord organ part to MIDI. The chorus begins at measure 19 so I set my punch-in to 19:01:000. Chorus ends at measure 29, so I set my punch-out to 30:01:000 to give myself a bit of overlap if necessary. I'm also looping it, and set my loop points to 17:01:000 and 30:01:000. Starting early so that I can drop into the groove and ending late in case I need to overlap. What's happening is that I start playing, but my playing doesn't start getting recorded until I get a full measure into the chorus. What I suspect is causing this is that I'm playing sustained notes and am rushing (see "not using the metronome" above), so starting them before the punch-in. Although I can hear notes sounding, my note-ons aren't getting recorded; it's not until I lift and go to the next chord that it sees note-ons. Sound likely? If that's the issue, let this function as a public service announcement: when punching in a MIDI performance, set your punch point a quarter note or so ahead of where you think you're going to start playing so that sustained notes don't get lost.

Perhaps not though, I have a memory that it was completely eliminated a couple of years back and then was returned for the Smart and Move tools after protests from the userbase. I don't remember why it's only for those two tools, of if there was a reason.

Something that has long bothered me is how when I have View/Show Clip Outlines enabled in the Piano Roll View, there would be shading for clips, but no indication where one clip left off and the other started. By accident, I discovered a way to tell clips on the same track apart from each other. It may be obvious to others, but it took me 3 years of using this program to stumble on it, so maybe not everyone knows. First, ain't this lovely? That's a single track with the clips showing up in different colors. Great for working with linked clips or just to know where one leaves off and the other starts. How to do it? It's the Inspector. Just select the clip you want to color, open the Inspector, click on the "Clip" tab at the top, and choose a Background color. The background color you choose for each clip will show up in the Piano Roll View. That's all there is to it. It may look a little different on your screen depending on whether you're using a custom theme. My themes use dark backgrounds for selected clips. I hope this helps someone, it's really helped me with keeping track of clips in the PRV. It also helps distinguish them in Track View. Foreground color will change the color of the data, or events in the clips but only in Track View.

They do look effn' cool, and that's a good thing for when someone's looking over your shoulder and wondering what that intriguing DAW is. Not surprising for someone as into CbB theming as I am, I'm really into how visuals can be inspiring, and this does it. For anyone wondering how to set their colors up, drop into the UI Themes subforum and see what we've worked out with Custom Color sets. Custom Colors is the only way to change the vertical lines in Track View, so it's important and powerful. The standard lines are too faint for my taste.

BTW @Glenn Stanton, I'm kinda interested to hear what "Watch All The Longtower" sounds like. Makes me wonder if you have a song called "Rock From The Third Sun."

I think you mean "set Now Time" in Cakewalk terminology. I'm with you on this. The behavior has changed a bit over the years, but I'm still reflexively clicking down in the whitespace with the wrong tool. I'm not sure what the rationale is for limiting it to the Smart Tool and Move Tool. I'm just as likely (if not more) to want to position the Now Time when I'm using the Select, Edit, and Draw Tools, so why not?

Yellow Submarine has been updated with more fun. More round buttons!

EVA 01 has been updated with round buttons (images are from Yellow Submarine, which has been similarly updated):

Even after having done all this testing and writing it up, there's still trial and error. It just started to bug me that my button images for the FX rack didn't match up. My choice for indicating ACT focus would be a simple on/off "light" rather than changing the appearance of half a dozen different images, but I don't think this was designed with end-user theming in mind. It's great that it went that way.

FX Rack gets my nomination for being the section with the most complexity. In addition to the stuff I already went over, there's also the matter of the bypass and show rack buttons on either side, which add 8 images to the stew pot. There are 4 conditions, which are active (no ACT Focus), bypassed (no ACT Focus), active (with ACT Focus), and bypassed (with ACT Focus). Fortunately, their behavior is consistent across all the conditions, for both the Bypass Plug-in and Show Rack Menu Drop-down buttons. One confusing quirk is the naming of the Bypass Plug-in images: The Bypass Plug-in image is used in the plug-in's active state, with no control surface enabled. When the Bypass button is hovered, it uses Cell 3. When the center of the Open UI button is hovered, it uses Cell 1. When the Bypass button is pressed, it uses Cell 2. Confusingly named,, the Bypass Plug-in Enabled image is used when the plug-in is bypassed. The cells are used same as described for Bypass Plug-in above. All other images follow the above behavior: hover button=Cell 3, hover center=Cell 1, pressed=Cell 2. Fortunately there are no curveballs when the center image is pressed. Of course, if you have a controller enabled, if you press the center, all buttons switch over to the ACT Focus versions. What this means in terms of use of the other images is that you can do things like matching the color of the buttons that appear in the center hovered condition. I just poke around at the buttons and see if anything looks jarring.

I just spent some time (time that I will never get back) with the images and colors in FX Rack. Here's what I found. With no control surface enabled and the effect in its active, non-bypassed state Normal: FX Rack/Name Background cell 1 Hovered: FX Rack/Open Plug-in UI cell 3 Pressed: FX Rack/Open Plug-in UI cell 2 Hovering the Bypass or Show Rack Menu button: FX Rack/Open Plug-in UI cell 1 With no control surface enabled and the effect in its bypassed state Normal: FX Rack/Name Background cell 2 Hovered: FX Rack/Open Plug-in UI Bypassed cell 3 Pressed: FX Rack/Open Plug-in UI Bypassed cell 2 Hovering the Bypass or Show Rack Menu button: FX Rack/Open Plug-in UI Bypassed cell 1 This is pretty much as expected. Things get more complicated when we enable a control surface. Once a control surface is enabled, there is another condition a plug-in effect can be in, which is having focus for the purposes of controlling it with the surface. A plug-in gets focus by having its UI opened, and keeps focus until the next plug-in UI is opened. I'll start with a plug-in that does not have what I'll call "ACT Focus." With a control surface enabled and the effect in its active, non-bypassed state Normal: FX Rack/Name Background cell 1 Hovered: FX Rack/Open Plug-in UI cell 3 Pressed: FX Rack/Open Plug-in UI (ACT Focus) cell 2 Hovering the Bypass or Show Rack Menu button: FX Rack/Open Plug-in UI cell 1 With a control surface enabled and the effect in its bypassed state Normal: FX Rack/Name Background cell 2 Hovered: FX Rack/Open Plug-in UI Bypassed cell 3 Pressed: FX Rack/Open Plug-in UI (ACT Focus) cell 2 Hovering the Bypass or Show Rack Menu button: FX Rack/Open Plug-in UI Bypassed cell 1 When the plug-in has ACT Focus, the behavior changes again as follows: With ACT Focus and the effect in its active state Normal: FX Rack/Name Background (ACT Focus) cell 1 Hovered: FX Rack/Open Plug-in UI (ACT Focus) cell 3 Pressed: FX Rack/Open Plug-in UI (ACT Focus) cell 2 Hovering the Bypass or Show Rack Menu button: FX Rack/Open Plug-in UI (ACT Focus) cell 1 With ACT Focus and the effect in its bypassed state Normal: FX Rack/Name Background (ACT Focus) cell 2 Hovered: FX Rack/Open Plug-in UI Bypassed (ACT Focus) cell 3 Pressed: FX Rack/Open Plug-in UI Bypassed (ACT Focus) cell 2 Hovering the Bypass or Show Rack Menu button: FX Rack/Open Plug-in UI Bypassed (ACT Focus) cell 1 Since these images are used as backgrounds for the text colors FX Rack/FX Name and FXRack/Bypassed FX Name, care should be taken to make sure that whatever image is currently displayed should go well with those colors.

Amendment to this observation: it apparently does have to do with ACT in that the behavior is only exhibited when I have a control surface enabled. So, in a revised nutshell, the images didn't have any effect until I plugged in my controller and enabled it as a control surface. As such, it's a useful indicator.

I have some more information on Control Bar/Menu Button's use in Tools/HUD Module (Large). Cell 1 is used when the Smart Tool or Draw Tool are not selected. This cell should be a color that will contrast well with the "default" white text color. Cell 2 is used on the HUD in that odd case where after you click on the duration menu, it flashes briefly as the HUD closes. It also acts as a "pressed" state button in the case where you have neither the Smart nor Draw Tool selected, but press on it. A brief flash again. Cell 3 is not used. Cell 4 is used when the Smart or Draw Tools are selected (which is appropriate, because note duration is meaningless for tools that don't draw notes). It should be given a color that contrasts well with Focused Track Text. For whatever reason, the HUD uses Cell 1 for the Smart Tool. Cell 5 has the usual Control Bar cell 5 duty of getting displayed when no project is loaded.

Note of caution: I downloaded this and checked within and the newest date on any of the files is August, 2018. This means that the themes will not be compatible with the current release of Cakewalk by BandLab.