sudo apt-get install build-essential python-opengl python-numpy
python setup.py build_ext --inplace
chmod +x mlrawviewer.py
./mlrawviewer.py /path/to/file.MLV [/path/to/encodedfile.MOV]
Did you make that program baldand (haven't it tested yet).
D:\Users\g3gg0>"c:\Program Files (x86)\Python\python.exe" d:\Users\g3gg0\Desktop\y\setup.py build
running build
running build_ext
building 'bitunpack' extension
error: Unable to find vcvarsall.bat
D:\Users\g3gg0>"c:\Program Files (x86)\Python\python.exe" d:\Users\g3gg0\Desktop\y\mlrawviewer.py
File "d:\Users\g3gg0\Desktop\y\mlrawviewer.py", line 32
except Exception,err:
^
SyntaxError: invalid syntax
cosmo@cosmo:~/Downloads/mlrawviewer-1-0-0$ ./mlrawviewer.py ~/Videos/M12-1345.MLV
Falling back to Numpy for bit unpacking operations.
Consider compiling bitunpack module for faster conversion.
Opening MLV file /home/cosmo/Videos/M12-1345.MLV
Could not open file /home/cosmo/Videos/M12-1345.MLV. Error:1280922707
cosmo@cosmo:~/Downloads/mlrawviewer-1-0-0$ ./mlrawviewer.py ~/Videos/M12-1345.MLV
Opening MLV file /home/cosmo/Videos/M12-1345.MLV
Could not open file /home/cosmo/Videos/M12-1345.MLV. Error:1280922707
for me I got;Code: [Select]cosmo@cosmo:~/Downloads/mlrawviewer-1-0-0$ ./mlrawviewer.py ~/Videos/M12-1345.MLV
Falling back to Numpy for bit unpacking operations.
Consider compiling bitunpack module for faster conversion.
Opening MLV file /home/cosmo/Videos/M12-1345.MLV
Could not open file /home/cosmo/Videos/M12-1345.MLV. Error:1280922707
and with the bitunpack.soCode: [Select]cosmo@cosmo:~/Downloads/mlrawviewer-1-0-0$ ./mlrawviewer.py ~/Videos/M12-1345.MLV
Opening MLV file /home/cosmo/Videos/M12-1345.MLV
Could not open file /home/cosmo/Videos/M12-1345.MLV. Error:1280922707
Bug:
When using nearest to de-mosaic instead of bi-linear, everything comes out blue
Found the solution:
You didnt "-black" on the other colours.
@baldand:
do you pre-index the MLV blocks before processing?
alex@thinkpad:~/src/mlrawviewer$ python mlrawviewer.py ./M08-1336.RAW
MlRawViewer v1.0.1
(c) Andrew Baldwin & contributors 2013
Falling back to Numpy for bit unpacking operations.
Consider compiling bitunpack module for faster conversion.
Opening MLRAW file ./M08-1336.RAW
Width: 1920 Height: 1080 Frames: 60
Traceback (most recent call last):
File "/home/alex/src/mlrawviewer/GLCompute.py", line 223, in __draw
self.onDraw(w,h)
File "mlrawviewer.py", line 186, in onDraw
self.init()
File "mlrawviewer.py", line 178, in init
self.demosaic = DemosaicScene(self._raw,size=(self._raw.width(),self._raw.height()))
File "mlrawviewer.py", line 93, in __init__
self.rawUploadTex = GLCompute.Texture((self.raw.width(),self.raw.height()),rgbadata=frame0.rawimage,hasalpha=False,mono=True,sixteen=True)
File "/home/alex/src/mlrawviewer/GLCompute.py", line 85, in __init__
glTexImage2D(GL_TEXTURE_2D,0,GL_R32F,self.width,self.height,0,GL_RED,GL_UNSIGNED_SHORT,rgbadata)
File "/usr/local/lib/python2.6/dist-packages/PyOpenGL-3.0.2-py2.6.egg/OpenGL/latebind.py", line 45, in __call__
return self._finalCall( *args, **named )
File "/usr/local/lib/python2.6/dist-packages/PyOpenGL-3.0.2-py2.6.egg/OpenGL/wrapper.py", line 792, in wrapperCall
raise err
GLError: GLError(
err = 1281,
description = 'invalid value',
baseOperation = glTexImage2D,
pyArgs = (
GL_TEXTURE_2D,
0,
GL_R32F,
1920,
1080,
0,
GL_RED,
GL_UNSIGNED_SHORT,
array([[16382, 16382, 16382, ..., 163...,
),
cArgs = (
GL_TEXTURE_2D,
0,
GL_R32F,
1920,
1080,
0,
GL_RED,
GL_UNSIGNED_SHORT,
array([[16382, 16382, 16382, ..., 163...,
),
cArguments = (
GL_TEXTURE_2D,
0,
GL_R32F,
1920,
1080,
0,
GL_RED,
GL_UNSIGNED_SHORT,
array([[16382, 16382, 16382, ..., 163...,
)
)
print self.width, self.height
print rgbadata
print glGetIntegerv(GL_MAX_TEXTURE_SIZE)
=>
1920 1080
[[16382 16382 16382 ..., 16382 16382 16382]
[16382 16382 16382 ..., 16382 16382 16382]
[16382 16382 16382 ..., 16382 16382 16382]
...,
[ 9928 6171 11226 ..., 6250 11173 6021]
[10345 6163 10482 ..., 5800 10179 6075]
[10423 5907 9725 ..., 5539 10362 5808]]
4096
diff --git a/GLCompute.py b/GLCompute.py
index 161cc79..73575f6 100755
--- a/GLCompute.py
+++ b/GLCompute.py
@@ -80,7 +80,7 @@ class Texture:
elif not hasalpha and not mono and fp:
glTexImage2D(GL_TEXTURE_2D,0,GL_RGB32F,self.width,self.height,0,GL_RGB,GL_FLOAT,None)
elif mono and not sixteen:
- glTexImage2D(GL_TEXTURE_2D,0,GL_RED,self.width,self.height,0,GL_RED,GL_UNSIGNED_BYTE,rgbadata)
+ glTexImage2D(GL_TEXTURE_2D,0,GL_RGB,self.width,self.height,0,GL_RED,GL_UNSIGNED_BYTE,rgbadata)
elif mono and sixteen:
glTexImage2D(GL_TEXTURE_2D,0,GL_R16,self.width,self.height,0,GL_RED,GL_UNSIGNED_SHORT,rgbadata)
elif not mono and sixteen:
diff --git a/ShaderText.py b/ShaderText.py
index dd82c4b..dbcc56e 100644
--- a/ShaderText.py
+++ b/ShaderText.py
@@ -32,7 +32,7 @@ attribute vec4 axyuv;
attribute vec4 argba;
attribute vec4 actmg;
varying vec2 texcoord;
-uniform mat4x4 matrix;
+uniform mat4 matrix;
uniform float opacity;
uniform vec4 urgba;
varying vec4 rgba;
diff --git a/mlrawviewer.py b/mlrawviewer.py
index d7609b1..d3082b4 100755
--- a/mlrawviewer.py
+++ b/mlrawviewer.py
@@ -90,8 +90,8 @@ class DemosaicScene(GLCompute.Scene):
frame0.convert()
self.raw.preloadFrame(f)
print "Width:",self.raw.width(),"Height:",self.raw.height(),"Frames:",self.raw.frames()
- self.rawUploadTex = GLCompute.Texture((self.raw.width(),self.raw.height()),rgbadata=frame0.rawimage,hasalpha=False,mono=True,sixteen=True)
- self.rgbImage = GLCompute.Texture((self.raw.width(),self.raw.height()),None,hasalpha=False,mono=False,sixteen=True,fp=True)
+ self.rawUploadTex = GLCompute.Texture((self.raw.width(),self.raw.height()),rgbadata=frame0.rawimage,hasalpha=False,mono=True,sixteen=False)
+ self.rgbImage = GLCompute.Texture((self.raw.width(),self.raw.height()),None,hasalpha=False,mono=False,sixteen=False,fp=False)
demosaicer = Demosaicer(raw,self.rawUploadTex)
print "Using",demosaicer.shader.demosaic_type,"demosaic algorithm"
self.drawables.append(demosaicer)
I've split the topic; feel free to add a link to it in the old one, and edit the first post to keep things updated.
Small remark: I've noticed you are updating the black level on the fly, and you are computing it as MIN(all_pixels). This is incorrect for the following reasons:
- some cameras have bad pixels with raw value = 0 (okay, you can filter these out easily)
- if the image is exposed to the right, you will end up with a black value much higher than normal, and this will cause strong green cast in shadows
- if the image is exposed to the left, you will read something way below the real black level (you have a Gaussian noise, stdev something around 15, so you can end up easily 100 units below the correct value => pink cast; also, the minimum is not statistically robust so the level will change while playing).
So, I strongly recommend you to use the "EXIF" black level. If that one is wrong, it's a bug in ML, and must be reported and fixed there, not worked around in post software.
Fixed my video card issues and the black level problem.
https://bitbucket.org/baldand/mlrawviewer/pull-request/4/small-fixes
Next up , I'm planning to integrate CPU-based AMaZE demosaicing (which is much slower than GPU demosaicing, but better looking) for using to export sections of a video through ffmpeg, e.g. to ProRes files.
I'll want my modified soft film curve from ufraw (http://www.magiclantern.fm/forum/index.php?topic=5197.msg91513#msg91513) :D
Would it be possible to use this to compile it for the various platforms?
http://www.pyinstaller.org/
Would it be possible to use this to compile it for the various platforms?
http://www.pyinstaller.org/
Microsoft Windows XP [Version 5.1.2600]
C:\Documents and Settings\Cosmo\Desktop\mlrawviewer>python -B mlrawviewer.py "c:
\Documents and Settings\Cosmo\Desktop\M14-2120.MLV"
MlRawViewer v1.0.1
(c) Andrew Baldwin & contributors 2013
Falling back to Numpy for bit unpacking operations.
Consider compiling bitunpack module for faster conversion and export.
Opening MLV file c:\Documents and Settings\Cosmo\Desktop\M14-2120.MLV
Black level: 2048
Traceback (most recent call last):
File "mlrawviewer.py", line 307, in <module>
sys.exit(main())
File "mlrawviewer.py", line 302, in main
rmc = Viewer(r)
File "mlrawviewer.py", line 182, in __init__
super(Viewer,self).__init__(width=userWidth,height=int(userWidth*self.vidAsp
ect),**kwds)
File "C:\Documents and Settings\Cosmo\Desktop\mlrawviewer\GLCompute.py", line
183, in __init__
glutInit(sys.argv)
File "C:\Python27\lib\site-packages\OpenGL\GLUT\special.py", line 324, in glut
Init
_base_glutInit( ctypes.byref(count), holder )
TypeError: 'NoneType' object is not callable
diff --git a/GLCompute.py b/GLCompute.py
index 811afb7..4e6601a 100755
--- a/GLCompute.py
+++ b/GLCompute.py
@@ -86,7 +86,8 @@ class Texture:
try: glTexImage2D(GL_TEXTURE_2D,0,GL_R16,self.width,self.height,0,GL_RED,GL_UNSIGNED_SHORT,rgbadata)
except GLError: glTexImage2D(GL_TEXTURE_2D,0,GL_RGB16,self.width,self.height,0,GL_RED,GL_UNSIGNED_SHORT,rgbadata)
elif not mono and sixteen:
- glTexImage2D(GL_TEXTURE_2D,0,GL_RGB32F,self.width,self.height,0,GL_RGB,GL_UNSIGNED_SHORT,rgbadata)
+ try: glTexImage2D(GL_TEXTURE_2D,0,GL_RGB32F,self.width,self.height,0,GL_RGB,GL_UNSIGNED_SHORT,rgbadata)
+ except GLError: glTexImage2D(GL_TEXTURE_2D,0,GL_RGB16,self.width,self.height,0,GL_RGB,GL_UNSIGNED_SHORT,rgbadata)
else:
glTexImage2D(GL_TEXTURE_2D,0,GL_RGB,self.width,self.height,0,GL_RGB,GL_UNSIGNED_BYTE,rgbadata)
if mipmap:
I can test an exe on win 8 if you can provide one?
Mac :P ::)Start coding then :P
I added encoding to ProRes using ffmpeg. It needs a newish versions of ffmpeg for that to work. Only tested on Linux so far.
python setup.py build
ln -s build/lib.macosx-10.9-intel-2.7/bitunpack.so .
7z x ffmpeg-2.1.1.7z
(if you need 7z, use homebrew and "brew install p7zip")I pushed a small change now so it will use an ffmpeg in the same directory as the script in preference to one on the path.That's a good idea. There are plenty of static daily builds around.
Fantastic!!!
How to install the ffmpeg?Unzip and click on it?
@baldand
Thank you for helping out Mac! My install crashes as soon as I drag a .raw file onto the app icon. Do I still need to install Python etc. before I install this app? I'm a little confused – sorry!
I'm on OSX 10.7.5
Thanks!
The Mac install package includes ffmpeg. ... It should include everything needed - no need to install a python unless you are building it from source.
Thanks for the clarification – I'll persevere! :)
@baldand – PS Should the 'Frameworks' folder inside the package be empty? Mine is! :o
I have checked the exported .mov but it is 422 (HQ) Is this expected behaviour?
I had a go at making an installable version of the app for Mac.
https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1.0.1_alpha.dmg
Thank you, this is awesome and definitely a step in the right direction.
.raw files play back smoother on my (aging) 2ghz MBP than .mlv files, is this expected behavior?
also tested the viewer with a clip from a 550D at work.(my 5d mark 3 is at home)
Seems the issue with strange frameissue/encoding is because of the framerate. 24fps is ok but 25fps causes the same issue as on my 5d mark 3.
This viewer/encoder is amazing
Thanks!
/D
I have checked the exported .mov but it is 422 (HQ) Is this expected behaviour?
OSX 10.9
Anyone on OSX 10.7.5 able to run this and help me get it working? It crashes for me…
It looks great though! (Thanks to @baldand)
But, when playing recorded 1280x720 both 24 and 25fps fails and recreates the problem I had with the first 5d mark 3 file.
Here,s one of the failing 24fps examples
http://sprend.com/download.htm?C=2b1ff5b9b7484b2e9f18c83b04f9f72b
/D
try to run the binary version from the command line.
That's clever! Thanks. It crashes again, but terminal reports:Thanks. Sadly not enough to pinpoint the problem.
Segmentation fault: 11
I would suggest trying to follow the instructions from http://www.magiclantern.fm/forum/index.php?topic=9560.msg91924#msg91924 (http://www.magiclantern.fm/forum/index.php?topic=9560.msg91924#msg91924) to compile it from source.
I have had an earlier version working that way on 10.7.x before I upgraded to 10.9.
Excellent work!!
@ baldand: Can you please update your opening post with the latest links and findings of you research? By doing this the new comers do not have to read the entire post to get up-to-speed.
Thanks
I have tested with quicktime and final cut pro,it show as a codec ProRes 442 (HQ).Do you have any other alternatives?
(https://www.magiclantern.fm/forum/proxy.php?request=https%3A%2F%2Fbitbucket-assetroot.s3.amazonaws.com%2Fc%2Fphotos%2F2013%2FDec%2F13%2Fmlrawviewer-logo-999853879-7_avatar.png&hash=3616913861ccc90603e4fe0bbc7f2b95)
MlRawViewer
MlRawViewer is a cross-platform viewer for raw video files produced by Magic Lantern.
It supports both the original RAW format, and the newer MLV (RAW v2.0) format in both single and multi-file versions.
Features/usage
- RAW and MLV playback at up to 25FPS (if you have fast file read and modest GPU), single and multi-file
- Progress bar and timestamp overlay
- Pause playback using SPACE key
- Step forward and backward through frames by one second (LEFT/RIGHT cursor keys) or one frame (,/. keys) while playing or paused
- Brightness control while playing using UP/DOWN cursor keys
- Fast GPU Bilinear demosaicing for playback
- High-quality (but slow) CPU demosaicing (AMaZE) when paused or enabled (Q key)
- Encoding frame sequences to ProRes using ffmpeg with E key
- White Balance adjustments. Keys: 1=WhiteFluoro,2=Daylight,3=Cloudy,4=Tungsten,0=None
- Exit viewer with ESC key
Linux Installation & Usage
Any normal Linux distribution (32 or 64bit) should work, but only Ubuntu 12.04 64bit has been extensively tested. NVIDIA or AMD GPUs using properietary drivers should work best. You may be able to use Intel GPUS, but problems may increase the older the GPU.
You should get the source code either with git (see below) or from a snapshot: https://bitbucket.org/baldand/mlrawviewer/get/master.tar.bz2 (https://bitbucket.org/baldand/mlrawviewer/get/master.tar.bz2)
You should use python 2.7 (not python 3), and install pyOpenGL and numpy package. On Ubuntu/Debian do:Code: [Select]sudo apt-get install build-essential python-opengl python-numpy
python setup.py build_ext --inplace
chmod +x mlrawviewer.py
./mlrawviewer.py /path/to/file.MLV [/path/to/encodedfile.MOV]
Then the video should appear and playback immediately. See above for keys.
Mac OS X 10.9 Installation and Usage
A binary release or source build can be used. The binary release is only known to work with 10.9.x. Source builds may work with earlier OS X releases.
NVIDIA and AMD GPUs will work best. Intel GPUs may work, but problems have been reported with e.g. HD3000.
Download the DMG from https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1.0.1_alpha.dmg (https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1.0.1_alpha.dmg)
Click the DMG to mount it, and drag the icon to your Applications folder.
The application cannot be opened directly. Instead, drag an MLV or RAW file into the app, or open a file using the app.
Windows 7 Installation and Usage
A binary release or source build can be used. The binary release is only known to work properly with Windows 7 (32bit or 64bit). Source builds may work with earlier Windows versions.
It has been run on Windows 8 with some success - files can be viewed, but it crashes when SPACE or Q key are pressed (problem in CPU demosaicing).
NVIDIA and AMD GPUs will work best. Intel GPUs may work, but problems have been seen with some older chips.
Download the zip from https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer-1_0_2_alpha-win32.zip (https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer-1_0_2_alpha-win32.zip)
Open the zip, and copy mlrawviewer.exe to somewhere in your machine.
The application cannot be run directly. Instead, drag an MLV or RAW file into the app icon (or a shortcut), or set up a file association so it opens when you double click a video file.
Alternatively you can run it from a command line, which also allows you to specify the encoding file name.
A log file (mlrawviewer.log) is generated when/where the program is run. In case of problems, please check and share the log to help the developers identify the causes.
Implementation details
The program is written in python, and makes use of OpenGL for image processing in order to be able to display videos at their intended frame rate. This also depends on you having good file read speed in your computer.
Almost everything (apart from bitunpacking and CPU demosaicing) is written in python, so it is quite easy to install, modify and extend in case you are familiar with that language.
The license for the program source code excluding AMaZE is BSD-style.
The license for the AMaZE demosaicer (amaze_demosaic_RT.c) is GPLv3
The license for ffmpeg is GPLv3.
Hence, binary releases of MlRawViewer must be GPLv3.
Testing, feedback and code contributions are welcome.
Home page: https://bitbucket.org/baldand/mlrawviewer
Git repo: https://baldand@bitbucket.org/baldand/mlrawviewer.git
Bug tracker: https://bitbucket.org/baldand/mlrawviewer/issues
I can confirm that the MlRawViewer does not work in 10.8.5, I drag the MLV file onto the program and the program quits unexpectedly. Tried other ways to open it, nothing. Guess I'll have to install a separate linux system and dual boot it on my macbook pro, not going to be upgrading to Apple's stupid 10.9.X
LINUX ALL THE WAY
i am really impressed, very good work :)
:D :D :D :D Works perfectly here on win 7 64 when playing raw and mlv from my ssd ! Just a maybe : how about support for mlv.snd Sound ? Would be the absolute point of maturing of MLV and Magiclantern RAW !
Thanks for reading and your amazing work !
win7 x64, nvidia card: works like a charm
Hi Baldand. Here,s a .MLV containing audio. Short and in 1280x720p since I,m on a mobilephone network.
https://drive.google.com/file/d/0B4tCJMlOYfirOW95a3NHeHE5cGM/edit?usp=sharing
Thanks for efforts!
/D
I think you probably would be able to get it working ok on 10.8.5 by building from source following the steps here (assuming you have XCode & the command line compiler):
http://www.magiclantern.fm/forum/index.php?topic=9560.msg91924#msg91924 (http://www.magiclantern.fm/forum/index.php?topic=9560.msg91924#msg91924)
Is it possible to apply a LUT during export?That would be awesome.
imagine the workflow.
Load the file with MlRawViewer>apply LUT>export as ProRes 444>Grade in your favourite application!!!
I would like to make that possible eventually.
There's an enhancement issue for it in bitbucket. Feel free to attach a LUT file as an attachment that I can use for testing the feature if/when it gets implemented.
https://bitbucket.org/baldand/mlrawviewer/issue/18/log-output-and-3d-luts-should-be-supported (https://bitbucket.org/baldand/mlrawviewer/issue/18/log-output-and-3d-luts-should-be-supported)
1. This is something I want to work on for the GUI, which still isn't functioning how it needs to.
2. Possibly, it can essentially convert to anything, at the moment only ffmpeg is coded in.
3. Being worked on (not by me).
4. Being worked on by me. If you pull the latest git and run: mlrawgui.py
5. Should already be available, when you're typing where you want it to be saved to.
6. Eventually in the gui, still being worked on.
7. I personally can't answer this one.
We all know he was stating the obvious, but there is no need to be a jerk about it.
Any chance you can update this to play the embedded audio? :-)
1. select in/outpoint
2. convert that selection to dngs
3. audio support
4. a lightweight gui with a small file browser and the possibility to select the files directly..
5. a way to select an output folder
6. convert button
7. spanned files
Finally, I made a new version of the Mac installer which I've tested on 10.7 and 10.9. I'm hoping it will work ok on 10.8 also. Anyone on an earlier OS X release than 10.9 that had troubles earlier, please try it out to see if you have more luck.
We all know he was stating the obvious, but there is no need to be a jerk about it. This viewer is amazing, and the developer doesn't seem to NOT be asking for user feedback.To this I am going to say; WTF?
Is there a way to change the encoding output to 23.976 fps? If not, is this something that is planned? Also, are there plans to allow vertical scaling of the prores output to unsquash 50/60p files? Again, well done!
If you are using Win, you'll need to wait for a new installer or install from source.
It would be possible to up-scale the content when encoding, but I suppose we aren't 100% confident right now that we know the correct scale factors for all cameras so that this could work reliably automatically.
Also, are there plans to allow vertical scaling of the prores output to unsquash 50/60p files?You can watch the video un-squashed by pressing 'A' (whether it un-squashes it correctly though).
To this I am going to say; WTF?Sorry, I think at first glance it just appeared to be someone complaining.
And see baldand's response.
Sorry, I think at first glance it just appeared to be someone complaining.Yes... I was complaining how I was working on the gui...
I am not sure if it has been mentioned or maybe I am missing something, but can we extract a raw/mlv to automatically go to the folder where the raw/mlv file is located? Currently, I have to navigate a loy to relocate it. And also have the ability to create a new subfolder using the name of the raw/mlv file?
@baldand Please excuse my ignorance, but has the mac.app package on your bitbucket site been updated now to read dngs, and mlv with audio? This is far and away the neatest viewer so far. Thanks a million!
tim
Rather than bug people with a lot of small releases containing in-progress functionality, I chose to hold off until there was a bit more to include. But if there is demand for just CinemaDNG playback I could of course make new Mac/Win packages from the current code.
But if there is demand for just CinemaDNG playbackThere is.... but does that mean I cannot (right now) play back a folder with ( non-cinema) DNG's that I converted with mlv_dump or raw2dng?
Directories containing "CinemaDNG" sequences can be played the same as RAW and MLV filesand how do I specify that? best would be if it would work when I give the path to one DNG and also if I give the path to the surrounding folder
./mlrawviewer.py ../Canon_5D_Mark_III_Magic_Lantern_Raw_Video_files/does that mean it generates a .mov for playing back the DNG's?
MlRawViewer v1.0.3 alpha
(c) Andrew Baldwin & contributors 2013
Using GLUT instead of GLFW. Some features may be disabled.
outfilename for CDNG: ../Canon_5D_Mark_III_Magic_Lantern_Raw_Video_files.MOV
Opening CinemaDNG ../Canon_5D_Mark_III_Magic_Lantern_Raw_Video_files/
Could not open file ../Canon_5D_Mark_III_Magic_Lantern_Raw_Video_files/. Error:51044
Using GLUT instead of GLFW. Some features may be disabled.what am I missing there? I just have glfw2 (libglfw.so.2.6) in ubuntu 12.04...,even 14.04 just has 2.7.2-1 would that be also sufficient?
There is.... but does that mean I cannot (right now) play back a folder with ( non-cinema) DNG's that I converted with mlv_dump or raw2dng?
how do I specify that? best would be if it would work when I give the path to one DNG and also if I give the path to the surrounding folder
does that mean it generates a .mov for playing back the DNG's?
what am I missing there? I just have glfw2 (libglfw.so.2.6) in ubuntu 12.04...,even 14.04 just has 2.7.2-1 would that be also sufficient?
The current code in git should pass the frame rate from the source file to the encoder, but only the Mac 1.0.3 DMG binary includes that - not the current windows binary - and I have to admit I haven't tested it with 23.976. If you are using Mac, upgrade to the 1.0.3 to try that. If you are using Win, you'll need to wait for a new installer or install from source.
Will the next release you are working on contain the new installer for Windows that supports Prores output encoding to 23.976? This is the only thing preventing me from utilizing the encoding capablility. Also, will there be a way of batch encoding a group of files, such as all the files in a folder (I'm a windows user)?
Also I would like to make a recommendation about white balance.We do not need presets, we need 4 keys (2 for temperature up/down and 2 for green/magenta +/- like all RAW Converters).what do you think?
Or what about a shortcut for "next" and "prev" clip in the folder?
update*
changing from .mlv to the next clip (O,P buttons) results in the next clip keeping the first played clips name. This results in merging the audio from the first file to the next file being exported. For now I have to close down the app and restart to get the names from the files played in the app. GOing from .RAW won,t let me change to the next clip at all.
Mac os X 10.9, 5d mark 3
1)When you try to convert to log ,the shadows get a pattern noise.Needs fine-tuning.Let me know if I can help.
2)When you try to export from a later frame it does not create a file and goes to loop.
Also I would like to mention that highlight recovery looks very good.
btw - can you try to honor the MLVI videoClass field?
...
currently the player crashes when you try to play a compressed video file.
i would just show an error message telling that the video format isnt supported.
One of the things I wish is that the app would open when you double-click on it on the Mac and perhaps display a window where files can be dragged on as opposed to dragging the file on the app icon itself.
It would be extra awesome if, say I dragged 5 .raw files in the app, and it played them back sequentially. This would be extremely handy for reviewing takes.
(Eventually however, there should be an integrated browser view for this kind of thing. And a proper UI instead of keyboard commands only.)
(Eventually however, there should be an integrated browser view for this kind of thing. And a proper UI instead of keyboard commands only.)
Thanks, I will see if I can reproduce that.
There's no pattern noise processing so far. I agree something is needed, mainly for the vertical stripes. I would be happy to get a good sample file from you to test with.
I'll see if I can reproduce. Was this with or without sound, MLV or RAW?
Question: next / prev uses MY finder order or simply alphabetic?
This info is useful because we think of renaming the clips according to whats in there so I may end up ordering them by creation date for some reason-
– After indexing, the audio plays a few seconds (5s or so) then drops out while the image stream continues to play. Is this correct, or just my slow mac? (Toggling Drop frame works as intended)What CPU and GPU you have? How long is the WAV file that is created - is that full length?
– When Encoding (E) to a folder I am getting: myfile.mov, myfile.wav, and an extra timestamped .wav myfile_10.54.24.wav Is this expected behaviour?
– Also when encoding I randomly / sometimes get a myfile.mov.wav of a few bytes that doesn't open – but no completed movie. I then have to delete all files and start again.
Can't seem to figure out how to playback CDNG sequences. If I drag the first file on top of the app, the app doesn't recognize it and the Mac Finder simply thinks I want to move or copy my CDNG file to a new folder.
What CPU and GPU you have? How long is the WAV file that is created - is that full length?Slow machine here: MacMini 2.5khz i5 8gb AMD Radeon HD 6630M 256 MB. Will test it on my Mac Book Pro. Rogue WAV file is always 44bytes!
Is it totally random or connected to the clip?Seems random. Have tried several clips. *But* I notice that if I play a file say half way through and press E the encode fails in the way I described. If I press E right at the start of the play the file encodes properly! Maybe that's a clue?
I've been using the 1.0.4 in windows.. and when I open an MLV file, sometimes it opens fine, but other times the program opens and closes in a second, quitting, the audio file is created. When I go again, there it is fine! Here is a log:
Would it be too much trouble to add a bar with controls? Or maybe that the overlay progressbar shows then the mouse is over the window? Or a key shortcut to hide and unhide it? When shooting 2.35:1, the video is not too tall, and the bar covers a good amount of the frame!
Also, the repeat function.. can it be disabled??
Another.. would it be too much trouble for the program to delete the .wav file after we close it? It happens that if you have a neat folder structure with MLV files, some will have wav files and some won't..
And last but not least.. in windows, do I have command line options? As I have my batch converter.. maybe those can be useful for comunicating with your program..
So the FPS number is interpreted as 29.776 instead of 21 fps. Have you got any ideas about how to fix this?
On version 1.0.2 I could choose RAW/MLV files to open default with MLRawViewer, but on 1.0.4 I have to drag and drop each file and next/prev does not work.
Sorry if this is a dumb question, but here goes- can I export mlv's to cinema dng's with sound on my Mac? Can't seem to find the answer anywhere.
Thanks for the great app!!!
You should be able to configure Windows to open mlrawviewer by default for any .RAW or .MLV files.
Try right clicking on a file, and choose "Open with..." to bring up the association options.
Hi, i have try the last version and it open some window and then it close, almost you can't see it...
Does encoding start from where you press E? I'm trying to save time and dump out to pro-res, but want to tweak sync/wb first. Just pause it and seek around?
I guess GUI will do wonders here for doing it in batch... The videos are coming out 4:4:4 and keying nicely. Decided to nudge after I pick whichever takes I want, i think its only a few frames difference. Its much slower than raw2cineform but the results are de-bayered correctly. Would be cool if the amazed frames could be sent to cineform since they're taking forever to implement any decent debayer.
Are you using Windows? I had to disable multithreaded AMaZE on Windows as it was crashing on Win8 (doh). On Linux it should use all cores and be a bit faster.
My question is, to get the best quality from this, should we use the build in encoder, or should we export as dng and then render video using something like avid DNxHD codec?
The built in encoder is ffmpeg/avconv. The settings can be tweaked so you can get whatever quality you like, and it essentially be the equivalent of exporting to dng then converting.
It all depends on your preferred work flow really.
Is there a thread showing how to pull the best quality out of the mlv using MlRawViewer? I haven't seen it. Maybe I missed it?
Extremly good viewer! I'm only missing a Fullscreen mode. You can maximize the window but fullscreen would be nicer. I would vote for Ctrl+f to toggle as in resolve :D.
/Cheers!
Extremly good viewer! I'm only missing a Fullscreen mode. You can maximize the window but fullscreen would be nicer. I would vote for Ctrl+f to toggle as in resolve :D.
/Cheers!
aace: I did actually look for that on the first page. And now that you say It's there I still cant find it? Am i blind or is the shortcut for fullscreen missing?
aace: I did actually look for that on the first page. And now that you say It's there I still cant find it? Am i blind or is the shortcut for fullscreen missing?
So I kindly ask again: is this just me, do I have to set some settings or is this feature currently not workin? :)
This happens after closing the viewer (clicking the red cross on Windows or using ESC-key). When I afterwards drop another MLV onto the .exe the window appears, but is black. RAM usage increases and after about 10sec mlrawviewer closes.
If I drop the file again, it will be played without problems.
I noticed when I double click the .exe between each MLV (of course producing an error in the log) the next MLV I drop will be played without issues.
Surprisingly the black window problem does not create an entry inside the error log.
This happens on an ATI MobilityRadeon Maybe the OpenCL / OpenGL is not shut down cleanly??
Anyway, in theory mlrawviewer should be able to play that combination, though you probably need to launch it from the command line giving the directory for the DNGs followed by the full path to the WAV file.
How would I do this on the mac?
Open a terminal, and go into the /Applications folder, and from there into the MlRawViewer.app directory to find the mlrawviewer binary (it's in a subdirectory).
Then launch it with (replacing the path names...):
./mlrawviewer /path/to/CDNG/directory /optional/path/to/audio.wav
(In case the paths have spaces in, put quotes around them, e.g. "/path/to/dir with spaces/")
not working. i don't know terminal too well though, so may be missing obvious steps.
is there a guide anywhere on how to do this? getting the wav out of the .MLV is easy enough (tho its one at a time... no batch options?)... but i still need the DNGs, instead of a prores file.
Hold on, are you trying to play DNGs, or extract DNGs from your MLV?ah, yes. found thread on MLV converter.
MlRawViewer can play CDNG (though it's not well integrated on Mac yet). It can't yet extract them but there are other tools that can - mainly mlv_dump.
Hi baldand,
I've seen a lot of changes in your bitbucket repo since 1.0.4. Do you have any plans to compile a new build in near future?
I've seen a lot of changes in your bitbucket repo since 1.0.4. Do you have any plans to compile a new build in near future?
Hi baldand,
I've seen a lot of changes in your bitbucket repo since 1.0.4. Do you have any plans to compile a new build in near future?
Hi baldand !
It will be nice if moving to 64 bit or with the GUI even if not perfect, I am ready to give feed back or close my mouth :-X or even still 32 bit but fix the last bug.
Yes.
A better GUI will be the next major improvement. It is already implemented in bitbucket.
But is there some reason why you need a 64bit build for Windows? The program is not so memory hungry that it would benefit much, and performance is mostly depending on your GPU.
...........
I am also looking forward to the next release, and please add in and out points!! I think that would be a main feature for converting stuff
Hi Baldand. Really like your app. Looking forward for your upcoming achievements. One question on my mind is about batchfunctionality. If It,s like now a simple inpoint and to start encoding from current frame would do fine. However, the question is what to do next when the conversion starts. Instead of waiting for conversion to finish I want to get on with the rest of my files. Would be awesome to maybe queue the files and when all settings are applied to all files being able to start the conversion queue from there. This might be too hard to implement and maybe this little "dream" have been discussed already.
Thanks again for all your work on this. Still the best rawviewer by far.
Testing with MLV and audio (ML Feb 10 build) on OSX (latest): for a ~23GB recording (> 4GB+exFat), during playback the audio cuts out at 1:50; when encoding to ProRes it cuts out around the same time. The fully extracted .wav file is OK (4m30s). Full audio file matched video correctly in PPro CC.
CPU utilization shows ffmpeg running around 143% and the host app running at 97%. If there's any way to multithread deBayer, that would help speed up ProRes output (tested on 4-core MBP (late 2013- fast CPU option)). My 2010 MacPro 12-core with AE+ACR runs 1/4 real-time (full CPU utilization): I believe this MBP has faster CPUs and SSD, so I don't think the MacPro will run your tool faster (will test). Would be nice if this tool ran as fast or faster than ACR+AE :) (MlRawViewer is about 1/2 as fast currently).
The AMaZE deBayer looks very good- appears to do a better job than ACR (AHD variant?), especially on super high contrast edges (where ACR looks strange- color/edge issue).
Vertical line removal, denoise, and perhaps sharpening during deBayer would be nice to see (looks reasonably sharp as is, and sharpens OK in post; might be possible to get higher quality sharpening as part of deBayer step (e.g. ACR sharpening looks better than post sharpening).
A film-like highlight roll-off option would be more useful than the current tone-mapping option...
A command line option to allow direct converting to ProRes would allow for scripting/batching (tried calling the compiled exe from the shell- didn't work).
Your tool brings the 5D3 one step closer to being a (useful) baby Alexa 8)
why does it keep connecting to bit bucket?
Very cool!!Can somebody explain what the third icon from top does?Only the pattern needs fixing,after that no more adobe for me!
the play and pause icons seem backwards to me. i expect the pause icon to show while the clip is playing and the play icon to show when the clip is paused. most app works like that.
when I click on the exe file, i expect the app to open up and nothing happens. i see that i can drop a file onto that exe and then it works. am i missing something on the way this works? i have mlv files in separate folders. do i have to copy and paste your exe to every mlv folder and then drag n drop on it? that seems to be a tedious way. isn't here a way to just open your app and then use an import function of some sort for single files? groups of files?
again, excuse my lack of understanding on this, but what else does the app do? It seems to only play back mlv raw files, some brightness control and color adjust. but then what? can i extract dng's? make prores proxies? i don't see any more menu items , drop downs or right click menus anywhere.
When the icon is a clock it will try to play in real time, dropping frames if needed. This mode is needed for playing audioStripes and pattern noise in shadow areas.
When the icon is a frame, it will play all frames so you don't miss anything (useful for checking if any frames are bad). This mode cannot play audio.
When you say "pattern", do you mean fixed pattern noise, or stripes, pink dots? Or something else?
Sound play in sync when playing in the app, but after exporting to prores it looses sync.
Questions. Anybody experienced problems with "unexpected error -10813" when trying to "change all" ponting to the app?
I,m on osx 10 mavericks on a macbook pro. I have older builds present as well but can,t seem to find any cache preferenses to clean. Maybe that,s what needed? Suggestions?
How do I play dng files by he way? Tried drag all of the to the app and also only the first one. Didn,t work.
*tried to "kill all" preferences and then open with but the app still doesn,t seems to be able to "change all" for a simplier workflow. Maybe not working on mac
I understand, as I had to think for a while when designing this.thanx for the reply. about the play/pause icons, it is obvious that the clip is playing by seeing it playing in the window and the frame numbers are changing as it plays to also confirm it is playing. So, do we also need to see the play arrow icon to know if a clip is playing? :-)
The model I went for is for all icons to consistently show the current app state rather than another state you can get to by clicking that icon. That means the play icon shows the arrow when playing, not when paused. It also means the icons can have more than two states (like the colour mapping).
On windows you should set the file associations for .MLV, .RAW and .DNG to the mlrawviewer.exe so that you can just click on the files to be opened automatically in the the viewer.
Make one copy of the MlRawViewer_1_1_0 directory, for instance in "c:\Program Files\"
Then find an example MLV/RAW/DNG file, right click, select "Open with" then "Choose default programs..." from the sub menu. Click "browse" on the dialog that opens, then find and select the mlrawviewer.exe.
In case this doesn't work for you (I've had problems in Win7), find the mlrawviewer.exe, right click and "Pin to taskbar", and drag the MLV/RAW/DNG file to the taskbar icon to teach Windows about the association. After that, you should be able to set the defaults.
It's primarily a real time player for MLV/RAW/CDNG files, which does not require the files to be converted first.
It can also convert marked regions of the files to ProRes (click the red button or E key).
More features may come in later versions.
thanx for the reply. about the play/pause icons, it is obvious that the clip is playing by seeing it playing in the window and the frame numbers are changing as it plays to also confirm it is playing. So, do we also need to see the play arrow icon to know if a clip is playing? :-)
Oh sounds bad. Have you tried moving or deleting the old versions of the tool? I'm not a heavy mac user, but this associating has been working for me with Mavericks, also with DNGs.
You should be able to drag one DNG file from a sequence onto the app icon, or doing "Open with". If that's not working, it may indicate another problem with the file associations or installation, since the app had to declare it handles .DNG files.
Maybe you should just delete all copies of MlRawViewer (including emptying the trash..) and reinstall 1.1.0?
Thanks for the report. Some more information could be useful:
- Is it obviously out of sync from the start (offset), or does it get more out of sync as the file plays (stretched)?
- Have you tried playing the ProRes file with different players and see the same thing?
- If you process the same file with e.g. mlv_dump and some DNG tool, is it in sync without any manual offset?
- Did you convert the whole file, or just a marked subsection? Is it out of sync in both cases?
- Which camera was the file made with?
(You can use the V/B/N/M keys to slide the audio, but I know that's not ideal if every track is out of sync for you)
export to dng using mlv_dump
- If you process the same file with e.g. mlv_dump and some DNG tool, is it in sync without any manual offset?
Yes, for the play icon this is the case. But it isn't for the other state icons like frame dropping & colour mapping. Those need to show the current state. The design decision I made was for all the icons to consistently show the current state.So, the button with the arrow icon indicates the clip is playing, as well as we can see it is playing and the frames numbers are changing at the bottom. What icon do we now click on to make it stop since there is nothing that shows this? Anyone else who knows the answer cannot reply. :) And, when the clip is paused and the well known symbol for pause is showing (a box usually means to stop), what icon do we click on to make it play the clip since there is nothing that shows indicating play? :)
Thanks for the quick reply.is now gone!
mlrawviewer is running as 2 threads. Both close when I hit ESC.
I am currently downloading the newest driver ...was really surprised that my current one is more than one year old. I will update this post with my results.
UPDATE:
- newest ATI driver installed: Still a pink frame and still the black window.
- I noticed that the black window does not appear when I drop the same MLV file on mlrawviewer again. It only happens with different files. Btw I have version 1.0.4 _alpha32 from the .zip as I can not build it on my own from the repository.
I just tried to run this app and it crashes on loading. I'm on OSX 10.9.2 on a current gen Macbook Pro retina 15" with 750M Nvidia card. Let me know if there's a fix. Thanks.
I just tried to run this app and it crashes on loading. I'm on OSX 10.9.2 on a current gen Macbook Pro retina 15" with 750M Nvidia card. Let me know if there's a fix. Thanks.I run the same setup. Works great. You do know you have to drag/drop the file onto the app?
i have the latest win 7 ver 1.1.2. Is it just me or is anyone else having trouble reading the new mov/dng icon? I have yo lean in closer to read it all the time. :) Can you make the text whiter and a little larger? The other items are easy to see since the are bigger simple graphic symbols.
i dont have that problem. my pro is i cant see the mark In and Out white bar clearly when i play clips that i shoot in bright sunlight.
It would be awesome if you could include a JPEG preview for those people on mac 10.9 mavericks. Not entirely sure how that works
i have the latest win 7 ver 1.1.2. Is it just me or is anyone else having trouble reading the new mov/dng icon? I have yo lean in closer to read it all the time. :) Can you make the text whiter and a little larger? The other items are easy to see since the are bigger simple graphic symbols.
Do you mean thumbnails in the individual DNG files, or something else?Yeah, essentially the option found in the adobe dng converter.
Yeah, essentially the option found in the adobe dng converter.
2. *EXPERIMENTAL* DNG export as alternative to MOV.
However, as you move forward on refining this, could I lobby you to consider CDNG instead of regular DNG? The reason why is that Adobe is likely about to fully support CDNG in Premiere Pro, and thanks to Blackmagic it's quickly becoming the de-facto standard for raw video files. My understanding is that the difference between DNG and CDNG is just in the header information which includes specific information as it relates to video.
@midphase could I ask you (or somebody else) to try out the DNG sequences being produced currently in Premiere Pro (which I don't have access to) and tell me what doesn't work or what needs adding? I've already tested in Resolve 10 and After Effects and they seem to import the sequences ok.
Is there a change log I can reference somewhere? I'm trying to keep track of the progress of this app. Which is awesome by the way.
noticed:I also saw that happen here yesterday trying the latest 1.1.2 ver on my win 7.
mouse cursor disappear after resize application window.
@baldand
the mystery behind cdng for premiere are not really the cdng-tags, but debiasing and maximizing values. possibly the delinearizationtable from bmcc-files can help. AND: of course the dng-files should be converted to 16, 12 or 10bit, because 14bit is no typical video-bitdepth, only supported by resolve (and acr as a photo->converter)
https://infogr.am/bmcc-delinearization-curve?src=web
and
http://www.magiclantern.fm/forum/index.php?topic=7122.msg105445#msg105445
regards chmee
When I use the "A" key to desqueeze my 1920 x 672 (60p) footage, the 1.4x de-squeeze is not enough to reach a vertical height of 1080. I believe you would need a 1.61 (1.6072 to be more precise) vertical stretch in order to bring the vertical height from 672 to 1080. Would it be possible for you to add 1.61 as another vertical stretch factor when toggling using the "A" key?
| Camera | Max 1080 | Max 720 | Squeeze |
| 5d3 | 1920x1280 | 1920x672 | 1.9x |
| 6D | 1808x1216 | 1792x568 | ?wat |
| 650D | 1728x1150 | 1728x694 | 1.657x |
| 7,60,600,550D | 1728x1156 | 1728x694 | 1.66x |
Thanks chmee. That should be enough info for me to work out what's needed for Premiere. I expect it's the 14bit data. I can easily make an option to pad to 16bit (though that will waste disk space)
That's the way RAWMagic handles it, but despite all the CDNG files being 16bit, Premiere still reads the files wrongly (they will import and playback, but there is a nasty pink overcast on all the footage which makes it kinda unusable).
Something is going on with the way Premiere is reading files generated by the Blackmagic Cameras vs. the files generated by ML CDNG.
PM me if you want me to give you some Blackmagic CDNG files to study.
5d3 1920x1280 1920x672 1.9x
That's the way RAWMagic handles it, but despite all the CDNG files being 16bit, Premiere still reads the files wrongly (they will import and playback, but there is a nasty pink overcast on all the footage which makes it kinda unusable).
Something is going on with the way Premiere is reading files generated by the Blackmagic Cameras vs. the files generated by ML CDNG.
PM me if you want me to give you some Blackmagic CDNG files to study.
the dng-support in premiere is a shame - its fixed on bmcc files. so best would be converting to 12bit/log (with the inverted table i linked) and leaving reconvertion to 16bit inside premiere with the same delinearizationtable..
My dngs are coming out Canon EOS instead of canon EOS 7D. Also 2 files got stuck converting... I tried to run a bunch of MLrawviewers at once, bad idea.
Changing the tag with exiftool gui causes a lockup after a certain number of files, gah. Its > ~420 files, exiftool hangs, then gui hangs.
hi Guys,
I start to use mlraw viewer to export to .mov,its worked perfectly.
since yesterday,its impossible to export anymore,the program freeze or crashes.
In the meantime I changed the preset on camera,and installed some program on the mac,like raw2dng.Since it doesnt work I re-install Mlraw viewer but no better.
I use a macbook air last version,I was wondering if its something to do with CPU?
the files to convert are on the local SSD and I try from an USB3 HDD.
the export button sometimes is vivid red,sometimes I cant click it,any case nothing exports.
Also when I play the mlv,it freeze after 3-4 seconds...Any help is welcome,cheers!
I shot a video on the Canon 50D.
I played it off the cf reader and the playback was smooth.
Now that I took the files off the cf card and put them on a hard drive, the play back is slow, skipping, and lagging.
@ baldand, could you add the keyboard keys functions to your first post please? somewhere at the end of your first post, for example :)... The way you have them in your Readme file(archive) gives a much easier view of which does what.
can it run on Android? 8)It can if you port it.
1.1.3 now availableAs always... Great!
- Now exports 16bit DNGs with per-frame metadata. Should directly import into PremierePro as well as Resolve/AE.
- S key switches between different anamorphic squeeze ratios (viewing only)
- MOV/DNG icon made clearer
- Mark line red instead of white so it shows up in bright scenes
See top post: http://www.magiclantern.fm/forum/index.php?topic=9560.msg91165#msg91165 (http://www.magiclantern.fm/forum/index.php?topic=9560.msg91165#msg91165)
I just tried the new version 1.1.3 of MlRawViewer, exported a couple of DNG sequences, and then imported the DNG sequences into Premiere Pro CC. Unfortunately, the highlights are pink, making footage unusable in Premiere unless there are no strong highlights in the footage. I tried both MLV and RAW files and both had the same issue. I can send you sample DNGs exhibiting this issue if you find it useful to your development. You are soooo close to providing a post processing tool that allows working directly with the DNGs in Premiere.
1.1.3 now available
- Now exports 16bit DNGs with per-frame metadata. Should directly import into PremierePro as well as Resolve/AE.
- S key switches between different anamorphic squeeze ratios (viewing only)
- MOV/DNG icon made clearer
- Mark line red instead of white so it shows up in bright scenes
See top post: http://www.magiclantern.fm/forum/index.php?topic=9560.msg91165#msg91165 (http://www.magiclantern.fm/forum/index.php?topic=9560.msg91165#msg91165)
GREAT JOB!!! this version resolves the bad pixel problem in Davinci Resolve importing (cdng) with some camera. (60D)
Thanks. ;D
That's good to hear! There is a very simple dead pixel detection/hiding I put in a while ago when I was doing something with raw from a 60D. I'm glad it's still working.
It seems the most practical method of post processing for Premiere users then would be then to export to ProRes using your Log curve, and then import into Premiere. Well at least that will be my preferred workflow unless the pink highlight issue is eventually solved.
-Will the ProRes exports eventually support queuing just like DNGs?
-Is the brightness control equivalent to an exposure control?
-Just wondering why there is no Tungsten white balance option. Also, it may be too much to ask, but would it be possible to add a white balance eyedropper/picker such as found in ACR, etc. to make it easier to find the correct white balance?
Anyway, terrific progress on your tool. So professionally developed and very efficient and refined. Much respect.
In old version 1.1.2 i've tested but bad pixel still exist. This is the news of the day man. I was waiting this fix since raw shooting is released.
Using 1.1.3 on a pc.
Hitting "W" key does nothing (I expected to select a directory).
Edit: I guess because I'm on Windows Vista?
I am using MlRawViewer 1.1.3 . Is there anyway to select which version of ProRes we can use use for a proxy export? Which version is it currently using? 444, HQ, etc.
Fast/lower quality proxies is not a feature that anyone has requested to the enhancements list: https://bitbucket.org/baldand/mlrawviewer/issues (https://bitbucket.org/baldand/mlrawviewer/issues)
If you can figure out the whole CDNG Premiere Pro thing, I'm not sure proxies would be even needed (assuming that other NLE's will also support CDNG).
Vista hasn't been tested, but I would expect it to work OK.
If you run MlRawViewer without giving it a video file, do you see a file selector then? If you can supply an "mlrawviewer.log" file from when you pressed W that might show something.
At the moment it is fixed. 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.thanx. I wanted to use the highest quality prores.
Fast/lower quality proxies is not a feature that anyone has requested to the enhancements list: https://bitbucket.org/baldand/mlrawviewer/issues (https://bitbucket.org/baldand/mlrawviewer/issues)
Hi, baldand. With several fps overrides on source, for instance 36 fps on no crop mode over 1080p canon video mode (RAW or MLV), the resulting movs are NOK (the video flickers up and down). I think that it's not able to guess the source fps. The DNG's are OK.
PLS can we have a Frameexport to high quality JPEG without overlays on button press? That would be awesome!
Hi baldand, I wanted to report a simple bug, I don't know if anyone else has it:
Sometimes mlrawviewer won't open some files, it's random. So when you hit Next key, it skips sometimes 1, 2 or 3 files until it finds one that can open. In the folder, you can see the .wav generated that is 1kb, so it failed. There is no way of opening those files with 1.1.3, will look for a log and try with an older version. Using Windows 7 here.
Cheers mate! AWESOME work!!!!! :D
Here's log: https://www.dropbox.com/s/kj33bt0iihq6ef0/mlrawviewer.log
The files that wouldn't open are there listed in the log, maybe you can take a look.
I was just looking in the ML builds and it seems the one I used (March 13th) had problems with MLV header write. So that might be it. Anyone knows about this bug? (I just recorded a whole short with this build)
Any tips?
Traceback (most recent call last):
File "./mlrawviewer.py", line 1478, in <module>
sys.exit(main())
File "./mlrawviewer.py", line 1468, in main
rmc = Viewer(r,outfilename,wavfilename)
File "./mlrawviewer.py", line 531, in __init__
super(Viewer,self).__init__(width=userWidth,height=int(userWidth*self.vidAspectHeight),**kwds)
File "~/*****/mlrawviewer/GLComputeGLUT.py", line 116, in __init__
glutInitDisplayMode(GLUT_DOUBLE|GLUT_RGB|GLUT_DEPTH|GLUT_BORDERLESS)
NameError: global name 'GLUT_BORDERLESS' is not defined
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?
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!It is also an industry standard to use the J K L keys where the K is for stop and play, J is Reverse and L is Forward. Tapping either J or L will increase speed in that direction. I think it is like 30% speed for each tap. I might be wrong, but there is a way for slow motion, fwd or rev. Maybe it is hold the K while tapping either J or L for slow motion increments in decreasing the speed.
I would think that the LE indicates it is the Light Edition so it would then not be 422 HQ. I personally, would want to use 444 since we are coming form a raw file that is 14 bit. One of the main reasons for shooting raw is to have better color grading with the larger amount of data it records. Seems silly to throw all the data away after shooting raw. Yes, the files from 444 are larger, but so what when we now can buy a 4 TB drive for $157 or a 2 TB drive for $80.
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.
You might want to read my somewhat rant-ish thread asking the same question.I have an M and it does not do audio, which is the big reason to use MLV at the moment. So, I use raw and it is also easier to get Pink Dot Removal from a few apps that only use Raw files and not MLV.
I find .raw gives me better performance and has stronger existing conversion tools in the form of RAWMagic on the Mac, but if you need in-camera sound then you really don't have a choice.
I would expect when MLV gets standardized and publicly released that a workflow standard will battle itself out.
It is also an industry standard to use the J K L keys where the K is for stop and play, J is Reverse and L is Forward. Tapping either J or L will increase speed in that direction. I think it is like 30% speed for each tap. I might be wrong, but there is a way for slow motion, fwd or rev. Maybe it is hold the K while tapping either J or L for slow motion increments in decreasing the speed.
Maybe these functions are not needed for this app. Take a vote from users if you are interested to add these functions.
When i adjust the white balance for a MLV file in MLRawViewer, it doesn't seem to stay with the file. I load another MLV file and then adjust the white balance for that file and extract to a DNG sequence. Now when I load the first DNG seq, the white balance did not stay and it shows the white balance from the last file I adjusted. What am I missing about this?
I have an M and it does not do audio, which is the big reason to use MLV at the moment. So, I use raw and it is also easier to get Pink Dot Removal from a few apps that only use Raw files and not MLV.
Yup, if you don't need audio then .raw is IMHO superior performance-wise. On my 5D3 I can easily record continuous 1920X1288 on all of my CF cards in .raw. When I switch to .mlv, at times it seems like the camera can hardly keep up with 1920X1080 even with audio disabled.that's a bummer on the 5d3. especially since it can record audio with mlv. maybe they will eventually work it out.
Hello Gary,if i use ACR and make any adjustments to a frame in the dng seq and the sync it to all the frames, i can save it out as new dng seq with all the changes i made on every frame. that is why i was wondering if it is possible in mlrawviewer.
My understanding is that CDNG files are white balance agnostic. What that means is that while the metadata might have information relating to what your preferred white balance setting is, it's not married to the actual image. I think that the white balance and tonal adjustments in MLRawViewer are only applied to the ProRes export.
Maybe Baldand could comment?
if i use ACR and make any adjustments to a frame in the dng seq and the sync it to all the frames, i can save it out as new dng seq with all the changes i made on every frame. that is why i was wondering if it is possible in mlrawviewer.
When i look at the material on my macbook pro 13", the material looks washed out. Like a blackmagic material.. Is that ok? When i try to change the curve on the upper left side of the menu to a straight line the video material is crushed..
Is that behavior normal, or is the iris gfx card the problem?
Thx. Sw
Hello baland! I wanted to ask why does 50fps footage sometimes play in slowmotion and sometimes in normal motion? Meaning 25fps or 50fps? Is there any shortcut that I am missing? Also, the audio does not stretch when it plays in slowmotion, it gets cut off at half of the clip, probably you know this, hehe.
Cheers!
I am not sure if this has been covered, but is there some way in your app to eliminate the pink dots we get on the M camera using raw or mlv files?also here,
also here,PDR is solved? how is it being done?
when i used dual iso on 600d i used to have pink dots, mlviewer solved this issue...
BTW:
Batch convert to cdng or prores will take this app great step forward.
best
David
I would think that the LE indicates it is the Light Edition so it would then not be 422 HQ. I personally, would want to use 444 since we are coming form a raw file that is 14 bit. One of the main reasons for shooting raw is to have better color grading with the larger amount of data it records. Seems silly to throw all the data away after shooting raw. Yes, the files from 444 are larger, but so what when we now can buy a 4 TB drive for $157 or a 2 TB drive for $80.BUMP. anybody?
If this guys had mlv instead of raw it would be great...Please indicate that this competing app for sale is only for Mac so Windows people do not waste time trying to get the demo and give out info with our email addresses for nothing.
but i think it is a nice referent for mlrawViewer
http://pomfort.com/cliphouse/ (http://pomfort.com/cliphouse/)
the idea is being able to view a pool of the files on the sd or cf card from the left, being able to view them on the right, convert the one that you see or batch convert all the files on the card to a destination folder.
color correction is not that important as i see when you digitize
Please indicate that this competing app for sale is only for Mac so Windows people do not waste time trying to get the demo and give out info with our email addresses for nothing.
Come on Gary...how about you read up what you're signing up for instead of blaming someone for posting about it?Come on Mid, you can't expect everyone to know what you know. I never heard of it before and I research a lot. Probably more than most people ever do. You are probably a Mac guy, so of course you have heard of it. I bet you are more upset about something being said about Mac rather than just my request for a warning, which most people usually do. -_) Or you wouldn't have said anything. I am a PC and Mac person since the first PC and the first Mac. I am currently only PC. My post was not against Mac, just that I wasted time and handed out personal info for something that could have been avoided from a simple sentence of, BTW, it is only for Mac.
Pomfort Cliphouse has been around for a long time, in my tests it's clunky and never played back more than a couple of frames at a time. The guys who make it never quite had a response as to why the issue is happening, and if I can't get a good sense of how well the app works from a demo, I'm not going to buy it.
All I'm saying is that before you sign up for something, that you look at the specs and make sure that it fits your system.you're right. I was moving too fast to get the download started.
For instance, I'm still running 10.8.4 on my main machine, so I have to carefully read to make sure that my specs fit the required minimums or I'm wasting my time. So that means no Red Giant Universe for me!
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.
All I'm saying is that before you sign up for something, that you look at the specs and make sure that it fits your system.
I love mlrawViewer it is the best thing that happened to raw on ml.
MLRawViewer is great, but you should take a look at what Thomas Worth has in store for us with the new version of RAWMagic too!
mac users are minority we always read before we download.
use to be a win user for a long long time,
an IT man acutely and a programer.
So yes, people should read what they are downloading.
I love mlrawViewer it is the best thing that happened to raw on ml.
Oh my god I just realized this is exporting to CINEMA dng... jesus!!!! Amazing!!! Is there a command line option to start encoding? I would love to incorporate it on my MLV Converter... if not, can it be added please?
Cheers!
How do I convert to cdng or is it that the dng converted are actually cdng files. The properties section doesn't say so.the dng converted are actually cdng files.
@baldand. The link to your repository in the OP is generating a phishing attempt error in firefox. The username before bitbucket.org needs to be removed.
https://bitbucket.org/baldand/mlrawviewer.git
Cheers.
MLRaw can conver also dual iso RAW?
When using mlrawviewer the video looks like crap: not sharp and colors are all washed out and sort of pinkish.It is preview.
Please help: what am I doing wrong?
It is preview.
Click "Export" (E key on keyboard or Red icon on left panel) to export to DNG and then look DNG :)
Also see issues about ACR color profiles:
https://bitbucket.org/baldand/mlrawviewer/issue/48/write-correct-camera-model-metadata-it-is
Unfortunately the video quality is still very bad after exporting :( . Some examples (password is MLV):
http://frankboekamp.smugmug.com/MLV/ (http://frankboekamp.smugmug.com/MLV/)
During recording in the viewfinder it looks all right. I must be doing something very wrong :o
great to hear there is a bugfix :D. I downloaded the version that is in the first post of this thread.
https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_1_3_win32.zip (https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_1_3_win32.zip)
Where can I find a newer version?
For the record: I was able to correct the video using ACR but it was a lot of work!
And to be more complete on this, I used the latest night build:
magiclantern-Nightly.2014Mar29.5D2212
As I understand it, the bug was in Magic Lantern - not MlRawViewer. Sorry, but I don't know any of the details about the fix.
Sorry if this has been posted before, I've done a search but couldn't find anything related.
Using MLRawViewer I can export to .MOV fine but nothing happens when I try to export DNG?
Parallel processing at once per CPU core. (at least 4 converting processes at a time.)Some info:
Btw, baldand, out of curiosity, how did you make the executables and package this for windows and mac?
Thanks
The feature that I'm missing the most is the ability to use all the CPU power when exporting dngs, it would make a HUGE difference in my workflow and I suppose the ones of everybody!
thanks for the software MLRawViewer.
Does it remove pink/green dots for 650d? Can it be builtin? :)
During an raw/mov export, Can video viewer/display be disable during an export just to save CPU/GPU?
Will there be waterdrop WB tool in future :) ? or I can enter the same numbers for WB so I can lock in the setting during mult clips export.
thanks
If possible please raise, vote and track the status of feature requests on bitbucket: https://bitbucket.org/baldand/mlrawviewer/issues?status=new&status=open (https://bitbucket.org/baldand/mlrawviewer/issues?status=new&status=open)Dear Baldand,
I'm working on the white balance and colour related features right now. The white picker might just make it to the next release. Not sure about numeric entry.
For now viewer can't be disabled during export since it is partially creating the data to export... in future (not the next release) this might change if the MOV export moves to background task.
Pink dot removal is also a possible future feature, though I don't have any camera with pink dots so I have some trouble to develop this one...
Dear Baldand,
Thank you for this great app
Right now you are the only tool that can be used as an mlv converter to cdng on mac
Please, add batch convert.
Is this batchworkflow working with the prores files as well??
Hi,
a quick question I stumbled upon yesterday. The version of Prores Mlrawviewer uses is 4:2:2 LT, isn't it? Why not 4:4:4, or would that exceed the amount of information stored within the .mlv?
Regards,
kontrakatze
MlRawViewer 1.1.4 is now available. See the top post for links and instructions: http://www.magiclantern.fm/forum/index.php?topic=9560.msg91165#msg91165 (http://www.magiclantern.fm/forum/index.php?topic=9560.msg91165#msg91165)Thank you Baldand for all this hard work and for keep update MlRawViewer.
Main changes since 1.1.3:
- Uses sRGB colour space instead of camera raw colour space based on matrix in RAW or MLV file
- sRGB and Rec.709 gamma curves added (defaults to sRGB)
- White balance can be picked by clicking a neutral coloured object anywhere in a frame
- White balance and brightness are written to (and read from) exported DNG files
- MOV exporting when changing resolution no longer causes image corruption
- Confirmation dialog shown when closing while exporting is ongoing
- Mark In/Out keys changed from J/K to I/O (next/prev file changed to J/K)
- Next/prev works also for CDNG sets
- DNG model metadata fixed to allow profile matching in ACR
If possible please raise, vote and track the status of feature requests on bitbucket: https://bitbucket.org/baldand/mlrawviewer/issues?status=new&status=open (https://bitbucket.org/baldand/mlrawviewer/issues?status=new&status=open)
I'm working on the white balance and colour related features right now. The white picker might just make it to the next release. Not sure about numeric entry.
For now viewer can't be disabled during export since it is partially creating the data to export... in future (not the next release) this might change if the MOV export moves to background task.
Pink dot removal is also a possible future feature, though I don't have any camera with pink dots so I have some trouble to develop this one...
thanks for the new version. The 1.1.3 allows dng files to be exported as mov. 1.1.4 doesn't. please don't remove feature. :)
I would like to ask if any other mac user has this problem with the ProRes files being 4:2:2 instead of 4:4:4.
By now these are the applications I tested:
- Finder info says ProRes 4:2:2 HQ
- Davinci resolve lite says 4:2:2
- FinalCut Pro X says 4:2:2
- Quicktime says 4:2:2
- Mediainfo says 4:2:2
I get the same results with MlRawViewer 1.1.3 and 1.1.4 regardless the .mlv I use as input.
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fwww.schoenharting.de%2Fpic%2Fmediainfo.tiff&hash=a3b423a0f360f62e61a68199ead3297a)
MlRawViewer v1.1.4
(c) Andrew Baldwin & contributors 2013-2014
Using GLFW
wavnames []
wavfilename C:\Users\Joe\Work\movies\2014\ML Raw Test\M08-1426.WAV
Opening MLV file C:\Users\Joe\Work\movies\2014\ML Raw Test\M08-1426.MLV
Black level: 1791 White level: 15000
FPS: 25.0 (25000/1000)
Audio frame count 0
Traceback (most recent call last):
File "C:\Projects\mlrawviewer\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 283, in __draw
File "<string>", line 755, in onDraw
File "C:\Projects\mlrawviewer\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 234, in renderScenes
File "<string>", line 414, in prepareToRender
ZeroDivisionError: float division by zero
Is the file corrupt or is it something with the player? When I convert it MLV Converter 1.9.2 it seems to only take the .MLV, but maybe that's just the converter.
Code: [Select]File "<string>", line 414, in prepareToRender
ZeroDivisionError: float division by zero
Nothing was removed from 1.1.4. MOV export should still work as in 1.1.3.
If it is not working for you, can you give details of your system (Windows or Mac) and the problem you see happening? Have you set an export target folder using W key?
On Windows 7 new 1.1.4 update only shows a black screen although audio can be heard. Checked same files on older version are viewable
The whiteblance picker only work with mlv-files right? Couldn,t get it to work with raw
Couldn't be better, Baland.
WB picker and MOV output works great. The only thing I hope is adding AdobeRGB mode.
(for taking RAW with Adobe RGB mode of 5D mark3.)
Do you think is it possible?
You refered to sRGB as a gmma tone not as a color chromacity. right?
(sRGB and Rec.709 share the same chromaticities and White point chromaticitiy.)
Is it possible to get full quality realtime playback? I'm planning on buying a pc i7 3770k 3.9ghz with a geforce gtx 660 2gb gddr5... will it work?
I see that the program also supports cinema dng playback. Would it be possible so extend that support to regular dngs or is the 14bits a problem? Would be great to be able to preview the dng sequences in the same way as is possible with the mlv, raw and cdng-files.
Hi, just tried the latest version (1.1.4) - but if I do MOVs the files are created in an old directory (where i was using it the first time). N
Is it possible to change output directory - or shouldn't it just save the output in the same directory as the source (if that is the case, I seem to have found a bug?) Anyway - great work! Use this alot!
OSX v.10.9.2
macbook air
tried several MLV files + MLVs from the latest nightly build
/J
MlRawViewer 1.1.5
Thanks!
*White balance seem to work, not brightness though. Strange
Just thought if you already use the metadata why dont you show shot name and take number when using ime module, it would be great.
Also maybe add option to export the files naming after shot name and take number from metadata.
1.when finish the pool, record icon stay pressed, so when using c again it start next batch immediately and not waiting for user to press.
2.also if hitting "c" again it ads the same pool again and again - maybe check if pool already aded and inform user to prevent user mistakes.
3.when leaving the app i get the dialog box even after i hit "x" or "z" and cancel or clear the pool.
crashes:
1.application crashes/not responding when hitting "w" to set export directory
*update - this does not happened if i launch the app and then choosing a file to open, it happened when double clicking an mlv to launch the app and then hitting "w".
*Update - after using "w" to set output folder "e" (file name to render) and "y" (render progres) overlays not showing up but the export happened.
Also after hitting "w" it takes something like 3-5 sec for dialog box to show up.
2.application crashes/not responding when in full screen mode trying to leave app while it rendered or pause rendered - not happening when not full screen - looks like maybe something with the dialog box event.
The usage of the queue has changed a bit since 1.1.4. As before, the E key adds an item to the queue using the current settings. But by default the export queue does not start processing as soon as you add something to it. Instead you need to click the red circle, or press the Y key. You can also pause the processing with another press.
The top item on the queue can be cancelled with the X key, and the queue can be reset with Z.
Also, pressing key C will add ALL files in the same directory as the current file, using the same colour balance settings. This might be useful for example if you are looking at a card full of takes from the same scene - one key will export or ProRes encode all of them.
Thanks!
Baldand can you add the new feature shortcut keys to the first page and the homepage? I've been using this app since the first alpha and I didn't know that the E key was changed to "add to queue". Heck didn't know that queuing was possible. I was under the impression that E was to export. Another question, how do we track what's in the render queue?
@Danne, @DavidSh
Many thanks for testing out the build and taking time to report the issues.
I'm a little bit lost. :-[And how this is got to do with MlRawViwer?
Some month before I got it to work, but now I lost the red line.
I recorded MLV files and use MLRaw 1.1.5 to get DNGs. That's ok. Now I want to improve DNGs a little bit bit and create a movie from it.
I have CS5, so I like to use PS5. The new DNGs are not readable by PS5 anymore. But I updated Camera Raw for PS5 so I could open them again. But what next? Can I create a MOV directly with CS5 or do I have to cnonvert them to TIFF and later on use QT Player for putting TIF to MOV????
I am unable to press the red record button to export the DNG files
17" MacBook Pro
Mavericks
Have tried 1.1.5 to see if the same issue - don't know if you changed the functionality of the little red button but now it just toggles on and off.
I typed W to open the Save To window but the app crashed.
Let me know where to send crash log cos I can't attach it here...
Baldand, how many cores does MIRAWviewer support?
1.1.5 runs 3 times faster than 1.1.4 !!!
Plus, does it any chance to support
1. Noise Reduction 2. constrast adjustment(Auto mode is good, too.) in the FUTURE?
=====================================
BTW, I don't know why I got a message like
"This message is awaiting approval by a moderator."
for the first time.
Are there any requirements or something else(donation?) to leave a message here???
Then, I feel really sorry for that.
=====================================
In 1.1.5 CPU demosaicing (used for MOV export) now uses all available cores.
With my hackintosh overclocked to 4.7ghz I'm getting nearly real time playback. Thanks baldand
WOW, can you share your Hackintosh specs? Thanks a lot! (I'm about to build one)
Also, MOV exporting should now use all available CPU cores on Win and Mac, which should make it it significantly faster (my quad core 3770 i7 desktop encodes at 7FPS).
Does 1.1.5 have chromasoothing?
I'm a noob, can I ask if the multithreading will be easy/possible to implement also for dng export or I can forget about that? :)
Hi baldand
I've just tested 1.1.5 (win32) version and noticed that when playback paused, pressing the "F" key (Toggle between drop-frame/sequential mode) activates audio only playback from the current position. Then I went back to version 1.1.4 and experienced the same behavior. Never tried this in earlier builds though. During playback everything is OK. This happens just in pause mode. Is it supposed to be that way or it's a bug?
Thanx for this fantastic app.
BB
great job baland..?
is dual iso support planned on a further release?
thx. sw
check reply #483
Would be great if you had nightlies or compiled versions that one could test of the latest 1.1.5?
In current versions of MlRawViewer, DNG export is mainly disk I/O limited, not CPU limited. In general, (more) multi-threading will not speed it up.
In later versions, there may be more processing done as part of the DNG export process. As much as possible, I will try to use the GPU for that, since for many operations it can be significantly faster than any CPU.
hi baland!Dear swinxx,
i wanted to try out mlrawviewer 1.1.5 on a macbook pro.. everything seems to work fine except "w"... (selecting directory)
when i press "w" the prog crashes.
strange..
thx
anyone else getting this issue? I tried searching but got no mention of this problem anywhere else.
Hi Baland
Here is my issue, I some how lost functionality on export I've been using MlRawViewer since the first version and always use the E key to export I understand the new changes that were made in
MlRawViewer 1.1.5 like making sure to click the red button then press the E for export and it was working fine for about 10-15 few clips but now I get no response when trying it out any suggestions would be awesome. Ive re-downloaded MlRawViewer older 1.1.4 and get the same thing :-\
Anyone :-[ I have went all the way back to 1.1.0 and still getting the same thing all buttons and functions seem to work except when I go to export it does nothing really appreciate if someone can point me in the right direction as this is extremely frustrating and annoying since I have used the app many times with no such problem. The only thing that I could think that happened was something got broke when I updated to 10.9.3 would love to hear feedback if anyone has it working under 10.9.3 However MLV Dumper v1.0 works fine :-\
Did I unterstand it right that MlRawViewer does support MLV to DNG conversion for single files, but no batch conversion for several files?
So "MLV to DNG Batch Converter" and "MLV BrowseSharp" are the only Windows GUIs available for converting several MLV files to DNGs, right?
whow that sounds so great thank you very much..
i wonder if mlrawviewer also support vertical stripe correction?
thx
simply same prob with 1.1.6
but not when I use LOG gamma curve. others I didnt tried.
What ProRes Codec is it 444 or...?
Here how my problem look like..:
https://drive.google.com/folderview?id=0Bzm-dWxWHoKWR2pLN3ROTUJmUkE&usp=sharing
Oboy is this welcome :)
I immidietaley had a problem with audio. When going through clips with k and J key and starting jumping looking through the clips adding to queue etc quite often I don,t get at preview with audio throughout the whole clip. It extracts the whole audiofile but the viewer doesn,t seem to recognize the whole audio part. SOmetimes it works, sometimes it doesn,t. It stops in the middle or at the end. It does, however exports the clip with the audio even though it can,t be heard so its a preview thing. Compared It to version 1.5, and the problem starts with version 1.6. 1.5 previews audio fine.
I ran three different .MLV files of different length on a macbook pro retina 15, OSX mavericks, 5d mark 3.
Thanks for your good work
Just a simple test if it can help.Silly question, but did you turn on the correction by pressing the zero key? Did you see any difference on screen when you toggled it on and off?
For me vertical stripes correction doesn't work. First image is from 1.5 and second from 1.6. Same vertical stripes in both.
...
Anyway, the rest of the improvements are great!!!
Thanks.
5Dmk3 1.1.3 KomputerBay 1000x 64Gb Nightly 6 may 2014
Ah, so it only corrects if gpu is working??
Would it be possible to implement it as always on? Is there a scenario where i dont want to correct the stripes vert/horiz?
Not a silly question... Not as silly as me!!!!
No
Now pressing 0 before export:
...
Not completely gonne, but much better!!!... Image is adjusted for a bad scenario, and the results are much better than before with 1.5
Thanks for the answer and sorry for the mistake.
The new GPU features are awesome!!! Def will be trying that on any line shots I have,
my apologies if this was asked, but is ther any way to add the filename of the MLV as a reel\tape name metadata to the Proxies? That would make the round tripping process significantly easier, and I wouldn't need to make my proxies in Resolve (as it adds that metadata, which really helps ensure the return part of the round trip is easy). Is this something that can be implemented easily?
It depends on the details. Can you make an enhancement request to bitbucket specifying exactly how you would like it to work - e.g. exactly what metadata tags you expect to be set to what kind of values in which kind of files - with examples if possible. That will help.no problem, will put in features request w details
Even better if you can tell me what ffmpeg command options should be used to achieve the right results.
Link: https://bitbucket.org/baldand/mlrawviewer/issues?status=new&status=open (https://bitbucket.org/baldand/mlrawviewer/issues?status=new&status=open)
Thank you, baldand.
After testing 1.1.6 ver, today I found some weird thing about bitrate of clips. by
If I put the setting default, the total bitrate of 7s-clip is 159Mbps.
While I changed WB and brightness the total bitrate skyrockets to 233Mbps (a whopping 46% up!)
I don't think the image quality of the WB-modified clip is 46% higher than the default clip. (no sharpening, no NR.)
If you didn't not intend to do this, could you fix it?
Hello Baland!!!! I have this problem when i apply Srgb and Rec709 curve...there are points yellow and blue in movement in the frame, in this picture is not very apparent but when I play the footage is very visual...I have 7d camera with the last build 24/05/2014, windows 7 and nvidia geforce gtx295 graphic´s
Thank´s!!!!!!!!
Which version of MlRawViewer? Linear and HDR modes look ok?
It sounds like it might be a GPU issue. Make sure you have the latest NVIDIA drivers you can get.
Hi baland.. Have you got my dual iso mlvs??
perfect. so i hope it will help.. greets
is there a possibility to implement stripe correction into cpu mode? thx
i am just testing the new 0 key gpu function with one mlv file from a nightly build from january17.
when i try to change wb after i pressed zero the shot is tinted green, when i press zero again and change wb it looks good but can not be changed?
how can i now check if gpu is activated?
thx
Hi Thomas
I bought RawMagic 1.1 and tried to use it for a shooting I had last weekend. I shot with 7D in the legacy .raw format (I find it more stable and had no need for sound). This is the issue I came across : when converting spanned files, Rawmagic converted the images of the R00 R01 etc parts in totally black dng's. So my DNG sequences only had the images of the .RAW part and then it was filled with black...
I tried converting with rawmagic lite (1.1), and didn't had this problem : I got all the DNG of the R0* parts wright.
Did you notice this issue before ? Will it be fixed in the next version of RawMagic ?
hi baland.
sorry to ask again but i have a lack of understanding..
so how can i turn on off the stripes correction?
is it turned on off with the zero key - cause if this is the case, when i turn off gpu the stripes correction is also turned of, no?
thx for your effort and time.
re
hello baland..
alright, thank you
so, can you ( in a further release) give us a hint if the correction is turned on or off.. cause now i only can guess.
thx.
Hi Baldand. This is great news for Canon EOS M user, it remove pink dots nicely, but it is still visible if you watch carefully. I've test on two MLV of 160 frames, it remove pink dots after the 30 first frames.
@hdclip
would you support our samples-library with such a 7d-file? please read here:
http://www.magiclantern.fm/forum/index.php?topic=11899.0
Hello Baland!!!! I have this problem when i apply Srgb and Rec709 curve...there are points yellow and blue in movement in the frame, in this picture is not very apparent but when I play the footage is very visual...I have 7d camera with the last build 24/05/2014, windows 7 and nvidia geforce gtx295 graphic´s
I get the same exact thing as hdclip has reported. Both the sRGB and Rec709 export to MOV have blue blotches (with some green blotches) in the dark areas with every clip I tested. Highlights seem ok. LOG, Linear, HDR export fine. The clips were shot with the latest nightly build for 5D3 using MLV. I had already downloaded the latest NVIDIA drivers. I also tried the use the experimental 0 key prior to export and the issue remains either way.
I can provide an MLV file that shows the issue if it helps... just let me know how you need me to send it to you.
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fi62.tinypic.com%2F1zxxgty.jpg&hash=a86335f802de6e1931b3c2debd08b745)
Hi Baland
Here is my issue, I some how lost functionality on export I've been using MlRawViewer since the first version and always use the E key to export I understand the new changes that were made in
MlRawViewer 1.1.5 like making sure to click the red button then press the E for export and it was working fine for about 10-15 few clips but now I get no response when trying it out any suggestions would be awesome. Ive re-downloaded MlRawViewer older 1.1.4 and get the same thing :-\
Anyone :-[
I have the same issue:(Also with 1.1.6?
Also with 1.1.6?Yes
Yes
Maybe Nvidia geforce problem????
Nice Parrot!!!! ;)
Could be... I'm using an Nvidia GeForce 560M.
I can't get MlRawViewer to export... not sure if it's the program or I'm doing something wrong.
It just stays stuck at 0.0% for forever :/
Suggestions?
Every time I try to export to mov, I get crash with the following:
[img...
The error is consistent for 1.1.4 - 1.1.6 versions , deleting the .mlrawviewer from user folder doesn't help.
Win 8.1 x64, UAC disabled
works with dng's though
I finally figured that out :D Thanks though!
Okay, next quirk (because it can't be THAT easy, right?)
It exported *this*...
(the color should have been the same as in my last posted image)
Was this with .RAW files or .MLV? There was a bug with .RAW exports to MOV which will be fixed in the next release.
Which Graphic card do you have???
NVIDIA GeForce GTX-460What do you think Baldand????another Nvidia... ::)
What do you think Baldand????another Nvidia... ::)
JxM:
Have you tried to first set the output-directory (W)? I had this problem before in an earlier build where the output directory was pointing to a removed folder.
What camera do you use?
What OS?
What kind of GPU do you have?
Hmm... I was hoping this had been fixed in 1.1.6 as it now checks that the xport path is valid. But I guess the problem must be caused by something else.
Could you find the ".mlrawviewer" folder in your user home directory, send me a copy of the folder and all the files in it (it's small).
Then you can delete the folder, and that will probably work around the problem so that it doesn't fail on exports.
Hi,
If you shoot crop mode (x5 zoom) with a 5D Mark III and use FPS override (for example 24 exact FPS) MlRawViewer will report 29,776 fps. Maybe it's a metadata mistake.
I verified shooting a timer watch in crop mode. It's actually using the override setting. Here is an actual file (2,2 Gb): https://drive.google.com/file/d/0B3ncQl4hSqlnR096bXNWbk1PYTQ/edit?usp=sharing (https://drive.google.com/file/d/0B3ncQl4hSqlnR096bXNWbk1PYTQ/edit?usp=sharing)
This converter is working great for me as far as exporting to DNGs, but I'm wondering is there a way to do batch conversions with it or something else? I was using M L RAW Video Converter 1.9.1 previously, but now it's spitting out errors and not working now...
If you just need DNGs, there's MLV Mystic...
http://www.magiclantern.fm/forum/index.php?topic=10466.0
Hello,
I'm having problems with Mac version 1.1.6.
...
Some ugly gradients in the grass, overexposed leaves on the right and on the top of the shot (yes, I know not to expose that way - it was a test).
And also, there are some pink dots on the overblown hair.
Quick question though. I have noticed that you allow export of adobeRGB, Log, and Rec709. What standards/libraries are you using to define your "Log", "Rec709", etc. I need to know because after I edit these files in Premiere and I'm ready to colour grade (I use FilmConvert and Osiris), it's very important that I identify the source material correctly, for the LUTs to work properly. I am using a 5dmark3.
Is your Log output exactly the same as the Canon C-Log? or equivalent to some other log like VisionLog.
Is your Rec709 the same as any other Rec709?
Is the adobeRGB the same as the ML RAW Standard input for FilmConvert (i.e. untouched colours)
Your insight would be helpful as then I know the correct input starting point when I begin my colour grade process.
Anyone experience that.
http://tinypic.com/r/xbcked/8
Anyone experience that.
http://tinypic.com/r/xbcked/8
Workflow
MLV - 5Dmk3 april 20 nightly
mlrawviewer 1.1.6 to mov log curve
premiere cc Windows
m31 lut LOG
Hi,
I am a beginner for using Magic Lantern. When I convert mlv file into mov. using MIRawViewer Im getting red spots in the dark areas of the footage.
Secondly, for making a music video the external sound got in sync with the mov. footage I got from MIRawViewer. But the colour grading is not as good as the one done by after effects.
If, I convert the Mlv file to dng through MLVMysticand take it to AE the colour grading becomes best but the external sound doesn't sync with it in the Final Cut Pro X.
Please guide me wht to do. Im a magic Lantern lover andI dont wanna quit using it because of lack of proper information.
Hi @baldand et al
I'm a regular user of the Cineform codec. Would it be a massive complication to add this to the export options some time?
Many thanks for your continued great work.
I have a few questions regarding the default exposure of the log curve.
...(lots of good analysis here)...
I think the problem is the mov convertion of mlrawviewer. Recently used raw2cdng and process in after effects. exported to mov prores and the problem is not present.
https://www.dropbox.com/s/yrdap681f7smiap/M02-1703_000001_DNG.rar
Baland, i really like the idea to drag and drop multiple files to the batch process (rawmagic). Is this also working within mlrawviewer? Cause for my understanding, you put all the files to the batch process one by one..
What i mean is:
Drag and drop to a queue, then all files are in a list where i can select e.g. Video1, set my in and out points, then video2,... Then select output format globally and the directory. Then convert button and voila.. That would be a great addition.
Thank you Baldand. The Viewer is a very, very good tool.
Like my predecessor, I think a histogram and the whitebalance displayed in Kelvin would be a very good next step.
Without the color and exposure is always a little sloppy and sometimes off.
With exact control over these parameters a conversion to DNG would be obsolete in most productions
and you could go straight to editing with the log-gamma-applied-10 bit-almost-linear .movs.
That would be so great :)
Hi Michael,
My goal with the log curve was simply to have a reversible mapping function which prevents some of the detail in the darker areas being lost during the reduction from 14bits to 10bits that happens when encoding to ProRes. In theory, the data could be linearised afterwards with a matching inverse function. However, I haven't made such an inverse function (e.g. in a LUT file) to do this, so it's still just a theory.
It would be possible to change the existing log implementation, or add new ones, or add LUT support so that this could be made part of a tested workflow. But I would probably need some help with in terms of requirements, code contribution and testing.
Has anyone tested how the log converted prores files react when converted to VISIONLOG\ Cinelog? Im curious if we are still able to use that workflow for grading if we convert toREC709 or LOG Prores in the viewer (as that would save LOTs of space), then convert to standardize VISIONlog, and hand grade or add OSIRIS\Impulz LUTs as desired?
Anyone had success with that?
Hi, my ProRes conversion is very slow. Probably 3-4 fps. Is that normal, or is there something I'm not doing here? I'm running v1.16 and converting 5dmkIII 1920x818 24fps footage on a Macbook Pro Retina with 16GB Ram. Recording to internal SSD, so there shouldn't be a bus or read/write speed issue.
I get realtime transcoding from DNG with Resolve, so the issue must be the program.
Should I be expecting faster transcoding, or is this as good as it gets?
Sorry if this has been mentioned or asked before but does MlRawViewer correct the vertical stripes?...
There will be an icon for this in later versions.That will be nice =)
@arrinkiiii I think dark frames cannot help 7D vertical stripes because the pattern changes during a few frames. The current algorithm re-measures the stripe pattern for *every* frame, so it can correct for this change.
I'm suddenly experiencing a bug where thin magenta vertical lines appear on the viewer (see pic below) whenever I click on a GUI icon, which then subsequently appear on the render.
I'm suddenly experiencing a bug where thin magenta vertical lines appear on the viewer (see pic below) whenever I click on a GUI icon, which then subsequently appear on the render. Have tried both 1.1.5 and 1.1.6 and they are both doing it. Is this a known bug to yourself or anyone else? :o
Hi @Midphase
Fair call, but it's been working fine up 'til about a week ago! :o
Ive read a lot of the thread. Are the adjustments that you can make within the program not applied to the .mov export? I am not seeing adjustments show up there.
Also Im seeing a lot of hot red pixels in the exported mov, but not the preview.
I believe mlrawviewer can handle DNGs, is this correct?
In addition, should it be able to handle DNG raw video from a blackmagic camera? (Turns out there's no a lot out there to view blackmagic raw files on earlier versions of mac (or probably on linux) (I'm on ubuntu, a friend is on mac)).
If mlrawviewer doesn't support it, and there's the possibility that it could, I'm trying to get my hands on a blackmagic file (from my friend), and I'll try to code something to handle it to push to the main repo.
I would be really happy to see Blackmagic files supported with contributions, or indeed any other sources of raw bayer video files such as Odyssey7 captures from C500 or FS700.
- new icon is cool,
- when i open the prog, i can not see all icons, i have to resize it!
- then mouse pointer disappears when window size is changed.
- would it be possible to add tooltip mousover?
- when pressing w, the window where i can select the dir for export is behind the video window. perhaps you can make the window pop up in front of that window?
- is there a possibility to delete all jobs out of the mlrawviewer..?
...
so when stripes correction is on, gpu processing is also on? right?
is it on when the icon is "stripes and cross"?
cause i exported 2 files and i think i can see stripes when the icon is stripes only and can not see them when the cross is seen too? is that right?
Testing 1.1.7 on new Mac pro base model and I am getting constant crashes when trying to export dngs. Same files exported fine on 1.1.6.
/Applications/MlRawViewer.app/Contents/MacOS/mlrawviewer/Make it crash, then it should leave behind a file "mlrawviewer.log". Please share that.hello baland,
sorry but i have to inform you that my mlv (latest 4 july build / 5d mk3 / 23,976fps) files cause your program to crash.
tried to convert the files (the file structure is deep).
nearly every single conversion caused crashes.
my system is 10.9.3, mbp 13" retina late 2014
dont know why, sometimes it works, but most times not.
the 2nd problem is when a directory has a äöü inside, it does not open the file.
thx. re
@baland:
i tried to export to dngs, and a window pops up when it crashes (see log file)
here are the log files: (mlrawviewer log file and crash report from mac)
http://we.tl/LRwEKu6GXD
greets. sw
this was the exact log file.. sorry.
however, it crashes during the export of the dng files.
greets. sw
- Fix for default brightness of log output (it was 16 times too dark)
I've also changed my build environments for both Windows and Mac. It's possible this will cause some problems for some people, but I hope it won't.
Please let me know here if you have tried this version out, and if it worked ok, or if you saw some problems.
Thanks!
The brightness of the log output is correct now indeed! I'm mainly using OSX but was trying MlRawViewer on Linux as well and noticed the brightness difference in 1.1.6. Seems it was working correctly in Linux!
Does that only apply for the Win/Mac build?
Didn't test much else but it felt quite solid!
Was the WB/Exposure saving feature (G and H keys) persistent between sessions in the last build as well? Just noticed yesterday while playing around ;)
Michael
...
Every time I work with MLV and DROPPED FRAMES ALLOWED I get a black frame for this dropped frame. I think it would be very useful to replace this black frame with this picture:
...
...Is there any way to set the fps manually?
Sorry if this been answered before... any way to export to mov without the overexposed signs (colors) embedded in the video?
MOV export to /video/test/M23-0349_000001.MOV started
Opening MLV file /video/test/M23-0349.MLV
Black level: 2044 White level: 13000
FPS: 23.97 (23970/1000)
Audio frame count 0
Traceback (most recent call last):
File "/home/sgofferj/mlrawviewer/ExportQueue.py", line 423, in doExportMov
self.processExportMov(jobindex,filename,movfile,wavfile,startFrame,endFrame,audioOffset,rgbl,tm,matrix,preprocess)
File "/home/sgofferj/mlrawviewer/ExportQueue.py", line 482, in processExportMov
self.encoderProcess = subprocess.Popen(args,**kwargs)
File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
Export job failed:
Traceback (most recent call last):
File "/home/sgofferj/mlrawviewer/ExportQueue.py", line 182, in run
self.nextJob(self.jobs[self.currentjob])
File "/home/sgofferj/mlrawviewer/ExportQueue.py", line 205, in nextJob
self.doExportMov(job[0],jobArgs)
File "/home/sgofferj/mlrawviewer/ExportQueue.py", line 430, in doExportMov
if self.encoderProcess:
AttributeError: 'ExportQueue' object has no attribute 'encoderProcess'
...Can't export to MOV. Export to DNG works...
I've been working on saving silent-pics and full resolution silent pics in MLV containers. The data from the full resolution silent pics has OB areas included. When using MLRawViewer to open these MLVs, it doesn't seem to be respecting the 'active_area' fields of struct raw_info...
One other issue I noted is the frame rate.Yeah I was thinking about that. It's kind of a sticky situation. I figured it was more important to capture the information about what the real frame rate was, since you know it as the intervalometer is running, in case you ever needed it or wanted to know later. If you just put 24fps there or whatever, this information is lost (well, not totally lost, you could figure it out from the timestamps).
@baldand, A suggestion would be that any changes made to support silent pics should coincide with manual framerate support. That way people would be able to choose between leaving the actual capture framerate in place as well accomodate those needing 23.976, 24, 29.970, 30 depending on what's needed for their project.
Hi! I use A 5d mark III with ML for 1.1.3 firmware and a build from the 20th of may.
I recently switched to MlRawviewer 1.1.7 and exported som MLV files. When I exported I noticed these red artifacts in the yellow parts of the workers clothes.
Does anyone have clue why? Could it be a wrong setting? The red artifacts are not there if I look at DNG´s.
See frame here: https://www.dropbox.com/s/4htmy976ni4c8j2/redareasx.jpg
Best Regards
Pettermannen
You need a static binary build of ffmpeg in the same directory as the source. Get it from here: http://johnvansickle.com/ffmpeg/ (http://johnvansickle.com/ffmpeg/)Still doesn't work :(. Now it writes a 185bytes big MOV file and then idles.
Still doesn't work :(. Now it writes a 185bytes big MOV file and then idles.
...I recently switched to MlRawviewer 1.1.7 and exported som MLV files. When I exported I noticed these red artifacts in the yellow parts of the workers clothes.
Does anyone have clue why? Could it be a wrong setting? The red artifacts are not there if I look at DNG´s.
My guess is that you are using GLUT rather than GLFW as the graphics toolkit. Unfortunately a few things don't work with GLUT - I think the MOV export is one of them.
Doubly unfortunately, MlRawViewer is using the latest version of glfw3 - 3.1 - which you will need to build for yourself from source from the git tree here: https://github.com/glfw/glfw.git
You will need cmake to build it. Make a "build" directory under the source tree, go in there and do "cmake ..". Then edit the generated CMakeCache.txt and change the line "BUILD_SHARED_LIBS:BOOL=ON" from OFF to ON.
Then build with "make", and copy the file "libglfw.so.3.1" into the mlrawviewer source directory with the name "libglfw.so.3"
After that your mov export should work.
Sorry for all the trouble. Hopefully in future, when GLFW3.1 is released and packaged by distros, this step will become as easy as "sudo apt-get install libglfw3".
Ok, I'll test but I have to check first if that messes up my system. A number of things are running on openGL. No worries about the "trouble" - it's none. I like to test stuff and with the price going half this summer, I'll likely get myself a BMPCC for that $500... So my 6D would be for photos only then :).
MlRawViewer crashes whenever I try to export 7D .MLV or .RAW with stripe removal activated. Version 1.1.7, OSX 10.9.4, AMD Radeon HD 6770M. Crashes whether the MLV has sound or not, and resolution makes no difference. Funny thing is, rendering to .mov works just fine. Playback works just fine, and rendering without stripe removal activated works fine. I'll pm you the crash log.
Any way to replace or update the OpenGL library? I know OSX includes OpenGL but I'm sorta lost on the library part.
Hey dude, anyway to turn the mov conversion into small proxie files? 444 is all well and good but i want cdng for resolve then small .mov files to edit in premiere with so i can just xml back to resolve and grade. so small .mov option would be amazing...unless i misses something...i read since page 11 :)
Also, when grading in resolve with BMD color spacing etc.. is it best to use log space? i am used to using raw2cdng.
Hi. There is no option for low res proxies at the moment.
When clicking around on the frame, why does it change the colour/tint of the video?
Should I be setting the grey point for WB when clicking at a point on the frame? If so, thats amazing but not sure yet?
I saw in the code that FFMPEG is executed with "-profile:4". No need for another symbol in the UI, but it would be really cool to switch between profiles or even the constant quantizer mode (maybe a config file?). I think ProRes 422 would sufficient for most cases...
http://transcoding.wordpress.com/2012/01/29/prores-ffmpeg/
I love what the HDR option does to my footage. What is it actually doing to the footage? I would like to recreate this effect in Resolve.
That would be great! Rawanizer had the option to write the ffmpeg code in a textbox or use presets, but config file would be good for mlraviewer.
I tried to modify the prores profile in the python source, but i don't know anything about compiling it to an executeble.
Done: https://bitbucket.org/baldand/mlrawviewer/commits/845b561366761c351aadad057f99efd669179f74 (https://bitbucket.org/baldand/mlrawviewer/commits/845b561366761c351aadad057f99efd669179f74)
Will be in the next release. This should allow you try to try different ProRes variants and bitrates (e.g. for proxies), as well as any other container or codec like H.264, or even JPG/PNG/TIFF output. Some examples are in the commit message.
In a later version I may take some of the best examples people make and offer them as standard options in the UI.
Totally cool, my only issue now is getting the .mov files to link to my DNG files back in resolve. xml and edl are being a real pain. Any ideas?
Quick question: When you decode to DNG, are you using any type of standard decoding method? Im trying to compare it to raw2cdng decoding quality and see which is better and I was curious if you decoded to DNG ? Long story short, should I execpect any quality difference when decoding using methods?
Excelent Sofware for use in the set.
Congrats.
I cannot Export (C letter, doesn't happen).
I use with Mavericks 10.9.4. .MLV
Everything works like a charm except export.
Any Ideas?
I love what the HDR option does to my footage. What is it actually doing to the footage? I would like to recreate this effect in Resolve.
It applies the simple "Reinhard" global tone map function x -> x / (1+x) which maps input from the range 0-inf to the range 0-1, i.e. it never clips. The brightness (exposure) multiplier can then be applied as much as you like to bring out the darker areas, and compress the brighter areas.
(Sorry, I've no idea how to achieve the same result in Resolve).
Press Y, or click the red circle to start processing the export queue.
In the next version this will happen by default.
MlRawViewer 1.2.0 available for testing
Windows: https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_2_0_win32.zip (https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_2_0_win32.zip)
Mac: https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_2_0_mac.dmg (https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_2_0_mac.dmg)
New builds are available and would need some testing. These include a few changes since 1.1.7:Please report any problems you see.
- FPS override. Press Shift-F to cycle through some alternative frame rates (23.976,24,25,29.97,30,48,50,60) instead of the clip's native rate. The new rate is persisted and used for exporting DNGs and MOVs.
- Better ActiveArea handling. This should prevent black borders being seen in full frame silent picture MLVs
- Persistent per-clip settings. Brightness, balance, in/out marks, tone map, external audio file, audio file offset and frame index are written to a ".MRX" file companion for each clip file
- FFMPEG export parameters read from text files (see earlier message for more details)
- Export queue processing on by default. This means export will begin as soon as pressing E
- Fix for OS X crash when exporting DNG with stripe correction
- Fix for flickering when playing clip while exporting with stripe correction
- Windows build changed not to use self contained exe to startup faster
ACR: Could not complete your request because Photoshop does not recognize this type of file.
Could not complete the command because the file appears to be from a camera model which is not supported by the installed version of Camera Raw.
Please visit the Camera Raw help documentation for additional information.
5D mark III
OSX Maverick 10.9.4
MLV 260 MB for testing.
ML build 08/08
I didn't test in DaVinci Resolve Yet, for me the most important.
I have other question that I can find in any thread about sofwares to convert MLV or RAW to DNG.
All the DNGs are the same? I mean, 16 bits DNG form MLViewer is the same as 16 bits by MagicRaw or Mystic or Son of Batch?
I think this is a very important question to decide which is more convenient. There's a lot of software around - with advantages and disadvantages depending of the user - but the quality, exposure, - not only the bits - it's something that people like me cannot understand .
THanks!
I can't comment specifically on the other software, but I gave a more detailed explanation of the DNG paths in MlRawViewer a few posts earlier: http://magiclantern.fm/forum/index.php?topic=9560.msg124946#msg124946 (http://magiclantern.fm/forum/index.php?topic=9560.msg124946#msg124946)
Since most of the software you are talking about is freely available for testing, you could spend a bit of time testing them yourself to understand how they differ. Your test material should probably concentrate on more extreme cases, e.g. with clipped highlights in different lighting, and range of ISOs. Then convert to DNG with all different SW available to you using their different modes, and try to push the resulting files in your grading - looking for any early introduction of colour banding, stripes, colour casts, wrongly coloured highlights, etc. Then you could post your findings as a reference also for other people, and raise any problems you find with the SW developers.
Thanks for the explanation. I'll do my best!
MLRaw have a " Reset" command to return to Original WB and exposure?
No. For exposure, this would be a useful addition.
For WB, there is currently no original WB used in RAW or MLV files - only in DNG files if they have the AsShotNeutral tag. Before the recent work of @chmee, there wasn't a good way to map from the WB info in MLV files to R/B multipliers, and I haven't yet taken his findings into use as an initial WB. Personally speaking, I anyway always try to just find a neutral colour in the clip and click that.
Is there a video / Tuto showing all the fonctionnalities of your smart software ?
And my last opinion it's about to add for export the last ProRes 4444XQ, that provide all the 16 bits potencial from DNG.
did not work for me. I tried to open these Full Res Silent Pics MLV, which were able extracted fine with mlv_dump
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2F199.167.201.88%2Fscreencaptures%2FMxtB6.png&hash=9fcf118fd87675d67b72db5d85ca81f2)
1) right click wun as adminstrator
2) a window popup allowing me to choose 00000000.MLV
3) then MlRawViewer just silently disappear. no sign of crash
Dng:s open fine in acr converting raw to dng in version 1.2.1 :)
I have a problem creating a "new folder" when choosing location. Anybody else experiencing this? I,m on mac Os X mavericks 10.9.4
Good work!
Please check the mlrawviewer.log file. It's now moved into the ".mlrawviewer" sub-directory in your user directory. That might give a clue about the problem.
MlRawViewer v1.2.1
(c) Andrew Baldwin & contributors 2013-2014
Using GLFW
Traceback (most recent call last):
File "<string>", line 1985, in main
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\MlRaw", line 1318, in loadRAWorMLV
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\MlRaw", line 611, in __init__
TypeError: 'NoneType' object has no attribute '__getitem__'
Could not open file D:/2014-07-26-Sillence-Full-MLV-AETTR/00000000.MLV. Error:'NoneType' object has no attribute '__getitem__'
Exactly. The Menu for Create a Folder not work.
Other things:
- DAVINCI RESOLVE 11: When I open the DNG, unexpected Quit. I did the DNG from MLV Mystic, and no problem. I repeat the test with other MLV files from this software and quit. This is a big one. LOG FILE: https://www.dropbox.com/s/chfrvmdf5ucsap2/davinci_resolve.log
New Version.
- The menu (finder) sometimes dissapiring
- When you closed the software, appear "unexpectedly Quit" dialog "for send to apple".
- When you touch any part of the image (not only for change Exposure or RGB colours in the right) change all the image and I insist Have to stay a shortcut - or UNDO - to return to the initial opened file, with the origin COLOR-EXPOSURE. Because if you don't like the color or exposure that you are looking for, have to close the file and open again (?!).
- The color that you change, when you open again the file, maintain the last setting. This is too bad. No undo or reset button. Practically, you lost the file in the mistake you can do.
- Cosmetic: When you press W, the dialog it's just behind the software layout and you have to move all. Bring to front?
hi, i tried some mlv 5d mk3 conversion with the the latest version of mlrawviewer 1.2.1
works great here, but when i import the footage into davinci resolve, the program crashed while working with the material.
that is strange because it happens unintentionally. (not from the very beginning but suddenly within the working process. (when working with the material) the video preview window freezes and the program stops to work. but not from the very beginning. (after i don't know.. one minute? or so)
i don't know if it is a problem with the converted material, but it always freezes when the new material is previewed, and i did not have such a problem with other material (converted with 1.1.7)
my resolve version: 11
my mac osx: 10.9.4
greets. sw
Thanks for the feeedback.
I see problems reading the audio file in the Resolve log. Can you manually delete the WAV file from within the DNG export difrectory before opening it with Resolve, and see if that still crashes?
UNDO/REDO stack and reset option seem like good possible features for the next version now that there is clip setting persistance. I'll look into that.
Yes Sir, is the .WAV file!
OK.
Do you see any obvious problems with the WAV file? is the file size less tham expected? Are you able to open and play it correctly in a program other than Resolve?
Thanks. My guess here is that one or more of the later files in the sequence is missing the normal MLV header chunk, which is usually (I mean in all MLV files produced by mlv_rec) in all the files.
To test this theory, you could try this:
- Move or rename the .M02 file, then try to open the MLV file again
- IF that doesn't work, also move or rename the .M01 file, then try again
- Repeat step above with .M00 file.
If it only works with the MLV file, then I would say there is a bug in the full res silent pics code. It is not writing a file header section in subsequent files after the initial .MLV.
...
Conclusion:
FFMPEG seems to indeed process in 8 bit and ProRes4444 in Resolve is worth the extra bandwidth/bitrate.
it only works with the MLV file after i rename .M02, .M01, .M00
The wav it's not usefull. I can't open in any software under OSX. It's too small.
You can also try, e.g. "-q:v 2" or "-q:v 0". All those settings should affect the final bitrate (and hence quality)
(The main reason to use the fixed qscale is that it encodes much faster, but if it turns out to be causing poor quality that will have to change!)
Would you be able to add the ability to apply a LUT file to the MLV files instead of using the built-in LOG, HDR, profiles? This would be enormously useful for conversion to VisionLOG, CineLOGDCP, etc in terms of applying specific log profiles or just using a general LUT overall?
LUTs would be possible - by which I mean LUTs loaded from simple/obvious file formats. LUT support is on the enhancement list (you can vote for it -> https://bitbucket.org/baldand/mlrawviewer/issue/18/log-output-and-3d-luts-should-be-supported (https://bitbucket.org/baldand/mlrawviewer/issue/18/log-output-and-3d-luts-should-be-supported))I'm referring specifically to 3d LUTs, not Adobe camera raw profiles. There are 3d LUT versions of visionlog that use .Cube based files for resolve
However, I don't know how to support DCP files, since those are a binary file format intended for Adobe products. So to use VisionLOG, or CineLOG, you would need to get "simple" LUT versions of those, or else help me find a spec for the DCP file format.
This should allow you try to try different ProRes variants and bitrates (e.g. for proxies), as well as any other container or codec like H.264, or even JPG/PNG/TIFF output.
Hi @baldand
This just gets better and better – thank-you!
Does using this option now allow me to export to Cineform (as long as it is on my machine). Please, please tell me it does – and the code I'd need to achieve it! :D
tim
You will need to manually update your settings in the $USER\.mlrawviewer directory if you used an earlier version with different defaults
I put together a quick article documenting my workflow using MLRawViewer. Should help those just getting started and want a quick walkthrough. Hope it helps!
http://bit.ly/mlraw2pr (http://bit.ly/mlraw2pr)
As MLRawViewer has continued to expand its functionality and options, IMHO it has also become somewhat challenging to use without referring to the text instructions for key shortcuts and the meaning of the various icons.
Is it perhaps time that MLRawViewer gain a proper GUI with an actual file browser, and easy to use checkboxes for the various options? I'm just raising the question because as much as I appreciate all of the work that has gone into it, I find myself still somewhat intimidated by its usage as anything other than an easy way to playback my footage.
I hope that you don't find this request insulting or improper, I really think MLRawViewer is a fantastic little app, but as much as I enjoy alternative UI's for some things (Red Giant products for example), I find myself wishing that MLRawViewer would move toward the type of GUI standards that ultimately just work.
@baland
would it be possible to make the mouse pointer (when moved to the app) always on top of mlrawviewer..
cause it disappears.
i´m working with mac osx 10.9
thx.
@balandSame thing here, have to toggle the full-screen option on and off to fix it.
would it be possible to make the mouse pointer (when moved to the app) always on top of mlrawviewer..
cause it disappears.
i´m working with mac osx 10.9
thx.
MlRawViewer has two different data paths for converting into DNG. In both cases a DNG container is created with tags extracted from the source file metadata.
1. When stripe reduction is NOT in use, the source raw data is copied and, if needed, padded to 16bit values with zero bits. In addition, (bad) pixels with zero value are hidden with surrounding data. This path should have very minimal impact on the data.
2. When stripe reduction IS in use, the data is loaded to the GPU and 3 shaders are run to estimate and correct any stripe patterns in the data due to different amplifier settings, as well as hot pixels. The result is written out as 16bit values. This path can touch all pixel values, but is intended not to cause an overall visible change in the image, other than reducing stripes and spots.
I can't get v1.2.2 to output. I click on record and reaches less than 1% where it just stops and freezes up.In 1.2.2, the export queue processing is on by default.
anyone else getting this?
I found something in OSX.
- You can't type to find a file, when the dialog appears to open files.
- The box dialog it's always back to all your windows (The last program you open always goes to front).
Thanks!
I don't quite understand the first issue. Can you explain a bit more?
When you open your application, appears a box dialog to open the file.
That dialog box include up to your right, an spotlight to find a file that you don't remember where it is.
That spotlight doesn't work.
I can't insert an image in this site, I left it here: https://www.dropbox.com/s/foq9ekz60o3qu9s/box.tiff
| FPS: | 24.0 (24, 1) |
| brightness | 8.57418770029 |
| Black level: | 256 |
| White level: | 51080 |
| BitsPerSample: | 12 |
| Unsupported BitsPerSample = 12 (should be 14 or 16) |
In reply to your PM:
Yes the app still crashes randomly and the pointer is still not there in version 1.2.2 on my iMac 13,2 3.2GHZ with GTX 680MX
Also the "log" doesn't look right. It's all pink and too bright. It has to be changed to represent something like the BMCC's log which is more accurate for color correction and appropriate for this kind of sensor.
Also if you continue work on this app please make text when mouseovering over the symbols so people can learn what they mean.
Thanks for your work. I put a link in our guide: LINK (http://www.cinema5d.com/guide-raw-on-a-5d-mark-iii-magic-lantern/)
The log curve is quite bright - it is just a pure log function without any S-curve. But your description of it being pink makes me wonder what exactly you are seeing, because there should not be any colour cast coming from the Log mode. Do you only see pink in Log - does colour from the other tone map functions look correct?
I thought I was the only one to see this. Yes, Log is not right (pinkish cast). It used to be but it went wrong in recent versionS. And the others (sRGB etc.) look correct.
Also the "log" doesn't look right. It's all pink and too bright. It has to be changed to represent something like the BMCC's log which is more accurate for color correction and appropriate for this kind of sensor.
I absolutely love the program. If only because audio becomes so much easier. And I prefer the color processing to Resolve. Would it be possible to also have a Prores 422 output setting? I love the debayering, but I seem to get more color noise at higher iso's than files processed with ACR (or am I doing something wrong). We could use 422 for offline editing.
For me personally, even if it still has some quirks, this is a huge step in the whole ML development. Thank you!
Hi Kurt, ProRes 422 can be configured easily. If you need a different picture size, you can add a resize filter to the ffmpeg string.
Have a look at page 31, everything should be there!
I want a user interface more like Adobe media encoder or something like that add files and have a preset and batch
It very much sounds - though I can't confirm for sure without the files in my hands - as though the silent picture MLV code is not writing the MLVI block at the start of the subsequent files (.M00, .M01, etc) in the series.
I've (hopefully) fixed the issue with MLVI headers. Testers needed: https://bitbucket.org/hudson/magic-lantern/pull-request/588/silent-pics-mlv-timelapse-write-the-mlvi/diff
See above explanation ;)
But the menu file-> source, hide console, clear console. Edit -> cut,copy, paste, clear, increase font sieze, decrease font size, start dictation, special charaters. Doesn't make any sense to me. I din't try the linux and mac version.
For just playing files it's fine but batch processing is a pain.
http://tv.adobe.com/watch/digital-video/batch-encoding-with-adobe-media-encoder/
also check raw2cdng for a much better workflow.
Idea. Maybe a stop/abort button if you want to abort ongoing export instead of closing the whole app? Low priority suggestion.
Hello,
I have a problem with the DNG files converted from MLV with MiRawViewer (1.2.2). When I open the DNG file in DaVinci Resolve Lite all the sequence is black. If I convert the same files in MOV the problem doesn't happen.
Thanks
Camera Canon 5d mark III ML
Macbook Pro OSX 10.6.8
A little clip exported with HDR tonemapping in 3x mode from a test roll I did when shooting some real estate.
@danne
All controls are still there on keys. From the README file:
Y - Pause or continue processing of the export queue. (this is the old "Record" icon)
X - Cancel current export job (and start next one in queue)
Z - Cancel all export jobs
Maybe I'll put some UI for the cancel ops in future version.
hello baland,
great thank you,..
i wonder if you have resolved the highlight problem from issue #88 in the new 1.2.3 version?? :)
greets.
Test build... I made a Mac test build of the current source as version 1.2.3
https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_2_3_mac.dmg (https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_2_3_mac.dmg)
Works great! (Well, some layering issues in the GUI, but as I understand there isn't much you can do about it. Perhaps just tell it to put the dialog windows behind the video, and it will show it correctly :) )
EDIT: Oh I see that it's J/K as stated in the full list of keys. Kept missing it somehow. I think the Feature list needs to be corrected though ;)
The built in Log Luts are amazing! Having Log5-16 like that is great! Would it be possible to add 1-4 though? Could be useful when combining with other Luts.
The built in Log Luts are amazing! Having Log5-16 like that is great! Would it be possible to add 1-4 though? Could be useful when combining with other Luts.
Where is the LUT location in MAC?. I want to replace them with the Osiris LUT's
I've noticed full screen toggle seems to be cropping the image.
Yes I use Shift L and import some ones after that press Shift and right or left arrow but only applies the default ones.
???
Import osiris luts export to prores without problems. Wohooo :)
What resolution are your videos, and what resolution is your display? Do they have a different aspect ratio? Are they clipped on the sides, or top/bottom?
LUT Import Test with VisionColor Osiris
All those improvements are great. Unfortunatelly it is hard to admit but seems that i dont know how to use the app. ...
...
Damn, how to use this thing? Seems so easy for everyone but me.
Would it be possible to toggle between ProRes4444 and ProRes422?
Ok, I have a fix for the LUT import on windows now. It will be included in the next binary release.
However, I also have a small patch you can apply to 1.2.3 for windows to fix the problem:
https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_2_3_win32_lut_import_fix.zip (https://bitbucket.org/baldand/mlrawviewer/downloads/MlRawViewer_1_2_3_win32_lut_import_fix.zip)
Open that file and copy "dialogs.exe" over the old version wherever you installed MlRawViewer_1_2_3. Then the LUT imports should work
Sorry for all the trouble
Is there any loss/compression in going to MOV vs DNG? Also is the live color grading in the program just for reference, or are people applying LUTS on the clips before color grading further?
edgar@linux-indh:~/mlrawviewer> ./mlrawviewer.py
MlRawViewer v1.2.3
(c) Andrew Baldwin & contributors 2013-2014
pyAudio not available. Cannot play audio
Using GLUT instead of GLFW. Some features may be disabled.so i tried different workflows and they are all not ideal at the moment, cause of the wrong primary color profiling of ml raw material.. (this will be a problem until some of the major companies start to support the Canon Raw Sensor Output of those cameras (eg. 5dMK3 - which could be seen as best option for ml raw filmers at the moment)
when using resolve we are forced to use profiles like bmd4k or bmd, rec709, ect. and they are not working very well with all the different luts cause the colors don´t look right..
"Using GLUT instead of GLFW. Some features may be disabled." What features are these, which are disabled?
@Baldand - I haven't had a chance to properly look at the source code but have a quick question: We have a couple of Cinelog users who want to use our luts with MLRawViewer. The gamma component part is easy but what primaries does it output as default? sRGB/Rec709?
Also, I just had a look at the bits you are working on (Slog/Slog2 etc). We did a lot of work to find an idealized log gamma for MLV for output to 10bit ProRes/DNxHD using the math from Arri, Sony, Canon etc and anything above Cineon log (~13.5 f-Stops) tends to degrade the image when linearized. It's not apparent in every shot so it might not be obvious without shooting a lot of test charts, a backlit DSC Xyla DR chart etc.
For MLV, Slog and Log-C are basically wasting a lot of space. Also, they tend work best when paired with their associated gamut (i.e. Log-C with Alexa Wide Gamut RGB, S-Log with S-Gamut, Canon C-Log Wide Gamut) and always require a transform lut unless the colorist really knows what they are doing. BMD Film 4k (gamma) is close to ideal for MLV and you should be able to derive the transfer function from the BMD luts that come with Resolve.
Also, I just had a look at the bits you are working on (Slog/Slog2 etc). We did a lot of work to find an idealized log gamma for MLV for output to 10bit ProRes/DNxHD using the math from Arri, Sony, Canon etc and anything above Cineon log (~13.5 f-Stops) tends to degrade the image when linearized. It's not apparent in every shot so it might not be obvious without shooting a lot of test charts, a backlit DSC Xyla DR chart etc.
For MLV, Slog and Log-C are basically wasting a lot of space. Also, they tend work best when paired with their associated gamut (i.e. Log-C with Alexa Wide Gamut RGB, S-Log with S-Gamut, Canon C-Log Wide Gamut) and always require a transform lut unless the colorist really knows what they are doing. BMD Film 4k (gamma) is close to ideal for MLV and you should be able to derive the transfer function from the BMD luts that come with Resolve.
@Tos_Maverick - BMD Film is (afaik) a proprietary, non-linear colorspace with no published information on how to get to and from it. Until Blackmagic release this info (they have no plans to do so) you will never get 100% accurate color, although it does still look nice (film-like) to a lot of users. The new Resolve Color Match tool requires you to know 100% what colorspace and gamma the source footage is and, even when this is known, it will only get you closer to photometric color and TBH this is nearly always best done manually with scopes. It currently falls apart with anything when trying to match the DSC One Shot chart (even Alexa, Red, F55 etc) and never gives uniform results with MacBeth charts. It's a nice idea but it's not quite there yet - use with extreme caution.
...I'll try and compile a version of MLRawViewer with basic Cinelog functions and see if it does what I think it can do.
MlRawViewer v1.2.3
(c) Andrew Baldwin & contributors 2013-2014
Using GLFW
Traceback (most recent call last):
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 304, in __draw
File "<string>", line 1100, in onDraw
File "<string>", line 1083, in init
File "<string>", line 337, in __init__
File "<string>", line 145, in __init__
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\ShaderPreprocess", line 177, in __init__
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLCompute", line 92, in __init__
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\OpenGL.latebind", line 61, in __call__
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\OpenGL.GL.VERSION.GL_2_0", line 230, in glGetAttribLocation
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\OpenGL.error", line 208, in glCheckError
GLError: GLError(
err = 1282,
description = 'invalid operation',
baseOperation = glGetAttribLocation,
cArguments = (6, 'vertex\x00'),
result = -1
)
Traceback (most recent call last):
File "<string>", line 2306, in <module>
File "<string>", line 2300, in main
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 247, in run
File "c:\Projects\MRV\build\mlrawviewer_win\out00-PYZ.pyz\GLComputeGLFW", line 336, in __idle
File "<string>", line 1560, in onIdle
AttributeError: 'NoneType' object has no attribute 'isDirty'I did some regression testing and found that, starting with V1.1.6, the prebuilt versions all crash with similar traces listed in the logfiles. ...
ProRes is 10bit, so some of the original data has been lost in conversion. If you want to grade in e.g. Resolve. You should use DNG, no question about that.
Are you sure that Proress 4444 isn't 12 bit?
https://www.apple.com/final-cut-pro/docs/Apple_ProRes_White_Paper.pdf
(see page nr 9) According to this prores white paper ProRes 4444 "support image sources up to 12 bits and preserve alpha sample depths up to 16 bits. All Apple ProRes 422 codecs support up to 10-bit image source".
I don't use GLUT myself any more so I can't say for sure how well it will work today. But I know that there are problems with the export process.
I would recommend you build the GLFW 3.1 shared library from git:
git clone https://github.com/glfw/glfw
cd glfw
mkdir build
cd build
cmake ..
vi CMakeCache.txt
change this line:BUILD_SHARED_LIBS:BOOL=ON
make
cp src\libglfw.so.3.1 ..\mlrawviewer\libglfw.so.3
Hey baldand, thank you for creating MlRawViewer. Unfortunately, I've only been able to open the program once on my macbook (OS X Maverick), and since then, it crashes before it opens, meaning, the icon is on the dock as if it's open, but it's not open. I've tried an older version too, the 1.2.2.
Also, I assume it'll work, so I'd like to ask this question now: Does it convert RAW and/or mlv files to cdng? And if it's an mlv file, will it create an audio file?
Hello,
How can I batch several raw files in MlrawViewer (Dng or Prores) ?
I have tried different possibilities...
- Drag and drop a group a raw file.... but noting happend...
- open a window to chooose the raw files...
Hi BL do you plan to include the MLViewers ability to convert MLV to HVEC/ H.265 in future. I am currently reading about this codec and am fascinated about its potential.
@DeafEyeJedi
Yes, your Lut's, can I try?
Can't find how to remove imported LUTs on Mac? I'm imported too many, and now try to remove some of them.
The DNG sequences that were exported with 1.2.3 contain several duplicate frames. they are usually in clusters of about 3-4 frames (duplicate) and then 5-8 good frames, then duplicates, then good, rinse, wash, repeat....
here is an .MRX file, and the log from user/mlrawviewer: http://www.filedropper.com/mlrawviewdiagnostics
I have confirmed that this problem does not happen with MLRawViewer 1.1.5 (another app) so it is my opinion that the MLV's are fine.
After reviewing the above attachment, please let me know if you require an MLV file, (I'll have to shoot a short take that will be easy to upload)
Maybe it's an EOS M thing. But I have the opposite thing happening. I can make the dots go away in MLRawViewer, but comes back when I render them out in either MOV/DNG.
It seems to not handle squeezed footage properly yet, but that's just my observation.
I'm getting pink/magenta highlights on 50D footage. Is this an MLRawViewer issue or more likely a 50D black level issue? I'm also curious, would a highlight recovery tool, like the one in ACR, be at all possible?
For realtime video encoding, codecs must be implemented in hardware. If it was as simple as putting ffmpeg on the camera, somebody would have done it a long time ago.
Pink dot removing is not a very mature feature, it shouldn't behave the way you are seeing.
Some questions:
1. Do you have the stripe removing turned on - there should be an icon with vertical stripes and an X through it. If there's no X, click to enable it otherwise no there is pink dot removal in use.
2. If the X is on, do you see the dots when paused, or if you click the quality icon or press Q to enable CPU demosaicing? That's the same mode used for exporting.
Hey,
when exporting from mlrawviewer the program will get so far and then freeze and I have to manually quit the program. It's only just started doing this. Any ideas (other than "reinstalling" the program i.e unzipping and replacing because I've tried that) It does this about about 8 out of ten attempts. If I keep trying it I will eventually get an export after many failings of the same raw at varying export percentages.
Do you plan to include ProRes 422 export in 1.3? ProRes4444 is great, but it's hard to justify the file size when the cameras themselves are only shooting 422 anyway.
The red dot is removed but feature is there. Try pressing Y after starting the export to see if processing starts. Y pauses/ resumes
Hey,
I could use some help with importing LUT's.
I press shift+L and choose a LUT, but it is not working. These luts are 3D, but I cant get them to work with MLRawViewer. I press shift+up/down and nothing happens. If I go through the 1D luts (left/right) I only find the ones included from MLrawviewer. Thinking maybe they were interpreted as 1D luts.
Do the .cube files have to be in a specific location?
Or is there something else I am doing wrong?
Thank you.
When will 1.3 be up?
If you are on windows, you need to apply the patch file on bitbucket to make LUT importing work. Will be fixed in 1.3
@sanzasn12: dualiso implementation would be superhandy, with the "-same level option on" for flickerfree dngs :)
greets.
Is there a plan to get audio sync in Resolve working?
second problem is that i can not load any 3d luts? they are not previewed.. 1d luts are previewed..
yes, the list stays empty - no luts available although i imported them.. :)
Thank you baland! You are top notch!
Is it possible to download that fixed version anywhere? Cause I have no idea how to compile it ;(
Gotta start working with the mlrawviewer and prores a bit more. I first did this dual iso sequence in after effects and acr and the time consuming workflow is such a tragedy compared to mlrawviewer.
This is a quick edit from the files coming from mlrawviewever.
@baland:
Would it be possible to include a 5d mk3 tuned vertical stripes correction too? Thx
Noob questions. Why the dng obteined with rawmagiclite are brighter? Someone has tried the new compressed dng? Are there some serious quality loss when playing with colours?
@ baland:
Is the problem lack of time, code complexity or the fact that you dont need it?
Your tool is so great - a must for all owners with ml cams. Never heared that the code must be optimized for a special cam,
So tell us how we can make the unlikely happen? Greets
Hi,
First off, thank you for developing such an awesome RAW workflow enhancer!
I've been playing around with the MlRawViewer for a few days now and everything was incredibly smooth until the last test I did which left me helpless. I was recording my RAW files as per usual and put them on my PC. I fired up MLRV, fiddled with the settings and tried to export the footage (one 20sec file with 50fps and one 25sec file with 25fps). MLRV just creates the .WAV-files to the specified directory for both MLVs (e.g. M04-1508.WAV + M04-1508_00.WAV for one file) and then stops the export at 0.00%.
What to do?
It seems to me that yes, it's slower. But without multithread (that it's difficult to implement if I remember it right) this is the max.
For me the only thing is the hot pixel removal, it seems to not have any effect (watching the dng in resolve), if it would be possible to make it effective it would be really useful.
Yes I have it. I'm still using RAW for the extra stability and performance, can I send you this? Do you also need the dngs that are created?
Things to check
1. Check the export directory is valid. Press W and select a folder
2. If export still stays on 0%, press Y in case you have paused the exporting process
3. Find the log file and send to me. Look in your home folder for the hidden ".mlrawviewer" folder, and find mlrawviewer.log inside that.
Can anyone please help?
Im running windows 8.1 and I cannot get MlRawviewer 1.2.3 working properly. It is probably something that I have done in the set up.
When I go to open the app it will ask for the mlv file to be opened then when I select the file the program opens for a split second then it closes.
So far I downloaded the zip, Unzipped it. Downloaded Python, installed it. (i dont know if I am required to link the programs some how). And shot my first mlv footage. Now I need to convert to DNG some how for use in After effects.
Any Ideas of where I may have gone wrong?
Thanks.
Ok, I'll try 1.2.3 and report back.
(Back)
Hmm...1.2.3 works for me. No pink.
TOS_Maverick could you give us so me info (folder/filenaming) and at least one dng and a WAV?
Something about 0.4 stops.The DNG from RAWMagic has BaselineExposure: +0.40. I'm not sure why. In MLVFS, I put the "raw_info.exposure_bias" here, but I've never really seen it be anything other than zero.
@Tos_Maverick. ah, ok, thats nothing especial. for this "media"-behaviour you just need kind of filenaming-convention.
folder: blabla_C0000
dng-file: blabla_C0000_00001.dng
(for example)
thats the reason i built the filenamegenerator into raw2cdng. interesting would be the part with embedded audio, does this work? look here (http://www.magiclantern.fm/forum/index.php?topic=10861.0) and here (http://www.magiclantern.fm/forum/index.php?topic=11520.0).
I've noticed that Curves and luts don't properly apply to squished 60p footage when exporting to ProRes. Footage always comes out much darker.
@baldand
[imghttp://http://(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fi1240.photobucket.com%2Falbums%2Fgg486%2F7kndp9gc%2Fb103ce34-6e77-46aa-9ef0-3457d5537986_zpsb64551ab.png&hash=a0dcf2b7ffb94ff2044ba767d3c8191a) (http://s1240.photobucket.com/user/7kndp9gc/media/b103ce34-6e77-46aa-9ef0-3457d5537986_zpsb64551ab.png.html)/img]
Using Lightroom 5.6.
I've noticed that Curves and luts don't properly apply to squished 60p footage when exporting to ProRes. Footage always comes out much darker.
I have similar problem, but I don't know if i am doing something wrong. I open the MLV, export the DNG and open in DaVinci, and the results are...
(https://www.magiclantern.fm/forum/proxy.php?request=http%3A%2F%2Fi108.photobucket.com%2Falbums%2Fn29%2FScatsy%2FCapturadepantalla2014-10-06alas150728.png%7Eoriginal&hash=32803bee606e1a34117f61a522d40402)
I Have this problem in 1.3.2 version too
Would it be possible to include noise reduction function or sharpen function ? thanx
Problem signature:
Problem Event Name: APPCRASH
Application Name: mlrawviewer.exe
Application Version: 0.0.0.0
Application Timestamp: 514e2c2f
Fault Module Name: bitunpack.pyd
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 543016a3
Exception Code: c0000005
Exception Offset: 00001347
OS Version: 6.1.7601.2.1.0.256.1Hi friends, Does MLRawviewer 1.2.3 or any version change the .mlv file characteristics (permanently)? Because the pink horizontal line problem that I am facing for a couple of months now seems to arise after being played in MLRawviewer. That pink strand is present in cdng extracts too and also seen in rendered output from editing or color correction software. The same file I had as a backup in another folder, when played for the first time in MLRawviewer did not show the pink lines. This is not always true as I also see pink lines in some first time opened mlv footage too. I use mlrawviewer a lot as i see 50-100 footage as rushes daily.
So just wanted to know if the viewer changes the characteristics of mlv file permanently. I am using april 2014 build ML, MLrawviewer1.2.3 and raw2cdng 1.6.1.
@baldand -- Thanks for the clarification on that part with the DNG's exports regarding Mac's. However, Once I tried to uninstall 1.3.2 and install 1.2.3 and now whenever I try to run it... nothing pops up like as if I didn't install it properly but I know I did.
Thoughts?
Hi,
Long time didn't tried MlRawViewer and now that i tried i run in 2 problems and maybe some one here in the forum can help me on this.
1- I have to format my main disk and install everything from new. I have install Premiere CC 2014 and now the MOV files that came out of MlRawViewer can't be read from Premiere. I have install Quick Time Pro but still can't read them. Do i need to install any kind of codec?
2- I was waiting for the version with stripes/noise removing tool and there it is, thanks =)) So i went to my MLV files to process them again and remove the noise. But i encounter one problem, especial with one clip. Where the highlight blow, it come out blue... the older DNG's are ok but with this new version it come like this. What is better to send for analyze? Maybe one DNG extract from the new and other DNG from the old conversion where everything is ok? For comparison?
PC
Win 7 i5
GeForce GTX 460
8GB Ram
Thnaks =)
Hi Baldand,
Sadly MlRawViewer Stop playing mlv files, It look like it crashes.
mac OSX mavericks.
Here is what i know,
1. when i am trying to play an mlv file nothing is happen (command option escape - shows the app for a blink and then it disappear)
2. It happens in 1.3.2 and also in 1.2.3
3. the app plays cdng and dng with no problem.
Your app is the number one viewer for me, i am using it from day 1.
Please help.
o.k got it, it is the .mld from the mlvfs.
Your app is still the Best mlv viewer and render around!
Thank you Baldand.
Just told you... MLVFS,
After deleting the empty folders ".mld" wich created by mlvfs your app came back to life.
Here's the CR from the latest crashing when exporting as DNG's...
https://www.dropbox.com/s/tyadlbg2tpedcpt/Mlrawviewer_CR.pdf?dl=0
Thanks. Looks like you managed to find a bug in the new lossless jpeg encoder.@Baldand -- Sure here they are...
Is it possible for you to share the (or an?) MLV that triggers this?
@Baldand -- Sure here they are...
https://www.dropbox.com/sh/8ypj1tj62al8j0b/AADDeukEIewP6b-zkfOAu2C8a?dl=0
As mentioned before I'm getting lock ups when exporting. I recently deleted everything and started again but it's still happening.
Here is the latest log file log file
https://www.dropbox.com/s/dmjbqgh9k6250bm/mlrawviewer.log?dl=0
CPU Intel i7 4930k
Nvidia 670GTX
RAM 32GB 1866mhz ( I think that's the speed anyway ) Quad Channel
Hybrid Seagate SSD 1 TB Win 7 ( Although SATAiii drives I work on for projects. Mainly 1TB - 3TB 7200rpm)
#1 - I was able to export as DNG's with original MLV folder on latest MlRawViewer (1.3.2) -- so that makes sense why you weren't able to duplicate the issue I was referring to earlier. (But since it was shot in DUAL-ISO so I'll need to convert it obviously)
Sounds good, No problem & Thanks! However, would you happen to have a preferred way to use dual ISO MLV if you wanted to be able to use your software as well as others when necessary?
Currently converting w 20-bit cr2hdr within LR -- stand by! (I'm still curious whether if it would still work or not)
Sorry, I can't give any guidance regarding dual-ISO as I only have a 7D, which sadly doesn't support dual-ISO video. If anyone has found some step in the dual-ISO workflow which MlRawViewer can help with as-is, that's great, but right now there is no explicit support for dual-ISO in the tool.
@DeafEyeJedi:
could you provide a short DualISO-Clip for the samplefiles (http://www.magiclantern.fm/forum/index.php?topic=11899.0)?
hmm. think most interesting would be 5DIII DualISO, EOS-M should be interesting cause of the af-pattern on sensor.
Now the only other idea that popped into my head is, what's the possibility of porting some of this code to a quick look plugin?
Quick and nasty lo-res preview would suffice, just something to make navigating heaps of arbitrarily named MLVs a bit more visual.
I can help with the quicklook framework side though I'm not so good with plain C.
@baldand It seems to crash with or without stripe correction on.
How do I get version 1.3.2?
Well done to all the developers of MLRawViewer!
Now I'm may be about to ask a silly question! I have been happily using v1.1.6, but decided the other day to update to v 1.2.3. But when I unzipped the file (I'm running win7), nothing would work. The exe file does not run, nor if I drop an MLV file on it does anything happen. And no LOG file is produced in my User directory. On further investigation, v1.1.7 will work, but not 1.2.0 or anything later (where there has obviously been a change since there were only 3 files in the zip folder up to v1.1.7, but 878 files for all later versions). Am I doing something incredibly stupid?
Thanks.