Run MovieStacker, then after you select all your filters, click on "Full screen editor" and change the GripCrop line to read: GripCrop(320, 172) and save your script

That's all

Edit:
BTW, I have to update the PocketPC templates to use the new Q. Matrix

-kwag

I will keep my eye open.

Hi mauddib..


SUGGESTION #1
---------------------
I finally made it here w/ my suggestion.

Ok, this is what I propose to improve script layout. It's not much,
but it does work for me a lot.. especially when I am trying to
read my OWN scripts.

If you could use variables in at least just one area.. the
directory (or folder) names, where a user would normally keep their *.DLL
files, that would be great. For example, when I first installed your
app, I installed it in a folder, in a folder, in a folder etc. By the
time, I got started to run your MovieStacker, and got to a point
that it would create the AVS scripts, my directories or folders took
up most of the Script's window space/area. Now, normally, one would not
use such LONG directiries/folder names, but sometimes, this IS un-avoidable.
I couldn't see what DLL's were being used etc. It was a pain to have to
scroll over, to see them. And, I didn't want to resort to opening up in
Full-Screen view (you icon) whenever this happened. Now, I can't say how
this effects others here, as they may have a few folders deep, while others
may not, or whatever the case, but if you could..

A - Example: (old)
------------------

LoadPlugin("C:\W98\DESKTOP\VIDEO INSTALLS\17 (APPS) - MOVIESTAKER V1.1.1\MOVIESTACKER\Filters\MPEG2Dec.dll")
LoadPlugin("C:\W98\DESKTOP\VIDEO INSTALLS\17 (APPS) - MOVIESTAKER V1.1.1\MOVIESTACKER\Filters\Sampler.dll")

AviSource("D:\011803.5th_d2v-vfapi.avi")
BicubicResize(320, 368, 0, 0.6, 47, 0, 626, 480)
AddBorders(16, 56, 16, 56)

.
.
.

SUGGESTION #2
---------------------

B - Example: (NEW)
------------------
txt_dir="C:\W98\DESKTOP\VIDEO INSTALLS\17 (APPS) - MOVIESTAKER V1.1.1\MOVIESTACKER\Filters\"

LoadPlugin(txt_dir + "MPEG2Dec.dll")
LoadPlugin(txt_dir + "Sampler.dll")

AviSource("D:\011803.5th_d2v-vfapi.avi")
BicubicResize(320, 368, 0, 0.6, 47, 0, 626, 480)
AddBorders(16, 56, 16, 56)
.
.
.

Notice how LONG Line A is. But, now notice how SHORT and EASIER Line B
is, and how clean the script is.

Another suggestion.. I haven't tested MovieStacker yet w/ AVI
files. I'm not sure if it was designed to be used w/ it - - is it user
friendly for AVI files ?? ..those that were CAPTURED, that is ??

If so, another suggestion I have is, that you incorporate the built-in
script to generate scripts to handle MULTIPLE AVI files. I have such,
in my script, and all I do, when I want to change to another AVI project
is (while my script is still opened) change a segment number, save, and
I'm ready to go. I do LOTS of captures w/ my ADVC-100, so I have many
AVI files w/ incremental numbers, i.e.,
100.05.00.avi
100.05.01.avi
100.05.02.avi etc.

For the above, I use a variable and concatenate the above in one shot.

Now, when I want to change to another AVI file project, all I have to do
is type of the increment number (which happens to be 05) and replace with
whatever my next number would be, i.e.,
100.06.00.avi
100.06.01.avi
100.06.02.avi etc.

Note, w/ segmentation, the above would actually look like this in an
AVS script:
100.05.avi
100.05.avi
100.05.avi etc.

Notice how the 00, 01, and 02 were dropped off. That is required.

If you need more detail/explanation, just ask. I use this route above,
routinely, every day. And it has NEVER failed me yet for any of my ADVC-100
captured.

SUGGESTION #3
---------------------
Note, for AVI captures, you could have a Toggle i.e.,
[x] D2V / AVI ..or something like this.


