RAWanizer - windows batch generation of video files from RAW

[marten]

Hey, I did quite a lot of testing,
It seems that I can only outpout working h264, prores444 does not play either in premiere or vlc/media player, and DNxHD seem to outpout regular H264? However I noticed that checking the box "use ffmbc" makes thing work better for vidéo generation.
The H264 is nice as a proxy but it's not the best for editing... would it be possible to use RAWanizer to outpout folders containing TIFFs to be used as images sequences? I guess it's possible as it already does it for video proxy generation.
Adam

The prores444 preset i found somewhere on the web. It doesn't play in my vlc, but my sony vegas nle opens the file fine.

The DNxHD does not output regular h264, at least not for me. I get a valid DNxHD that open up fine in sony vegas and also plays fine with vlc.

If you only want tiffs I can see two workarounds. Just let the tool make the proxy mp4 and then trash the mp4 file, the TIFFs will still be there. Or choose to make mp4 and also uncheck 'do all process steps before next item in queue', then it will first extract all dngs for the raws, then it will create all tiffs. It will also create all mp4 in the last step, but then you can just hit cancel and all tiffs should be there.

[marten]

I have uploaded a new version, see link in first post.

Now settings are applied when processing starts which I hope will help some people who experience that the settings "does not work" since they have changed settings after items has been added to the queue.

[marten]

Niiice!!! What optic did you use there? One funny comment - I watched the video clip and I were singing birds outside the window ... I did not realize that they are singing outside my window, and not in the video! Very inspiring! Thank you;)

Used a 300/2.8 for all the shots. Well, I think I even used a 2x extender on some.

[marten]

Is the DNxHD/185 a 8bit or a 10bit version?

To tell you the truth, I don't know. If you look at the settings for the preset you see all parameters, I do not add to that.

[marten]

I was more looking at a simpler workflow that could be used on simple projects, ouputing to a 10-12bit video file that could directly be imported into premiere and retain much of the info for simple CC, as I don't own resolve nor know how to use it :/

So far I have only been able to oupout H264 or prores 444 files that premiere won't open?? the later seem to be a good file for what I want to do but maybe my premiere setup is not good, I have been able to read the files with quicktime fine...

I forgot, if you have problem with DNxHD, you may have to download the DNxHD codec from Avid website (free). I think ffmpeg is relying on that somehow. On one machine I had to do that to get it to work.

[bzhwindtalker]

The prores444 preset i found somewhere on the web. It doesn't play in my vlc, but my sony vegas nle opens the file fine.

The DNxHD does not output regular h264, at least not for me. I get a valid DNxHD that open up fine in sony vegas and also plays fine with vlc.

I have no froking idea of what I did but now prores is working... just as I wanted it to! the only thing tat changed is the resolution, I was previousely shoting on a T2i at 1024px, those would not play when converted to prores, now it seems to be working with 50D files at almost 1600px, I don't see how this could have caused the issue.

 Anyways thanks for the soft man, it really eases the workflow for me!

Does it get simpler than this?

Camera > .RAW > RAWanizer> Prores 444 > premiere > H264> vimeo

I did not test this for data loss over 16bit tiff but that's something I will do!

[dandeliondandy]

Any idea why I'm getting my error?

Thanks!

[marten]

Any idea why I'm getting my error?

Thanks!

I did give a suggestion to look at in a post http://www.magiclantern.fm/forum/index.php?topic=5557.msg50958#msg50958. I do believe ffmpeg has problem with your resolution.

[marten]

I did not test this for data loss over 16bit tiff but that's something I will do!

If you set dcraw settings to 16-bit the tiff files will be 16-bit for sure. But I don't know for sure if ffmeg/ffmbc handles them correctly, but I hope so.

[mkrjf]

Anybody working or interested in working on Mac osx equivalent?!
Even if it is a CPU hog getting prores444 from Mac workflow would be perfect

[KahL]

