Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Kent Clasen]

We did an event recently and had the DL32 stop passing audio 5 mins before an event! My guys figured out that AES50 port A quit working and connected the STP to port B and DL32 showed up and worked fine.

Brought it back to shop and tested multiple cables (all shielded CAT) but couldn’t get any to work on port A. Left it connected and the next day DL32 shows up as connected on port A and has been left on for about a week and still shows connected on console.

I don’t have much faith in using it on a event though. We had an X32 we sold to a church lose port A about a year ago, but it quit working completely.

Several calls and have emailed Music care, but no response.

Any one else had this happen or thoughts what is happening??

[Kevin Maxwell]

We did an event recently and had the DL32 stop passing audio 5 mins before an event! My guys figured out that AES50 port A quit working and connected the STP to port B and DL32 showed up and worked fine.

Brought it back to shop and tested multiple cables (all shielded CAT) but couldn’t get any to work on port A. Left it connected and the next day DL32 shows up as connected on port A and has been left on for about a week and still shows connected on console.

I don’t have much faith in using it on a event though. We had an X32 we sold to a church lose port A about a year ago, but it quit working completely.

Several calls and have emailed Music care, but no response.

Any one else had this happen or thoughts what is happening??

Did you check the Cat socket on the mixer? I had a problem with a device that somehow got something in the socket and it messed it up. I had to clean out the socket and the pins. I used a flashlight and a magnifier to see what the problem was. It’s possible there was something in there causing the problem and then it got dislodged so it then started to work again.

It’s also possible that the Cat cable is starting to be a problem. The Cat connectors and sockets and cable are not the most robust connection scheme around. But anything else would be so cost prohibitive that it isn’t a reasonable choice.

[Kent Clasen]

Did you check the Cat socket on the mixer? I had a problem with a device that somehow got something in the socket and it messed it up. I had to clean out the socket and the pins. I used a flashlight and a magnifier to see what the problem was. It’s possible there was something in there causing the problem and then it got dislodged so it then started to work again.

It’s also possible that the Cat cable is starting to be a problem. The Cat connectors and sockets and cable are not the most robust connection scheme around. But anything else would be so cost prohibitive that it isn’t a reasonable choice.

Thanks Kevin.

Checked the ports and they both look the same. No damage or dirt.

Also, the day after the event tried 4 different cables and none worked. All worked when plugged into port B. Then a day later A works without changing anything and hasn’t disconnected by itself since in our shop.

[Dan Mortensen]

We did an event recently and had the DL32 stop passing audio 5 mins before an event! My guys figured out that AES50 port A quit working and connected the STP to port B and DL32 showed up and worked fine.

Brought it back to shop and tested multiple cables (all shielded CAT) but couldn’t get any to work on port A. Left it connected and the next day DL32 shows up as connected on port A and has been left on for about a week and still shows connected on console.

I don’t have much faith in using it on a event though. We had an X32 we sold to a church lose port A about a year ago, but it quit working completely.

Several calls and have emailed Music care, but no response.

Any one else had this happen or thoughts what is happening??

Port A could very well have stopped working and you need Music Care to get it fixed and retain warranty.

Call and write them every day until you connect with someone. I don't think there's any other advice that will work.

In the meantime you should keep connecting/disconnecting it and the same cable it didn't work with to see how often it doesn't work and maybe what conditions of plugging/unplugging/length of time powered on/temperature/humidity/stock market prices/time of day connected cause it not to work.

The problem is even if you send it in to them and they cannot replicate the problem they will send it back and you are in the same place you are now.

[Debbie Dunkley]

See... I hate it when I read that companies don't get back to people in a timely fashion. It really affects how I feel about the company and down the road causes me to hesitate when I am making my buying decisions even if their product is the best there is for the money.....

[Kevin Maxwell]

Thanks Kevin.

Checked the ports and they both look the same. No damage or dirt.

