der_lala 1 Posted October 25, 2017 Posted October 25, 2017 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
Luke 40082 Posted October 25, 2017 Posted October 25, 2017 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.
der_lala 1 Posted October 25, 2017 Author Posted October 25, 2017 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
Luke 40082 Posted October 25, 2017 Posted October 25, 2017 Of that Samsung app. That app is a community built and maintained app. We will need @@cmcg to provide input here. Thanks.
Solution FrostByte 5257 Posted October 25, 2017 Solution Posted October 25, 2017 (edited) 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 October 25, 2017 by FrostByte 1
der_lala 1 Posted October 25, 2017 Author Posted October 25, 2017 ok, I ll try this one named here : https://emby.media/community/index.php?/topic/48756-223b-audio-transcoding-fix/
der_lala 1 Posted October 25, 2017 Author Posted October 25, 2017 ok, THANKS for that GREAT and FAST support ! Updating to 2.2.3b solved my issue indeed. best REGARDS der_lala 1
cmcg 875 Posted October 26, 2017 Posted October 26, 2017 Glad that fixed your issue @@der_lala I'll release this as 2.2.3 I think. No need for you to update again.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now