msmcleod

It's also worth mentioning that Midi Export is now selection sensitive, so it'll only export what is selected. As mentioned above, the fool-proof way is to Save As -> Standard MIDI File.

Look forward to that one. @Craig Anderton BTW - I've been collecting your "Musicians Guide to Recording" series, but a few of them seem to be unavailable, particularly "How to Record and Mix Electric Bass" and "Desktop Mastering". Are these still in the pipeline?

Personally, I would avoid USB mics on Windows, the reasons being: 1. You can't use ASIO, as most USB mic's don't come with an output and Windows only allows one ASIO driver to be open at once. 2. You're stuck with the preamp built in to the mic, which may or may not be a good one... but it's never gonna be a Neve 1073. 3. You can't plug it into anything else but a computer. Additionally, if you're using it with other audio devices, there's no way of syncing the word clocks. So even using WASAPI Shared to record from multiple audio devices, they're all going to be misaligned and you'll have to deal with any phase issues by aligning the audio yourself afterwards. An XLR mic gives you way more options, and will be still be useable for decades - way past the point the drivers for your USB mic no longer work on your PC's OS. So unless you're ONLY doing pod-casts / voiceover work, I'd stay clear of them.

I managed to get one of those for a stupidly cheap price from Amazon a few years ago. It's surprisingly good as a guitar MIDI controller, although it does require its own playing technique. I've used it for recording finger style parts with the Ample Guitar M Lite.

When a Meloydne Region FX is active, Melodyne takes ownership of the clip which is why split is disabled. You need to render the Region FX first to relinquish control from Melodyne.

CC's 121 to 127 are Channel Mode messages: 121 - Reset All Controllers 122 - Local Control On/Off 123 - All Notes Off 124 - Omni Mode Off 125 - Omni Mode On 126 - Mono Mode On (Poly Mode Off) 127 - Poly Mode On (Mono Mode Off) For synths that support it, sending CC 126 with a non zero value turns that channel into a mono synth, which is handy for keyboard solos.

Enable auto-crossfade before you start recording:

Realtime guitar to MIDI is always going to be a challenge, especially on lower notes. It needs enough of a complete waveform (or more likely enough several complete waveforms) to correctly detect the pitch, but by that time there's an audible latency. You can get used to it over time and learn to anticipate the notes with a lot of practice, but I suspect that time is better spent getting more proficient at learning the part on keyboard, or even entering melodies via PRV or staff view.

Strictly speaking only CC up to 97 are true CC's. CC's 98/99 are 14 bit NRPN's and should be sent as a pair - same with 100/101 ( 14 bit RPN's). As far as I can tell, they are chased as long as they do come as a pair. 102 - 120 are undefined, but 102 to 119 are chased 121 onwards are reserved for Channel Mode Messages and are not currently chased. It doesn't look like aftertouch messages are chased. I'm not sure why, although I suspect this was due to historical performance reasons.

No, dirty is common computer science term for a file or structure with unsaved or uncommitted changes. https://softwareengineering.stackexchange.com/questions/410262/whats-the-origin-of-the-term-dirty-in-regards-to-unsaved-progress

If the main project is modified, but not saved since the modifications - i.e. there's an asterisk (*) after the project name in Cakewalk's title bar:

I've tried using the GK2A (and also a GK3) with my GI-10, and also the MIDIGuitar plugin - both return mixed results from my experience. I've had much better results just recording the guitar, then dragging the audio to a MIDI track, which uses Melodyne's pitch-to-MIDI conversion. You'll need either Melodyne Editor or Studio to do polyphonic conversion though. Whichever method you use, you should expect to have to edit the results in the PRV afterwards.

