msmcleod

I guess the point is, if the OP's customers are specifically asking for AAF files, then it might be worth the investment... especially if its something he could charge extra for. Interestingly, the main reason why the enhanced version of AAF is so much more expensive than the standard version, is down to the amount of effort in providing OMF, AAF and ProTools support (and presumably keeping it working). The developer alludes to this in one of the links I posted. But I agree, individual track exports/stems & MIDI file export are far more useful, and they'll work with everything.

You can also uncheck "Select Events With Sections", or use the button in the select module:

An EQ or de-esser should do the trick. You just need to scan through to find the right frequency. You can also use a dynamic eq, so it only ducks the frequency when it gets particularly bad, rather than all the time.

Cakewalk only supports OMF export, which is the format that preceded AAF. AAF is ridiculously complex and over-engineered, and unfortunately offers little over OMF for audio projects (it was primarily developed for video). What's more, every DAW that does support AAF has implemented it differently, so there's no guarantee that an AAF file from one DAW will even import properly in another. There's currently only 2 ways to get AAF files from a Cakewalk project: 1. Export it as OMF from Cakewalk, then either import that into another DAW that supports both OMF/AAF and export as AAF from that DAW. 2. Export it as OMF from Cakewalk, then use AATranslator to convert it to AAF. Note that you need to purchase the enhanced version to support OMF/AAF. FYI - this has been discussed before... this was my reply:

While this request isn't necessarily off the cards, due to the way folders were originally implemented, it's in no way trivial. However, in the meantime, for large projects you could consider using Track Manager presets. They are per-project presets allowing you to hide groups of tracks, so you only see the ones you're focusing on at any point in time. You can also combine them with Screensets, with each Screenset using a different preset (i.e. Screenset 1 = all, Screenset 2 = strings, Screenset 3 = brass etc. ), so you can quickly switch between them.

Saving a template will always remove the events. Anything else would simply be a normal project. However, you can achieve what you're suggesting by doing the following: 1. Create your template project as you would normally, and add your events and articulations. 2. Save it as a regular cakewalk project (i.e. cwp file) 3. Copy the .cwp file to your project templates directory 4. Rename the file so it's extension is .cwt instead of .cwp

@dubdisciple You could try renaming Offline.html in %APPDATA%\Cakewalk\Cakewalk Core\ to Offline.html.bak It should get recreated from scratch when you re-open CbB. You should try to work out why this has happened though... do you have OneDrive enabled? I could have re-synced from an older machine maybe ? Check your OneDrive configuration, and consider excluding this directory... or at least make sure everything is synced and up-to-date.

The time display in Cakewalk is tempo based, whereas audio data is absolute time based - that's why you see the audio stretch when you slow down the tempo, and shrink when you speed it up. To get the audio to automatically stretch with the tempo, switch on "Stretch to Tempo" for the selected audio clips in the clip inspector. Important - make sure you set the Original Tempo to the existing tempo value BEFORE you change the overall tempo in your project. You can do it afterwards, but you'll need to make sure you remember the exact tempo you had it at when your recorded your audio.

As far as I can see the Zoom LiveTrack L-20 doesn't work as a control surface. It provides audio over USB, but no MIDI. You can rename the audio ports in Preferences, by enabling Friendly Names and editing the name in the areas shown below: The Inputs and Outputs are shown as stereo pairs - to name each "side" of the pair, use the | character to separate the odd and even channel names (SHIFT + backslash).

This looks like you installed SONAR after you installed CbB. Re-install CbB - you can use the downloader in this early access thread:

Most of the time, you either have a chart or you just work out what key it's in. For alto sax it's easy - you just go down 3 semitones from the key everyone is playing in.... in other words, if everyone is playing in C, you play in A; if they're playing in E you play in C#/ Db. In my head I see it as switch to the key of chord 6. For Tenor sax, you play 2 semitones up - i.e. if the band is playing in C, you play in D. If the band doesn't bother telling you the key, you can look at what the guitarist or bass player is playing, and work it out from there. 9/10 when playing sax, I only ever played the solo, so there was plenty of time to get it right in my head. And if someone gives you the chart for a tenor sax when you're playing an alto.... you just pretend you're playing the clarinet in the lower register. The fingering is similar enough to get you most of the way there.

