As far as I am aware, and according to the leaflet included, you have to have it set to ON TIME both for the start of a recording and also ON TIME for the end of a recording (set in same place where you now set padding) for the Accurate recording to work, it seems that if you choose to pad, then accurate recording will not work??? As it states (and I quote) Auto tracking (the name that Humax give for accurate recording) becomes available when setting the recording's start/end time to ON TIME. (end of quote.) Now I read that as to mean that if you pad, it won't work because you have to choose either ON TIME or the padding say 2mins, etc, you can't select both.

GG

No dazbarber, you are misunderstanding what I was asked by the poster to check. He wanted me to check the anomoly that had happened to him with the00.10 build where say you had set two recordings and then forgot and later set a recording which would overlap either of the two recordings, with that build there was no warning, and you were allowed to set the third recording, which obviously then stopped one of the original recordings from taking place, and should not have been allowed. So he asked me to check if this still occured and it will now not let you do this if there is going to be a conflict of recordings, and this is actually how it should work!! Its a twin tuner, you can record two channels simultaneously, but not three, so if you had two recordings set where say one was from 2.30 to 3.00 another set from 2.30 to 4.00 and then ages after you tried to set another recording for 2.00 to 4.00 you would effectively be asking it to record three, so now you cannot set a recording if it means it will conflict with other recordings already set, the warning pops up and this is how it should work!!

GG

Yes Phil and this feature is also part of the Freeview specs, the user must be informed if there is or will be a conflict of recordings being set. (Or words to that effect.)

GG

Thats not the bug GG. The bug is when you try to set recordings that follow each other. For instance, you set Eastenders and another at 8pm on Monday and then after you set Coronation Street at 7:30pm. Although the Humax should have no problem recording all 3(it should drop auto padding) if they are not set in the correct order then 1 of the later recordings will fail. Setting up the recordings in chronological order results in all being recorded correctly.

Has this been corrected in this firmware?

On the subject of GG extracting the software, I'm not sure this is possible. I tried to do it on my 9200T using Formula4Neo and although there's a .hdf file appeared, it's only 16KB, which is nowhere near large enough.

Just got off the phone with Humax to ask them when this software will appear on the internet. They claim that there is no Freeview Plybk firmware on the new boxes and they all have .10! Is this software going on the internet??

Hmm, strange that people have V.15 on the new boxes .......

Re
re: "I'm only an old granny you know!!! " - don't believe you!

You are an exemplar of why this forum is so good; people spending their own free time for the general good! I'll come and do the ironing for you!

Since no-one has replied to your question: Project X and a suite of related software - allows one to demux (i.e. strip out the broadcasting info) a recorded program that you have transferred to your PC and end up with something you can burn on a DVD, at near DVD quality. The related software from memory is Cuttermaran, DVD Styler, VideoLAN and I think it was "Dare Devil Denis" manged to create a script to run them all in sequence automatically! Sorry I can't remember the details, it's 6months ago, but if anyone is interested see earlier posts elsewhere on this forum.

<<A 4mb broadband could in theory delivery approx 30mb of a file per minute, or 1.2gb in about 40mins - right on the money with your question GG!>>

Regards - Browntea

Sorry, bytes or bits?

fair point !
I've followed convention - if unspecified it is Bytes for file sizes, and bits for datacomms.

So 4mb broadband really means 4Mbit broadband
And 1.2Gb file means a 1.2Gbytes file
(and to transfer a file down a wire, 1byte = 8 bits)

Browntea

Hm, will believe it when I see it. How many times have we been promised OTA upgrades, only to see v6 repeated again and again...?

Isn't standard convention MB = megabytes, and Mb = megabits?

Sorry I misunderstood you!! (me old brain you know!) So you want me to set a programme with padding and then another that starts at the same time with padding and then go back and set one that preceeds one of the set programmes (with the padding which would conflict) Is that correct?? Does it matter how much padding??

GG

Well what do you deduce from that???

GG

Hey thanks for that!! Well its true! I am 63 years old, and I really am a granma but one who is into all the new technology and av equipment, and a firm believe that you must keep the old brain ticking over!

GG

That is the correct scenario. I think the important bit is padding before but I've not tested all the scenarios. I have mine set to 2 mins before and 3 mins after.

When you add the earlier recording first padding is dropped on the later recordings.
I think what happens is the before padding is included as part of the schedule (e.g. 10:58 - 11:30) whereas the after padding happens at record time.

When the two later recordings attempt to start early the earlier recording is still in progress so one of the later recordings doesn't happen.

