Reply to thread

Message

<blockquote data-quote="Doug Lippincott" data-source="post: 123082" data-attributes="member: 7426">Re: X32 DiscussionMy first post, corresponding to my first mix with 2.04 last night.&nbsp; Salsa band in small dance club.&nbsp; After updating to software on my iPad to get a look at it, I realized that I was committed since new iPad app is not compatible with 1.17 firmware and there was no way to go back.&nbsp; (I can&#039;t imagine mixing anymore without being able to interact directly with musicians to set monitors and to be able to mix while listening to what the dancers are hearing in the middle of the room, meaning I had to make the board work with the iPad.)&nbsp; So 4 hours before my gig, I updated the firmware and PC app.&nbsp; Turned out that updating the board was super easy, and it worked fine.I liked the invert function for scribble strips that effectively gives several more colors, and the RTA is really, really nicely done.&nbsp; When saving scenes, the name no longer pre-populates with the name of the last scene loaded.&nbsp; Bit of a PITA to have to enter the whole name again and just change the number I append for the version being newly saved.&nbsp; My list of complaints with the firmware and iPad app stops there.&nbsp; Behringer, you really nailed the firmware and iPad app.And then there&#039;s the PC app.&nbsp; I like to run a couple of instances to put channel meters and buss meters on a monitor attached to a laptop, and I was going to add a third instance for the RTA display.&nbsp; Problem was, the PC apps kept losing communications and stopping.&nbsp; Not all at the same time, just randomly.&nbsp; A few times the meters on one display would freeze, but switching to another set of meters would show operation, and then switching back to the ones previously frozen would restore operation.&nbsp; But mostly I got a popup saying communication had been interrupted.&nbsp; Sometimes on the meters, and almost immediately on the RTA.&nbsp; I don&#039;t think I saw it work more than 10 seconds, and frequently if would stop while copying all of the configuration data from the board.&nbsp; Even as the two meter instances just kept working.&nbsp; It acts as if it&#039;s looking at the integrity of the data being received, and just one unexpected error causes that instance of the PC app to assume a communication failure and stop cold.&nbsp; What the app desperately needs is to keep trying for a while when it thinks comms have gone bad.I never had a problem with the iPad app dropping out while the PC app was consistently failing.&nbsp; Also, I tracked the second act. That added a bit to CPU utilization, but didn&#039;t seem to affect the rate at which the meters and RTA were thinking comms to the board had failed.&nbsp; Fix that Behringer, and then I&#039;ll have absolutely nothing to complain about.Same thing with iPad app.&nbsp; No problems at all.&nbsp; It&#039;s just the PC app that seems to have gone out without enough testing.</blockquote>

[QUOTE="Doug Lippincott, post: 123082, member: 7426"] Re: X32 Discussion My first post, corresponding to my first mix with 2.04 last night. Salsa band in small dance club. After updating to software on my iPad to get a look at it, I realized that I was committed since new iPad app is not compatible with 1.17 firmware and there was no way to go back. (I can't imagine mixing anymore without being able to interact directly with musicians to set monitors and to be able to mix while listening to what the dancers are hearing in the middle of the room, meaning I had to make the board work with the iPad.) So 4 hours before my gig, I updated the firmware and PC app. Turned out that updating the board was super easy, and it worked fine. I liked the invert function for scribble strips that effectively gives several more colors, and the RTA is really, really nicely done. When saving scenes, the name no longer pre-populates with the name of the last scene loaded. Bit of a PITA to have to enter the whole name again and just change the number I append for the version being newly saved. My list of complaints with the firmware and iPad app stops there. Behringer, you really nailed the firmware and iPad app. And then there's the PC app. I like to run a couple of instances to put channel meters and buss meters on a monitor attached to a laptop, and I was going to add a third instance for the RTA display. Problem was, the PC apps kept losing communications and stopping. Not all at the same time, just randomly. A few times the meters on one display would freeze, but switching to another set of meters would show operation, and then switching back to the ones previously frozen would restore operation. But mostly I got a popup saying communication had been interrupted. Sometimes on the meters, and almost immediately on the RTA. I don't think I saw it work more than 10 seconds, and frequently if would stop while copying all of the configuration data from the board. Even as the two meter instances just kept working. It acts as if it's looking at the integrity of the data being received, and just one unexpected error causes that instance of the PC app to assume a communication failure and stop cold. What the app desperately needs is to keep trying for a while when it thinks comms have gone bad. I never had a problem with the iPad app dropping out while the PC app was consistently failing. Also, I tracked the second act. That added a bit to CPU utilization, but didn't seem to affect the rate at which the meters and RTA were thinking comms to the board had failed. Fix that Behringer, and then I'll have absolutely nothing to complain about. Same thing with iPad app. No problems at all. It's just the PC app that seems to have gone out without enough testing. [/QUOTE]

Verification