-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playback fails after upgrade to plex 1.4.1 #52
Comments
I can confirm this issue, it's a weird one that only seems to fail in my tests on remote nodes, I'll have to try and pin it down. They've made some large changes around GPU & DVR support although from my initial observations I suspect there's some variables changed/added as it gets all the way through to the decoder on the remote nodes then just doesn't run. |
I'm having no problems with the current version, running on Plex 1.4.2.3400 |
Hi, Have tried today with 1.4.2.3400 and get the exact same symptoms, it appears to transcode, but according to plex its Buffering and never begins playing although transcode continues. |
Im having the same issues as above. Any pointers? The transcoding starts and there are no errors I can find, but the client just keeps saying buffering. |
I'm running into this issue as well on 1.4.4.3495. Is this still being investigated? |
I have some time today to investigate. Stand by... |
@zfreak782 @UsbBitMinter @speedminion87 @Awarua- I was able to get this working on fresh install of For future reference, this is how I debugged this. On the master host open |
@wnielson not working for me. it's always trying to connect to localhost.
|
@wnielson |
You're getting an
Your ffmpeg looks old--you're on
|
@zfreak782 |
@wnielson Sorry for the delay! Life gets busy. Using the debug instructions you provided, I selected a movie to watch and captured the logs. I'm seeing a large number of connection refused errors in the prt.log. It looks like it's trying to connect through the Plex port (32400). How should I proceed? |
@zfreak782 I removed your attachment because it contains tokens and strings that shouldn't be shared. I fixed the connection refused issues that you were seeing in the version that I created today. I'm not sure that'll fix the issues you're seeing, but you should take a look and see if that helps. I don't see anything else in your logs that would explain the distortion you are seeing. |
Thank you! I was unaware this information was present... Perhaps I should clarify on distortion. The video plays for a second and then freezes on a very distorted looking image and then the picture goes away, showing me a giant play button in the middle. With smaller video files (250-700MB) the video will intermittently come back, but the audio is not always in sync. I have yet to see it intermittently come back with a large video file though (10GB+). I will test the version you mentioned this weekend and report back |
@wnielson When trying to run warning: no previously-included files matching '' found under directory 'docs/_build' I'm unfamiliar with python and am unsure if this is on my end or not. Please advise. Something I noticed is that if the slave I enter in the .prt.conf is the same server as the master, it transcodes without issue. If I'm thinking about this correctly, I want to say that the transcoder communicates back with Plex over localhost IP 127.0.0.1. That being said, I would think this somehow needs to change, or be forwarded to the master. Perhaps I'm way off though. Or perhaps the change you made intended to do something like this? |
The newest version requires
If you enter the |
@wnielson That fixed the connection refused issues. It appears that all the NFS communicaiton is just too much for my Raspberry Pi 3's to handle. I can confirm that NFS works fine with a unidirectional connection (IE, only reading from NFS media library) but when you add another connection and/or have it write, the performance degrades significantly. I believe this to be the case due to the fact that that playback performance seems to depend heavily on bitrate. The movie file in which I had most difficulty had a bitrate of ~15000kbps. I had significantly fewer issues (though not smooth playback) with a file around ~1400 kbps. I appreciate the time you've dedicated to helping me out. If you feel my conclusion is incorrect for whatever reason, please let me know as I would really like to use PRT if possible. |
So Pi3 has 10/100 Ethernet so 150000 Kbps will never work as the max throughput is 7-8 Mbps which is 50% short of your requirements. Take a look at replacing file server with ASUS's Pi equivalent which has gigabit. |
@zfreak782 You're conclusions seem reasonable to me. The Pi is a pretty limited device, so I'm not surprised that you are experiencing some issues pushing large amounts of data around while also taxing the CPU with a heavy encoding task. That said, it would be pretty cool if we could reliably use a Pi as a transcoding slave, so if you continue testing and can find a configuration that works keep us posted! |
Running with latest git download on plex 1.5.2, works just fine. But cant skip/seek just launches multiple plex_transcode sessions on remote host so this one could be closed unless others are still having problems? |
@dhruvb14 My issue isn't with the file server Pi but with the transcode slave Pis. I can pump in a 15,000kbps video without issue, it's pumping it back out to the transcode directory that the IO limit is reached. @wnielson In all my testing, I've never been able to reliably video transcode. However, audio transcode works like a dream. I wanted to have a cluster of Pis talking to the PMS master Pi that would transcode the audio for me and direct play the video. I've read somewhere that, while not full gigabit, the pi3 has seen substantial speed increases with a USB gigabit adapter. May pick one up and see if that provides the bandwidth I need. As this is not the best place to post findings, where should I follow up in the event that I do try the usb ethernet adapter? The only way I can see the Pi being a viable option for transcoding is if we had a way to distribute a single transcode jobs across multiple Pis. That may be way out of desired scope for PRT, but I would be seriously interested in a project that could provide such functionality. |
@zfreak782 I'm interested in your findings too; perhaps you could start a new issue related to Pi… @wnielson let us know if you'd rather not tho |
@zfreak782 Checkout this PR which distributes chunks of the transcode over multiple machines. |
@wnielson I would love to see something like this! Even if it was only as an optional feature. I didn't realize anything like that was out right now. If you want my vote, I say add it. Given it's instability I would understand if this was an optional feature that received limited support or work after the main functionality. While I can't be much help on the Python side of things, I would be more than happy to test and provide feedback. I have 4 or 5 Pis just laying around waiting to do something! |
@hughker I'll probably give the RP @wnielson mentioned a shot and see how it works for me. I'll be sure to keep you posted. @wnielson Please keep me posted on the decision to integrate or not. I'll try to do some testing this weekend and will create a new issue related to it all unless you advise posting it elsewhere |
Good Day to you all, and may I once again thank all of those involved in this project. Truly an amazing feature which should be part of plex by default.
Anyways, I'm hoping someone can shed some light on the latest issue when they have a moment,
I have had the remote transcode working perfectly up to version 1.3.4.3285.
After an upgrade to the latest 1.4.1.xxx release there seems to be something very slightly amiss.
I go through the usual steps of upgrade by, removing plex_transcode, upgrade plex, re-run prt install etc, I then restart plex for good measure.
When I try to play a file on my iphone for example, I can see it appear in Now Playing, and i can see that prt has started the transcode job on the remote server, but nothing actually plays.
Under Now playing it just says Buffering (this is over wifi where it worked moments before the upgrade) and just stays like that indefinitely until I press stop and it ends the transcode job, no errors to be seen.
I then rolled back to 1.3.4, followed the above steps and everything works great again, tried the upgrade once more, and again back to the buffering and no play.
So to summarise, after the 1.4.1 upgrade and re-install of prt...it seems to begin the transcode fine, but never seems to start playing, and according to plex its Buffering.
I hope this can be tested and fixed easily for now I have rolled again back to 1.3.4 and all is well again.
Thanks for all your support in this project
SpeedMinion.
The text was updated successfully, but these errors were encountered: