[rikardo1979]

(11th Feb, 2015 06:06 AM)Dave400 Wrote:  I used it initially as I still had a CRT TV when I first got the Pi, there for calibration has remained in use since..

Ahh, I removed the sdtv settings, maybe that's why..

not sure I get you, so all is good now? no calibration needed?

[menakite]

(11th Feb, 2015 04:17 AM)rikardo1979 Wrote:  are you sure about this?

Yeah, unfortunately yes :|
See more detailed explanation from popcornmix: http://forum.kodi.tv/showthread.php?tid=217063&pid=1912191#pid1912191

[Dave400]

(11th Feb, 2015 06:16 AM)rikardo1979 Wrote:  

(11th Feb, 2015 06:06 AM)Dave400 Wrote:  I used it initially as I still had a CRT TV when I first got the Pi, there for calibration has remained in use since..

Ahh, I removed the sdtv settings, maybe that's why..

not sure I get you, so all is good now? no calibration needed?

Disable overscan and overscan left, right,top bottom values work outside of xbian (ie in terminal) seems xbian once booted overrides the settings till manually set.

[rikardo1979]

(11th Feb, 2015 06:44 AM)Dave400 Wrote:  

(11th Feb, 2015 06:16 AM)rikardo1979 Wrote:  

(11th Feb, 2015 06:06 AM)Dave400 Wrote:  I used it initially as I still had a CRT TV when I first got the Pi, there for calibration has remained in use since..

Ahh, I removed the sdtv settings, maybe that's why..

not sure I get you, so all is good now? no calibration needed?

Disable overscan and overscan left, right,top bottom values work outside of xbian (ie in terminal) seems xbian once booted overrides the settings till manually set.

please, can you post all lines from your config.txt ?

[Dave400]

(11th Feb, 2015 06:53 AM)rikardo1979 Wrote:  please, can you post all lines from your config.txt ?

Terminal

#initramfs initramfs.gz 0x1000000
gpu_mem_1024=256
gpu_mem_512=144
gpu_mem_256=100
initial_turbo=3
decode_MPG2=0x
decode_WVC1=0x
overscan_left=38
overscan_right=38
overscan_top=22
overscan_bottom=22
hdmi_ignore_cec_init=1
disable_overscan=1
disable_splash=1

[rikardo1979]

(11th Feb, 2015 09:33 AM)Dave400 Wrote:  

(11th Feb, 2015 06:53 AM)rikardo1979 Wrote:  please, can you post all lines from your config.txt ?

Terminal

#initramfs initramfs.gz 0x1000000
gpu_mem_1024=256
gpu_mem_512=144
gpu_mem_256=100
initial_turbo=3
decode_MPG2=0x
decode_WVC1=0x
overscan_left=38
overscan_right=38
overscan_top=22
overscan_bottom=22
hdmi_ignore_cec_init=1
disable_overscan=1
disable_splash=1

OK, thats confusing now. cos you said you use to have it on your SD TV but as I understand now you run it on Samy flat screen over HDMI.
so you shouldnt use any overscan and igonore cec

Terminal

#initramfs initramfs.gz 0x1000000
gpu_mem_1024=256
gpu_mem_512=144
gpu_mem_256=100
initial_turbo=3
decode_MPG2=0x
decode_WVC1=0x
#overscan_left=38
#overscan_right=38
#overscan_top=22
#overscan_bottom=22
#hdmi_ignore_cec_init=1
disable_overscan=1
disable_splash=1

[Dave400]

I use hdmi_ignore_cec_init=1to prevent the tv from switching automatically, for instance, if I'm doing stuff on the pi via ssh that requires a reboot. the wife gets narked if the tv switches over whilst shes watching something on normal tv..

As it is, commenting out overscan and cec init still looses the edge of the image per image.


The settings from my old pi (still shows as RC3) which works fine is:

Terminal

initramfs initramfs.gz 0x1000000
gpu_mem_256=100
gpu_mem_512=128
sdtv_mode=2
sdtv_aspect=3
decode_MPG2=0x
overscan_left=41
overscan_right=26
overscan_top=9
overscan_bottom=18
initial_turbo=1
arm_freq=840
core_freq=275
sdram_freq=400
over_voltage=0
disable_overscan=1
hdmi_ignore_cec_init=1

[Smultie]

