ozob

joust, on 24 April 2013 - 08:21 AM, said:

Basically I just copy/pasted the procedure I first posted on 10-2011, that I knew would demonstarte problem.  The specifics of seeing malfunction are related to drive level and resonances/sensitivity/positions of speakers, etc.  So problem MIGHT be harder to notice sometimes.  In my case I did not have to clip or drive into protect - or do anything special really.  Just lucky, I guess.  

However since that time - and playing around - I have found a very easy way to demonstrate issue.
I am convinced problem is related to back emf on a muted channel.  Here is an easy way to see the basic behavior:

Just plug in a monitor wedge to each output channel.  DSP off.  No special settings needed.  Set the wedges on the floor literally faceing into each other a few inches apart.  Play music to both channels and mute one channel.  Adjust drive level and BINGO - amp reads "SHORT" and muted channel turns itself back on.

Certainly not a "real world use" but just to show what can/does happen when conditions are enough to produce sufficient back voltage on a muted channel - that confuses the amp.

2 real world scenarios where this is a problem for me:

a. Trying to write presets for a 3-way system with xover, delay, eq, etc.  Testing and measuring response one passband at a time, thus muting sections and driving others alternatly.  Pretty frustrating when passbands randomly turn themselves back on!  
b. Set up show with floor wedges on floor next to FOH subs.  Band goes on break - mute monitors - play break music and get, "Hey dude, the monitors are still on"!  

joust, on 17 April 2013 - 11:29 AM, said:

Verified, all my XTis are and already were firmware v1.1.5.6.  Latest v SA3.4 and BandManager2.  Not aware of anything newer v wise.

Just try this and tell me what happens:

1. Set up a simple 2 way system on one Xti amp.  A sub on ch1 and a top on ch2.  Use Bandmanager or System Arch.
2. Write a preset with y input and basic x-over at 100hz with independent channels. Store it.
3.Plug in a sound source to ch1 and turn up ch1 front panel knob.  Play some generic rock with good bass.

Everything should sound and work as expected - so far so good.

4. Now use Bandmanager or System Arch. to mute the tops.  You will see button change color and hear only the sub.
5. Now slowly turn up sound source and feed more input to amp.  It may need to be loud - but not stupid loud.
6. As soon as the muted top is sufficiently excited by the sub you will see the amp read "SHORT 2".
7. As soon as the bass drops down or you turn down, the amp channel goes out of "SHORT 2" and forgets that it was muted and BINGO - the tops suddenly come back on by themselves.  This change is not reflected in Bandmanager or System Arch.  They still think the tops are muted.  You have to toggle the mute buttons to get back to condition normal.

So two problems really.  One, the amp interprets back EMF from a muted speaker channel as a short and two, the amp responds by unmuteing itself, and Bandmanager doesn't know it.  

This problem will also happen across amps, as in using one amp for mains and one for monitors.  If you mute the monitors and play the mains such that the monitor speaker is excited, monitors will un mute.

It does not matter if the amp is connected or un connected to Bandmanager or if the mute command is a temporary edit or stored in a preset.

At the time I discovered the problem and during the discussions with Kevin Heber, I had the latest firmware.  I am not aware of any later versions - but I will check anyways and report back.

As far as Band Manager 2, yes I am using it.

Odd now but with BM2, every time I disconnect the usb from any amp- the program self terminates.  BM1 did not do this!

bump

ozob, on 05 December 2012 - 12:10 AM, said:

ok then...........over a year now.........wow time sure flys by

........and no solution / firmware fix / update to address this bug ???

Hard to believe that of the many thousands of XTi and XTi2 users out there that I am the one and only user who finds this malfunction to be a major PITA!...........but there you have it.

Crown must have a pretty good teflon jacket.  I even posted this bug/defect on some "professional" audio forums and was met with resounding disinterest or deafening silence.  Other products have been roasted for far less an issue.

Don't worry, I won't let the door hit my backside on my way out.  So long and thanks for all the fish!