@Mike Davies - you can also use an articulation for this:

You can also use a transform articulation to do this. Just make sure the articulation spans the length of your track: This is the definition, or you can download it here, and use the import button to add it: https://msmcleod.co.uk/cakewalk/Transpose.artmap

The highest resolution of tempos in Cakewalk has always been 0.01 BPM (since the DOS days). Even if the dialog at some point let you put in 0.001, it's likely it clamped it to 0.01 under the hood. The old step value allowed you to specify the minimum increment of BPM values when inserting a series of discrete tempos. The insert start time for each of those steps would then be calculated based on the range specified. With the tempo track, it's the other way around. The Tempo Map Decimation setting defines the minimum time gap between each step, and the tempo value is calculated based on value at that time for the given curve type. In other words, the resolution of this value is always 0.01, however instead it restricts the time gap between these increments to the Tempo Map Decimation setting. A setting of 3, means that 16 tempo changes will be inserted every quarter note. For the next release, we've increased the Tempo Map Decimation setting range from 3 to 8. Specifying a value of 8 will mean 320 tempo changes per quarter note at a minimum step value of 0.01. I've compared using setting 8 with what SONAR Platinum was doing with a step value 0.01, and the results are almost identical, so hopefully this will solve your issue.

Two things: 1. Within Cakewalk, make sure your tracks are being sent to a Master Bus, and your audio interface output is set at unity volume. 2. Within Windows, make sure any sound enhancement is turned off by clicking on the speaker icon in the taskbar:

It's probably more to do with your audio interface / audio interface driver. When the PC wakes up from sleep, the status of everything (including the audio interface driver) is restored. However if the actual status of your audio interface mismatches what the driver thinks it is, you'll get these sorts of issues - at worst you could get a crash. You could try turning the engine off then back on again within Cakewalk to see if this solves things: The only other alternative is to save your project and close Cakewalk before putting your PC to sleep.

Try this:

It's still there from what I can see, and the Event's View hasn't been touched for a few releases now. Maybe you've just not scrolled down far enough?

@TheSteven - the XLN Audio errors are likely down to a Windows update. I get this from time to time (got it today in fact). Just opening the XLN Online Installer and logging in to your account should solve it. I'm not sure what the issue with Synthmaster One is - it's working fine on all my PC's. Maybe try re-installing it.

Ahh... right, now I understand what's going on.... There was a slight change to the track visibility logic in the console view, as users were complaining that hiding MIDI tracks would also hide Instrument Tracks. So now, unchecking "MIDI Tracks" will only hide stand-alone MIDI tracks, and not Instrument Tracks. If you want instrument tracks to be hidden too, you need to uncheck "Instrument Tracks" in the console view.

I tried the upgrade using both older projects and also a test project I made just before I upgraded. I didn't get any issues, but then I can't remember if I'd actually upgraded to the early June or not. It's possible (if not likely), that I was on the previous version before upgrading.

One gotcha with SI Bass that gets me every time, is the fact that it's transposed down an octave, while still only playing the range of a bass guitar. In other words playing A2 in SI Bass will play the open A string on the bass (whereas on GM / GS you'd play A1 to get the same note). If you play a A1 in SI Bass, there will be give silence because there's no lower octave A on a standard tuned bass guitar. The answer is (for this issue anyhow) is to transpose the MIDI track up an octave.

fair enough - although personally I just freeze the track, or if I need to keep it copy the frozen audio to another audio track

Yeah, the split instrument track is basically the audio & MIDI tracks separated. I almost never use split instrument tracks nowadays, as I hate the fact I've got twice as many tracks, and also it makes it less clear what is a real audio track and what is actually just a source for instrument audio. Nowadays you should be able to just about everything you could with split instrument instrument tracks with Per Output Instrument tracks. I think we've sorted out all the loose ends such as the Replace Synth scenarios, automation etc. If anyone can think of anything you can't do, please let me know...