transcoding of live tv media failing on smart tv

[mammt 5]

Hello, i'm having this issue on my smart tv which emby is failing to transcode a media in "Live TV" even tho it's working fine on my computer and my iphone. here are the logs if you could please take look at.

 

 

embyserver-63863825345.txt ffmpeg-directstream-0219b9d0-f7ee-4008-9304-f6c2f0946316_1.txt ffmpeg-transcode-c591ceb0-c0ca-4cda-8cb7-f302637a1de3_1.txt ffmpeg-transcode-c6010490-edc8-4f67-96af-e5ebb4350c12_1.txt

Edited October 6, 2024 by mammt

[mammt 5]

bump! still need help please

[Carlo 4561]

Hi,
There is a lot going on in your logs with library scanning which might be causing I/O issues.
There is a lot of errors caused by the AniList plugin as well showing up in your logs.

Out of curiosity, is this a new Emby setup?
Are your Libraries still being scanned in?

[mammt 5]

3 hours ago, Carlo said:

Hi,
There is a lot going on in your logs with library scanning which might be causing I/O issues.
There is a lot of errors caused by the AniList plugin as well showing up in your logs.

Out of curiosity, is this a new Emby setup?
Are your Libraries still being scanned in?

well wasn't really new, it was like 2  days old. and no, library wasn't being scanned. but i don't think such things can be the problem since as i said the problem is on the "live tv" tab, and that live tv channel streamed fine on my phone & my windows pc but showed a transcode error on the smart tv

Edited October 8, 2024 by mammt

[Carlo 4561]

OK so it's a new install still doing a lot of background work gathering metadata.
You can turn off debug logging which wis only needed by support when asked, otherwise it's logging everything it's doing, spamming the log file which makes overall reading of the server log file harder and uses more IO as well.

A dev will need to look at this to see why the transcoding is being ended with a quit command.
Can you get a picture of what the Live TV settings are set to on the Samsubg Emby Client?

Carlo

[mammt 5]

2 hours ago, Carlo said:

OK so it's a new install still doing a lot of background work gathering metadata.
You can turn off debug logging which wis only needed by support when asked, otherwise it's logging everything it's doing, spamming the log file which makes overall reading of the server log file harder and uses more IO as well.

A dev will need to look at this to see why the transcoding is being ended with a quit command.
Can you get a picture of what the Live TV settings are set to on the Samsubg Emby Client?

Carlo

the debugging logs were already off as i can see, i have never enabled them.

i'll get the live tv settings of the samsung emby client asap; but i had left them default if that changes anything

[mammt 5]

I just checked the Samsung Emby client, but I don't see any "Live TV" settings. The only option available is "Playback," and none of the settings there mention anything about live TV (even though they are set to auto).

As for the issue on the smart TV, any TV channels that work fine on other TVs, the website, and the iPhone app show an error message. The error on the smart TV translates to: "No compatible streams are currently available."

I've also attached some new logs since I retried again just now.

embyserver.txt ffmpeg-directstream-bcc02cab-bc03-4c46-b40d-ba061d86f16b_1.txt ffmpeg-transcode-e7286805-781f-44a2-b2ca-7a32091f630b_1.txt ffmpeg-transcode-9971528b-3c15-438a-9b6b-0c54ba31d654_1.txt

[mammt 5]

still need help please 

[Carlo 4561]

Thanks for uploading the logs.

A dev will have a look at them.

[mammt 5]

Any News? since i can't play live tv on my smart-tv it's making my experience terrible. i really need it to work

[Luke 42079]

Hi, are you able to play the same channel using the Emby web app?

[mammt 5]

14 hours ago, Luke said:

Hi, are you able to play the same channel using the Emby web app?

from the smart tv or other devices? from other devices it works fine but havent tried on the smart tv will try soon

[Luke 42079]

6 hours ago, mammt said:

from the smart tv or other devices? from other devices it works fine but havent tried on the smart tv will try soon

 

hi, from what other devices have you tried?

[mammt 5]

17 hours ago, Luke said:

 

hi, from what other devices have you tried?

i tried from my iPhone using the emby app and from my computer visiting the website & also the emby threater app 

[mammt 5]

still happening on another smart tv

[mammt 5]

still need help....

[BillOatman 596]

Just my opinion, but I have never been impressed by how "smart" TVs work.  My recommendation is to get something external, even just a FireStick which has a small footprint will work better.

[mammt 5]

3 hours ago, BillOatman said:

Just my opinion, but I have never been impressed by how "smart" TVs work.  My recommendation is to get something external, even just a FireStick which has a small footprint will work better.

