|
|
Post by wizardofoz on Apr 6, 2015 0:07:40 GMT -5
your wife watching too many late night movies eh?  Needs a programmed macro to turn off the IR rec in the front panel .... also requires not having the app on other PC's in the house hehehehe and being able to lock the front panel too |
|
|
|
Post by wizardofoz on Apr 7, 2015 3:15:51 GMT -5
Had a bit of a crash with the new 3.01 in case anyone else tried it. worked selecting either of the 2 XMC's and I like the help/about info you get. Both units at this time are running V2 firmware. crash appears to happen when one of the units that's not being displayed changes a setting (in my case tuner freq) then it crashes...other giveaway if the tuner freq indication in the app is swapping between one units freq and the other. I'll post a video seems like your code is not IP specific in one more areas and is maybe using an old, broadcast or alternating address then again I could be wrong as it happens when only one XMC is powered up and the tuner is changed by holding the tuner button and rotating the volume. also had a los of sync with the displayed volume and the app volume too. good progress tho...more than we do with anything else out there for now unit selection  info unit 1 and 2   brightness 100  brightness 20  |
|
|
|
Post by Chuck Elliot on Apr 7, 2015 4:07:32 GMT -5
Had a bit of a crash with the new 3.01 in case anyone else tried it. worked selecting either of the 2 XMC's and I like the help/about info you get. Both units at this time are running V2 firmware. crash appears to happen when one of the units that's not being displayed changes a setting (in my case tuner freq) then it crashes...other giveaway if the tuner freq indication in the app is swapping between one units freq and the other. I'll post a video seems like your code is not IP specific in one more areas and is maybe using an old, broadcast or alternating address then again I could be wrong as it happens when only one XMC is powered up and the tuner is changed by holding the tuner button and rotating the volume. also had a los of sync with the displayed volume and the app volume too. good progress tho...more than we do with anything else out there for now Wiz, You are the only on with 3.0.1 for now. Th only broadcast packet should be the Transponder packet which is sent out by the scanning window. Does it show 2 different IP addresses? I'll take a look at the code, but this may be hard to debug with only one XMC-1. Chuck |
|
|
|
Post by wizardofoz on Apr 7, 2015 4:53:15 GMT -5
the displayed tuner freq flip flops from one units setting to the other...PM yr email and I can send you a video
|
|
|
|
Post by ÈlTwo on Apr 14, 2015 8:02:13 GMT -5
FYI: On a lark, while I had my main PC booted with my Puppy Linux USB I installed WINE and ran the XMC-1 PC app. I had no problems running the app, and here's a screen shot:  |
|
|
|
Post by janfier on May 6, 2015 20:40:38 GMT -5
getting parser error: 139. can anybody help me with this.
|
|
|
|
Post by millst on May 21, 2015 12:14:42 GMT -5
|
|
|
|
Post by AudioHTIT on Aug 26, 2015 14:39:14 GMT -5
|
|
|
|
Post by Chuck Elliot on Aug 26, 2015 17:34:39 GMT -5
No, I'll have to check it out. Thanks |
|
|
|
Post by ÈlTwo on Aug 26, 2015 22:43:46 GMT -5
I think the funniest thing is that Keith titled the thread XMR-1
|
|
|
|
Post by millst on Aug 28, 2015 12:44:10 GMT -5
No, I'll have to check it out. Thanks Don't get too excited. Looks like most of the stuff added since the preliminary spec doesn't work. I was able to get zone2 volume working, at least. -tm |
|
|
|
Post by romotiva on Oct 15, 2015 14:24:01 GMT -5
No, I'll have to check it out. Thanks Did you make some changes für FW 3.1 ? I can connect to my XMC-1, however only a screen showing the main buttons appears. Thanks for your higly estimated work !: |
|
|
|
Post by Chuck Elliot on Oct 15, 2015 16:05:00 GMT -5
No, I'll have to check it out. Thanks Did you make some changes für FW 3.1 ? I can connect to my XMC-1, however only a screen showing the main buttons appears. Thanks for your higly estimated work !: I'm going to install 3.1 and work out any bugs over the weekend..... |
|
|
|
Post by Chuck Elliot on Oct 16, 2015 13:06:41 GMT -5
I can verify the issue from "romotiva"
Gonna be a long debug session as I need to retrace all the packets.
Standby......
|
|
|
|
Post by ÈlTwo on Oct 16, 2015 14:43:06 GMT -5
Good luck Chuck.
As always your efforts are really appreciated.
|
|
|
|
Post by Chuck Elliot on Oct 16, 2015 21:05:31 GMT -5
Started looking at stuff tonight. I first problem was that the emotivaSubscription reply packet now contains a "visible" property. Since my XML parser is VERY strict both in content and order this caused a parser crash. Emotiva says this is the correct format: <emotivaSubscription> <power value="On" status="ack" visible='true'/> <zone2_power value="Off" status="ack" visible='true'/> <source value="HDMI 5" status="ack" visible='true'/> <mode value="Surround" status="ack" visible='true'/> </emotivaSubscription> It's not, 'visible' comes before 'status' Work will continue......... |
|
|
|
Post by Chuck Elliot on Oct 17, 2015 20:27:15 GMT -5
Almost there! I have a 3.1 version of the PC App running.
I have not incorporated any of the new features, but it is functional.
You guys want an interim release or are you willing to wait a bit longer???
|
|
|
|
Post by novisnick on Oct 17, 2015 20:33:12 GMT -5
Almost there! I have a 3.1 version of the PC App running. I have not incorporated any of the new features, but it is functional. You guys want an interim release or are you willing to wait a bit longer??? Willing to wait, take your time big guy, thanks for all your work! |
|
|
|
Post by Chuck Elliot on Oct 17, 2015 20:38:20 GMT -5
PS: Just a quick note about 3.1 firmware, Zone 2 volume now WORKS.
|
|
|
|
Post by Chuck Elliot on Oct 21, 2015 10:51:24 GMT -5
Ran into a nasty bug related to 3.1 and perhaps the protocol changes.
It appears that Subscription Notify traffic causes dropouts in the digital audio stream.
This is just optical PCM input on input #1 from my PC.
As soon as I shutdown the program the dropouts stop!
It would seem that processing should have priority over UDP traffic, but this doesn't seem to be true!
|
|
