Xoo

I do not want snap to be global! I may be editing MIDI clips glued to measures in one and editing audio, where snap needs to be off, in another.

And lane buttons (drives my niggling sense crazy - why should a button's glow status change just because I clicked on it once???).

This.

It shows there's data in a track after the current time (there are no ellipses after the last clip in a track).

12 - No-one mentioned lawyers...

Thanks for the headsup about Sumatra - it's just replaced FoxitReader as my PDF reader of choice (lightweight and 64 bit!).

That won't set the command line parameters correctly, so it won't populate the registry with updated/new information.

This seems a very workflow specific requirement (ie. not that useful to a lot of people) - not saying it isn't, but what's the use case for this?

And if you run vstscan as adminiatrator, and CbB as a different user, you may not see the VSTs you expect in CbB (depends on if you're elevating or using another account which has admin privileges).

This is really more of an idea for people to look at rather than a completed AM to show how AMs can be used in "unusual" ways. I have fxPansion's BFD 2 (and BFD 1 and BFD 3, but I've spent most of my time with BFD 2): it has internal grooves that can be triggered by MIDI from your DAW. In CbB, you can use a drum map to expose them or (thankfully because fxPansion implemented the VST note exposure API correctly) from a normal piano roll view. But it's not always obvious when they stop (especially as there are multiple latch modes in BFD 2) or what pattern is playing at a particular time. I've started building some AMs to expose the groove MIDI notes within the articulation lane, so you have more visibility over what is playing when. BFD 2 Grooves.artmap

Oh yeah. I'm sure I managed to do this yesterday somehow like this...it was late!

Slightly faster (this made me think of it): Arm the first track normally Before next recording, Ctrl-A, then Ctrl-click the record button on the new track to record

And Shared Utilities - that's where the cw*auto.dll is stored and if that's out of sync with your version of CbB, bad things (TM) happen. Ah, I see a certain @scook beat me to this ?

But did it look like a kitten..?

Or sustain pedal?

I've seen a development request with a hand-drawn sketch and the immortal words "like this, but better".

Same here with Melodyne - that said, Melodyne behaves the same (slow startup) in Sound Forge, so I don't think it's Cakewalk specific.

OK, so try this... Same file Search for DriverType= Set its value to 2 (ASIO)

It was suggested on another thread that this might be due to Ozone's copy-protection. Are you using machine authentication rather than iLok, and don't have any iLok authenticated products on youe system? If so, then I think this *might* be the issue - I get the same with Melodyne. See below for details and way to check it.

It doesn't - I tried last night. Sorry ? I tried adding a DisableWDM entry just in case it also worked - no dice. Fortunately, WDM works for me in Windows 10/Project5, and if it didn't, my MOTU driver exposes a setting "Use WaveRT for Windows audio" (or similar - not at my PC right now) which bizarrely disables WDM in Project 5!

I have it switched on (nVidia GT1030) and it works OK with Cakewalk - doesn't make an obvious good or bad difference in anything I use to be honest.

Graphic design that uses fonts still seems to be a Mac stronghold in my (current) experience.

I can't see as the Simple Instrument Track (SIT) doesn't display MIDI input, but my guess is that its MIDI track is either not configured to use the virtual keyboard as its input or the note range is wrong (do you get any MIDI recorded at all on the SIT track?).

The controller is either an external MIDI controller or the virtual keyboard you have open. The bar at the top of the screen is the *control bar*.

Onboard battery?