LarsF

Yes, proper markers for nodes of tempo and just handle like automation of anything would be nice.

Yes, please, a tempo track like some do it would really be nice. And ability to see nodes and new tempo from a certain point as some daws do it, Reaper and StudioOne as I recall. So being aware of that change in tempo - like doing video and different scenes are different tempo all the time almost. And scaling of tempo view is really strange as of now, it should always have integer tempoes on scale, not like 127,46 as one marked level. And draw nodes, like visual dots, on timeline for tempo - sometimes difficult to see very small tempo changes.

I'm with you on this one. Allowing one track to be like master(VCA) to the others - and in nested levels too - is so smooth. So programming automation on a fader as master - this is superimposed(layered on top) on tracks it controls. You can just do a fade on master - and you see a silhouette of what this does to tracks it controls, on top of tracks automation itself. Then when done - you merge/freeze master into. The write automation you are forced to do is just not as good as workflow. While doing it all in one go - you can use undo - and be fine with it. But if to go back later you are f-ked. And forget about nested control. Both Samplitude and Reaper has non-nestable VCA-similar approach. ProTools, Cubase and StudioOne do it right - both on getting double visuals on what vca is doing on children it control, as well as allowing a vca to control other vca's. But to finalize - Cakewalk control groups is astounding in itself. How you can make any control part of a group - spectacular!!!! Maintaining states on buttons and other reverse stuff - really, really nice. Not complaining about that. But the offset mode is demanding a write operation realtime now and is burned in as soon as you stop automation. Just that little bit missing to have a master control that works on automation level to the children in realtime and double visuals of automation and what vca do when total sum up on each child it controls. https://www.soundonsound.com/techniques/how-use-vca-groups

I bought the article - but sorry to say to core point of VCA is not even mentioned - neither 'dry' or 'wet' is in article. - Keeping the dry/wet relationsship while automating - that is the core point And "Take the bus" example is ambiguous to me as I read it - you want to change dry/wet? As I feel is most common having post fader sends - just automating faders will keep dry/wet relationship and as fader go down the send level do too in the right proportion. This compared to a drums bus, with sends on tracks feeding the bus - lowering bus will keep same amount go to reverb and thus altering dry/wet relationship - out from bus is lowered but sends abount stays the same. Alternative to this is sacrificing another instance of reverb for drum bus alone, and have the return of reverb go to the normal drums bus - so you can automate this bus and perfectly keep dry wet relationsship.

Just noticed this when using locked markers in time. You get the status on the tool panel selecting it - but there is a column to show Lk status which is always blank. So when mixing locked and non-locked markers - it is hard to differentiate and have to do trial and error on each marker. Really smart use of markers to be able to lock certain to video scenes and those that used for musical purposes following tempo. So quickly seeing the locked markers is really useful. Thanks.

Like ProTools maybe - that look like pic below. They have a module in console that looks like that - on every track and you see where your culprits are. - It says how much latency is on that track - it says how much this track is delayed in the total as running - and a field to set you own added delay +/- to a track to modify how a track is handled. Very neat and you are in full control. Could be among console module to show or not.

Thanks for viewing. Not quite, will try and explain. When you do solo override on fx busses - it means when doing normal solo or exclusive solo on other tracks it does not mute those with solo override set. But since solo override do solo itself now - you only hear fx busses if even set, meaning you have to remove that every time after using it. And for that you need to make fx busses visible just for this purpose putting solo override on them every time - if want sends to fx busses to still sound. In other daws this feature called, solo safe, solo excempt etc, you can set solo override once and let it stay there as saved with project, and even hide fx busses away. Activating a solo override does nothing unless you solo other tracks normal way. So you always get fx busses excluded from mute soloing other tracks with no extra overhead each time. TIP! for doing what I think you are saying --------------------- There are very neat features in Cakewalk doing control groups of buttons - and the extra neat thing is that their retain their toggle status as they were when creating the group. Some were on, others were off etc. The toggling these as a group - the all swap state . So lets say you have a bunch of tracks you want to solo together - and swap over to another group of tracks soloed - you can have one set with solo=on, and the other group solo=off. Create the group with all of these and then use as you please. - clicking on one part of group, lets say solo goes off, the other part solo goes on - their reverse state are maintained. I had a similar thing going doing surround where I wanted to swap what I heard front L+R +center and rear L+R - very usable with such a group - and one click to swap between hearing either side.

