AviSynth for CinePaint / Photoshop / PaintShop Pro??

[oldchicken]

Ive been using lbkiller to extract images from some avs files and i find it very usefull. I have a task that requires me to extract frames from thousands of avs files. Using lbkiller to manually grab these frames would lead to immediate carpal tunnel. So with my health on the line im begging and pleading for a solution.

Would it be possible somehow to perhaps call lbkiller from a command line and have it extract frames every X seconds or perhaps just every X frames? Perhaps the compression could be decided on the line as well. I figure that it would be awesome to be able to do this via a batch file. Since i only need 2 or 3 frames from each avs file this would work alot better than dumping all the frames out.

If anyone has any other suggestions please let me know, i have done alot of searching the boards and looks like this might be the only way.

Thanks!

[esby]

I'll think about adding command line argument & batch mode.


Since i only need 2 or 3 frames from each avs file this would work alot better than dumping all the frames out.

How long are your files, taking 2-3 frames as samples?
fixed position?


esby

[oldchicken]

Hi esby!

The files in question are on average 450 frames. The frames extracted are to be used as samples correct. As they are all different just nabbing 1 frame from each at the exact same position wouldnt be much use. I figure in the end i will have 3 images and choose the best 1. Hope this answers your q's

Thanks for the quick response!

[esby]

supposing they have all the same resolution & properties...
you could use avs
to put the files together,
add a overlay describing the filesource
merge them
do a selectEvery() to choose which frames
and load the result in lbkiller taking the shot on the avs file.

esby

I'm going to work now, so I can' do anything before 6-7 hours...
Supermarket are not really interessant, but I must live from that...

[oldchicken]

Im not sure i understand your solution. Im really kinda new to all this so if im misinformed please let me know.

