|
|
| Cela |
| Posted: Apr 26 2010, 06:33 PM |
 |
|
Member
Group: Members
Posts: 18
Member No.: 27492
Joined: 26-April 10
|
Sorry! I am not a curious developer but a curious user (since many years).
Please allow me to contribute two feature requests:
1. Cue-list driven append segments from specified avi(s)
Let a cue-list (cues.txt) with a sequence of selection definitions
sfos efos ifv
where
int sfos ... start frame # of selection
int efos ... end frame # of selection
int ifv ... input file version # (1 ... v1.avi, 2 ... v2.avi, ...) to use for the selection defined by this cue-line.
example:
0 413 1
413 472 2
472 1739 1
1739 1764 2
1764 1977 1
...
drive the execution as if it were an interactive user input:
>> Open an New avi "appended.avi" which is empty.
>> Open for Read the input text file 'cues.txt'
>> DO for all lines of input text file 'cues.txt'
>>> Read line
>>> Do what it asks to be done:
>>>> Define selection from sfos to efos
>>>> Write as AVI "v<ifos>.avi" (example: v1.avi for ifos=1)
>>>> and
>>>> Append from AVI ""v<ifos>.avi"
>>> EndDO
>> EndDO
internally, without actually really writing to and reading from disk, of course.
At the end the final result, the New file "appened.avi" is filled with all cues from the cue list, should be ready to be written by the user by the 'Save as AVI...' command in 'Direct stream copy'-mode.
Please find more details in http://forum.doom9.org/showthread.php?p=13...363#post1393363 especially summarized in posting #5
Expected benefits:
Cue-list driven editing would be very useful for many applications, especially for 'Best-of' compositions of different takes of the same recording.
If I knew how to attach a text file I would attach as an example the cue.txt that consumed a good part of my spare time in last week's evenings (and nights) to manually do this best-of based on the originally recorded avi and an avisynth processed duplicate where duplicate frames were substituted by an MVTools interpolation (see http://forum.doom9.org/showthread.php?p=13...871#post1391871 #1).
2. Please show "Saving frames..." during 'Save as AVI...'
(1) Before 'File > Save as AVI...' we can see the selection frame numbers in the info area. 
Example:
Selecting frames 199-200 (1 frames)
(2) During 'File > Save as AVI...' we can NOT see the selection frame numbers any more. 
(3) To let us see what selection region we are saving (for better quality assurance!):
(4) During 'File > Save as AVI...' let us see what we are in the process of saving!!!
Example:
Saving frames 199-200 (1 frames)
(now this part is empty or filled with a general tool tip)
(also see http://forum.doom9.org/showthread.php?p=13...72#post1394972)
I recently posted these two feature wishes in the doom9 forum, but I am not sure if my posting will reach there the right VirtualDub experts to get a fair chance to be considered for soon implementation, which I would desperately need asap.
Please let me know if these requests have a chance to be impleneted in some near futute or if I run into open doors and I merely have overlooked that these features are already implemented.
Please feel free to ask for more details. If needed, I also could upload some example data and screenshots of my interactive user procedure to rapidshare.
Thanks!
Cela |
|
| Cela |
| Posted: Apr 29 2010, 11:06 AM |
|
|
Member
Group: Members
Posts: 18
Member No.: 27492
Joined: 26-April 10
|
Using what I learned by examples in thread
http://forums.virtualdub.org/index.php?act...=ST&f=5&t=18547
and reading VirtualDub scripting language reference, v0.7, the only reference I found, I tipped a toe into the wide ocean of the VirtualDub scripting. Now, I think I know a brute force workaround to accomplisch by VirtualDub scripting what I asked for in Question 1. Cue-list driven append segments from specified avi(s) But I am still strongly convinced that an intrisic feature addition would be a much better solution and should be added.
Regarding my second feature request show "Saving frames..." during 'Save as AVI...' I am almost ashamed how simple the implementation must be for a developer after having seen VirtualDub.SetStatus(...) scripting command. Therefore, because of its importance for improving the options for quality control, to display a final control information of what exactly we are going to save, when we click Save, IMHO it should be implemented ASAP! |
|
|
