Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - baldand

Pages: 1 [2] 3 4 ... 17
I have a mid-2011 iMac and tried the other suggestions.  Still no luck.  It played smoothly before, during tests, but can't figure out why it won't play smoothly now.  I'm not sure what to do.  I am currently exporting as MOV to check all the clips.  The sound plays normally, just the picture skips.  I know it might be frustrating with little issues like this, especially since you just put out a new update, (I'm using an older version) so if you don't have any other suggestions, I understand.  Thanks! 

Your machine should be fast enough for smooth playback, so this is a bit mysterious.

If you play back in non-drop frame mode (press F, or change clock icon to a frame) there is no sound but you will see all frames. Is that not a usable alternative to the MOV render for checking? Does that play back noticeably under the real speed?

You say it was smooth "before" - can you say in which version? 1.3 introduced a new demosaic function for playback, which could possibly be slower on older GPUs, but I wouldn't have expected this on your machine.

Another question - how long (number of frames) and what res are the clips you are playing? Is it skipping even with short or lower resoluton clips?

If you try 1.4.2, please write a short note here about your environment and observations, even if everything works OK, and especially if it doesn't.


- Shift-B key tries to find the first 12kHz beep in the audio file, and sets the audio offset to that

This is pure magic. I use the same work flow that you and this could save a lot of work!

I hope this works for you. It's not 100% perfect, but for me it is working quite well in most cases. If the first 60 seconds of the wav has a lot of broad spectrum noise it can pick the wrong offset though.

MlRawViewer 1.4.2 is now available

Download link:

Summary of Changes:

- Fix for C key so multiple exports can be queued
- Fix for W key to launch dialog for choosing export directory
- Shift-W opens dialog to choose an external WAV file to play with the clip
- Colour store/restore (H/G keys and MS/MR icons) now store also tone map and all LUTs allowing all colour-related settings to be copied between clips
- Tone mapping and balance no longer "floats" when changing between clips because it was not being persisted to the per-clip settings. Instead, you should use the store/restore to copy settings.
- Audio file name and offset are now shown in the metadata
- Audio offset can be reset to the current video position with Shift-N key
- Audio file names are now stored relative to their parent clip so they can be moved and stay associated
- Numeric keypad should work for colour balance nudging
- Shift-B key tries to find the first 12kHz beep in the audio file, and sets the audio offset to that
- Fixed bug in Histogram. Previously it was only measuring the bottom third of the image.
- Audio playback system reworked for better random access performance
- WAVs exported with DNGs now include bext, iXML blocks & DNGs include CameraSerialNumber and TimeCodes tags. With these, Resolve should automatically embed the WAV in the clip.

About this release

This release has mainly been about improving the audio handling, particularly with daily issues affecting me.

Since I use an external Zoom-H1 for all my audio, I wanted a better way to pair and sync those files with my clips.
I use the ML feature to play a 12kHz beep at the start of every clip, and I always start recording audio before video.

In MlRawViewer, this workflow should now work quite well. Open the clip, then press Shift-W and choose the matching audio file.
Then press Shift-B, and in most cases the (high quality) audio should now be very well in sync with the video.

If you don't have the beep, then Shift-N can still help with sync - wait until you hear the start of the video and then press Shift-N. The use the audio offset nudge keys (B/N) to get the sync exact.