Wouldnt that solution destroy the filename structure of the input?
I think {originalname}{frame#}{extension} would be best instead of {mergedavsname}{frame#}{extension}
Plus theres still the manual step of picking through the merged avs file.
In theory a quick batch would dump images in a dir then they could be picked through using an image viewer.

Supermarkets I used to work at one! A very motivational experience. :rolleyes:

[esby]

function source(string str)
{
avisource(str)
subtitle(str)
showFrameNumber(true)
selectevery(150)
return last
}



clip = source("source1.avs") + source("source2.avi")

return clip


will gives you an example of what I mean.

I'll probably have tomorrow a new version of lbkiller supporting multiples files & automated captures by frame number.

esby

[Karyudo]

@esby:

Some more questions about and ideas for the increasingly-awesome LBKiller:

- Where do the "hint" text strings in the .ini file show up when using LBKiller? I'm expecting maybe tooltips, or something in the status bar at the bottom, but I'm not seeing anything.

- Rather than having to cut-and-paste the AVS file that's displayed, could a "Save AVS File" option be added? I like to work by making changes in one source, then reloading a master AVS to check how the changes look in context. It would save me some time and effort to be able to quickly save the updated AVS, so that the changes show up immediately and (almost) automatically.

- It would be nice to be able to specify a directory for the location of captured frames, rather than them just going in the same directory as the .lbk file.

- I like that the scroll wheel acts to move forward and backward through frames. Could some more options be added like this? Say, maybe ALT + or SHIFT + various buttons or keys? Like maybe ALT + Enter Captures and Edits, if your default is set to Capture. Or maybe some way of toggling between edited/unedited pictures? There's a lot of potential to make the UI very flexible and shortcut-enabled.

- One or more menus in LBKiller have "OK / Annuler" dialog boxes. Maybe the more familiar "Cancel" is preferable? Various other error messages (which I found when I messed up some BMPs...) are also "en Francais".

- Could you explain the three "Change" buttons at the top right? These don't seem to do anything. Or do they?

- Could you explain the syntax of the info box near the bottom of the screen, with format "Frame 00645 [2586] (0:25.800) [none]"? I understand the frame number and the time, but what's the descending [2586] number? Is the [none] thing telling the user if that frame is being replaced? For replaced frames, what's the final [___] info telling me?

LBKiller is a great tool, and it's very cool to see you actively developing it! Please don't take any of my points as demands or harsh criticisms -- these are just minor things that I'd like to think will help make LBKiller even better and more polished!

[esby]

- Where do the "hint" text strings in the .ini file show up when using LBKiller? I'm expecting maybe tooltips, or something in the status bar at the bottom, but I'm not seeing anything.

hint shows up when you drag the box over a menu and waits usually.
hints are saved to the ini file, like caption, and can be changed...
The goal is handling linguistics settings in a future version.


- Rather than having to cut-and-paste the AVS file that's displayed, could a "Save AVS File" option be added? I like to work by making changes in one source, then reloading a master AVS to check how the changes look in context. It would save me some time and effort to be able to quickly save the updated AVS, so that the changes show up immediately and (almost) automatically.

I'll probably add the option.
When i started lbkiller(), I had a certain goal for it, which has been lost since, since luminance blocks are/were a specific problem of the divx 3.11 codec. Now xvid does not have such problem, and I am problably going to disable or switch disable some of the option linked to ecf generation.


- It would be nice to be able to specify a directory for the location of captured frames, rather than them just going in the same directory as the .lbk file.

I'll think about it.


- I like that the scroll wheel acts to move forward and backward through frames. Could some more options be added like this? Say, maybe ALT + or SHIFT + various buttons or keys? Like maybe ALT + Enter Captures and Edits, if your default is set to Capture. Or maybe some way of toggling between edited/unedited pictures? There's a lot of potential to make the UI very flexible and shortcut-enabled.

mmmm 'scroll wheel' = mouse wheel, I just can't remember putting code to handle it in it ;), so it must be a fair bug. :)
Now I am going to change / modify heavily the UI in the next days/weeks.
So I might add custom related shortcuts.
Using alt enter for a second 'choice' could work.


- One or more menus in LBKiller have "OK / Annuler" dialog boxes. Maybe the more familiar "Cancel" is preferable? Various other error messages (which I found when I messed up some BMPs...) are also "en Francais".

Some dialog box as you noticed are handmade...
Meaning they have no linguistic adjustment provided by the os.
Related dialogs are in french too.
Error messages like that are going to stay in french for now...
I am a bit sorry, maybe I'll hunt them in the code and translate them...
But the solution I see would be to associate those settings with an list of 'sentences', thus allowing to put them into a separate file for linguistic purpose.


- Could you explain the three "Change" buttons at the top right? These don't seem to do anything. Or do they?

They are part of the old UI linked to the lbk profile options.
Basically, each box should have been linked to an option,
and would have allowed to directly change the option.
option are info, ecf & stats right now.
I won't detail much these options, except that it is going to change in the future.
Stats are used when loading lbk produced by nandub ndy...for semi automated quality check purpose...
So the buttons are probably going to disappears.


- Could you explain the syntax of the info box near the bottom of the screen, with format "Frame 00645 [2586] (0:25.800) [none]"? I understand the frame number and the time, but what's the descending [2586] number? Is the [none] thing telling the user if that frame is being replaced? For replaced frames, what's the final [___] info telling me?

[2586] is the number of frames until the next scene change, (or something like that...). It is intented for editing samples containing an avi file structure, with keyframe & deltaframe..., I can't run the executable right now, but [__] is probably the detected frame structure associated... whether KF or DF KeyFrame, DeltaFrame, it is probably going to change too... For using vdub convention.

Now I think that I am going to try having lbkiller evolving into an NLE application for the next weeks to come... That might cause some UI changes, some internal structure changes, and some interresting features...

Feedback is always welcome, as I can't necessary see all of the problem myself, Maybe I'll put the project on sourceforge and use the associated specific boards, for bugs suggestion & feature request handling.


esby

[esby]

new version upped...

mainly multi file loading
and automatted screenshot / editing.

You might want to run first your editing program prior to launch batch edit this way.

esby

[Karyudo]

Originally posted by esby
new version upped...

[whispers] ...and it still says "1.8b"...!

[oldchicken]

Just tested out the new file looks very promising :)
The auto grab feature is nice, i think an option to grab a frame every X frames would be great here.
I see you added the menu item for command line options, im excited about that!
I will do some more beta testing if i find any bugs will be sure to post.

