msmcleod

Automating the threshold control is the way I usually do it.

Great to hear BBT are going to continue - they're one of my favourite bands. I'm really tempted to go to that gig if I can get tickets... it's a 400 mile trip, but I have family in Aylesbury.

All of the M-Audio MIDISport range share the same drivers, which unfortunately are not playing well with Windows 10 any more - they suffer from lost / hung notes. MCU = Mackie Control Universal. These are the three original "MCU" units Mackie released: The MCU Pro / MCU Pro XT's look like this, and don't need MIDI interfaces as the MCU Pro has built in USB:

I'll probably need the zipped folder... if you have a OneDrive or other cloud account, just upload it there and PM me the link. Let me know if this doesn't work, and I'll PM you my email address.

I'm not sure if it was your support submission or a similar one, but I do remember looking into this issue and I couldn't find any way to reproduce it. Unfortunately with these sorts of issues, until we can get a solid repro, they're almost impossible to fix. Feel free to PM the project directly, and I can look at it again.

Yes, MIDI interfaces that are built into audio interfaces are fine. The MIDI ports in my Scarlett 6i6 work fine with the MCU too.

I've got an original MCU... and I've also got an identical MIDI cable to yours, and that cable does not work. The reason being that it MIDI data needs to be transmitted at 31250 baud, however it readily receives data at the USB2 speed 480Mbps. So it has to store all that data received at one speed, and slowly transmit it at another. In order to do this it has to store the data internally, however it's internal storage is literally tiny... something of the order of 8K. This may be fine for 8 to 16 notes played on a keyboard, but no where near enough for many continuous controllers, and certainly not for the traffic generated/received by the MCU. You need a much better MIDI interface for the MCU. I used to use a Midiman (M-Audio) Midisport 8x8 - this worked fine in Windows 7, but the drivers are old and too unreliable in Windows 10. The only modern interface I've found reliable enough for the MCU is the MidiTech Midiface 4x4 or Midiface 8x8. I use the Midiface 8x8, and it works perfectly with my Mackie MCU + XT + C4, as well as receiving data from my controller keyboards. At the moment, this is really the only interface I've found that works in Windows 10. I've tried a few other makes such as MidiBox, and ESI, but they all use the same chips as that MIDI cable, and won't support any busy MIDI traffic.

Double-clicking the task will also recall the task settings.

try: CTRL + Home then CTRL + SHIFT + Page Down

You might be able to use both using WASAPI Exclusive mode, but personally I'd advise against it, as you'll get timing issues unless you can synchronise the word-clocks of both units. You can normally do this using one of three methods: - BNC cable from a wordclock out to a wordclock in. - ADAT output to ADAT input - SPDIF output to SPDIF input As neither the Zoom L-12 or SSL 2 / 2+ have any of these ports, you'll not be able to synchronise the wordclocks. What you could do I guess is connect the analog outputs of the SSL to two line inputs of the Zoom L-12. This would give you the ability to use the superior pre-amps of the SSL, and record them via the Zoom L-12. You'll need to ensure that the SSL is set up for zero latency monitoring so it's echoing the inputs to the outputs.

This may be the Windows bug that prompted us to change some of the menus in the track view to the new style menus. Windows menus used to have a limit of around 4000 items, but since Windows 10, this has been reduced to around 1200. The bug was raised with Microsoft around 11 years ago, but they've not done anything about it ( it's actually got worse! ). If you've a lot of templates or subfolders, it could be hitting this limit.

I find trying to play piano parts on a non-weighted keyboard unusually difficult... even the semi-weighted keyboards that have piano style keys just don't do it for me. I used to use an old Yamaha PF80, which was a beast at 34Kg (75lbs), and I'm pretty sure the keys were heavier than a real piano. Although I miss the extra controls it had for transposing & changing MIDI channels, the StudioLogic SL990 at 20Kg ( 44 lbs) has a way better feel and is much better on my back! I'm not brave enough to attempt to use a laptop on stage, as I don't trust computers in a live situation. If I can get away with it, I'll stick to the sounds in my Korg X5D which sits on top of the SL990. For anything more adventurous, I use an SMPro V-Machine with my old hardware synths & some VST's sampled on it. It's about the size of a VHS cassette.

Clip Gain Automation affects the clip volume only (pre clip fx, and pre track fx), whereas volume automation affects the volume of the track post fx. In other words, clip gain automation affects the volume at the start of the chain; volume automation affects it at the end of the chain.

