Welcome Guest ( Log In | Register )


Important

The forums will be closing permanently the weekend of March 15th. Please see the notice in the announcements forum for details.

 
New Command Line Option Suggestion, Re-derive keyframe flags
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
levicki
Posted: Jan 14 2010, 06:08 PM


Advanced Member


Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07



Avery,

I often invoke VirtualDub from the context menu option (right-click on file, Open in VirtualDub) which I added manually to the registry.

I also often open incomplete AVI files with missing index block.

I would appreciate having a way to specify on a command line that a file should be opened with "Re-derive keyframe flags" option enabled.

The way it is now, I have to open it and then open it again using extended options dialog (or browse to the file which is somewhere deep in the folder hierarchy).

Would you consider adding a switch or perhaps you have another suggestion on how to do it?

Oh, and it would be cool if that dialog showing (in my case pointless) warnings:

user posted image

Could also be silenced from the command line.
 
      Top
squid_80
Posted: Jan 15 2010, 03:43 AM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



You could script it. I think the open string with "Re-derive keyframe flags" enabled looks like this:
CODE

VirtualDub.Open("file.avi","",0,"HAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAHkAAA==");

But I think there's a chance it's version dependant...
 
     Top
phaeron
Posted: Jan 15 2010, 04:44 AM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



That'll work for a while. I'll add the request to the feature request list.
 
    Top
levicki
Posted: Jan 15 2010, 07:06 PM


Advanced Member


Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07



QUOTE (phaeron @ Jan 15 2010, 05:44 AM)
That'll work for a while. I'll add the request to the feature request list.

Thanks Avery, script is not a solution because it requires injecting filename which would at least need a .BAT file and a temporary file for a script itself.
 
      Top
squid_80
Posted: Jan 15 2010, 09:29 PM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



Use the /i switch and VirtualDub.params[0].
 
     Top
levicki
Posted: Jan 16 2010, 05:57 PM


Advanced Member


Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07



QUOTE (squid_80 @ Jan 15 2010, 10:29 PM)
Use the /i switch and VirtualDub.params[0].

Thanks, will try that, but that still won't disable the warning and its messy.
 
      Top
squid_80
Posted: Jan 16 2010, 08:03 PM


Advanced Member


Group: Members
Posts: 594
Member No.: 13813
Joined: 22-January 05



You could always make the changes and compile it yourself.
 
     Top
levicki
Posted: Feb 6 2010, 06:35 PM


Advanced Member


Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07



QUOTE (squid_80 @ Jan 16 2010, 09:03 PM)
You could always make the changes and compile it yourself.

Yes, and repeat those changes each time the new version of VirtualDub comes out.
 
      Top
levicki
Posted: May 29 2010, 12:06 PM


Advanced Member


Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07



Avery,

Is there any update on the status of this feature request?
 
      Top
phaeron
Posted: May 30 2010, 04:17 AM


Virtualdub Developer


Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02



Uh, sorry, no progress... I've been really busy at work and not really in much of a VirtualDub mood lately.
 
    Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
9 replies since Jan 14 2010, 06:08 PM Track this topic | Email this topic | Print this topic

<< Back to VirtualDub Development Forum