Log in

View Full Version : Green Problem!


FroggSkippa
14th March 2003, 04:24
Ok I've seen numerous accounts other places then just here about getting a green cloud on playback.

Well honestly I never experienced green clouds at all until I just started using Keopi's new latest unstable build.

I don't know if you would call it a green cloud or not but going vertically across the resolution of the the movie there is a thick green line that takes up bottom half of the movie. Now for the upper half I get like the movie but branched off 3 times with crazy lines going through the movie :p Now is this Green Clouds? If so then whats the proper way to get rid of them? But if not what in the blue hell is this then it's just really weird and I never seen this before. I've always used Keopi's stable build, but I wanted to try unstable because I know it has more unlocked features of the codec to produce better quality! So please any help would be appreciated and until then I'll search and see what I can find :D

EDIT: Going to get a snapshot quick!

FroggSkippa
14th March 2003, 04:56
http://geocities.com/natefrogg15/images/feck.txt

Pretty nasty looking huh? :scared:

BoNz1
14th March 2003, 04:59
It would be helpful if you would have said something about what you are using to playback the movie. Probably installing the latest ffdshow from here will solve the problem though, http://sourceforge.net/projects/ffdshow/

FroggSkippa
14th March 2003, 05:03
I'm using BSPlayer I'm going to try Nic's standalone direct show filter now I already tried this version of ffdshow "ffdshow-20030103" That's the newest Alpha!!!!! I'll also try there June 17th build! of ffdshow

FroggSkippa
14th March 2003, 05:12
Well still doesn't work with Nic's newest standalone decoder installed I get some green shit with both BSPlayer and WMP9 :( I usually don't use WMP9 though. I mainly use BSPlayer or just basic mplayer2.exe!

Ok now whats really weird is this I open up the video I encoded in VirtualDubMod and hehe it gave me a really weird error!

WARNING: NOTHING TO OUTPUT B-FRAME DECODER LAG!

I Can still scroll through the movie though with the slider and I get the green shit throughout I'll try the latest regular build of ffdshow now!

Frogg

EDIT: If it doesn't work with ffdshow june 17th 2002 version I'll come back with the options I used to encode the movie with! Also I'll check the stats file!

FroggSkippa
14th March 2003, 05:34
EDIT: Also I don't use avs script to encode. But I really want to learn how to :(

Ok tried June 17th 2002 version of ffdshow as well same problem with decoding it while playing back and also same problem loading up in VirtualDubMod afterwards but I can still scroll through and I get same shitty green stuff!

Now for my stats file from my 1st pass and also what settings I used maybe I goofed up somewhere to make it output like this or is it a decoder problem? I think encoder :p

Stats File
----------
iframes: 626
pframes: 138323
bframes: 15997
total frames: 154946

1stPass Settings Used
---------------------
MSP: 6 Ultra High
Quantization Type: H.263
VHQ: OFF
Max I-Frame Interval: 300
Min I-Frame Interval: 5
Checked: Qpel
Max B-Frames: 4
B-Frame Quant Ratio %: 200
B-Frame Quant Offset: 100
B-Frame Threshold: 0
Checked: DX50 B-VOP Compat
Credits Tab: I&P-Frame Quantizer 20

2ndPass Settings Used
---------------------
Quantization Type: New Modulated HQ (THIS MIGHT BE A PROBLEM)
Quantizer Restriction
---------------------
Min I-Frame: 2
Max I-Frame: 6
Min P-Frame: 2
Max P-Frame: 16

2Pass Tuning
Below I-Frame Distance: 10
I-Frame Bitrate Reduction %: 30

Curve Compression
Highbitrate Scenes: 0 >These Two could have been a problem!
Lowbbitrate Scenes: 0

Payback Proportionally!

Alt Curve Unchecked!

That's what I used fellas got it from somewhere in hear!
Honestly I don't know hardly anything about these settings except maybe a little that I understand! So I just want to know why I get this horrible green shit in playback? What went wrong? And if so what are the correct settings to used with the unstable builds!

Frogg

BoNz1
14th March 2003, 05:57
You should not use modulated quantizers and b-frames together. Use one or the other, otherwise you break mpeg4 specs. Not sure if this is the problem though. Try encoding a short clip with one of those things disabled and see if that fixes it.
EDIT: Just out of curiousity, how are you getting your video into virtualdubmod if you are not using avisynth? Are you using vfapi?

FroggSkippa
14th March 2003, 06:08
That's the weird thing m8 if I encode a short clip with the settings it works just fine :p

But bam I do a whole movie and it gets like this :p

I'm going to try and do a short clip again with same setting and see if it does it, and then a short clip again without modulated quants!

FroggSkippa
14th March 2003, 06:21
Originally posted by BoNz1
You should not use modulated quantizers and b-frames together. Use one or the other, otherwise you break mpeg4 specs. Not sure if this is the problem though. Try encoding a short clip with one of those things disabled and see if that fixes it.
EDIT: Just out of curiousity, how are you getting your video into virtualdubmod if you are not using avisynth? Are you using vfapi?

Yes I'm using VFAPI m8! I've used it before with Keopi's stable build with no problems at all and now I'm using with unstable as well!

BoNz1
14th March 2003, 06:37
I would get rid of vfapi to eliminate that variable and use avisynth2.5.1 beta here and mpeg2dec3 which you can find in the avisynth forum in one of the sticky pages, https://sourceforge.net/projects/avisynth2/ the easiest way to figure out how to use a avisynth script is to open the d2v file in GordianKnot and save the avisynth script. Take a look at this guide, http://www.doom9.org/mpg/d2a-mpeg2dec.htm for simple avisynth script creation.

Koepi
14th March 2003, 07:01
It seems your setup is messed.

Get rid of vfapi (like described above) and see if that helps the problem.

Koepi

FroggSkippa
14th March 2003, 10:22
Ok saweet thanx alot fellas I'm going to do that right now never was much a fan of vapfi I think it's time to update :p

Cheers,
Frogg

Will get back to you guys then on how my results come through :sly:

sysKin
14th March 2003, 11:23
Originally posted by BoNz1
You should not use modulated quantizers and b-frames together. Use one or the other, otherwise you break mpeg4 specs. Actually it's modulated quantizers which break mpeg4 specs. They always do. Therefore, they are not implemented to bframes part of the code.

N_F
14th March 2003, 12:51
@FroggSkippa

Heh... you had me really confused there for a while. I kept looking at the pic I thought you attached but couldn't see anything greenish... until I realised that wasn't an attached picture, that was your signature! :)

