msmcleod

Map the Left/Right keys to "Start/Stop Rewind" / "Start/Stop Fast Forward":

There's no single operation to delete them all, but you can do it this way: 1. Right click -> Convert to FX Chain 2. Press the Del key That's one mouse click and one key press. I can't see how doing a multiple selection / deletion would be any quicker.

Cakewalk needs to be re-activated at least every 6 months. Normally, updating Cakewalk from inside the application will automatically refresh activation. If you don't refresh activation, after 6 months you'll still be able to use Cakewalk, but Save and Export will be disabled. Because Cakewalk is now free, we have no sales figures to refer to, so activation is the only way we can keep a track of how many active users we have and what version they are running.

This is not strictly true - The correct way to chain MIDI hardware is by connecting the midi Thru from synth X to midi in on synth Y. Some synths have a "MIDI Out as thru" or merge function that merges MIDI Out with MIDI In, which allows the MIDI Out to act somewhat like a MIDI Thru. However, there are differences: MIDI THRU - echo's exactly what came in on the MIDI IN port MIDI OUT (with no thru/merge function) - only outputs what this particular synth is sending (i.e. what you're playing on the keyboard), anything that came in on the MIDI IN is not sent out. MIDI OUT (with thru/merge function) - outputs exactly what came in on the MIDI IN port as well as anything you're playing on the keyboard. Obviously, if you're not physically playing anything, in this mode its essentially the same as MIDI THRU, but be aware that some MIDI data may have been filtered out or re-ordered. You should also be aware of cable length limits when chaining synths in this way, especially when using MIDI THRU.

To be honest, I'm sceptical about relying on such information in this particular use-case. The fact that Cakewalk is saying that the files are missing even though they're not, would indicate the part of project that stores information about the clips has been corrupted, so there's a very good chance you couldn't rely on any other clip information as this may well be corrupted too. A better question would be how it got corrupted in the first place. Although it's possible it could be a Cakewalk bug, I suspect it's more likely to be a plugin overwriting memory it shouldn't be - else we'd be seeing reports of this all the time. If you want a bullet-proof backup of your audio files, maybe consider exporting the clips as broadcast waves using the Export Dialog, and using a filename such as {projectname}-{tracknumber}-{laneindex}-{clipindex}-{trackname}-{clipname} It should then be easier to drag these back into the project if necessary.

@Adam - I think I've found a workaround: 1. Make sure the Selection Module is showing as either medium or large 2. Set "Display all times as SMPTE" to checked within Preferences->Customization->Display 3. Create arranger sections for all the sections you want to export 4. Click on an arranger section, so it selects both the section and the events underneath it 5. Copy the selection start/end time (shown in blue below) to the video track start/end time (shown in red below): 6. With the selection still active, export your video 7. After exporting, set the video start time to 00:00:00:00 and the video end time to the time shown in green above. Repeat for each section. I'll make a suggestion to the team that we incorporate this somehow into the export, so this can be done for multiple sections in a batch, or at least be able to do it per section without manually having to edit the video start/end time.

Keyboard shortcuts don't use the character that pressing a key shows, instead they use the actual keyboard code sent from the keyboard itself. Keyboards designed for different countries may result in different codes than the ones you might expect. For example, UK keyboards while close to US keyboards, give different results on certain keys. The only sure way to find a particular key is to use the "Locate Key" button on the keyboard shortcuts screen and press the key you want to map.

For some weird reason this CTRL + ALT + L didn't work for me.... CTRL + ALT + M (which cycles through the magnifier views) did though. You're right though - Lens view is the one to use.

The Help Module is context sensitive and will show a summary of the control you're hovering over. Pressing the "Y" key will bring up the help module. Pressing F1 is also context sensitive, but will go to the overall section that control lives in ( e.g. Tracks View, Clips View, PRV etc ). This is built into Windows. Press Windows Key & "+" key to enable it; Windows Key & Esc to disable it. If you just want finer control, holding the SHIFT key when moving a control will move it at a much finer level. If you don't want something docked, un-dock it, close it and save as a custom workspace. Alternatively just hit "D" to hide the multi-dock. We'll consider this.

Maybe a plugin on your master bus that has reverted to demo mode? Major Windows updates can cause this with some plugins. Try exporting with your FX bypassed - it the problem goes away, enable FX again and disable each plugin one by one to track it down.

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