Bill Phillips

I don't sync track and console views. I hide everything except active audio/midi tracks and track folders in track view. I'll also show buses and aux tracks when working on bus and aux automation. I only show anything with controls I want access to (all active tracks including aux tracks and active buses) in console view.

I don't know why that's happening. I think I followed the steps in you described in the 2020.05 Early Access 1 topic. I uploaded a GIF. However I've now noticed that BBCode option was missing for that GIF so I used the Linked BBCode option which probably converted my GIF to a mp4. Looking back I noticed that GIF is over 50 MB which may be to big to embed in the forum post so it was converted to mp4 and the BBCode option was removed. Thanks for getting my wheels back on the ground here. I'd gotten confused by the new "Inverse Link" feature in Neutron 3. A little more time reading Neutron 3 help documentation and watching videos cleared that up. Neutron 3's dynamic EQ sidechain input requires a send from another track like all other sidechain inputs.

Yes. You can press "H" to open the console view track manager, scroll to and "un-tick" the strings folder and click OK to hide them all; and repeat the process to "tick" the folder to show the string tracks. You need to be careful to make sure that the console view is selected when you press "H" if both the console view and any portion of the track view are visible. There are separate track managers for the track and console view as long as the "Keep track/console views in sync" option on the track manager is un-ticked.

This probably is a problem to refer to Izotope but wanted to check here first to be sure that it's not a Cakewalk related problem. The GIF below shows a vocal track Neutron EQ plugin (left) and acoustic guitar EQ plugin (right). I mouse through the EQ curve selections for each plugin and the masking meter dropdown for the guitar EQ. I have a dynamic EQ set up in the Guitar EQ for Band 3 that is sidechained to Band 3 for the vocal. Once the music starts, it's clear that the dynamic EQ is not responding. Is there something I need to do in Cakewalk 2020.05 to make this work? Any suggestions. http://i.imgur.com/VNCctKm.gifv Not sure what's going on with the GIF. Clicking the link opens it in a separat imgur tab but doesn't show up in the forum post. Maybe it's too big.

Using the media browser preview usually does it for me

@msmcleod, thanks. I used save as to create the project so the clips were already nearly the correct length, but I "Applied Trimming" to be safe. That didn't solve the problem. I use aux tracks, not buses for FX these days so, I hadn't really looked at buses. When I did I saw bus automation that stretched out across the whole tracking session. Deleting the bus automation solved my problem. Now "Shift + F" stretches the project to fill the screen. I think I'd originally added the bus automation to do a rough mixdown of the whole session. It looks like you get all the bus automation with each song when you use "Save As" to create a single song mix project from a multi-song session with bus automation. That probably also means that the bus automation is not in sync with the song. Not good, but ok if you don't use bus automation or don't mind recreating it manually for each song.

Thanks @Promidi & @msmcleod. That's it! I moved the left selection boundary to 6:02 and was able to move all the clips left. I also noticed that the selection extends to measure 903. So when press Shift + F to display the project which ends at measure 219, I get the display in the screen shot. I looked at the event list and there are no events after measure 219. Any idea what's out there? Dashed lines for track automation envelopes extend out there but nothing else I can see. As a note the clips for this project were cut from a recording session that most likely extended to measure 903.

Why can't I drag the 18 tracks in a project to the left? The attached GIF shows me trying to drag move 18 clips left. The clips won't drag left and the gray shapes shown show up while I'm trying. I then dragged one clip left with no problem. There are also white dots in the empty space to the left of most of the clips. What's the significance of that?

@MediaGary, are you using a 100% display scale factor?

Focusrite has a floating buffer size popup that you could leave open but using it several times in a session is about the only way I can BSOD Cakewalk

Are you saying that using Workspaces makes Screensets obsolete? I've been trying to use them together on a single project with no luck. I'll worry about other projects once I've got one working. Right now I've got a Workspace definition with the Screenset box not checked that loads one of the screensets that I want to use for mixing, but I have several other screensets I'd like to be able to easily toggle to. With the Workspace Screenset box not checked, Screensets are unavailable in that Workspace. If I check the box, I can't get the Workspace to load that screenset that it will load with the screenset box not checked. I've tried defining a screenset (1) that matches the one I want, but have been unsuccessful. Is there some trick I'm missing? Or should I abandon screensets, which wouldn't bother me, and define more Workspaces for the other screensets I'd like to have available. I just want to take advantage of the workflow tools Cakewalk offers to move around as repeatably and quickly as possible.

Yeah. I think the same thing would happen to me. I have 1st gen 18i8. I don't disconnect audio interfaces when Cakewalk is running so I don't know for sure. I do have a similar problem, when I change ASIO buffer size which is usually dodgy after the first attempt which works flawlessly. But if I'm searching for the smallest buffer size possible, I'll change the buffer size multiple times. Using the buffer size is always iffy and the Focusrite buffer size popup stays under Cakewalk after the first change. And once in a while, I'll get a BSOD. Both Cakewalk and Focusrite have made software updates to resolve this problem. But not there yet.