On my Asus P8B75V motherboard, my 1st gen Scarlett 18i20 works far better using the USB 3.0 ports than on the USB 2.0 ports, but I suspect his is more to do with what other devices are using the same IRQ as the USB 2.0 port, rather than a USB 2.0 / USB 3.0 thing. Looking at the IRQ assignment in Windows Device Manager, it looks like all USB 2.0 ports are going through the same IRQ (23) - so my trackball, keyboard, USB wifi adapter & USB midi devices will all be serviced by the same IRQ. The USB 3.0 port however, has it's own dedicated IRQ.

Ok, so you're using the on-board audio interface on your motherboard. WASAPI should work fine with that - if it doesn't, make you've got the most up-to-date audio drivers installed for your motherboard.

whatever your sound is coming out of (i.e. what your headphones or speakers are plugged into)

MME is the worst performing driver mode, and is most likely your issue here. Here are the driver modes in order of best performance: ASIO - use this when your audio interface has it's own dedicated ASIO driver (except if it's an onboard Realtek device) WASAPI Exclusive - use this when using an onboard audio device. Performance should be almost as good as ASIO. WASAPI Shared - use this when using an onboard audio device that doesn't support Exclusive mode WDM - for use with very old devices MME - for use with even older devices What audio interface are you using? If we know this we may be able to suggest a solution.

Yes, this is correct - in essence: There is only ever one auto-save file, which is overwritten each time at either the interval, or number of changes. This is totally separate from the versioning. The versioning works for manual saves. So each time you press CTRL + S, it will rename the current .cwp file, giving it the current timestamp, and save your .cwp. Any older versioned files greater than the "number of versions to keep" will be deleted. When an auto-save interval is specified, auto-save won't kick in unless the project is dirty, but as soon as you do change something it'll auto-save right away if the previous auto-save file is older than now minus the interval time.

This is the correct command for switching to the clip gain. The track filter (and the automation lanes for that matter), can show many envelopes - clip gain just happens to be one of them. We added this particular shortcut for convenience, because it's a track filter that is frequently used by users. Others find it more convenient to just add an automation lane.

First of all, unless you need it, you should turn off MIDI Out on the VSTi. This can be done from the VST2 / VST3 menu on the title bar of the plugin UI window. If you do use MIDI Out on the VSTi, be selective about which MIDI IN is selected for that track - i.e. don't set it to None or Omni. If you're using a hardware controller, you should either: 1. Disable the MIDI out to your controller within Cakewalk's MIDI devices, or 2. Turn "local off" on the controller, and use MIDI echo in Cakewalk, or 3. Leave the controller as is, and turn MIDI echo off within Cakewalk. Which option you choose depends on a number of factors, but unless you need Cakewalk to output MIDI to your controller, option 1 is the easiest.

For un-rendered region FX, all cakewalk is doing is saving the Melodyne state along with the project. As long as you're using the same version of Melodyne, it should be safe to have projects with un-rendered region FX. The problem is, AFAIK Celemony makes no guarantees that that state will be compatible with future versions, and it's likely at some point you'll upgrade Melodyne forgetting you have older projects with un-rendered FX. This bit me when I upgraded from Melodyne v2 to v4. Nowadays I always copy the track and archive the original, then render any Melodyne edits to the copy. If I'm 100% happy with the edited track, I'll delete the original.

I've got both a 2-tier stand and a 3-tier stand... it was fine with lighter keyboards, but it always felt a bit unstable to me with heavier keyboards on the tiers. I had my CZ-1 on the lower tier for a while, but it just felt scary. Hopefully you'll be able to get a rugged enough stand to take both. Nowadays, I just put my Korg X5D directly on top of my SL990 and rely on a guitar-style MIDI program change pedal for changing sounds. I've got a bank of sustain pedals and an expression pedal for any further control, and a stool I can sit on at near-standing height so I can use them with both feet without falling over! I used to use a 65W combo amp on a wedge stand, more or less next to me, positioned 45 deg between the back of the stage and to my left. This was usually loud enough to hear without blasting my ears out. I used the same amp & stand as a wedge monitor when I was doing my guitar/singer or bass/singer gigs.

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.