(11th Feb, 2015 06:31 PM)Dave400 Wrote:  I use hdmi_ignore_cec_init=1to prevent the tv from switching automatically, for instance, if I'm doing stuff on the pi via ssh that requires a reboot. the wife gets narked if the tv switches over whilst shes watching something on normal tv..

As it is, commenting out overscan and cec init still looses the edge of the image per image.


The settings from my old pi (still shows as RC3) which works fine is:

Terminal

initramfs initramfs.gz 0x1000000
gpu_mem_256=100
gpu_mem_512=128
sdtv_mode=2
sdtv_aspect=3
decode_MPG2=0x
overscan_left=41
overscan_right=26
overscan_top=9
overscan_bottom=18
initial_turbo=1
arm_freq=840
core_freq=275
sdram_freq=400
over_voltage=0
disable_overscan=1
hdmi_ignore_cec_init=1

Are you sure it's not related to a setting on your TV? Overscan is often changeable on your TV as well.

[Dave400]

If that was the case wouldn't any other hdmi input be affected in the same way..

As I said before, my old pi was fine, this issue has been since I applied the fresh image to the rpi2

[Smultie]

(11th Feb, 2015 07:46 PM)Dave400 Wrote:  If that was the case wouldn't any other hdmi input be affected in the same way..

As I said before, my old pi was fine, this issue has been since I applied the fresh image to the rpi2

If you use your new Pi on the same HDMI-input as you used your prior Pi, you are probably right.
If not; sometimes you can set overscan per HDMI-input?!

[rikardo1979]

just get rid of all sdtv lines and overscan etc. it should work be default , and yes make sure u don't have overscan on TV
you should not use sdtv if u using HDMI as it's only for composite video out

[Dave400]

SDTV lines were on old pi, never needed to remove them, saw no need to include them for the new pi..

Overscan lines commented out edges cut off..

It doesn't work by default..

It's on the same HDMI input and the same HDMI lead

[IriDium]

Ok, latest update (11/02/2015) has brought back the names in Xbian-config Kodi. However, xbian-config.common.clicktoload is still visible until clicked.

[Eric Petty]

(11th Feb, 2015 04:17 AM)rikardo1979 Wrote:  

(11th Feb, 2015 02:22 AM)menakite Wrote:  No, it's a hardware limitation. The bandwidth of the GPU cannot handle HD audio.
On the Pi 2 though it seems these can be decoded in software and you'd get 5.1 PCM (assuming your receiver supports multichannel PCM).

are you sure about this?

Quote:by dom » Sat Sep 08, 2012 10:39 pm
Hardware: yes.
Software: no.

I've been hoping another customer would request it, but so far it's not been asked for.
I asked around and was quoted about a man-week to do the work (from the guy who did the standard DTS passthough).

Need to find out if RPF could justify paying him to do the work.

Dolby is definitely licensing, but if you want higher quality audio just pick up a Wolfsen board: http://www.adafruit.com/products/1761?gclid=CjwKEAiAmOymBRD0_evS4aTh2hUSJAB7Fkhywidyk9-l2YAz_n6tTZ6x9PD67y0fAYPWnDWsTD1NiBoC2Nrw_wcB

Then you could even use the older pi's you have hanging around for HD audio (5.1 etc)

[rikardo1979]

(12th Feb, 2015 04:31 PM)Eric Petty Wrote:  

(11th Feb, 2015 04:17 AM)rikardo1979 Wrote:  

(11th Feb, 2015 02:22 AM)menakite Wrote:  No, it's a hardware limitation. The bandwidth of the GPU cannot handle HD audio.
On the Pi 2 though it seems these can be decoded in software and you'd get 5.1 PCM (assuming your receiver supports multichannel PCM).

are you sure about this?

Quote:by dom » Sat Sep 08, 2012 10:39 pm
Hardware: yes.
Software: no.

I've been hoping another customer would request it, but so far it's not been asked for.
I asked around and was quoted about a man-week to do the work (from the guy who did the standard DTS passthough).

Need to find out if RPF could justify paying him to do the work.

Dolby is definitely licensing, but if you want higher quality audio just pick up a Wolfsen board: http://www.adafruit.com/products/1761?gclid=CjwKEAiAmOymBRD0_evS4aTh2hUSJAB7Fkhywidyk9-l2YAz_n6tTZ6x9PD67y0fAYPWnDWsTD1NiBoC2Nrw_wcB

Then you could even use the older pi's you have hanging around for HD audio (5.1 etc)

doesn't that requires ALSA?