Hey everyone, I am heading out on vacation and will be returning on July 14th. In the meantime @Atomatth and @ChuckPa have agreed to manage the thread while i’m gone. Once I get back I will work on producing a new build which addresses the issues reported so far.
6 posts were merged into an existing topic: Transcoder Upgrade Preview - Discussion
Does this support Av1 hardware transcoding on windows? At the moment it’s not supported using intel ARC.
@Feanorl av1 hw decode on windows is one of the features this update will allow for and will be one of the forst things i tackle once this update is public and stable
@brainslayer i’m not sure what you are refering to as ffmpeg 7.x provides no additional av1 decoders over 6.1.
Guys, this thread is for bug reports and preformance feedback, if you want to start an additional thread to complain about the choices that were made i’d be more than happy to interact with you there once i return from vacation. However its starting to interfear with the type of feadback we are looking for, which may cause a more unstable launch when this is included in the main product.
Please use this thread for discussion
as far as i know (and i might be wrong of course) 7.x was the first ffmpeg with official av1 support. and 6.1 had av1 only using a external patch. if i’m wrong. accept my excuse
Sorry that I haven’t had a chance to read through this entire thread in detail, but what do you think the best course of action is for this issue? Rollback server version? Any config change that will help maybe?
I also am using the HD Homerun, but on a Nvidia Shield. I think it’s the same issue, but not recording, just streaming.
Client: /video/:/transcode/universal/decision… status: 400
Console log:
TranscodeUniversalRequest: unable to get container: /livetv/sessions/5eb408b4-7919-43cb-8428-cff1fde33c9e?includeBandwidths=1&offset=-1&X-Plex-Incomplete-Segments=1&X-Plex-Session-Identifier=3552cd1bb9f682fd-com-plexapp-android
Please share the entire zip of your PMS logs.
Please do check out this issue, which is still happening with some QSV devices.
Can you please stick to the topic and purpose of this thread.
I did skim through your linked thread and grabbed any still available sample files. However there is a lack of logs and feedback in that thread while using this preview build. Please install this preview and provide feedback. Most importantly your PMS logs (please enable debugging logging). Your logs, with or without errors entries around your playback sessions, are still important and provide context to how PMS is handling playback.
It is related to transcodes, and it is a bug. How is it not related to the topic when we’ve had this bug for the past 2 years, and only on Plex. The old thread has no more employees replying, even tho some employees confirmed the bug.
Thanks!
Missed that comment. I’ll sync up with @chrisallen
May I get a sample of that video file to replicate the problem?
( I now have a 12-gen NUC )
I am not sure if this contains the same sample that is mentioned in the now broken download link, but this one is still available for download.
Yeah, those are accurate files. Sorry, cleaned up my gdrive a few months ago. If you need any testing from my end, let me know- I have my proxmox cluster with a 10th gen and 12th gen and can migrate the PMS LxC between the two to reproduce/resolve the issue at-will.
@Atomatth i see the issue from this report is not in the known issues list at the top of the thread. is that because it is not considered a transcoder issue? I ask because the issue was repoducible by @BigWheel if you look in the thread that was quoted and the response was that to fix it require the ffmpeg update, i.e. this forum preview. thanks for the work.
As I posted over here Pixel 8 Pro reports EAC3 is supported, but EAC3 content fails to play - #53 by Gavin-Ashford this transcoder preview has seemingly helped a little with the Pixel EAC3 (with Atmos?) issue by attempting direct play and finding it fails and falls back to transcoding when it can’t. However from my limited testing (and with the older, non-new UI, Android app) its certainly not resolved all the instances; some still fail as before. If the intention is that in all instances of f…
There were a couple previous issues that fell into the same bucket “FFMPEG bump should fix this”. Looks like this one just fell through the cracks. Thanks for reviving it! Looking into the specifics now. If you can continue to test with this forum preview, enable debug logging, and share your PMS logs (client logs too) that would be helpful. I’m asking BigWheel for the same. The more data points the better. Thanks again!
I tested the movie fragment “1917” on my i9-12900 Ubuntu 22.04
- I see no video artifacts in the conversion
- I see standard HEVC HDR stream with a reduced bitrate
Input #0, matroska,webm, from 'Test_Movie (1080p 10bit x265 AAC 7.1).mkv':
Metadata:
title : 1917
encoder : libebml v1.4.4 + libmatroska v1.7.1
creation_time : 2023-02-27T13:31:43.000000Z
Duration: 00:04:57.40, start: 0.209000, bitrate: 5704 kb/s
The original movie is: (I ripped it from the disc)
Input #0, matroska,webm, from '/glock/media/uhd/1917 (2019) [2160p]/1917 (2019) [2160p].mkv':
Metadata:
title : 1917
encoder : libmakemkv v1.17.7 (1.3.10/1.5.2) x86_64-linux-gnu
creation_time : 2024-09-14T20:48:08.000000Z
Duration: 01:58:59.49, start: 0.000000, bitrate: 81195 kb/s
Likewise, there are no visible defects in the Anime.