chuckebaby

See my earlier comment

I am starting to like the Selection markers more and more but its simply too small an area (the timeline) to be able to click accurately. All I want is one of these...

Could be a VST plug in refusing to playing nice with Cakewalk. Try and keep notes of "what happens directly before the crash". Its like being a detective. With issues like this, its all forensic analysis. OR you could send in a Crash dump file to cakewalk . I would start by loading a new project and see if you notice any consistency between projects. If not, it could be one project corrupt or possibly a bad plug in working in that project.

Use Cntrl+Shift+A to deselect. This will free up the timeline

Selection markers https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.20.html

Its actually pretty easy. Change all your tracks edit filter to Clip Gain. Select all tracks and adjust clip gain to taste.

Common practice is to select all clips and use the "Bounce to clips" function. Permitting slip edit data is no longer needed. Then you are able make changes to one whole clip vs. smaller pieces of clips all in one track. Its also a good house cleaning tip for storing projects.

@MusicMan11712 (aka Dr. Steve) It all depends on what we are used to I guess. Since I can remember (early 1990's) ive always wrote out drum parts in sequences, either in realtime using loop like on older drum machines or step write. Once I made the transition to a Piano roll, I write out notes one by one and then use copy/paste to tweak my own rhythms. I made this video years back and shows exactly how I use the PRV for drum editing. I still use the same principles. My advice for anyone has always been the same, stick with a method and learn to burn (get faster at it). no matter which way you work, one can always get familiar with their own process and work very productively.

This was literally the first thing I suggested

Nothing to do with Drum Maps. @bitman is referring to note names in the PRV/Notes menu to Show/hide note names. This is nice for some folks (like myself) who enjoy writing drum sequences in the PRV using the Typical Piano Roll vs. the Drum pane. Example -

Have you ever had any other devices on this PC (installed drivers, ASIO4ALL) ? If so I would remove them if they are not being used and I would also try renaming/save AUD.INI and let Cakewalk repopulate a new one.

I use a 10 ft midi cable to control my Mackie Controller. Wouldn't even bother with wireless unless I had to.

Kind of harsh to damn the tools when you haven't given them a fair shot ? no ? I remember going from Sonar 8.5 to Sonar X1 and it was tough. For the most part I kept working in 8.5 till I became familiar with the X series. So I know exactly where your coming from. But I did give it a fair shot and im glad I did. This tool behavior has been the same (for the most part) for 9 years now. You have some catching up to do before you can honestly say you don't like it. You tube is your best friend.

Awesome !!! That's what its all about. After playing with it a while, I was also able to repro the issue using your project, toggling ghosted on/off. Just glad we were able to track this down, it was really driving me crazy, I must have loaded your test project 20 times trying to find an solution .

Yes sir, this was using the latest version (which I believe was 7.2019) when I made the video. This is a good observation @jono grant. Now we might be getting somewhere. Let me check out some things on my set up and get back to you. It might be Ghosting data. Try enabling it by doing this... To enable/disable data type ghosting Click the Track view Views menu, point to Display and choose Display Ghosted Data on the submenu

Its all about gain staging. What you want is each individual signal path to be respectfully within its range (db wise). This means following/analyzing/adjusting the path from input to output. When your at this point in the mixing stage don't worry too much about cohesiveness (one track being louder than the other). Be more concerned with gain staging. Don't red line any of your track levels. I've had projects with 30+tracks that require some tracks to be set at -24db to avoid blowing up my master bus. Once proper gain staging is accomplished, then you can move on to adjusting track faders by both using visual inspection and more importantly...Ear inspection. Some tracks may read 0db and another -10 db and sound the same room level. This is where EQ and a good ear will help.

Have you tried eliminating the sidechain and just roll with gates on each channel ? As long as gates aren't chattering while 2 or more people are speaking than it should work fine. You might even be able to experiment with phase polarity if bleeding is too overbearing (TBH though, a little bleeding sounds more realistic in these situations). I do use ducking myself, but only for simple talk over narration with music backings.

There should be a kick plug in called "Kick yur Azz". The name alone would sell millions of licenses.

Not for nothing but your reply ^^ makes me wonder why I even bothered responding.

The issue here had to do with Region FX. Your issue might be related to latency ? Check your soundcard and or your midi buffer size.

Seriously though Juno, I wouldn't have downloaded your project, tested it, uploaded the video if I wasn't trying to help you. sometimes things go beyond my spec. Wish I had an answer for you. The only link between our set ups I can confirm is I don't have X1 installed on my PC. I have Sonar Platinum and up (Bandlab). So that I could not test. Does it happen in every single project you are using ? EDIT- Something else I just took note of in your video is you are using the Tools HUD to access the Edit filter (switch back and forth between Automation and Clip). Have you tried using the Track Edit filter instead (Like I did in my video) ? Just looking to replicate every step in order to find a bug if there is one.

Im a brain surgeon not a software developer. I don't know.

I believe he is referring to focus itself. While hitting D does indeed open the multidock, focus is not initialized until you click somewhere within the dock area. Example, PRV. While focus is in TV, hitting D will surely pull up the PRV that's been multidocked, but using the mouse to scroll up/down - side/side cant be achieved unless you click somewhere in the PRV area itself. Similar thread on TV/PRV focus

I know it might not be exactly what your looking for but you could create a track template. These templates can contain folder and multiple tracks that also include buses. I have some track templates that consist of 12 tracks nested in a folder. This is my drum template for doing almost exactly what you do. PS- Track templates also include routing. Here's a good example. I made this video several years ago but it still works today.

Can you try to list out the steps you are trying to do ? It could be a bug of some sort and that's what I'd like to help you with. Writing up the report. Also keep in mind, sometimes when Lenses are used in conjunction with Screensets, funny things can happen. For example, a locked Screenset may be preventing certain views from being docked/undocked when using a Lens.