Josh Wolfer

I'll take a video and upload to youtube so you can see the whole thing. Just a moment.

Please note my request to do it from the PRV, as that would be pretty great. Regarding your work around, It's mildly annoying since: Other controller data like the modwheel completely dominates the track PRV. No other instrument notes are overlayed. Not the worst thing in the world, but still not ideal for me. Working out of PRV would solve these. How do you record automation straight from my controller? I have a feeling this is something to do with ACT. Specifically, I'm using an NI s88 with the ribbon. If I select write automation on the lane (set to CC 11) and then touch the ribbon, it's not recorded to the automation lane: If I arm the instrument track and press record, it's obviously going to record it in the midi CC area of PRV, like I've been doing. How should I go about this? Thanks!

You're probably already aware of this, but on the latest and last release, if you adjust the END of an arranger track part, CW crashes. It doesn't do this if you move the start of an arrangement part. You'd think I'd learn by now to stop adjusting things during play back....

For example, I'd really like to be able to work out of PRV with all the context like this, but with nodes for CC automation:

Oh snap! This is indeed a great workaround! I wasn't aware of this short cut to switch track selection. THANKS!

@msmcleod I understand the differences between the track volume vs midi volume. Check out my screenshot where it has "(volume)" vs "volume". The prior controls nothing (but is what you get when you use the new '=' key bind) and the latter is the correct track volume. Happy to do a screen share and show you as well. I'm 99% certain that you will agree this is a bug. Also, fwiw, I'm doing this all from the main track view without doing anything from the Inspector module. I can reproduce it each time.

@msmcleod Thank you for the information. This has a few problems with the workflow: The CC information in PRV does not sync up with the Track view midi automation. This is especially problematic if I want to perform the CC from my midi controller. My NI s88 has a ribbon I've assigned to CC11 and it's great for recording a CC11 performance. But if I ever want to use Nodes as well as my performance, I now have 2 very different places I have to modify and keep track. Think of it like this: Just like automating faders with a control surface that has 100mm faders, I want to potentially start a CC11 performance on my midi controller, and then refine it via the nodes / curves automation style. The track view isn't a great place to set the CC automation. I would much rather set CC automation from PRV as it's a better view to look at the notes that are going on in the track I wish to modify, as well as other tracks for musical context. It's a lot easier to follow along.

I was waiting to add bass traps to re-analyze the frequencies. I need to do that now. I still have some cloud absorbers to put up, but that's final touches. After I do the analysis with bass traps (they're installed now), I'm going to finally turn on my sonarworks reference 4 tuning that I picked up a while ago. Should be the icing on the cake. I'm lucky enough to also be in an odd shaped room. It's not just big rectangle.

This, this, and more this. it happens all the time. At least there is a a right click - "revert to X dB", which helps. But it only does the last value too. It's be nice if each change could be undone.

Already exists. Woot! Sometimes I'm blind. My apologies, leaving up so others can see the answer too.

I have yet to really use Workspaces. Frankly, I don't really understand their usefulness. I get that you can customize a lot about them, but I'm just accustomed to using 1 workspace for everything whether it's tracking or editing. I've really been focusing on making everything streamlined. These monitors and this room transfers so well, I haven't found the need to add a second set of monitors yet. I'm sure I will at some point, but these Adams were an insane investment

Just wantedand bump this because it's still hindering my work flow. Decided to take a video clip to show what I mean. In it, I have auto track zoom enabled and I click on a clip in a different track because I want modify the clip gain, but it's a two step process. I have to manually change track focus to switch the zoom: It doesn't help that my main monitor is 49" extra ultra wide. It's quite the journey to travel from the middle of track view, all the way over to click the track on the left. That's a big part of the issue. My native resolution is : 5120x1440. Imagine if that clip was further away.

Forgive me if I'm being obtuse, but aren't VU meters just RMS? I do personally use other metering for things like LUFS, but don't generally meter tracks in VU.

