Base 57

Instead of rolling back I have a workaround. I set a nudge to my offset amount (374). This accurately lines up new recordings quickly. There are too many things I like about this update to roll back.

I accidently posted this in another thread. It belongs here. Record Latency Adjustment in Preferences has no effect at all. In a loopback test I have an offset of 374 regardless of the setting. If I change the Manuel Offset, it changes where the clip boundary starts but the wave is off by 374. Whether checking the Use Reported ASIO Latency box or not the wave is offset by 374. edit. Instead of rolling back I have set a nudge to 374. That lines up the Wave accurately. So I will use this as a workaround until there is a fix.

Record Latency Adjustment in Preferences has no effect at all. In a loopback test I have an offset of 374 regardless of the setting. If I change the Manuel Offset, it changes where the clip boundary starts but the wave is off by 374. Whether checking the Use Reported ASIO Latency box or not the wave is offset by 374.

Punch is also late.

You are right. This is definitely broken.

Yes please. Or at least put the busses at the top of the output list. I have to click through 64 line outs before I get to the busses.

Cakewalk will import from an audio CD. With a CD in the computers disk drive use File-Import-Audio CD. It will pop up a track list of the songs on the disk.

I was feeling experimental so I tried the High DPI Rendering variable. It definitely looks better. So thanks for that. Bandlab integration seems to work well. I love the Tempo Track. This is a very impressive update. Great job Bakers.

Credit where it is due. @Craig Anderton wrote that article. In it he correctly points out that if you want to use automation on grouped tracks it must be enabled on all of the tracks. If you write automation on only one grouped track, the rest of the grouped tracks will not follow it. I believe it was also Craig that suggested using a midi fader through LoopBe if one wanted to only write a single automation envelope for all of the grouped faders to follow. I don't remember if he suggested it in the old forum thread I wrote of earlier or if it was a Tip of the Week.

Autosave and Save are two different files. Autosave is going to save every ten minutes regardless of the Save status. Furthermore Autosave is not going to clear a "dirty" project. FWIW I have Autosave disabled. There is no setting for it that is not annoying. Instead I have learned to hit "Cntrl-S" every time I even look at the keyboard.

Recording the track with headroom as you are doing is the best way to avoid clipping. After recording you can normalize the clips to make them louder for mixing.

Short answer. Export clips not tracks. Longer answer. 1. Bounce each track to a single clip that starts at time 0.00.000. Then give each clip a useful name. In the "Track" menu at the top of the Track View there is an option to "Copy Track Names to Clip Names". 2. Select all the tracks you wish to export and then open the Export Audio menu. 3. Navigate to the folder you want the export to go to. 4. In the Bounce Settings "Source Category" choose "Clips". Do Not put anything into the File Name box. Just hit export. If you do not want Windows to sort your files alphabetically put a number at the beginning of each clip name.

What are your computer specs? Because Keyscape and Omnisphere are serious resource hogs. In the first picture the crash is in Omnisphere but Keyscape is running also. In the second picture the crash is in Keyscape. It is possible that you will get better performance with those VSTi's in Reaper. But if your computer specs do not exceed the minimum requirements even Reaper is likely to crash. In any event you need to send the crash dumps to Spectrasonics' and Cakewalks' support.

You can sort your projects by date in Windows File Explorer

To do VCA type automation you need a Midi Loop (software* or hard). I use LoopBe1. It is free and easy to use but there are other options. -Group tracks as in the video above. -Create a blank Midi track (Name it VCA) and set it's output to the Midi Loop then move it's fader up and down. -Right click one of the grouped controls and click "Remote Control"- then click "Learn"- then click "OK". Then you can automate the VCA track and all of the grouped tracks will follow it. For hardware control, link the VCA Track to the controller as in the video above. The Track Group Control in Cakewalk is very flexible and powerful. But if you want to use automation envelopes you either must arm the automation Write on all of the grouped tracks or create the VCA track I just described.

This would be great if it worked. Your video doesn't show the grouped tracks actually following the single automation lane. There was a long thread on the old forum discussing this. So when I saw this video I thought there had been an undocumented fix. But no, only the fader with the automation lane follows the envelope.

As I read through this thread the thing that jumped out at me was that no one was commenting on the Bandlab integration. I have now downloaded a couple of projects I had created on Bandlab (band rehearsals) and it was very easy. Collaboration is going to much easier now. This entire update is awesome. Wow! Great job Bakers. Thank you.

I was just about to do exactly that.

To be more specific, my wish list for this would be- -The contents of the Project Notes/File Stats -A list of the Tracks by number and name - And the contents of the notepads in both the Folders and the take lanes. If it were in the form of a spreadsheet that could be opened (edited?) in Excel that would be very cool.

Yes. Please do this.

There are several ways to do this. You have mentioned two and either of them will work. You could also explore Offset Mode. Just be sure to turn it back off after you finish the edit. However the easiest way is to just lower the gain control of the Master Bus.

Most likely this is a clock issue. Any time you are synchronizing two or more different machines there must be a common clock or they will drift apart.

A mono track panned center will play from both speakers equally. Mono sources should always be recorded to a mono track. In Cakewalk, even stereo sources like keyboards should be recorded as dual mono (separate left and right tracks). In Pro Tools (and some other DAWs I believe), there are separate left and right pan knobs for stereo tracks. But in Cakewalk the pan knob in a stereo track is a balance control. It only reduces the volume of the side you pan away from. If you record dual mono you can pan each side anywhere in the stereo spectrum without using a plugin like Channel Tools.

Don't forget Groove Quantize.

I have an Orion 32+ which I love. I use the Thunderbolt driver which is ASIO only so I use a different device for Youtube and Spotify. While the driver seems to be bulletproof, the Control Panel can only be opened with the Antelope Launcher which has crapped out on me twice. Cakewalk and Reaper could see and use the device with no problem but the Antelope Launcher could not. Both times Customer Service was unable to help. They were very friendly and prompt but the solution both times was to reload Windows 10. My only other complaint is that there is no remote control capability for the Effects which means no automation. They sound fantastic but I can only control them with a mouse in real time and for me that makes them unusable. I have had the Orion 32+ for over 4 years now and the problems with the Antelope Launcher has only cost me a couple of days reloading Windows. And both times I've done that I have been glad I did. The machine works so much better afterword. So, I am glad I bought mine. If I ever have to buy another interface it will be the 32+ Gen 3.