Another thing to bear in mind.... When a clip is frozen, a backup of the original clip is kept at it's original location. In most cases, moving / editing a frozen clip around will not move or affect the original clip. There are some exceptions, like Ripple Edit All and some Arranger operations, but as general rule, when you unfreeze, the original clip will be re-instated in its original position. So basically - if at all possible, avoid edit operations with frozen clips.

Your device could listen out for MIDI Start/Stop/Continue messages, and get Cakewalk to send out those. This is set per project in Preferences->Project->MIDI

Make sure you've set your power scheme to "High Performance".

If you left click on the plugin within the rack, and hold the left mouse button down, you can press the del key to delete the plugin. The quickest way to do this I find is: - Right click the fx rack header, and "Convert to FX chain" - this then becomes one composite plugin - Click and hold the mouse button on the fx chain and press the del key (as described in the previous answer) CTRL + dragging a plugin will copy the plugin plus all it's current settings to the track you drop it on. @Mark MoreThan-Shaw had the right answer here - use the browser. This isn't an error. The FX rack just doesn't support multiple selection. If you need to move all the plugins, either: 1. Clone the track with FX 2. Convert the plugins to an FX Chain first, and move/copy that. You can either leave it as an FX chain, or "Extract FX Chain Plugins" to separate them out again.

This is what the arranger is for. Create an arranger section covering your chorus. You can then record an intro after it, or a verse in whatever order you want - then create an arranger section covering each section. Once you've got your sections recorded, drag the sections within the Arranger Inspector to an arrangement. You can preview it to see if it works - if it does, committing the arrangement will re-arrange the project to match your arrangement. You can also create multiple arrangements to test each one out to see which works best before committing. The example below is just using one track, but it'll work with a complete project with any number of tracks:

Check your "Clip Tail Duration" within Preferences->File->Audio Data. This determines how much extra time of audio is added to account for things like reverb tails etc. When set to 0.00, the bounced clip should be the same length as the original - any other value will result in a longer clip.

Have you updated Melodyne since you saved those projects? When you have un-committed Melodyne Region FX in a project, the Melodyne state is stored within the project folder. The state files are binary files grabbed directly from Melodyne. Sometimes updating Melodyne to a newer version will make those files incompatible - AFAIK, they don't guarantee backwards compatibility with their state files. The best practice is always to render your Melodyne effects. You can always copy and archive your tracks before you apply Melodyne if you want to go back to its previous state.

The only way I can see this technology working is if VST3 developers modify their existing algorithms to take advantage of these new API's. Whether they'll do this or not is anyone's guess. The way VST's work is pretty simple from a high level: The DAW prepares an un-effected audio buffer in memory, and passes it to the VST. The VST then does its processing and passes the effected audio buffer back to the DAW. This buffer then gets passed to the next VST, and so on, until is ready to be mixed with all the other tracks in the DAW. Obviously there's some delay compensation logic in the DAW to ensure the buffers are all processed at the correct time, but apart from that, it's the VST's that are doing all of the heavy calculations. The current functions in GPU's are more generally suited to large matrix transformations rather than pure DSP functions. Perhaps GPU Audio have found a way to leverage the GPU functions in a way that is more suitable to DSP - but as I said, this is more a thing for VST3 developers to deal with rather than DAW developers.

Check your template folder within preferences, and then navigate there within Windows Explorer to check the template files are there: If you've changed the template locations, you can copy the templates from the default location (shown above) to your new location. If this still doesn't fix the problem, delete the following file before opening Cakewalk: %APPDATA%\Cakewalk\Cakewalk Core\Offline.html

You also need to make sure your track automation is selected when moving your clip data. This can be done either via the select module (in large mode), or the track view menu: If you also want bus automation to be moved along with your tracks, I find the easiest way is to create an arranger section that covers the area you want to move, then move that section making sure "Select Events with Sections" is enabled.

Yes, I think the SY77 is not receiving program changes while in Multi Mode. IIRC, my TG500 ( the rack version of the SY85) is the same. In reality, it shouldn't be a huge issue. All it means is that you need to set up the sounds on the SY77 first. Of course this means: 1. You're limited to 16 sounds - one per channel. 2. All of the sounds will share the one effects block, so you'll need to be clever in the way you set your effects up. In the past, I've done this by using one reverb/chorus effect for most sounds (adjusting the send A/B for reverb & chorus accordingly), and one "speciality" effect for a particular sound that needs it. 3. The SY77 will continue to receive note/CC data on the separate channels, so you can click on a track to change sounds - but it'll be the sound you've pre-chosen for that channel.

This is a long shot, but.... have you checked if MIDI control is enabled in your Keyboard Bindings? It could be a MIDI note triggering the "Open Soft Synth on Current Track" command. Another long shot could be something triggering X-Ray.