Resolution dropping after time

[summershere]

Connected to a 1080p display (Acer), this pi is running OMX Player. After a while of working perfectly it drops down to standard definition.

Any ideas why? Is it anything to do with the overscan? The mp4 files are all 1080p I believe. config.txt:

[code]
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=1
hdmi_mode=31

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# for more options see http://elinux.org/RPi_config.txt
[/code]

[summershere]

Anyone got any ideas here?

[FTrevorGowen]

Connected to a 1080p display (Acer), this pi is running OMX Player. After a while of working perfectly it drops down to standard definition.
Any ideas why? Is it anything to do with the overscan? The mp4 files are all 1080p I believe. config.txt:

Code: Select all

...
# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=1
hdmi_mode=31
...

What do you see if you re-comment the forced HDMI group & mode above and run the tvservice command as shown here:
http://www.cpmspectrepi.webspace.virgin ... tings.html ?
(I'm wondering if you've not chosen the best 1080p mode for the monitor/TV)
Trev.

[summershere]

Ok, have done this... just rebooted so will check it throughout the day. This is what I get from a tvservice -m CEA :

Code: Select all

Group CEA has 11 modes:
           mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
           mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive 
           mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive 
           mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 
           mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced 
  (prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 
           mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive 
           mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive 
           mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive 
           mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced 
  (native) mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive 

...so the mode I forced it onto is the one it believe is native... so that's right I guess?

[summershere]

Hmmm, it has selected 60hz though for some reason, should be 50hz here...

Code: Select all

state 0x12001a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60Hz, progressive

[summershere]

What do you see if you re-comment the forced HDMI group & mode above and run the tvservice command as shown here:
http://www.cpmspectrepi.webspace.virgin ... tings.html ?
(I'm wondering if you've not chosen the best 1080p mode for the monitor/TV)
Trev.

Uncommenting the mode did the trick... strange that forcing the resolution does quite the opposite!?

Thanks for your help

[summershere]

Back to this thread unfortunately - thought it was fixed but it isn't

Once again getting:

Code: Select all

root@pi:~# tvservice -s
state 0x12001a [HDMI CEA (1) RGB full 4:3], 640x480 @ 60Hz, progressive

...and yet it's correctly reporting native resolutions:

Code: Select all

root@pi:~# tvservice -m CEA
Group CEA has 11 modes:
  (prefer) mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
           mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive 
           mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive 
           mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 
           mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced 
  (native) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 
           mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive 
           mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive 
           mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive 
           mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced 
  (native) mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive 

So, changing whether the mode is forced to the native or not doesn't help... anything else I can try?

[FTrevorGowen]

Does tvservice -m DMT report any usable DMT modes? If your "Acer box" is a monitor (cf. a T.V.) one of those should be better/more stable (and maybe even "preferred" rather than "native").
Trev.

[summershere]

It's a monitor with speakers, which is kind of a TV I suppose??

Output of that below... none are preferred or native though..?

Code: Select all

root@pi:~# tvservice -m DMT
Group DMT has 12 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
           mode 8: 800x600 @ 56Hz 4:3, clock:36MHz progressive 
           mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive 
           mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive 
           mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive 
           mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive 
           mode 28: 1280x800 @ 60Hz 16:10, clock:83MHz progressive 
           mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive 
           mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive 
           mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive 
           mode 82: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 
           mode 85: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 

[summershere]

Have changed it to DMT now, and forced it to mode 82 - will see if that sticks... does that still support audio via HDMI if I force it?

[FTrevorGowen]

Have changed it to DMT now, and forced it to mode 82 - will see if that sticks... does that still support audio via HDMI if I force it?

You may need "hdmi_drive=2" IIRC - check http://elinux.org/RPi_config.txt for more info.
Trev.

[summershere]

Still no joy with this, it's driving me crazy! Forcing it into DMT mode just goes straight into 640x480 half the time when it boots up. So I've put it back to letting it pick its own resolution - starts off fine in 1920x1080 but after an hour or two drops back to 640x480 4:3...