[esby]

[whispers] ...and it still says "1.8b"...!

yeah, i know...
it's what I got from packing source & release in 10 minutes...
before going to work...

About command line,
This is not really command line, but rather batch mode...
The menu item for command line option is here
for another purpose.
If you want to run an image editor than use a different syntax than Gimp or photoshop...
you can just specify the option before the filename and the option after the filename...
And the lines may be greyed... it does not means it is not supported ;) Just try clicking on the blank part.

I'll probably add True command line support in the future...
but not yet.



esby

Edit:

Here the right explanation for the [__] field...

[__] : no INFOECF action
[??] : frame marked for later check. It indicates usually a scene change if you did a scene change detection.

the other infos are ecf related... (nandub ndy...)
[KF] : frame will be a KeyFrame in the ECF generated
[DF] : frame will be a DeltaFrame in the ECF.
[SF] : frame will be a subtitle frame (or Suggested keyFrame).
That tells nandub ndy to encode this frame in a particular way, Mostly to avoid artifacts problem on subs.
Now it is somewhat not exploitable with xvid...
[CF] exists... but is has no use... it was for cloned frame... but i never implemented the idea in nandub ndy.

[oldchicken]

Ah i see thats cool :)
Doesnt quite do what i need yet but what it does do it does very well. Looking forward to future builds your plans for expansion soung good. Might be time for a new name though since hunting down those luminance blocks isnt what its all about anymore :)

[Karyudo]

I'm gonna go out on a limb here, and suggest something like "SBRoto" or "esbyRoto" or "AVIRoto" or "Rotor".

Or maybe "Rotoshop"?? (That's my favourite so far...)

Rotoscoping is the main point, so perhaps that should be featured in the name?

@esby:

Thanks for the info on the [___] field. I guess because I'm using a HuffYUV AVI, every frame is a keyframe, so I don't have to worry!

[esby]

new version upped... v.19b
- UI tweaks/clean
including the possibility to save to an avs file directly, whith the choice of using an avsi import (actual method) or creating a working avs file. This last case adds avisource('filename').lbkiller() at the end of the avs.

- version number corrected.
- some bugs corrected, one left but I cannot reproduce it('error' when loading the stat window).

Oh for the name I have an idea, but nothing in roto...
I'll drop the Killer part, since I don't like aggressive naming.
and I'll add a little n before LBK...
Since I plan to upgrade it to a non linear editor/encoder.
so it will probably be 'nLBK'

esby

@Oldchicken;
about your needs...
You can do the following.
edit grablist.ini
first line is number of frames to be captured.
other are the line number, one per line.
for example:

grablist.ini

4
0
150
300
449

and then select all the avs you need to shot
by holding the shift/ctrl button in the load menu...
You don't have to worry about frame position exceeding the end of the file, they won't be captured.

You can also use the following (it should be supported, but it's still untested)
grablist.ini

1
0;150;300;449

And finally:
0-99 can be used to capture the first 100 frames

@Karyudo:
I guess because I'm using a HuffYUV AVI, every frame is a keyframe, so I don't have to worry!
Well that can be applied to huff file...
Supposing you need the scene structure...
the number previewed will tell you in how many frames the scene will probably change...
it can be useful sometimes... supposed you did a scan for scenechange.
It is somewhat slow, but the information can be saved in the profile...

[oldchicken]

I have tried your instructions im assuming once i load all the files and set the frames to extract the next step is to perfom action on all frames.

Once i do this it extracts all the frames selected for the first file in my load list. My question is how do i get it to move on the next file in my load list and cycle through the rest of the list?

Maybe im just going about it all wrong let me know, thanks! :)

[esby]

Just keep the load list open, and double click on the next file...
basically all you have to do it clicking on the capture all frames from list, then double clicking on the next file to load.

I'll probably change that to get a real automatic mode.

esby

[oldchicken]

Ok thats what i thought i was supposed to be doing, its sort of semi automatic right now but we are one step away, cant wait for the true automatic mode :)