wouldn't be an option for me, one of the few things that made me purchase emby was the official android smart tv app.

[Carlo 4561]

On 10/18/2024 at 3:13 PM, mammt said:

wouldn't be an option for me, one of the few things that made me purchase emby was the official android smart tv app.

The Emby team is looking at this and trying to do what it can to handle this better for you. With that said:

Keep in mind your "Smart TV" isn't really that smart. It just has built in apps to let you connect to external services.
These services build multiple streams with different resolutions and bitrates as well as subtitles so that they can pick a stream fitting the device and bandwidth available on the client at the time of playback. All of these streams are created in a format made for streaming. What this does is allow the "Smart TV" to be rather stupid and not have the functionality to handle or adapt to anything other than what these services would typically use.

On the flip side, you're running a personal media server that has media and sources of streams on it that were never design for streaming.  Emby server does a great job of transcoding completed media (ie disk based) when needed that is playable on a vast number of devices available in the marketplace. Many of these devices handle a wide number of different formats and combination of media packages and codecs including those not designed for strictly streaming. Now enter streams being created in real time from a tune or being fetched in real time from a 3rd party source. These streams lack the metadata available on disk-based formats requiring a client that is built with logic and functionality to play them.

This puts you in a situation where you have a powerful media server and lots of media and sources not designed for streaming. You have a client lacking functionality to handle one type of stream you want to use but handles other formats you already have. That creates a predicament for those in this situation. You either need to choose:

• Play only formats from your media server that the client can handle.
• Switch the client device used for Interface and stream playback to something with much greater functionality and logic that handles these types of streams as well as nearly anything else you can serve it. The cost of these devices, start at $30 US dollars for much greater functionality!
• Try and find another vendor solution that satisfies all the requirements you have for your personal media and sources of content that work with your client of choice.
• Wait for a vendor solution to bridge this situation so you can continue to use the "dumb" client you already have.

Solution 1 isn't an option you likely choose to consider.
Solution 3 doesn't currently exist.
Solution 4 is currently in progress but may never be perfect as there is only so much that can be done when the playback device is lacking on so much functionality.
Solution 2 is actually the only option viable if you need a solution usable right now.

This comes down to a matter of need vs want. A matter of how much time you have to invest and tinker to try and a solution to satisfy your wants.

At the end of the day, factoring in your time and $, you'll find that option 2 really is your best option at present and for future media you might at.
 

[mammt 5]

14 hours ago, Carlo said:

The Emby team is looking at this and trying to do what it can to handle this better for you. With that said:

Keep in mind your "Smart TV" isn't really that smart. It just has built in apps to let you connect to external services.
These services build multiple streams with different resolutions and bitrates as well as subtitles so that they can pick a stream fitting the device and bandwidth available on the client at the time of playback. All of these streams are created in a format made for streaming. What this does is allow the "Smart TV" to be rather stupid and not have the functionality to handle or adapt to anything other than what these services would typically use.

On the flip side, you're running a personal media server that has media and sources of streams on it that were never design for streaming.  Emby server does a great job of transcoding completed media (ie disk based) when needed that is playable on a vast number of devices available in the marketplace. Many of these devices handle a wide number of different formats and combination of media packages and codecs including those not designed for strictly streaming. Now enter streams being created in real time from a tune or being fetched in real time from a 3rd party source. These streams lack the metadata available on disk-based formats requiring a client that is built with logic and functionality to play them.

This puts you in a situation where you have a powerful media server and lots of media and sources not designed for streaming. You have a client lacking functionality to handle one type of stream you want to use but handles other formats you already have. That creates a predicament for those in this situation. You either need to choose:

• Play only formats from your media server that the client can handle.
• Switch the client device used for Interface and stream playback to something with much greater functionality and logic that handles these types of streams as well as nearly anything else you can serve it. The cost of these devices, start at $30 US dollars for much greater functionality!
• Try and find another vendor solution that satisfies all the requirements you have for your personal media and sources of content that work with your client of choice.
• Wait for a vendor solution to bridge this situation so you can continue to use the "dumb" client you already have.

Solution 1 isn't an option you likely choose to consider.
Solution 3 doesn't currently exist.
Solution 4 is currently in progress but may never be perfect as there is only so much that can be done when the playback device is lacking on so much functionality.
Solution 2 is actually the only option viable if you need a solution usable right now.

This comes down to a matter of need vs want. A matter of how much time you have to invest and tinker to try and a solution to satisfy your wants.

At the end of the day, factoring in your time and $, you'll find that option 2 really is your best option at present and for future media you might at.
 

great response, thank you! i think i will go for option 2 for now

Edited October 20, 2024 by mammt