|
|
| vmaronek |
| Posted: Nov 8 2014, 11:39 AM |
 |
|
Newbie
Group: Members
Posts: 6
Member No.: 38404
Joined: 8-November 14
|
Hi,
I found Deshaker filter for VirtualDub to stabilize "hand recorded" videos, but it don't work for H264 video format.
With my plugins I can open and process 264 videos in my VirtualDub, but this filer results in Error-100.
I would like to stabilize 264 video directly (not to be converted to worse XviD), what are the possibilities?
Thanks for any reasonable advice. |
|
| dloneranger |
| Posted: Nov 8 2014, 12:54 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
If I remember the error 100 message it's a 'corrupt data' one?
Try using a different way of decoding, like the ffmpeg plugin (in my sig), different decoding codec, or just cutting out the bad section
When posting errors, its always best to give the full message, and whatever details are in the dial information dialog box - what kind of file it is, decompressing codecs used etc (it may just be you are using a decompressor that's known to be awful)
H264 has two main codecs for avi's and (fcchandlers quicktime plugin for mp4 and mov) ffdshow's vfw codec and x264vfw
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| vmaronek |
| Posted: Nov 9 2014, 09:51 AM |
|
|
Newbie
Group: Members
Posts: 6
Member No.: 38404
Joined: 8-November 14
|
Hi,
the file is not corrupted. If I process it without Deshaker filer, everything is running smoothly.
I guess the error 100 (corrupted file) is given because the filter can not work with this format.
Therefore I am looking for the stabilizing filter which can work with AVC (264) format (original file is coming form Samsung Galaxy S2). |
|
| dloneranger |
| Posted: Nov 9 2014, 01:57 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
Virtualdub decompresses the video and gives the decompressed frames to deshaker - the filters never know what the original format was, it's all uncompressed data to them
Which means the message is coming from virtualdub trying to decompress it, see the first post for alternative ways to load the file and use different decompressors
As you haven't stated what format the video is or what you're using to decompress it, there's not much help to give
eg it's an mp4 and i'm using the quicktime plugin, which is using x264vfw to decompress
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| raffriff42 |
| Posted: Nov 9 2014, 03:19 PM |
|
|
Advanced Member
Group: Members
Posts: 384
Member No.: 35081
Joined: 25-June 12
|
The problem may be that Deshaker accesses frames out of order and VirtualDub is having trouble accurately seeking to the correct frames.
In straight dub mode, VirtualDub's error concealment should handle the odd bad frame. I would dub your h.264 videos to some lossless format such as Huffyuv, Lagarith or UTVideo. The files will be huge, but you can delete them after doing your final video. |
|
| vmaronek |
| Posted: Nov 9 2014, 09:24 PM |
|
|
Newbie
Group: Members
Posts: 6
Member No.: 38404
Joined: 8-November 14
|
Thanks for your help. It is a little bit strange. One video file caused me described problem (OK without Deshaker filter, but Error-100 with), but other H264 file was OK.
Anyway hopefully I will process it finally. |
|
| asaleo |
| Posted: Nov 9 2014, 09:27 PM |
|
|
Advanced Member
Group: Members
Posts: 70
Member No.: 26562
Joined: 4-December 09
|
There is no problem deshaking H264/avc1 files in VirtualDub.
I do a lot of deshaking of mp4 files.
I use the Tateau plugin and use mode 2 för all type of files.
Regards |
|
| raffriff42 |
| Posted: Nov 9 2014, 09:53 PM |
|
|
Advanced Member
Group: Members
Posts: 384
Member No.: 35081
Joined: 25-June 12
|
Very interesting. Where can I get this "Tateau" plugin? |
|
| dloneranger |
| Posted: Nov 10 2014, 06:51 AM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
It's on the input plugin page
It's an older one and requires Quicktime be installed (minor snark -> look I'd be using a different codec just like suggested in the first post of the page.... sigh)
http://forums.virtualdub.org/index.php?act...=ST&f=7&t=19812
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| vmaronek |
| Posted: Nov 10 2014, 08:25 PM |
|
|
Newbie
Group: Members
Posts: 6
Member No.: 38404
Joined: 8-November 14
|
So final investigation:
Source video file: Samsung Galaxy S2
Then I open it in AviDemux and save with following settings: Video:copy, Audio PCM, output format mkv muxer (it is for the reason of sound synchrone).
Then open in VirtualDub. I tried several files with following error when Deshaker filer tried to run video analysis pass (according to tutorial):
x264vfw [error]: timebase mismatch with 1st pass (8038921/200000000 vs 10049047/250000000)
x264vfw [error]: x264_encoder_open failed
I am using Deshaker 3.1.
When I save the file under VirtualDub (without Deshaker filter), it is OK.
When I save it as x264, and then open and try to apply Deshaker, the same error occures.
But when I save it as XviD and then open and try to apply Deshaker, it is running correctly.
What is strange, that one of the testing mkv files (x264) was running, another 4-5 no.
|
|
| vmaronek |
| Posted: Nov 10 2014, 08:59 PM |
|
|
Newbie
Group: Members
Posts: 6
Member No.: 38404
Joined: 8-November 14
|
One more note:
I ascertained that the error problem is not connected unambiguously to Deshaker or x264 file.
It is very strange, but I received the error, after restarting the VirtualDub it ran.
I really don't know what I should think about it. |
|
| raffriff42 |
| Posted: Nov 10 2014, 09:35 PM |
|
|
Advanced Member
Group: Members
Posts: 384
Member No.: 35081
Joined: 25-June 12
|
vmaronek, please post a MediaInfo report for the Galaxy file and another one for the AviDemux file. Instructions at the link.
EDIT scratch that; I have no idea what the trouble could be. |
|
| dloneranger |
| Posted: Nov 10 2014, 09:48 PM |
|
|
Moderator
Group: Moderators
Posts: 2366
Member No.: 22158
Joined: 26-September 07
|
The stats file for x264 isn't the same for pass 1 and 2
They've got different frame rates for a start
Try changing x264vfw's stats files to a full path instead of .\x264.stats
The .\ means it's a relative path, and the current directory's probably being changed somewhere between pass 1 and 2
--------------------
MultiAdjust JoinWav WavNormalize FFMPeg Input Plugin v1827 UnSharpMask
Windows7/8 Codec Chooser
All FccHandlers Stuff inc. Installers for acm codecs AAC, AC3, LameMp3 |
|
| vmaronek |
| Posted: Nov 26 2014, 07:49 PM |
|
|
Newbie
Group: Members
Posts: 6
Member No.: 38404
Joined: 8-November 14
|
Hi there,
when I start VirtualDub, open the file (does not matter if X264 codec) and use Deshaker, everything is OK.
The above mentioned problem appears, when I open and try to process another file (even of the same type from the same source)
I don't know, why.
So I solved it that after processing one file I close VirtulDub and open it again.
Then I can process another file and so on... |
|
| BugMaster |
| Posted: Nov 26 2014, 10:16 PM |
|
|
Advanced Member
Group: Members
Posts: 50
Member No.: 23001
Joined: 6-February 08
|
As was said above it is because current working directory is changing (it changes to the directory you navigated in open/save file dialog) and so relative path ".\x264.stats" now point to another place (where for some reason there can be x264.stats file which was left from another encode). And yes it is recommended to change stat-file path to full path if it possible (to prevent such directory jumps affecting it). Also if you do video analysis pass than decide why are you doing it and configure all accordingly:
1) if don't want encoder to be involved at all (dunno what for you run it than) than change video compression to uncompressed;
2) if you want to generate encoder stats-file without creating output file (that was imho the reason for video analysis pass in first place) than configure encoder accordingly (i.e. for x264vfw it should NOT be configured for N-th pass but to 1-th pass in this case);
3) if you going to use already generated stats-file than either use full path or don't change working directory (do not change directory in open/save dialog) between first and second pass. |
|
