Messages

26

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 29, 2014, 01:17:13 AM »

The possible options are to provide two different automator workflows (one with chroma smooth and one without), or to prompt the user to select options (which is some extra mouse clicks). Any preference, or other ideas?

I'm limited on the Windows/PFM side because I can't actually supply any parameters for the mounting.  My likely solution is to have a configuration text file (e.g., "config.ini") in the MLV's directory that can be parsed for such parameters on the fly.

Note that with the "config.ini" saved in the associated .MLD directory, this approach would make possible per-MLV settings (e.g., one file needs more chroma smoothing than others) that are persistent.

27

Camera Emergency Department / Re: Canon 50D - Sometimes JPG/RAW are corrupt

« on: September 29, 2014, 01:07:18 AM »

What you are describing is highly unlikely to be related to ML, and instead sounds like some sort of hardware problem.  ML doesn't intercept the normal recording of photos by the camera, and it also doesn't affect the transferring of files from the CF card.  Since you've tried four different cards, I'm inclined to suspect the card reader.

When you look at the files in camera, do they look corrupted at all?

(There are no modules in the ML version 2.3, so don't worry about that question.)

28

Raw Video / Re: RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST

« on: September 28, 2014, 08:24:18 AM »

The OP is wrong about the 60D (e.g., as pointed out in this post).  Because of the bottleneck of the SD card, the 60D is very constrained on the resolution it can continuously record at.

29

Share Your Videos / Re: My first DUAL-ISO RAW Video Test with EOS-M

« on: September 27, 2014, 07:23:11 PM »

chmee's mlvdiag 1.0.0 lets you save a minimal version of the MLV ("all metadata, one videoframe and one audiochunk").  (I don't know if there's a direct link to version 1.0.1, which has another option for saving just the first 55 MB of MLV file, but it's included in the raw2cdng download.)

30

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 27, 2014, 06:43:16 PM »

@Frank7D: I've uploaded a new version that fixed any crashing on my side, but I'm not using AE.  Can you try it with your workflow?

31

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 27, 2014, 05:36:18 PM »

@dmilligan: I've only encountered a few problems with cross-platform support for POSIX threads, and even those problems were localized to thread attributes and handling (joining, canceling, etc.).  As long as we're not talking about instantiating threads ourselves, I don't believe we'd encounter any weirdness at all with just mutexes.

@Frank7D: I think I may have tracked down the problem with the Window/PFM version.  Stay tuned.

32

General Chat / Re: 10.9.5 Mac: Macboo: Making card bootable failed Help!

« on: September 26, 2014, 10:09:43 PM »

Walter's point was that the nightly builds of ML have an improved installer (no need for MacBoot/EOScard) compared to the stable build (2.3).  Thus, even if you can't install the stable build, you may be able to install nightly builds without any difficulty.

33

Duplicate Questions / Re: 5D mak II ¿do i need a nightly build to record raw? ¿can i use a stable release?

« on: September 26, 2014, 01:23:40 AM »

I recommend starting the the latest nightly build, and only switch to something less recent if you have a very good reason.  Using builds other than the most recent ones is not particularly helpful to ML development.

34

Duplicate Questions / Re: 5D mak II ¿do i need a nightly build to record raw? ¿can i use a stable release?

« on: September 26, 2014, 12:57:22 AM »

Nope, raw recording is not available on any stable build.

35

Raw Video Postprocessing / Re: Workflow using MLVFS and After Effects

« on: September 26, 2014, 12:56:10 AM »

I've uploaded a new version of the DLL that now saves the XMP sidecar files to an associated .MLD directory.  Thus, you shouldn't need the scripts to save and restore the XMP files.  *However*, the existence of the .MLD directory may guarantee that the "Smart Import 2.jsx" script will fail.  Can you give the new DLL a try?

36

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 26, 2014, 12:52:33 AM »

New version of the Windows/PFM MLVFS DLL: like the other implementations, XMP sidecar files are now preserved in an associated .MLD directory.  Other types of files can be created, but they will be discarded upon unmount.

37

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 22, 2014, 01:42:38 PM »

I appears that the 10 day old version is working fine on AE 2014 for me. However, cannot say the same for the g3gg0's version on my Windows 8 machine. This maybe be because I am doing something horribly wrong.

