Linux What is "Discontinuity2" in DEBUG?
#1
I am currently investigating a playback issue on my set which only occured after I lost my settings due to disk full when xbmc tried to write to advancedsettings.xml.

I then re-configured xbmc from memory and some old pre-12 backups and think I pieced it together, I do have an issue tho: every once in a while, most visible when the camera pans sideways there is a small stutter. Sometimes don't see it for minutes, sometimes about every minute.
I noticed about every 51 seconds (*not* 41 - I set xbmc to speed up 23.976 to 24) there is a message in the debug log about an error "Discontinuity2".

Is that possibly related?

Other than that: en/disabling vaapi does not matter (sandy bridge), disabling the pvr addon does not help, when enabled in live TV I see it, too, especially on SD material, not quite as bad on 720p to my surprise.

Machine is a core i5 4x2.3GHz most idling, even with vaapi disabled it is at about 15% load. Disabled all other services apart from TVHeadend.

OS is Debian 7 - I had to move from the deb kernel 3.2.41 to 3.8.5 as for reasons beyond me after the upgrade from 3.2.39 to 3.2.41 I could not compile the liplianin dvb drivers I need for my TT-4600 S2 against it anymore while on the 3.8 it works.
I mostly configured the 3.8 from scratch, no idea if I missed something there.

Any ever so far fetched pointer appreciated.
Reply
#2
Post a screenshot of your video playback settings.
Reply
#3
Also - post the offending logs...
Need help? Check out my XBMC Frodo Guide. It contains full featured guides to Sickbeard and CouchPotato as well.

Image
Reply
#4
Image

From top this is in english:
Video settings
play next video automatically[]
render methid GLSL
hardware accel vdpau []
hardware accel vaapi [X]
change refresh to match video [always]
pause on refresh change [off]
sync playback to display [X]
a/v sync method [audio clock]
allow AR error [none]
display 4:3 as [normal]
VDPAU studio level color correction []
videotext [X]
scale teletext to 4:3 [X]


Currently I am back on 3.2.41 (log says 3.2.0 due to weird debian kernel version umbering scheme), managed to chew my way through compiling the DVB modules and here it does not happen anymore:

http://www.vaultofsages.de/~dexterf/xbmc.nodiscont2.log

Xbmc overwrote previous logs, so at present I do not have logs from the 3.8.5 runtime and right now.

But - I did not change anything in xbmc, so it's quite clear it's something in the kernel. Maybe a scheduler thing.
Reply
#5
"sync playback to display" with audio clock as master makes no sense if fps does not match refresh rate exactly (IMO it does not make sense in general) You neither have a mode for 24.0 not 23.976.
Set video clock as master and audio to drop/dupe or resample in case you don't use pass through for audio.
Reply
#6
Analog audio, and I do have a 24fps mode.

I tried video clock, that would result in the audio taking very notable dives.
Reply
#7
Agreed if you consider this as 24
ID:0xc2 Name:HD_2400 Refresh:23.999781 Width:1920 Height:1080

EDIT: audio won't get resampled if you set audio clock as master.
Reply
#8
Well, tell me how to create a mode that's 24.000000 on the spot and I'll do.
Reply
#9
I was not bitching at the minimal inaccuracy at the 4th fractional digit, just overlooked it in the log Smile
On Nvidia and AMD systems this is in general 24.0
Reply
#10
Did not imply bitching.
It's just that the intel sandy bridge contrary to nvidia did not list all modes the LG TV is capable of, so I had to calc modeline myself.
Well, that's as close as I got.
Right now everything is working a charm, so I prefer not changing it (at least until I created a real good backup of the system partition...)
Reply
#11
Code:
Section "Device"
  Identifier  "Device0"
  Driver      "intel"
  VendorName  "INTEL Corporation"
  Option "AccelMethod" "sna"
EndSection

Section "Screen"
  Identifier  "Screen0"
  Device      "Device0"
  Monitor     "HDMI1"
  DefaultDepth  24
  SubSection "Display"
    Depth       24
    Modes     "1920x1080@50p" "[email protected]" "[email protected]" "1920x1080@24p" "1920x1080@60p"
  EndSubSection
EndSection

Section "Monitor"
  Identifier  "HDMI1"
  HorizSync   14.0 - 70.0
  VertRefresh 24.0 - 62.0
  Option      "DPMS" "true"
  ModeLine "[email protected]" 74.057 1920 2558 2602 2719 1080 1084 1089 1136 +hsync +vsync #INTEL
  ModeLine "1920x1080@24p" 74.400 1920 2558 2602 2758 1080 1084 1089 1124 +hsync +vsync #INTEL
  Modeline    "1920x1080@50p"    148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
  Modeline    "[email protected]" 148.352 1920 1960 2016 2200 1080 1082 1088 1125 +hsync +vsync
  Modeline    "1920x1080@60p"    148.500 1920 2008 2056 2200 1080 1084 1089 1125 +hsync +vsync
EndSection

Section "Extensions"
  # fixes tearing
  Option      "Composite"           "Disable"
EndSection

Those I use on my Celeron 847. Change all appearances of HDMI1 to whatever your output is.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#12
Your 24p modeline results in a refresh of 24.000056, but a first quick try did not produce the Discontinuity2 error and I saw no jitter (by the way, it was there on the 3.2.41 kernel as well, did not see it first.)
Will do some more testing.

Wonder why the machine does not detect the LG's 24p mode, it lists the others fine.
Reply
#13
24.000056 <- hehe. Check the other one, the 23.976 - do you also have it now?
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#14
Nah, didn't tinker with that as I take the +.1% speedup rather and have 24fps display that.
After all, there is no such thing as a 23.976 refresh physically, anyway.
Reply
#15
(2013-05-12, 19:22)fritsch Wrote:
Code:
Section "Device"
  Identifier  "Device0"
  Driver      "intel"
  VendorName  "INTEL Corporation"
  Option "AccelMethod" "sna"
EndSection

Section "Screen"
  Identifier  "Screen0"
  Device      "Device0"
  Monitor     "HDMI1"
  DefaultDepth  24
  SubSection "Display"
    Depth       24
    Modes     "1920x1080@50p" "[email protected]" "[email protected]" "1920x1080@24p" "1920x1080@60p"
  EndSubSection
EndSection

Section "Monitor"
  Identifier  "HDMI1"
  HorizSync   14.0 - 70.0
  VertRefresh 24.0 - 62.0
  Option      "DPMS" "true"
  ModeLine "[email protected]" 74.057 1920 2558 2602 2719 1080 1084 1089 1136 +hsync +vsync #INTEL
  ModeLine "1920x1080@24p" 74.400 1920 2558 2602 2758 1080 1084 1089 1124 +hsync +vsync #INTEL
  Modeline    "1920x1080@50p"    148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
  Modeline    "[email protected]" 148.352 1920 1960 2016 2200 1080 1082 1088 1125 +hsync +vsync
  Modeline    "1920x1080@60p"    148.500 1920 2008 2056 2200 1080 1084 1089 1125 +hsync +vsync
EndSection

Section "Extensions"
  # fixes tearing
  Option      "Composite"           "Disable"
EndSection

Those I use on my Celeron 847. Change all appearances of HDMI1 to whatever your output is.
I'm not trying to pick a fight, but why do you even have entries for fractional framerates when using an Intel IGP? It's not capable or reproducing them, unless something has changed in the past 8 months since I moved off the IGP onto an nVidia GT430 because of judder on 23.976fps material.
Reply

Logout Mark Read Team Forum Stats Members Help
What is "Discontinuity2" in DEBUG?0