SUGGESTION #4
---------------------
hmmm... ok, I'm ripping, stacking.. but I don't like what I have so far..
So, I think I'll re-rip again, but w/ other parameters.. hmmm... would be
nice if you had a speed button point to my Smartripper app. and, by
pressing this so called button, before launching Smartipper, MovieStacker
could "pass" my script's *.D2V file from the script source showing in the
window. ie, AviSource("D:\011803.5th_d2v-vfapi.avi")** and THEN
launch Smartripper. Smartipper would open w/ my (above) video now displaying
and I'm happy, and have a smile on my face, and oh.. yeah.. I revise or
make some other quick change, and then proceed to re-rip that same
AviSource("D:\011803.5th_d2v-vfapi.avi") file, saving as the same
name (works for me) and when I'm finished, I close down Smartripper and
continue messing w/ tweaking MovieStacker.. follow me so far ??

** I meant for AviSource("D:\011803.5th_d2v-vfapi.avi") to be used via
DVD2AVI. ..that it would be launched w/ above file (per AVS script)

I don't know, but maybe you (and snollygoster) could benefit these
additions/features inside your apps ??

SUGGESTION #5
---------------------
Also, if you add in another TAB that opens another box for storing those
movies a user Stacked (i mean) fitted on ONE cd (like a database) and
a user (newbie too) could just click a selection and BOOM !! ..as Kwag
said elsewhere, just Rip, Stack and Encode !!
Below is an example of a layout for a library file, but can be changed in
(strickly hypertheticle) orientation:

Note, you may have to enlarge your browser window, else some text may
rap to other line, distorting actual view.

You could setup a database structure like:
So, in the example above, a user cold click on LN 04, and do a RSE of
Sharky's Machine.. testing out someone elses experiences, or
comparing theirs to your, or just backing up a movie, but that is
based on another user's experience or recommendations, ie., Kwag's
This so called Library could be an on-going compilation of all the
users here on this FORUM's, expeirence. Maybe once a week, a "latest"
list could be D/L'ed into the database (based on user updates via this
FOURM [if a thread were to be created for just this event]) and opon runnig
MovieStacker, this list (or Library) would be loaded up (by default)
or by user control via a Load button.

Any further questions, just ask. If someone else understands what I'm
suggesting (and likes too) and I'm not available to answere just yet,
please feel free to jump in and answer/suggest


Ok, I've taked enough. . . sorry for the long post.
Well, it's 2:28am, and I think that's it for now.. so enjoy.

Thanks all.
-vhelp

PAL Presets would be nice, Moviestacker seems to be a palcist hehehe

Hi andy!
This was quoted from the first page of this thread:

@vhelp

1.) About long folders names:
Hey, do you really read all that "LoadPlugins" !?
I was thinking in put all them in a separated file...
But I will think about using a variable to store the directory name.

Now I want to make one suggestion for you.
Why don't you install MovieStacker in the root directory, or even put you "VIDEO INSTALLS" in the root directory. This way you will get a much cleaner script.

You will change from this
LoadPlugin("C:\W98\DESKTOP\VIDEO INSTALLS\17 (APPS) - MOVIESTAKER V1.1.1\MOVIESTACKER\Filters\MPEG2Dec.dll")
to this
LoadPlugin("C:\VIDEO INSTALLS\MovieStacker\Filters\MPEG2Dec.dll")
or even this
LoadPlugin("C:\MovieStacker\Filters\MPEG2Dec.dll")

edit: I forgot to say that you can also move the filter dir to the root (like c:\AvsFilters)
and then just point the "filter directory" setting to it. Your script will be much clean and elegant.

2.) About AVI support.
Yes, you can use MovieStacker with AVI files.
The only difference is that instead using "Mpeg2Source" it will use "AviSource".
I understand when you said you use a variable to concatenate all your segmented AVIs. But I loose you when you said that you drop off the 01, 02, 03, etc...

