• The forum software that supports hummy.tv has been upgraded to XenForo 2.1!

    This upgrade brings a number of improvements including the ability to bookmark posts to come back to later. Please bear with us as we continue to tweak things and open a new thread for any questions, issues or suggestions in Site/Forum Issues.

Audio hiccups on BBC One HD recordings

ejstubbs

Member
I've noticed over the past week or so that recordings of programmes on BBC One HD seem to suffer from fairly frequent audio hiccups - brief drop-outs of sound lasting no more than a fraction of a second. The recordings of "Dublin Murders" from Monday and Tuesday were particularly affected (which was annoying because I find the accents and delivery on that programme tricky to follow at times anyway, although I managed without having to turn on subtitles).

This only seems to happen on BBC One HD, and only on recordings. It doesn't seem to affect recordings from other HD channels (although a recording of "Grand Tours of Scotland's Lochs" the other day had a massive video and audio glitch at one point, but that was very different to the persistent and annoying micro-glitches on the BBC One HD audio), and it doesn't seem to affect live viewing.

Any ideas?
 

Black Hole

May contain traces of nut
If you're sure the problem is not external: free up some disk space, run fixdisk. (I can't explain why slow disk accesses might affect audio and not video, but that's all I can think of.)
 
OP
E

ejstubbs

