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.
Code:
LN Movie Length Script desc
----------------------------------------------------------------
01 Superman 120m mySuperman fist ever encode
02 Superman 120m mySuperman bla, bla, bla
03 Blue Streak 133m vhelp.122102 .
04 Sharks Machine 122m vhelp.120102 by vhelp
05 Sharks Machine 122m kwag.020103 by kwag
06 Phantom Menace 188m kwag.kvcd.352x240v1 352x480 better
You could setup a database structure like:
Code:
Type
MS_LibStruc = record
LN: integer;
MoveName: string;
Length: integer;
Script: string;
Desc: string;
end;
Var
myLib: MS_LibStruc
f: file of MS_LibStruc
.
.
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