Hi As working are now, you need to have all fx busses visible to quickly activate this Solo override on each one - then go on to solo what you attempted. Very cumbersome compared to letting solo override do stuff only as normal solo or exclusive solo is activated anywhere. This is how it works on other daws - you just set it once, and hide fx busses away and never have to worry about it. Thanks for any support on this. It will be soooo much easier doing solo, just for mixing or as for recording and using dim on solo etc. Running Cakewalk 2020.01.

I revert what I said - after experimenting what is predictable result is doing what you said. Keep musical timebase, no lock at all - and do even repeated "Insert measure at.." is working. So you count what seems like one measure on what you recorded - and insert desired measure there. And you can continue through out a clip recorded and adjust like that repeatedly. One alternative though - hold Ctrl Shift and drag either left or right end of midi clip to be the length that makes it fit. Described p682 pdf manual. I made to many assumptions how Cubase and StudioOne do it by having tempo track as rubberband just drag nodes. Since they have tempo map as a track syncronized with grid above you can do this.

So to figure this out - I made a midi loopback and looked at a midi monitor on a receiving track, since what comes out from FX bay is not the last say on what is sent. Track you operate on, the midi track, need not be echo=on. If settings have zero controllers on stop, pw, mw and sustain pedal plus zero controllers(cc 121) is sent at stop - on every midi channel 1-16. Vel+(Gain) - most consistent workings, always modify velocity accordingly. Latch type midi Reverb, chorus - once touched they are sent every start of transport on channel sent on. To turn off rightclick and Disable control. Then it stops. Also send realtime when altering value, transort running or not. Momentary type Pan(cc 10) - when touched sent once at transport start, and realtime while moving as transport run or not. Vol(CC 7) - when touched sent once, and realtime while moving as transport run or not. Both momentary are sent on transport start, once one is touched, those that are not disabled. So touching any vol or pan is sending the other if touched before at each transport start - once. Disabled on rightclick menu Disable control. Status of disabled or not can only be seen on these in midi track panel, having these visible with parenthesis around value. All above are done after midi FX bay - so not seen on a midi monitor loaded. Rightclick menu on control, rev, chor, vol, pan Value -> Set Start to = Current Value -> Set End to = Current Value -> Set Snap to = Current No clue what these does and meant to do. EDIT: seems these are to do with grouping - from manual "The Set Start = Current and Set End = Current commands set the range of motion that a grouped control moves through as the other members of the group move through their starting and ending values. You don’t have to designate a group as a custom group to create a custom group—just group some controls and set their starting and ending values."

Noticed that you have to set effect busses to solo override at every occasion you are to solo anything. Then remove when done - or those are soloed disregarding if anything is soloed normally. Solo Safe and Solo Excempt and what it's called, I usually could set and forget - it does not solo anything, just set permanently and you don't have to think about it. But there are many settings in these config files as I learned, is there anything to change this? Thanks.

Great stuff, thank you. Will immediately test this - makes perfect sense. EDIT: Got it as good as it gets - this is what I did - setup windows and docked on left and right as I wanted it - checked all checkboxes but keyboard shortcuts on lens/workspace manager and saved. - then removed one checkbox at a time and saw what changed - finally it was only transportbar with tools left . This secured that custom module got the same content for every project I opened. So did not have to redo that every project. So the rest goes by screensets and is saved with project it seems. Still have no clue how it works, since if I let any more checkboxes in lens/workspace the custom tool module would not stay. Anyway I found a way.

Thanks for tip on parenthesis that showed that I touched volume and Vel+. So i checked further - and it works towards the instrument - but the midi monitor I used seems to track data right from track before Cakewalk does that extra processing, weird? Have to look at flow chart how signal goes again for midi plugins on midi tracks....

