|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
MTRX II / DADman -"Sum Error"
I have been occasionally getting a blinking red "Sum Error" in the monitor section of DADman where it usually has a green "Locked". Muting my DVS 7.1.4 output and unmuting it again seems to make it go away. I thought it might be 'clipping' but I can't actually get it to happen again intentionally.
Is it that or what? |
#2
|
||||
|
||||
Re: MTRX II / DADman -"Sum Error"
Quote:
__________________
Jan Lykke Business Development Manager DAD - Digital Audio Denmark |
#3
|
|||
|
|||
Re: MTRX II / DADman -"Sum Error"
I don't think it differs much from this (attached)
|
#4
|
|||
|
|||
Re: MTRX II / DADman -"Sum Error"
Quote:
In DADMan where it says Sum inp -- every time I change the Control Room volume level, either from the surface or from DADman, the Sum Inp first number increases, until it eventually hits 512 and I get 'Sum Error'. Then it stays 'Sum error' until I mute and unmute the DVS 7.1.4 source, at which point the Sum Inp number is set back to a low number. The Sum Inp increment does not happen if the DVS source is muted. The increment also happens each time I press talkback on and off. I could make a video for you but it's exactly as I said above so hopefully that's clear. version 5.7.0.1 Bug for you guys? Does it happen for you? If not I can try to provide more information.. Also not sure where I should submit it.. DAD support? Also, Jeff K. uses this same DVS setup, curious if it reproduces for him.. Last edited by basehead617; 01-25-2024 at 07:13 PM. |
#5
|
|||
|
|||
Re: MTRX II / DADman -"Sum Error"
Just updating this thread - Jan and his guys (thank you!) helped figure out the issue here.
This was happening due to 2 control room monitor outputs (top speakers) not connected to any actual outputs (haven't gotten a 2nd DA card yet). With them temporarily being assigned some kind of output as a workaround, I have no problems. This is a bug that will likely be fixed at some point since those outputs should be ignored but obviously kind of a niche thing so not exactly high priority. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Dadman "Open Recent" menu not showing names correctly | flavor32 | Pro Tools | MTRX & MTRX Studio | 4 | 01-22-2024 10:10 PM |
DADman cannot "find" MTRX after Catalina Sec update | Jeff Schmidt | Pro Tools | MTRX & MTRX Studio | 15 | 03-16-2022 10:42 AM |
Pro tools 9 crashes at startup "Bus error" in thread "MainThread", at address 0x0 | danball | macOS | 2 | 09-26-2011 04:49 PM |
PT9 Session Troubles - "Bus Error" in "Main Thread" & Could not complete the Open... | tohmit | macOS | 5 | 03-23-2011 12:13 PM |
"unable to parse audio file" and "OSStatus Error -208" ! | reichman | Post - Surround - Video | 2 | 03-22-2010 04:46 AM |