Member
If you're sure the problem is not external: free up some disk space, run fixdisk. (I can't explain why slow disk accesses might affect audio and not video, but that's all I can think of.)
Thanks for those suggestions. Not sure how much disc space I can free up, unfortunately, but I'll see what I can do, and then give fixdisk a go.
Which transmitter?
Craigkelly. (I have checked that it hasn't somehow managed to retune itself to Black Hill.)
 
OP
E

ejstubbs

Member
Ah, just hopped in to the webif and found this in the disk diagnostics:

Screenshot 2019-10-24 at 14.31.51.png

I'm guessing that's not good...

No idea why it should suddenly have started to run hot, unless the fan has failed.

Should I still run fixdisk, or should I investigate the over temperature issue first?
 

Ezra Pound

Well-Known Member
With the standard Humax firmware the fan turns on at 56 Deg. C so it has over-run that a little but as your 'Worst' temperature is only 62 Deg. C it is unlikely to have caused your problems, the 'FAILING NOW' message is very misleading and really only means that your unit has reached a temperature where the fan is turned on

I would proceed with the fixdisk, if the fan had completly failed your unit would have a much higher 'Worst' figure, it is worth checking the fan spins and that air flow isn't being restricted though
 

MartinLiddle

Super Moderator
Staff member
I'm guessing that's not good...
Wrong guess as Ezra has said. You might want to consider using the fan package to keep the temperature down. Please could you show the rest of the output from the disk diagnostic (cut and paste between code tags is better than inserting an image).
 
OP
E

ejstubbs

Member
Good to hear that the nasty red message isn't terminal! As it happens, I am required by SWMBO to delve around the back of the AV unit at some point today anyway so I'll check the fan and airflow while I'm doing that. I've installed the fan package and if the fan seems to functioning OK I will try dialling the minimum speed up a tad. (The sitting room has been a bit warm these past evenings, with the fire lit to take some of the edge off the autumn chill, so that might be why the Hummy's HDD has been running a little hotter than usual.)

I've got fixdisk running just now. So far it's looking OK, as far as I can tell. I'll post the output from that, and the full disk diagnostics from the webif, when that's done.
 

Ezra Pound

Well-Known Member
When running the fan package you can temporarily set the fan speed to 100%, it is then easy to hear and feel that the fan is spinning, normal 'fan' operation only requires 40 - 50% fan speed to be selected

There is also a Tempmon package you can install which will flash the main LED on the front of the unit at a pre-set temperature
 
Last edited:
OP
E

ejstubbs

Member
Here's the fixdisk output:
Code:
Please select option: fixdisk
Any additional options (-h for list or press return for none):
Are you sure you wish to run the hard disk checker? [Y/N] y
Running /bin/fix-disk

Checking disk sdb (512 byte sectors)

Unmounted /dev/sdb1
Unmounted /dev/sdb2
Unmounted /dev/sdb3


Running short disk self test
                  
No pending sectors found - skipping sector repair

Checking partition tables...

MBR Status: MBR only
GPT Status: not present

Using superblock 0 on sdb1
Using superblock 0 on sdb2
Using superblock 0 on sdb3


Thu Oct 24 14:57:28 BST 2019: Checking partition /dev/sdb3...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 240k/0k (157k/84k), time: 14.13/ 5.68/ 2.46               
Pass 1: I/O read: 165MB, write: 0MB, rate: 11.68MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 340k/0k (260k/81k), time:  0.01/ 0.00/ 0.01               
Pass 2: I/O read: 1MB, write: 0MB, rate: 74.25MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 340k/0k (260k/81k), time: 14.66/ 5.95/ 2.51
Pass 3A: Memory used: 340k/0k (260k/81k), time:  0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 340k/0k (259k/82k), time:  0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 340k/0k (54k/287k), time:  1.21/ 1.18/ 0.01               
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 340k/0k (53k/288k), time:  3.08/ 2.36/ 0.04               
Pass 5: I/O read: 1MB, write: 0MB, rate: 0.32MB/s

          19 inodes used (0.00%, out of 655776)
           2 non-contiguous files (10.5%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 3/2/0
      608312 blocks used (23.19%, out of 2622611)
           0 bad blocks
           1 large file

           8 regular files
           2 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
          10 files
Memory used: 340k/0k (53k/288k), time: 18.98/ 9.49/ 2.57
I/O read: 167MB, write: 1MB, rate: 8.80MB/s
Thu Oct 24 14:57:47 BST 2019

Thu Oct 24 14:57:47 BST 2019: Checking partition /dev/sdb1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 140k/0k (62k/79k), time:  0.81/ 0.25/ 0.42               
Pass 1: I/O read: 17MB, write: 0MB, rate: 21.04MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 140k/0k (72k/69k), time:  0.01/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 67.08MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 140k/0k (72k/69k), time:  0.93/ 0.28/ 0.43
Pass 3A: Memory used: 140k/0k (72k/69k), time:  0.00/ 0.00/ 0.00               
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 140k/0k (71k/70k), time:  0.01/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 140k/0k (50k/91k), time:  0.11/ 0.11/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 140k/0k (50k/91k), time:  0.32/ 0.26/ 0.00               
Pass 5: I/O read: 1MB, write: 0MB, rate: 3.11MB/s

          15 inodes used (0.02%, out of 65808)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 3/2/0
       15907 blocks used (6.05%, out of 263064)
           0 bad blocks
           1 large file

           3 regular files
           3 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
           6 files
Memory used: 140k/0k (50k/91k), time:  1.37/ 0.64/ 0.43
I/O read: 17MB, write: 1MB, rate: 12.37MB/s
Thu Oct 24 14:57:49 BST 2019

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=7ed2a574-4512-49aa-bd44-82cb423b677b

Thu Oct 24 14:58:12 BST 2019: Checking partition /dev/sdb2...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 824k/4672k (549k/276k), time: 1408.38/790.02/83.37       
Pass 1: I/O read: 7564MB, write: 0MB, rate: 5.37MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 824k/9344k (534k/291k), time:  2.54/ 0.63/ 0.15           
Pass 2: I/O read: 6MB, write: 0MB, rate: 2.36MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 824k/9344k (534k/291k), time: 1429.46/808.53/83.58
Pass 3A: Memory used: 824k/9344k (547k/278k), time:  0.00/ 0.00/ 0.00         
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 824k/9344k (528k/297k), time:  0.06/ 0.03/ 0.00
Pass 3: I/O read: 1MB, write: 0MB, rate: 16.29MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 824k/0k (484k/341k), time: 46.85/46.16/ 0.04             
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 824k/0k (471k/354k), time: 122.93/91.56/ 1.14             
Pass 5: I/O read: 29MB, write: 0MB, rate: 0.24MB/s

        8727 inodes used (0.03%, out of 29860704)
         439 non-contiguous files (5.0%)
          13 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 538/228/7
    71832199 blocks used (60.26%, out of 119209984)
           0 bad blocks
          48 large files

        6960 regular files
         415 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
        1343 symbolic links (1343 fast symbolic links)
           0 sockets
------------
        8718 files
Memory used: 824k/0k (471k/354k), time: 1599.43/946.29/84.78
I/O read: 7599MB, write: 1MB, rate: 4.75MB/s
Thu Oct 24 15:24:52 BST 2019
Removing extra swap space.

Finished
fix-disk: session terminated with exit status 0

Press return to continue:
And here's the disk diagnostics report:
Code:
SMART data read from device /dev/sdb

Disk Information
SMART Status    PASSED   
Model Family    Seagate Pipeline HD 5900.2
Device Model    ST3500312CS
Serial Number    6VV3ATMB
LU WWN Device Id    5 000c50 027e131f5
Firmware Version    SC13
User Capacity    500,107,862,016 bytes [500 GB]
Sector Size    512 bytes logical/physical
Rotation Rate    5900 rpm
Device is    In smartctl database [for details use: -P show]
ATA Version is    ATA8-ACS T13/1699-D revision 4
SATA Version is    SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is    Thu Oct 24 16:16:37 2019 BST
SMART support is    Available - device has SMART capability.
SMART support is    Enabled
Attributes
ID    Name    Flags    Raw Value    Value    Worst    Threshold    Life Left    Notes
1    Raw_Read_Error_Rate    POSR--    43418675    112    099    006        -
3    Spin_Up_Time    PO----    0    097    097    000        -
4    Start_Stop_Count    -O--CK    22652    078    078    020    73%    -
5    Reallocated_Sector_Ct    PO--CK    0    100    100    036    100%    -
7    Seek_Error_Rate    POSR--    579045516    087    060    030        -
9    Power_On_Hours    -O--CK    19975    078    078    000    78%    -
10    Spin_Retry_Count    PO--C-    0    100    100    097    100%    -
12    Power_Cycle_Count    -O--CK    11326    089    089    020    87%    -
184    End-to-End_Error    -O--CK    0    100    100    099        -
187    Reported_Uncorrect    -O--CK    0    100    100    000        -
188    Command_Timeout    -O--CK    0    100    100    000        -
189    High_Fly_Writes    -O-RCK    6    094    094    000        -
190    Airflow_Temperature_Cel    -O---K    35    065 (35°C)    039 (61°C)    045 (55°C)        In_the_past
194    Temperature_Celsius    -O---K    35    035    061    000        -
195    Hardware_ECC_Recovered    -O-RC-    43418675    045    022    000        -
197    Current_Pending_Sector    -O--C-    0    100    100    000        -
198    Offline_Uncorrectable    ----C-    0    100    100    000        -
199    UDMA_CRC_Error_Count    -OSRCK    0    200    200    000        -
Self-test logs
No.    Description    Status    Remaining    When    First Error LBA
# 1    Short offline    Completed without error    00%    19975    -
# 2    Short offline    Completed without error    00%    18801    -
# 3    Extended offline    Completed without error    00%    14845    -
# 4    Short offline    Completed without error    00%    14668    -
# 5    Short offline    Completed without error    00%    14608    -
# 6    Short offline    Completed without error    00%    8774    -
# 7    Short offline    Completed without error    00%    7203    -
# 8    Extended offline    Completed without error    00%    6661    -
# 9    Short offline    Completed without error    00%    5520    -
I'll install tempmon and see whether it indicates any issues in general use.
 

MartinLiddle

Super Moderator
Staff member
Nothing wrong there. I'd be more inclined to look at your aerial feed - signal/quality levels, cable type, wall plates, flyleads etc.
I agree with prpr on both counts. When tuned to BBC1 HD could you tell us the signal strength and quality (as reported by the Humax) please?
 
OP
E

ejstubbs

Member
Signal strength 70%
Signal quality 100%

As I mentioned before, I've not noticed the problem on recordings of programmes on BBC 2 HD (the aformentioned Grand Tours of Scotland's Lochs, plus NFL This Week, The Name of the Rose and Saving Lives at Sea) or Channel 4 HD (The Great British Bakeoff), which share the same mux as BBC 1 Scotland HD.
 
OP
E

ejstubbs

Member
OK, a development: watching The One Show live this evening (well I suppose someone has to) I thought I noticed another audio hiccup. I pressed the immediate record button to see if I could "capture" any more. Sure enough a number of further, very obvious glitches occurred, which quick reviews confirmed were also present on the recording.

So it looks like the issue is present in the live programme stream and not related to anything going on in the recording or playback process. Which still leaves the question: what's going on with the live broadcast - or my reception of it?
 

Born cynic

New Member
I've also noticed this, possibly for a few weeks. It's on both recordings and live TV, whether from my HDR-Fox T2 through the TV (Toshiba 40L2863DB) via HDMI, or using the TV tuner. This seems to be purely BBC1 Scot HD (I receive from the Angus transmitter). All the other (main) HD channels seem fine, as are the SD channels I watch/record from. I did send a complaint to the BBC yesterday, which has been acknowledged, but if I get a reply I'm sure it'll be the fault of my set-up.
 
OP
E

ejstubbs

Member
Thanks, it's reassuring to know that I'm not the only one experiencing this!

Unfortunately I can't check to see whether the problem occurs on the TV as well as the Humax as my TV doesn't have a DVB-T2 tuner. The only other DVB-T2 receiver in the house (the TV stick in the back of my computer) uses Black Hill, due to the location of the aerial it uses (it's on the other side of the house from Craigkelly, and below roof level, so can't get a decent signal from Craigkelly). Although I suppose I could run parallel recordings on the Humax and the computer to see if the problem affects Black Hill as well. If you're getting the problem from Angus, and I can demonstrate that I'm getting it from Black Hill as well as Craigkelly (and on completely separate aerial infrastructure), that might give the BBC techies something to actually think about rather than a standard "have you tried turning it off and turning it on again?" style response!
 
Last edited:

MartinLiddle

Super Moderator
Staff member
I can demonstrate that I'm getting it from Black Hill as well as Craigkelly (and on completely separate aerial infrastructure), that might give the BBC techies something to actually think about rather than a standard "have you tried turning it off and turning it on again?" style response!
Raise a complaint with the BBC via their web site; you should at least get a response (NB use the complaint procedure rather just a comment).
 

MartinLiddle

Super Moderator
Staff member
I've noticed over the past week or so that recordings of programmes on BBC One HD seem to suffer from fairly frequent audio hiccups - brief drop-outs of sound lasting no more than a fraction of a second.
Another thought; what Audio output setting are you using (Multichannel or Stereo) ? Do you still get the problem if you switch to the alternative?
 

Born cynic

New Member
This was their response:

Website Technical Fault - Case number CAS-5707719-C9M1G1

Hi there,
Thanks for getting in touch about the BBC website.
We’ve forwarded the details to the relevant team, and if it’s something they can correct they’ll do so as soon as they can.
We’ll be in touch again if we need to get back to you to request or provide further information.
Many thanks for letting us know.

Regards,
BBC Audience Services

I'm updating that complaint with the reference to Blackhill and Craigkelly also.
 
Top