i.e.
The following sequence loses a recording

1. Timer 11:00 - 11:30, sched 10:58 - 11:30
2. Timer 11:00 - 11:30, sched 10:58 - 11:30
3. Timer 10:30 - 11:00, sched 10:28 - 11:00

You can see here that between 10:58 and 11:00 there are three recordings scheduled so one will be dropped

The following sequence makes all three recordings

1. Timer 10:30 - 11:00, sched 10:28 - 11:00
2. Timer 11:00 - 11:30, sched 11:00 - 11:30
3. Timer 11:00 - 11:30, sched 11:00 - 11:30

As there is already a recording up to 11:00 pre-padding is dropped for recordings 2 and 3.

It's a bit confusing so I hope I've explained that clearly.

Right finished my tests of the padding and recording being dropped test, as follows.....

All set with 3 mins padding at start and end of recordings.

The Wright Stuff......Five............9.00 am to 10.00 am
Earth Story..............Uk History..9.00 am to 10.00 am
Big Brother..............Ch 4...........8.30 am to 9.00 am

Set in that order so BB Ch 4 set after the other two.

Results All recordings made as requested, no recordings dropped!!! So make of this as you will. Will set some more if you want and different padding times if requested but can you please try to be specific when asking as because I have never set padding myself in the past, I need it spelt out for me ( and me brain!!)

GG
Last edited by Grannygrunt : 21-06-2007 at 09:54

Thanks for your time testing this GG.

It looks like Humax may have fixed this one. It's caught me out a few times in the past. The only thing I need fixing now is the saved EPG and the truncated programme names

Can you confirm you set the padding before setting the recordings. Can you also confirm what times the three programmes were recorded for. I would guess;

The Wright Stuff......Five............9.00 am to 10.03 am
Earth Story..............Uk History..9.00 am to 10.03 am
Big Brother..............Ch 4...........8.27 am to 9.00 am

Hi


Thanks GG, however this is the same as what we currently get on version 10 software, so I'm not sure why the question is being asked unless it confirms that with padding enabled the functionality is the same on version 15 as it is on version 10.

With accurate recording 'on' you would not have been allowed to set the Big Brother timer event as the recorder would not know the precise time it would end and it isn't allowed to cut it dead at 9am to allow it to use the second tuner for one of the other recordings, as the whole point of accurate recording is to get it in it's entirety.

The other thing to test perhaps to see if work has been done on padding recordings is to set two back to back, for example:

Program on BBC1: 12:00 to 12:30
Program on BBC2: 12:30 to 13:30

(of course this doesn't have to be BBC1 or 2 but any channel as long as they are different channels).

The current behaviour some don't like is the recorders priority is to keep one tuner free for watching. In order to do that it has to drop padding, so the earlier recording stops dead on 12:30 (rather than 12:30 plus the padding minutes), the tuner then changes to BBC2 and starts recording dead on 12:30 (rather than 12:30 minus the padding minutes). The result being you are likely to loose the last few minutes of the end and start of each recording as padding is removed. I've been caught out by this before!

What some would like to see is priority given to using the tuners for recording. In the above example tuner 1 records the BBC1 program from 11:57 to 12:33 (assuming 3 minutes of padding each side) and at 12:27 the second tuner is employed to record the BBC2 program from 12:27 to 13:33. So padding remains in this case.

For accurate recording, then the recorder would have to use both tuners as it can't just shut a recording down by itself, it only reacts to the signal sent to it, but have they changed the behaviour when using padding?

Regards

Phil

This is not the same as v10. Currently v10 will allow you to set these three timers but will only record two of them. It depends on the order you set the timers and only occurs if you have padding enabled.

For me this was the most serious bug in v10 as it meant you could lose recordings without knowing it.

The sloppy convention used between people who are on the same wavelength rather than one used to communicate precisely and effectively with the world at large? I was more concerned about your indiscriminate use of m and M.

4 milli-bits per second *is* a tad slow.

Hi


I thought this was fixed from version 8 upwards? I've set timers in this order and it has worked absolutely fine, and I use padding.

Regards

Phil

Yes he promised me he'd let everyone know and he's said nothing since. I sent him an email the other day reminding him of this and pointing out they've since released the 9200TB and heard nothing back !

Perhaps it also depends on the muxes the channels are on. I have v10 and this has happened to me several times. It's very annoying. Especially when you know about it but it still catches you out.

I'm not sure that I get this. Following this logic you will never be able to set consecutive recordings.