You can input YUY2,YV12 or RGB32 to TMPGEnc-here's how!!

[mgh]

Download Radlight Filter Manager -extract in new folder-run exe
click on plus sign next to DirectShow Filters- select Color Space Converter-adjust setting as shown

click the set value button-close-reboot and you can load any colorspace avisynth file into TMPGEnc-have checked all three of above by putting convertto...() as last line.

[celtic_druid]

But then it just gets converted back to RGB24 yeah? and probably AVISynth does it faster.

[mgh]

My TMPGEnc was accepting only yuy2 input from avisynth -it was not accepting rgb input via avisynth
Till i increased the merit of the color space converter, TMPGEnc was not accepting rgb input via avisynth.
You can do it via registry-the radlight tool is a small utility for changing merits of various codecs in registry etc painlessly so that direct show will use codec of your choice.
e.g if you have more than one mpeg codec you can decide which one will be used by direct show by changing the merit
You can also resolve codec conflicts with the radlight tool.

[celtic_druid]

I know how directshow works. I am just saying that you don't really gain anything by say feeding it YV12 if it is just going to be converted anyway. Where as if an encoder can process YV12 then you gain speed and quality by staying in the same colourspace throughtout the conversion.

[adam]

This just saves you the step of having to add the converttorgb24 line into your avisynth script. Either way its still getting converted to RGB before it hits TMPGenc, regardless of what the source is.

This would be really good though if it were either a faster or higher quality conversion than what avisynth does. Its definitely worth looking into, but I suspect avisynth is much better at doing this conversion.

[mgh]

I repeat-pl. read my post properly before replying-my TMPGEnc was accepting only yuy2 input and refusing rgb input.
So I would have been extremely foolish to put a convertto rgb line in avisynth.
I needed a converttoyuy2 line in avisynth at the end to feed it to my TMPGEnc.

[celtic_druid]

What version? Because I was under the impression that v2.5.x only handles RGB24. So that would mean that if it didn't previously accept RGB24, that your RGB24 is being converted to something else and then back again.

By default I don't think it opens AVISynth scripts via directshow anyway.

TMPGEnc Express I think can process in YUY2. Once again by default I think it would handle AVS files via its avi file reader and not directshow.

[Abond]

My older TMPG version (12h or 12j don't remember) opens avisynth scripts without any conversion lines. What I have - XviD latest and ReadAVS.dll registered to TMPG. Why it is so I don't know exactly. I think XviD or DGDecode decode YV12 to make it acceptable to TMPG (also even DVD mpeg2 files through avisynth script - d2v) and ReadAVS makes possible for TMPG to accept decoded frames from avisynth.

[mgh]

My own version is 2.5 series but pretty old- haven't bothered to update
My own understanding was mpeg is not encoded to rgb
I did these exercises because i thought something was wrong with my TMPGenc-even now the avs files load fastest with the converttoyuy2 line at the end.

[adam]

All versions of TMPGenc only accept RGB input and only output mpeg to YUV. I was assuming that you were mistaken when you said your TMPGenc was accepting YUV and not RGB, since this is impossible. I think it is more likely that your YUV sources were being converted to RGB without your knowledge, and your RGB sources either weren't actually RGB or were not accepted for other reasons.

[mgh]

Nothing is impossible-i repeat i needed to put converttoyuy2 as last line in avs if colorspace wasn't already yuy2. I could use avs only with yuy2 output.
I do not know the reason. Now i can use converttoyuy2,converttoyv12 or converttorgb32-all three work.

[adam]

Yes you can use all three because they get converted to RGB in the end via directshow. Like I said, your problem was related to something else. TMPGenc does not support YUV input at all...period. It is impossible, because that function simply does not exist in the encoder. It doesn't exist in most other encoders either.

Don't get me wrong. I'm not trying to trivialize your advice. Alternatives are always nice. But I am trying to clarify that this method will not, in fact, let you input YUV sources into TMPGenc. Nothing will do that until the program is modified to accept other than RGB sources. Yes your footage is leaving avisynth as YUV, but its getting converted back to RGB before it gets to TMPGenc, as all YUV sources are.

Also, be careful which convertto commands you use. Using your method, if your source was RGB than you would be going RGB->YUV (via avisynth) then YUV->RGB (via direct show) then RGB->YUV (via TMPGenc). You want to avoid all of these conversions if possible. Its best to just leave an RGB source RGB unless you need to use a YUV only filter.

[mgh]

Again and again you guys are telling me to input rgb to my TMPGEnc-it was not taking it. Now i do not need to put any convertto line at the end. TMPGEnc wil take whatever color space it wants.
I put specific convertto lines only for checking that TMPGEnc will accept all inputs.
I also avoid unnecessary color space conversion. The avisynth 2.5 filters that i use need yv12-the line i needed to put at the end was converttoyuy2 not converttorgb-now i don't need to put any line.

[celtic_druid]

Try converttoRGB24() and resetting TMPGEnc's VFAPI settings so that the script isn't being opened via dshow.

[adam]

mgh, I'm sorry if I did not adequately explain what I was talking about.

TMPGenc accepts input via its VFAPI plugins. VFAPI ONLY operates in the RGB colorspace. Any non-RGB source loaded into TMPGenc will first be converted to RGB as it is processed through VFAPI. Using your method this conversion will be performed by direct show filters. In my opinion, it is probably faster and higher quality to do the conversion through avisynth first, but either will work.

I understand that you loaded an RGB source into TMPGenc and it did not work. What I am telling you is that there are a billion and one reasons why it might not have worked other than the fact that it was RGB. Perhaps you ran a YUV only filter in your avisynth script. That would prevent you from frameserving that file into any encoder, because it kills the frameserving right there at that spot in the chain. If you haven't already, I suggest recreating such a script and playing it in media player. If there is any error or incompatibility then you will get a message telling you which line the problem is in.

Whether you realize it or not, those YUV sources that you successfully loaded into TMPGenc were in fact converted to RGB first, behind the scenes.

I will just say this one final time. TMPGenc only supports RGB input. You can either convert to RGB before feeding the footage into TMPGenc, or you can let VFAPI do it instead, but the conversion is inevitable. Please before debating this point further do some searching on this issue. TMPGenc's RGB limitation is widely documented.

[midnightsun]

mgh, if you're using avisynth 2.5.x then converttorgb will NOT work with tmpgenc because converttorgb actually means converttorgb32 (see avisynth documentation on this very matter), not converttorgb24 which is the colorspace tmpgenc accepts. Try what celtic_druid said above:

ConvertToRGB24()

and reset the vfapi settings.

[mgh]

I had tried all including rgb24-yuy2 was the only one working.
Anyway,is there any advantage in using avisynth instead of the direct show filter for conversion-am not seeing any speed gain or quality gain advantage for avisynth.
TMPGEnc accepts vdr files which are rgb24-so definitely it should have accepted my avs files with converttorgb24 as last line but it didn't

BTW-problem could be specific to some 98 SE systems-i do not use my XP except in emergencies-checked a friends' PC with 98 SE-same problem was there as well.
Am going to be away for a few days-will check on my XP and report back after that

[adam]

I'd say there is always an advantage to avoid using direct show filtes for anything. They are intended to be used for playback, not for processing with the intent to encode. Simply put, they are not very reliable. If they work that's cool, but I'd recommend trying to get avisynth to work first.

vdr files are not limited to rgb24. They are just the loading files used by Virtualdub for frameserving, so they can be used to pass on any type of data that Vdub can output. I believe Vdub can output RGB8, RGB24, RGB32, YUY2, UYVY, or YVYU.