Jump to content

Play movie fails with transcoding+subtitles+non-admin permission


Recommended Posts

bolderbast
Posted

Hi all,

 

Versions:

  • Emby Server 4.4.0.40 running on up-to-date Arch Linux
  • Kodi 18.6
  • Emby for Kodi addon 4.1.19

Issue:

  • Playback without transcoding works with & without subtitles
  • Playback using transcoding works without subtitles
  • Playback using transcoding fails with subtitles
  • Playback using transcoding works with subtitles, if the user has "Allow this user to manage the server" permission in Emby Server

Kodi log is attached.

 

Does anyone else have this issue?

Would this be an Addon issue or a Server issue?

Playback using transcoding with subtitles from the Emby web interface does work (without "Allow this user to manage the server" permission), so my guess would be that this is a Addon issue?

 

Any suggestions?

Posted

Hi there, did you forget to attach the log?

Posted

Thanks. Can you please attach the emby server log as well? Thanks.

bolderbast
Posted (edited)

Sure, just reproduced the issue and grabbed the server log. It's attached.

 

Would be great if we can find the cause, I'd hate to let simple users have Admin privileges... :-)

embyserver.txt

Edited by bolderbast
bolderbast
Posted

Were you able to find any clue in the logs?

Posted

Looks like the add-on needs an update.

  • 2 weeks later...
bolderbast
Posted

Hi guys, any progress on this? I'd love to revoke admin privileges from my regular users!

  • Like 1
  • 2 weeks later...
correctomundo
Posted

I'm seeing the same problem, wondered what it was and saw this thread.

 

Any update on the fix?

  • 2 weeks later...
correctomundo
Posted

I'm seeing the same problem, wondered what it was and saw this thread.

 

Any update on the fix?

 

I found out that the latest version (4.1.19) doesn't contain the fix (it's from December '19). If you pull the latest code from github and install manually, the issue is indeed fixed.

Just have to wait for a new release I guess...

Posted

 

I found out that the latest version (4.1.19) doesn't contain the fix (it's from December '19). If you pull the latest code from github and install manually, the issue is indeed fixed.

Just have to wait for a new release I guess...

We'll work on getting a new release out. Thanks for the feedback !

  • Like 1

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...