msmcleod

It's the track properties tab, not the inspector itself... so: CTRL + SHIFT + I toggles between the Track tab and no tab selected CTRL + I toggles between the Pro Channel tab and no tab selected SHIFT + I *should* toggle between the Clips tab and no tab selected, but instead it just switches to the Clips tab and won't toggle back.

Normally this means your MIDI prepare buffer is too small. The default is 250, so consider increasing it (I normally use 750) Another issue could be your Driver Mode (see top of image). Not all MIDI interfaces play well with UWP, so if you are using UWP consider using MME (you'll probably have to close your project to change this).

I agree with @bitflipper - the sound cutting out every 1.5 secs sounds suspiciously like a plugin that isn't authorised, and given that some plugins use hard disk serial numbers as part of their authorisation, swapping to a new drive may have de-authorised a plugin. If you're using something like Sonarworks Reference, it may not even need to be in your project if it's working at a system level. If it was a CPU problem, I'd expect the playback to stop rather than go silent for a bit and carry on. As bitflipper says, you normally hear pops & crackles with high CPU load. Another possibility might be that you've got some synth sending MIDI data out somewhere and automating the output of one of your plugins somewhere? I'd start by bypassing all effects. If the silence has gone, then introduce each effect one by one until you find the one that makes the issue come back. If the issue happens with all effects bypassed, try muting all the tracks and bring each track back one by one.

Email notifications seem to be working fine for me. I definitely get email notifications for PM's. For particular posts however, you have to be following the post to be notified by email. Depending on what your settings are, this either means clicking the "Follow" link up at the top right of the topic, or having automatic following set up. You also have to ensure you've set the appropriate options up in your account's notification settings:

This is more likely the cause of both Sonar not shutting down AND the file handles not getting released. Are you using any 32 bit plugins under BitBridge? If so, try using JBridge instead and if necessary check the "Dirty Close" option to force it to close down. Also, check your plugins are up to date. I had exactly this issue a while back with TH-U causing Cakewalk not to shutdown. Upgrading to the latest version of TH-U fixed it (actually, thinking about it, this might have been the cause of the incident I mentioned in my previous post). If you do suspect a plugin: Open the smallest project that exhibits this issue and take a note of the plugins you've used. Reboot your PC Create a new project, adding them one by one, saving then closing down one plugin at a time. At some point you'll find out which plugin is stopping Sonar from closing, allowing you to investigate further. Finally, if you update a plugin, make sure you do a fresh VST scan.

I've noticed this in the past. From what I could tell at the time, it was the last file that Cakewalk wrote to. Just opening up a new project cured it for me. One thing that you might want to try is rather than closing Cakewalk, try closing the project first (so it shows the start screen again), then close Cakewalk - is the file still locked then?

+1 to this. Although what you can do already, is drag/drop the project from the media browser into your existing project. There's a couple of gotchas... 1. It will import all the tracks, so you'll need to delete the ones you don't need 2. Instrument tracks are split into separate Audio & MIDI tracks, and can be tricky to wire-up again if you've already got a fairly complicated existing project.

I almost never use pitch correction on my vocals, but quite often do on guitar. I’ve got a 1/2 size cheap thing I use to get ideas down, with pretty bad intonation (all my decent guitars are safely locked in my studio). Melodyne is great for cleaning the pitch up.

@Mesh - you could try using ASIOLink Pro, setting it's ASIO device to your 2i4. This cured the problem for me on my 6i6, and didn't add any additional latency. Details of the download are in this post:

You could try doubling or tripling the part, and alter the timing slightly for each so the attack is blurred. This should also make the sound bigger as more parts are playing at slightly different times.

I've started to use comping much more nowadays with guitar. I tend to record every other phrase in one take, then the other phrases in another. I don't know if it's old age making my hands stiff, or lack of practice, or (most probably) both... but comping certainly helps. Funny thing is, solo's are fine. It's just moving between certain chord shapes I struggle with nowadays.

If you're using a soft synth,I find the easiest way is just to freeze the track. You can either leave it frozen, or copy the rendered audio to a blank audio track. For real hardware MIDI devices though, @bitman is correct - you need to record the output of the synth to an audio track in realtime.

Melodyne MAutopitch is similar to how the original AutoTune used to work, and also how IzoTope Nectar works... It basically works automatically, so there's no editing. What you can do however, is use automation to change the intensity of the effect, or whether it's on or off at all at various sections. Another way of using it, is to use the select tool to select the area you want corrected, the use Process->Apply Effect from the menu.

I've found using bounce to clips on the whole track DOES work, but only once I've minimised the take lanes. It seems to behave differently when the take lanes are visible. [Edit] - I was doing exactly the same with audio tracks earlier today. I had exactly the same reaction as you, in that I was sure it worked before... so maybe something has changed in behaviour since the latest update. But anyhow, minimise the take lanes and see if it works for you.

I have one of these velcro'd to the wall, next to the "vocal booth" (aka padded corner of the room) in my studio: They're only £35 - £40, and gives me control over most of what I need when doing a vocal take. It's also fun watching my daughter freak when the MCU faders move "on their own" when I move the nanoKONTROL 2 ones.

I always disable hibernation on my PC's, which also disables hybrid sleep too: For those who don't know the difference: Sleep - Put's everything into a kind of standby mode, using a trickle of power to keep the machine on and the memory contents alive. If you're on battery though, it'll eventually die. Hibernate - Dumps your current memory state to disk, and powers off the machine. When you restart, the memory state is restored from disk and you're back to where you were before hibernating. On Windows 10 machines, the default for powering off is actually to hibernate - not turn off. Restart actually does a full reboot. Hybrid Sleep - does both. It dumps your current memory state to disk AND keeps your hardware in a standby mode. It's much quicker to power back onfrom this mode, and if you get a power outage, it acts as if you've done a standard hibernate. Some USB hardware goes through a kind of restart when it "recovers" from sleep or hibernate (bear in mind that the USB hardware has its own internal memory, which Window's can't save when you hibernate). On wake up, the devices state is then different from what the Windows driver thinks it should be, and is the likely cause of issues with coming out of hibernation/sleep. Hibernate isn't all bad though. I'll quite often re-enable it on my laptop if I'm going to be using on battery for extended periods. Laptops will automatically hibernate when the batter is low, so at least if the battery dies I've not lost my work.

ASUS allows browsing to a BIOS image on an attached HD - does AsRock allow this too?

The DX plugins are at least 64 bit though... they have to be else they wouldn't work at all. Although in the DAW community, they're often seen as "legacy", it would be more accurate to say that they're just not popular anymore - i.e. VST has simply won the plugin format war on PC's. Windows still uses the same underlying technology in its media stack for its media players, and a bunch of video editors still use DX technology.

FWIW I've got the 1st gen 6i6. It works fine for me with a buffer size of 64 (1.5ms), and for very light projects I can go to a buffer size of 32. This is on an old 3rd gen i5 at 3.4Ghz with 16Gb of RAM. I've not experienced any slowdown or crashes for several years, with the exception of the old Melodyne crashing issue (which had a workaround to avoid it). On an i7 with 24Gb of RAM, you should easily be able to run at an ASIO buffer of at least 128, or 256 if you've got hundreds of plugins. Are you using any "lookahead" plugins in your project (e.g. linear phase plugins) ? These sorts of plugins are designed for mixing only, not for recording. Using them will introduce a fair amount of latency (especially with a large buffer size) as they have to read in "x" number of buffers ahead of time to process. This may explain the slowdown. Another possible cause could be bad video drivers, which could explain both the slowdown and the crashes. Another possibility could be bad memory sticks, which I've personally experienced - and it's a nightmare to diagnose. Even mismatched memory sticks can cause crashes (e.g. different makes or different speeds).

Sorry for the late reply on this, and apologies for the link to midiroute - I missed the fact that the project had been discontinued. A good (probably better) alternative to midiroute is MIDI-OX. You can download it here: http://www.midiox.com/ Instructions are as follows: (note you can press CTRL + F5 on your browser to force the animations back to the start) 1. Make sure you've installed both loopMIDI and MIDI-OX. 2. Click on the loopMIDI tray icon, and configure it as follows: 3. Start MIDI-OX, and configure as follows: 4. Within Cakewalk, make sure your MIDI keyboard IN/OUT are now unchecked within MIDI devices; check the "Keyb loop MIDI IN" device in the MIDI Input section, and check "Keyb loop MIDI OUT" device in the MIDI output section. NOTE: Don't check the "Keyb loop MIDI OUT" MIDI IN device, or the "Keyb loop MIDI IN" MIDI out device - else you'll get a feedback loop. Just remember, MIDI IN is for MIDI IN and MIDI OUT is for MIDI OUT: Now you can use the "Keyb loop MIDI IN" for your MIDI input device in both Cakewalk & Finale, and "Keyb loop MIDI OUT" as your MIDI output device in both programs too.

This is very strange. It's almost as if for Sonar mode, they've actually not implemented an MCU at all, but instead the VS-700. From what I can see, the VS-700 display works differently from the Mackie one, which is perhaps why you're seeing this behaviour in Sonar mode. From comments in the VS-700 code, it looks like the fader implementation on the VS700 is based on the Mackie one, so they kind of speak the same language with regard to faders. There's no Zoom function on the VS-700, so nothing is implemented in the VS-700 control surface DLL to handle zoom. On the original MCU there's a bunch of buttons that send out certain messages. To get around the differences between DAW's, they provided overlays that corresponded with the different functions each DAW had implemented for those buttons. For other control surfaces (which usually have much less buttons), they had different "modes" which essentially changes the button you're pressing so it matches what the corresponding DAW is expecting for that function. Given that the Platform-M is very light on buttons, you might get away with picking another MCP based DAW preset (i.e. that actually uses the MCP protocol for the screen, rather than pretending to be a VS700). Can you try setting it to another preset (Reason looks the closest) and see if it works any better? [Edit] - The reason why I ask, is that if the display is working ok, I should be able to get the other buttons working with a few modifications. I'll then add a "Platform-M mode" checkbox to the MackieControl panel.

As far as I can see, yes. I've had zero problems with Melodyne 4.2.1 & Cakewalk 2019.5.

Ok, I've been hammering my space bar for the past 20 minutes. Here's what I've found... Focusrite ASIO: I can reproduce the buzz maybe 1 times out of 100 start/stops. It makes no difference if Windows is using the device as the default or whether Windows is set to using the motherboard device. WASAPI: Cannot reproduce, however WASAPI isn't an option for me. Latency is terrible. 12ms was the minimum that would cope, whereas ASIO was 1.5ms. Also, not all the inputs/outputs show up. ASIOLink Pro, using Focusrite ASIO as its primary device (with Cakewalk set to use ASIOLink Pro): Cannot reproduce. So I'm pretty sure it's the Focusrite ASIO driver. Maybe the ASIOLink Pro device is either different enough in its implementation to hide the issue, or gives enough of a timing difference to hide it. Here's the weird thing though... on previous occasions, I had to stop/restart the audio engine. This time around, just stopping/starting the transport solved it. As I've been routinely restarting the audio engine whenever it happens (which in normal operation is not often), I'm not sure when this change happened - but it certainly makes it less serious IMO.

I'm seeing it on both a 1st gen Scarlett 18i20 & 1st gen Scarlett 6i6 (on two separate machines), both in ASIO mode. It is very infrequent, so much so that it don't consider it much of an issue... especially since stopping/starting the audio engine cures it immediately. I'm pretty sure you're correct in saying it is a driver issue though. I think I may be able to reproduce it just by stopping / starting lots of times, so I'll switch over to WASAPI for a while on my 6i6 setup and see if I can reproduce it. Another option would be to try using the ASIOLink driver, acting as a wrapper for the Focusrite one. I didn't notice any difference in latency when using this, and only a very slight increase in CPU. Maybe it handles calls subtly differently, which might be all it needs. [Edit] - I just noticed my earlier post in Feb, where it was happening more frequently. I sometimes have my Focusrite set to being the Windows sound device, especially if I'm following a tutorial... maybe this might make a difference. I've not being doing this as much lately, which is maybe why it's not happening as much? The next time it happens, I'll make a note of whether Windows is using the Focusrite or the motherboard sound device.

What about your USB sleep settings? You should have everything set to sleep "never". BTW sometimes windows updates have a nasty habit of resetting these.