Messages

BUMP.  anybody?

The ffmpeg argument currently is "-vcodec prores_ks -profile:v 3". The colour format that uses is YUV444 10bit. The quality is quite high, and of course it's using (slow/expensive) AMaZE for demosaicing.

I opened it in VLC.  It reads it as ProRes 4:4:4 YUV 10-bit LE.  Based on comments from baldand, this is the most accurate answer.

Gary, the question of what ProRes has been answered by both baldand and myself.  What more do you wish to know?

Andrew, I just discovered your tool, and suffice to say I am incredibly impressed.  The last time I took a deep dive into ML Raw post-production tools, there was much function (great) with terrible design and layout choices.  This software is a breath of fresh air. When you package features with slick design, expect an audience to grow, good sir.  Again, very impressed.

I just submitted an enhancement issue requesting tool-tips.  First-time users often hover over buttons and want to know functionality before clicking.  While the text-based Readme file is useful for explaining the software's purpose and keyboard controls, it can't and doesn't break down the visual elements.  I hope to see a short description for each visual button on-screen.  If you would like, I can write the tool-tips up and PM them to you to save you time.  Let me know if that would be helpful or not for you.

Additionally, integrating the documentation (i.e. About--> Help/Manual) inside the software would be swell as well.  Many end-users don't think to check the Readme file (or keep it long enough to check it) and only go looking for help once they think a feature is missing or are running into a problem which is likely just a user error.

Anyway, I'm just being a proponent of fool-proofing the tool you've designed because the easier it is to use, the easier it is to just pass on to someone new without sending them to a forum / website to figure it out.

I would expect when MLV gets standardized and publicly released that a workflow standard will battle itself out.  At this rate, assuming batch encoding shows up soon for this application, I hope it becomes the, or one of the, gold standards.  Simplicity and beauty meets function.  Recognition is well deserved.

Edit: BTW, I endorse the earlier suggestion of making 'Mark In' and 'Mark Out' I and O respectively, as that is relatively standard for video prep and editing.  Again, if someone didn't read, that's what they would press on the keyboard.  Cheers!

Just one question that is hard for me to figure out that maybe one of you can answer, What kind of proress does MLV viewer export to?

I opened one of the files in QuickTime.  It reads it as ProRes 422 HQ.
I opened it in VLC.  It reads it as ProRes 4:4:4 YUV 10-bit LE.  Based on comments from baldand, this is the most accurate answer.

I can confirm I am experiencing the same issues on the 600D as the OP is.  Stopping RAW capture generates this error.

I hope very much that some individuals with the willingness and resources tackle the merge of TL mutually with 1%, because fragmentation over time is a bad, bad thing.  Especially with projects like these.

Just figured this out--7 months later.  I was under the impression that the files/scripts in the HDR workflow folder being downloaded were self-contained.  I realized just now that I needed to copy all the contents of the "Avisynth-plugins" folder into my Program Files folder where Avisynth is installed.  After doing that, the audio script works perfect.  This issue is resolved.

Modifying the video mode to slow down from 30fps to, say, 2-5, that would be ideal IF i can get the exposure right for fireworks.

If you want a timelapse straight out of camera, then do what you said here.  You would likely need an ND filter.

As far as I'm aware, the only way around the 4GB limit is ML's auto-restart feature.  exFat or otherwise, doesn't matter.  Someone can correct me if I'm wrong.

You don't need a fast lens/aperture for fireworks.  They're bright, and can overexpose easily the longer the exposure.  f8-12 is a good place to start.

Keep ISO low, generally 100 is fine.

Use a tripod.

Shutter speed is the hardest to nail down.  I know many people just use a remote shutter + BULB mode to decide when to start the exposure and when to stop it.  This gives you full control over how many fireworks fill the frame and the brightness level.

If you don't want to be next to the camera to maintain control over the shot, your best bet is probably around 2-4 seconds exposure.  Turn on ML intervalometer and let it go.

From there, it's trial and error.  You'll get a feel for it.  Good luck.

First off, try opening to f1.8 through Canon buttons, not ML menu.  I.E. hold 'Q' and use shutter wheel.  Cycle through the on-screen displays using 'INFO' to check between the ML aperture reading and the Canon aperture reading.

It could just be the ML on-screen readout and your lens is opening to f1.8.  I have some similar issues with exact shutter speed readings on my ML menu sometimes.

If you're still having issues after the above and want to be really certain, take a picture of a subject in static lighting conditions in manual mode at f1.8 and another picture at f2.0.  Then in video mode hold 'Q' and use the wheel on top to open your aperture as much as possible.  Take a third picture.  Compare the histogram of picture C to A and B to see if your aperture is at f1.8 or f2.0.  Obviously your shutter and ISO need to be maintained for all three pictures for it to work.

I just submitted this as a bug, but thought I'd post here too to see if any of the community might have an answer.

My 600D isn't creating any sidecar files when taking pictures, whether normally or through the intervalometer.    I am using nightly build, August 17.  After taking a picture, the bottom left corner of the LCD states, "Deflickering..." until image review stops. If I leave image review on "Hold" via the Canon menu, then the deflicker message just stays onscreen until I cancel out. I didn't find this important until I plugged in my SD card to my PC. No sidecar files. I have tried both XMP and UFRaw. If there is some sort of log I can attach for troubleshooting, let me know and I'll happily do it.

Cheers!
Dreamer

Yep, installed avisynth through interframe script package, install file named "AviSynth_110525.exe"

It could well be you are running Avisynth 2.6 alpha and that may be the problem. The link provided above to AVISynth_110525.exe  is the 2.6 alpha, Sourceforge's Avisynth setup is well stuffed up, so easy to download 2.6 alpha rather than 2.5.

Try this link:

http://sourceforge.net/projects/avisynth2/files/AviSynth%202.5/AviSynth%202.5.8/

...

I found the above quote in the ML Post-Workflow sub forum. This was a reply to another user having trouble getting his C series of frames to compile from the A and B series.  I bring this up because in my "Program Files (x86)" directory I find the folder Avisynth (2.5), yet when I open Window's "Uninstall a Program" dialog box, it lists "Avisynth 2.6", so could this be an issue?  I have only ever installed Avisynth once, and that was from the user-friendly interframe package downloaded from the ML Userguide webpage.

Cheers,
Dreamer

[UPDATE]

UPDATE:  See last post.  Issue resolved.

Hey guys.  I use the Canon 600D, ML Unified v2.3.
My computer is a Windows 7 64-bit machine.

I am successfully creating HDR video using the user-friendly version of the interframe script found in the userguide section of this site.  However, I am receiving an error message in VirtualDub when attempting to attach the audio to the movie prior to export.  I am following the steps outlined in the 'README' file downloaded with the interframe script package, read as follows:

• Choose your processing options in VirtualDub:
.....
– Optional: add the audio track from the original video (Audio > Audio from other file,
select scripts\audio.avs)

I have labeled my movie as RAW.mov in the root directory of the interframe script package. Avisynth command prompt opens and successfully extracts the A and B frame series, then creates the C frame series.  VirtualDub reopens.  I can choose all my video options.  However, when I follow the above guideline for audio, I receive the following error message:

Avisynth open failure:
Script error: there is no function named "FFAudioSource"
(C:\Users\...scripts\audio.avs, line 2)

I can export out the movie just fine without audio.  Any help would be greatly appreciated.

Cheers,
Dreamer