Bug #1900
Problem with mkv header - sample rate
0%
Description
Apparently sample rate in the header of the mkv of recording doesn't match the contents which makes it impossible to watch it on players like omxplayer.
Please find attached the example file: "Lanterna-Verde.2013-12-29.mkv".
ffmpeg -i Lanterna-Verde.2013-12-29.mkv claims the audio tracks are Audio: aac, 48000 Hz, stereo, fltp (default)
mkvinfo Lanterna-Verde.2013-12-29.mkv claims the audio tracks are Sampling frequency: 24000
Files
History
Updated by Adam Sutton almost 11 years ago
- Category changed from PVR / DVR to Muxers
- Assignee changed from Adam Sutton to John Törnblom
Updated by John Törnblom almost 11 years ago
- Status changed from New to Need feedback
What does the recording log say about the sample rate? does it happen every time, or just occasionally?
Updated by nf gb almost 11 years ago
The log displays sample 2400 and it does happen every time.
Here's an example of the recording log:
"DiBcom 7000PC", network: "TDT Continente", mux: "TDT Continente: 754,000 kHz", provider: "", service: "RTP 2"
Jan 14 15:04:01 pi tvheadend2888: dvr: # type lang resolution aspect ratio sample rate channels
Jan 14 15:04:01 pi tvheadend2888: dvr: 1 TELETEXT
Jan 14 15:04:01 pi tvheadend2888: dvr: 2 H264 720x576 20:11
Jan 14 15:04:01 pi tvheadend2888: dvr: 3 AAC por 24000 2
Updated by John Törnblom almost 11 years ago
Okey, could you provide us with a mux dump or a pass through recording (pmt/pat rewrite disabled).
Updated by nf gb over 10 years ago
John Törnblom wrote:
Okey, could you provide us with a mux dump or a pass through recording (pmt/pat rewrite disabled).
Hi,
How can I do that? >Tv adapters>Multiplexes->Play?
Updated by nf gb about 10 years ago
Sorry to dig up this issue...
Here is the mux dump. I've noticed that the sample error only happens when using mkv (and not with the pass through).
thanks
Updated by Jaroslav Kysela over 9 years ago
- Status changed from Need feedback to Fixed
I believe that it's fixed in recent release. Create a new issue,if this problem exists for 4.x.