Great Inc, downloaded and testing (when was the last time I used other tool to calculate cropping and so...?).

I tried and loaded a MP4 of my own. It launches ffdshow to decode.
It doesn't recognize the AR: well it really says 4:3(?). The MP4 is 720x400 non-anamorph... I don't dare to ask: is it 4.3 or 16:9?
In FourCC it says ????.

I like a lot the new previewing window for scripts.
Congratulations.

We miss some options for loading standard scripts, adding new avisynth filters and so. But sure you've lot of things to be done, and this is just a hobby for your little spare time... thank you for your effort and generousity.

This just keeps getting better
Thanks Andrej

-kwag

Right, the std. WinAPI Routines cant recognise the AR or SAR/PAR informations. So the Appl. just can assume the such imports are simple PAR 1:1 nonanamoprh(4:3), so NO anamorph inputs in case of avi, mp4, mkv and wmv are supported.
BE SHURE that you select the right import option! Means in case of captured avis the "captured avis and d2v" ... and for common avis/mkvs/mp4s and wmvs the other "Common ...." import option.

FFdshow is launched cause internally Dshow is used for decoding the mp4/mkv/wmv sources via a temporal avs build which is loaded instead by the appl. including a "Directshowsource(...)" line Thats the trick which makes imports other than avis possible.


A "dream" would be to make PARanoia Modular, means diff. modules for avs handling could be integrated.
But maybe its better to keep PARanoia in its purpose said by its name. Other Stuff could be handled via separate utils where the readymade output of paranoia could be easely imported for further scripting or filter addings.
There is a LGPL based dll available called "Scintilla", a dll including very powerful textediting functions like auto braket highlightning, auto-text-fill etc etc etc. So a cool avs scripting editor can be done.

But maybe you could include such optimal scrips as

RemoveGrain()
Deen()

or the last one

LRemoveDust_YV12

and

LRemoveDust_YUY2

You can leave additional parameter for the user.

What do you think?

I dont support deen as its old, and beaten by much newer routines like the ones you quoted also above.
BUT! Even LRemovedust() would be an option, its very risky as it forces the user to have such filters in his avs plugins directory and we all know how many problems do occur if a user doesnt use the right removegrain.dll according to his CPU type. So I have first to find out a user-friendly solution before I do integrate these functions.

The first purpose of PARanoia was to be a comfortable resizing tool.
Of further add ons I already thought about as seen in the to do list, but that will be implementated if the core of the appl. is well beta-testet and almost bug-free.

What I suggest is to introduce three string that PARanoia will recognize in a loaded script, and will replace with the correct values :

PARANOIA_Crop
PARANOIA_Resize
PARANOIA_borders
(and may be PARANOIA_letterbox)

This way the user can provide the script he wants, and just have to replace his old crop/resize/border lines by these three reserved words.

If I understand you right, you want to go into paranoia using an already exisiting script? Why? Why dont you just first let the appl. do output a script incl. the resizing and the most needed commands where you add some specific routines afterwards?

Hey ! I don't ask for nothing, others do
I'm already used to copy/paste lines from FitCD, I can do the same for PARanoia. But people are lazy

You told that you won't support filters because it's not easy to be sure that people will have the correct plugin installed, that is why I suggest a way to support all plugins by letting the user to be sure that he can use them.

Thats an argument! Ill think about it

a very little BUG in 0.31B:

F3 is showing preview/save script instead F4 XD

Im just rewriting PARanoia where some nice addons will be included like cutting manually the borders using the mouse (as known from Vdubs cropping dialog). Also HDTV support will be given.

Till now I use a routine to access the specific dgdecode.dll or mpeg2dec3.dll directly for obtaining the Info and the image itself. Other sources will be accessed via a temp. avisynth script generation which is done in the background for obtaining info and imagedata.

Im thinking about dropping that direct dgdecode.dll or mpeg2dec3.dll access so also d2v sources will be read via a temp. avisynth script generation.
For the user it will make NO difference.

But my main intention is about DVD2AVI.! Im thinking about dropping the support of DVD2AVI. Its buggy, gots less features and for shure even not longer supported.

Does someone still use that old tool for generating d2v files?
If yes, is it just cause till now you even did not try dgIndex or is it REALLY a must to be compatible with some other stuff or for some other obvious reasons? In case of CQmatic etc. AFAIK its only needed for obtaining the movie length - which can be entered manually into cqmatic. - and Karl should give his nice appl. an update on this

Hi Inc,

Seems to be a long time since we read about you .
Concerning support of old dvd2avi, my opinion is that you should drop it, either poeple use it or not. If they need to use them, then they can provide directly an avs script.

I had a question for you : what is the internal diff between "open an avi-capture" (F1) and "open common avi" (F2) ?
I opened once a "common" avi (Divx) with F1 and the tool looped for ever once I pressed "Autocrop Sample". This puzzled me .

Beside this, a small request : can you please allow to press "Autocrop sample" even if the preview is playing ? (no need to press "pause" first...). Thanks a lot

Ideed. When I was online in here I primary took my time to read and last week I had some days of vacation in Fuerteventura - no big deal as I only spend 5 days on that "desert" island in a resort.

I also took my time getting into the new addons of the recent purebasic release as I want to get into these before handling again PARanoias sources.

Thats also my opinion. Why supporting outdated/superseded things by keeping them alive in newer uptodate apps.

If your source is a captured one, means you got the stream out of an own capture workout, then do choose that input option as it takes into account the cards specs, so no matter which resolution you did choose when capturing -> PARanoia will fix it.

The other option "Common avis" means regular PAR 1:1 avis (or mkv, mp4) like out of GordianKnot etc.

I think it would be better if the playback does not automatically start if the source is imported, so you can directly "autocrop the frames" or seek to a perfect frame sample for choosing that actual frame to be used for autocropping.

Why do you want to catch a frame for cropping when playback is in progress? Or did I catch something wrong?

Hi Andrej ,
Long time no seeing .
Say, I won't complaint if you remove DVD2AVI support from PARanoia even because since the begining I have always been a follower of DGMPGDec (previously DVD2AVIdg).
But in fact Calcumatic users could find it a harder task if they can't use DVD2AVI in order to get their movie length.
It would be wonderful if Karl could find some time in the near future to update Calcumatic and add DGMPGDec support .
Please Karl, oh please-please-please ?
That is, when you find some...*cough* spare time .
But in the mean time I think there is a workaround and I'll post it as soon as I have proof that it is working 100%.
Cheers buddy

__________________
Rui

No I don't want to catch a frame on the fly. I never use "Autocrop frame" but always "Autocrop samples". I just want to avoid to roll my mouse all the way down to the bottom of the screen to click the "pause" button after I loaded a source . But if you just remove this "autoplay", that's ok for me too

Just as I had previously mentioned, here is a workaround for people using DGMPGDec and Calcumatic.
http://www.kvcd.net/forum/viewtopic.php?p=125052#125052
That is, while Karl is taking care of the issue .
Cheers

__________________
Rui

I love your flash-guide ways.
Excellent initiatives Rui!

And I love your tools and scripts Andrej .
I just hope that my guides can actually help newbies to get everything going with the tools we use .
Cheers

__________________
Rui