Messages

Tony, the proxies are in sync now; thanks!

One thing that bothers me, and I think it is my fault, is that, in between the transcoding from MLV to DNG it appears a POPUP that freezes the processe until I it "Continue". This is bad because I put my footage to transcode while I am out, and I would expect it to be done when I get home, so, with this, I have a huge break in the workflow... Some Idea how to stop this POPUP from windows OS?

If you are referring to the Windows security warning window that asks "are you sure you want to run this software," then just uncheck "Always ask before opening this file" and you shouldn't see it again (but if you get a new version of the software, you will have to do this again; probably would be smart to run a short file through it once so you can disable all the warnings quickly).

For the people who aren't getting proxies:

While the program is running, do you see the tiffs appearing in the same folder as the DNGs? (the tiffs are the intermediate files that are generated after the dngs but before the proxies and then are automatically deleted)

The program tells you what it is doing while it is doing it. What is the program doing right before it finishes?

Does it finish with the normal pop up message saying it is done?

The more detail you give about what is happening, the easier it will be to figure out what is wrong.

Hey Frank.. I'm sorry I did not do a lot of testing for the proxies, I just assumed if you did a simple command to the dngs it will be ok. Just so you know.. of course it detects your framerate, i have the option -r "videoFPS", it is not at the front like rawanizer.. would that change anything? Does your proxy say 25fps? But anyway.. there must be other parameters to look at.. and the rawanizer line was for .RAW files, no audio involved here.. and so new troubles arise! Will look into it.. Thanks!

Hi Tony, according to the one solution I found (quoted in my last post), you need to put the input frame rate at the front. Otherwise, ffmpeg assumes a 25fps input rate (because it's an image sequence) and drops (or adds) frames to match the 23.976fps (or whatever you request) output rate. Not sure if you need to put the output rate also or not (I'm guessing not).

I did some more testing and found:

1. My proxies are adding duplicate frames but also are dropping frames and are ending up shorter than the dng sequence.

2. The audio in the proxy mov files is out of sync. The audio is the correct length but the video part is too short. The difference is made up by black frames at the end.

3. The dng sequence and the wav file are exactly in sync.

4. The shortening of the video in the proxy mov files is just the same as if they were assumed to be 25 fps (in actuality my videos were shot at 23.976 fps).

Reading here:

http://ffmpeg.org/ffmpeg.html#Stream-specifiers-1

I see some information about frame rates which may be helpful.

