-
Notifications
You must be signed in to change notification settings - Fork 161
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
Subtitle codec 94213 is not supported #682
Comments
I believe the plugin performs a container check and does not perform any action if the container already matches the output, e.g. if it is already .mkv and the desired version is also .mkv it will not do anything and thus not actually "force conform". It's not ideal but remuxing an mkv to mp4 and back again with force conform should work. edit this seems to be a common problem (the subtitle codec 94213 error) so I created one of these files to test with by muxing an srt into big buck bunny sample file. HGG has implemented a monitor for this error and the job log alert text for it points to using the Tdarr_Plugin_MC93_Migz1Remux classic plugin with force conform true to resolve, BUT I think it has the same issue in that it doesn't do anything if the container isn't changing. Down the rabbit hole I found that HGG has actually implemented what I would consider a proper fix though which is to directly remove the offending stream without using the container remux force conform method. The solution is either the classic plugin "Tdarr_Plugin_00td_action_remove_stream_by_specified_property" or the ffmpeg flow plugin "Remove Stream By Property" and setting Property to Check = codec_name and Values to Remove = mov_text or Alternatively Property to Check = codec_tag_string and Values to Remove = tx3g (either works). |
Hi,
Getting this error "Subtitle codec 94213 is not supported" when using Flow, using the 'Set Container' as MKV with Force Conform turned on. I would have expected this to remove the unsupported streams, unless I'm incorrect. Is there a way of using Flow to fix this issue?
The text was updated successfully, but these errors were encountered: