Issues after Updating to IOS 6- Seek bar problem!

Dev Community Apps & Creations
1

  • ATV3 latest software IOS 6

  • DNS server is set manual for 10.0.1.6 

  • My Plex Server Version 0.9.8.4[/size] is running from Macbook Pro with ML and IP is 10.0.1.6

  • The PlexConnect is updated today morning using Github.

Issue has been since updating to iOS 6 and this is to just report some issues I personally had since then.
First issue is for some videos that are resumed from prev time , they start off with Seek bar already full and not showing how much time has elapsed or remaining, No way to seek the video forward or back, not able to pause the video. 
Second issue is that when a Tv episode reaches the end it gives error "An Error occurred loading this content"
 

13:55:55 DNSServer: ***intercept request

13:55:55 DNSServer: -> DNS response: 10.0.1.6
13:55:55 Localize: aTVLanguage: en
13:55:55 ATVLogger: Player state: Playing at this time: 982.890510155
14:26:04 DNSServer: DNS request received!
14:26:04 DNSServer: Source: ('10.0.1.4', 55192)
14:26:04 DNSServer: Domain: atv.plexconnect
14:26:04 DNSServer: ***intercept request
14:26:04 DNSServer: -> DNS response: 10.0.1.6
14:26:05 Localize: aTVLanguage: en
14:26:05 ATVLogger: Player state: Stopped at this time: 0
14:27:57 DNSServer: DNS request received!
14:27:57 DNSServer: Source: ('10.0.1.4', 65151)
14:27:57 DNSServer: Domain: bookkeeper.itunes.apple.com.akadns.net
14:27:57 DNSServer: ***forward request
14:27:57 DNSServer: -> DNS response from higher level
14:27:57 DNSServer: DNS request received!
14:27:57 DNSServer: Source: ('10.0.1.4', 53401)
14:27:57 DNSServer: Domain: EVSecure-ocsp.verisign.com
14:27:57 DNSServer: ***forward request
14:27:57 DNSServer: -> DNS response from higher level
14:27:57 DNSServer: DNS request received!
14:27:57 DNSServer: Source: ('10.0.1.4', 59479)
14:27:57 DNSServer: Domain: EVIntl-ocsp.verisign.com
14:27:57 DNSServer: ***forward request
14:27:57 DNSServer: -> DNS response from higher level
14:27:58 DNSServer: DNS request received!
14:27:58 DNSServer: Source: ('10.0.1.4', 55022)
14:27:58 DNSServer: Domain: upp.itunes.apple.com.akadns.net
14:27:58 DNSServer: ***forward request
14:27:58 DNSServer: -> DNS response from higher level
2

>> Seek bar already full

Full (blue)? Empty (dark grey)? Unkown (white)?

Is your experience the same as shown here... http://forums.plexapp.com/index.php/topic/81253-progress-seek-bar-issue-after-ios6-update/?

>> a Tv episode reaches the end...

please set loglevel=High, restart PlexConnect, repeat the issue and *attach* the PlexConnect.log file. No copy/pasting into the message. Use pastebin or something else if it doesn't fit... (but then again, try to keep it small by restarting PlexConnect right before the interesting communication)

3

yeah its white and experience is almost same as in the other thread. and now after 2-3 episodes i did not have that error anymore , i mean i had it form several episodes but not for last 1 episode.

4

where is the log file and where to change loglevel=high

5

2) Settings.py  -> cfg

1) in the PlexConnect directory

6

Okay it log file i found was being used and created in old plexconnect folder not the one i am using now 

Edit- found the right one. even recreated the error. 

7

okay this is after several attempts to recreate error at end of file 

file played at 14:28 and i seeked it forward and played again at very end, as soon as file was almost over it gave me error

http://pastebin.com/iJMX9rfN

8

This log is not "loglevel=High" (with capital H).

Also, some interesting stuff is missing - might have still been in your file output buffer... I guess it might help to CTRL-C PlexConnect before uploading the log.

Any chance of recreating it another time?

9

Now this is a new one. Here I could recreate the issue of seek bar being full with white and not able to seek or pause. but this time no issues at end of file. same file in both pastes. 

http://pastebin.com/b9bp7Q4u

10

This log is not "loglevel=High" (with capital H).

Also, some interesting stuff is missing - might have still been in your file output buffer... I guess it might help to CTRL-C PlexConnect before uploading the log.

Any chance of recreating it another time?

Let me try all over again. 

11

on settings.py it shows 

 'loglevel'        :('Normal', 'High'), \
    'logpath'         :('.',), \
    }
 
so should i change that to
 'loglevel'        :('High'), \
    'logpath'         :('.',), \
    }
12

Uh. Sorry. My fault. Don't edit Settings.py - you should see a Settings.cfg file.

Did I really write ".py"? Plain stupid... never ever again even only think about editing Settings.py.

13

Did recreate error at end again. Initially could not when subs were on for the episode. but turned subs off and was able to create , video end at 16:49:50 I think.  But could not recreate seek bar issue this time. 

http://pastebin.com/4p7AhtUy

14

Uh. Sorry. My fault. Don't edit Settings.py - you should see a Settings.cfg file.

Did I really write ".py"? Plain stupid... never ever again even only think about it.

Oh okay. So should I do this once again? 

or what logs i have pasted are enough?

15

Okay I recreated both issues with Settings.cfg having Log=High but now Pastebin won`t let me paste as it exceeds size allowed of 500kbs.

16

Thought so...

- create logs for each issue alone, don't try to cramp everything in, we won't be able to find it anyways :-)

- restart PlexConnect just before pressing PLAY on the media, as this will overwrite the existing log.

- stop PlexConnect right after the error occurred.

This should give you smaller files... does it?

17

Thought so...

- create logs for each issue alone, don't try to cramp everything in, we won't be able to find it anyways :-)

- restart PlexConnect just before pressing PLAY on the media, as this will overwrite the existing log.

- stop PlexConnect right after the error occurred.

This should give you smaller files... does it?

let me try , i have no problem in trying but the issue some times pop ups first time some time not. so will also keep in mind timestamp so i can copy log from there.

18

or i can paste log in two different instances what you say? because i have it complete on my notepad. 

19

This one if for error at end 

http://pastebin.com/gqmxMw0b

20

Also uploaded a log to Dropbox which include both issues I recreated earlier , its a 2.5mb text file.

https://www.dropbox.com/s/s5b83pgm08wt488/Both%20issue.rtf