+1

I haven't used it yet but this one may have more features than LICEcap, but seems a little scary to me. Install took longer and once installed a capture launch dropdown was added in the top center of my screen that I couldn't immediately determine how to remove. So I uninstalled it which required a reboot that took considerably longer than usual to get rid of the capture launch dropdown.

Sorry @David Baay. I guess I misunderstood. I have my answer which I stated in my previous post and you helped me find it. For that I'm grateful.

Thanks for the analysis. But, the default range interpretation applying only to tracks added is news to me and counter to my own experience. My experience indicates that changing meter options including display range under Meter Options in Track View affects all existing track meter ranges not just any tracks added after the change. So I don't believe that it is possible to change Meter Options without the changes affecting meters for all existing tracks. However, given other issues I've had with Workspaces, I suspect it's possible, but unintended, that changing Workspaces for an existing project could change Meter Options indications without actually changing the meter ranges of the tracks in the project to which the Workspace change was applied, or vise versa. If true, I think this is an unintended consequence, or in other words a bug. In either case, the workaround is relatively painless changing meter display range and then changing it back to intended range will sync the meter display range selection with the actual displayed meter range.

Nope, didn't do that. As my screenshot shows I verified the setting being different than the meter scale range for several tracks. Didn't use a template, but I have been using and having problems with Workspaces which I've posted a separate question on. I'm thinking that Workspaces have some difficult to discover/modify features.

@David Baay, thanks. Yes, selecting -24dB display range and then reselecting -42dB solved the problem. The OP was posted to report the anomaly shown in the attached screenshot. As shown in the screenshot, playback meters were set to -42dB but operating at -60dB. I would have submitted it as a bug report but I can never seem to figure out how to do that. I've been having some other problems using workspaces to manage display options and I suspect that this is another one.

It didn't work. As the screenshot shows. -42dB is selected for Tracks but they're scaled to -60dB.

This looks like a bug to me. Cakewalk is in Playback mode but Track View meter ranges are set to Record mode range. This is more of a potential bug report than a question. Should I have posted it somewhere else?

Thanks @Nigel Mackay, For the 2020.04 update I installed the early release version and the final version and the final release versions. So I don't think that un-installing and re-installing is likely to help. Also, it's possible that this problem is related to the 2020.04 update. One of the problems I'm having is deciding if this is a bug or caused by my Workspaces setup. I haven't been able to find anything in my Workspace setups that looks to me like a potential cause.

I still haven't solved this problem, and would appreciate any assistance. If the question isn't clear please replay with a request for clarification. Here are some additional details: 1. I'm unable to un-tick "Set as Default Height" and it doesn't seem to set a track height used when the "Restore Strip" button is pushed for a track. This appears to be true even for the Workspace "None" selection. I don't think I've ever understood this setting though I do seem to find a way to randomly set default track heights from time to time. I just don't know how. 2. "Auto Zoom" seems to work fine for the "None" Workspace setting but not the custom one I'm using right now, but I can't determine why. For my custom workspace, the "Restore" and "Minimize" Strip buttons disappear when "Auto Zoom" is ticked. But, when I drag expand the selected track, and then select another track both tracks drop back to minimum height. I can't find a reason. I've un-ticked "Theme" and "Display Settings" boxes under "Manage Workspaces." 3. "Lock Height" seems to work fine. 4. I searched both the 25 09 00 PDF manual and the online documentation. BTW, the "SHIFT + Z" "Auto Zoom" toggle doesn't seem to work. That's not a problem for me, but I noticed it's in the 25 09 00 PDF manual.

Auto (track height) Zoom is not working in any of my workspaces. If I switch to Workspace "none" and some of the default workspaces, it does seem to work. What setting in my workspaces disables Auto Zoom? I've searched and can't find it. Is Auto Zoom affected by the Set as Default Height tick box in the track right-click dropdown? If so, that could be the problem. I've never completely understood what Set as Default Height does. I've never found a way to get tracks to move to the default height. And now I find that once I tick Set as Default Height, it's ticked. I can't un-tick it. This behavior seems to be independent of workspace selection. Any idea what's going on here?

@Nigel Mackay thanks. Useful analogies

@User 905133 & @wunderbier thank you. Your comments help. My problem is I haven't used screensets for a long time, can't remember when if ever. I've been using Workspaces since Lenses were replaced by Worksapces. I'm now experimenting to see if Screensets and Workspaces can be complementary. I've made some progress. I now have Screenset 01 set to show my Mix Edit project view I see when it opens and the Workspace is still Mix Edit 1 which is the work space I'm using. So I renamed Screenset 01 to Mix Edit Home. To save additional screensets it looks like I need to first duplicate my Mix Edit Home screenset, then make changes to another mix edit view and save that as the next screenset and so on. All the time my workspace is Mix Edit 1 which also includes default screen settings. Seems like overlapping not mutually exclusive. I'm still confused, but making progress I think.