search

GerryDazoo / Slinger

Reuse SlingBox hardware without SlingBox Servers
170 stars 34 forks source link

Can you make a 32-bit version of sling_server.exe #172

Closed Lope0407 closed 1 year ago

Lope0407 commented 1 year ago

The 64-bit version generates a compatability error on 32 bit Windows. Thanks

Lope0407 commented 1 year ago

Forgot to leave my name, Garry Lawson

GerryDazoo commented 1 year ago

Sorry, I don't have the time or inclination to support this. Run the python code or make your own 32 bit executable. Google is your friend. https://pypi.org/project/pyinstaller/

Lope0407 commented 1 year ago

It's not for me, but some of the people in The Slingbox Alternatives, Open Sources, Solutions, etc.. Facebook group. Installing python is beyond most in that group. I did manage to create the 32 bit executable. It has to be done from a 32 bit Windows version, so I built a Win 10/32 image in Virtual Box, installed all the python stuff (and Visual C++ so netifaces will work), and used pyinstaller to generate the exe. It works on both 32 and 64 bit windows (v8 and later). If you want a copy it's at https://drive.google.com/drive/folders/1SVbrdmZLylJZcyS3owRz5SdPpgBjPDID?usp=sharing .

If I may ask a quick question, do all devices use the same codes for the same buttons (up/down/left/right/OK etc) or is there a website you know of that I can get that information from? The sites I found showed long - 20+ characters - for each button, not the 2 digit numbers that I see in your CustomRemotes files.

Thanks, and great work on that fantastic program. Double thanks for converting it to python from perl.

Garry Lawson

On Wed, Oct 26, 2022 at 7:21 AM GerryDazoo @.***> wrote:

Sorry, I don't have the time or inclination to support this. Run the python code or make your own 32 bit executable. Google is your friend. https://pypi.org/project/pyinstaller/

— Reply to this email directly, view it on GitHub https://github.com/GerryDazoo/Slinger/issues/172#issuecomment-1291950289, or unsubscribe https://github.com/notifications/unsubscribe-auth/A32KAO3IBJFNSRMKHVCRMM3WFEO4XANCNFSM6AAAAAAROQFX5I . You are receiving this because you authored the thread.Message ID: @.***>

-- Garry Lawson

GerryDazoo commented 1 year ago

Garry Thanks for doing that. To answer your question. The long string you see is a representation of the data that gets transmitted by the IR LED, sort on on-the-wire. What we send to the slingbox is one level of abstraction away from the IR data. The sling data is a KeyCode that maps to a particular key on the remote type that you configured when you setup the Video Source. The slingbox takes that keycode and maps it internally to the IR data and then poops that out on it's IR blaster. Not all remote definitions are the same but in general all the digits keys and power keycodes I've found to be standard. All the keycodes for the remote get printed out by my code when you start a stream on a configured VideoSource. Up until now figuring out what each keycode does has been a bit of trial and error exercise. We have recently uncovered a cache of info on the Remote Control stuff. See discussion https://github.com/GerryDazoo/Slinger/discussions/165

Yeah, I managed to take 150 lines of perl and turn it into 1500 lines of python. :-)