msmcleod

@razor7music - I've got this one in my collection and totally forgot about it: https://8dio.com/instrument/songwriting-guitar/ It comes with a bunch of guitar licks you can string together to make solos. Best of all, it's free! The keys in blue each play a different lick (there's 5 nki instruments, so essentially you've got 5 banks of licks). All of the licks conform to a single key signature. Two of the nki instruments are in C, whereas three are in G. The red keys in the lower register pitch shift the key of the riff into whatever key you want. The yellow keys at the top apply various effects presets to the lick.

IMHO, the best value controller out there (if you don't mind not having motorized faders) is the Korg nanoKONTROL Studio. The nanoKONTROL 2 is also very good value, but obviously you get limited control and the faders are very small. I regularly use both: the nanoKONTROL Studio is in my office, and the nanoKONTROL 2 is mounted on my studio wall next to my vocal mic so I have transport/mix control while I'm doing vocal takes. The Presonus FaderPort 8/16 are excellent value and have native CbB/SONAR support. The only downside is the the "shared" v-pot for all channels. The desk footprint of the Faderport 16 is very small - it's almost the same as the original MCU - so you get 16 channels using up the same space the MCU uses for 8. The Behringer X-Touch is also an excellent buy, and is the closest to a real MCU. You can get a CbB/SONAR overlay here: https://store.birchwoodstudioandevents.com/Sonar-Overlay which will ensure the buttons match what CbB is expecting. From what I can see, the X-Touch seems to have all of the MCU buttons so you should get support of all CbB's MCU functionality.

This is over simplified, but basically : Cakewalk is a largely a musical time based DAW. The absolute time (i.e H:M:S:F or samples) for any event is calculated based on the tempo map. When the audio engine is running, it's running in samples... however it relies on the tempo map to convert to/from musical time. So having tempo changes based on a particular absolute time makes no sense in this context, as it's the tempo changes themselves that dictate the absolute time at any point in the time line. It's a complete chicken/egg situation. Technically, there may be some ways around this, such as: Converting the start of your tempo change back to musical time based on the previous tempos, and inserting it there Adjusting the start of any future tempo changes accordingly. However, there's a huge risk that the future tempo changes could actually end up being before or in the middle of the tempos you're actually inserting.... cos, well, you've changed the tempo, so the equivalent absolute start times of all the other tempo changes have now changed too. So currently, the only way to ensure a clip starts at exactly the time you want is: Bounce your clip to audio Set the bounced clip to absolute time This will ensure the clip with all its tempo changes "baked in" will be aligned to absolute time. You could do this as a temporary measure until you're happy everything is where it should be, then adjust your tempo map at the end, and go back to using the original MIDI clips. Adding the bpm at the end of the temporary audio clip name may help in identifying where you need to put your tempo changes. Another solution may be to use Process->Fit to Time to stretch the events to fit the tempo (or indeed the tempo map to fit your events). I appreciate this may take a bit of "getting your head around", but I hope this makes sense!

We'll look into this one.

Cakewalk currently does not support MIDI 2.0 - we'll be working closely with Microsoft when they natively support MIDI 2.0 in Windows. Pitch Bend is a channel event, which means it'll affect all notes on that channel. Polyphonic after touch is the only note specific event available, but very few synths support this (most only support Channel after touch). Using after touch also would limit you to only bending up, or bending down. The way I've done this in the past is to use a CAL script to split each note into separate tracks and channels, then move these tracks in to separate lanes (making sure the MIDI channel of the track is set to "None"). This way I could apply pitch bend on a specific lane/channel/note. This could be done either by recording the pitch bend, or by using an automation curve. As I was using hardware synths at the time, this involved creating a multi-patch with the same sound on each MIDI channel. I think @Promidi 's idea of using a second instance is probably the easiest for VSTi's.

This isn't as straightforward as it seems. Many of the MCU emulations send more than one button press message with the pressing of one of their buttons. So it's not a case of just mapping one button to another. I guess it's possible to write your own control surface DLL to deal with this (feel free - the SDK is here: https://github.com/Cakewalk/Cakewalk-Control-Surface-SDK ), but other than that the only other route is AZController

@natalini - FWIW quite a few of the team have surface books to test touch-screen functionality. Is there anything specific that isn't working for you?

Maybe I'm misunderstanding you, but I think you can do this already:

There are a couple of things that could make this happen: - A "hidden" automation envelope - i.e. you've deleted the lane, but not the envelope itself (this could be the result of an accidental copy/paste of your envelopes) - Using remote control / ACT / generic surface control on your faders, with a VSTi outputting MIDI that is somehow being routed back to the faders. The best thing would be to post your project (either here, or PM me or @Jonathan Sasor ) so we can take a look.

There are a couple of things that could make this happen: - A "hidden" automation envelope - i.e. you've deleted the lane, but not the envelope itself (this could be the result of an accidental copy/paste of your envelopes) - Using remote control / ACT / generic surface control on your faders, with a VSTi outputting MIDI that is somehow being routed back to the faders. The best thing would be to post your project (either here, or PM me or @Jonathan Sasor ) so we can take a look.

The transport, faders, vpots & display will likely work with either the Cubase, Ableton or Studio One profiles. But all the other buttons will do the wrong thing. It might be worth looking at the Presonus FaderPort (8 or 16), the Mackie MCU Pro, the QCon Pro G2, or the Behringer X-Touch.... all of which are cheaper than the SSL and offer more features.

Look at the nudge settings in Preferences->Customization->Nudge. You can configure up to 3 different nudge timings, and use the keypad (with numlock ON ) to move the selected clip(s). https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=Arranging.25.html

Yes - IRRC the first thing it does is apply the region effect, then continues with the bounce.

Bouncing the track has other options, like applying the track fx & automation, whereas Render Region FX only applies the edits you've made in Melodyne.

Interesting... strange, because Cakewalk follows the exact same code path right up until it calls into the Windows API. Only at that point does it decide whether to make a standard MME call or a UWP call. Maybe it's a Windows UWP issue, or perhaps a specific MIDI driver issue when using it under UWP. Personally, because I use older MIDI interfaces (e.g. the original MidiMan MidiSport 8x8), I always use MME.

This is most probably the cause. If you're using ASIO, you can tell Windows not to open a particular device as part of "Windows Sound". It was fairly easy to do this in Windows 7, but it's a bit more hidden away in Windows 10. If you're using any of the other driver modes though, you need to make sure that the Windows sample rate is the same as you want to use in CbB. This isn't strictly required for WASAPI Exclusive, but not all devices support this. So err on the side of caution - just make them the same.

Ok, it's as I suspected. The track's MIDI Program change is being sent out as well as the one in the MIDI clip. Setting the Track's MIDI Program change to none fixes the issue:

@John Darrow - can you PM me a copy of your project so we can take a look?

This might explain why my machine started BSOD'ing just after installing the AIR products when I did a "clean" windows upgrade to Windows 10 20H2 (i.e. the one where it wipes out all your program files, but keeps your data). Luckily, I eventually managed to get a normal upgrade to Windows 10 20H2 working in the end, and all my AIR products work normally. So I guess if you've got the option, run the installers on Windows 10 1909, update iLok licence manager - then do your Windows upgrade. Doesn't help people who are already on Windows 10 2004 or 20H2 though. I'm surprised they just don't take the PACE installers out completely, and just tell people to install iLok manager first. I mean... installing AIR products is a PITA anyhow - there's that many files, it's easy to get lost - so adding an extra step isn't going to make a huge difference.

The only time I've seen this happen is when using the Realtek ASIO drivers, which are really buggy. Changing the driver mode to WASAPI fixed it for me, so if you're using a Realtek sound device, switch your driver mode within Cakewalk to WASAPI.

The only way I can reproduce this behaviour, is when there's also a Program Change set within the track's MIDI inspector, as well as the one in the event list.

One thing I would say though if, for 600GB of data, you're initial sync will be pretty slow (unless you've got a VERY fast upload speed). My connection is 80Mb down / 20Mb up, and it took a few hours for the first upload. Now that's done though, incremental uploads are usually less than 2 mins. I use that time to let me pack some gear away (mics / cables / switch pre-amps off etc), and make sure my phone and keys are in my pocket! The download sync takes less than 20 secs.

If you don't like the names, just rename them in Audio->Devices. Each input/output has a "Friendly Name" field. You can name this to what you want, and this will be what is displayed if you check the "Use Friendly Names" checkbox.

I suspect its an issue with TTS-1 rather than DXi in general. The technology behind DXi's is still widely used in Microsoft products, so if it was fundamentally broken, you'd see issues with video playback and audio playback in a bunch of apps. Unfortunately TTS-1 is a Roland product, so there's not much we can do to fix it.

Pitchproof is a free pitch shift plugin: https://aegeanmusic.com/pitchproof-specs Also, MeldaProduction's FreeBundle has MFreqShifter and MVibrato - both which can be used for pitch shifting effects: https://www.meldaproduction.com/MFreeFxBundle