Cristiano Sadun

A workaround, but have you tried Windows scaling? I've used it in the past with CW and it helped.

These days it's hard to record backing vocalists due to covid, so I purchased a new backing vocals synth (the engine is EastWest's Play 6.2) and I'm learning the ropes by trying it on a song I'm mixing. What I'm specifically doing is to automate the "volume" control of the synth so that I can control exactly where the sound fades. In order to do that, I add an automation envelope on the synth's "volume" parameter, and set up a simple 4.-nodes fadeout curve. This works fine. The problems start when I add 4 new nodes to create another curve: I can create the nodes alright, but I when I move the points, the previous nodes move or disappear. If I then move one of the nodes and undo, some of the midi data after the last node disappears! If I undo again (to the event where I have just created the last of the 4 notes), the data reappears. Here's the link to the Dropboxed video . The behavior is repeatable (even if open/close the DAW etc). Is it something in this project that's corrupted? Or anyone has experienced issues with MIDI automation? It's really the first time I use automation envelopes on MIDI tracks so don't know if it's known issue or something. Automation on audio tracks (which I use a lot, all the time) works just fine. Obviously there's other ways to do what I want , but it should work.. Thanks! PS: Cakewalk is updated to the last version (today's) but I experienced a version of the problem last week, with the previous version.

No stress, got it anyways. Now let's hope someone listens!

Done, both on mine and your request!

Yes absolutely, even better! Let's cross fingers. Is there a way to vote for bugfixes?

Haven't seen Cakewalk code, but definitely Windows does what the programmer asks it to do - at the very least with ..windows 😄. There's plenty of docking frameworks around, and I haven't seen any with that behavior. I suspect it's a bug - a resize of that kind after reopening a window would make perfect sense when the window is docked, and a check that the windows is floating is probably missing. But no need to speculate - hopefully a developer with access to the code will pick this thread up.

Thanks all, yeah I have myself several workarounds. But the request is about not needing a workaround in the first place It should be an easy fix, it's probably a remnant from when the docking framework code was created...

Hi! The following s a small thing, and hopefully easy to fix, but it always irritates the beejeezus out of me. Not sure if it's a bug or by design, but in the second case I'd ask to review the design 🙂 I am pretty sure it's been the behavior from Sonar times, but hopefully it's a simple fix. I use a two-monitors setup, and I have CW on the left monitor and undocked windows on the right one: typically for the console or the tempo map (full screen) or sequencer (typically a fit-size window). Of course a new project starts with the various windows docked, so I undock the interesting window (say the console), move it to the right monitor and maximize it. When saving the project, CW remembers this which is great. So far so good. However, I often compose ideas switching between a demo I build piece by piece in CW and some other application. Typically that's a text editor where I am writing the lyrics and updating them to find the best flow with the music, or a browser, whatever. In doing so, I often close the undocked window (not CW) on the right while it is maximized full screen. After a few minutes, I reopen the same window (say the console) using the keyboard shortcut (or the "Views" menu).. CW opens the window undocked, but immediately resizes it to whatever not-full screen size it had before being maximized. So I have to go and click to maximize it again. 😭 This thing can repeat itself dozens of times in a writing or mixing session, and its mightily annoying. It seems that the menu is opening the window and then for some reason issuing it a request to toggle its size from maximized to not maximized. Which makes no sense, no other program I use insists in returning a window in non-maximized state if it had been closed as maximized (within the same runtime session, of course, I would understand if I were closing Cakewalk), So, the request: would it be possible to fix that behavior, and re-open an undocked window in exactly the same state it was when it was closed? (if it was closed maximized, keep it maximized, if it was closed not maximized, keep it not maximized) I love CW to bits, but this would really make me love it more! Every single unnecessary click is incredibly frustrating when you're balancing a guitar in front of the desk and trying to focus on the music or the mix. If there's already a way to change that behavior, happy to be told of course! Thanks! -Cris

In one installation at the studio I have the Cakewalk sound center synth that came with (I think) X3 Platinum. Unfortunately we never purchased any of the add-ons sample packs, and now obviously can't be had any more. Anybody knows if it's possible to buy or get them otherwise? Thanks!

Apologies for not getting back but got distracted by the whole pandemic thing here in Europe last month and totally forgot about this thread. Thanks for the replies and good that it's being fixed!

Do you export to identical word length and sample rate? If your tracks are really hitting 0dBFS (which they shouldn't until you want a master for physical CDs, you may have inter-sample peaks. Cakewalk's meters aren't True Peak so they show only the sample level, not the reconstructed analog signal meter. There's a free TP meter at youlean (and many others), if you place it on the master bus you will see if you have IS peaks or not.

Cheers, open it does what you need. As I understand this is not so much a workaround as the "official" way of rejoining clips - you splice, do your adjustments and then finalize by creating an complete clip out of the parts. Best of luck!

Not sure if it's exactly what you mean, but you can always select two or more clips and bounce them together with "bounce to clips". The side effect is that the new clip has a different name. If you have unwanted crossfades, you need to remove manually first.

Absolutely +1 to this. A big problem of all DAWs is that they default to show all the 24 bits worth of dynamic range, with the double whammy of tricking inexperienced people into overcooking their levels (because they think if they can't see the waveform well there must be a problem) and for the others, having well-recorded takes look very small unless you zoom in to a more sensible range. Having to zoom take lanes one by one manually is an unnecessary pain in the bottom. Even more, it'd be great to have the option to configure the default size of each track or take lane, separately from buses where it may make more sense to see the full scale.

Which gate are you using? Can well be CW, but I use sidechained gates a lot and never experienced the problem (Sonitus:fx Gate and Fabfilter-G)

On my installation trying to freeze archived tracks simply closes the DAW, with no warning (and of course no saving of the project). It's happened a few times in busy recording sessions: the two buttons are so close so that it's easy to get the mouse a little wrong, and push "freeze" when you want to de-archive a track. 🙂 The result of course is disaster as anything after the last save is lost. To test: create a new empty project insert an audio track archive it with A push the freeze button on the side Bam! No more Cakewalk. Anyone else experiencing the same?

Thank you Mark! No, just the delay section. The final sound is mixed in with an Eventide Ultraverb - Hall 1 setting I think - with the predelay tweaked. It's a very nice amp and the Nuvo is a crazy good mic for guitar, you can use it basically as you would a 57 but it sounds much better! The actual song is (will be) on a nylon string - I've just recorded the part last week.

..thought of sharing this. Btw, all of my band's productions have been produced with Cakewalk. It rocks even more now that's actively maintained.

Thanks guys, good to know. It's not a big deal but odd as the plugins that appear on top are the ones I've just inserted (as they should) so no reason should point to no longer existing ones. Will change the layout configuration and see if it's a layout problem.

A small bug perhaps. Normally, when I add an effect to a track (FX/+/Insert Audio Effect...), Cakewalk places it on top of the effect menu, so that it's quick to find should I want to add the same effect to another track. There's usually space for 4 effects there, meaning I can quickly reach for the last 4 effects I used. Some updates ago this stopped working: the last 4 effects get placed on top alright, but selecting any of them does nothing (i.e. no effect gets inserted). The layout I use for the audio effects is "by Manufacturer". There's no problem adding an effect again from the its position in the menu tree of course, and my workaround is simply to Ctrl+Move (copy) from one track to another in console view and then reset the effect setting to default. Is it something only I am experiencing? It's no showstopper but it was an useful little function that made the workflow a trifle quicker, so if it's indeed a bug and the fix is quick, it would be great to have it back. Cheers, -Cris

Yeah, one can hope.

I love the VX and imho it's got one of the easiest to set up compressors that I know of. Together with saturation options, the little nice EQ and the delay it's a killer strip. The de-esser is pretty useful as well. I've never liked the doubler but then there's no match to actually doubling vocals by using two takes. The only reason I've stopped using it is that I've experienced several times that, well into a project, it suddenly crashes (muting the audio or simply stopping processing) and never recovers. Perhaps that's why it comes disabled by default? Happy to see it can be enabled in CW now, I still have the version from Platinum but perhaps the bundled on would be better.

Cheers @msmcleod have been out to sessions a couple of days but at the studio later this evening and will do (if I find how to send a PM that is 😁)

Thank you, I'll give it a try - will this move the markers as well?

I don't remember really, it's not that I used it often. I would guess a few months back.