Orsay Installation problem on UE40D6500

[FrostByte 5042]

Okay, I have 1.06 on my web server and can load that and test.  Will try 2.2.4 also if there's issues.

 

 

In the app settings is DTS playback turned off?  I would assume that's why it's requesting a transcode.  My TV supports DTS, but I can turn that off to force transcode

[SamES 890]

Yes I already made all of that.

I wrote the ip of my computer (it's the one which running the iis server), and the name of the zip file.

 

It's not clear on the video because of the colors, but the TV seems to download the file correctly (the progress bar fills with blue completely).

 

Any other idea ?

 

 

Just try entering this address (with correct IP) in a web browser on your PC and confirm that it does download the app as expected:

http://192.168.x.x/Widget/Emby_1.0.6_Europe_20160120.zip

Aside from that, I don't really know why it isn't installing correctly using this method.

 

The other thing you can try is doing the 'Config Server IP' again.  I've seen issues in the past where it is populated but you need to re-enter it every time for it to actually load correctly.  Sometimes even a full power cycle of the TV is required -> Enter Server IP. -> Sync User Applications

[SamES 890]

I also downloaded the Emby App 1.0.7 (from GitHub) onto a USB stick and ran that. It exhibits the same problem.

 

 

Do you mean 2.0.7?

[SamES 890]

Okay, I have 1.06 on my web server and can load that and test.  Will try 2.2.4 also if there's issues.

 

 

In the app settings is DTS playback turned off?  I would assume that's why it's requesting a transcode.  My TV supports DTS, but I can turn that off to force transcode

 

Let me know if 1.0.6 works with transcoding.  Maybe it is possible that this is now broken?

[SamES 890]

I had originally followed the instruction here to install the Emby App (v1.0.6) on on my old D-Series Sammy 46D650.

I then followed these side loading steps and Emby (v1.0.7) loads fine from the USB.

 

However, I cannot get either version to play anything.

The same content plays fine from another TV (LG OLED55B8) running Emby App.

 

The Emby App reports "Unable to Play", "None of the MediaSources are playable".

See screenshot:

IMG_0343.jpg

 

If I click on the Apps log screen, I see the following:

IMG_0344.jpg

 

Line 690 seems to be indicating why there's no playback and seems to say that Default User is set to Off BUT in the settings, I have definitely set it to TRUE.

 

I know it's an old TV and unsupported app but anyone seen this behaviour and any solutions ?

 

 

As a test, for each user config on the server, can you make sure each of these options is On (and don't forget to press the save button at the bottom of each screen) then try playback again

 

[FrostByte 5042]

Okay, I just loaded 1.06 and playing a DTS file I can make it transcode and I get Playback added in the app log and the server is direct streaming the movie after converting

 

In the app under TV SETTINGS

 

"Enable Transcoding on D series"  make sure that is True.  It's off by default because chessdragon thought it experimental

 

While your there make sure you have the Dolby and DTS settings correct for your TV also.

 

Let us know what you find

[macnb 26]

Do you mean 2.0.7?

 

No. It's 1.0.7 as my TV is a D-Series and there does not seem to any higher versions for my TV.

[macnb 26]

As a test, for each user config on the server, can you make sure each of these options is On (and don't forget to press the save button at the bottom of each screen) then try playback again

 

 

Yes all these settings are enabled. Thx.

[macnb 26]

Okay, I just loaded 1.06 and playing a DTS file I can make it transcode and I get Playback added in the app log and the server is direct streaming the movie after converting

 

In the app under TV SETTINGS

 

"Enable Transcoding on D series"  make sure that is True.  It's off by default because chessdragon thought it experimental

 

While your there make sure you have the Dolby and DTS settings correct for your TV also.

 

Let us know what you find

 

Thx for quick replies.

I enabled what you suggested and the following :

 

 

Now, movies with Dolby Digital plays fine.

 

But movies with DTS seems to crash the Emby App. I got a pop-up on the TV with "Render Error Type: 3" (sometimes it says type 1) and seems to hang. It appears to be transcoding on the TV but nothing is playing. Emby Server says that the playback finished. Only way out is to press the Power button on the remote and restart the TV. See App log:

 

 

If I set "Enable Transcoding on D Series" to FALSE, movies with Dolby Digital plays fine. The problem is DTS.

 

If the Samsung's Videos DLNA App can play the movies (DTS or DD) without transcoding (I assume), why does the Emby App need to transcode DTS on the TV ?

Edited March 5, 2019 by macnb

[FrostByte 5042]

It shouldn't have to and I'm seeing the same thing where DTS is being converted to ACS even though I said my TV supports DTS.  I don't believe this was an issue back when I used the app before so I'm not sure why it's converting DTS now.  

 

Let me try 2.2.4 which was the latest I was running before switching to the official app to see what that does

[FrostByte 5042]

Okay, I just loaded v2.2.4 and it is no longer requesting that DTS be transcoded and movies with DTS are Direct Playing.  

 

Version 1.06 never did that before the app was forked, but development on it ended long before v2.X ended so it's possible something changed server side which is reflected in the newer version or 1.0x got broke at some point after I stopped using it.

 

 

 

So, I think we figured out why the app wasn't transcoding before, but the problem now is why is the app even trying to transcode DTS when it shouldn't

Edited March 5, 2019 by FrostByte

[macnb 26]

Okay, I just loaded v2.2.4 and it is no longer requesting that DTS be transcoded and movies with DTS are Direct Playing.  

 

Version 1.06 never did that before the app was forked, but development on it ended long before v2.X ended so it's possible something changed server side which is reflected in the newer version or 1.0x got broke at some point after I stopped using it.

 

 

 

So, I think we figured out why the app wasn't transcoding before, but the problem now is why is the app even trying to transcode DTS when it shouldn't

 

 

Thx for your efforts and investigations.

 

Also, in the App log, I noticed this:

 

It shows the result of "Audio File Analysis results". Starting Line 3055, log says "Codec compatibility : false : dts". Same for "Container mkv" and the "Channel compatibility". It's like it think DTS is incompatible. Maybe someone with source knowledge can tell why it states this ?

 

It's a shame v2.x cannot work with the older Samsung TV's.

 

@@Luke , so if the Emby App v1.0.6 never used to transcode DTS, what could have now changed on the Emby Server side to cause the App to now transcode DTS ?

Is there any tweaks/settings on the server to try and test ?

Edited March 5, 2019 by macnb

[SamES 890]

FYI:

Render Error 1 :  Unsupported container
Render Error 2 :  Unsupported video codec
Render Error 3 :  Unsupported audio codec
Render Error 4 :  Unsupported video resolution
Render Error 6 :  Corrupt Stream

[SamES 890]

So looking at the code, for 1.0.6

 

• Audio support only only included dca, not dts
• I'm a bit suspicious that the video bitrate might also be a bit low for this video format (but let's look at one thing at a time)

 

Assuming you're still running from USB, find and replace this file (remove the .txt extension) and reload.  It should be located in app/javascript/Gui/GuiPlayer

 

GuiPlayer_TranscodeParams.js.txt

[macnb 26]

So looking at the code, for 1.0.6

 

• Audio support only only included dca, not dts
• I'm a bit suspicious that the video bitrate might also be a bit low for this video format (but let's look at one thing at a time)

 

Assuming you're still running from USB, find and replace this file (remove the .txt extension) and reload.  It should be located in app/javascript/Gui/GuiPlayer

 

GuiPlayer_TranscodeParams.js.txt

 

That's a really quick fix. That worked.

 

See log to confirm:

 

I tried several movies with DTS (5.1) and DD (5.1) and they all worked with DirectPlay.

Really cool.

 

With DTS-MA (7.1 8-channel) movies, render type 1 error and the log shows that "Channel Compatibility : false : 8".

In the settings, I had "Enable Transcoding on D Series" set to true. Setting it to false produces the same error.

[SamES 890]

Find this section in the file I sent you (there are lots of repeating sections, you need the one on about line 671), and change the audiochannels value to 8

		case "dca":
		case "dts":
			this.audiocodec = true;
			this.audiocontainer = ["avi","mkv"];
			this.audiochannels = 6;
			break;

Let me know if you have trouble with this

[macnb 26]

Find this section in the file I sent you (there are lots of repeating sections, you need the one on about line 671), and change the audiochannels value to 8

		case "dca":
		case "dts":
			this.audiocodec = true;
			this.audiocontainer = ["avi","mkv"];
			this.audiochannels = 6;
			break;

Let me know if you have trouble with this

 

 

Made the change.

That fixed the DTS-MA 7.1 playback.

 

Many thanks.

 

Another issue is AAC audio which refuses to play.

So I enabled Transcode on the TV settings and get a "Loading" message and immediately fails with "Undefined" render err type 1. Here's a screen shot:

 

 

Any clue as to the issue ?

[FrostByte 5042]

Do you see a ffmpeg log on the server?  Can you post?  The app SHOULD have converted AAC to AC3 if you had that option set in the app.

Edited March 5, 2019 by FrostByte

[SamES 890]

Also be aware that for D-Series, if you play any audio track other than the first audio track it will stream the file to perform the audio track switching as I don't think audio switching is supported by the model

[macnb 26]

Do you see a ffmpeg log on the server?  Can you post?  The app SHOULD have converted AAC to AC3 if you had that option set in the app.

 

 

It's working now. Not sure if I had forgot to turn on AAC-to-DD option. It's now on and it's working. Many thx.

[macnb 26]

Also be aware that for D-Series, if you play any audio track other than the first audio track it will stream the file to perform the audio track switching as I don't think audio switching is supported by the model

 

V1.0.7 does not have any GUI option to select the audio track. 

So if there were two audio tracks in a file, which one does the App select (first one or the one flagged as Default) ?

 

(Trying to figure out how to avoid streaming and get Direct Play to work as much as possible).

[FrostByte 5042]

@@SamES would it be possible for you to add your changes and make a v1.08 and upload to GitHub?

[macnb 26]

@@SamES would it be possible for you to add your changes and make a v1.08 and upload to GitHub?

 

 

Better still, is it possible to put into the Samsung developer account (like v1.0.6 was) so that it can be installed directly onto the TV. That would save a USB port.

[SamES 890]

Where did 1.0.7 come from? I can’t find any reference to that anywhere

[macnb 26]

Where did 1.0.7 come from? I can’t find any reference to that anywhere

 

 

I got the reference from @@FrostByte from Post #11 here.

It's a link to Github which refers to v1.0.6 but when you download the sources from there and load it onto the USB stick, the Splash screen states v1.0.7.

If you check the source Main.js, it says v1.0.7:

var Main =
{
		version : "v1.0.7",
		requiredServerVersion : "3.0.5211",
		requiredDevServerVersion : "3.0.5507.2131",
		
		//TV Series Version
		modelYear : null,
		
		forceDeleteSettings : true,
		
		enableMusic : true,
		enableLiveTV : false,
		enableCollections : true,
		enableChannels : false,
		
		enableScreensaver : true,
		isScreensaverRunning : false,
};

So whoever changed the sources, has not updated the Github Readme and NOT produced a release zip for the Releases page.

The Releases pages has NO reference/download link to v1.0.7.

If you click/download 1.0.6 release zip file, the Main.js states v1.0.6. That is, the release page definitely has v1.0.6 but the sources is v1.0.7.

I hope that makes sense