[oldchicken]

Im guessing this is a bug,
If you try to load over 27 files and then goto "show files to load" it only shows the first 27 files. This bug also pops up in the autograb frame menu as well.

Also the second method of listing frames in the grablist doesnt seem to work either. It will not print any frames except the first one in my tests.

[esby]

I've been working on v.20 since a while, I need to debug some options...

For the 27 first files, you should be able to go down with the keyboard... unless there is really a bug.

I reworked those menus heavily btw.

I think i'll have v.20 ready this night.


esby

[Wilbert]

@esby,

If you write a nice documentation page (about how to use this stuff + possibilities), I will add this utility to the faqs.

[esby]

Well, I am going to stop the developpement of this version.
So v.20 is probably the last version with major improvement.


I am going to restart from 'scratch' the project with some more updated objectives:

* Linear editing: Frame fixing, as it can actually do. Wether it is freezeframe or screenshots' editing via Gimp etc.

* Non linear editing: To allow easy trims, and concatenation of video
segments.

* Avisynth script / function handling: To allow the user to use custom avisynth scripts inside of the application.

* Encoding via avs2avi command line.

* Non linear encoding, or splicing, to allow partial encoding while keeping the other parts intact.


So I guess I'll have some time to write a minimal documentation for the lbkiller v.20


esby

[esby]

Lbkiller v.20 up

* Some UI changes...

* some bug fixes...

* automated screenshoting.

maybe I'll do a 20b to add an option in the framelist... ('*X' as each X frames)

esby

[oldchicken]

@esby this version looks great! I have a Q for you,

Does this version still use grablist.ini files? Because its not reading my old one. If not where do i enter a list of frame names? I have about 3400 entries and it would be easier to do it in a ini or text file do i have to use the ui to do it?

[esby]

yes it does,
it is located into the ini directory

you can also specify -L drive:\path\yourgrablist.ini while launching lbkiller.
The init format being
first line = number of entries
all the other lines, entries...
an entry could be whether a simple number, whether a range 5-50 or multiples items or range 5-50;3-40;
Spaces and ':' are allowed too as item separator.


esby

[oldchicken]

Ah i see its in a new dir this time, i was looking for it in the old place. I will now unpack new versions to their own folder.

I have been doing some testing and the weirdest thing is happening. Its not reading my avs files i load them and all i get is a black screen.

I had assumed that it was reading them properly since previous versions did, what i was concentrating on testing is the batch abilities. Batch mode via the gui is working though made me alot of nice black images ;)

I have verified that the avs work via media player and previous builds so whatever is happening is unique to this build.

What i have noticed is that the list still only allows so many frame number entries only 27. I am unable to scroll down the list any further it stops at 27 i have alot more entries than that. The grablist is also limited to 27 files in its list. Are you able to verify this is not a bug?

I will try out commandline mode now not sure what will happen there if it doesnt see the avs in gui mode but what the hay :)

[esby]

let me check that.

I'll add a quick workaround for your avs problem.

esby

[esby]

New version up.

v20b.

The problem you were talking of are fixed.

@oldchicken:
use 'workaround decoder' to check if it solves your main problem

@Karyudo:
There is now an option to change & save the basefilename (and location) used for screenshoting.

esby

[oldchicken]

Workaround decoder did the job for me got things back on track :)

The que is bigger but still not big enough for my job it goes up to around 331 now my grablist calls for 3687 frames :eek:

Im curious does the *X option work in this version? I think this would probably solve all of the troubles. Unless you can get the lists to go way up, not sure how practical that would be. Its a great idea, but im very biased :)

[Karyudo]

@esby:

LBKiller rules! I am seriously impressed by how far you've pushed LBK in such a short time. I'm sorta sad to hear you're not going to be developing it any further -- but of course I'm happy to hear you're going to do even more with nLBK!

I have modified the LBKiller.ini file to add quite a few hints, to correct capitalization consistency, to fix a few spelling errors, and to set the defaults a little more how I like them (editor is Photoshop; file format is PNG). Want a copy? I can e-mail it to you, or up it to your FTP or whatever. Just say the word...

