atmosx
Posts: 24
Joined: Mon Aug 06, 2012 1:36 pm
Location: Greece

Samsung Screen Resolution Problems [newbe]

Thu Dec 20, 2012 11:08 am

Hello,

I have a Samsung 32" LE32R71W, trying to set-it-up with screenly.

According to the Pi the optimal screen resolution is 1280x720:

Code: Select all

[email protected]:~/screenly$ /opt/vc/bin/tvservice -s
state: HPD high|HDMI mode|HDCP off|composite off (0x12001a), 1280x720 @ 60Hz, progressive
This is my config.txt:
disable_overscan=1
sdtv_mode=2 #Normal PAL
sdtv_aspect=3 #Sets to 16:9
hdmi_drive=2 #Normal HDMI mode (Sound will be sent if supported and enabled)
hdmi_group=1 #Set to CEA
hdmi_mode=4 #Sets to CEA 1280x720p 60Hz - optimal for my TV


I have a coulpe of questions. Screenly runs on X11 and uses a resolution of 1920x1080 (screenly.conf) ... Does this affect in any way the 'hdmi_mode' setup that I should use?

Secondly, when I'm running videos using omxplayer the screen doesn't fit the video, which is the bigger problem, see here for example.

Is there any way to gather setup pictures/omxplayer and console in way to use full screen without using enabling overscan which leaves most of the screen out?

best regards

atmosx
Posts: 24
Joined: Mon Aug 06, 2012 1:36 pm
Location: Greece

Re: Samsung Screen Resolution Problems [newbe]

Thu Dec 20, 2012 12:00 pm

I have a sort of 'tip'. Videos no matter how I change the resolution using ffmpeg, always display the picture bigger then the screen.

The images though, if I use a resolution of 1200x680 they fit pefectly.

Bonzo
Posts: 1
Joined: Fri Dec 28, 2012 7:00 pm

Re: Samsung Screen Resolution Problems [newbe]

Fri Dec 28, 2012 7:03 pm

If it help, I had a problem with oversizing of the screen to my Samsung 38" screen. I resolved it by setting the screen to 'just scan' instead of the previously set '16:9'.

Return to “Other projects”