[dcongdonParticipant]

Thanks for chiming in, Keith. Can I request a different approach to feature logging and requests? I feel like A&H’s policy encourages forum behavior that makes this platform uninviting.

I want to see certain features implemented as much as the next Dlive owner, but this feels like “the loudest voice wins” …and in a forum environment, that either looks like threads full of “+1”s or commenters out to win more than to learn.

It would be nice if A&H would log every feature suggestion into a polling system so we know it has been seen. Then we can vote them up or down OR debate how they are implemented. Features that have no chance of implementation are never included in the poll. Maybe each feature pole has an assigned thread dedicated to “feature scope” where A&H keeps a working document that user can discuss.

[dcongdonParticipant]

Like msteel said, the Global/Scene safe for scribble strips is under the “OTHER” tab. It offer left or right bank safes, but not specific layers.

If you want to fix your strip assignments for a batch of scenes (or all scenes), I suggest using the Scene Update tool. Select all the scenes you wish to change, select Auto-tracking and Absolute, then rearrange your layers to taste, then go back and click Apply. This will update all of the selected scenes with your new scribble strip layout.

[dcongdonParticipant]

Problem solved. Found a network port looped on a connected switch.

[dcongdonParticipant]

When programming for theater, I may have 250+ scenes with several different recall filter “presets” that I use for dialogue, dance or musical number. The copy filter button and Global filters are great, but I am interested in:

1. Auto-tracking filter updates for a selection of scenes.

2. User defined “Master scene” that is lockable and not affected by global safes.

3. A scene filter preset library.

4. A filter overview window that gives a bird’s eye view of what is globally and locally safed.

[dcongdonParticipant]

I don’t think this feature exists but would love to see it!

[dcongdonParticipant]

I would personally not like to have faders on screen. That is what Director is designed to do. Maybe rotaries as an emergency fail safe if a physical fader goes out, but there are better ways to expand control.

It’s an expensive sidecar, but any Dlive surface can be a remote control if you connect it by network port.

Mixing Station with a midi fader bank also works well. Of course, you lose the Mix button in place of a typical SOF workflow.

[dcongdonParticipant]

Let’s break down the entire signal chain:

– Dlive aux bus is routed in the IO menu/Output Tab, to Dante Card IO port, channel X
– Dlive clock sync is set to Y
– Dante Controller (DC) sets Dlive Dante card clock sync to Y, 48kHz
– DC sets CL5 Dante clock sync to Y
– DC routes Dlive Dante channel X (transmit) to CL5 Dante channel Z (receive), audio signal confirmed on Device page
– CL5 clock sync confirmed to match DC
– CL5 Dante channel Z assigned to input channel

[dcongdonParticipant]

I believe VSC is above scene recall but below showfile recall. If you want it to be scene-controlled, better to use tie-lines.

[dcongdonParticipant]

+1. I say this without any expectation it will materialize on the Dlive platform, but it would be cool to dream up a next gen Channel EQ. Love NEQ. More Q control and asymmetrical filter options would be slick, but I would be happy with NEQ as-is on a channel.

Want to go crazy? Give us a 2-mode option to choose between NEQ or a 6-band dynamic EQ (similar to F6) with sidechain (per filter).

Dyn8 is a great insert, but I would rather see dynamic EQ imbedded with channel EQ (without insert latency) and have Multiband comp as a standalone insert.

[dcongdonParticipant]

I am all for adding more Direct Out pick points (and independent pick points!), but I have to disagree with the rest of the OP’s requests. Tie Lines provide the best pick option for pre-processing. Direct outs should default to something other than what Tie-lines already offer. I can see an argument for that being post EQ instead of Delay, but that’s about it.

I also do NOT want polarity baked into a direct out feed. That should stay with channel processing on the way back in.

I can empathize with the amount of time it takes to fully program a dlive system (especially inserts)…but I agree with RS that you need to build a base showfile that you start from.

Cheers!

[dcongdonParticipant]

Best solution I have found is black tent canopies and mesh side/rear walls

[dcongdonParticipant]

Onboard FX bus and FX return options exist for users who may need higher channel counts (think of a shared surface setup with 64 inputs each) AND your fx processing is a lower priority (think volunteer engineers or corporate).

For more advanced setups, it doesn’t make a lot of sense to use the onboard FX routing. I typically use a handful of stereo and mono aux bus sends + corresponding stereo input channels to route fx.

This also works really well with outboard FX (Waves/hardware). You can send the aux bus to the onboard FX as well as outboard processing. Then setup your stereo returns with ABCD preamp selection with Source A fed from outboard and Source B from the onboard backup. Create a scene to change between those sources and you have a good redundant system.

[dcongdonParticipant]

Also, if you tap any scene in the left column, you can preview the scene notes in a pop-up.

[dcongdonParticipant]

Great list. A few items I would like to add to basic functionality of the console:

1b. Add in gang window a choice to gang Dyn8 insert on A or B

4b. Scene preview

5b. Showfile and scene data (create date, last modified date, last recalled)

7. Routing window for Insert points for inputs and outputs.

7b. Inserts retain patch number even when card slot is changed

7c. Insert returns are not linked (similar to sends)

[dcongdonParticipant]

+1 for everything mentioned so far. I think it is fair to say 1.9 was a huge success and we are excited to see A&H continue to push the platform forward.

For my part, I would like to see meta data on each scene above the notes section. It would help to have:
1. Created on / by (login)
2. Last modified on / by (login)

Some other things:
1. Ganging for Dyn8
2. Full channel recall (labeling and dyn8)
3. Manual override for delay compensation to allow for bus to bus patch
4. ABCD source for external PAFL input
5. More options than a global Direct Out

[Author]

Posts