Jump to content

Sync: Transferred Files Are Unplayable


Anon28109
 Share

Go to solution Solved by Luke,

Recommended Posts

In cases where the source file meets the sync profile requirements and Emby transfers rather than converts, the transferred file is not playable in Emby, VLC or other 3rd party apps.

 

This only applies to transferred files, converted files work properly.

 

The transferred file size matches the source file size (according to Finder) so I don't think it's a case of the transfer being interrupted.

 

The log file only shows one line indicating the file is being transferred:

Info App: Profile: Cloud Sync, Path: /Volumes/Download/Movies/My Movie/My Movie.mp4, isEligibleForDirectPlay: True, isEligibleForDirectStream: True

 

This is a problem with if not every transferred file then almost every transferred file.

 

I work around it by manually copying the source file to the sync destination.

 

I'm running 3.5.0.0 on OS X. The problem began with the previous release.

Link to comment
Share on other sites

  • Solution

That's very odd. I can't reproduce this (yes on a mac). We're just using a system command to transfer the file. Is there any chance it is permissions related?

  • Like 1
Link to comment
Share on other sites

  • 2 months later...

Follow up: Emby's not the problem. Manually copying the files on my NAS drive on mac OS (where I run Emby) produces the same corrupted files. Strange.

Edited by Anon28109
Link to comment
Share on other sites

Results after (tedious lol) testing:

On Mac OS:

  • Moving file from Mac OS to NAS: works
  • ​Copying file from Mac OS to NAS: works
  • Moving file from NAS to Mac OS: works
  • Copying file from NAS to Mac OS: works
  • Moving file from NAS <location 1> to NAS <location 2>: works
  • Copying file from NAS <location 1> to NAS <location 2>: fails

So "convert" (which only uses "working" actions) is fine. "Transfer" which uses the "failed" action, doesn't.

 

I don't know if the bug's in Mac OS, my NAS's afp implementation, or a combination of the two. I also can't say how long it's been a problem - earlier versions of Emby were more strict with sync bitrate so transfers were rare and it's possible I didn't notice.

 

For completeness I also ran tests on my NAS.

 

On (debian-based) NAS:

  • Moving file from NAS <location 1> to NAS <location 2>: works
  • Copying file from NAS <location 1> to NAS <location 2>: works

 

Edited by Anon28109
Link to comment
Share on other sites

  • 1 month later...

Resolved.

 

I traced the problem to AFP incompatibility between OS X 10.13 and netatalk. I switched to SMB and the problem disappeared.

 

Note to anyone using an SMB library with Emby on OS X: AppleDouble files will cause problems with Emby - use the 'veto files' option to suppress them.

 

Admins, can you please move this thread to the Mac forum?

Edited by Anon28109
Link to comment
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
 Share

×
×
  • Create New...