146 replies to this topic

[swiffer]

Tuner A for me. The only thing I do, is to insert an USB key to watch another film during the record of the incredible.
In fact, at the present time my both receiver are connected.
So, tonight, Dr Who & Wild Hogs are scheduled, and I will do nothing on it.
Recording demux size was previously set to 1,5 Mbytes, I set it to 2Mbytes to see.

both record failed (5 mn & 35 mn).

[johnybegood]

@OD. Did you already test with the original image? Could you send me link to download the orignal one?

Thanks OD

Br,

Jbg

[johnybegood]

Problem recording:

I have got an email today form Clarke-Tech. This email is in german and I will post it here:

Sehr geehrter Herr xxx,

soweit uns bekannt ist , wird das Problem behoben !

In den nächsten Tagen wird ein Forum für den ET9000 eröffnet und es werden
weitere Images zu Verfügung gestellt.


Mit freundlichen Grüßen / Best Regards

CT Support Team

My english translation:

Dear Mr. xxxx

We know about this issue and this problem will be solved.
In the near future a support board from us will be opened and there we will provide images aswell.

Best regards,

Customer support team CT


Br,

Jbg

[Pedro_Newbie]

soweit uns bekannt ist , wird das Problem behoben = As far as we know will this problem be solved

[jedeje]

I guess http://et-view.com/d...d/image_makers/ is the link. The image then is the 24-11-final.zip file.

My one timer recording last night using the 2.0 Beta went ok. Looking at the list of failed recordings, it looks like HD recordings fail more often then SD ones but that might be a coincidence.

It also looks like the failures happen when the box is doing two or more things at the same time. All my timer recordings that took the box out of standby and back into standby are ok. But these are all SD and just 35 minutes in length each.

Did anyone already report this behaviour to Clarke Tech?<- Ah just saw the other postings about CT's response.... /images/smiley/smile.gif .

Gr
JeDeJe

[malakudi]

I also experience the same problem with NFS mounted NAS as HDD. Recordings (scheduled or interactive) fail at random interval.

I also want to report the following issues:

1. deinterlacer/upscaler are not setup correctly. SD interlaced content (most SD content is interlaced) is shown with fields inverted on 1080i output and with flickering on 720p or 576p output (it can be easily observed in channel logos). I can only get good SD interlaced quality only when I set autoresolution plugin to provide 576i, thus disabling deinterlacer/upscaler of the chipset.
2. SNR is always 98-99%, it doesn't scale according to signal.

[nfnovice]

I dont have one of these .. but is the issue tied to file size ?
like anything recorded over 2gb doesnt work ?

might make sense why SD for 35 mins works
and HD fails more often ..

worth a think

[johnybegood]

@nfnovice
no. I have file sizes from 300MB up to 3.6GB, so this cannot be the problem.

[OldDeuteronomy]

No, has nothing to do with filesize. Some of my test recordings are only 2 or 3 minutes, which is way below any kind of filesize boundary.


@Jbg: I will test the factory-preloaded image now and will report later.

[OldDeuteronomy]

There is a new driver available:

http://www.et-view.c...44-20101227.zip

Changelog says:

- recording improvements

Trying it now.

[johnybegood]

I am not a home, so I can not try now. Thanks a lot OD, your comments are always helpful!

Br, Jbg

[OldDeuteronomy]

Well, what could be more fun in xmas vacation than beta-testing crappy sat receivers

[OPERATION]

Is there a chance to convert and test the new drivers with the OpenPli 1.0?

[OldDeuteronomy]

No. And it would seem to me like new drivers will only come out for OE2.0, so OE1.0 will probably not be developed any further. Let's face it: The OpenPLi team themselves has not updated the OE1.0 image since 10 days.

For me, it's not an issue at all, because all I need runs perfectly well under OE2.0.

My test recording with the new driver is still running. Push thumbs!

[swiffer]

Well, what could be more fun in xmas vacation than beta-testing crappy sat receivers

I totally agree :-)


I switch on 2.0 and will perform tests with these new drivers

[malakudi]

Well, what could be more fun in xmas vacation than beta-testing crappy sat receivers

Unfortunately early time to market is more important than bug-free operation. This has happened with all linux receivers. Even DM800 at early stages had many issues. I wouldn't call ET9000 "crap", it has very good hardware specs, I guess most driver issues will be resolved soon.

[OldDeuteronomy]

Unfortunately early time to market is more important than bug-free operation. This has happened with all linux receivers.

Yes, I know. I owned most of them.

[swiffer]

I am an owner of a CT 5000 HD since 4 years. I bought it a couple of weeks after its market availability. The responsiveness of CT support has always been good in the past for this receiver. This was my first "free" receiver, and in 4 years, I got perhaps 4/5 resets, and missed 2 records !

So I am confident, this will be certainly also the case for this receiver.

[malakudi]

CT5000HD was running enigma2? Or own image?

[OldDeuteronomy]

OK guys, I would say the new driver fixes the issue. My test recoring is now already at approx 7GB, which is way more than I ever had before. I will let it run for some additional time, and then I will do some more tests (parallel recordings, switching channels while recording), but I think it's fixed.

On one hand, I find it totally unacceptable that the box was launched with such a major and obvious bug. On the other hand I am quite delighted that CT provided a fix so fast, having in mind that it's only 1 day ago that I reported this issue for the very first time. This is impressive and makes me believe that future bugs that need to be fixed in the drivers will be quickly adressed as well.