Do a flash erase when changing images.
How come Aurora and cccam 2.0.8 works on your 7020 and only cccam 2.0.0 works everywhere else?
This is a bit long but should be of interest to some.
I have a 7020, Gemini 4.3 Cccam 2.0.8 Newcs 1.50. Works with Aurora keys (previously had to use cccam 2.0.0 or lower in my DM500) Works with external phoenix. Pictures are perfect - no pixelation either when reading a card in the phoenix or from a cs server on V or H TP's on C1 or playing back something from the HD.
I also have a DM500. I've tried Gemini 3.1 with Cccam 2.0.3 and Newcs1.30. Can't get Auroa with keys. Got it working with a phoenix and has perfect pictures with no pixelation either with reading a card in the phoenix or from a cs server on V or H TP on C1.
I also tried with Cccam 2.0.0 and Newcs 1.20. Initially I found the channel changing slow but seemed ok after a few minutes. But works with Aurora. otherwise, all results are the same as above.
I didn't do any recording and playback with the Gemini 3.1 image. It was time consuming as it was doing what I did!!
Now what prompted all this was I loaded Gemini 4.1 and 4.2 on my DM500 when they came out thinking the latest is always best and was always getting some sort of pixelation. This seemed to be while watching FBO channels which are all on V TP's. Now I can't get a phoenix reader to work with these image versions either hence me going back to Gemini 3.1 to see if I could get the phoenix going. I haven't tried Gemini 3.6.
I decided to build up an image like my 7020 from scratch for my DM500 except with Gemini 4.3.1 instead of 4.3, Cccam 2.0.8 and Newcs 1.50. I couldn't get an external phoenix going still. I could get pics via CS but once again some pixelation.
So the big question. Why with Gemini 4.x on a DM500 do I get the pixelation and why can't I get a phoenix going? The 7020 runs great with the latest. The DM500 runs great with Gemini 3.1 etc. Is it a case that the newer images are somehow 'bloated' and hence run slower on a DM500 becasue of less memory or some other reason???
I know I'm not the only one experincing this!
Leroy
PS And before someone goes on about trying Pli I did try Z80's image which was configured for a phoenix and was pixelating using a card in the reader and watching C1 V TP's!!
Look Here -> |
Do a flash erase when changing images.
How come Aurora and cccam 2.0.8 works on your 7020 and only cccam 2.0.0 works everywhere else?
Thanks Leroy for your efforts, tried the gemini 3.1 image with cccam 2.0.8 and has fixed all my problems with pixelation.
I agree the newer images on the DM500 cause pixelation, thats my experience anyway with gemini 4.3.1 and PLI 2008 image. Cam versions did not make a difference for me.
There is a lot more free memory when running the gemini 3.1 image than there was with the later images.
Everybody must be getting similar results with newer versions of images on DM500's?
Yep I am. Gemini 4.3.1 and cccam 2.0.8.
Seems like 3.1 is a solid image. Anyone comment on > 3.1 and < 4 versions having the same problem? I wondering if I should got back to 3.1 or, for example, 3.6 had some good bug fixes.
Did some more testing and I only saw pixelation 1 time watching box office over a couple of hours with a cardserver over the internet... try the same thing with gemini 4.3.1 or latest pli on a DM500 on a local card server and get pixelation city every couple of minutes.. go figure.
I will try gem 3.6 and see how it goes.
4.3.1 with cccam 2.0.8 - free mem approx 2.4MB
3.6 with cccam 2.0.4 - free mem approx 6.5MB
Haven't tested 3.6 long enough yet to make a call.
Can anyone without pixelation post their free mem usage?
I got this stat by pressing the blue button, going to sys info, and selecting memory info.
Side note - I downloaded 2.0.8 because it did not show in the list of addons under 3.6 (anyone find that?). I tried a manual install coying the file to /tmp. Everything looked like it installed OK and the completed dialog appeared. But when I see the available CAMs in the 'blue' button screen it's not there. Tried a couple of times and restarted with same result.
hmmm, fascinating thread. I am having massive issues with pixelisation, perhaps this throws some light on it.
I think when i have some time, i'll play around with images to see if I can make it run a bit nicer.
:edit: Running Gemini 4.1.0 with CCCam 2.0 decoding an NDS channel, have 3.7MB free. Still get pixelisation though.
lukebe you can just replace the CCcam_2.0.4 binary with the 2.0.8 binary (the extension of the binary you want is .ppc) in /var/bin, just overwrite it, make sure the new file is chmoded correctly like the old binary. It will still display cccam2.0.3 etc in the menu though but its really running 2.0.8 binary. I havent figured out how to change it in the menu yet but havent looked to hard yet.
Food for though. Anyone played with a sawp file?
3.6 running cccam 2.0.0 - 7.1MB free me - no pixelation so far.
How's the Gem 3.6 going Lukebe?
I'm surprised more aren't having these pixelation issues with 4.x images. Is this the case or a few of us just unlucky?
Leroy
Gemini 3.6 was the best image I found.
Just made up a DM500s gemini 4.31 image and it is also fine.
Pli will DEFINITELY pixellate more as a server under Cccam 2.0.5.
I have proven it. The channel changes are slower etc etc.
As a client... Pli is okay, as the cam downloads are quite intensive.
LeroyPatrol - I was a fan of 3.6 but unfortunately it gives me the same result, although slightly less pixelation than 4x. Still not good enough.
Starting to think it's not the image but some other factor. Got a list of theories that I've got to step through and test.
I don't think it's the image that's your problem. There would be plenty more posts if it were. Going to be a process of elimination me thinks
I can vouch also that I still get Pixelation on a DM500s using Geminin 4.+ as described in this post.
When I have a moment I will load a DM500 with an older Gemini 3.6 image and see what happens.
Bookmarks