msmcleod

A common reason for pedals not working is because it's been set as a SHIFT key within keyboard shortcuts. Within the Preference->Keyboard Shortcuts, change the CC from 64 to something else, and uncheck "Enabled" at the top:

Looks like small error in the logic - if you happen to have a loop end time that is smaller than the punch out time, it'll use that. Easiest way around this is to set the loop end time to your punch out time ( shouldn't matter if looping is enabled or not).

That's the comping tool you're using, and it looks like your lanes are not identical, which is likely to confuse it. Have you tried just pressing "K" to unmute them?

Not really. I've had to do this in the past when I moved from hardware synths to VSTi's. What I did was: 1. Add the instrument tracks with the synths I wanted in the same order as the existing MIDI tracks 2. Selected all the original MIDI tracks 3. While holding down SHIFT, drag the first clip on the first original MIDI track to the first instrument track. 4. Deleted the MIDI tracks. Another way of doing it is to insert your synths without creating corresponding MIDI tracks, then just set the output of your MIDI tracks to those synths. You could then select each MIDI / Audio track pair, and make them into instrument tracks one by one, but this step isn't strictly necessary.

Select your tracks, then choose "Selected Track Outputs" from the Track View "Tracks" menu:

Normally holding down CTRL will group assign everything.

The option to show/hide controllers in the clips view will be available in the next main release. The controllers will also be drawn slightly darker with the notes appearing on top at their current colour, so the notes will be far more visible.

I'm not sure how you've set up routing to this synth, but it sounds like there's some MIDI feedback going on. Check that none of your synths have MIDI out enabled unless you really need it, and restrict the MIDI input on the Z3ta track to only what you need.

What you're seeing there are CC events - not CC automation ( sorry to be pedantic! ?) Having an option in the Track View "View -> Display" submenu to show/hide CC's is certainly doable. I'm not sure having it per-track is a good idea though. Firstly, none of the other options are per track; and secondly, it would be really easy for a user to forget they'd switched it off on one track and wonder why their controller data is being shown on some tracks and not others. As a workaround in the meantime, you could always switch the track filter to "Notes".

You really don't want to be using the "Balanced" power scheme. If there's a "High Performance" scheme, use that one - better still, create your own with CPU min & max set to 100%, and any "turn off device after.." set to never.

You could try stopping / restarting the audio engine:

The two separate options are only available in specific circumstances: On per-output instrument tracks On instrument tracks that have other MIDI tracks feeding their synth

Process -> Length certainly does, and it'll do any articulations, and track envelopes (if selected) as well. The stretch tool only does notes + CC's, and not track envelopes.

I certainly use Split at Time - if I need to split at selection, I'll use the split tool and just drag the selection while the split tool is active (i.e. ALT + drag across the clip with the smart tool). If I need to split over all tracks, I'll normally just create an arranger section then right click->split at boundaries.

The easiest way would be to stretch the MIDI clip to 50%, then change your tempo. CTRL + SHIFT enables the stretch tool, then just drag the right edge until it reaches 50%: Alternatively, just select all your MIDI clips then from the main menu Process->Length, check Start Times & Durations, set to 50%, and uncheck "Stretch Audio".

It occurred to me I must stress that many of the registry entries (especially the plugin inventory) also contain absolute paths to the files in the file system. For backup/restore purposes on an existing install, this shouldn't be an issue, but if you intend to restore the registry on a different machine or fresh install you should take care to ensure that any paths held in the .reg files are correct for that machine. The best way to make sure that this is the case is to make sure you install everything to the same location on the fresh install. In saying that, VST locations are actually less of an issue, as the next plugin scan should update the location as it re-scans each plugin, but you should be careful to ensure you don't have duplicate copies of plugins.

Your spec is slightly better than my older ASUS ROG laptop, which copes with some quite demanding plugins, so I don't think an upgrade should be necessary. I take it you're running with your power mode set to high performance mode, and CPU min/max are both set to 100% ? If not, that could be the cause. Next, I would try disabling plugins one by one to see if you can identify if there's one in particular which is causing the issues. I would also recommend downloading and running LatencyMonitor to find out what other things may be taking up CPU cycles. FWIW I'm able to run my Focusrite interfaces at a buffer of 64 without any issues at all, even with a modest set of plugins.

%APPDATA%\Cakewalk\Cakewalk Core is where some of the settings are, the most important ones being: AUD.INI, Cakewalk.ini, TTSSEQ.INI, ctrlsurface.dat and master.ins If you use MIDI learn with control surfaces or your keyboards knobs/sliders, you'll also want to back up %APPDATA%\Cakewalk\ACT Data A lot of the options in Cakewalk itself however are in the registry, under Computer\HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core Your plugin inventory is stored under Computer\HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST X64 Control surface presets are stored under Computer\HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\ControlSurfaces\Presets You can export the relevant parts of the registry using regedit.

The downside is increased latency - i.e. if you've got a soft synth, and you play a note on the keyboard there will be a noticeable delay between you playing the note and the note sounding. This isn't really an issue when mixing, but can be an issue during recording. The pops and crackles are a symptom of your CPU not having enough time to do all the processing of your audio & plugins in time for it to be output to the audio interface. Increasing the buffer size, gives your CPU more time to do the calculations. The general advice is: For recording: Use a small to medium buffer size of 64, 128 (or 256 at a push), using a minimum amount of plugins - and certainly no look-ahead plugins. For mixing: Increase the buffer size as needed Freezing tracks can also help free up CPU cycles, which can be useful if you need to overdub later in the mixing process, or increasing the buffer size no longer helps get rid of pops & crackles. The other option for recording later in the process, is the FX bypass button on the transport. This disables all fx plugins allowing you to reduce your buffer size for your recording.

Yes, it is the wave shell that is causing the re-scan every time. I suspect the toasts not closing are a result of the project loading a synth that is also being scanned at the same time. There are few ways around this ( in order of preference ): Switch to manual scan - unless you're constantly installing new VST's, there's really no reason to have scan on start-up or automatic background scan enabled; or Wait until the scan is finished before loading the project; or Turn off scan in sandbox ( I wouldn't really recommend this one though ).

This will do it - changing USB ports can cause Windows to treat it as a new device. To avoid this, I normally always plug the devices in the same ports and ensure I power up my PC with them all plugged in. The ensures that not only do they keep their device name, but their ordering remains the same ( less important for MIDI Out in CbB, but is important for MIDI in).

This isn't a bug - it happens when "Split MIDI Notes" is enabled. When enabled, any notes or active CC's are retriggered at the split point. The primary purpose of this is to support arranger operations, so that the status of any CC's at that split point are honoured regardless of where a section is moved. Turn off "Split MIDI Notes" and you won't see this behaviour.

The HUI protocol has been deprecated for a long time. If a genuine Mackie HUI comes up on the second hand market at a reasonable price, I may get one and improve the HUI support... but until then, we don't plan on doing any other improvements.

Things to try: 1. Turn off the splash screen in Melodyne 2. Make sure you've got a default algorithm set You may want to run it as standalone first to do this.

Have you enabled "Select Events with Sections" ?