I've done similar things in other daws - fitting tempo to free running recording, kind of. If you set timebase to absolute on midi track, and then change time signature, you should be able to then adjust tempo to get measure boundaries over the same without the midi clip is moving or sounding different. But this is if you actually recording as 3/4 to start with, but were just free wheeling a recording. But have not done this in Cakewalk yet, just thought I spread the idea - to let clip remain as is without changing how it sound, just getting tempo and time signature to fit. As David said, but making rest of clip not changing as you suddenly moved a boundary. Once they fit, you can change back to Musical timbase and adjust tempo and have this in the new time signature. If I at all understand the questions what you want...

Thanks. Bakers has really raised the bar many notches overall, software, manual and tutorials. Glad I found my way back.

Interesting approach there, thank you, will try some of that.

Hi EDIT: Look further down for experiments how it works. Looking through manual and searching forum I fail to find any info on this. In Cubase a midi fader is inactive if channel is set to Any. If set to channel 1-16 fader send CC#07. Have tried various ways in Cakewalk 2020.1 to do anything like that to midi when sent to instrument. Manual states just that it do this and that - but no, it does nothing what I could find with a midi monitor(Tencrazy TrackDiag). How is this done? I tried set a midi channel, I tried the rightclicking stuff, but no clue what this Value and stuff do. Under what conditions do these operate? Thanks.

Thanks. I guess it's bit of trial and error. One coin that dropped was that track control preset said "Workspace" so guided by Workspace as default. So that is nice to be able and make track panel less crowded always or according to switching Workspace.

Hi Had everything I opened as project keep having this Browser tab opened and tried to get rid of it. So a collapsed Inspector on left, and collapsed Browser on right - is what I wanted. So just trying to understand this new stuff Lenses, now thankfully called Workspaces and Screensets combined. This is the route I took - created a new project and imported a video, since that is what I needed to see how it worked in Cakewalk - tried setup gui as I wanted and did Save on the Advanced workspace selected - did not help - new projects always opened with Browser tab opened. - went into Workspace manager - and also added Display as checked - then repeat above - did not help. - then tried different screen sets - both 1 and 2 had Browser open - but 3 did not - so duplicated that into 1 and 2 and locked and saved Workspace. - then I got rid of Browser finally, and it was collapsed. Reading manual it says Screensets need not be saved, they are saved as project is saved. The first two, 1 and 2 were not locked so thought that would be enough - just collapsing Inspector and Browser and save - but it was not enough. I had to do the operations above before in sticked. And I can open all on recently used list(done in Sonar Artist 2015) and get that Inspector and Browser are collapsed - perfect. But Screensets are saved with projects - so don't understand how that operations fixed something actually in Workspaces part? What is Workspaces and how it overlaps Screensets as it seems? Does Workspace save the last Screenset used and copy into it's settings? They seem to be related somehow. Just want predictable result and understand how this works. Any ideas? Reading manual on Windows Management does not include Lenses part(now Workspaces), just a reference to other part of manual. Still they seem very much related. Thanks. Anyway, after out in wilderness of Cubase Pro and StudioOne I am back on good old Cakwalk again. Started with Cakewalk Pro late 80's, Sonar 4, 8.5, X3 and Artist. Excellent job Bakers.

It's a pity that CHM help was dropped, means daw have to be online - which it isn't. Is the last chm available to download at least - and we can enter registry stuff ourselves? Anyway, manual is really, really good. And to get the most use of it I could tip on using PDF Xchange Editor instead of Adobe Reader. You can make own bookmarks(remeber to save), since that part is empty in pdf manual - and it always retains last place you were in a document next time you open it. Better search as well. Highly configurable beyond anything I saw, everything in gui as you wish. https://www.tracker-software.com/product/pdf-xchange-editor I use the free version, still can save bookmarks.

Thank you, perfect. I'll see if any performance differences, I really don't notice I run video even now - very smooth. If so, I can render a preview video with 8s black frame in front. Just didn't get why it was disabled.

Hi Just installed 2020.1 as my first install, migrating from Sonar Artist 2015. Just getting the grayed field for video to enter an offset into timeline where start offset is, thought it was limitation on Sonar Artist. Same thing i properties dialog. Installing Cakewalk this field is still gray. It is mentioned in help and reference manual and says nothing why it might not be available. Any ideas? Thanks.