Jump to content
der_lala

ANSWERED Samsung App fails with "Connection Error"

Recommended Posts

der_lala

Hi

playing some of my files always fails with message" CONNECTION ERROR":/

 

[..]dex=1&VideoCodec=h264&Profile=high&Level=41&MaxVideoBitDepth=8&MaxWidth=1280&VideoBitrate=7689730&AudioCodec=dts&AudioBitrate=360000&MaxAudioChannels=6&MediaSourceId=37be07606503ea8e68d8d8828a8c827c&DeviceId=ZPCAMPY4GXSJS&StartTimeTicks=0 [...]

(it contains h264 but its h265,  is that a coinciedence?).

 

On other devices transcoding works; so I assume the Samsung is the problem.

 

The more I´m playing around with it, I´m coming to the point that a CONCURRENT transcoding of HEVC & DTS is a problem - pls see the att. files.

but

H265 / DD is working

H264 / DTS works

 

Please see the info and logs.

 

tnx for helping me

 

 

 

 

Samsung model number: UE65F8090

 

Samsung firmware version: v1135 (latest available at 25.10.2017)

 

Samsung Emby client version #: v2.2.2

ffmpeg-transcode.txt

server.txt

post-193798-0-57702400-1508950244_thumb.jpg

Share this post


Link to post
Share on other sites
Luke

The app is trying to do something that is not supported. Are you sure you're running the latest version? I thought @@cmcg already resolved this. Thanks.

Share this post


Link to post
Share on other sites
der_lala

latest version of what ?

 

emby server is 3.2.34.0

Samsung app was installed after a firmware update and full TV factory reset today with 2.2.2

Share this post


Link to post
Share on other sites
Luke

Of that Samsung app. That app is a community built and maintained app. We will need @@cmcg to provide input here. Thanks.

Share this post


Link to post
Share on other sites
FrostByte

Cmcg did fix an audio selection problem with 2.2.3b beta.  Maybe try that since the input has multiple audio files to choose from.

 

"Fixed: Unsupported audio codec selected when transcoding."

Edited by FrostByte
  • Like 1

Share this post


Link to post
Share on other sites
Luke

Yea that was it.

Share this post


Link to post
Share on other sites
der_lala

ok, THANKS for that GREAT and FAST support !

 

Updating to 2.2.3b solved my issue indeed.

 

best REGARDS

der_lala

  • Like 1

Share this post


Link to post
Share on other sites
cmcg

Glad that fixed your issue @@der_lala

 

I'll release this as 2.2.3 I think. No need for you to update again.

Share this post


Link to post
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

×
×
  • Create New...