Closed robosmith closed 1 year ago
Might there be a bug or two, quite possibly. I'll need to fire my crack team of system testers. But comments like this are particularly unhelpful. Could you be a little more specific about what "kinda worked" means. Also some more details on the "crash". Can you reproduce it? If so please response with some useful information. I've not used anything except SlingerPlayer for streaming since Christmas and others have had no issues. Here's some comment's I've received, "Used V4 to watch TV last night and it worked really well." "player runs solid." "this is dang near like watching normal TV with the player response time"
I have been running Slingerplayer 4.0 on a Surface Go (small tablet) for the last 3 days and see no issues. The only thing I would want to improve is scaling the remote to fit in the space available.
Jeff, RE: Remote. The remote window is a "standard" browser. You can resize the text with the ctrl +/-. But as you know depending on the remote type, text or HTML it gets redrawn when the key click gets posted. You can always just make your remote window bigger. Unfortunately I haven't been able to figure out how to make the remote fit the window. If there's any Javascript/HTML experts out there an example would be helpful. But it would seen that trying to make that work is counter-intuitive to how web pages are supposed to be rendered. But what I've done is I just changed the remote definition file to use a smaller font which is fine for running on the PC. The original default size was one I picked out of the air was to make the buttons big enough for my fat fingers to press when using my phone for a remote.
only time I get a crash is when my remote (PR) slingbox is having connection issues.
works fine internal network.
Try this. It gets rid of the MemoryLeak dialog when you X out the app while it is trying to connect.
Might there be a bug or two, quite possibly. I'll need to fire my crack team of system testers. But comments like this are particularly unhelpful. Could you be a little more specific about what "kinda worked" means. Also some more details on the "crash". Can you reproduce it? If so please response with some useful information. I've not used anything except SlingerPlayer for streaming since Christmas and others have had no issues. Here's some comment's I've received, "Used V4 to watch TV last night and it worked really well." "player runs solid." "this is dang near like watching normal TV with the player response time"
Kinda worked means it was able to display video initially, but when I sent commands to the Tivo they took a long time to show up on the screen; much longer than a freshly run VLC. I will try your new release and see if I can nail down exactly what conditions cause a crash.
I'm seeing the exact same error. Server is a Raspberry Pi running on Debian Bullseye 64bit lite. It happens when starting to connect on SlingerPlayer and it never finishes the connection. The only way I've found to work around it is to shutdown SlingerPlayer and restart. That error box appears on the screen right after shutting down. The Slingbox ProHD is connected to a TiVo Mini.
It's not really an error, it's some debug code that I forgot to turn off. Use the exe I posted earlier.
Robo, An out of the box VLC has about 4 seconds of default buffering, SlingerPlayer out of the box is configured with minimal buffering. I'm seeing response times of about a second. So there's something else going on.
I am using the exe on a Windows 10 laptop although it is the one dated 1/15/2023. The video resolution on the versions that were posted this month don't fill the screen vertically. The video resolution is set to 16 although I've also tried a setting of 12 with the same result. The error screen seems to only happen when connecting to the Sling server on the Pi. I've installed the server on three Windows PCs and SlingerPlayer doesn't exhibit the same issue.
Please post a screenshot. Fullscreen should be fullscreen no matter what.
What are you feeding the Pro? looks like you've got a 1920x540 video stream. I was just watching that channel. Her'e what I see with the same parameters.
ProHD Selecting Video Source 3 ProHD Keycodes= [1, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 21, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 35, 36, 38, 39, 40, 41, 42, 43, 44, 46, 53, 56, 57, 59, 60, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80] VideoParameters: Resolution= 16 FrameRate= 30 VideoBandwidth= 2048 VideoSmoothness= 63 IframeRate= 5 AudioBitRate= 96
What device are you viewing on?
And here is what I get with the one dated 1/15/2023
The Pro-HD is connected to a TiVo meaning. I'm not sure what is included in the updates but this version works flawlessly.
I'm viewing this on a HP Envy Windows 10 laptop.
Found the problem. Just loaded SlingerPlayer dated 02/17/2023 and it works again. The file I was having the issue with was from 02/13/2023.
Slinger Player stuff now has it's own repository https://github.com/GerryDazoo/SlingerPlayer
Tried out the new 4.0 release sw with SlingerPlayer and it kinda worked but crashed. On shutdown, it displayed a memory leak dialog;