Forum Replies Created
-
AuthorPosts
-
2017/04/11 at 9:05 pm #62834
I haven’t got the software in front of me, but one way might be to have some scenes heavily recall filtered to just the midi strips, that way you could use soft keys to recall different configurations etc…?
2017/03/29 at 10:43 pm #62457Yes yes yes please. Even if its not Dante, some digital loopback would be amazing.
2017/03/29 at 10:42 pm #62456Yes please. This. 🙂
Part of what has put me off getting me-1s for more of my tours is the messy minijack via pc di box to xlr and loom back to the iem rack! Especially when it is already so neat with me-u running p.o.e.
Would gladly use my dm64 xlr outs to drive the iems if there was a digital loopback available.2017/03/29 at 10:27 pm #62455Also just worth a check that your Dante card has the latest firmware also?
2017/03/29 at 10:05 pm #62450I find that director works ergonomically pretty well with 2 touchscreens! A smaller one for the processing window (like the desk itself) and a larger one for the fader and buttons control.
Have you also considered pairing the director software on a touchscreen pc with 2 or 3 ip8 fader banks? Could be quite a nice surfaceless solution…
2017/03/29 at 9:56 pm #62449I would personally love to see a value in a text input box on every rotary and fader control that we could click on to type in exact adjustments!
Heres hoping for the future!
2017/03/29 at 9:53 pm #62448Hi Santir,
As far as I’m aware, at present it is only possible to connect a single surface to a single dLive mixrack. Although I understand that it is on a&h’s future roadmap for dLive.
For now, I would investigate using a surface at foh, and using a copy of the “director” software on a good quality touchscreen PC for the monitors. You can run them fairly independently and even have a separate pafl bus for each engineer.
2017/03/27 at 11:09 pm #62407I think for now, sends on fader, with option to show vales on the ‘lcds’ is the closest you can get.
I find this very frustrating too!2017/03/22 at 5:35 pm #622862017/03/22 at 5:30 pm #62285BTW – https://www.allen-heath.com/media/dLive-Firmware-Reference-Guide-V1.4.pdf
is not 1.41 but effectively the same. I just retyped the URL as 1.4 from the official 1.10 link… 😉
2017/03/22 at 5:27 pm #62284Hi Jay and Nicola,
I’ve done some 3 days or so of testing with my setup here in various configurations.
10 iPad4, 3 copies of director (2 on mac, 1 on pc)
The Director copies on mac are connected via the dante card in the mixrack (through the network link port)
64 channels bi directional in use on Dante.I’ve tried this on wireless (with apple airport express router) and it all works great –
Immediate scene recalls and fully responsive OneMix’s and Directors! Yes!Also tried the iPads wired through my NETGEAR 24port switch (unmanaged)
Still immediate scene recalls and fully responsive onemix and directors.THANKS A&H for a very effective fix! I don’t know what you did to the net code on the surface or mixrack, but it all seems to be working great now!
2017/02/18 at 1:48 am #61428Hi Yacob! Thanks for your input.
I’ve had to take a different approach with this in the end. I have their mixes’ routing recall-safe, and I unsafe the routing for the groups and input channels. That way I can scene the inputs in and out of the groups as needed, without messing with the send levels of those channels to the mixes.
It just means that the guys won’t be able to sometimes hear the input channels instead of the groups. They can only listen to the groups. I’ve had to burn up more groups making copies of the drum groups and keys groups that can have a different level for when a different guy is playing them.
It’s a matter of needing to be able to change the input channel’s routing on/off without affecting the routing levels.
Your solution works for other mixes on the same input (such as fx sends), but I want to be able to remove an input from a mix and then put it back on a later scene (night of which require unsafing of the mix) without storing or recalling the send levels into that same mix.
Sorry if I’m not being very clear as to why it’s needed, it is quite complex when trying to put it into words!
Thanks for having a crack at solving this, but alas, this time it’s not quite the right solution. Roll on firmware 1.5! 😉
2017/02/10 at 1:25 pm #61246You can type in a custom IP address. So you just need to find out what your “director” computer’s ip is. Where you look depends on what version of windows or macOS you’re using. If it’s on the same computer as your show control or qlab, you can use 127.0.0.1 as a loopback ip.
Hope this helps,
Neak2017/02/08 at 10:40 am #61183Regarding midi scene changes without a surface, via the a&h tcp midi driver, I’ve solved it.
Send the midi to the IP address of the computer running director, rather than the MixRack IP address, then all is happy and scene changes get ‘noticed’ and auctioned.
Yay! One issue down, a few still to go! Wish me luck!
Neak
2017/02/07 at 11:11 am #61139A&H tech support are on this – investigating and testing, but I thought I’d give an update.
When 7-8 devices are connected (one Director on Mac and 6-7 iPads (rev4) running OneMix) I hit a wall where scene recalls from the surface became intolerably slow – up to 3mins most of the time. Some parts of the scene were only activated by the end of the recall (the band didn’t hear themselves as they weren’t patched until the scene completed!). When the number of connected devices drops again, the scene recalls get back to full speed.
Unusable unfortunately. I had to do the 2 shows from a static scene with all channels open and frantic manual muting song to song.
When scene recall was initiated via Director, the scenes recalled instantly across all devices, except that the Surface “scenes” page wouldn’t show that it had scene recalled (but the mutes fades and routing etc, seemed to be shown straight away though).
I moved my Dante card down to the MixRack and ran a separate cable from FOH from DanteVirtualSoundcard to it to see if it was somehow taking any bandwidth on the GigaAce. It didn’t make any difference to the issue.
Also found a curiosity – maybe I’m doing something wrong here, but I can’t get the mixrack to respond to MIDI scene changes unless the Surface is connected! (and obviously, my slow recall issue then occurs again as it would seem that the surface initiates the scene recall).
I was running the scene changes from the Qlab via the A&H TCP Midi driver and DanteVirutalSoundcard for the audio but over a second Ethernet interface (to keep Dante out of the way). I was also making sure I was connecting to the MixRack IP address, not the Surface…
I hope this isn’t by design as there will be times that I will want to MIDI recall scenes on a MixRack without a Surface connected!I’ll let y’all know when A&H get back to me with workarounds or solutions! They do suspect I may possibly have a bad surface…
-
AuthorPosts
