Tue Apr 16, 2019 10:29 pm
OK, I'll bite. Specifically & only about Fairlight:
Audio input patching is still a dog and fails to work as it should. eg:
- The Fairlight input page rarely shows any inputs available at all (in this case, using an RME UFX+ as Win system IO WDM Devices; inputs and outputs enabled as required & working on other apps).
- Conversely, the ADR /Voiceover setup window does show a few inputs available (puzzlingly, only some) & these can be routed to a mono or stereo track. Returning to the Fairlight input menu: this still shows no inputs as available, but now does show the inputs selected in the VO setup as patched to those tracks. Buggy as hell.
Overall, the IO setup fails to work as it should and is temperamental /inconsistent following re-launch /system re-boot /re-install. Some of this also greatly effects film playback performance in the Cut and Edit pages, that is: after messing about & trying to get audio happening, the whole program may then suffer other performance issues. Drivers?
Good to see all of the new Fairlight plugs, in my experience, these all test and work well so far.
In my view (and reflecting many similar comments elsewhere) - the Fairlight menus for patching, busing, input routing are not only buggy as per DR15, they remain unnecessarily unwieldy and complex. This means by comparison to long standing conventions for audio patching in DAWs. Perhaps BM may want to look far more closely at that in say, Pro Tools, Cubase, Studio One etc. While designed by very different companies, the conventions for IO patching remain remarkably similar & that's how pro studios operate in terms of easily interfacing between various DAWs, much outboard IO and also transferring projects between studios.
On the other hand, one can easily see these conventions being applied and growing in the main Fairlight mixer page. Well done, this is becoming increasingly easier to navigate and not to have to re-learn.
- Would like to see drag and move mixer strips as per other DAWs.
- Buses do not show for automation etc as described as availble via the Index pull down; 'sometimes' they might.
Clearly the Fairlight development is going for that DAW market & is the only NLE to truly do so. Perhaps at some point it will actually make round tripping unnecessary. It would also seem from various user comments that Resolve is being rapidly adopted in recording studio environments. Hopefully this then requires an adoption of those protocols and conventions, and far less so the apparent trend of trying up-skill the film editor (?). That's kind of no man's land and surely a more conventional approach to audio engineering would be a better place to start?
Finally, for God's sake, add ASIO driver support and much of the above will go away. Surely that enormous base of studio installations and a multitude of pro audio hardware will serve BM adoption far better than the oddities of (say) BNC audio IO on Decklink etc etc.
While we're at it: add MIDI tracks, VSTi support and along those lines, the main preference page requires more options than being only able to select a single control surface (HUI or MCU) and requires any number of ports being able to be selected and controlled by other MIDI controllers such as keyboards, surfaces, Ableton Push etc.
Thanks. My 2 cents for now.
MacPro 7,1 16 core, 192GB, MacOS 14.4.1, Vega II Duo. Antelope Pure 2 & Orion 32+, UA Apollo x8. RAID-4 Thunderbay 6, RAID-0 Sonnet M.2 4x4. MiniMon 4k, Dell U3415W & BenQ SW2700PT. Nuendo, Wavelab, Resolve Studio 18.6.6.