Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
Sem;colon wrote:
What you maybe can do is:
-Shorten to DHCP scope of your router, or make an exclusion for one IP Address. (just to make sure that the router won't give the IP of the receiver to another device also)
-After that you turn of DHCP on your receiver and give the receiver one of these excluded IP addresses and the subnet mask (usually 255.255.255.0).
-also you have to give the receiver the IP address of your router as default gateway.
-and optionally the IP address of your router as DNS server.
Wow, Sem;colon, you really hit the nail on the head!
I had already done the first three of your recommendations, but would have never thought that the IP address of the DNS server should actually be the gateway's IP address (I had instead used my ISP's DNS server IP addresses).
I completed step number 4 and Voila, internet radio is back!
it's been a while since I gave you the last update, but as I promised, I won't quit developing this plugin until it works perfect for me.
Sadly this is still not the case, so I will release another new version in the future.
Major changes since last release:
-Better handing of connection problems (please let me know if get any more connection errors)
-Now you will get two events in EventGhost per events that the AVR creates; one with Payload and one without (please let me know if you find some events that are not split correctly)
-You now get every change to the Display of the AVR as an event with payload in EventGhost by default.
Thanks for the continued improvement and sharing, Sem;colon!
I think I will not have time to test before next weekend, but I am interested in seeing the result of the display of the AVR as payload. I wonder if this will mean that the titles of internet radio stations will show up as a payload?
yes, you will see it
But you get a new event every time the display changes - which means you will get a lot of events when you have a scrolling title.
...sadly the receiver doesn't give me that information, but it would be possible to write a script that checks if its scrolling (with matching the prev. event with the new) and adds the new char to a string.
It would then take a little time to get the whole title, but at least you have it then completely in one string.
When starting up (re-enabling) the plug-in, I get all of the Pioneer.Received.Unknown 'XXXX' entries, then as soon as I do something, like press the AutoSurround button on the front panel, I get the error.
it seems like you are using the other Pioneer Ethernet Plugin (yes, there are two for the same thing )
If you have trouble using the other plugin (what was the reason for me to create this second plugin) you could give mine a try (download at the first post) or go to the topic of the other plugin viewtopic.php?f=9&t=3488&p=27349&hilit=+pioneer#p27349
Mine is not as comfortable as the other one, but it runs very stable.
Sem;colon, now that I've got your attention, I hope you won't mind another question. The event Pioneer_AV_NET.FL u" [)(]DIGITAL " doesn't seem to be associated with a payload event. Dragging it to the configuration pane just gives Pioneer_AV_NET.FL. What I'm trying to do is every time the receiver is in Dolby Digital mode, change it to DD EX (0022SR). The 0022SR command works, but I don't have the DD trigger. Is this possible?
kkl wrote:Sem;colon, now that I've got your attention, I hope you won't mind another question. The event Pioneer_AV_NET.FL u" [)(]DIGITAL " doesn't seem to be associated with a payload event. Dragging it to the configuration pane just gives Pioneer_AV_NET.FL. What I'm trying to do is every time the receiver is in Dolby Digital mode, change it to DD EX (0022SR). The 0022SR command works, but I don't have the DD trigger. Is this possible?
well, you never see the payload when you drag the event in your configuration; To trigger on a specific payload like " [)(]DIGITAL " you would have to write a little python script like this:
The problem seems to be that there are no SR**** or LM**** events that are specific for DD mode. If I use AutoSurround to get to DD, I see:
eg_auto.JPG (22.09 KiB) Viewed 9650 times
If I use Direct, I see:
eg_direct.JPG (17.77 KiB) Viewed 9650 times
So, there are numeric codes for the modes that get the receiver into DD mode, but not for Dolby Digital itself. This isn't the fault of the plug-in because Pioneer doesn't seem to provide a code for it, which is why it would be nice to be able to trigger on " [)(]DIGITAL ".
I will try your script example, if I can figure out when to test for that payload. Thanks again.
Sem;colon wrote:I see...
well, the script should work for you
To close this out, yes, it worked great. Thank you very much. It just took me a long time to realize that even though the full payload wasn't displayed, it was still there.
Is it possible to get the Audio input type (Request AUDIO information Parameter by ASCII code) ? I only can get the ASCII value with "?AST" and the output of that isn't an event.
Thank you for the quick reply, and for the plug-in!