[AndreasModerator]

Of course any implementation of FX/EQ will sound and behave different, but I’m not sure if switching from the 01R to the Qu is for the internal FX/EQ…

Sure, recording additional track to an existing recording could be an issue if there is some error in the latency path between ASIO and the DAW. Normally this should be properly handled in 2014 but probably worth to test…
…give me a minute…

[AndreasModerator]

Probably a stupid question: Why do you want to use FX and EQ from the desk? Any modern DAW (and plenty of free plugins) should provide those manipulations, right?

I’d only record dry inputs to the DAW and do anything there. Full automation, not depending on external gear, no affected by any loopback latency issue etc…

Only if you need a particular _external_ FX which does not exist as plugin latency may be a concern (DAW->USB->DAC->ExternalFX->ADC->USB->DAW). But even if this is not correctly handled by the DAW and the ASIO-Driver (should communicate the latency with the DAW), you can still shift the re-recorded track accordingly (that’s what I did in very early days).

[AndreasModerator]

+1 !
…what about some more cosmetic stuff, like (should we create threads for each?):
…highlighting the selected channel in the meters display
…display current DirectOut settings in dialogs where this is actually used (Monitor selection etc.)

[AndreasModerator]

Saw that V1.6 had some fixes on QuDrive, sadly my 64GB SanDisk UltraFit stick still does not work (and the desk needs a power cycle to accept my USB HDD again). Just to mention…

[AndreasModerator]

CPU usage dropped significantly with V1.6 on my old Dell laptop, so something indeed changed.

[AndreasModerator]

Already love the Qu-You, great addition!
For “real use” I somehow wish to enable/disable specific mix buses for Qu-You usage, just to ensure they’re not tweaking mixes (accidentially, of course) not intended for monitoring (i.e. a mix bus used for external FX gear, works great btw.).

[AndreasModerator]

sure, its all there… somewhere. But if you’re in a hurry and something does not work as expected you first have to think about which places to look for and check one by the other. In my case, I just forgot that I played around with DCA on FX sends before and not checked that page (which is not on the channel but one the FX bus). But maybe thats only me…

[AndreasModerator]

At least USB/dSnake/Console can be seen/changed on one page of the UI for all channels..

sure, but that may take several buttons to be reached…

I’ve recently wished to have the exact opposite, when I silently muted one of my FX sends with a forgotten DCA link: The possibility to see from one screen which path(s) a specific channel takes and where it is potentially blocked. Probably not easy to visualize but maybe helpful not only for me…

[AndreasModerator]

would be nice for Phantom and USB too…

[Author]

Posts