For Windows, you can try the MLVFS version that uses Pismo File Mount Audit Package (see Frank7D's post on his AE workflow.  The MLVFS formatter can be downloaded here: https://bitbucket.org/dmilligan/mlvfs/downloads/mlvfs.dll

@dmilligan: can you add a download link for the DLL to the first post?

38

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 22, 2014, 12:59:46 AM »

Hmm, that's odd.  I'm no longer getting errors on my OS X side, so I don't know if I can help you track down the problems.  If you haven't already, I recommend nuking everything (object files, .MLD directories, any files starting with a period) to make sure everything builds and runs as cleanly as possible.

39

Raw Video Postprocessing / Re: Workflow using MLVFS and After Effects

« on: September 21, 2014, 10:37:35 PM »

I just uploaded a new version of the DLL with a couple of small improvements.

3. Get rid of the IDX files that will appear in the MLV directory. You can delete them or move them. You need to do this or the After Effects script will get confused. I run the batch file "Save_IDXs.bat" to move them to another folder (named "IDXs" in my case) just in case they might be useful for something. If you don't use the script, be careful not to accidentally delete or move any spanned files that might be in the MLV directory.

For MLV files without sound, the IDX file will no longer be created.  Because of how the code is currently structured, MLV files with sound still need the IDX file.  There's no particular reason to save these files; they're generated on the fly whenever they're needed.

4. Make all the virtual DNGs writable. This is necessary in order to import them into After Effects. To do it manually means right-clicking on each virtual folder, which can be tedious if you have a lot of them. For a quick and easy alternative, run "Make_Writable.bat"

Read-only attributes are no longer set, so you can skip this step.  ACR somehow "knows" to use XMP sidecar files for the virtual DNGs, even when they are not read-only.  I'm not going to question it.

40

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 21, 2014, 09:21:03 PM »

I believe I've fixed the problem.  dmilligan, please confirm and update.

41

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 21, 2014, 03:29:56 PM »

Something's wrong with the latest OS X MLVFS, now that there is a write implementation, and I haven't figured it out yet.  It may have to do with the "._*" files that OS X wants to create for all of the files.  Sorry guys: we'll get this fixed as soon as possible.

42

General Help Q&A / Re: Camera froze while recording, can I repair the file?

« on: September 21, 2014, 06:31:09 AM »

Perhaps.  Were you recording MOV, RAW, or MLV?

43

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 20, 2014, 11:52:25 PM »

I was hoping that AE would fall back to using an XMP sidecar if the DNGs were readonly, but this didn't happen and it appears there's no way force it to (unless you can find one). There's certainly no way to make the DNGs themselves writeable, so it looks like an AE workflow is not going to be possible.

I don't have or use AE, but Frank7D's workflow uses the Windows/PFM version of MLVFS, and those virtual DNGs aren't writable either.  He turns off the read-only attribute on the virtual DNGs, and then AE can open the sequence.  If AE actually tries to write to the virtual DNGs, that implementation will return a type of error that is actually soft-ish (i.e., AE might not actually realize that the writes failed), which may also be helping.

44

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 20, 2014, 06:13:30 PM »

Are you sure you are typing the command in the correct directory (i.e., where you downloaded mlvfs.dll to)?  You can type "dir mlvfs.dll" to make sure that the DLL is present in current directory.

45

General Help Q&A / Re: Canon 60D Dual ISO Question

« on: September 19, 2014, 03:46:21 PM »

>You say that Dual ISO reduces effective resolution? really? I thought it didnt affect anything? Wasnt that HDR video?

With dual ISO, pairs of lines at one ISO are interleaved with pairs at the second ISO.  So, for example, you'll lose resolution for sure in those parts of your frame where the high ISO is completely blown out.

>And I am limited by budget and isnt the 50d severely outdated?

The 50D continues to hold up well despite its age because it predates Canon pulling features from that line (e.g., AF microadjustments) and, quite important for video recording, it uses a CF card, so it can record much higher resolutions than the 60D.  One drawback compared to the 60D is that that the 50D cannot (currently) do dual ISO video.

>What are your thoughts on the 70D?

Keep in mind that ML does not yet support the 70D, although that may change in the not-too-distant future.

46

Raw Video Postprocessing / Re: not getting 1920x1080

« on: September 15, 2014, 10:44:49 PM »

mlv_dump (the one for OSX) won't open as it's a Microsoft thing.

Okay, I'll bite.  What in the world does this mean?  Running mlv_dump on OS X requires some Microsoft library?  Or you can't run the OS X version of mlv_dump on Windows?  Regardless, since you're talking about RAW video and not MLV video, you should just use raw2dng.

What's wrong with using RawMagic on regular non-MLV RAW footage to convert to DNGs and then work on them in Camera Raw?

If it works, nothing is wrong, but since you're apparently getting invalid DNGs, you should try other tools to try to isolate the problem.

47

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 15, 2014, 05:39:40 PM »

With no objections to removing "_audio", I have made that change.  New Windows/PFM DLL uploaded.

48

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 15, 2014, 03:47:17 PM »

Yeah, there really doesn't appear to be any benefit for having "_audio" in the filename when it already has the extension ".wav", so the cleaner approach would be to remove the "_audio".

49

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 15, 2014, 07:05:13 AM »

I've changed the naming scheme in the FUSE and Windows/PFM versions to match g3gg0's scheme.  (dmilligan: please update the OS X binaries)

50

Raw Video Postprocessing / Re: MLVFS - a FUSE based, "on the fly" MLV to CDNG converter

« on: September 14, 2014, 07:56:10 PM »

Is this xmp creation present on mac as well working with ae or is it a windows thing?

For now, just on the Windows side.  Because of the differences between FUSE and PFM and the rapid nature of MLVFS development, I imagine this won't be the last time you'll see features show up on one version before they show up on the other versions.

"I presume you want the filename of the MLV video prepended to the individual DNG files and WAV file?"

That would be perfect (for me at least).

Does anyone else have any thoughts?  I don't want to make this change if there turns out to be a compelling reason to keep it as it currently is (or to change it to some third option).