[abenessParticipant]

Hey, A&H: NTP has been requested since 2018, nearly 6 years ago. It really is frustrating to find the console severely out of time sync. NTP is robust and mature technology. Would you please advise whether you have added this to your “flagship digital mixing platform” development roadmap, and if so, when we might be able to expect it? My middle and high school students regularly complain about it… each year a new crop!

Thank you,
Abe

[abenessParticipant]

That’s an excellent point, Dave. A&H, I really hope you can find a way to help us out with faster compatibility updates.

[abenessParticipant]

Now that macOS Sonoma has been released (Sept 26), we are now two OS versions behind.

[abenessParticipant]

@nicola Great News re: Monterey and M1, thanks. Would you be able to post the known issues with Ventura? It may be that some will find them to be manageable.

@SteffenR Let’s please not malign OS manufacturers here. Testing during beta and reporting specific issues is critical; developers can’t catch every problem on their own. I do admit to avoiding the bleeding edge: I’m much happier running shows on the mature OS with 6+5 service packs (e.g. Monterey 12.6.5) than on the latest release, for sure. But by the time 13 gets to 13.3.1, most software should be functional, because most issues will have been raised and addressed.

[abenessParticipant]

Thanks for the quick help, Peter, hard to believe I missed that, except that there was too much going on. Fab. And thanks Steffen for the useful examples. It would indeed be a chore to change shows under those circumstances.

[abenessParticipant]

Thanks, Steffen and Wolfgang. I’ll experiment with those things. The cue list is certainly of value insofar as we’re a school with many events, and so it is useful for us to have one show file that covers a number of different basic events. Moving scenes between shows is indeed cumbersome given the show load time (though faster than iLive!), but I’ll try it. Thanks again!

[abenessParticipant]

Grr, sorry, folks, missed that I was in the SQ forum. I’m on dLive! Whoops. Same comments still apply, though!

[abenessParticipant]

Hi, Alex. Is there an ETA for testing? I need to wipe our theater control iPad for reasons too gory to recount, and it will therefore end up on iOS 13. It would be great if you folks could prioritize testing with iOS beta versions when they come out, so that apps can be qualified at time of public release. It’s complicated to manage devices with iOS version restrictions.
Thanks,
Abe Hendin
Abraham Joshua Heschel School, NYC

[abenessParticipant]

Hi, Steffen R. You’re right, I mean balance, oops. Thanks for the Input AFL pointer, and I love the Stereo Image options, those could be very handy. If I turn on Input AFL at Surface/Audio/PAFL, then PAFL in the phones shows expected results.
(I guess I could add another PAFL bus if I want both pre- and after-fade listen available for reference. Have to explore how to select on the fly which PAFL bus is in the phones. I’ve only ever used PFL.)

However, changing the IP balance left or right does not affect the output to booth mons with post-fade mix routed there. What am I still missing? IP fader adjusts the booth aux output, so I know post is engaged.

If I change the balance on the Booth output fader, left/right level changes as expected.

[abenessParticipant]

To clarify: surface outs 5 and 6 are patched to my booth monitors.
System won’t allow me to edit my post (fails with a Stop Spammer Registrations prompt, then “Error: Are you sure you wanted to do that?”).

[abenessParticipant]

Another vote for NTP. Just because one person doesn’t connect the system to a network doesn’t mean that no one does. iPad control is essential for us, so we do connect our system to a network. Time is front and center on the main screen. Adding an optional NTP client to the system would be a trivial thing, and would eliminate one of those basic things that is best left to software to manage (well, for the last 30 years or so, anyway). You would be free to use it or not.

No, I don’t use my smartphone while mixing a live show, nor have I worn a wristwatch for 25 years, nor do I have a clock nearby when our board is out in our balcony for a musical. 😉

[abenessParticipant]

Thanks for piping up quickly, Steffen, sorry for delay in getting back. p51 refers to renaming a range of channels, not individual channels–which is cool in its own right. Renaming individual strip is on… wait for it… page 6 (first page of content), 1.1.1. The Harmony UI method is easily accessible and no longer subject to that unfortunate bug on the iLive FW where strip selection didn’t carry over when Name & Color button was pressed, and you might end up changing the name of another strip while thinking (b/c the select indicator was lit) that your currently selected channel was the one you were about to rename. I’ll get used to it.

[abenessParticipant]

Turns out I had an old WRT54GL lying around, and MixPad 1.9 works perfectly with our iDR-32/T112 on wireless-G. I’m running DD-WRT firmware v24-sp2 (build 13064), with WPA2 Personal security. GLORIOUS!

And while I initially thought it was not possible to adjust input routing to AUX channels (monitors), I just found that. SUPER AWESOME!

Abe Hendin

[abenessParticipant]

Relatively new to an iLive T112/iDR-32 here, and just upgraded to 1.9. Has anyone tried to use the new non-multicast MixPad 1.9 on an 802.11g/100Base-T router? I’ve always been delighted with the rock-solid stability (zero drops and months and months of uptime) of the now ancient Linksys WRT54GL with DD-WRT firmware. It may be a dinosaur, but its reliability is unbeatable, and now that multicast is no longer necessary, I have hope. There will be just one iPad on the system, nothing particularly fancy.

Thanks,

Abe Hendin

[Author]

Posts