3.) About all other suggestions.
They are really good/interesting. But I have many other simpler changes that I think are more urgent. Not to mention the bug fixes.
I wrote your suggestions down but I'll wait a little more when MovieStacker gets more mature.

Hi mauddib..

1)
>> Now I want to make one suggestion for you.
>> Why don't you install MovieStacker in the root directory, or even
>> put you "VIDEO INSTALLS" in the root directory. This way you will
>> get a much cleaner script.

Installing MovieStacker where I did was purely out of wanting
to give your app a test run. I will probably install it elsewhere
later (perhaps where you suggested)


>> I wrote your suggestions down but I'll wait a little more when
>> MovieStacker gets more mature.

No problem. remember, they were just some suggestions, that's all.

2)
>> I understand when you said you use a variable to concatenate all
>> your segmented AVIs. But I loose you when you said that you drop
>> off the 01, 02, 03, etc...

Ok, let me try and be clearer here. Remeber, this works w/ AVI
captured files, but not *.D2V files.

AVI SEGMENTATION GUIDE:
---------------------------------
Below, is an working example of one of my scripts (partially) but
demonstrates the use of multiple AVI files in your scripts (segmented)
Once you've quickly studied it, you'll WANT to (and will) USE IT,
instead of the 01.avi + 02.avi + 03.avi ...
As this wont work effeciantly.

So, use the code snip below:

Ok, assuming you use the above in your script..

Your source is multiple AVI files that you captured w/ your
new capture card (or DV card) i.e., below, is your actually
captured AVI files (segmented if used by vdub or avi_io)
6.11.01.avi
6.11.02.avi
6.11.03.avi
6.11.04.avi
6.11.05.avi
6.11.06.avi
6.11.07.avi
6.11.08.avi
6.11.09.avi
6.11.10.avi
6.11.11.avi
6.11.12.avi
6.11.13.avi
6.11.14.avi
6.11.15.avi

When you want to use the above AVI files in your AVS script
effectively, you would enter (first line) in your script, but
w/out the last digit (ie, 6.11.01.avi)
Note the BOLD number. This is our index number,
hence, our segments. Always finallize your AVI's w/ a '.'
before your .avi ie, xxx.number.01.avi

Also, notice how the line above is only used once, and there
is not multiple of all those AVI files concatentated together
It's very clean. Sorry, so far, this does not work for *.D2V
sources.

Ok, a little discussion on the 6.11.01.avi (or AVI) file nameing
convention.
This naming was just for demonstration purposes. Also, when I
am capping many TV snips, I don't want to cap over my filename,
ie, most apps default to "capture.avi". With my number naming
convention, you just increment the first two digit.. ie, 6.11
Example, when I'm capping, I'll just increment the 6.11 to
a 6.12, and then my next cap will be 6.13, till I either reach
6.10 or 6.99 or whatever, then the next day, I'll increment the
first digit and start again. Example, 7.01, 7.02, 7.03 etc.
till I reach 7.10 or 7.99 (whatever I decide at the time)
Like I said, I do LOTS of capping w/ my ADVC-100. Sometimes, 5 min.
and other times, 18minutes, etc. etc.

Just remember, when using in your AVS script, 6.11.01.avi, don't
forget to drop the last digit .01 !!

Ok, so I've done LOTS of captures today.
Tomorrow, I will have increatemented my counter as thus..

The reason why I don't just re-use the numbers in my capture projects
is because I don't always delete the files right away, or I just
don't have the time to work w/ those I did previously captured.
This way, I can just continue capping (remembering to increment the
numbers) I do this every day, so it comes naturally to me.
Now, for someone who does ONE capture a month or week, this naming
convention won't really matter. But, for those that do MANY multi
capture testing and stuff, this WILL work great.

Let me know if you still need more details.. I'lll walk you through
the process.

-vhelp

Now I got you!
Thanks for the explanation. Everything was very clear!
Btw... clever file naming convention.

Hi mauddib and everyone..

>> Btw... clever file naming convention.

