Jump to content

3.5.2.0 Playback Error - no compatible streams


keithterrill
 Share

Recommended Posts

keithterrill

System information:

 

 

RELEASE=18

CODENAME=sarah
EDITION="Cinnamon 64-bit"
DESCRIPTION="Linux Mint 18 Sarah"
DESKTOP=Gnome
TOOLKIT=GTK
GRUB_TITLE=Linux Mint 18 Cinnamon 64-bit

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 42
Model name:            Intel® Core i5-2400 CPU @ 3.10GHz


I have not been able to run my server for a few months. I booted it back up and attempted to watch something, anything via Roku but it wanted to be updated. So, I came down to the server and discovered it wanted to be updated too. So, I updated it to 3.5.2.0 as per the Linux down load. I used the Debian installer. Then I launched the emby via local:8096 and got the error:

 

Playback Error

No compatible streams are currently
available. Please try again later or contact

your system administrator for details.

 

I have searched the forums and attempted the fixes I found. None have worked. I cannot play from the emby web site, I cannot play from other computers on my intranet, I cannot play on the Roku. I changed the /etc/emby-server.conf as one had suggested would work. It did not.

I can play the movies using VLC so I know I can play it back and the drives are good.

I have posted a couple from when I fist started, as well as the last few logs.

Let me know what else you need to know.

 

embyserver.txt

ffmpeg-transcode-0a7df318-923b-4ab7-9359-6774596ed00b.txt

ffmpeg-transcode-00bc712d-2371-459e-bb2c-f1ed9a5301e9.txt

server-63670289077.txt

ffmpeg-transcode-faa99a2d-1f81-41f7-beb7-ef73c3f1b17c.txt

Link to comment
Share on other sites

keithterrill

Looks like ffmpeg is having issues.

 

You could try reinstalling or using an older version of ffmpeg.

 

Krs

 

Mark

 

 

This answer is like the Microsoft Standard answer for all problems: reinstall.

 

So, for grins and giggles, I grabbed a hard drive not in use and installed a new OS (Linux Mint 19) and then installed emby 3.5.2.0. Then I took the media hard drive and mounted it into this new system (via fstab), and booted up. I set up two users and added the libraries to the new system. Since I placed this new system on the same node, etc. there wasn't anything else to do.

 

I fired up the client browser and it worked.

I went to another computer on the network and fired up a client browser and it worked.

I went to a roku and fired it up and it worked.

 

Nothing more to do.

 

BIG GRIP AND COMPLAINT THIS IS NOT THE FIRST TIME THAT EMBY WAS UPGRADED AND THE WHOLE SYSTEM WENT TO #$%^&. Before I had to just take the library off line, rename it, put it back on line, and add it again. That didn't work for this last upgrade.

 

But, why or why should we have to reinstall, rebuild, etc.??? Why should a new upgrade break the system.... were not talking about an obscure little used hacked together Linux system. We are using an out of the box most popular distro built on the most used home distro.

 

And.... the only help we get is reinstall or depreciate to something earlier? Really?!?!?

Link to comment
Share on other sites

Hi, you shouldn't have to do that. I hadn't yet responded here but this topic was on my list for review. I am glad you were able to get back up and running. Apologies for the disruption.

Link to comment
Share on other sites

keithterrill

Hi, you shouldn't have to do that. I hadn't yet responded here but this topic was on my list for review. I am glad you were able to get back up and running. Apologies for the disruption.

 

I agree. The good news is that I pulled the hard drive with the system. I did not destroy it. I can put it back into service. Considering that the Linux Mint 19.0 is giving me problems in other area that is what will happen.

 

So, if you can help with the emby installed on the original drive... would be appreciated.

 

And, I apologize for thinking the advice coming from support was:

 

 

 

Looks like ffmpeg is having issues.

 

You could try reinstalling or using an older version of ffmpeg.

 

;-)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...