[lposoundParticipant]

Hi Julian,

I’ve been following this thread with interest since the beginning but only took the time to test on my dLive today.

Let’s keep it short and efficient, according to my test (1 unmute every 5 seconds for 60 seconds = 12 unmutes), after a sudden power cut, the dLive boots to its last state… minus about 25-30 seconds (7 unmutes were kept but not the last 5 that occurred in the last 30 seconds before the power “loss”)! The test gives the same result regardless of when it’s started. We can therefore assume that the autosave is not performed on an hourly basis, but continuously, with a constant 30-second offset.

All in all, your feature suggestion made me discover something about my beloved dLive… which I’ve had for over 6 years now! So, thank you!

Loïc

[lposoundParticipant]

Hi Matthew!

There’s a very simple workaround to that limitation of the “Virtual SoundCheck” feature: use the ABCD feature on the inputs.
I’ve been doing this for years and it’s no less convenient.

Here’s my configuration:
1. In the “Virtual SoundCheck” tab of the “I/O” menu, patch the channels to be recorded (direct outs) and switch to “Record Send” (leave that setting like that “forever”).
2. In the “Inputs” tab of the “I/O” menu, set up my “live” inputs as “Input A” and my “virtual soundcheck” inputs as “Input B” > here you can patch a source to a channel as many times as you like.
3. Set a Surface SoftKey to “ABCD Set All” – “Source A” to switch to “live” mode and another SoftKey to “ABCD Set All” – “Source B” to switch to “virtual soundcheck” mode.

Hope this helps! 🙂

Loïc

[lposoundParticipant]

Of course I’ve already fiddled with the “MIDI Thru” field in MainStage. Whether it is set to “Automatic” or “Do not pass through” doesn’t change anything. 🙁

[lposoundParticipant]

Hi Klaus,

If we think this feature request to the end, every processing of that stereo channels, input, mixbus, main or matrix should be able to be unlinked.

Yes, indeed, good point!
The stereo inputs already have a workaround thanks to the ganging of 2 mono channels.
Likewise, the processing of the main bus is already completely dissociable thanks to the option of “Individual” channel strips (Mixrack > Config > Mixer Config).

Best,

Loïc

[lposoundParticipant]

Hi Klaus,

Stereo is in live environments definitely overrated, and so is Daves mixing strategy too. 😉

Thanks for your constructive input…

As said above in reply to Andreas, I shouldn’t have referred to Dave Rat’s mixing strategy as it seems to bother you all! Maybe we can just stick to the dLive feature suggestion I made while avoiding personal views? 😉😉😉

Best,

Loïc

[lposoundParticipant]

Hi Andreas,

if you think about it, all dave rat ever had, was mono groups.

That’s simply wrong.

If you stick to the Dave Rat reference I made, we’re talking about stereo subgroups capable of keeping the stereo image set in the channels section. Of course, trying to do that on a mixer that can’t handle it doesn’t help… but this is not the case here as Dave was using Midas Heritage 3000 consoles > Excerpts about subgroups and panning taken from the linked documentation: “… The Group Master busses themselves (see the flexibility section) may be configured as mono aux masters, stereo aux masters or post pan audio sub groups.” / “… The Pan defaults to control the channel placement within a group or master stereo mix and has a constant power law.”

I shouldn’t have referred to Dave Rat’s mixing strategy as it seems to bother you… but could you just focus on the topic of this dLive feature suggestion? dLive has both mono and/or stereo subgroups. By design, dLive maintains a channel panning in a stereo subgroup (not possible in a mono one). It would be great to have the ability to unlink the dynamics parameters of a stereo subgroup, point.

Best,

Loïc

[lposoundParticipant]

Hi Scott,

Thanks for your proposal… but using two mono subgroups to create or reproduce a complex/subtle stereo image (= not only hard panned channels/sources) is a no go. Think about your solution applied to the LR bus and you’ll understand it wouldn’t work.

Best,

Loïc

[lposoundParticipant]

I do share your opinion 100%.
With Controller not working on Catalina, it is a bit risky for most situations.

Audinate is always extremely slow… Shame on them 😉

[lposoundParticipant]

Hi Geep,

DVS is working great on macOS Catalina since their last compatible release (v4.1.0.8).
On the other hand, Dante Controller is not yet compatible with macOS 10.15, as you wrote, BUT if you do not have to launch it (to modify your configuration for example), the Dante does stream with no problem from and to the macOS Catalina computer to and from the rest of your Dante network.

