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.

Pages: (26) « First ... 5 6 [7] 8 9 ... Last » ( Go to first unread post )
Ffmpeg Input Driver, Experimental driver based on ffmpeg libs
« Next Oldest | Next Newest » Track this topic | Email this topic | Print this topic
travisk
Posted: Aug 29 2013, 10:08 AM


Newbie


Group: Members
Posts: 4
Member No.: 37053
Joined: 29-August 13



I've continued development of the FFmpeg Input Driver and made a new version 0.8.

ChangeLog
========
- Upgraded to current versions of ffmpeg - avcodec-55, avformat-55, avutils-52, swscale-2.
- Minimized usage of deprecated features in ffmpeg.
- Added support for planar audio formats.
- Added support for 32-bit audio samples.
- There's tentative support for multichannel, but Virtualdub hangs when fed multichannel audio by an input plugin. So for now, multichannel is down-mixed to stereo as before. See Below.
- Fixed a bug that caused garbled audio and occasional crashes near the end of playback.
- Split the sources to make them more manageable.
- VS2012 project files.

Edit [Sep 1 2013]
============
I've uploaded release 0.8.0.2 with following changes
- Implemented full support for multichannel.
- Fixed a memory leak.
- When opening a file with the plugin, if you select "Ask for extened options after this dialog", you get the following options for audio
-- Downmix Audio - if selected, downmixes multichannel to stereo (off by default).
-- Limit Audio To 16-bit - converts 32-bit audio source to 16-bit samples (off by default).

Note that virtualdub has some limitations when dealing with multichannel or 32-bit source audio:
- Some audio compression codecs do not accept multichannel or 32-bit samples as input.
- Virtualdub menu Audio->Conversion does not know how to mix multichannel down to stereo, or convert 32-bit audio to 16-bit.
- Therefore, above options in "Open video file" were implemented to convert to stereo or 16-bit if necessary.

Binaries: FFInputDriver_0.8.0.2_bin.zip
Sources: FFInputDriver_0.8.0.2_src.zip

Regards.
 
     Top
Abrazo
Posted: Aug 29 2013, 07:10 PM


Advanced Member


Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10



Thank you very much for creating an update of this inputdriver.

Little correction please :
The subfolder "fldlls" needs rename to "ffdlls", if not we get "An exception occurred in module 'KERNELBASE'."
 
     Top
Abrazo
Posted: Aug 29 2013, 08:30 PM


Advanced Member


Group: Members
Posts: 775
Member No.: 28995
Joined: 5-November 10



In the meanwhile I received a private mail that the correction has been made.
Tested via new download.
Rename to "ffdlls" confirmed by this post.

Thanks again.
 
     Top
travisk
Posted: Sep 1 2013, 06:15 PM


Newbie


Group: Members
Posts: 4
Member No.: 37053
Joined: 29-August 13



I've uploaded version 0.8.0.2 with some improvements. See my previous post for details.
 
     Top
raffriff42
Posted: Sep 2 2013, 01:08 AM


Advanced Member


Group: Members
Posts: 384
Member No.: 35081
Joined: 25-June 12



Nice! This has been my favored input method for some time, and now suddenly (AFAIK) there's support for UT Video 4:2:0 codecs!
 
     Top
travisk
Posted: Sep 2 2013, 11:55 AM


Newbie


Group: Members
Posts: 4
Member No.: 37053
Joined: 29-August 13



QUOTE (raffriff42 @ Sep 2 2013, 01:08 AM)
> suddenly (AFAIK) there's support for UT Video 4:2:0 codecs!

UT Video is supported by current avcodec. To get a full list of decoders, get the command-line version of ffmpeg from Zeranoe and run 'ffmpeg -decoders'.
Also, when opening a file with the plugin from Virtualdub, going to File->File Information shows you the codec details.
 
     Top
L.H.V.F.
Posted: Sep 3 2013, 09:23 PM


Advanced Member


Group: Members
Posts: 49
Member No.: 28822
Joined: 19-October 10



Private Messages copies:

QUOTE (L.H.V.F.)
Hi, @travisk

I have saw that you are making a good work in developing and in resuming of the stopped development of the plugin by raythe0n. One thing that would like and that you could do, is put all your developments on a dedicated Server, for archive the same, and at a place where this never expires (Sharing sites has a time limit for hosting the uploaded files, as MediaFire), or that one day it will be desactivated. Thus, since that the developer "@raythe0n" had released all the previous plugins and source codes at the Google Code, could you put all developments, including the source codes on a appropriate and dedicated site, as the "SourceForge.net", for example? This would be very usefull, because never would repeat the server choosed by "@raythe0n", and would go permit a place definitive for the Project, with the right of a Bug Tracker. Previously on a sharing site I had hosted the previous versions of the binaries (not the sources), that you have did before.

