msmcleod

Just remember, unless you've got something to sync the word clocks of multiple interfaces, expect some timing issues. This can usually be done: - by connecting the SPDIF out of one device (the timing master) to the SPDIF in of another, and making it the slave. - by connecting the ADAT out of one device (the timing master) to the ADAT in of another, and making it the slave. - by using a coax wordclock cable fed from one device to another, or from a master clock device to all of your devices. If your audio interfaces have no way of doing this, you may need to nudge your audio clips a bit to line them up properly. In saying that... they may be close enough for you not to notice... but pay attention to any phase issues.

Does the GT-1 actually send audio over the USB ? I'd be surprised if it does. If it does send audio over USB probably could, but I'd be tempted to just stick with using the GT-1 analog out -> 2i2 audio in.

You need to uncheck all references of the Echo Pre 8 within CbB, and use the ASIO Link driver exclusively within CbB instead. You just need to make sure all the inputs / outputs are created & routed for all your devices within ASIO Link. IIRC there is a limit of 64 inputs/outputs in all. The last time I tried this, I noticed absolutely no difference in performance/latency using my Focusrite 6i6 going through the ASIO Link driver vs the native Focusrite driver.

VB Audio has a bunch of utilities to allow you to do this: https://vb-audio.com/Cable/

It might be worth seeing if you can upgrade Kontakt 5.6 to Kontakt 5.8.1 - I'm running both Kontakt 5.8.1 and Kontakt 6 without issue. You should be able to do this via Native Access, but NI has also provided a link on their forum: https://support.native-instruments.com/hc/en-us/community/posts/360005447937-Kontakt-5-8-1-installer-de-

I've been reading about this is on the Avid & Steinberg forums, just to get any indication as to what plans they have, but its pretty much all speculation at this point. Going by past upgrades though (i.e. PPC to Intel, and also the OSX compatibility cycles), it's likely that the Intel Mac's will continue to be supported for around 5 years after the ARM macs start hitting the streets. The more worrying issues for those tied to the Apple platform are: - Will DAW companies, and more importantly plugin companies be able to make the switch? I mean, there's a lot of codebase there that may or may not be easy to port over. Some will simply be able to recompile for ARM, others may have DSP specially tuned for Intel and will require more work. Also differences in chip architecture / OS could mean major changes to their threading models. DAW companies that target both PC & Mac may have a tough decision to make here if they're looking at maintaining a divergent codebase moving forward. - Will the audio interface companies be ready with drivers for the ARM macs? Presumably Apple will also need to come up with some new Thunderbolt 3 solution for ARM too, unless they ditch Thunderbolt and come up with some new proprietary interface. - People who rely on bootcamp to run Windows will be out of luck. This feature was only viable because both OS's ran on the Intel architecture. So even if the DAW companies manage to make the transition, there's a pretty good chance that you'll have to upgrade your audio interface and say goodbye to many of your plugins. I can envisage a lot of pro studios moving over to Windows to avoid this pain.

I tend to rely on the Mix Module for this. If the record button in the mix module is highlighted, I just click it to disarm all tracks, then arm the track I want.

There's no N series emulation - I've had both those modules (still got the NX5R), and I sampled mine to use them in the box. The closest VSTi to the N series is probably the Korg M1 VSTi. The synth engine is actually better than the N series one, and the sound quality is far better, but it's not got as many multi-samples.

FYI - the "=" key will toggle between the last selected track envelope filter and the clip. Likewise SHIFT + "=" will toggle between the selected clip's gain envelope and the clip.

You can kind of doing what your suggesting already (minus the meta data) by creating arrangements for each individual section. In other words, drag section 1 into arrangement 1, drag section 2 into arrangement 2 etc.. so each arrangement has only one section in it. Make sure you rename each arrangements to match each song name. When you select "Export as Audio" from the arrangement dropdown, you'll have the option of selecting all the arrangements (songs) and it'll export them all as individual audio files.

@Colin Nicholls - just so I understand correctly... Do you mean: 1. Export a stereo mix down by sections, e.g: Section1.wav, Section2.wav, Section3.wav etc.. or 2. Export multiple tracks by sections, e.g.: Section1-Track1.wav, Section1-Track2.wav, Section1-Track3.wav, Section2-Track1.wav, Section2-Track2.wav etc ?

