33 replies to this topic

[Doofus]

Ah, now the mpv log makes sense. It's playing via a network IP rather than a directory. A stream not a file.

http://IPAddress:809...ea28a9ff24a0aa4
[ 0.047][d][ffmpeg] tcp: Starting connection attempt to IPAddress port 8096
[ 0.061][d][ffmpeg] tcp: Successfully connected to IPAddress port 8096

How do you have your library location set up in Emby? Where are the files located, and how are you sharing them?

[schogobong]

That's how the libraries are set up:

 

Edited by schogobong, 04 January 2020 - 11:25 AM.

[Doofus]

The shared network folder path should be what you see in Windows explorer. Navigate to the folder in Windows explorer and copy what's in the address bar.

[schogobong]

Ha - like magic! So that makes the experience a whole lot better Can't believe I was using the wrong settings all this time... thanks

 

But when connecting remotely, the issue is still there (long loading with Emby Theater from the Emby site; no playback (or at least not withing around 40 seconds) whith Emby Theater from the Windows Store). At the same time, I am not having any issues at all when using the Android app.

 

Any idea what that is about?

[Doofus]

When remote, that is likely due to transcoding. Is there a transcode log? Having a NAS transcode is hard work. They aren't designed for that kind of load.

[schogobong]

For some reason playback with Emby Theater from the Emby website (let's call this by its version 3.0.10) doesn't create a transcode log - playback actually seems to have improved even when being remotely connected.

 

On the version from the Microsoft store (version 1.1...) I'm still not getting a playback of that file, so I'm also not getting a transcode log. But I just found one from earlier today (playing back a different file). Maybe this helps?

 

Is there no way to access the file directly and transcoding on the machine when accessing remotely? Why can a playback with no issues on the Android App but not on the Microsoft Store App?

Attached Files

•  ffmpeg-directstream-b02ed630-02de-4256-aacf-3800296e6681_1.txt   41.32KB   1 downloads

[Doofus]

The store app and Android mobile app have different players. The Android mobile app has the same player as 3.0.10. But the store app is using the Windows standard player, which is basically, crap.

[Doofus]

And it appears as though you are using subs. Try turning subs off.

[schogobong]

And it appears as though you are using subs. Try turning subs off.

 

Wow ^^ That actually did the trick when playing the file locally! I mean, it's not ideal that it doesn't work with subs but at least now it plays properly CPU usage has also gone down considerably.

 

Remotely there is considerable lag - but maybe that has something to do with player. It's kind of a pity, that the Microsoft Store app (which I think is better from a UI-perspective and probably is more in line with what Microsoft is doing) doesn't work properly.

 

But as long as I've got one working app I'm happy

[Doofus]

For subs, it's best to use external srt files.

[Doofus]

And you can change the UI layout in 3.0.10. Have you look at the settings?

[schogobong]

For subs, it's best to use external srt files.

 

Will do that, thanks for the tip!

 

And you can change the UI layout in 3.0.10. Have you look at the settings?

I have, but for example: I'm not able to re-size the window. Well not really "for example" - that's the main issue I've come across so far.

[Doofus]

You mean resize when playing? Yeah, Luke has that locked down because of electron. The whole UI is in the process of being rebuilt. So when that's finished, we may have more fancy shmancy stuff

[schogobong]

Yeah exactly - looking forward to that

 

Thanks for your support!

Edited by schogobong, 04 January 2020 - 05:16 PM.