No Compatible stream Error With ASS Subtitles

[NeverExists 21]

This show played fine before updating, and now it won't play with ASS Subtitles. There isn't even any transcoding log. It won't play anything with ASS Subtitles. I went back to the previous beta and now everything works again.

embyserver.txt

Edited May 7, 2022 by NeverExists

[Luke 42083]

Hi, looks like you rolled back from the beta release. That's not supported and is likely the reason for your hate issue.

Why did you do that?

 

[NeverExists 21]

1 minute ago, Luke said:

Hi, looks like you rolled back from the beta release. That's not supported and is likely the reason for your hate issue.

Why did you do that?

 

? I don't understand..... I said when I updated to the new beta version I got that error... then when I went back to the beta before this one, it works fine now. Why did I do that because I would like to watch my content..... is that OK?

[Luke 42083]

This log appears to be from 4.6.7 stable.

[mawa1213 0]

I'm experiencing a similar issue. Running binhex/arch-emby:latest in docker on unraid, there was an update 2 days ago (from 4.6.7.0-3-01 to 4.6.7.0-4-01). Some TV shows didn't play anymore, even stuff I've watched before the update. Got the error "Playback Error No compatible streams are currently available. Please try again later or contact your system administrator for details." 

Here's my log, before I reverted back to 4.6.7.0-3-01:

embyserver.txt

2022-05-08 16:54:21.421 Error Server: Error processing request
	*** Error Report ***
	Version: 4.6.7.0
	Command line: /usr/lib/emby-server/EmbyServer.dll -programdata /config -ffdetect -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartexitcode 3
	Operating system: Linux version 5.15.35-Unraid (root@Develop) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP Thu Apr 21 13:44:00 PDT 2022
	Framework: .NET Core 3.1.20
	OS/Process: x64/x64
	Runtime: usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.20/System.Private.CoreLib.dll
	Processor count: 12
	Data path: /config
	Application path: /usr/lib/emby-server
	System.Exception: System.Exception: No video encoder found for 'h264'

Version  4.6.7.0-3-01 works like expected.

Don't know if it's the container or the software. Hope the log helps.

Edited May 8, 2022 by mawa1213

[Luke 42083]

2 hours ago, mawa1213 said:

I'm experiencing a similar issue. Running binhex/arch-emby:latest in docker on unraid, there was an update 2 days ago (from 4.6.7.0-3-01 to 4.6.7.0-4-01). Some TV shows didn't play anymore, even stuff I've watched before the update. Got the error "Playback Error No compatible streams are currently available. Please try again later or contact your system administrator for details." 

Here's my log, before I reverted back to 4.6.7.0-3-01:

embyserver.txt 315.57 kB · 0 downloads

2022-05-08 16:54:21.421 Error Server: Error processing request
	*** Error Report ***
	Version: 4.6.7.0
	Command line: /usr/lib/emby-server/EmbyServer.dll -programdata /config -ffdetect -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartexitcode 3
	Operating system: Linux version 5.15.35-Unraid (root@Develop) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP Thu Apr 21 13:44:00 PDT 2022
	Framework: .NET Core 3.1.20
	OS/Process: x64/x64
	Runtime: usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.20/System.Private.CoreLib.dll
	Processor count: 12
	Data path: /config
	Application path: /usr/lib/emby-server
	System.Exception: System.Exception: No video encoder found for 'h264'

Version  4.6.7.0-3-01 works like expected.

Don't know if it's the container or the software. Hope the log helps.

@mawa1213 can you use our official Docker? I don't know what's going on with this one and it's ffmpeg build, but I think this will have to be reported to the package maintainer. I would suggest using ours:

https://emby.media/docker-server.html

[NeverExists 21]

3 hours ago, Luke said:

This log appears to be from 4.6.7 stable.

It's wasn't. It was from this current beta. I literally installed the latest beta, tried to play something, got the error, then uploaded the most recent files.

