Messages

Yeah I agree with you, importing individual image sequences is a pain!But Rigth now I can't get anything else than H264 working for proxy video, and that's basicaly what we try to avoid shooting raw!

But I do not see any problems with this... We do proxies with which we work in NLE, then do XML and conform in Resolve. Where we can color correct and grade what we want. Or am I wrong? (Of course, it remains to solve the problem with the right conform XML in Resolve)

So leaving the video out field blank will cause the video proxy generation to fail so I will just have tiff sequences in individual folders? Nice, I will try that, thanks. BTW I changed the raw2dng to the latest one and I'm still getting pink tones from my 50D files, but raw2dng does it too :/

No, video proxy will generate near the original RAW and TIFF will generate whare you set. In RAWanizer video proxy generate from tiff proxy. And yes! I also have pink in overbright areas


In Resolve I fix this with HUE vs SAT but it's strange...

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

Yes, it's possible!



Tiff will be generated in this folder. But, how do you think to work with proxy tiff sequences? In Premiere, for example, when I import image sequence, I need to select each sequence and press "import as sequence" button. And this is for avery clip... Very painfully and inefficiency.

Took a break from programming and went out in my garden with my 5D mkII. Processed with RAWanizer of course

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;)

I'm still waiting for some xml-examples - maybe after analyizing them we can find any hints for solving - we have to narrow down the problematic factor - is it in the dng-tags or is it kind of naming-convention-problem? where does it happen?! is resolve working with its xml-files if you export and right then import them? etc pp..

Hi chmee, I create little project for testing and include all needed files on it (prproj file, xml, proxy video, source raw and cinemadng)

here https://drive.google.com/folderview?id=0BxDyTWKlBKcWd1dpelQtMEh3Wms&usp=sharing

Hope this will help us to brake this problem!

Hello everybody! I read a lot of branches of this forum and test such workflow (sorry again for my english)

1. RAW -> CinemaDNG with  raw2cdng http://www.phreekz.de/wordpress/2013/06/magiclantern-raw2cdng-cinema-dng/
2. RAW -> Proxy TIFF sequence or video with RAWanizer http://www.magiclantern.fm/forum/index.php?topic=5557.0
3. Edit Proxy in Premiere
4. Premiere -> XML or EDL
5. Conform xml in Davinci Resolve and grade
6. Resolve -> final Export

I think that is the right approach that can be applied to a real project, but... I failed at step 5. Resolve wrong conform XML and EDL. Cuts right, but content wrong.
My fils name:

Proxy video - M0000000.mov M0000001.mov etc
CinemaDNG sequence
M0000000_000000.dng
M0000000_000001.dng
.....
M0000000_000150.dng
===============
M0000001_000000.dng
....
M0000001_000001.dng
...
in Resolv in media pool it look like M0000000_[000000-000150].dng

Maybe problem in naming?... I not experimental else with tiff proxy (but this method more complicated becose importing tiff sequence in Premiere Pro very painfull=( and performance with tiff lower then with mov.

So, your comments about this method and troble

Yeee!!! It's Work! I don't now what I did, but...
This is my screens, maybe it halps anybody (sorry for my english, this is not my native language)



RAWanizer create M0000002.proxy.mov file near original RAW file

I have same problem as above...

20:08:28 Start extracting dng from M0000000.RAW
20:08:30 Finished
20:08:30 Start converting tiff from M0000000.RAW
20:08:43 Finished
20:08:43 Start creating proxy from M0000000.RAW
20:08:43 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
Input #0, image2, from 'X:\RAW_Test\Source\Proxy_TIFF\M0000000.proxytiff\M%06d.tiff':
  Duration: 00:00:09.20, start: 0.000000, bitrate: N/A
    Stream #0:0: Video: tiff, rgba, 960x540, 24 fps, 24 tbr, 24 tbn, 24 tbc
X:\RAW_Test\Source\Video_Proxy\M0000000.proxy.mp4: No such file or directory

20:08:43 All items Finished

RAWanizer ver 0.5.3 Win 7 x64
no any kind of proxy =(

Is there a way to batch convert dng-sequences to tiffs? So that we do not have to convert shot by shot?

I think he was referring to how to automate the process, if there is a lot of folders with DNG. That's a good question, a very vital. Because the test shooting 3-4 plans is one thing, but when they are 100-200, etc. Automation is very relevant question. Who has ideas? (sorry for my English, I write through translator)