I've just conducted some tests on the power-cut bug using the new beta and it appears that the problem remains - the bug appears not to have been fixed.

Using loader U7.53 and 1.00.15 Beta.

It may well be that loader U7.54 is required along with 1.00.15 in order to fix this bug, given that we have been previously told that the loader needs to be updated to fix the bug.

It occurs to me that there are three cases to test the power-cut handling:-

1) While in full standby;

2) While in the 15 minute pre-recording monitoring standby period;

3) While recording.

I also noticed that the firmware is dated back in December. Why release it as a Beta if it has been tested for the last 3 months? I'm hoping when its officially released we have more features.

I'll tell you how I tested it anyway:
- Turn box on, set a timed recording to start in 30 minutes.
- Turn box off.
- Cut power to box for one minute.
- Put power back on to box.
(the box should boot up in 15 minutes from now to check for the start of the recording)
- Wait 20 minutes, confirm that the box hasn't booted up.
- Manually boot box up.
- Turn off box and watch it go into its "waiting for recording" standby.

The fact that the box didn't bring itself into the "waiting for recording" standby before I booted it up manually tells me that the bug isn't fixed, on U7.53 and 1.00.15 anyway.

Version 1.00.13 contained them too

Can someone please test recording from buffer?
Can also test pause whilst a program is recording? When the program gets to the end does the time shift stop playing?

scargill, just tested the above.

Neither has been fixed - you cannot record from the buffer and if you pause a programme you are recording then it jumps to the end of the programme when it ends.

And, whilst I was testing, the subtitles bug reappeared, whilst watching in timeslip.

It amazes me how long Humax can spend working on a new release and not fix anything.

Not impressed.

Has anyone tested the stereo down-mixing yet?

Edit: Just done so, or at least I think I have as I understand how this is supposed to work and that does not seem to be fixed either.

So, I make it that every single fix listed that has so far been tested by people on here has failed. Which leads me to believe that what we have here is not the new firmware at all. Incompetence or deception? You decide.

Has anyone yet tried the bug of a recording not starting when tuned to off air channel.

It must be a feature of PVR software development. Sky manage it as well.

To be fair though Sky's last interim update (made available for two days) did fix a couple of things they only claimed at the time to be 'aware of'. So they can't fix what they claim to be fixing but can fix things they aren't even trying to

Well - I would suggest that everyone who has installed the beta does test the ITV player and fill in the response survey - it will help the coming release and show Humax value in putting up beta's for end user testing.

maybe loader .74 is needed with this firmware, odd how humax will not release it as an update yet install it on all new stock.

And if the bootloader is needed to fix the power cut issue most users will never benefit from it unless they are advised to perform a manual bootloader update from USB.

Bootloader, I understand can not be done safely over the air.

Automan.

The latest bootloader is not required for the power cut bug fix.

http://myhumax.org/forum/topic/new-firmware-funnies

So far tested a power cut in the pre 15 mins prior to recording. That worked no problem. going to try one outside the 15 mins now

My hdr has just gone into recording sby after setting a recording reservation about 45 mins ago followed by a 5 minute power off. As far as I can see at least in respect of recovery from a power cut it works just fine.

That is good to know. Will try it myself now while listening to the cricket ...

1) On doing an instant record: Instant recording terminated at point of cut marked as bad recording but still able to play what it had - Qualified PASS

2) In standby doing an instant record: Recovered back to standby. Instant recording terminated at point of cut marked as bad recording but still able to play what it had - Qualified PASS

3) In pre-recording standby: Recovered back to pre-recording standby with correct time. Recording started ...

Edit: Whoops! Was an 11:30 end not an 11:00 end.

It would certainly be possible to use the ftp mods with the new firmware. All you'd need to do would be to replace the second filesystem block in the HDF file (and its associated validation block) with those from the modded HDF. All the changes are likely to be in the kernel and the settop application.

There exist tools to unpack and pack HDF files. (No I haven't done it.)

Hmm.

Not sure why it didn't work for me then - although I didn't give mine a 45 minute head start, it was more like 25 minutes.

3) In pre-recording standby: Recovered back to pre-recording standby with correct time. Recording started. Recording finished. Back to full standby. Recording plays properly. PASS

4) In full standby: Recovered back to full standby with recording pending in 20 minutes. Gone into pre-recording standby. Recording ...

Provided it was longer than 15 mins it should not matter, it just happened that the next programme outside the 15 minute window was about 45 minutes away.

Can you explain exactly what steps you did to emulate the power cut ?

From above:

I'll tell you how I tested it anyway:
- Turn box on, set a timed recording to start in 30 minutes.
- Turn box off.
- Cut power to box for one minute.
- Put power back on to box.
(the box should boot up in 15 minutes from now to check for the start of the recording)
- Wait 20 minutes, confirm that the box hasn't booted up.
- Manually boot box up.
- Turn off box and watch it go into its "waiting for recording" standby.

The penny might have just dropped actually....

As I pointed out up there ^^^ I set up a manual timer recording, rather than recording to the EPG.

Looks like the box doesn't wake up 15 minutes before a manual timer recording.

No it doesn't. Never has. Doesn't need to.

No it does not, nor does it if you set auto padding as there's no need as it knows when to start recording.