Edited May 8, 2022 by NeverExists

[Luke 42083]

49 minutes ago, NeverExists said:

It's wasn't. It was from this current beta. I literally installed the latest beta, tried to play something, got the error, then uploaded the most recent files.

The log you posted in the first post of this topic is definitely from 4.6.7. You can see it right at the top:

2022-05-07 12:23:37.795 Info Main: Application path: C:\Users\NanoF\AppData\Roaming\Emby-Server\system\EmbyServer.dll
2022-05-07 12:23:38.488 Info Main: Emby
	Command line: C:\Users\NanoF\AppData\Roaming\Emby-Server\system\EmbyServer.dll
	Operating system: Microsoft Windows 10.0.19044
	Framework: .NET Core 3.1.21
	OS/Process: x64/x64
	Runtime: C:/Users/NanoF/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
	Processor count: 12
	Data path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata
	Application path: C:\Users\NanoF\AppData\Roaming\Emby-Server\system
2022-05-07 12:23:38.488 Info Main: Logs path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata\logs
2022-05-07 12:23:38.488 Info Main: Cache path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata\cache
2022-05-07 12:23:38.488 Info Main: Internal metadata path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata\metadata
2022-05-07 12:23:38.488 Info Main: Transcoding temporary files path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata\transcoding-temp
2022-05-07 12:23:38.489 Info Main: Tray icon path: C:\Users\NanoF\AppData\Roaming\Emby-Server\system\embytray
2022-05-07 12:23:38.664 Info App: Application version: 4.6.7.0

Then later in the log you can see additional evidence of rolling back from beta to stable. That is what's not supported.

[NeverExists 21]

Just now, Luke said:

The log you posted in the first post of this topic is definitely from 4.6.7. You can see it right at the top:

2022-05-07 12:23:37.795 Info Main: Application path: C:\Users\NanoF\AppData\Roaming\Emby-Server\system\EmbyServer.dll
2022-05-07 12:23:38.488 Info Main: Emby
	Command line: C:\Users\NanoF\AppData\Roaming\Emby-Server\system\EmbyServer.dll
	Operating system: Microsoft Windows 10.0.19044
	Framework: .NET Core 3.1.21
	OS/Process: x64/x64
	Runtime: C:/Users/NanoF/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
	Processor count: 12
	Data path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata
	Application path: C:\Users\NanoF\AppData\Roaming\Emby-Server\system
2022-05-07 12:23:38.488 Info Main: Logs path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata\logs
2022-05-07 12:23:38.488 Info Main: Cache path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata\cache
2022-05-07 12:23:38.488 Info Main: Internal metadata path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata\metadata
2022-05-07 12:23:38.488 Info Main: Transcoding temporary files path: C:\Users\NanoF\AppData\Roaming\Emby-Server\programdata\transcoding-temp
2022-05-07 12:23:38.489 Info Main: Tray icon path: C:\Users\NanoF\AppData\Roaming\Emby-Server\system\embytray
2022-05-07 12:23:38.664 Info App: Application version: 4.6.7.0

Then later in the log you can see additional evidence of rolling back from beta to stable. That is what's not supported.

Weird cause I have only installed from the beta channel for the last year, so I don't know how your getting that info. Your info is wrong.... 

[Luke 42083]

1 minute ago, NeverExists said:

Weird cause I have only installed from the beta channel for the last year, so I don't know how your getting that info. Your info is wrong.... 

It's the log file you gave us. You can look at the contents from your end as well.

[NeverExists 21]

That may be, but I have only clicked the beta download button for the last year. That is all!

[Luke 42083]

8 minutes ago, NeverExists said:

That may be, but I have only clicked the beta download button for the last year. That is all!

Ok in any event I'm glad to hear it's sorted out now.

[NeverExists 21]

I have been sick with covid these last few days so it is possible I clicked the wrong download

[Luke 42083]

Sorry to hear that. Hope you feel better soon.