Since .238 everything transcodes

[LASooner 24]

I noticed the Buffering started showing up

 

 

And I could no longer start movies anywhere but the beginning and could not skip ahead

 

 

when I checked the server logs I noticed the transcode logs of the same time/date and sure enough those are the movies I was trying

 

I'm running .223 on my living room media center and it is not suffering from this problem, since I can't roll back to a previous version I'm taking a little heat from the wife on this one. She can't skip ahead or start a movie from the chapters.

 

help.

MBClassic-2122014fb146053cd844636a1bad6df3125f479.log

server-63553075201.txt

transcode-5c50998d-bf8e-4a94-abd5-7df84dcdb34f.txt

transcode-d3df2218-cb2d-4059-8061-9e709f28e354.txt

transcode-ecd9350b-4a7e-4251-9fb3-b470dc730010.txt

[ebr 16176]

The new version shouldn't affect this so that is probably coincidental.  The issue is one of access.  If it is streaming, it means that machine/user cannot directly access the file location as it is defined on the server.

[AgileHumor 123]

delete me, pii cleanup

Edited April 17, 2015 by AgileHumor

[ebr 16176]

The file format should be irrelevant.

[LASooner 24]

I have access to the server from the computer, as I said, I immediately noticed this after the new client installed.

 

If I play these same movies through Mediacenter's Library, they function fine.

Edited December 2, 2014 by LASooner

[bigjohn 753]

I had the exact same issue, but it only affected one user on the PC. Logged in as a different Windows user and everything was fine.

 

So I uninstalled MBC, renamed the c:\users\myusername\AppData\Roaming\MediaBrowser-Classic folder to MediaBrowser-Classic-old and C:\ProgramData\MediaBrowser-Classic to MediaBrowser-Classic-old, installed MBC again and the problem was gone.

 

I kept the old config directories, so I could probably do a comparison and see what is different when I have time.

[LASooner 24]

When I get home from work I'll look into the network and I'll try John's suggestion.

[ebr 16176]

All the installing and uninstalling at the MB level really shouldn't make any difference.  The only way we should be streaming items is if they are from channels or if we could not directly access the file at the time it was attempted to be played because of either permissions or maybe a network connection dropping.  Sometimes Windows gets its user stuff messed up and you need to re-create the windows account.  But that should be pretty rare.

[LASooner 24]

It seems a service related to peer to peer naming had stopped, and even though I could navigate to those folders that was somehow affecting the connection when trying to play through MB, once I restarted it, it's working again. Man windows can be a pain in the ass.

[bigjohn 753]

All the installing and uninstalling at the MB level really shouldn't make any difference.  The only way we should be streaming items is if they are from channels or if we could not directly access the file at the time it was attempted to be played because of either permissions or maybe a network connection dropping.  Sometimes Windows gets its user stuff messed up and you need to re-create the windows account.  But that should be pretty rare.

 

 

Yeah, you are probably right that it had nothing to do with starting fresh. There was also some logging off and rebooting involved, so no telling exactly what fixed my problem.

[jayTcold 8]

The new version shouldn't affect this so that is probably coincidental.  The issue is one of access.  If it is streaming, it means that machine/user cannot directly access the file location as it is defined on the server.

 

I had some funky transcoding issues and they where resolved by using UNC paths within my Library's Media Location's fields.