Why this happened??

[MoonWalker]

Look at this sreenshot? Why is that??

http://www.geocities.com/aleksikerayno/1.jpg

Thanks,
MoonWalker

[anecd0te]

"We're sorry, but this page is currently unavailable for viewing."

Try moving the pic to another site, so we can see/ diagnose your problem :D

[MoonWalker]

But I can see it...Hmm well.. It's a scene from Blade Runner totaly filed with blocks...

http://www.geocities.com/aleksikerayno/1.zip

Here is in zip...And I also tried to attched it...

MoonWalker

[breathtaker]

copy and paste the url . i have the same problem but with viewing files from cds i get the samething but when i copy it to my hdd its still like your picture

[gooki]

from the looks of things it appears that you have a bad/corrupted keyframe in your movie.

[Slogra]

I don't think anyone know what causes these errors.

Not too long ago, I encoded a movie at a real low bitrate and it was full or these kind of errors. So maybe it's causes by a too low bitrate...

btw. the picture works when you remove http:// from the url.

[gooki]

from memory if you use fast re-compress (nandub) without any anti shit you can get bad frames. Also i had experienced bad frames through using flaskmpeg as well - reason - not sure - was a long time ago.

[destarded]

so anti-shit is worth the extra time?
I mean, better safe than sorry, right?

[diji1]

gooki : from memory if you use fast re-compress (nandub) without any anti shit you can get bad frames.

i don't necessarily think that's a given ...

destarded : so anti-shit is worth the extra time? I mean, better safe than sorry, right?

sometimes ;). sometimes it can increase filesize, meaning u have to tune the settings to try and remove any shit and keep in ur target filesize. i personally don't use that feature unless i encounter bad artifacts or "shit" on viewing the video then ill re-encode with it turned on, others have it on as a "default" setting. i think that prolly both methods have their drawbacks - i end up re-encoding and others end up using it where there really was no need for it ... just depends what we happen to be encoding and other settings/filters.

[Pen-Pen]

Originally posted by gooki
from memory if you use fast re-compress (nandub) without any anti shit you can get bad frames. Also i had experienced bad frames through using flaskmpeg as well - reason - not sure - was a long time ago.

for antishit to work, you need to set nandub in full processing mode, you know ^^

[AuK59]

out of curiosity, what are your system specs?