[BiggsoundsParticipant]

Unfortunately as a production company with multiple SQ’s (and dLive’s), the pricing just isn’t realistic… all ours will stay as stock even though we’d love to implement the same DEEP processing we use on dLive, as others have said here the lack of cross platform/cross console usability means the pricing just isn’t viable – if it was a new product with new R&D costs you could understand, but these are models you’ve had running for years on dLive, it doesn’t make sense to charge UAD/Waves (or higher) costs per console 🙁

[BiggsoundsParticipant]

Pretty disappointed to see no official support for DX32 in this upgrade… is it coming soon?

[BiggsoundsParticipant]

I still use an analog split if there’s going to be consoles substituted in at FOH or whatever, it’s just on shows where it’s just going to be the dLive’s that we use the GigaACE

[BiggsoundsParticipant]

Wondering if anyone has had any joy on this other than the expensive (and stupid) dual dongle fix? Has there been any movement from Apple to correct the issue?
Every time I use my very expensive MacBook Pro to send an email or watch netflix, instead of using it for the ONE specific thing I bought it for, it pisses me off 😉 (my old 2013 is still doing the job just fine, but I’d love to be able to take out the computer I actually bought for Waves!!!)

[BiggsoundsParticipant]

I’ve sent the direct outs, gain tracked, out of a dLive into an SQ, so not sure why that wouldn’t work into a second dLive (you’d need to use another gigaACE card I’d assume though, on the SQ it was via the sLink). Begs the question though, if you’ve got 2 systems, is there a reason why you wouldn’t just do it as a multi-surface rig & leave the second rack in the truck?

[BiggsoundsParticipant]

I usually do it via the routing tab, it’s the fastest way (and helps to make sure you haven’t accidentally assigned the same channel to multiple groups etc)… this is a great visual way of doing it, especially now there’s all the extra routing possibilities in 1.7

[BiggsoundsParticipant]

I currently own 3 DM racks, 2 S (5000/7000) series consoles and a C1500, I’m looking at changing out one of our DM32 racks for a CDM simply to drop the weight for fly shows (I can fly a DM32, but it doesn’t allow for a lot else in the pack, where I can get the same I/O count on a CDM32 5kgs lighter, and a smaller unit means I can also use a smaller pelican dropping the weight again. I’ve found no performance difference between surfaces, only workflow (and after using the C1500 quite a lot I’ve got all my workflow stuff down anyway – I use the soft keys & an IP8 for DCAs etc & it’s all pretty easy from there).

[BiggsoundsParticipant]

Hey RobbO, I’d imagine the main benefit of going to a DM0 as opposed to using 2 surfaces off of one rack (via a GigaAce card) would be if you required a very high channel or buss count – the Mixrack supports a finite number of channels and outputs, if you’re starting to talk big channel counts and and lots of sends on top of whatever internal busses are required, you need to factor that into your configuration… a DMO would allow you a full channel count on both surfaces, and totally independent busses/FX etc… having said that, it would need to be a very complex system to need it! If you go the analog split, you’re still going to need 2 DM racks (48 or whatever) to do the job. On a permanent install, gain sharing/tracking would suit most people realistically, and saves an awful lot of copper (as you’ve said, that’s been a source of failures).

[BiggsoundsParticipant]

Same pre’s on the surface as the rack, and WORLDS better sounding than the iLive pre’s (staggeringly better preamps & conversion).

[BiggsoundsParticipant]

I don’t think the name calling is necessary Tor, and while it’s not the intention, they’re a very programmable unit & in theory can be set up that way… what I’d love to see if an editor which makes programming faster (it’s horribly slow to do it for a big setup, either on the console or on Director, some sort of copy and paste functionality would be amazing, or even a grid based editor).

[BiggsoundsParticipant]

Andrew, even if they’re personal iPads I’d suggest to them if they’re using them for professional purposes it’s worth turning off auto update (I mean, it’s literally one button press to ‘update all’ when you are ready)… I don’t Auto update ANY of my devices (computers/iPads etc), as there’s always the risk of incompatibility (as some of us running the new MacBooks are finding with Waves/Dante clocking issues). No biggie, just let them know to turn it off, even temporarily, while the update cycle is in play.

[BiggsoundsParticipant]

Are we far off for 1.6 Ben?

[BiggsoundsParticipant]

Awesome, thanks Ben, looking forward to watching it

[BiggsoundsParticipant]

If you’re on a transformer split you wouldn’t be able to feed phantom to the other rack, so all good there, but yes, on a festival with quick changes etc & minimal comms with Monitor/FOH world I find the analog split easier, but Dante split is super easy & works great when both crews understand gain structure 😉

[BiggsoundsParticipant]

In all honestly I’d suggest you’ll probably be better off just keeping it as an analog split. You can swap out cards (put a Dante in the GLD would be the cheapest fix – the letterbox adaptor in the dLive Dante kit already does the sample rate conversion), but you’ll need to share head amp gain between systems, and if the engineers don’t want to do that then your easiest solution is still analog.

[Author]

Posts