I came up w/ this simple naming convention becuase the old way
of saving AVI file (naming them, that is) was too combersome..
ie, "capture.avi" or "capture.01.avi" etc, etc.. this doesn't
help me logically, that is, it doesn't give me an "ordered" or
chronelogical feel, when I'm doing MANY avi captures. i can't
be bothered with actual filenames. Its just better to index the
filenames in numericle order, so that I don't acidentally go over
those that I did.

I use DVIO and my cap device, as you already know, if the ADVC-100.
.. no framedrops, and no audio sync issues. Excellent color and
frame/field quality from just about any source. I've done some VHS
(becuase, I do MANY VHS sources) I'm still debating on. At the moment,
I much prefer the DC10+ card for ALL my VHS projects. I pretty much
have it down to a science w/ using special "filter-chain" (VHS cleaning)
and am pretty satisfied w/ my results.. but I know I can do better. So,
I'm still working on the final encoding quality issues for VHS sources
using "filters"

Anyways.., I haven't just yet, installed the latest AVIsynth version,
but I will give a go today or tomorrow (weekend) I like doing most of
my work and things on the weekend.


>> The only difference is that instead using "Mpeg2Source" it will
>> use "AviSource".

Oh, I don't use AVISource.. I use segmentedAVISource(x) instead.

And, as far as those "long filenames", I'm sure they may come up in other
situations, and that's why I use the variable ie, "X" I could
have used a more meaningful name, but I was shooting for minimal space
and/or typing - - in other works, it worked for me.

>> 3.) About all other suggestions.
I feel the same.. that they are good (but anal too) but they work for
me (or would, if they were implemented)

I didn't mean to overload you w/ all those suggestions in my previous
response to you

Well, let me get back to some more reading, then on to my VHS project
I was fiddling w/ late last night - - working on balancing filters for
noise handling.

Have a good evening.
-vhelp

Will there be support for Gripcrop(), Gripsize(), Gripborders()?

That's already supported in MovieStacker

-kwag

Smoochie3, was done!


do you download the new MovieStacker?

It's a warm hearted forum here, isn't it

I heard somewhere in other forum novices with "funny" questions will be asked "Is there a hospital near you", hehehe

Omega

hey..........Omega,
shhhhhh, .......don't talk to nobody....stay in silence....it's a secret!

but,.........some members here are







not me,of course

I thought i had the newest version. I'm at work right now, so I'll have to check when i get home. I must be blind!


Edit: I found it!

Is there any way to make it so when you change something in the scipt--like checking or unchecking the box for a certain filter, or changing the resolution--it wont reset all the default values for all of the other filters?

Did that make any sense?

Thanks.

No!

MovieStacker saves all settings for all filters every time you exit the program. And it's not supposed to reset the default values of any filter.
Please, explain what's happening.

OK, lets say i load my d2v file and i check all of the filters i want to apply, but i dont like the default value of a filter so i change it. Then maybe i realize i selected the wrong filter, so i uncheck the filter, when i uncheck the filter every filter is reset to the default value even though i had just changed it to the value that i wanted.

Like letter boxing. When i select letterbox, the default vaule is:

Letterbox( 8, 8, 8,8 )

but i want:

Letterbox( 0, 0, 8, 8 )

But then when i add another filter to the script the Letterbox goes back to

Letterbox( 8, 8, 8, 8 ).

See what i mean?

Now I got you!

All filter settings in MovieStacker are supposed to be done clicking on the name of the filter. This will bring up a window where you can adjust the filter the way you want. When you hit the OK button the settings will be saved and the AviSynth editor updated with the new settings.

Every time you "check" or "uncheck" a filter, the avs editor is updated with the filters you select and the saved settings for these filters. So, if you want to manually edit the script do it as the last thing before you save your script, because if you change anything... all your manual alterations will be lost.

I gotcha!

OK, well then as a requested option... would it be possible to add a letterbox editing option so you can set the default to Letterbox( 0, 0, 8, 8 ) or Letterbox( 0, 0, 16, 16 )....etc..