The "There is not enough memory" error is what Windows returns when the device is already in use. Most MIDI devices only allow one application to open the device at any one time. The way around it is to use a loop-back device, e.g.: https://www.tobias-erichsen.de/software/loopmidi.html https://nerds.de/en/loopbe30.html The loopback devices are multi-client - i.e. they can be used in more than one application at once. You can use these either on their own, or in combination with MIDIOX if you need extra routing/processing. What I tend to do is create two loop back devices, with the MIDI input of my hardware MIDI device routed to one loopback device, and the MIDI output of my hardware MIDI device routed to the other. Be careful to get the loopback ports the right way around else you'll create a feedback loop.

@Mcu pro - can you post a screen shot of the Control Surfaces page within preferences (ALT + PrtScn) ? There were some issues with the first release of 2020.08 with the loading of presets/configuration. This was fixed in 2020.09. Can you confirm you're using the very latest MackieControl.dll that came with 2020.09 ?

Can you show a screen shot of the recorded waveform on the track?

Check your mains outputs in Cakewalk, by clicking on your master bus and looking in the Inspector - the mains outputs have red faders. Check they're set to the same level:

If you're exporting to use the audio files in another DAW or audio editor, then you might want to keep the quality of 32bit / 64bit. However, if you're exporting to play the files, you'll need a bit depth that most sound cards support - e.g. 16 bit or 24 bit.

This is the setting that you need to set:

This disabling/enabling read automation has been fixed for the next release.

The next CbB release will accept -1 ( e.g. 65535 for the FX #) to denote the track FX bin itself.

Do they not still provide the Kontakt libaries too?

I'm pretty sure this weather guy's colleagues got him to do this hoping he'd slip up.... he pronounces it perfectly tho:

It's most likely not set up correctly within Focusrite Control. You need to make sure that: 1. The DAW inputs 9-16 are being fed from the ADAT inputs; and 2. The OctoPre is wordclock sync'd to the 18i20 (see page 10 of the OctaPre userguide: https://d2zjg0qo565n2.cloudfront.net/sites/default/files/focusrite/downloads/31897/scarlett-octopre-user-guidev1.pdf )

Your extra inputs/outputs were always "there" - they just weren't connected or routed. Stereo Inputs 1,3,5,7 relate to the 18i20's eight inputs. Stereo inputs Digital 1,3,5,7 are your eight OctoPre inputs. If you're using mono: ASIO Input 1 Left = Analog Input 1 ASIO Input 9 Left = ADAT Input 1 ASIO Input 1 Right = Analog Input 2 ASIO Input 9 Right = ADAT Input 2 ASIO Input 3 Left = Analog Input 3 ASIO Input 11 Left = ADAT Input 3 ASIO Input 3 Right = Analog Input 4 ASIO Input 11 Right = ADAT Input 4 ASIO Input 5 Left = Analog Input 5 ASIO Input 13 Left = ADAT Input 5 ASIO Input 5 Right = Analog Input 6 ASIO Input 13 Right = ADAT Input 6 ASIO Input 7 Left = Analog Input 7 ASIO Input 15 Left = ADAT Input 7 ASIO Input 7 Right = Analog Input 8 ASIO Input 15 Right = ADAT Input 8 This is the standard routing, but you can obviously change this in the Focusrite Control app. The same goes for the outputs: Stereo outputs 1,3,5,7 are the analog outputs on the 18i20; Stereo outputs 9,11,13,15 are the ADAT outputs.

On my AX44, the jack socket was a "sealed" socket soldered directly on the PCB. Luckily the back of the socket was clipped on and could be easily removed and put back so I could push a screwdriver in: The problem I had, is that the tip had actually snapped off, so it was a blunt end that was stuck. The connector that clamps on the tip is pretty strong, which I guess is why it snapped in the first place. Cyanoacrylate didn't work at all. Epoxy resin did, but it just wasn't strong enough.

@CJ Jacobson - this has been fixed for the next release. In the meantime, if you make sure "Center on Now Time with Keyboard Zoom" is checked and also your mouse zoom settings are set to "At Now Time" this should work: In the next release, you'll be able to set your mouse options independently of the "Center on Now Time with Keyboard Zoom" setting.