Green Video Output

[mixt]

So I've given myself a crash course in video in the past couple of weeks and I'm still obviously a novice but I've got most things falling in line as I need it but there is one error that keeps coming up. Every so often I get videos that simply output as solid green. Most of the time I can make it work by using another program (e.g. it won't work in vdub but it will work in GIMP GAP, or it might work only if I don't send it through Avisynth), but sometimes the recorded file is just dead. It is rather frustrating to research it because all my searches direct to chroma-keying. The only lead I got is on an avisynth forum where it mentioned getting the display type from vdub or mediainfo (in my case YUY2) and manually telling it to avisynth such as...
AVISource("file.avi",fourCC="YUY2")
but it hasn't helped any.


On a different note my friends were making requests for various file types (for the sake of example I'll talk about .mp4), so I figured I would just apply the mpeg-4 codec and change the extension. This worked but it also works almost regardless of what I make the extension (.wmv, .mkv, .mov, etc), still under that mpeg-4 codec and without error. Is this normal? Could similar behavior be expected on other computers?

[poisondeathray]

So I've given myself a crash course in video in the past couple of weeks and I'm still obviously a novice but I've got most things falling in line as I need it but there is one error that keeps coming up. Every so often I get videos that simply output as solid green. Most of the time I can make it work by using another program (e.g. it won't work in vdub but it will work in GIMP GAP, or it might work only if I don't send it through Avisynth), but sometimes the recorded file is just dead. It is rather frustrating to research it because all my searches direct to chroma-keying. The only lead I got is on an avisynth forum where it mentioned getting the display type from vdub or mediainfo (in my case YUY2) and manually telling it to avisynth such as...
AVISource("file.avi",fourCC="YUY2")
but it hasn't helped any.


On a different note my friends were making requests for various file types (for the sake of example I'll talk about .mp4), so I figured I would just apply the mpeg-4 codec and change the extension. This worked but it also works almost regardless of what I make the extension (.wmv, .mkv, .mov, etc), still under that mpeg-4 codec and without error. Is this normal? Could similar behavior be expected on other computers?

post the mediainfo text information (view=>text)

you can't just change the extension , it has to be muxed into a different container properly

"mpeg-4" can indicate about 20 different things. e.g. mpeg4-avc part 10 is h.264 , mpeg4-asp part 4 is divx/xvid, part 14 is the container format ".mp4"

http://en.wikipedia.org/wiki/MPEG-4



EDIT:

Are you still talking about this topic: ?
https://forum.videohelp.com/threads/334278-GIMP-GAP-Green-Frames

Did you read the replies? You're probably dropping frames from inadequate I/O

Post a short sample that has "green frames" in one program , but decoded properly in another. You can use vdub (video=>direct stream copy) mark in/out and file->save as avi

[mixt]

post the mediainfo text information (view=>text)

This file will work if loaded directly into vdub but wont work frame-served through avisynth and won't open in window's media player.

Format                           : AVI
Format/Info                      : Audio Video Interleave
Format profile                   : OpenDML
File size                        : 2.63 GiB
Duration                         : 15s 100ms
Overall bit rate                 : 1 494 Mbps

Video
ID                               : 0
Format                           : YUV
Codec ID                         : YUY2
Codec ID/Info                    : YUV 4:2:2 as for UYVY but with different component ordering within the u_int32 macropixel
Duration                         : 15s 100ms
Bit rate                         : 1 493 Mbps
Width                            : 1 440 pixels
Height                           : 1 080 pixels
Display aspect ratio             : 4:3
Frame rate                       : 60.000 fps
Color space                      : YUV
Chroma subsampling               : 4:2:2
Compression mode                 : Lossless
Bits/(Pixel*Frame)               : 16.005
Stream size                      : 2.63 GiB (100%)

The audio is in a separate file that gets dubbed in.

you can't just change the extension , it has to be muxed into a different container properly

That is why it was confusing me. I was expecting it to flat out not work, or at least give me a compatibility error before opening. If it was not for the fact that I changed the extension myself I would never have guessed it. And I tested it with other files on my computer and those give the expected errors. Something about the recorded ones are allowing it.

"

mpeg-4" can indicate about 20 different things. e.g. mpeg4-avc part 10 is h.264 , mpeg4-asp part 4 is divx/xvid, part 14 is the container format ".mp4"

http://en.wikipedia.org/wiki/MPEG-4

The two I've been testing with are listed in vdub as "x264vfw - H.264/MPEG-4 AVC" and "Xvid MPEG-4"

Are you still talking about this topic: ?
https://forum.videohelp.com/threads/334278-GIMP-GAP-Green-Frames

Did you read the replies? You're probably dropping frames from inadequate I/O

Now that you mention it this might not have merited a new thread...

The green frame problem is the same, though it has become a broader problem. The duplicate frame problem seems to have fixed itself. I'm questioning at this point if I misinterpreted something and jumped to conclusions.

Post a short sample that has "green frames" in one program , but decoded properly in another. You can use vdub (video=>direct stream copy) mark in/out and file->save as avi

Hold on, file hosting is acting funny and I have to leave soon. I'll get it up as soon as I can.

[poisondeathray]

YUY2 (fourcc YUY2) is uncompressed and should frameserve with AVISource() . This uses VFW (video for windows) subsystem that vdub uses. In other words, when you use AVISource, it should give you the same results as opening directly in vdub, especially when pixel_type is specified

You can use other source filters that don't rely on VFW system, e.g FFVideoSource() or DirectShowSource() . FFMpegSource2 relies on libav framework , and DirectShowSource relies on DirectShow subsystem . WMP uses directshow system

Eitherway, they should all decode the same, yielding same results, because this is uncompressed Y'CbCr 4:2:2 video.

This file will work if loaded directly into vdub but wont work frame-served through avisynth and won't open in window's media player.

With the file loaded directly in vdub, if you use file=>file information, what does it say ?


If you zip it up, you can upload it directly here if <30MB or you can use a free hosting site e.g. mediafire.com, sendspace.com, many others...

[mixt]

Here we go. Earlier it wasn't redirecting me to the download link so I had no way of sending you the file. It is compressed into a 7z, if that is an issue I can do zip or try again with the full file.
http://www.filedropper.com/pcsx2

If they both use VFW then I would guess that avisynth's connection to it is having problems. I'll try a reinstall and see if that helps.

Frame size, fps (μs per frame):         1440x1080, 60.000 fps (16667 μs)
Length:                                 906 frames (0:15.10)
Decompressor:                           Internal DIB decoder (YUY2)
Number of key frames:                   906
Min/avg/max/total key frame size:       3111408/3111408/3111408 (2752867K)
Min/avg/max/total delta frame size:     (no delta frames)
Data rate:                              1493482 kbps (0.00% overhead)

Going through avisynth says almost exactly the same thing. It just shows a slightly lower frame size and lower data rate to compliment.

[jagabo]

you can't just change the extension , it has to be muxed into a different container properly

That is why it was confusing me. I was expecting it to flat out not work, or at least give me a compatibility error before opening.

Media Players are good at determining the real container even if the file is misnamed (by looking at the contents). But if you have a player that can't play MP4 files and you rename an MP4 file AVI, it still will not play. It might play if you remux the video and audio into an AVI container.

manually telling it to avisynth such as... AVISource("file.avi",fourCC="YUY2")

I got a green screen too. Using AviSource("PCSX2.avi", fourcc="VYUY") worked.

[mixt]

Media Players are good at determining the real container even if the file is misnamed (by looking at the contents). But if you have a player that can't play MP4 files and you rename an MP4 file AVI, it still will not play. It might play if you remux the video and audio into an AVI container.

I've seen that happen before. like if I make a wmv into an avi, WMP says "The file you are attempting to play has a file extension (.avi) that does not match the file format. Playing the file may result in unexpected behavior."

In contrast the avis can change video formats seemingly without the player even noticing. In fact I just found that the PCSX2.avi that I said didn't play in WMP earlier will work as an mp4.

I got a green screen too. Using AviSource("PCSX2.avi", fourcc="VYUY") worked.

Is there a way to figure that out or do you just guess if the one you're using doesn't work?

[jagabo]

I got a green screen too. Using AviSource("PCSX2.avi", fourcc="VYUY") worked.

Is there a way to figure that out or do you just guess if the one you're using doesn't work?

I just tried different YUV 4:2:2 fourcc codes until I found one that worked. Oddly, the output of AviSource() was RGB24.

[banman]

Hi, I'm not sure if I'm in the right tread here.



I use AVISynth along with VirtualDub and TMPGEnc encoder to convert old VHS tapes to mpeg2

files.


I was experiencing green screens/flashes appearing in my AVI capture conversions. Very

similar symptoms in your discussions here.

Sometimes the scenes instead of being green screens/flashes they were unusually messed up

frames of the capture.

This was very a frustrating situation for me.

When I left AVISynth as a frame server out of the conversion process the problem

disappeared. However,I didn't have the correct de-interlacing. Not ideal.

I was capturing using VirtualDub's internal capture facility,which is excellent.

I had used VirtualDub's segmented AVI capture (producing several files of approx 1.9 GB).

This allowed me longer capture times. My capture card is old and not to stable & I have to

use it under Win98.

I went back over what I was doing. I found the problems were occurring where one AVI file

ended & the next started. This issue doesn't show up when using VirtualDub alone.

Using AVISynth to frame serve seems to have issues adjusting to the file crossover.

All versions of AVISynth & VirtualDub I used seemed to have the same problems.


I re-saved the original segmented AVI capture to one long concatenated AVI file (VirtualDub

has this facilitate in the File Options Tab). Taking care to set the Video & Audio Tab option

sections as Direct Stream copy.

Windows 98 FAT32 file system won't handle >4GB files.I used a NTFS file system under XP.

The resulting AVI files were over 4 GB.

Using AVISynth along with VirtualDub and TMPGEnc encoder to process this long file (under an

XP OS) the problem of green screens/flashes appearing & unusually messed up frames of the

capture stopped.


I know it seems complicated, it was the only way I knew around my green screens / flashes

issue.



I hope my experience helps someone.