By the way, I still can't get any of the hints to show up, ever! What am I doing wrong?

A few more things I can think of that might make nLBK (or a final, final release of LBKiller??) even cooler:

- Menu option to "Create .LBK from a directory of images". The other day (with v1.8) I had a corrupted .LBK file, and I had to manually edit it, which wasn't fun (don't forget the two Tab characters at the end of each line!). Of course I always had the directory full of PNG files, all labelled correctly...

- Shortcut key to "Skip to next frame replaced by IMG file". Or am I missing this, and it's there already?

- Shortcut key to "Toggle between IMG and AVI/AVS". Sometimes I'd like to see what I changed, or remove images I exported only for use as good source material to fix a damaged frame. Toggling would remove the frame from the .LBK file. It would be nice to be advised in the status bar that a "modified IMG file exists" for a given frame, but that it is not being used.

- "LBKiller.dll" AviSynth 2.5 plugin. I'd still like to be able to use the exact same .LBK file in both the standalone LBKiller and in an AviSynth script. Generating an AVS script is now much better than it was (thank you!), but it's still an extra manual step required, rather than just saving and closing like you'd do anyway.

- (Free?) scaling of the video window. I'm using LBK to look for (and eliminate) dust and scratches. This would be quite a bit easier if I could stretch the image to fill more of my screen, like VDubMod lets me.

- In situ editing of screen captures. I find that I have been using Photoshop's Clone tool with a brush size of 4 pixels to do more than 90% of the repair work on my 720 x 576 LD capture. If you add any tools at all to nLBK, add something like this first! Next thing would be to add Layering a lasso selection from the previous/next frame to the current frame. With just those two options, I think every single flaw in my video could be fixed.

Can't think of anything else at the moment. And please understand I'm only coming up with these crazy and demanding ideas because LBK is already able to take care of all the "easy" stuff!

I plan to work on a bit of a tutorial on How To Rotoscope Video Errors with LBKiller. If/when I get a rough draft done, I'll send it your way first. I'd have started already, but LBKiller keeps changing (and getting easier/better to use)...!

[esby]

- Menu option to "Create .LBK from a directory of images". The other day (with v1.8) I had a corrupted .LBK file, and I had to manually edit it, which wasn't fun (don't forget the two Tab characters at the end of each line!). Of course I always had the directory full of PNG files, all labelled correctly...

mmm edit -> show tables of edited frames -> scan directory for frames


- Shortcut key to "Skip to next frame replaced by IMG file". Or am I missing this, and it's there already?

Well you can use up & down.
which will seek to the next frame replaced or switched with an other image.


- Shortcut key to "Toggle between IMG and AVI/AVS". Sometimes I'd like to see what I changed, or remove images I exported only for use as good source material to fix a damaged frame. Toggling would remove the frame from the .LBK file. It would be nice to be advised in the status bar that a "modified IMG file exists" for a given frame, but that it is not being used.

I'll probably add something for the legacy version.


- "LBKiller.dll" AviSynth 2.5 plugin. I'd still like to be able to use the exact same .LBK file in both the standalone LBKiller and in an AviSynth script. Generating an AVS script is now much better than it was (thank you!), but it's still an extra manual step required, rather than just saving and closing like you'd do anyway.

MM that would mean a dll able to understand the lbk v3 format, which should not be difficult, and doing framefreezing & frame from img in a row.
Now I can't use the actual code to directly produce a dll, I'll rather directly code it in c++.


(Free?) scaling of the video window. I'm using LBK to look for (and eliminate) dust and scratches. This would be quite a bit easier if I could stretch the image to fill more of my screen, like VDubMod lets me.

I'll look what I can do, the problem is that you are shoting the displaying frame... So I don't know if I can zoom/unzoom without affecting the image size or resolution used for screenshoting.


- In situ editing of screen captures. I find that I have been using Photoshop's Clone tool with a brush size of 4 pixels to do more than 90% of the repair work on my 720 x 576 LD capture. If you add any tools at all to nLBK, add something like this first! Next thing would be to add Layering a lasso selection from the previous/next frame to the current frame. With just those two options, I think every single flaw in my video could be fixed.