Resolve should now also show the WAV files embedded in the clip (thanks to dmilligan/chmee/danne for all the tips about how to do this), however since Resolve doesn't seem to handle 96kHz WAVs, this hasn't been a very useful feature for me :-(

The other big change is that you should now use the colour store/restore (H/G keys or MS/MR icons) to copy settings between clips. Earlier there was ambiguity about what settings a clip was using because some values would float until you had explicitly set them. This was useful when jumping through takes, but confusing later when coming back to those clips again and seeing them with diferent settings applied. Now it should be more explicit - there is a default value and if you change it, the changes are persisted. Full sets can be copied between takes with H/G

As I said before, I really love this player.  It's been a life saver.  (unintended rhyme)  Although, I cannot get it to play my mlv's at 24 fps.  It's if it's skipping frames or something.  I am still using an older version (v1.2.3) because it's what I'm familiar with and is easiest for me exporting.  Could someone please let me know how to get smooth playback?  Thanks!

What GPU do you have - is it Intel integrated or discrete? Only discrete or recent Intel GPUs can play smoothly.
Things to try: turn off stripe correction, remove all LUTs, update graphics drivers.

my clips say this the best log??

That's just the default. You can change it by clicking the tone map icon (box with a curve in) or pressing the T or Shift-T keys.

Other log options currently are: Log-C, S-Log, SLog2 and "Log8". You can also provide your own preferred log curve as a 1D LUT.

The exporting to MOV file always stops at 0.22% and no MOV file is produced...

1. Did you set an export directory using the W key?
2. Open and share the log file in $HOME\.mlrawviewer\mlrawviewer.log (this is probably easiest to do using the command line)
3. Try deleting the $HOME\.mlrawviewer directory and running again. From command line: cd<press enter key>rm -rf .mlrawviewer<press enter key>

Feature request: I would love to make MLRawviewer my one-stop encoding program for all my editing work, also for non-raw files. What are the chances?

Unfortunately quite small at the moment.

This would really need to use the libav underlying ffmpeg in order to get metadata and allow efficient random access to frames. Possible, but not trivial.

after viewing can you delete clips in the mlrawviewer you don't need?

No, and I wouldn't be keen to add that kind of option as it might be too easy to lose clips by accident.

@feureau looks like a couple of keys were missing from the top post:
H/G - Save/load current colour balance & brightness (for matching multiple takes)
The MS/MR buttons on screen do the same thing.

So, set the white balance and exposure in one clip, the press the H key or click MS.
Go to a new clip with the same conditions, and press the G key, or click MR.
In the next build, this will also store LUTs and the tone map setting as well as exposure and balance.

are the following keys supposed to work with the numpad?

Also: Would an x64 version decode/encode faster? I was rendering in the background (set to low priority so I can work on other stuff, premiere runs normally, for instance) and found that the busy computer for some reason made MLRawViewer's processing goes really slow. What used to take half a day took 2 days to complete.

Nice find with the numpad. This will be fixed in 1.4.2 so they work same as the other number keys.

I doubt a windows x64 version would make much difference, but I have to admit I haven't tried it. Linux and Mac version are usually 64bit, and I don't think they are radically faster. 

Rendering to MOV or export to DNG with stripe processing requires the GPU, so it's possible that putting it to the background and running other programs could disrupt this and have a big impact to the performance. To be honest, the CPU should be maxed out for export or render to get the best speed. It's quite ambitious to consider doing other things on the computer at the same time.

However, I have found the C key does not work.

Thanks. This will be fixed in the next build (1.4.2)

Just to clarify:

MlRawViewer DNGs are 16bit, but this 16bit data is padded with 2 zero bits from the original 14bit Canon data.

As they use lossless JPEG compression, the file size on disk is typically less than a 12bit uncompressed DNG. No data is lost in this process. The DNGs contain every bit the camera produced.

(I still wouldn't recommend it as an archival format for MLV files - I think it would be better to integrate lossless JPEG to the MLV format. g3gg0 has done some work initial towards that approach in the mlv_rec_lj92 branch of ML but I don't know what the status is currently).

The win32 should work fine on 64bit win7. Please give details of the problem you have.

Just click all the luts you want and they are immediately imported (shown by dimming)

If you are trying to playback direct from CF card, you should check the read speed you are getting and confirm that it is higher than the bitrate of the file.

For example, my KB64GB cards can write 70+MB/s in camera, but for some reason they only read back with my card reader at 60MB/s, so I can never get perfectly smooth playback straight from card

If you have verified the read speed and it should be good enough. then other things to try are:

1. Disable the histogram by clicking on it
2. Turn off the vertical stripe correction
3. Remove all 1D and 3D LUTs

Finally, you can guarantee seeing every frame (no skipping) at a lower frame rate by changing out of the default drop-frame mode. Click the clock icon to a "frame" or press F.

There is a thread for discussions about MlRawViewer. You should move this question there:

When you do that, please include a screenshot giving a clear example of your "vertical black banding" because it's not clear exactly what that is from the description.

Sorry about the export folders bug. I have a fix for this now which will be included in 1.4.2, but for now you will have to use the drag-folder workaround found by @danne (nice one!)

Does anyone else have comments or feedback about the browser in 1.4.1? Is it working better than 1.4.0 did?

- perhaps it is possible to add a button for leaving the folder in the hierarchy. (Like /..) e.g. from c:/MLV/Files1 to c:/MLV - would be great because then there is no need for searching the right keystroke.

There is an up arrow icon (button) next to the filename which does that - same as shift key

MlRawViewer 1.4.1 is now available for testing from

The same warnings as for 1.4.0 apply. Don't expect this to be bug free.

Major changes since 1.4.0:
- Browser should be much more responsive when browsing root dirs
- Folders show number of files and a selection of thumbnails they contain
- Thumbnails use set white balance & exposure, and update again after files are viewed
- J/K keys can be used to jump quickly to sibling directories in Browser
- Fixed crash when opening files with paths containing non-ASCII characters
- Various performance improvements

Can you open the app with an existing MLV file so it doesn't go to the browser first? Then open the browser. It should be in the same folder as the file.

kudos @baldand :D once again you realized a thing i wanted to code as well :)
regards chmee


mlvfs is now compatible with resolve and now it is a breeze to work with those converted files.
...with mlvfs all the stripes were gone

It's really great that MLVFS is doing such a good job with the MLV->DNG->Resolve/Premiere path.

I will probably recommend people to use that for DNG export rather than MlRawViewer, and instead try to focus on improving viewing/reviewing use cases, and maybe something else.

Forgot to say: with "latest", I meant 1.3.3. This is also where the trace is taken from.

Could you test with 1.3.4 as well and verify it still happens there? That had some fixes for .RAW files.

Thanks all for the testing and detailed feedback about 1.4.0. It's very helpful.

@all, regarding the slowness when going towards the root directories. I will try to find a good solution that lets me limit the number of shown folders to just the relevant ones but without making the UI slow/unresponsive as it is now.

@MAVisuals, @kgv5 maybe it would help you to think of the browser as a temporary dialog on top of the viewer. The X (or BACKSPACE) key closes the browser and returns to the viewer. But when the app is launched without a file, when the browser closes without selection something, there is nothing to view, hence the app is closed. Maybe I can do something visually to make more explicit this kind of "mental model" for the UI.

@Danne, @feureau I agree the export folder is not so intuitive due to lack of a way to "choose" a final folder. In fact the model here is continuous choice - every time you navigate you have changed the folder, so when you close the browser with X or BACKSPACE, it is set to use the folder you were last viewing. In other words, there is no "cancel" option. This is sadly a bit opposite to the behaviour in the file choosing modes.

@Danne, sorry for the repeated failures with accented characters. I will try to fix it (again)

Pages: 1 [2] 3 4 ... 17