msmcleod

For trailing notes: If none of the notes end within the section end time + overlap threshold, then the notes will be split at the end of the section. However if one or more notes end within the section end time + overlap threshold, then any other notes after the threshold will be cropped at the threshold limit. Clips cannot be slipped on a note by note basis, so it keeps as much of the note duration as it can. For leading notes: Leading notes that start before the overlap threshold, but end after the section start + threshold will be cropped at the section start. It's worth pointing out though, that although the logic does its best to ascertain which sections notes belong to, it cannot possibly get it right every time. There's no way an algorithm can work out the musical intent of your notes. The larger you make your overlap threshold, the more you should expect to have to tweak the clips afterwards. Personally, I keep my threshold at a tiny amount - i.e. 1/64, 1/128 or 1/256. We did discuss more verbose methods of associating notes to sections, such as being able to individually assign notes to a section. In this case, it'd probably get it right every time, but it would be an arduous task for the user to pick these notes on a note by note basis. So we went with a threshold.

We did this change to make "Insert Instrument" consistent with how "Insert Audio Track" and "Insert MIDI Track" work - i.e. they always insert above the currently selected track. I you want the old behaviour, use the "Add Instrument Track" button:

I did look into this. The issue isn't with Cakewalk, it's with Windows not notifying Cakewalk. Sometimes I can wait around 20secs to a minute before Windows finally recognises the devices have changed. When Windows does notify Cakewalk of device changes, you get a popup dialog right away. Until Windows actually acknowledges the device exists, a refresh button isn't going to help.

Are you looking for a library pre-canned phrases, or just a library that can do a good rock solo guitar sound? If it's pre-canned phrases you're looking for, I'm not aware of any (if anyone does know of any - please let me know!!) You'll probably have more luck at producer loops or a similar loop library provider, where they have a bunch of "toolkit" type samples you can drag into your project and manipulate. However, they're not cheap, and IMO they're very limited in scope. The best results I've had for guitar solos, believe it or not, is from Band In a Box. [EDIT] - Just found one!! : https://www.wesoundhuman.com/collections/kontakt/products/rock-starter-pack it's half price at $49 atm.

You may be able to drag/drop the tracks from SONAR to Cubase (or just export the tracks from SONAR and import them into Cubase) Other than that, there's no conversion program I know of to convert SONAR projects to Cubase.

@NealClark - thanks for reporting this one. The bug was caused by changes to the "Insert Instrument" behaviour to make it consistent with Insert Audio Track / Insert Midi Track - i.e. it puts it before the current track, and if that track is in a folder, the new instrument gets put in the folder too. Basically what is happening is the MIDI part of the instrument track is being put in the folder, but the Audio part isn't. This is causing the move from folder command to fail. We've got a fix for this, but in the meantime if you split the instrument track you'll be able to move the MIDI part out of the folder and re-combine it with the audio track by selecting both tracks and doing a "Make Instrument Track".

@NealClark - I can repro this - I'll look into it.

One the Melodyne trial period is over, you can no longer save edits. The Cakewalk functions that leverage Melodyne, such as Audio to MIDI and Tempo Extraction will continue to work however. Upgrading to Melodyne Essentials, or one of the other versions will allow you to make edits and save them. Certain functionality is limited however in the cheaper versions. The Celemony website details the differences.

There's two functions that do that: Bank Up/Bank Down - move the current track by banks of 8 Channel Up/Channel Down - move the current track by 1 I've checked the code, and the MackieControl is correctly interpreting the HUI versions of those buttons, so you'll just need to make sure they're correctly assigned on the DM2000. I don't think there's anything in MackieControl.dll that would deal with that. However, you could use AZController on that port to map the messages to anything you want - it's complex, but very flexible. @azslow3 has just released a new version today which works better with the 2020.01 release of CbB. The community at http://www.azslow.com/index.php should be able to help you with set up.