I'll put it in the todo list for nLBK.
I can't say I'll do it or now.
I'd rather rely on gimp for that,
or just using the previous or next frames instead,
since the human eye won't be able to detect the changes.
(I've been doing that for 3 Hunter X Hunter episodes- nobody complained yet)


Can't think of anything else at the moment. And please understand I'm only coming up with these crazy and demanding ideas because LBK is already able to take care of all the "easy" stuff!

Well there are not necessary crazy.
I know how long it can be to edit this kind of stuff, so it's not very crazy to ask something better :)



I plan to work on a bit of a tutorial on How To Rotoscope Video Errors with LBKiller. If/when I get a rough draft done, I'll send it your way first. I'd have started already, but LBKiller keeps changing (and getting easier/better to use)...!

Feel free to work on any tutorial.
Well there won't be much changes now.
Probably a few possbiles bugs fixes or some little additions.
If you want to send me your ini files with the fixed capitalization,
I'll change the default settings.

esby

@oldChiken:

The * option works like selectEvery filter.

*5 will do a screeshot each 5 frames in fact it is defaulting to *5-1 )
*130-11 will do 11 sucessives shots each 130 frames etc.



@Karyudo:
I'll try to look on the 'hints' problem... but I cannot garantee any results.

[oldchicken]

Esby im really enjoying using lbkiller here are the results of my latest tests, I hope this helps :)

*(frame) works great on my shorter avs files but crashed during my longer avs file which is just all of the shorter ones being loaded as one. Doesnt seem to be any trouble with the avs file in media player.

*(frame)-(numberofgrabs) doesnt seem to work for me at all either it grabs every single frame of a file but *(frame) works just fine grabs all the frames.

Batch jobs seem to have some problems. It captures frames from only the first avs file in the list. But it will attempt to process the entire list. So the result is that it creates files named for each avs file i have in the list but they are all captures from the first file in the list. eg: 1.avs.1.jpg and 2.avs.1.jpg both contain the identical fram fetched from the 1st avs.

Also a stop button would be great, especially usefull when testing im having to kill the task to end the program. Sometimes i can just click the main window of the program and get an access violation which is pretty handy in stopping things.

So it works on one file but not on multiple files, let me know if you need more details but i hope this helps. :)

[esby]

So it works on one file but not on multiple files, let me know if you need more details but i hope this helps.
I assume you are using 'selection' or 'list' mode', right? (If that is not the case (using loaded) that's normal).

I'll look into these bugs...

esby

PS: Edit:
There was a variable corruption on a loop explaining that the 100*4 was not working properly (crashing).
Should be fixed in next version.

[oldchicken]

Yup i am using list mode, look forward to the new build excited as usual :)

[esby]

v21.rc1 (legacy version candidate) up.

changelog extract starting from the previously released version...

--DONE--* screenshoting is interruptable by ESC now.
--DONE--* Fixed issue crashing the application when a frames was physically deleted.
Added a state of deletedframe
--DONE--* Fixed issue(s) with multiples screenshots & basename
--DONE--* Verified that a profile will be reset each time the batch sequence is used.
Included base filename in the algo.
--DONE--* Fixed a bug with deleteItem of popupmenu of auto grabber.
--DONE--* UI: Edit selected entry popupmenu added

v.20c - bugfixes (not released)
--DONE--* Fixed up & down keys command skipping sometimes a frame when they should not.
--DONE--* Fixed number preview of the 'next key in file' (what indicates number of frames left before the next special one)
--DONE--* Fixed a problem with an old feature linked to mouse clicking on the image, while a non bmp image was the source of the image.
--DONE--* Fixed a bug in '*X-Y' (selectEvery) option of autograbber.


So if you are screenshoting and want to interrupt it, hold esc

esby

[oldchicken]

Works flawlessly in batch mode now very goood stuff here, you are great! And lbkiller has earned a permanent place on my hard drive! :)

I shall continue to test but so far i have nothing but praise!
:thanks:

