Log in
Register
Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Dan Mortensen" data-source="post: 205659" data-attributes="member: 2826"><p>Hey, the new Sound Forums has a "like" button on each post and a counter for likes! That seems like a good idea.</p><p></p><p>On-topic: I finally called Behringer Care last week as a result of posting in this thread to find out about the Producer they've had for a while. They were surprised nobody has called me.</p><p></p><p>The problem was that it would then wouldn't talk to a wireless access point like an Airport Express. I've mentioned way earlier in the thread that I've had many problems with AE's directly connected to the console either stop working or not connect to the console when first trying, then randomly connect an hour or two or some amount of time later, and that I discovered that if I put a switch in between the AE and the console it would instantly connect and stay connected Every Single Time.</p><p></p><p>In this case, even with a switch, it would connect and then some random time later stop connecting and never connect again. Swapping AE with Linksys EA4500 made no difference; a different Producer would connect to both modems but not the problem console.</p><p></p><p>Sending it back to Care in July or so resulted in it working again, but checking it before a show in October had it working for an hour or so, then I watched while the image on the iPad grayed out and it was the same old problem, refusal to connect to console. So I sent it back to care in November, I think.</p><p></p><p>Last week when I called, the tech (not a customer paperwork coordinator, but a long time tech) said they don't like AE's and don't recommend them, but had never heard of the switch solution. He said that their testing showed it worked, but when I explained my experience with the consoles and belief that the console DIDN'T work, agreed to leave it powered up over the weekend. </p><p></p><p>He called on Monday and said that indeed it did NOT connect to their Linksys modem (which is the only one they use for testing- didn't get the number), so they will have a specialist look into it and figure out what is intermittent with that port/guts.</p><p></p><p>I mentioned to him that the only other problem I've had is one AES50 port stopping working, and he said that was a result of using unshielded cable and having ESD (electrostatic discharge) problems and the driver for the port getting zapped. He also said in response to a question that each AES50 port has its own driver.</p><p></p><p>I pointed out that Behringer initially recommended using any CAT5e cable that was available at every hardware store, and that their tune changed in response to problems discussed here and on another live audio forum where users had dropout problems caused by ESD, and that Brian Wynn conclusively showed that you had to use shielded cable and connectors with Ethercon shells to be immune to ESD. The tech chuckled about the hardware store part and seemed to not know about the forums discussions, but I know Uli was aware at the time.</p><p></p><p>So there's my two big problems with the consoles which are small potatoes in the scheme of things. As I said earlier, they are great consoles and keep working (with these two exceptions). The one with the bad AES50 port is way out of warranty, fyi, and has been repurposed to a use where it won't need to use AES50 ports, which I'm happy with.</p></blockquote><p></p>
[QUOTE="Dan Mortensen, post: 205659, member: 2826"] Hey, the new Sound Forums has a "like" button on each post and a counter for likes! That seems like a good idea. On-topic: I finally called Behringer Care last week as a result of posting in this thread to find out about the Producer they've had for a while. They were surprised nobody has called me. The problem was that it would then wouldn't talk to a wireless access point like an Airport Express. I've mentioned way earlier in the thread that I've had many problems with AE's directly connected to the console either stop working or not connect to the console when first trying, then randomly connect an hour or two or some amount of time later, and that I discovered that if I put a switch in between the AE and the console it would instantly connect and stay connected Every Single Time. In this case, even with a switch, it would connect and then some random time later stop connecting and never connect again. Swapping AE with Linksys EA4500 made no difference; a different Producer would connect to both modems but not the problem console. Sending it back to Care in July or so resulted in it working again, but checking it before a show in October had it working for an hour or so, then I watched while the image on the iPad grayed out and it was the same old problem, refusal to connect to console. So I sent it back to care in November, I think. Last week when I called, the tech (not a customer paperwork coordinator, but a long time tech) said they don't like AE's and don't recommend them, but had never heard of the switch solution. He said that their testing showed it worked, but when I explained my experience with the consoles and belief that the console DIDN'T work, agreed to leave it powered up over the weekend. He called on Monday and said that indeed it did NOT connect to their Linksys modem (which is the only one they use for testing- didn't get the number), so they will have a specialist look into it and figure out what is intermittent with that port/guts. I mentioned to him that the only other problem I've had is one AES50 port stopping working, and he said that was a result of using unshielded cable and having ESD (electrostatic discharge) problems and the driver for the port getting zapped. He also said in response to a question that each AES50 port has its own driver. I pointed out that Behringer initially recommended using any CAT5e cable that was available at every hardware store, and that their tune changed in response to problems discussed here and on another live audio forum where users had dropout problems caused by ESD, and that Brian Wynn conclusively showed that you had to use shielded cable and connectors with Ethercon shells to be immune to ESD. The tech chuckled about the hardware store part and seemed to not know about the forums discussions, but I know Uli was aware at the time. So there's my two big problems with the consoles which are small potatoes in the scheme of things. As I said earlier, they are great consoles and keep working (with these two exceptions). The one with the bad AES50 port is way out of warranty, fyi, and has been repurposed to a use where it won't need to use AES50 ports, which I'm happy with. [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
Top
Bottom
Sign-up
or
log in
to join the discussion today!