Server isn't using folder sync'd copy of movie

[Jorpd 0]

Hi,

 

I've set up a test movie to use with foldersync, using baseline profile @ 5Mb/s.

I can see the movie sat there under path/to/foldersync/myservername/Baseline-5000000/Videos/ but my tests from the android app, web app, and kindle fire tv show that it's still using the original file.

 

I went as far as to disable transcoding for my user, but the logs showed it still took that original file when direct streaming from the web app (albeit, with no audio).

 

Any advice on things that I may not have considered?

 

Thanks

[Luke 42077]

Hi there, we're sorry to hear about this. In order to best help you, let's go over an example. Please provide the information requested in how to report a media playback issue. Thanks !

[Jorpd 0]

I have a user who's using a Roku 3, just about every movie they play requires transcoding as I typically look for DTS audio where I can for my own set up.

I wanted to set up a test to see if it would be worth queuing up an entire sync job of hundreds of movies. I chose baseline 5mbps for the test, as I wanted to see it working from the Amazon fire TV we have here. I'd then have set up movies using the general profile for the Roku 3. 5mbps was a number I landed at trying to keep the filesize low while still looking passable.

As mentioned above, I can see the foldersync copy of the movie in question when i navigate that dir.

Attached is a transcode log of playing this movie from the Fire TV and a zipped (huge, apologies) server log that should also cover that time.

ffmpeg-transcode-26ae6f4e-d781-41fa-9ba0-3fe0297b59a3.txt

server-63614106751.zip

Edited November 7, 2016 by Jorpd

[Luke 42077]

Does the server show it as being synced?

[Jorpd 0]

Yes. I ran another sync job for a different movie last night, the job is showing as complete but when I play the movie I can see it's transcoding, and the transcode log shows it's coming from the default dir. So it doesn't seem to be limited to the one title. I'll attach logs again this evening if this would help.

[Luke 42077]

Ok after further review, I think the issue is your in-app bitrate setting is still lower than the bitrate of the synced file, and that's why it ends up transcoding. I am adding additional logging information so that we can verify but that looks to be the issue. I've tested this myself and saw the expected result of the synced content being utilized.

 

Now the scenario of disabling transcoding is an interesting one, that's something we can look at in order to continue to improve this. Once you apply that setting we kind of assume that everything is supported by the client app. However in this case when there are multiple choices available, we may still want to add some decision making in order to pick the most desirable one. We will review this for a future update. 

 

Thanks !