Note: Good work you are making, but since the "@tateu" forum member already had tried to correct the current issues of the previous developments, He never have released publicly the same, because the API of the FFmpeg was changed, and this could infringes the License possibly. I would like that you go talk your developments with the "@tateu" forum member, because He already have developed a fix for the most common issues of the Project of the "@raythe0n" developer, but He never went public your developments.

QUOTE

The FFMpeg dlls that I compiled are built with enable-nonfree so I can't redistribute them.  I'm out of town this weekend but I can recompile FFInputDriver using the latest FFMpeg dlls from http://ffmpeg.zeranoe.com/builds/ early next week.

I also fixed issue #10, https://code.google.com/p/ffinputdriver/iss...es/detail?id=10 (it was a 64 bit int truncation error) and could easily fix issue #9, https://code.google.com/p/ffinputdriver/iss...ues/detail?id=9.


Edit: Nevermind, I can't post a build with updated FFMpeg dlls, audio doesn't work because they changed the audio decoding API.



Reference Thread:

http://forums.virtualdub.org/index.php?act=ST&f=7&t=20025&st=75

Do you agree with these ideas for the file hosting, following the same steps that "@raythe0n" forum member had did previously?

Waiting your reply.
Thanks for the attention.

Best regards,
L.H.V.F. .

QUOTE (travisk)


tateu claimed in his post that he fixed an integer truncation problem and "can easily fix" some other bug - but he never uploaded any fixes or anything else - so I have no idea what he was talking about.

I fixed a couple bugs in the audio handling that I found.  Haven't looked at the video handling at all.

There is no licensing issue because the dlls I uploaded are from Zeranoe.

I'm not putting the code at public source control.  The files at mediafire can be there for years.  I've had other files on mediafire for years.




Hi to Everyone

What you of the Unofficial VirtiualDub Forum thinks about the decision of "@travisk" of not want to go publicly also for development your plugin updates, and not continue the Google Code hosting, or a similar dedicated server as "SourceForge.net", because this last is shared for a Community of developers?

The "fccHandler's Mirror" surged because a necessity of storage and keep the latest developments of him unlimitedly, but the FFmpeg Input Driver could use SourceForge.net for only host the Project, in an organized form, and as was being done by "@raythe0n" developer forum member at the "Google Code" in keep all the sources and versions stored in the same.

In Doom9.org Forum, for example, is recommended in the case of submit a sample, to use MediaFire.com, but for Project hosting there is some other factors that may interfere in that decision, as the time limit, that one day can expire some source code or version of the plugin. The fccHandler's site also had the lucky of be copied in snapshots of the "Wayback Machine", not the same with sharing sites.

Reference:

http://forum.doom9.org/showthread.php?t=96362

Edit:

QUOTE (L.H.V.F. @ Jul 13 2011, 01:52 AM)
Hi, raythe0n

[...] I suggest that you keep all versions of your plugin stored, for these possible problems.[...]


In the case of occur a possible regression, or if some sample media not work as before, or for the user be able to download a version of the plugin that works better, would be very usefull if it was mantained all the versions developed including the source codes and these files being thus stored unlimitedly, to one day, if some user need a previous version of the plugin, can download without any limitation in life time of the uploaded files, as dedicated servers for development.


Thank reply.

Best regards,
L.H.V.F. .
 
     Top
-vdub-
Posted: Sep 4 2013, 04:40 AM


Advanced Member


Group: Members
Posts: 613
Member No.: 27087
Joined: 24-February 10



A bit crazy to place the files on any file-server such as Mediafire. When it is not know how many people can download or access Mediafire. For last six or seven years I could not access Mediafire at all, only this summer has it started to work again. Who knows for how long or how many other people were also affected the same over the years. This itself tells you how bad such file-servers can be. All old links I wanted to download years ago none of them work all links are dead

Doom9 makes sure members use file-servers in case the file are not GPL or illegal to save their asses. If as Travisk says There is no licensing issue because the dlls I uploaded are from Zeranoe. Then there is no reason not to use Sourceforge.net or similar as a permanent place for the files and source code released. Just as RaytheOn has done when the FFMpeg Input Driver project started using http://code.google.com/p/ffinputdriver/downloads/list as a repository and permanent location for all files
 
    Top
play32
Posted: Sep 24 2013, 09:21 AM


Advanced Member


Group: Members
Posts: 43
Member No.: 23178
Joined: 4-March 08



travisk, thank you so much for taking over the development of Ffmpeg Input Driver.

