ShadowKindjal 21 Posted January 2, 2019 Posted January 2, 2019 Some of my users are experiencing highly distorted video streams during transcoding.
ShadowKindjal 21 Posted January 2, 2019 Author Posted January 2, 2019 The issue with the stream happened around 9:25 at night Log.txt
ShadowKindjal 21 Posted January 2, 2019 Author Posted January 2, 2019 To resolve the issue I had to role back from the latest beta update to 3.6.0.74
Luke 42077 Posted January 2, 2019 Posted January 2, 2019 Hi there, rolling back is not supported. can you please attach a log file from the latest version? Thanks.
ShadowKindjal 21 Posted January 4, 2019 Author Posted January 4, 2019 (edited) The log from that same night Log 1.1.19.txt Edited January 4, 2019 by nharmon
ShadowKindjal 21 Posted January 4, 2019 Author Posted January 4, 2019 This is another example of the issue happening at 6:45am Log 1.4.19.txt
ShadowKindjal 21 Posted January 4, 2019 Author Posted January 4, 2019 Sorry, here are the two remux and two transcode files for the stream Log (1).txt Log (2).txt Log (3).txt Log (4).txt
ShadowKindjal 21 Posted January 4, 2019 Author Posted January 4, 2019 It seems to just happen on the transcode
ShadowKindjal 21 Posted January 4, 2019 Author Posted January 4, 2019 @@Luke, I know you said rollbacks aren't supported but that seems to be the only way to get emby to transcode correctly
softworkz 5066 Posted January 5, 2019 Posted January 5, 2019 @ - does it work when you disable hardware acceleration? Could you please post the hardware detection log - one from .74 and one from the latest version? There have been changes in the Linux packages regarding AMD drivers for VAAPI between .74 and current, so this might be something for @@alucryd to look at.
ShadowKindjal 21 Posted January 5, 2019 Author Posted January 5, 2019 Hardware detection logs Log (5).txt Log (6).txt
Luke 42077 Posted January 5, 2019 Posted January 5, 2019 @ Can you answer this question as well? does it work when you disable hardware acceleration? Tanks.
softworkz 5066 Posted January 5, 2019 Posted January 5, 2019 Hardware detection logs Thanks, those are identical... What is unusual is that only decoders are detected but not a single encoder. (but that's a different story then) Right now, we'll need to find out what's different between .73 and the latest version. I'm afraid, you'll need to create two more ffmpeg logs to compare .73 vs latest version. Please make sure that - in both cases: You're playing the same file same audio track same subtitle setting (preferrably off) The client settings are the same (e.g. max bitrate) You're playing from the beginning (no resume) We'll need two ffmpeg logs only: Transcoding working with .73 Transcoding failing with .83
ShadowKindjal 21 Posted January 5, 2019 Author Posted January 5, 2019 Same file, no subtitles, limited to 6mbps with no resume Transcode 1.5.19 3.6.0.74.txt Transcode 1.5.19 3.6.0.83.txt
ShadowKindjal 21 Posted January 5, 2019 Author Posted January 5, 2019 @ Can you answer this question as well? Tanks. Disabling hardware acceleration solves the issue. Transcode 1.5.19 3.6.0.83 no HA.txt
softworkz 5066 Posted January 5, 2019 Posted January 5, 2019 @ - Thanks very much for creating the logs. From those logs I can see that the Radeon VAAPI device was not detected with version .73 That means in turn that the hw detection logs that you've posted were not from the two versions. Both were from version ..83 Anyway, the question is no longer about what was "right" with .73 because the VAAPI device simply wasn't detected there. Next steps: 1. Install the latest AMD drivers 2. Post a detection log again We'll no longer need .73. You can stick with .83 and disable hw acceleration (there wasn't any with .73 anyway)
ShadowKindjal 21 Posted January 5, 2019 Author Posted January 5, 2019 @ - Thanks very much for creating the logs. From those logs I can see that the Radeon VAAPI device was not detected with version .73 That means in turn that the hw detection logs that you've posted were not from the two versions. Both were from version ..83 Anyway, the question is no longer about what was "right" with .73 because the VAAPI device simply wasn't detected there. Next steps: 1. Install the latest AMD drivers 2. Post a detection log again We'll no longer need .73. You can stick with .83 and disable hw acceleration (there wasn't any with .73 anyway) I'm not sure if it matters but the version is .74 not .73. Also, I was pretty sure that one log was from .83 and the other was from .74 based on the application version denoted at the top of the log file. Regardless, I will update the drivers and get back to you as soon as I can. Thank you.
softworkz 5066 Posted January 5, 2019 Posted January 5, 2019 I'm not sure if it matters but the version is .74 not .73. Also, I was pretty sure that one log was from .83 and the other was from .74 based on the application version denoted at the top of the log file. Regardless, I will update the drivers and get back to you as soon as I can. Thank you. .73 was just a mistake, but it doesn't matter. For the logs, I meant and wrote 'hw detection logs'.
ShadowKindjal 21 Posted January 5, 2019 Author Posted January 5, 2019 .73 was just a mistake, but it doesn't matter. For the logs, I meant and wrote 'hw detection logs'. You are correct. My apologies. I'll get a new set of logs as soon as I'm able to.
softworkz 5066 Posted January 5, 2019 Posted January 5, 2019 Don't bother with that for .74. We already know that nothing was detected there.
Luke 42077 Posted January 6, 2019 Posted January 6, 2019 So that's the reason the older version was fine, because it was just using software transcoding?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now