Jellyfin Forum
Issues playing DV (profile 5) via DirectStream or Transcode - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Issues playing DV (profile 5) via DirectStream or Transcode (/t-issues-playing-dv-profile-5-via-directstream-or-transcode)

Pages: 1 2


RE: Issues playing DV (profile 5) via DirectStream or Transcode - xenoexclusive - 2024-07-30

Hello again! Sorry for the necro.

I've finally got around to trying this again after a very busy time.

Have got the paths correct and I'm still struggling. It looks like the command you mentioned is doing a full (and very slow surprisingly) transcode as opposed to simply changing the container. I'm currently several hours into a transcode for a 1 hour episode.

Is there something I'm missing?


RE: Issues playing DV (profile 5) via DirectStream or Transcode - TheDreadPirate - 2024-07-30

I have gained a lot of ffmpeg experience since that post.

Code:
/usr/lib/jellyfin-ffmpeg/ffmpeg -fflags +genpts -i "/path/to/your/video.mkv" -map 0 -codec copy newFile.mp4



RE: Issues playing DV (profile 5) via DirectStream or Transcode - xenoexclusive - 2024-07-30

Hey mate! Hope you are well.

Interestingly, after waiting several hours for the previous transcode to finish, I just tried the mp4 file and it was still doesn't work. The mkv file log shows a DirectStream attempt. The mp4 log shows a Transcode. But BOTH are green/purple unless I play with a profile that doesn't allow transcoding (which results in the correct DV image and shows as a Remux). I'm starting to think it's potentially little to do with my setup and more to do with the Android TV app.

I will try your command now and update you!

EDIT: This is the result:

Quote:[mp4 @ 0x5a1758944cc0] track 1: codec frame size is not set
[mp4 @ 0x5a1758944cc0] Could not find tag for codec subrip in stream #2, codec not currently supported in container
[out#0/mp4 @ 0x5a1758947300] Could not write header (incorrect codec parameters ?): Invalid argument
[sost#0:26/copy @ 0x5a175890fb40] Error initializing output stream:



RE: Issues playing DV (profile 5) via DirectStream or Transcode - TheDreadPirate - 2024-07-30

Ok. For testing, let's remove the subtitles.

Code:
/usr/lib/jellyfin-ffmpeg/ffmpeg -fflags +genpts -i "/path/to/your/video.mkv" -map_chapters 0 -c:v copy -c:a copy -sn newFile.mp4



RE: Issues playing DV (profile 5) via DirectStream or Transcode - xenoexclusive - 2024-08-04

No error this time! And no green/pink tint. But the actual problem I care about is still not solved :'(

Unfortunately the new mp4 is still not playing in HDR and still the only way to play these DV files in HDR/DV is by making a user that does not allow transcodes, which results in a log listed as 'remux' but plays the video correctly (with other issues like subtitles and seeking problems). In fact, the new mp4 file with a user that does not allow transcodes results in 'too many errors. giving up' whereas the original mkv plays video correctly.

Really appreciate your patience with me.


RE: Issues playing DV (profile 5) via DirectStream or Transcode - xenoexclusive - 2024-08-05

Oh boy. I think I've just solved it.

Was just reading in the new Android TV app release announcement and read something that gave me an idea. I changed the client app behaviour from 'Downmix to Audio' to 'Direct' in the audio section, and now the original MKV file is playing in DV without tints and working perfectly :')

Thanks so much for your help!! Apologies for wasting so much of your time.

Kindest regards.