msmcleod

Did the "No Cakewalk Project Loaded" message come up when you first closed the project? There's only two circumstances that the faders go back to zero: 1. When Cakewalk goes back to no project loaded; and 2. When the Control Surface DLL itself is closed down. From what I can see in the code, the only reason it would not return to zero is if Cakewalk though the MCU had actually disconnected (in which case it wouldn't receive the messages anyhow). There is maybe another reason however... if the project itself didn't actually close, or Cakewalk itself didn't close, due to a plugin not closing down properly. I experienced this myself the other day with this: https://discuss.cakewalk.com/index.php?/topic/2947-solved-cakewalk-not-shutting-down-when-using-overloud-th-u/ If you check in Task Manager, is Cakewalk still running as a background task? [Edit] - One more question: What MIDI mode are you using (i.e. UWP or MME) ?

When I "donated" my second monitor to my daughter, I thought it was a good time to get used to using just the one HD monitor. The idea being, that if I swapped to using my laptop, I wouldn't feel restricted in any way in my workflow. The key thing for me is to have a screen-set for each operation. It varies from project to project, but the basic idea is: Screen-set 1: Everything on it, but browser & track inspector minimised Screen-set 2: Console view full screen; no browser, track inspector minimised Screen-set 3: Track view full screen; browser & track inspector minimised Screen-set 4: PRV full screen Switching to a screen set for the function I want, means nothing is ever cluttered, and my workflow is sped up. I guess lenses go a stage further, but I've never felt a need for them myself - quite the opposite - when I open the control bar I like it to be exactly the same each time.

Fantastic - so glad it worked out for you.

I'm not sure if it has to be honest. Although in saying that, I don't think that MixControl or the driver will work with the older firmware. You should have had some sort of prompt when installing the drivers or starting MixControl that it was upgrading the firmware. If not, you can run the firmware updater: C:\Program Files\FocusriteUSB\ScarlettDfu.exe My firmware (on my 18i20 anyhow) is saying v1056. I'll check the version on my 6i6 as soon as I can. [EDIT] - my 6i6 is showing firmware version 1056 too.

Before you do that... just in case this works, try deleting AUD.INI from %APPDATA%\Cakewalk\Cakewalk Core I found after changing settings, or re-installing drivers, this can get corrupted. CbB will recreate it the next time you launch. Oh - and if you do upgrade your firmware/mix control to the beta version, you'll still want to delete AUD.INI, so that CbB can generate it with the new driver settings.