I know that some people may find this silly, but I figure I might as well ask, even as silly as it might be to most. I have 2 monitors in my studio, as such: I'm working on films quite a bit and when I want to audition my score / sound edits, I start play back and look above to watch the film. The challenge is that I get distracted by everything that's going on in the main cakewalk window. If I minimize Cakewalk, it minimizes the video view window as well. It'd be nice if maybe there was a "no distraction mode" where the main view was opaque and dark, so it doesn't distract when auditioning. My current go to in lieu of this is to open up an image and max it out over the main monitor during playback, like this: I know it's likely a one off that many other people don't care about, but if it happens to be low hanging fruit, I figured I'd at least ask :). Thank you bakers for all that you do.

FWIW, I use a chrome plugin called "deluminate" to make browsing dark and low contrast.

I don't see a way to dark theme this forum, but that'd be cool too lol.

+1 Aye! Darkness in all the things!

I'd like to be able to manipulate midi CC data via nodes with options, like jump, linear, fast curve, slow curve. This would make adjustments quite a bit easier for me and the visual easier to understand as well. I'm doing a lot of orchestral style instruments lately and being able to click a couple nodes and set to slow curve, would simplify drawing in the curve manually. And it'd make fine tuning it a bit easier, as you could just drag nodes around instead of re-drawing the curve.

I stole the screenshot from another post for Reaper. Shows exactly what I want. Instead of having the bottom row in PRV set for 1 view with changeable midi data, I'd like to see multiple CCs at the same time. Specifically I'd like them vertically stacked on top of each other like the track automation lanes. Not necessarily overlayed. I'm doing more orchestral arrangement work and need several CCs that I have to make many adjustments to for proper dynamics and what not. In this track I have 1,11, and 21 that are all important.

Track Volume automation no longer works on instrument tracks in the latest release. This behavior is not seen with midi or Audio tracks. It appears that when using the new '=' bind to display track volume, the automation lane has no effect on the track volume. If you pay attention to close detail, the automation lane says "(volume)" instead of "volume". The lane with "(volume)" has no affect. You can still pull up the correct "volume" automation lane by manually selecting it: This yields the expected result. Other Details: The midi volume that specifies "volume (default ch. 1) still works properly in automating the midi volume send into the plugin. If you enable write automation and then drag the track volume, it works fine. The (volume) automation co-exists in the automation lanes. I have all 3 in this particular instrument track to show it: Mild annoyance since I figured out a workaround. Also, it seems like the '=' bind to clip between the last automation lines use is a bit glitch on instrument tracks in general, IE: it stops working and doesn't flip back from the (Volume) line. Thank you for the new release, it's generally excellent.

By your description, I'm not following. If you take a video of the behavior, I"m happy to chime in. I do a ton of zooming in and out and don't have too many frustrations with it. So maybe my workflow is just different. But I'd like to understand

Call it old habits, but I've been through some rough patches with Sonar where I've had major corruption issues (hasn't been bad for many many years though). I save crap ton of iterations of my projects and I ONLY rely on manual save. Auto save has corrupted a file on me before. Example:

I'm running an 8 core i9 at 5Ghz with 64 GB of ram. Resources are not a problem. But I don't want to unnecessarily use those resources. I always bounce when I know what I've done is fine to be committed. Especially things like Audio snap sound much better with the high quality engine and I'm not going to leave them churning up CPU when they don't need to be. I get that you're trying help, but I have this workflow for a reason. And I get that I'm probably in the minority on this. I'm reporting the feature because it would be useful to me. If they bakers decide to implement it or not, is up to them. Cheers.

@Roland-Music if you have second to chat, I'd like to discuss scoring ideology with you, since you have more experience than I do and I'd love to not stumble on my own if my workflows are inherently flawed.

Just had a friend show me Beat Mapping in Logic. @Roland-Music brought this up in page 8 of this thread. Absolutely get inspired by Logic's Beat mapping. This would be awesome. And as I mentioned in another feature thread I made, tying the beat mapping to an arranger section (as opposed to just a marker) would be wonderful too.