Rober2D2
14th March 2003, 13:48
I have had this same problem with Koepi's unstable versions since 09-12-2002 if I do one of the following things:

- Encode using Vidomi in YV12 Mode

- Encode using Virtualdubmod in Fast Reprocessing Mode (I suppose this one is your problem)

Koepi
14th March 2003, 14:45
when serving with vfapi (=RGB), you can't use fast recompress(=YUV).

Koepi

sh0dan
14th March 2003, 18:10
[edit] No - I was totally wrong ;) It wasn't related to the image size (unless it isn't 592x320).

FroggSkippa
24th March 2003, 08:40
Ok guys since then I've encoded 3 movies with avisynth 2.51, mpeg2dec3.dll and GKnot. And then load avs into VirtualDubMod :D

Everything works just fine, couple issues with GKnot but nothing serious. I want to eventually make my own avs script manually and not use GKnot. I tried it a couple of times with no success so far :p I'll keep stabbing at it though and will see what happens :D

Thanx for your help fellas and you to Keopi cause I really dig your build of XviD :D And to Sh0dan for Avisynth and anybody else I missed :p

Frogg

rudeboymcc
16th April 2003, 12:54
EDIT by Koepi: DON'T DO THIS! DON'T DOWNLOAD NIMO CODEC PACK, YOU MAY BE TEMPTED TO INSTALL IT - WHICH WILL IN MANY CASES RUIN YOUR SETUP. INSTEAD, HEAD OVER TO http://sourceforge.net/projects/ffdshow/ AND DOWNLOAD THE 11122002 VERSION (the real file is called 13122002 then).
-- End of EDIT

to anyone who has this problem there's a very easy way of sorting it out. firdst, download Nimo 50 build 9 (search in google), and then after installing, type this in the run box:

regsvr32 /u ffdshow.ax

works like a dream.

Mel Maconoo
16th April 2003, 22:20
i thought Nimo was bad..?

Koepi
17th April 2003, 05:37
Nimo IS bad, guess why we have a section of it's own in the sticky FAQ in this particular forum? I think it was question 15. Read the FAQ (forum rule 1, rudeboymcc).

Regards
Koepi

rudeboymcc
17th April 2003, 09:47
JESUS!! sorry guys. the reason i didn't read that FAQ is becuase i used the search function and i didn't look at what part of the forum this topic was in, but normally when i browse i do rread sticky's.

is Nimo that bad? what does the FAQ mean it's "evil"? i've had it for ages and i haven't had a problem with any avi making, or dvd ripping. anyone got an example of an evil it does to my system?

also, why does it say in the faq "happy reformatting and reinstalling your system"? surely i can just uninstall?