Boulder, I do think you used the "Open Regular avi-file" Import option?

As you can see above, if I do set PARanoia to your Cap.Card environment and want to have a 704 output, it even doesnt crop the height and scales to 704 (kkeping AR) but just padds from 696 to 704 and keping the height in case of 696 sources which is the correct way.

So I do think theres a Problem in the MCI API decoding routine in case of your source, MCI Playback uses vfw and surely PICVideo comes with vfw decoding support.

Do you also let PicVideo decode your mjpeg's? What happens if FFdshow does decode them, ... same Output in PARanoia?

No matter if FFdshow is the en or decoder for mjpeg or PicVideo or even mixing .... in my cases the output and Framecount is ok.

No, I used the capture avi option. I just noticed that choosing regular avi fixes the display issue.
Yes, PicVideo decodes the stream. If I use ffdshow, the stream works like it should so it seems that the PicVideo decoder isn't delivering the goods here However, the framecount issue still remains.

And that causes the appl. to assume a source at PAR1:1 as you can imagine

Seems something is odd in your "PicVideo mjpeg" decoding routines, which PicVideo Vers. do you use? I still got the vesion before the first 3.x release, so Im still at 2.x as I dont like their updated C.Space output rgarding avisynth where I would always had to use the Pixel_Type="YUY2" option in Avisource()

Did you try latest FFdshow mjpeg encoding option when capturing?
(then you also should let FFdshow do the mjpeg decoding)

It beats all others as testet in a comparison by Ligh at Gleitz:
http://forum.gleitz.info/showthread.php?t=24071
(Its german but as germany more and more do use english verbs *lol*
But anyhow .. here's Babelfish's output:
http://world.altavista.com/babelfish...hp%3Ft%3D24071

I've used PicVideo v3 but I'll try ffdshow's MJPEG the next time I capture stuff. That comparison should have been posted at the English D9 as well as I'm sure it would interest a lot of people there. The bad thing about ffdshow's MJPEG is that it's slower than PicVideo. My scripts are already slow enough due to LTSMC

Slower? Really? In my case almost 1:1 (maybe again a cpu instruction set related issue ).

Yep, so much new stuff has been born in the scripting sector duing the last month's/weeks ... Id really like to try out these too ... but the magic word is "time"

Oh, I probably misread a bit. The performance LigH states the encoding time, not decoding. Nevertheless, I'll give it a go next time. Actually I've been waiting for a good quality competitor but have been a bit afraid to use ffdshow's MJPEG for the reason that I apparently need DirectshowSource (or do I?) to decode it.

As Avisynth uses vfw when using avisource() you have to enable the mjpeg decoding in the vfw part of FFdshow. Also do disable PicVideo in its dialogue so FFdshow is forced to decode mjpeg from there on.

OK, I'll try that. I actually thought that ffdshow supports VfW encoding only.

@incredible,

I found a problem in the information display of PARAnoia.

If I use a non-standard resolution avi (like I tried to use a capture avi of my camera phone) which is very small. The info displayed on screen is cut, I could only see the Source information, most of the target information was cut due to the small Screen area of the video.

I guess the same would be for if you pick up a trailor video for lets say Star wars, since they also use small resolutions.

Is it possible for you to extend the Information display beyond the video display screen area ?????.

The source/target info box is already shown using a very small typo, so I guess I cant reduce its size. But that infobox is just a "bonbon", so the main importand values can be seen in the gadgets on the left side.
In your case just switch the onscreen info off.

I do think trailors in mini resolutions arent purposed to be resized to high resolutions - these are just for PC watching purposes, ... but anyhow if you want, just switch the box off.

Yes, but the Source/Destination mu's, frequency, DAR and PAR value can only be seen in the Video frame and not outside it, maybe you can make is appear over the GUI, just like floating on top of it.

What is suppose to happen when you press "Preview AVS script"?
When I press it; a window opens kind of transparent, and then nothing else happens...
Are you supposed to have a player installed, that will play the AVS script or is it something internally?

-Anerboda

Its should give you avisynth script to be used in your encoding, simple, but something is wrong or you havent selected the correct parameters

Anerboda,

the "preview" (means the avisynth script button itself) only works if a source is loaded and by that automatically a calculation internally has been made.

So the "preview" Button in the avs section does show the resulted avs script using windows API for Playback.
It seems that the MCI API sometimes does take 1-3 sec. till the preview starts.

What system do you use? Win98?, Win2000?, WinXP (SP1?, SP2?)

@Inc

I'm on win XP SP2...

I just tried again and waited 2 minuts, and nothing happens exept the transparent window, and then it just quit and close...?

-Anerboda

What happens if you "save script" and open that saved script in Vdub i.E. ?

It plays fine...

Vdub ver 1.6.3

-Anerboda

A few Q's Anerboda ....

a) What type of colorspace is given out of the resulting avs:
YUY2, YV12, RGB?
(check it by applying info() at the end of the script in the scriptwindow)

b) Which codec is used in your system to decode "that" avs script resulting bitstream-Colorspace?

c) Of what kind of source youre talking about: d2v, avi, captured avi?

Thanks


@ All

Someone else suffers from that issue?

YV12

How do I find this information?
If it's under fileinformation i Vdub, it says the decompressor is "ffvfw MPEG-4 codec".
What would be the optimal decoder for this?

.d2v

-Anerboda

ffvfw MPEG-4?
You should try to make XviD your YV12 main decoder.
Try to uninstall FFdshow and (re)install XviD.
Now see if you still run into problems.
I quit using FFdshow because of some issues just as the one you are complaining but with other tools instead of PARanoia.
Cheers

__________________
Rui