|
|
| phaeron |
| Posted: Oct 30 2010, 09:57 PM |
 |
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Well, there's three reasons why I don't do that. One is that it would remove the impetus for improving the input plugin API for third party plugins. The second is that the improved driver wouldn't be usable with older versions of VirtualDub. The third is that my release schedule for VirtualDub sucks as it is and it's a lot easier for me to push out a revised plugin than to rev the entire program.
|
|
| levicki |
| Posted: Oct 31 2010, 02:58 PM |
|
|
Advanced Member
Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07
|
| QUOTE (phaeron @ Oct 30 2010, 10:57 PM) | | Well, there's three reasons why I don't do that. One is that it would remove the impetus for improving the input plugin API for third party plugins. The second is that the improved driver wouldn't be usable with older versions of VirtualDub. The third is that my release schedule for VirtualDub sucks as it is and it's a lot easier for me to push out a revised plugin than to rev the entire program. |
If you kept the ability to build both the plugin and the built-in version from the same source-code, you could update both at your leisure.
Impatient people could then download the plugin which would override built-in version until you release another version of VirtualDub with updated built-in plugin.
Another option would be to remove ASF plugin and just show the error message if the Directshow input driver is not installed.
|
|
| phaeron |
| Posted: Nov 3 2010, 09:49 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
That brings up another problem, though: there is currently no way to disable an internal plugin or filter. That's fine for filters since you have to manually add them, but it's not fine for input plugins since they all participate in the file detection process.
|
|
| b-vigilanT |
| Posted: Nov 22 2010, 10:34 PM |
|
|
Newbie
Group: Members
Posts: 1
Member No.: 29137
Joined: 22-November 10
|
Hello, sorry for the newb question, but I can't seem to get this plugin to work.. I extracted the DShowInputDriver.vdplugin file into C:\Program Files\VirtualDub-1.9.10\plugins\ and I still can't open .mkv files I am getting "The file n is of an unknown or unsupported file type." error. What am I doing wrong? Help, please.
P.S
I hope I provided enough info.. I am using the latest version of VirtualDub and I have ffdshow tryouts revision 3416 installed. |
|
| phaeron |
| Posted: Nov 28 2010, 11:34 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Try changing the file type filter drop-down on the open dialog to the DirectShow input driver. If that works, then it's a file type detection issue and File > File Information is your next stop. Otherwise, you're probably missing a Matroska splitter -- some players have this built-in, so the DirectShow driver won't see one unless you have installed it separately.
|
|
| ale5000 |
| Posted: Dec 13 2010, 11:38 PM |
|
|
Advanced Member
Group: Members
Posts: 1114
Member No.: 22180
Joined: 30-September 07
|
Can you please add version info to the plugin?
This will make easier to check (outside VirtualDub) what is the version what I have on the pc.
--------------------
New VirtualDub forum
VirtualDub AIO (All-in-One installer for VirtualDub and plugins)
Codec Toolbox RS (A tool to read/change merit of codecs and many other things)
Input plugins for VirtualDub / ACM codecs / VFW codecs |
|
| Superb |
| Posted: Dec 29 2010, 01:10 PM |
|
|
Newbie
Group: Members
Posts: 2
Member No.: 29470
Joined: 29-December 10
|
Any chance to see a x64 binary for v0.8? 
Thanks in advance! |
|
| ale5000 |
| Posted: Dec 29 2010, 04:26 PM |
|
|
Advanced Member
Group: Members
Posts: 1114
Member No.: 22180
Joined: 30-September 07
|
The same .zip in the first post contains both the 32 and the 64 bit version.
--------------------
New VirtualDub forum
VirtualDub AIO (All-in-One installer for VirtualDub and plugins)
Codec Toolbox RS (A tool to read/change merit of codecs and many other things)
Input plugins for VirtualDub / ACM codecs / VFW codecs |
|
| Superb |
| Posted: Dec 29 2010, 06:20 PM |
|
|
Newbie
Group: Members
Posts: 2
Member No.: 29470
Joined: 29-December 10
|
| QUOTE (ale5000 @ Dec 29 2010, 04:26 PM) | | The same .zip in the first post contains both the 32 and the 64 bit version. |
Oh, I see now. Wonderful! Thx! |
|
| dloneranger |
| Posted: Jan 4 2011, 01:02 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
Is there a chance of better source code 
The current one is missing bits out eg .sln, project files, resource.h, resource.rc etc etc
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| levicki |
| Posted: Jan 11 2011, 01:12 PM |
|
|
Advanced Member
Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07
|
I would appreciate to be able to see which filters are getting used in the graph.
Sometimes an application I install adds its own decoders for some formats (without me being aware of it) so decoding of videos opened using DirectShow input plugin in VirtualDub stops working.
I have a hard time figuring out which particular decoder is overriding the one I want DirectShow input plugin to use.
What is worse, both VirtualDub and AVISynth DirectShow components pick the wrong decoder while GraphEdit and Media Player Classic Home Cinema pick the correct decoder. |
|
| dloneranger |
| Posted: Jan 11 2011, 02:08 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
| QUOTE | | What is worse, both VirtualDub and AVISynth DirectShow components pick the wrong decoder while GraphEdit and Media Player Classic Home Cinema pick the correct decoder. |
Can't say I've ever seen that, apart from the differences you see on an X64 OS when using 32 and 64 bit software
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| phaeron |
| Posted: Jan 12 2011, 05:14 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Apologies, I was not aware that the source code archive was incomplete. I've re-uploaded the latest 0.8 source with the missing files:
http://www.virtualdub.org/beta/DShowInputD...ver-0.8-src.zip
You will need the VirtualDub source to build it, since it uses the system library.
|
|
| dloneranger |
| Posted: Jan 12 2011, 09:32 AM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
Thanks
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| levicki |
| Posted: Jan 22 2011, 01:15 PM |
|
|
Advanced Member
Group: Members
Posts: 167
Member No.: 22605
Joined: 13-December 07
|
| QUOTE (dloneranger @ Jan 11 2011, 03:08 PM) | | QUOTE | | What is worse, both VirtualDub and AVISynth DirectShow components pick the wrong decoder while GraphEdit and Media Player Classic Home Cinema pick the correct decoder. |
Can't say I've ever seen that, apart from the differences you see on an X64 OS when using 32 and 64 bit software |
Well I did, and I am still trying to figure out why VirtualDub uses wrong decoder. Any help would be greatly appreciated.
All video software used is 32-bit on a 64-bit OS.
|
|
