Black Hole
May contain traces of nut
Because I, for one, have my Humii set to stereo output not multichannel.
Because I, for one, have my Humii set to stereo output not multichannel.
This implies the box is capable of transcoding an audio stream in real time, and with minimal latency, unless AC3 is just a repackaging of AAC. Really? It seems far more likely that it simply passes through whatever comes in. (PCM doesn't require re-encoding, just decoding.)Pretty sure all Humax boxes convert aac to ac3 unless you turn off surround sound in the box TV setup.
This implies the box is capable of transcoding an audio stream in real time, and with minimal latency, unless AC3 is just a repackaging of AAC. Really? It seems far more likely that it simply passes through whatever comes in. (PCM doesn't require re-encoding, just decoding.)
PCM is only uncoded data converted to serial, so I don't regard this as transcoding - only decoding. "Pulse Code Modulation" simply means serial data.The box transcodes to pcm for digital audio output.
PCM is only uncoded data converted to serial, so I don't regard this as transcoding - only decoding. "Pulse Code Modulation" simply means serial data.
PCM is a serialised decode of the broadcast/recorded audio stream, for sending over HDMI - not a transcode. To create AC3 from AAC requires a decode of the AAC and then a re-encode to AC3, ie a transcode - I'm not saying it's impossible, but I very much doubt the HD- or HDR-FOX has enough horsepower or hardware support to perform the encoding without introducing a noticeable delay in the audio (lip sync errors). There is of course hardware support for decoding, which is a much simpler process.
Your position seems to stem from your belief in what your audio kit is telling you: that the audio stream from the HDR-FOX over HDMI when receiving/playing HiDef with multi-channel audio selected is AC3. I suggest it is mistaken, unless the broadcast itself is AC3 (which it is for satellite).
Besides, it makes sense for the HDR-FOX to pass through AAC or decode to PCM - a TV capable of HiDef reception will be able to handle AAC for sure, and if it isn't HiDef-capable there's PCM to fall back on.
So the answer does lie in the need for the receiver to either transcode to a suitable format such as Dolby AC-3 or DTS or to output multi-channel linear PCM. Earlier versions of the UK D Book were only able to recommend the presence of transcoding. But now that transcoding solutions are becoming available the UK is no different from all other European standards. No doubt receiver manufacturers are working hard to incorporate these into their products.
Fair enough, but it's well buried.Don't you ever bother to do the slightest bit of research before posting ?
http://www.bbc.co.uk/blogs/bbcinternet/2010/06/questions_around_surround_soun.html
Does that apply to all TVs or just yours? If only PCM is acceptable over HDMI then clearly no form of multi-channel audio would be practicable.From the spec of my twin Freesat twin Freeview Panasonic AS802B TV
External Equiment Valid Input Signals for HDMI.
2ch Linear PCM (Sampling 48kHz,44.1kHz, 32kHz).
No other audio input by HDMI is supported.
Fair enough, but it's well buried.
Does that apply to all TVs or just yours? If only PCM is acceptable over HDMI then clearly no form of multi-channel audio would be practicable.
All I can say about audio transcoding in the HDR-FOX is that I haven't seen anything in it that would be capable of doing the job (although it could be buried in a DSP in the SoC)... but I am very surprised that it is possible without significant delays in the audio path. We can assume the encoding is frame based (not video frames), and each frame would have to be long enough to contain enough waveform data to compress. Therefore, to transcode, a whole frame needs to be accumulated, decoded, re-encoded, and sent on, and then the renderer has to accumulate the frame and decode it. Even if the decoding/encoding is instant (which it isn't), there's an extra two frame buffer times in the delay path.
If a frame is 1024 samples (which I think it is), that's 25ms of audio, and at least 50ms additional delay in the audio path compared with simply decoding the audio once at the renderer. The lip sync setting only delays the audio further - not speed it up.
Yes, I admit I am pontificating without any hard knowledge. However, the more I think about it the more problems I can see and the more amazing it is if anyone has cracked them. And all this started from an article about how somebody cocked it up.
Electronics Weekly 24/08/2016 said:The ringmaster of Seoul
The memory industry is becoming as exciting as it used to be in the 1980s when the US was fighting against the Japanese while the Koreans prepared a massive assault – simultaneously building fabs and products for the 64k, 256k and Mbit generations.
Thirty years on, and the leading-edge is no longer kbits, Mbits or even Gbits but a mighty Tbyte of non-volatile storage in a BGA package weighing one gram, which is promised for next year by Samsung, which seems to have taken the technology lead in 3D NAND.
Five hundred and twelve 256Gbit three-bit/cell (‘TLC’) 64-layer chips in a 16-layer stack will go into its tiny frame. It will read sequentially at 1,500Mbyte/s and write sequentially at 900Mbyte/s. Samsung will put 32 of its Tbyte gems into a single solid-state drive (SSD).
This is setting a high bar, which Intel, Toshiba/Western Digital and Micron seem some way below.
Toshiba/WD says it is in pilot production of 64-layer 256Gbit chips, but Intel and Micron have to up their game from their current 48-layer products by the end of next year if they’re to stay in the running.
Thirty years ago, as now, Intel was losing money in the memory business. Next year will be crunch-time, with much depending on whether the company can ramp 3D cross-point (‘3D XPoint’) production and whether this will find customer acceptance.
Hovering menacingly in the wings Yangtse River Storage Technology is gearing up to make 3D NAND – but at what density in terms of layers or storage capacity, with what levels of reliability, yield, performance or production capacity no one knows.
Meanwhile the Samsung ringmaster in Seoul cracks the whip and sets the pace. “We want 100Tbyte SSDs by 2020”, it says .