Edit: Here is something I found somewhere else which might be applicable (a solution to someone else's problem):

"An image sequence is assumed to be 25 frames per second.  Your command line requests 23.976 frames per second output.  So FFmpeg drops frames from your
video to achieve the requested frame rate.

I think you need to put the "-r 23.976" in front of the "-i".  Options that describe the input file must be given before the "-i" on the command line. "

Edit 2: Also, here are the command lines that Rawanizer uses to make proxies:

-threads 8 -r {InputVideoFps} -i "{InputVideoName}" -i "{InputAudioName}" -strict experimental -vcodec prores -pix_fmt yuv444p10 -s 1920x1080 {Parameters} "{OutputVideoName}.mov"

If you use a "proxy" of prores 444, is very good for final result/output.

That's true, but I'm planning to use the dngs for final render. I will use proxies just for editing (and after all, that's what the word "proxy" implies).

I guess you're right though; some people will want high quality "proxies" to use for final render, so I guess the intermediate tiffs need to be high quality.

Mmmmmh.. I don't know.. I dont want to drop the quality until I pass down ffmpeg.. since it's acting as a debayer shouldnt we use the full bit depth? Well really I am not sure.. and the -T is for creating tiffs instead of ppm.. don't know about the metadata... anyway gonna research on Ufraw, to see if its better and faster... when is ffmpeg gonna support DNGs?!?!?

You're right, I didn't notice that -T indicates tiff output!

As far as bit depth, we're talking about proxies here, which won't be used for final output, so do we really need 16 bits? Don't know whether using 8 would speed the tiff creation or not though.

It SUCKS that first you have to convert to TIFF in order to create a proxy, ffmpeg doesnt support it. Does anyone know a workaround? For now DCRAW is debayering the dng's into heavy tiffs. IT IS SLOW!

This are the parameters of dcraw that I'm using for now:

dcraw -v -w -H 0 -6 -T IMPUTFILE

I understand it has LOTS of options, can anyone point me in a better direction? I notice a color shift with the proxies. I dont know if I'm gonna add a dcraw section, the point of this program is to keep it user friendly and not "hackish" or complicated. The user must have a complete NON understanding of these complicated procedures and still be able to get the footage processed!

So maybe it is slow because of some of the parameters?

tony, I did a little reading on dcraw. I don't know if you've seen this:
http://www.cybercom.net/~dcoffin/dcraw/dcraw.1.html

Based on the above, my suggestions to maybe speed up proxy creation process:
~ Make 8 bit tiffs instead of 16 (drop the -6)?
~ Eliminate metadata in tiffs (drop the -T)?

So, you tested with someone walking and it "appears" to be in sync? That's what I was asking.. sorry..

Yes, the audio is pretty much in sync, but as I said if it's off by 1 frame it would be hard for me to tell.

The proxy is definitely off by one frame (visually) from the dng sequence however, because of the extra frame at the beginning, which makes editing with the proxies problematic if you want frame-accurate edits.

Thanks for the new metadata; very helpful!

As far as the proxy sync issue, I haven't determined yet if the sound is in sync or not for the mov files; it's hard to tell because they are only off by one frame (from the dng sequence). I can probably chop that first frame (the dupe) off somehow before editing it, but if you can figure out why the extra frame is getting tacked on the beginning of the proxy files, that would be even better.

"So, you tested a video with someone talking and it is IN sync?"
I haven't gotten that far; I'll check audio sync when I'm back at my workstation.
But that would be a separate question, I think. Ideally we would want the proxy to be in sync with the video it is being substituted for, so that we can edit the proxy and then swap in the best quality video for final render. Not that there aren't possible workarounds, but if the proxy matched the original video frame for frame, that would be best.

"By dupe frames you mean black frames?"
In the proxy video, the first frame of the sequence is duplicated so it appears twice at the beginning. This makes the proxy 1 frame out of sync with the dng sequence.

When I make proxies ("Prores Proxy" "Scale to 1080p") the proxies get dupe frames so they end up longer than the original dng sequence (and are out of sync with the sequence). At least, that's what it looks like in After Effects.

Edit: Looking at it in Premiere, I see that the main thing is that there is a dupe frame at the start of the clip (sometimes some garbage frames at the end of the clip but they don't matter since they can be trimmed).

tony, v 1.5 works for me; thanks so much!
As far as metadata, in addition to what you already have, it would be helpful to see the lens name and aperture and focal length and shutter speed and ISO. I see those when I play an mlv in MLVViewSharp; not sure if they are from the current frame being played, but for me seeing those for even just the first frame of the mlv would be helpful. Any way you could make that available would be great, whether out front or accessed through a button or any other way.

Yes, tried different files and settings. I can use 1.2 for now. I'll try the next version when you release it; thanks again for your efforts!

Hi tony,
I tried v 1.3 and got an "unhandled exception" error message which says "Only supported on Windows 7 or newer". I have Vista. I had no trouble with your previous versions.
It happened when I hit the "CONVERT" button.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.PlatformNotSupportedException: Only supported on Windows 7 or newer.
   at MS.WindowsAPICodePack.Internal.CoreHelpers.ThrowIfNotWin7()
   at Microsoft.WindowsAPICodePack.Taskbar.TaskbarManager.get_Instance()
   at WindowsApplication1.Program.Stopper_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4223 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MLVtoDNG BATCH
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Frank/Desktop/Apps%20Backup/Freeware/MLV%20Batch%20Converter/v%201.3/MLV_Converter_1.3/MLV%20Converter/MLV%20Converter.exe
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4223 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4228 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4230 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Microsoft.WindowsAPICodePack.Shell
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Frank/Desktop/Apps%20Backup/Freeware/MLV%20Batch%20Converter/v%201.3/MLV_Converter_1.3/MLV%20Converter/Microsoft.WindowsAPICodePack.Shell.DLL
----------------------------------------
Microsoft.WindowsAPICodePack
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Frank/Desktop/Apps%20Backup/Freeware/MLV%20Batch%20Converter/v%201.3/MLV_Converter_1.3/MLV%20Converter/Microsoft.WindowsAPICodePack.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Hi tony, thanks for the app; it's already great and I appreciate your efforts to improve it further!
One question; when you say:
"WAV file renaming. This way you can grab all your folders in your root DNG folder and throw them into after effects. You will be prompted with ACR for each sequence. Time saver."
I'm not sure I understand. The only way I know how to do it is to double-click in After Effects and browse to the folder with the dngs and select them all and open as raw sequence. In other words, I only know how to import one sequnce at a time. Is there a way to do multiple sequences at once?

I found that sometimes NV can't find a good sample area in my video. Here's what I tried that seems to work well:

Shoot a short clip aimed at a blank area, such as a white posterboard, using the same settings (especially ISO) as you used for the video to be cleaned. Shooting this out of focus worked better for me for whatever reason. Note that shooting with the lens cap on didn't work for me.

Load this blank video the same way you did the video to be cleaned, i.e. same ACR settings or whatever.

Use Neat Video to sample the blank video. Save the profile.

Apply the profile to the video to be cleaned. Adjust NV's sharpening etc. to taste. Save the NV settings if you think you might use them again.

This has gotten me the best results I have seen so far.

You can view them in file manager if you have two modules loaded: the file manager module (file_man), and also the mlv_play (or called something like that, not at home now). Just don't pause and then exit or your camera may freeze (which would force you to turn it off to resolve).

Trying 1/20/14 build.
When I view (play) a raw file using file manager, and hit pause, then select exit, camera freezes and I have to turn it off.

Using 1/14/14 build.
Is separate wav audio recording working with raw_rec?
No wav files are showing up for me.

Hi, I searched for this issue but couldn't find it.
Is this to be expected (occasionally) when shooting crop mode?
Good frame:

The next (bad) frame:

I found out why I didn't have ml grayscale; I had canon overlays turned on. Once I hit the info button to get rid of them, the ml preview appeared.

First post, hi everyone.

I was using the 1/13/14 nightly build, shooting crop mode 1920x1080 23.976 fps when the filming stopped with beeps and "Early Stop 9 This is a bug please report it" so that is what I am doing. I have filmed a little since then and it hasn't happened again yet.

Also, I can't get the ml grayscale preview to appear. I set it to that and also tried "auto" but don't see it when shooting crop video.