[oldchicken]

I just thought of something obvious in batch mode missing its really the only thing i can think of. If we where able to specify an output directory that would be a great ui enhancement.

Also in the auto grab menu a refresh file or refresh video would be good for when changes are made to an avs file. Or does it matter? Im not quite sure on this one.

Its just about trivial but its the little things that make a program great :)

[esby]

Also in the auto grab menu a refresh file or refresh video would be good for when changes are made to an avs file. Or does it matter? Im not quite sure on this one.


Unless you are processing 'current' file...
the file is reloaded each time.
You can also force a reload by double clicking on it.
Beware that this mode will not take in account any change
you did in a lbk profile if you did not save it before.

Now if the avs was changed, the video will be obviously reloaded.

esby

I'll be adding a batch output directory option and some progress bars in the next rc.

[esby]

lbkiller v.21 rc2 up.



v.21.rc2 - legacy version candidate.
--DONE--* Now you can replace frames in the video by image by dragging the file on lbkiller while being at the correct position...
--DONE--* The filename loaded is now displayed in the application title (like in vdub)
--DONE--* Added drag & drop to autograbber form.
--DONE--* Added autoresize option when inserting frames (images) that are of the clip size for the avs generation
--DONE--* Completely removed luminance block basic correction option (mouse click on the picture)
--DONE--* Added resample option a bit like in vdub, at the difference that you can choose this resample ratio.
Please note that you can choose to capturate the frame when they are resized or not...
Avoid to 'chain capture' a frame unless you want to blur it.
--DONE--* Removed some non necessary codes that were slowing down the image updating.
--DONE--* Fixed vdub inherited scene seeking.
--DONE--* Added go start and go end of clip button.
--DONE--* Hint system should be working and diplayed in the last statusbar.
--DONE--* Replaced any showMessage (asking user interruption) by an entry in log form.
--DONE--* implemented force destination directory for autograbbing
--DONE--* implemented ProgressBars for capture mode.
--DONE--* added an option to permanently hide the nandub ndy related menu
--DONE--* fixed *properly* the 24bits/32bits issue.
--DONE--* added filename substitution in auto grabber when saving a profile
(that means 'toto.avi' becomes 'toto.lbk' if it is saved)


I might continue this version after all, since I cleaned most of the code that was disturbing me. But I'll have to change the structure for the next features I want to put.

This version provides two external avs filter, for the user convenience, bicublin (MarcFD) and simpleResize (TRBarry).
These filters will only be loaded in the avs generated if the they are actually used,
The usage being resizing when inserting image with different width / height than the clip ones.
UpSampling is if you use a smaller image,
DownSampling if you use a bigger image.

esby

[oldchicken]

Hi esby new candidate looks great, good to hear that you may possibly continue developing it as is.

Im trying out the new batch features im having some trouble with the force save path, would be nice if there was a way to select a folder. I tried double clicking on it and the choose folder dialog came up but didnt seem to work. I fiddled with it for a minute and got a path to show up but lbk isnt respecting the path it still outputs to the source directory.

Also when i try to run a batch now things seem to freeze up and it cant get pass the first file. This usally ends in my killing the process since i cant get a response and its no longer outputting files.

Looks very promising though nice creature comfort features here :)

[esby]

Im trying out the new batch features im having some trouble with the force save path, would be nice if there was a way to select a folder. I tried double clicking on it and the choose folder dialog came up but didnt seem to work.


Oh well, you just have to choose a file in the path you want, even if this file does not exist, and it will use the path corresponding to it.
That's a small 'hack' as I don't know how to ask for a folder...
This method works as far I know, even if it might seems disturbing at first glance.

There were two small bugs that I fixed,
- one linked with the non possibility to interrupt inside of a selectEvery. (I forgot to add the lines for interrupting it there)
- one linked to the file that was not loaded when it should in some situation, which may explain that the forcePath was not taken in account.

If you can check with v.21.rc2b

If you still have any bugs, feel free to report(including how to reproduce them).

esby

[oldchicken]

Everything looks good with batch processing, nice progress bars :)