One thing you *could* try is upgrading your 18i8 to the latest beta drivers. A big warning though - this is a one-way process! Once you've upgraded, you're stuck with the latest version, and there's no way of reverting. I've upgraded all 3 of my Scarletts, without issue, but the risk is still there. The latest beta version is Scarlett MixControl 1.10b3 (it should be top of the page here: http://beta.focusrite.com/

I have to agree with Byron here. I've got a 18i20, a 6i6 and a 2i2 - all 1st gen, and all working with CbL (on different PC's) with a latency of 1.5ms. I hardly get any dropouts, and if I do I just up the ASIO buffer size. So, a few somewhat retorical questions... 1. Are you using ASIO, and if so what is your buffer size (drop-outs would indicate it's too small and needs increasing). If you're not using ASIO, you should be - it's gives by far the best performance and the lowest latency. 2. Are you connected via a USB hub? If so, make sure it's connected directly to it's own port - you don't want your audio interface to be sharing a USB port with anything. 3. Are all your motherboard drivers (esp. USB drivers) up to date? 4. Are you connected to a USB-3 port? If so, try connecting to a USB-2 port instead.

To be fair, I mentioned that I use L2 for interm mixes, and razor7music mentioned OneKnob Louder with some pretty heavy caveats... that's hardly a recommendation. I believe I mentioned that too... I do agree with the rest of what you said though. Cakewalk provides more than enough to do the job.

When I moved from 4 track (Yamaha MT1X) to 8 track (Yamaha MT8X) I used the JLCooper PPS-100, just cos it was the only one available 2nd hand at the time. I remember it blew me away when I fast forwarded half way through a song and it just played exactly on time. I did find it worked best with an Alesis DataDisk though, rather than with a computer based sequencer. On the 4 track, I just played guitar live alongside the "live" keyboards coming from MIDI. This gave me a track for vocals, and another for backing vocals/guitar solo. I'd put effects on the vocals on mix-down. I didn't really bother with audio in the box until Pro Audio 7 came out, which I bought because it supported the DS2416.

Aha - found the issue. I was running v1.0.0 (I got it as soon as it came out). v1.0.4 fixes the issue.

Thanks for that Lynn - it's obviously something peculiar to my setup . Strange it's affecting both my laptop & desktop though... I'll need to dig further.

It's always prudent to make backups. I'm not sure what would cause a beeping sound though. There were some bugs that were later fixed when dealing with the track compressor - maybe that was the issue? I always make a backup of my MackieControl.ini, simply because it took so long to arrange all my EQ & Dynamics plugins into some consistent layout. It's worth mentioning though, that neither Cakewalk's, Azslow's or my version of the MackieControl surface dll alters MackieControl.ini in any way - it just reads from it.

I think this is it: https://www.windowscentral.com/how-allow-blocked-apps-ransomware-protection-windows-10-october-2018-update I'm unsure how this would affect ProChannel settings as to me it seems totally unrelated... in saying that, this is Microsoft, and nothing would surprise me.

It works every time for me. Luckily I'm not in the habit of routinely dragging Audio tracks on to MIDI tracks. This will crash every time on 4.2.x if you've not created a region FX first.

That was the logo on the first version I bought - Pro Audio 7. I was swapping between Cakewalk Express / Music-X (Amiga) before then. I think Pro Audio 7 was the debut for that logo: Before that it looked like this: I must admit though, I personally prefer the current logo.

v4.1.1.011 works perfectly for any later version, (e.g. 4.2.x) you need to create a region fx before doing any operations.

Cakewalk could mitigate this to some extent by asking the user what "level" he/she is at when installing (e.g. beginner, intermediate, advanced), and setting the default lense accordingly. The Basic lense is much less intimidating for newbies. In general though, my main criticism of the Cakewalk UI (from a beginners point of view) is that there's so many almost-hidden features... it's not always obvious that the buttons have a right click menu, or that a slight change in the icon is actually an indication of a huge difference in behaviour (e.g. record mode). Once you know it though, it's absolutely fine.

Any 32 bit version of Windows. Not to be confused with Win32S, which was a bundle of laughs. A 32 bit O/S with a Windows 3.11 interface. I used it for a bit to upgrade get some Video for Windows based apps ready for Win 95 in the mid 90's.

OK, this is definitely a TH-U issue. Using VST-2 instead of VST-3 makes no difference - Cakewalk still stays running the task manager. If I set the VST-2 to load with JBridge, then JBridge's AuxHost stays active in the task manager after shutting Cakewalk. I've just tried TH-U with MixCraft, and it stops MixCraft from shutting down. The only thing that seems to work is disabling VST-3, using VST-2 with JBridge and having the "Dirty Close" option checked.... that or going back to TH-3.

I had a project that was leaving Cakewalk active as a background process in Task Manager. I've narrowed it down to Overloud TH-U. Using TH-3 instead seems to solve the problem (luckily I'm using a patch that is in both versions). Has anyone else seen this behaviour?

I can't see myself ever wanting to use this - it just looks like an alternative GUI for a sound browser. I find this new product a strange one to release... IMO AD2's biggest competitor is SD3, which is an amazing product. I'd have thought they would want to release an AD3 to bridge the gap.

Coming from a traditional tape recording background, I still find it tempting to record as loud as possible. This made sense when tape was noisy and we needed to minimise the signal to noise ratio. The thing is, in the digital world this is probably the worst thing you can do, as you're completely destroying any headroom and severely limiting your dynamic range. If your mixes sound good, but they're quiet, then that's probably a good thing. 24 bit digital recording has a huge dynamic range, but this is extremely limited if everything is close to peak. If you need it louder during mixing, turn the volume knob on your amp/monitors up. Now obviously when you get around to distributing your music, you don't want it that quiet, hence all the advice on mastering. I'd treat mastering as a separate process. Take your "quiet" mix as a stereo pair, put it in either a new project in Cakewalk, or use an audio editor such as SoundForge or Audacity and use something like Ozone to master it. For interim mixes (i.e. when my project isn't finished, but I want others to listen to it), I'll quite often temporarily stick Waves L2 on the master bus and wack it up as far as it'll go without "pumping" (you can use Cakewalk's Boost11 as an alternative).

The nanoKONTROL comes with software to define what CC messages it can send out. Each set of CC mapping is known as a scene. You can have up to four scenes.The "Scene" button on the original nanoKONTROL is used in conjunction with the cursor buttons to go from one scene to another. To be honest though, I'd keep things simple and ignore the scene button for now and just go with whatever it's configured to as is. You need to get Cakewalk to "learn" the CC mappings for each of Cakewalk's operations: I found some old instructions here (it's really difficult to find ANY information on the original nanoKONTROL !): https://web.archive.org/web/20180227221018/http://untidymusic.com/midi/setting-up-nanokontrol-sonar here's a video about ACT:

MMcL Mackie Control #1 is the one you should use. The XT is only for the Mackie Extender, and the C4 is for the Mackie C4. Note: All the instructions in the original MackieControl.chm help file still apply - the pdf just covers the extras included in the MMcL version.