Since Virtualdub doesn't currently support multichannel or 32-bit audio, I was wondering if you could set the "Downmix Audio" and "Limit Audio To 16-bit" options on by default, or perhaps add a "Save options as default" button in the extended open options dialog (similar to what fcchandler did in revision 4.1 of his Mpeg2 plugin -- the plugin reads the settings from the registry), in a future version?

It'd greatly help when you use full processing audio mode and you have to process many files with multichannel or 32-bit audio.
 
     Top
Michaelusa
Posted: Sep 27 2013, 04:32 AM


Member


Group: Members
Posts: 20
Member No.: 22512
Joined: 28-November 07



I'm using the latest versions of both VirtualDub and the ffmpeg input driver plugin and Vdub is crashing at a certain point.
Is this the proper sub forum to report the issue or is the Testing / Bug Reports sub forum a more appropriate choice?

Regards, Gideon.
 
     Top
play32
Posted: Sep 27 2013, 10:17 AM


Advanced Member


Group: Members
Posts: 43
Member No.: 23178
Joined: 4-March 08



With 0.8.0.2 on Vdub 1.9.11 (and unlike the WMV plugin by fcchandler that overrides VirtualDub's restriction -- added in v1.3d -- concerning ASF files), we get the "ASF files are not supported" error message when trying to add a ASF/WMV/etc. file IF we use drag/drop OR the regular "open all types" (though *.asf, *.wmv and the likes are on the list).

Switching from "open all types" to "FFMpeg supported files" and selecting the file does work, though.
 
     Top
trodas
  Posted: Oct 9 2013, 11:51 PM


Advanced Member


Group: Members
Posts: 88
Member No.: 22291
Joined: 22-October 07



Using Windows 2000 SP4 and VirtualDub 1.10.4 I wanted to try out this plugin, because fccHandler MKV plugin fail to detect audio in MKV AC3 file, so the result had no audio data at all...

At as soon, as I copy the FFInputDriver.vdplugin into plugins32 directory, with the subdir ffdlls of course, then VirtualDub on start come with this message:

user posted image

...and there is no way to choose any FFmpeg plugin from the open box dialoque. Obviously the function is missing on W2k and all I can do is to ask, if that could be added, so the plugin will work on Windows 2000 too.

Thanks!


(ended up using DirectShow input driver, but it give only half second or so of the audio in the end... sad.gif )

--------------------
"It is dangerous to be right in matters on which the established authorities are wrong." - Voltaire
...just keep folding, just keep folding... :) my config - my caps
 
         Top
play32
Posted: Oct 16 2013, 02:09 AM


Advanced Member


Group: Members
Posts: 43
Member No.: 23178
Joined: 4-March 08



With 0.8.0.2 on Vdub 1.9.11, we get a "The source video stream uses a compression algorithm which is not compatible with AVI files. Direct stream copy cannot be used with this video stream." error message when trying to use direct stream copy with a file handled by Ffmpeg Input Driver.

This isn't the case with fcchandler's plugins, where a direct stream copy is achieved successfully (with FLV, MKV, MOV, WMV, etc.).
 
     Top
dloneranger
Posted: Oct 16 2013, 05:07 AM


Moderator


Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07



That's correct, it doesn't
Fcc handlers plugins decode the container and pass the video/audio streams to virtualdub for decompression, which is why they need vfw codecs to decode as well
This and the directshow plugin decode the video/audio by themselves and pass uncompressed video/audio to virtualdub
There is no 'video/audio stream' for virtualdub to copy, and if it let you it's just be a huge uncompressed file anyway

It's not a bug/problem, it's just how these two plugins work

--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3
 
    Top
play32
Posted: Oct 16 2013, 10:29 AM


Advanced Member


Group: Members
Posts: 43
Member No.: 23178
Joined: 4-March 08



Thanks for the explanation, dloneranger.

However, I made a few tests and it is possible, using fcchandler's plugins, and with no VFW codec installed (Virtualdub says "MISSING CODEC"), to use direct stream copy and save a compressed AVI (I tried with a wmv -- which uses a VC-1 codec) and fcchandler's WMV plugin: the resulting file is a perfectly fine AVI, still compressed with the VC-1 and thus with a file size equivalent to the original WMV (in fact, usually Virtualdub shaves off a few bytes: my 216 MiB WMV file resulted in a 207 MiB AVI file).

I also tried to save only part of the file (of course, without seeing anything since I had uninstalled the VFW codecs I use), with success.

This must be why fcchandler's plugins all have to parse the whole file before loading it into Virtualdub, while the Ffmpeg Input Driver opens it directly.
 
     Top
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
378 replies since May 10 2011, 10:20 AM Track this topic | Email this topic | Print this topic
Pages: (26) « First ... 5 6 [7] 8 9 ... Last »
<< Back to VirtualDub Filters and Filter Development