Sooooo I accidentally deleted the DNxHD option and now I cannot get it back. Is there any way of retrieving it (ver 0.5.4)? :-(

[marten]

Sooooo I accidentally deleted the DNxHD option and now I cannot get it back. Is there any way of retrieving it (ver 0.5.4)? :-(

You can delete the user.config files found in C:\Users\YourUserName\AppData\Local\RAWanizer folder. That should bring back all defaults, but you'll loose all your other settings.

Or you can take this string and paste it to a new setting:
-threads 8 -r {InputVideoFps} -i "{InputVideoName}" -i "{InputAudioName}" -vcodec dnxhd -b 185M {ScaleTo1920x1080} -r {InputVideoFps} {Parameters} "{OutputVideoName}.mov"

[bzhwindtalker]

Would it be possible to add a checkbox for deleting DNG after proxy creation? Sorry to just ask and expect 
Btw I converted 32GB of footage without issue on my laptop. It just stopped on the few last clips when my HDD was full haha

[marten]

Would it be possible to add a checkbox for deleting DNG after proxy creation? Sorry to just ask and expect 
Btw I converted 32GB of footage without issue on my laptop. It just stopped on the few last clips when my HDD was full haha

Added in new version 0.5.5 (link in first post)

[marten]

Sooooo I accidentally deleted the DNxHD option and now I cannot get it back. Is there any way of retrieving it (ver 0.5.4)? :-(

In version 0.5.5 there is a button on the file settings tab to restore default presets.

[bzhwindtalker]

Added in new version 0.5.5 (link in first post)

Tanks ! You rock!
Now I just need to get rid of the pink tone (issue not related to RAWanizer)

[KahL]

I'm getting the same error as everyone else beforehand.

13:54:30 Start converting tiff from Cntrl Park North.001.dng
13:57:32 Finished
13:57:32 Start creating proxy from Cntrl Park North.001.dng
13:57:32 Failed:
ffmpeg version N-35966-g1d0ae92, Copyright (c) 2000-2011 the FFmpeg developers
  built on Dec 19 2011 13:01:15 with gcc 4.6.2
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-runtime-cpudetect --enable-avisynth --enable-bzlib --enable-frei0r --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
  libavutil    51. 32. 0 / 51. 32. 0
  libavcodec   53. 46. 1 / 53. 46. 1
  libavformat  53. 27. 0 / 53. 27. 0
  libavdevice  53.  4. 0 / 53.  4. 0
  libavfilter   2. 53. 0 /  2. 53. 0
  libswscale    2.  1. 0 /  2.  1. 0
  libpostproc  51.  2. 0 / 51.  2. 0
R:\Central Park North 110st\Cntrl Park North.001.dng\proxytiff\Cntrl Park North.001-%06d.tiff: No such file or directory

13:57:32 All items Finished


What's happening here? How do I prevent this?

[marten]

I'm getting the same error as everyone else beforehand.

13:54:30 Start converting tiff from Cntrl Park North.001.dng
13:57:32 Finished
13:57:32 Start creating proxy from Cntrl Park North.001.dng
13:57:32 Failed:
ffmpeg version N-35966-g1d0ae92, Copyright (c) 2000-2011 the FFmpeg developers
  built on Dec 19 2011 13:01:15 with gcc 4.6.2
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-runtime-cpudetect --enable-avisynth --enable-bzlib --enable-frei0r --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
  libavutil    51. 32. 0 / 51. 32. 0
  libavcodec   53. 46. 1 / 53. 46. 1
  libavformat  53. 27. 0 / 53. 27. 0
  libavdevice  53.  4. 0 / 53.  4. 0
  libavfilter   2. 53. 0 /  2. 53. 0
  libswscale    2.  1. 0 /  2.  1. 0
  libpostproc  51.  2. 0 / 51.  2. 0
R:\Central Park North 110st\Cntrl Park North.001.dng\proxytiff\Cntrl Park North.001-%06d.tiff: No such file or directory

13:57:32 All items Finished


What's happening here? How do I prevent this?

As it states in the known issues in original post (easy to miss, I understand): Does not work with spaces in the file names. I think this is your problem.

[dandeliondandy]

The ffmpeg libx264 can be picky about video resolutions. 940x353 sounds like it could be problematic. In the preset for mp4 I added a scale setting that has worked for me. Can you check that you have -vf "scale=1920:trunc(ow/a/2)*2" in the preset you are using. This scales up to 1920 and may cut some lines to make it work.

You can change the 1920 width to something you like better.

Sorry, didn't see this! Thanks. I didn't have anything like that in my preset so I added it as the bottom line under the other settings, and I'll give it a test soon to see if that helps anything.

[KahL]

As it states in the known issues in original post (easy to miss, I understand): Does not work with spaces in the file names. I think this is your problem.

Ooooohh, I see. GOTCHA, and thanks, man. Pardon my ignorance on that O_o

[creese13]

Nice App Marten. Works Seamless with the raw files right from the camera.  When I try to use "Make video from output of external dng converter", it gives error msg.  I have no spaces in the file name and created sub "tiff" folder within the dng folder.  Any Clue what I'm doing wrong? I use the same file structure the app creates when converting the org raw.  Funny thing is if I delete the video created from the raw process, select "dng folders" option at the top and change the "proxytiff" folder to just 'tiff" it recreates the video with no problem, but with outside dng file folders not created by this app it doesn't like for some reason.  Hope that makes sense. 

01:25:34 Start creating video from DNG002.dng
01:25:34 Failed:
ffmpeg version N-35966-g1d0ae92, Copyright (c) 2000-2011 the FFmpeg developers
  built on Dec 19 2011 13:01:15 with gcc 4.6.2
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-runtime-cpudetect --enable-avisynth --enable-bzlib --enable-frei0r --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
  libavutil    51. 32. 0 / 51. 32. 0
  libavcodec   53. 46. 1 / 53. 46. 1
  libavformat  53. 27. 0 / 53. 27. 0
  libavdevice  53.  4. 0 / 53.  4. 0
  libavfilter   2. 53. 0 /  2. 53. 0
  libswscale    2.  1. 0 /  2.  1. 0
  libpostproc  51.  2. 0 / 51.  2. 0
C:\Users\Reese\Desktop\test\DNG002.dng\tiff\DNG002-%06d.tiff: No such file or directory

01:25:34 All items Finished

[oddname]

What am I doing wrong if I try the cineform export-option and get a really noisy image that even is worse than the in-camere h264?  Looks like really high iso noise, but its not
Doesnt look like raw to me at all.

Other modes work fine.

[marten]

What am I doing wrong if I try the cineform export-option and get a really noisy image that even is worse than the in-camere h264?  Looks like really high iso noise, but its not
Doesnt look like raw to me at all.

Other modes work fine.

For cineform the all conversion is handled by the cineform tool. Try asking you question here http://www.magiclantern.fm/forum/index.php?topic=5479.200

[marten]

Nice App Marten. Works Seamless with the raw files right from the camera.  When I try to use "Make video from output of external dng converter", it gives error msg.  I have no spaces in the file name and created sub "tiff" folder within the dng folder.  Any Clue what I'm doing wrong? I use the same file structure the app creates when converting the org raw.  Funny thing is if I delete the video created from the raw process, select "dng folders" option at the top and change the "proxytiff" folder to just 'tiff" it recreates the video with no problem, but with outside dng file folders not created by this app it doesn't like for some reason.  Hope that makes sense. 

01:25:34 Start creating video from DNG002.dng
01:25:34 Failed:
ffmpeg version N-35966-g1d0ae92, Copyright (c) 2000-2011 the FFmpeg developers
  built on Dec 19 2011 13:01:15 with gcc 4.6.2
  configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-runtime-cpudetect --enable-avisynth --enable-bzlib --enable-frei0r --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
  libavutil    51. 32. 0 / 51. 32. 0
  libavcodec   53. 46. 1 / 53. 46. 1
  libavformat  53. 27. 0 / 53. 27. 0
  libavdevice  53.  4. 0 / 53.  4. 0
  libavfilter   2. 53. 0 /  2. 53. 0
  libswscale    2.  1. 0 /  2.  1. 0
  libpostproc  51.  2. 0 / 51.  2. 0
C:\Users\Reese\Desktop\test\DNG002.dng\tiff\DNG002-%06d.tiff: No such file or directory

01:25:34 All items Finished

According to the log, ffmpeg can't find any files matching the path you see at the bottom. Can you verify that you have files matching that pattern. The file name of the first file should be DNG002-000000.tiff, second DNG002-000001.tiff

Which version of RAWanizer are you running?

[creese13]

According to the log, ffmpeg can't find any files matching the path you see at the bottom. Can you verify that you have files matching that pattern. The file name of the first file should be DNG002-000000.tiff, second DNG002-000001.tiff

Which version of RAWanizer are you running?

Thanks Marten for the reply.  I'm using the latest version and I see what's happening.  The org program I used created the DNG file names with an underscore and your program sees file names with dash.  So the org file name was DNG002_000000.tiff, I changed the file name to  DNG002-000000.tiff and it worked perfect.  Thanks hope this helps someone else.