Forum Replies Created
-
AuthorPosts
-
2022/07/15 at 8:42 pm #108044
We are seeing this behavior with a single IP8 connected – I believe our board is on v 1.13 as well. I see this behavior listed as known issue ID1031 in the v1.03 release notes, but it is not listed under v1.10 notes in either the Fixes or Known Issues list. Seems clear it should still be listed as a known issue right?
2021/09/28 at 11:35 am #103702For the second part – you can use a cheap tablet with Custom Control and have dedicated meters there, you pick the layout and size. Costs money for the tablet, but leaves the built-in screens free for other tasks.
2021/07/02 at 3:39 pm #102189Flow could be – channels to groups (with or without compression), groups to main (compressed) or to matrix (bypass compression), main to matrix. This gives you the double-compression flow you’re looking for. If you have groups that you don’t want to compress, you can send them directly to the appropriate matrix and bypass the main output with its compression. Run your speakers or other outputs from the matrix outs, not directly from the main LR.
Another option is to take instrument group outputs and patch back as inputs (presuming you have enough spares), route those to compressed/uncompressed groups, then to mains. As long as you patch back all instrument groups, they will still be phase coherent with each other at the mains.
2021/04/26 at 6:05 pm #100940OCD Labs has a nice solution, including a Pelican with custom foam for transport. I have one new in the box that I’m no longer going to use. Send me a PM if you’re interested.
2020/09/22 at 7:00 pm #95151There is a way to use the FX sends for external gear. You have to patch one of the effects that has a bypass button, like MultiBD. This then routes the unaffected send directly to the FX return, which you can then patch to an output of the desk. You still need to burn channels for the returns from your Bricasti, but it at least lets you use the mono FX sends of the desk.
2020/09/08 at 12:55 am #94711outside-the-box, you are not doing anything wrong. Having your mixrack sync to Dante is the correct way to avoid clocking issues when using the Dante card. In general, Dante clocking issues can be avoided by adhering to the phrase “the network is the clock”. Every device on your Dante network should derive its clock from the Dante card it contains, and then let the network elect the clock master (unless you have a need for a preferred master).
2020/08/25 at 11:28 am #94359To close the loop here, I got the following response from Jack/Allen & Heath support via a support ticket. In case anyone else faces a similar issue, here’s how to permanently delete the logs from the mixrack:
If you navigate to the history tab, and click the ‘Setup’ button to the left of the screen, you should see an overlay on the history log in blue that says “Event Logs”
Clicking this will show a menu in which you’re able to enable “Show all Event Logs”
The button that previous said “Clear Logs” will now read “Delete Logs” and you will be able to permanently delete the log history.
2020/08/21 at 4:05 pm #94271Related is labels for the channels of the I/O card. For example, you always have external hardware hooked up on the same channels to use as hardware inserts. Would sure be nice to pick a named port instead of just a number for the send/return pair.
2020/08/21 at 3:00 pm #94269Thanks Jack. I verified that the DIP switches are all in the OFF position, and the error persists. I actually just installed Director on a different machine, and after rebooting the DM0 I see a bunch of older errors from 2018, many of which say Internal Error. Should we move this discussion to a support case? I can send the logs.
2020/08/21 at 12:12 pm #94265Actually there is one more message about “MixRack – communication lost to unit”. This message came back from yesterday even after I pressed Clear Logs. Screenshot of history attached.
Attachments:
You must be logged in to view attached files.2020/08/04 at 11:35 am #93860The Dante 64×64 Card allows 64 channels of audio over 64 separate flows and is based on the Dante HC technology (not chip, my mistake!)
That is, you could send 1 channel of audio from 64 separate devices to the card – although it wouldn’t be terribly efficient (wasting 3/4 of bandwidth as each unicast flow encapsulates 4 channels of audio)
I just got the Dante card for the SQ and it has 128 flows. That number is what is reported in Dante Controller so I presume it is correct. As you say, that is enough for every channel in the 64×64 config to have its own flow – amazing.
-
AuthorPosts
