Hi Khaver! Sorry, I've been AFK for a while... I think I'll try formatting my PC (man, it needs that really bad) and I'll tell you if that was the problem. Thank you so much for your help!
Hi Khaver! Sorry, I've been AFK for a while... I think I'll try formatting my PC (man, it needs that really bad) and I'll tell you if that was the problem. Thank you so much for your help!
Update to my Batch Intermediate Creator.
Version 2.1
Squashed some bugs. Created some new ones?
Changed the pulldown cadence analysis to use the included custom version of the GetDups avisynth plugin instead of the Decomb plugin. The Decomb method required playing 2 seconds of video for each cadence variation until the correct one was found. This new GetDups method only requires 1 run through 2 seconds of video.
Having the Matrox VFW codecs installed would cause bicutil.exe to hang in previous versions of BIC because of a bug in the codec that wouldn't end the process when encoding was finished. The new version kills the bicutil.exe process when completed thus bypassing the bug. (the codec configuration dialog still takes a long time to appear, as in all programs, when the Matrox codecs are installed)
It would be nice to update the first post in this thread to include a link to the newest version.
The moderator has to edit this, but my signature has the links.
I knew I would need that someday. Converting .mov to .avi with Matrox Intermediate would make things even easier to deal with. Thanks Khaver!Originally Posted by Khaver
Edit: it seems to be "stuck" at the beginning of the encoding and not to encode at all. It started 2 minutes ago, easily, and still doesn't show any progress in the video encoding...strange (Matrox I-Frames HD codec).
In the avisynth template try adding converttorgb() at the end. Matrox seems to need rgb.
Awesome! Seems to work and quite well at 14-15fps but still! I won't have to do it manually for each video in After Effects!
Thanks a lot, saves me a couple of hours!
Actually..........Assuming your are using .MOV files from yout t2i and want to color correct/grade, then you should instead use:
ConvertToRGB(matrix="PC.601", interlaced=false)
That will flatten and use the full scale 0-255. That will be helpful for color grading and correcting. If you are going to keep everything the same, then use:
ConvertToRGB(matrix="Rec601", interlaced=false)
Or simply:
ConvertToRGB()
There is no such thing as "Idiot-Proof".........a good Idiot will get around that every time.
Thanks to Khaver for the tips so he made it work.
And thanks Racer. Actually, I didn't planned to do some color correction, but I'll probable end up doing some, to match the HV and the DSLR. Thanks for the info.
It's probably more the Matrox codec issue, but when I select 150mbps with the I-Frames HD option, I never been able to get more than 53mbps of bitrates in the videos. Other than this, it went well, at an average of 15fps and it saved me a couple hours of conversion being done all alone during the night!
Thanks a lot again Khaver!
Been trying to get this to work on my Win7-64bit machine with no luck. I have installed the application and associated prerequisite files fine. I can even render an intermediate file okay. But, whenever the 3:2 pulldown button is pressed I get a "Job Progress: Failed!" Seems to die at the cadence stage. Any ideas?
BTW: I can execute the older batch program v1.6 okay, but get very out of sync audio. The newer BIC v2.1 seems much nicer, so I'd like to get it to work if possible. Suggestions? Thanks!
Make sure your avisynth & plugins are 32bit not 64bit.
Yeah, good point. I meant only the FFDshow that are 64bits. I tried Avisynth x64 once for MeGui (still x64 version) and it wasn't a success.
So, using these, it should work fine:
FFDShow: x64
Avisynth: x86 + Plugins: x86
Well, I uninstalled avisynth, and ffdshow. Then I reinstalled using the links you provided, avisynth 2.5.8 and the 64bit codec pack then rebooted. But, I still get the error. During the cadence stage it says "analyzing", for a few seconds with a bunch of >>>>>>> symbols, and then it says "additional analyzing", but then dies with a "Job progress: Failed!".
I notice the sjobs.ilc, created from GetDups.dll is blank when I look at the left over temporary files. If I play the script sjobs-ANL.avs file manually through media player classic the sjobs.ilc does have a lot of text. Is this a clue to the problem?
This script looks really interesting. I have a question, which is, is it possible to remove the duplicate frames, that is, do the pulldown, but keep the original AVCHD frames intact, so that you have a smaller file, but the exact same frames except for the duplicates.
In other words, you would produce the same type of file that a native 24p setting in the camcorder would produce.
If you remove the pulldown, you can select the type of stream you want as output (.mp4/.avi/etc) with that encoder. You simply need the proper codec to be installed. For .m2ts, you could render the video stream (no matter the extension) and use tsMuxer to "mux" the video into a .m2ts video stream, which can be more compliant with NLE.
I know I can export MP4/h.264, but ideally what I would like is to losslessly retain the original h264 frames, without re-converting them. Seems like we should be able just to use the the progressive frames "as is" from the camcorder.
Theoretically, the process should be very fast--only removing frames, not converting them--and also give exactly the same file I started with, but without the extra frames. Maybe I'm missing something but it seems like most of the solutions re-encode the video.
Part of the compression of these codecs is encoding the differences between the current and previous frames. If you remove a frame the frames that rely on that frame will become corrupt. So to remove pulldown from these codecs you have to completely decode the video, remove the fields that are duplicates, recombine the fields correctly and re-encode to a new or the same codec.
Yes but I am assuming (perhaps misguidedly) that the duplicate frames are actually exact duplicates, so the next frame would "see" the same frame as before in 24p.
Howdy:
I'm trying to set up and run your BIC program, but whenever I hit the start button, I get Line 3466 Error:Array variable has incorrect number of subscripts or subscript dimension range exceeded". Any tips on what I might be doing wrong?
I'm embarrassed to say that I think that I found the problem, but was still unsuccessful. I assumed that ffmpeg was installed with ffshow, but I assumed poorly. I installed ffmpeg and that error message did not show up again, but then again no avi was generated, with the machine telling me that the job was finished with errors. I will try to find the script and post it. Thanks for your help.
Here is the AVS of the run that "ran" but gave no resulting file-
LoadPlugin("C:\Users\testbudda\Downloads\Batch_Int ermediate_Creator-v21\GetDups.dll")
LoadPlugin("C:\Users\testbudda\Downloads\dgmpgdec1 58\DGDecode.dll")
Mpeg2Source("E:\national anthem\Clip 001.d2v", UpConv=1).trim(15,75)
GetDups(mode=0,show=3,log=4,logfname="E:\national anthem\Clip 001.ilc")
Does this give any hint as to why I'm not getting an output file?
Thanks.
First, make sure the checkbox to remove temporary files is unchecked and run the conversion again. The resulting AVS file you show in your post is the "Clip 001-ANL.avs" file that is created first. After this AVS file is run during the analysis phase does the "Clip 001.ilc" file get created, and are there frame and metric entries in the file or is it empty? Does a "Clip 001.avs" file get created and are there entries in it? If there is no "Clip 001.ilc" file generated then try running the "Clip 001-ANL.avs" file in Virtualdub to see if there are any errors. If running this script in Virtualdub creates the "Clip 001.ilc" file correctly but it's not being created when you run BIC, and I'm assuming you're running an ffmpeg conversion, then something is not right with ffmpeg. Make sure the version of ffmpeg you're using has avisynth support enabled.
At a command prompt, go the the directory where the "Clip 001-ANL.avs" file was created and run this command:
X:\path to\ffmpeg.exe -i "Clip 001-ANL.avs" -an -f null null.avi
Replace the "X:\path to" with the path to your ffmpeg location. Ffmpeg should run and create the "Clip 001.ilc" file. If it doesn't, look for possible errors in ffmpeg's output. If that ran okay and created the .ilc file and a "Clip 001.avs" was previously created try running it using:
X:\path to\ffmpeg.exe -i "Clip 001.avs" -an -f null null.avi
Look for any errors in ffmpeg's. Let me know your results.
Reply With Quote
