Threaded Mode | Linear Mode

**menakite** · 10th Feb, 2015, 07:57 AM

See http://www.raspberrypi.org/xenon-death-flash-a-free-physics-lesson/

**rikardo1979** · 10th Feb, 2015, 08:33 AM

a drop of glue over U16 and you are protected Big Grin

Exnor · 10th Feb, 2015, 10:49 AM

(10th Feb, 2015 07:51 AM)IriDium Wrote: According to the BBC the RPi2 will reboot if you take a flash picture of it Will save a lot of time if true

Lol. What? how the hell is that possible?

(10th Feb, 2015 07:57 AM)menakite Wrote: See http://www.raspberrypi.org/xenon-death-flash-a-free-physics-lesson/

How ok now i understand Tongue

ringlord · 10th Feb, 2015, 11:17 PM

Does Xbian output DTS-HS or Dolby TrueHD on RPi2?

**rikardo1979** · 10th Feb, 2015, 11:48 PM

(10th Feb, 2015 11:17 PM)ringlord Wrote: Does Xbian output DTS-HS or Dolby TrueHD on RPi2?

no it doesn't
it's Raspberry Pi limitations not XBian

ringlord · 11th Feb, 2015, 12:05 AM

Thanks, I understood that it was a RPi limititation but had hoped with the more powerful processor in RPi2 it would have been fixed.
As a very satisfied user of XBian on RPi model B, I don't see a reason to upgrade then?

**rikardo1979** · 11th Feb, 2015, 01:06 AM

(11th Feb, 2015 12:05 AM)ringlord Wrote: Thanks, I understood that it was a RPi limititation but had hoped with the more powerful processor in RPi2 it would have been fixed.
As a very satisfied user of XBian on RPi model B, I don't see a reason to upgrade then?

it's about licencing not a power. means the Raspberry foundation would have to buy those and than project into the final price of RPi

**Smultie** · 11th Feb, 2015, 01:14 AM

(11th Feb, 2015 01:06 AM)rikardo1979 Wrote:
(11th Feb, 2015 12:05 AM)ringlord Wrote: Thanks, I understood that it was a RPi limititation but had hoped with the more powerful processor in RPi2 it would have been fixed.
As a very satisfied user of XBian on RPi model B, I don't see a reason to upgrade then?
it's about licencing not a power. means the Raspberry foundation would have to buy those and than project into the final price of RPi

Or offer as a purchase like the mpeg2/vc-1 license?

**menakite** · (This post was last modified: 11th Feb, 2015 02:22 AM by menakite.)

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).

**rikardo1979** · 11th Feb, 2015, 04:17 AM

(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.

Dave400 · 11th Feb, 2015, 05:27 AM

The only issue I appear to be having is overscan related (I've searched and not found anything similar)

Overscan settings defined in config.text or set via previous boot in calibration, all is good..

Reboot device, background comes up, all appears good, then as the menu pops up (and the bleeep sound) the display jumps and resets back to 0...

**rikardo1979** · 11th Feb, 2015, 05:29 AM

(11th Feb, 2015 05:27 AM)Dave400 Wrote: The only issue I appear to be having is overscan related (I've searched and not found anything similar)

Overscan settings defined in config.text or set via previous boot in calibration, all is good..

Reboot device, background comes up, all appears good, then as the menu pops up (and the bleeep sound) the display jumps and resets back to 0...

what TV u got? make sure you have no overscan on on your TV and you have 16:9 by force not in auto in TV settings
no issue here at all

Dave400 · 11th Feb, 2015, 05:30 AM

(11th Feb, 2015 05:29 AM)rikardo1979 Wrote:
(11th Feb, 2015 05:27 AM)Dave400 Wrote: The only issue I appear to be having is overscan related (I've searched and not found anything similar)

Overscan settings defined in config.text or set via previous boot in calibration, all is good..

Reboot device, background comes up, all appears good, then as the menu pops up (and the bleeep sound) the display jumps and resets back to 0...

what TV u got? make sure you have no overscan on on your TV and you have 16:9 by force not in auto in TV settings
no issue here at all

Samsung UE40F6500 no problem with my old pi, just this new install on the rpi2..

**rikardo1979** · 11th Feb, 2015, 05:37 AM

(11th Feb, 2015 05:30 AM)Dave400 Wrote:
(11th Feb, 2015 05:29 AM)rikardo1979 Wrote:
(11th Feb, 2015 05:27 AM)Dave400 Wrote: The only issue I appear to be having is overscan related (I've searched and not found anything similar)

Overscan settings defined in config.text or set via previous boot in calibration, all is good..

Reboot device, background comes up, all appears good, then as the menu pops up (and the bleeep sound) the display jumps and resets back to 0...

what TV u got? make sure you have no overscan on on your TV and you have 16:9 by force not in auto in TV settings
no issue here at all

Samsung UE40F6500 no problem with my old pi, just this new install on the rpi2..

so why u using a calibration?should fit without any of these extra settings. I have never used one on any of my TVs in past 7 years

Dave400 · 11th Feb, 2015, 06:06 AM

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..