Strange error with a show and transcoding error related

[nopenope12345 5]

Hi,

This is a new one for me. I am running Emby 4.8.8.0 on Unraid and streaming to an AppleTV running the latest version of the Emby app.

For some reason Emby cannot play some episodes of a show. On the episode page the media info is showing incorrect information as well. These files have been transcoded to h265 using tdarr but the server still thinks its the old h264 file. 

I have tried to get Emby to notice the file change manually using library and metadata scans but it will not update the files in the database.

I can play these files directly on my laptop with VLC so I know that the files are fine.

Does the fact that the server thinks these are h264 make the transcoding fail? The filenames are unchanged after being changed to h265. 

I have been running this setup for several years and this is the first time this has happened. Transcode log file attached. Thank you!

ffmpeg-transcode-8584cc77-965b-4f42-8032-4d9686478652_1.txt

[Happy2Play 9780]

Have no idea how tdarr process the media but if Emby is not seeing the file change then you will have to touch the file for Emby to see the change.  Note this will remove and readd the item as Emby currently does not know what upgrade file is.

Have you tried Refreshing metadata on one of your issue files?

Edited August 18, 2024 by Happy2Play

[Spaceboy 2573]

i use tdarr as part of the workflow for adding new media to emby, so for me emby doesnt "see" the file until tdarr has prepared it.

i don't use Emby RTM as i don't like what it does, i have a scheduled library scan run as the final step in the workflow

[Neminem 1518]

Jep when move/copy from Tdarr transcoding temp to Emby library is too slow.

Emby will see the awsomemovie-gsjg.mkv file and try to index that file.

When Tdarr is done moving/copying the file Tdarr will rename it to original file name.

And now Emby is confused.

Make sure Tdarr does the atomic move, and Emby wont notice the temp file, and index the right file.

Hardlinks - Atomic Moves - TRaSH Guides (trash-guides.info)

Edited August 18, 2024 by JayceDK

[nopenope12345 5]

10 hours ago, Happy2Play said:

Have no idea how tdarr process the media but if Emby is not seeing the file change then you will have to touch the file for Emby to see the change.  Note this will remove and readd the item as Emby currently does not know what upgrade file is.

Have you tried Refreshing metadata on one of your issue files?

Yes, I refreshed the metadata on the file and also did full library scans but the server does not notice that the file is changed. Does the server ffprobe the files during the library scan? I'm not sure what the mechanism is for it to know that the file is updated.

 

Are you suggesting I simply run a touch command on these files for Emby to notice them being changed?

[Happy2Play 9780]

Normally a scan will see file change and reprocess the media so I can only guess tdarr is changing media in a way that does not trigger change.

But if Refresh is not seeing it either we will probably need to see a server log showing that.

And yes the touch command on a file should trigger Emby noticing file changed.

[nopenope12345 5]

6 hours ago, Happy2Play said:

Normally a scan will see file change and reprocess the media so I can only guess tdarr is changing media in a way that does not trigger change.

But if Refresh is not seeing it either we will probably need to see a server log showing that.

And yes the touch command on a file should trigger Emby noticing file changed.

I really appreciate your insight! After touching the files everything is how it should be.

I'll look into tdarr further because after several years with this setup this is the first time this has happened.