I did the test yesterday on my setup with no error nor issue at all:
– CDM32 with Dante card (+ C1500)
– MacBook Pro on macOS 10.15 (Catalina)
– MacBook Air on macOS 10.14 (Mojave)

In that setup:
– I recognise that I do have the very same issue you have with the localhost if I open Dante Controller on my Catalina machine… turning all devices red.
– At the opposite, opening Dante Controller on my Mojave machine shows no warning at all. Correct routing, subscriptions, latency and settings.
– On the audio side, I can stream 32 channels from my Mojave laptop to the Dante network patched in channels on the dLive + send auxiliaries from the dLive to the Catalina laptop through Dante and get FX returns from that Catalina laptop back to the desk through Dante as well.

Best,

[lposoundParticipant]

My personal workaround was to use a singlesurface template showfile… but the guys who really needs a multisurface setup should (and can only) use the MIDI strips for MIDI interactions and should know that scene changes won’t send any MIDI signal as expected (that appears to be pure logic as scenes are specific to each surface but A&H should notify the users).

[lposoundParticipant]

Hi Rojack,

I had a similar problem with MainStage last week (on the last firmware: 1.62).
Found out the MIDI communication was limited (MIDI strips ok but no MIDI sent to the computer when recalling scenes) because I built my showfile using a multisurface template instead of a singlesurface one.

Otherwise, did you monitor the MIDI activity (with “MIDI monitor” or “Osculator” for example)?

[lposoundParticipant]

Hey TCMG,

The connection is made through the mixrack IP.
I did find out the solution as I explain it in this thread: MIDI communication is limited in a multisurface setup (or, at least, when building a show from a multisurface template showfile).

[lposoundParticipant]

Hi Tor,

As I said, I already monitored MIDI signals with MIDI Monitor and I did search so please don’t be too rude (no offense) because, you’ll see, I’m new here but I do not ask anything without searching first 😉 But I do apologise for the lack of concluant testing ‘cuz…

… anyway, I did find the problem! And proper testing was easy peasy: just loading the FOH factory show file.
Doing that, MIDI signals from scene changes came back.

So, my finding – yes, there is a finding here – is that something important – yet “consistent” – is not documented at all by A&H (official firmware manual and MIDI implementation):
multisurface showfiles disable all the MIDI communication apart from the MIDI strips controls!

FYI, I first loaded a multisurface showfile to do some testings and find the best workflow for my use.
I cleaned it up (at least I thought) from any “multisurface related aspect” (roles for example) and kept going with my scenes setup until I discovered my MIDI problem.

Anyway, thanks for your procedure Tor! Any dLive/MainStage user has now details if he needs support on scene changes 😉

Best,

LOIC

[lposoundParticipant]

Hey TCMG (if I can…),

Using Osculator (or MIDI monitor), my desk is only showing MIDI traffic when moving any control of a MIDI strip (that seems logical BTW).
But, changing scenes on the desk should also send MIDI bank and program changes… and mine doesn’t seem to send those!
So, you saying “Connect any mac to the desk via TCP midi, run an osculator session and grab whatever parameter you want to automate w/ “if-this-then-that,” args” is a bit disappointing for me as I’d very much like to do things like you describe.

My setup is very simple with no custom MIDI configuration (computer side)… and I can’t figure what’s wrong.

Best,

LOIC

[lposoundParticipant]

Hi Tor,

Sorry but this is not helping ‘cuz, as I said:

I can already say that my Mac doesn’t see any MIDI message (using “MIDI monitor”) when changing scenes on the dLive… although the document says “Also transmits this message when a Scene is recalled from the dLive screen”.

Do you mind being more specific on your setup?
– A&H TCP/IP driver setting > do you had to enter manually the IP of your desk or does your network list it in the dropdown menu? I had to go the manual way.
– Desk MIDI channels > on which range are you? Mine is set on 12 to 16.
– Audio MIDI setup > do you setup anything special?
– MainStage “Concert” > what are your concert MIDI settings?
– MainStage “Patches” > if sending scene ID from MainStage, do you use the attributes “Bank Select” and “Program Change” to match the corresponding dLive scene?

Thanks in advance for your time!
Best,

LOIC

[Author]

Posts