Also, the day after the event tried 4 different cables and none worked. All worked when plugged into port B. Then a day later A works without changing anything and hasn’t disconnected by itself since in our shop.

It could be a port that has gone bad as Dan said is possible. On the device I had the problem with I couldn't see the problem till I used a magnifier (jewelers eye loop) that I use a lot for really close up work and a flash light. I could then see something on it and I cleaned it and got it working just fine again. I think I even had to re-bend the contacts in the socket. Unless you really know what you are doing don't try this at home. yo will break something that might not be broken.   

[Tim McCulloch]

See... I hate it when I read that companies don't get back to people in a timely fashion. It really affects how I feel about the company and down the road causes me to hesitate when I am making my buying decisions even if their product is the best there is for the money.....

I agree.  It really pained us to watch how Yamaha strung you out and how the 1st tier JBL support was less than helpful.

Now it's up to dealers, distributors and importers to pick up that ball and the results are better in respects; we've got dealers small and larger that have tremendous customer support and competitive pricing (some of whom are among our participants on the LAB/Lounge).  But they're still stuck with whatever the respective Motherships decide to do, on whatever time line things eventually happen.

But some questions need answers to come from the manufacturer; warranty and after-warranty support need to be timely and competent.  No number of wonderful dealers and user forums can take their place.

[Douglas R. Allen]

Any chance at all there was a scene used with different aes patched? 

Douglas R. Allen

[Michael Lapke]

We did an event recently and had the DL32 stop passing audio 5 mins before an event! My guys figured out that AES50 port A quit working and connected the STP to port B and DL32 showed up and worked fine.

Brought it back to shop and tested multiple cables (all shielded CAT) but couldn’t get any to work on port A. Left it connected and the next day DL32 shows up as connected on port A and has been left on for about a week and still shows connected on console.

I don’t have much faith in using it on a event though. We had an X32 we sold to a church lose port A about a year ago, but it quit working completely.

Several calls and have emailed Music care, but no response.

Any one else had this happen or thoughts what is happening??

Hi Kent,

Douglas makes a good point, is there any chance that was playing a factor?

As for not getting a timely response from CARE, how did you try to contact us? CARE can be reached by phone at 702-800-8290 (US) or +44 1562 732290 (UK) or by sending us an email to [email protected]. Our technical CARE specialists will be glad to assist you with troubleshooting. If they believe you are experiencing a hardware issue then they can also communicate with you on the best way to remedy the situation.

Of course if you're still having difficulties reaching them then please feel free to send me a private message here with your direct contact information and I'll politely ask them to reach out to you.

Hope this helps.

Michael Lapke
Specialist, Community
MUSIC Tribe
BEHRINGER

[Kent Clasen]

Hi Kent,

Douglas makes a good point, is there any chance that was playing a factor?

As for not getting a timely response from CARE, how did you try to contact us? CARE can be reached by phone at 702-800-8290 (US) or +44 1562 732290 (UK) or by sending us an email to [email protected]. Our technical CARE specialists will be glad to assist you with troubleshooting. If they believe you are experiencing a hardware issue then they can also communicate with you on the best way to remedy the situation.

Of course if you're still having difficulties reaching them then please feel free to send me a private message here with your direct contact information and I'll politely ask them to reach out to you.

Hope this helps.

Michael Lapke
Specialist, Community
MUSIC Tribe
BEHRINGER

Michael,

We got a RMA # emailed over the weekend. M32r was shipped yesterday to Nashville, TN.

Tried both of those methods for contact. We are a dealer. In the past they have been quick to reply.

There were no presets involved, but good point. It literally stopped working 5 minutes prior to a performance, then in our shop trying multiple short and long STP cables. Then a day later port A started to work again with same cables, same preset, no changes.

Intermittent, unrepeatable problems are the hardest to troubleshoot. That is why I reached out here. I appreciate all the suggestions and ideas given.

[ProSoundWeb Community]