Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
9th January 2011, 09:38 | #1001 | Link |
Registered User
Join Date: Mar 2005
Posts: 30
|
Hi,
I'm trying to open a TS file (recorded from DVB-T, H264 1440x1080i50 MBAFF) with FFVideoSource. I tried with both the TS and remuxed to MKV, and the number of frames is not correct. The loaded video is strange : the odd field only changes every two frames, and the even field often jumps forward and backward by several frames. If I force the fps (fpsnum=25, fpsden=1) it loads correctly. |
9th January 2011, 11:33 | #1002 | Link |
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
That's a known bug. FFMS2 hates TS; writing our own TS parsing library and supporting that format properly is on the todo list but nobody I know including myself has time to work on it right now.
|
16th January 2011, 23:48 | #1005 | Link | |
Registered User
Join Date: Aug 2010
Location: Paris
Posts: 52
|
Quote:
|
|
17th January 2011, 11:45 | #1007 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
(Actually the Avisynth plug-in is yet another wrapper around the FFmpegSource2 core library. Applications, like x264, can use the FFmpegSource2 library directly)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 17th January 2011 at 11:48. |
|
17th January 2011, 12:05 | #1008 | Link |
Registered User
Join Date: Jul 2010
Location: Tbilisi
Posts: 75
|
for example: I have an avi file(divx) and I want to open it in Edius, Vegas or Premiere Pro in uncompressed. I write a script for avisinth(ffvideosource("C:\avifile")). now I can import this script in virtual dub, but how can I make a fake avi to open it in this big programms like Premiere Pro. I tried makeavis and vfapi , but it didn't work.
|
17th January 2011, 12:14 | #1009 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
So your question is NOT specific to FFmpegSource2. You want to know how you can open Avisynth scripts in the aformentioned applications.
I think this can not be answered in general, but at least for Premiere Pro a plug-in exists: http://urchin.earth.li/~tomford/avisynth/ See also: http://forum.doom9.org/showthread.php?t=47194
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
17th January 2011, 12:17 | #1010 | Link | |
͡҉҉ ̵̡̢̛̗̘̙̜̝̞̟̠͇̊̋̌̍̎̏̿̿
Join Date: Feb 2009
Location: No support in PM
Posts: 712
|
Quote:
__________________
dither 1.28.1 for AviSynth | avstp 1.0.4 for AviSynth development | fmtconv r30 for Vapoursynth & Avs+ | trimx264opt segmented encoding |
|
18th January 2011, 03:13 | #1013 | Link |
warpsharpened
Join Date: Feb 2007
Posts: 787
|
ffms2-mt-r411.7z
ffms2-mt-r412-avs64-2.7z For avs64 (for use with 64bit avisynth) be sure to load with LoadCPlugin. Edit: Uploaded fixed avs64 version. Last edited by TheRyuu; 18th January 2011 at 19:39. |
18th January 2011, 07:04 | #1014 | Link |
Registered User
Join Date: Aug 2006
Posts: 2,229
|
The 411 build from the link about doesn't seem to work properly for xvid AVI's, whereas the 408 build and earlier has no issues. I tried 411 with a mkv x264 file I did earlier and it worked fine, so it seems its only 411. The encoding crashed pretty quickly, and if I quickly jump quickly back and forth through staxrip's preview with 411 it ends up crashing too...
|
18th January 2011, 09:06 | #1015 | Link | |
Registered User
Join Date: Dec 2001
Posts: 145
|
Quote:
Versions were ffmpegsource svn trunk + ffmpeg svn trunk + x264 git trunk built on Jan 11. I need to try if I can still replicate this. |
|
27th January 2011, 15:30 | #1016 | Link |
Registered User
Join Date: Aug 2006
Posts: 2,229
|
Neither the FFmpegsouce build 411 and the new 423 build work correctly, once indexed and the video loads, it crashes. I'm using Staxrip, and yes I did do everything correctly!!! This is with multiple source files, with no exisiting index files etc.
Sticking with 408 for now. |
27th January 2011, 19:06 | #1017 | Link | ||
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
Quote:
Quote:
|
||
28th January 2011, 00:25 | #1018 | Link |
Registered User
Join Date: Aug 2006
Posts: 2,229
|
Ah ok! Are they the builds on code.google.com/p/ffmpegsource ? They're the ones I were having issues with.
Are there other sites that keep the builds up to date? I was thinlking a weekly build wouldn't be a bad thing... i realise ffmpegsource2.14 is technically the latest release version, but that is quite old. At least with the weekly version, if anyone encounters an unknown problem it can be reported and listed quicker, and they can go back to using the previous weeks build (which isn't several months old)... |
28th January 2011, 01:08 | #1019 | Link | ||
Excessively jovial fellow
Join Date: Jun 2004
Location: rude
Posts: 1,100
|
Quote:
Quote:
I'm actually planning to release 2.15 quite soon. Have a test build (vanilla ffmpeg as usual): http://mod16.org/ffms2/ffms2-r426.7z Changes since 2.14:
Quite a few regressions in earlier test builds have also been fixed. To force a demuxer, use demuxer="lavf" as an argument to ffindex(). Possible choices are lavf, matroska, haalimpeg and haaliogg. |
||
28th January 2011, 10:26 | #1020 | Link |
warpsharpened
Join Date: Feb 2007
Posts: 787
|
I've poked the ffmpeg-mt dev about the issue, apparently there may have also been some talk in #ffmpeg-devel about it although I don't know the details.
So I'm trying to figure out what the issue is with my ffmpeg-mt builds, vanilla builds (even mine) do not seem affected so they should be safe for the time being albeit a little slower on things like h264. |
Thread Tools | Search this Thread |
Display Modes | |
|
|