CTRL + I - toggle Pro Channel/Track Inspector SHIFT + I - toggle Clips props/Track Inspector CTRL + SHIFT + I - toggle track props / Track Inspector SHIFT + ALT + I - toggle arranger / Track Inspector

CbB does not support sending Sysex to VSTi's.

An explanation of what is going on here: 1. The Clips are being rippled by the amount of "clip" that was removed, rather than the whole section extent. This was an old bug. This has now been fixed and will be available in the next update. 2. The notes being deleted is expected due to the size of the overlap threshold (1/4 note) - i.e. as the notes overlap the section end by < 1/4 note, they're being included with the section when it's deleted. Setting a lower threshold amount (or turning it off), splits the notes as expected.

yes.

No, it's not face in/out - splitting & crossfading does the following (assuming a 5ms crossfade): Splits the clips at the split point (creating two exact copies of the clip, but slip-edited at the split point - i.e. the left clip's end is now at the split point, and the right clip's start is now at the split point). Slip edits the right of the left clip by 5ms, and adds a fade out of 5ms. Slip edits the left of the right clip by 5ms, and adds a fade in of 5ms. I'd recommend using the default 5ms as this works pretty well, but it's really down to taste.

@marled - can you PM me your project so I can try to work out what's going on with the ripple?

This is how "big" auto crossfades should be:

@AdK Studios - can you retry automation with the latest hotfix? Please let us know if you're still having problems with this. We're aware of the "Show Clip Outlines" issue in the Tungsten theme (Mercury theme doesn't have this issue). I'll try to get it bumped up the to-do list. I'll discuss the other issues with the team.

This has been implemented in the latest hotfix:

Turn the ProChannel off, do the freeze, turn it back on again.

This is to be expected. When setting any MIDI device up as a Control Surface, that control surface takes full control over the MIDI device. When adding the ACT Control Surface, the MIDI input & output devices assigned to the control surface will be used exclusively by the ACT Control Surface and cannot be used for standard input. This is true for ALL Control Surface device types. Most keyboard controllers with DAW functions present themselves as more than one MIDI device, where one MIDI Input device is used for standard keyboard functions, and the other(s) are used for DAW functions. So its important to ensure only the DAW function MIDI ports are assigned to the ACT Control Surface. If your MIDI keyboard only has one MIDI output, you can't use it as a standard keyboard and an ACT device at the same time. You can however, assign controls using the "Remote Control" feature of controls such as faders & pan controls. An example of Remote Control (without using the ACT Control Surface) - once set up, this can be saved as a project template for later use: You can also use MIDI messages within Preferences->Customization->Keyboard Shortcuts to assign MIDI keys or controller messages to anything that can be bound to a key (e.g. transport controls). Again, this is without the need for the ACT Control Surface.

I'm not familiar with the new Focusrite Control (my interface uses Scarlett Mix Control). The analog inputs aren't what you need to be looking, you should be looking at what is being routed to the analog outputs. I think this video may help ( around 2:13 talks about hardware outputs )

If it's working in headphones, then it's more likely the routing in the 18i20's mix software isn't set up properly. You need to make sure that "Mon 1" is routed to the hardware outs 1 & 2. Unfortunately I've got an older 18i20 (with different mix software), so showing you my screen-shot probably won't help.

Just turn off track FX in the freeze options. No need to remove or reset plugins.

I occasionally use JamOrigin for converting guitar to MIDI. I've also got a Roland GI-10 (with a GK2A pickup on my guitar). I've got to say JamOrigin does just as good a job (if not better) than the Roland GI-10... although the GI-10 is a bit dated nowadays, perhaps more modern devices work better. Oh and a quick tip - you've got to set JamOrigin to an ASIO buffer of at least 128 for it to work. I rarely use either though, as it's rare I need to actually hear the "MIDI version" of the instrument in real time. Most of the time I just use Melodyne to convert it afterwords. Nothing beats Melodyne.

You can have as many arrangements as you like, but only one active arrangement. You can preview any of the arrangements until you find the one you like. Once you commit the arrangement however, the other arrangements go (because the sections have now changed).