Menu

Show posts

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

Show posts Menu

Messages - bashi

#1
This feature would be really nice!

On this site are the needed signals listed:

http://marcuswolschon.blogspot.de/2012/04/easterhegg-basel-2012.html

"The protocoll is RS232 at 3.3V with 2400bps 8n1
The remote sends 2 sequences of 2 bytes with a small delay:
Record: 0x81 0x00 | 0x80 0x00
Play:   0x82 0x00 | 0x80 0x00
Stop:   0x84 0x00 | 0x80 0x00
ffwd:   0x88 0x00 | 0x80 0x00
rwd:    0x90 0x00 | 0x80 0x00
vol+:   0x80 0x08 | 0x80 0x00
vol-:   0x80 0x10 | 0x80 0x00
rec+:   0x80 0x20 | 0x80 0x00
rec-:   0x80 0x40 | 0x80 0x00
mic :   0x80 0x01 | 0x80 0x00
ch1 :   0x80 0x02 | 0x80 0x00
ch2 :   0x80 0x04 | 0x80 0x00"
#2
Quote from: Lucas480 on July 09, 2013, 08:33:55 AM
Hey, thanks for the program but, How to deactivate DNGs for keep only prores 4444?

currently not possible. The raw2dng in raw2dng.app is only able to output files to folder. We could delete it afterwards though.. IMO the raw2dng should be abgle to be piped - so we can 1. don't save them to disk, only keep them in memory and 2. we could extract frame ranges. This needs to be done by someone familiar with C and raw2dng.
#3
Quote from: Olli5D on July 17, 2013, 04:54:58 PM
this raw2dng gives me directly Prores4444, Just Drag and Drop. cool.

But now i checked the prores files and they are shit.

The color within a shot keeps changing. Not really from frame to frame,
but with in 3 or 4 frames, skin tones suddenly green or blue.
Sucks.

But when i do Photoshop then export to tiff then quicktime pro to sequence,
everything fine.

Now I need a new converter from raw to dng,
cause raw2dng does the prores transfer automatically and that keeps ages.

known issue.: currently the raw converter calculates WB for each frame, will be resolved by option to keep WB same for all
#4
Quote from: menoc on July 17, 2013, 05:28:30 PM
Is this still a problem with raw2dng?

For some reason, the proresHQ 4444 file put out by raw2dng is unrecognized by my system - OSX 10.8.4





Anybody has any idea why? Here's the resultant text:



raw2dng converter GUI for OsX
Beta ver.0.13

M28-1957 File Supported
Generating ProResHQ 4444 with FPS: 23.976
ffmpeg version 1.2.1-tessus Copyright (c) 2000-2013 the FFmpeg developers
  built on May  9 2013 21:58:14 with llvm-gcc 4.2.1 (LLVM build 2336.1.00)
  configuration: --prefix=/Users/tessus/data/ext/ffmpeg/sw --as=yasm --extra-version=tessus --disable-shared --enable-static --disable-ffplay --enable-gpl --enable-pthreads --enable-postproc --enable-libmp3lame --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-libspeex --enable-bzlib --enable-zlib --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libxavs --enable-version3 --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvpx --enable-libgsm --enable-libopus --enable-fontconfig --enable-libfreetype --enable-libass --enable-filters --enable-runtime-cpudetect
  libavutil      52. 18.100 / 52. 18.100
  libavcodec     54. 92.100 / 54. 92.100
  libavformat    54. 63.104 / 54. 63.104
  libavdevice    54.  3.103 / 54.  3.103
  libavfilter     3. 42.103 /  3. 42.103
  libswscale      2.  2.100 /  2.  2.100
  libswresample   0. 17.102 /  0. 17.102
  libpostproc    52.  2.100 / 52.  2.100
[image2pipe @ 0x102019600] Stream #0: not enough frames to estimate rate; consider increasing probesize
[image2pipe @ 0x102019600] Estimating duration from bitrate, this may be inaccurate
Input #0, image2pipe, from 'pipe:0':
  Duration: N/A, bitrate: N/A
    Stream #0:0: Video: ppm, rgb48be, 1920x1080, 23.98 tbr, 23.98 tbn, 23.98 tbc
Output #0, mov, to '/Users/oscarmoreno/Desktop/test/M28-1957.mov':
  Metadata:
    encoder         : Lavf54.63.104
    Stream #0:0: Video: prores (apch / 0x68637061), yuv444p10le, 1920x1080, q=2-31, 200 kb/s, 11988 tbn, 23.98 tbc
Stream mapping:
  Stream #0:0 -> #0:0 (ppm -> prores_kostya)
frame=    3 fps=2.1 q=0.0 size=    2844kB time=00:00:00.12 bitrate=186177.9kbits/s   
frame=    4 fps=1.6 q=0.0 size=    3792kB time=00:00:00.16 bitrate=186204.1kbits/s   
frame=    5 fps=1.4 q=0.0 size=    4740kB time=00:00:00.20 bitrate=186198.5kbits/s   
frame=    6 fps=1.3 q=0.0 size=    5688kB time=00:00:00.25 bitrate=186211.6kbits/s   
frame=    7 fps=1.3 q=0.0 size=    6637kB time=00:00:00.29 bitrate=186225.3kbits/s   
frame=    8 fps=1.2 q=0.0 size=    7585kB time=00:00:00.33 bitrate=186231.5kbits/s   
frame=    9 fps=1.2 q=0.0 size=    8533kB time=00:00:00.37 bitrate=186225.4kbits/s   
frame=   10 fps=1.2 q=0.0 size=    9481kB time=00:00:00.41 bitrate=186221.4kbits/s   
frame=   11 fps=1.1 q=0.0 size=   10428kB time=00:00:00.45 bitrate=186206.4kbits/s   
frame=   12 fps=1.1 q=0.0 size=   11377kB time=00:00:00.50 bitrate=186209.4kbits/s   
frame=   13 fps=1.1 q=0.0 size=   12325kB time=00:00:00.54 bitrate=186211.3kbits/s   
frame=   14 fps=1.1 q=0.0 size=   13273kB time=00:00:00.58 bitrate=186209.0kbits/s   
frame=   15 fps=1.1 q=0.0 size=   14221kB time=00:00:00.62 bitrate=186216.2kbits/s   
frame=   16 fps=1.1 q=0.0 size=   15169kB time=00:00:00.66 bitrate=186212.7kbits/s   
frame=   17 fps=1.1 q=0.0 size=   16118kB time=00:00:00.70 bitrate=186218.8kbits/s   
frame=   18 fps=1.1 q=0.0 size=   17065kB time=00:00:00.75 bitrate=186210.9kbits/s   
frame=   19 fps=1.1 q=0.0 size=   18013kB time=00:00:00.79 bitrate=186204.8kbits/s   
frame=   20 fps=1.1 q=0.0 size=   18961kB time=00:00:00.83 bitrate=186203.5kbits/s   
frame=   21 fps=1.1 q=0.0 size=   19909kB time=00:00:00.87 bitrate=186204.9kbits/s   
frame=   22 fps=1.0 q=0.0 size=   20857kB time=00:00:00.91 bitrate=186204.0kbits/s   
frame=   23 fps=1.0 q=0.0 size=   21805kB time=00:00:00.95 bitrate=186202.9kbits/s   
frame=   24 fps=1.0 q=0.0 size=   22752kB time=00:00:01.00 bitrate=186202.0kbits/s   
frame=   25 fps=1.0 q=0.0 size=   23701kB time=00:00:01.04 bitrate=186206.6kbits/s   
frame=   26 fps=1.0 q=0.0 size=   24650kB time=00:00:01.08 bitrate=186209.7kbits/s   
frame=   27 fps=1.0 q=0.0 size=   25597kB time=00:00:01.12 bitrate=186208.6kbits/s   
frame=   28 fps=1.0 q=0.0 size=   26546kB time=00:00:01.16 bitrate=186211.4kbits/s   
frame=   29 fps=1.0 q=0.0 size=   27494kB time=00:00:01.20 bitrate=186211.7kbits/s   
frame=   30 fps=1.0 q=0.0 size=   28442kB time=00:00:01.25 bitrate=186208.4kbits/s   
frame=   31 fps=1.0 q=0.0 size=   29389kB time=00:00:01.29 bitrate=186205.5kbits/s   
frame=   32 fps=1.0 q=0.0 size=   30337kB time=00:00:01.33 bitrate=186203.8kbits/s   
frame=   33 fps=1.0 q=0.0 size=   31284kB time=00:00:01.37 bitrate=186198.8kbits/s   
frame=   34 fps=1.0 q=0.0 size=   32233kB time=00:00:01.41 bitrate=186201.7kbits/s   
frame=   35 fps=1.0 q=0.0 size=   33181kB time=00:00:01.45 bitrate=186202.6kbits/s   
frame=   36 fps=1.0 q=0.0 size=   34129kB time=00:00:01.50 bitrate=186203.7kbits/s   
frame=   37 fps=1.0 q=0.0 size=   35077kB time=00:00:01.54 bitrate=186202.6kbits/s   
frame=   38 fps=1.0 q=0.0 size=   36026kB time=00:00:01.58 bitrate=186206.1kbits/s   
frame=   39 fps=1.0 q=0.0 size=   36973kB time=00:00:01.62 bitrate=186205.2kbits/s   
frame=   40 fps=1.0 q=0.0 size=   37922kB time=00:00:01.66 bitrate=186205.4kbits/s   
frame=   41 fps=1.0 q=0.0 size=   38869kB time=00:00:01.71 bitrate=186203.8kbits/s   
frame=   42 fps=1.0 q=0.0 size=   39817kB time=00:00:01.75 bitrate=186205.0kbits/s   
frame=   43 fps=1.0 q=0.0 size=   40765kB time=00:00:01.79 bitrate=186204.8kbits/s   
frame=   44 fps=1.0 q=0.0 size=   41713kB time=00:00:01.83 bitrate=186201.0kbits/s   
frame=   45 fps=1.0 q=0.0 size=   42660kB time=00:00:01.87 bitrate=186196.7kbits/s   
frame=   46 fps=1.0 q=0.0 size=   43608kB time=00:00:01.91 bitrate=186196.9kbits/s   
frame=   47 fps=1.0 q=0.0 size=   44556kB time=00:00:01.96 bitrate=186196.1kbits/s   
frame=   48 fps=1.0 q=0.0 size=   45503kB time=00:00:02.00 bitrate=186195.8kbits/s   
frame=   49 fps=1.0 q=0.0 size=   46452kB time=00:00:02.04 bitrate=186197.0kbits/s   
frame=   50 fps=1.0 q=0.0 size=   47401kB time=00:00:02.08 bitrate=186200.4kbits/s   
frame=   51 fps=1.0 q=0.0 size=   48349kB time=00:00:02.12 bitrate=186202.9kbits/s   
frame=   52 fps=1.0 q=0.0 size=   49298kB time=00:00:02.16 bitrate=186206.9kbits/s   
frame=   53 fps=1.0 q=0.0 size=   50247kB time=00:00:02.21 bitrate=186210.0kbits/s   
frame=   54 fps=1.0 q=0.0 size=   51195kB time=00:00:02.25 bitrate=186209.3kbits/s   
frame=   55 fps=1.0 q=0.0 size=   52144kB time=00:00:02.29 bitrate=186211.3kbits/s   
frame=   56 fps=1.0 q=0.0 size=   53092kB time=00:00:02.33 bitrate=186213.0kbits/s   
frame=   57 fps=1.0 q=0.0 size=   54041kB time=00:00:02.37 bitrate=186213.6kbits/s   
frame=   58 fps=1.0 q=0.0 size=   54988kB time=00:00:02.41 bitrate=186213.1kbits/s   
frame=   59 fps=1.0 q=0.0 size=   55936kB time=00:00:02.46 bitrate=186211.6kbits/s   
frame=   60 fps=1.0 q=0.0 size=   56884kB time=00:00:02.50 bitrate=186212.4kbits/s   
frame=   61 fps=1.0 q=0.0 size=   57832kB time=00:00:02.54 bitrate=186209.4kbits/s   
frame=   62 fps=1.0 q=0.0 size=   58779kB time=00:00:02.58 bitrate=186209.0kbits/s   
frame=   63 fps=1.0 q=0.0 size=   59727kB time=00:00:02.62 bitrate=186208.0kbits/s   
frame=   64 fps=1.0 q=0.0 size=   60675kB time=00:00:02.66 bitrate=186208.5kbits/s   
frame=   65 fps=1.0 q=0.0 size=   61624kB time=00:00:02.71 bitrate=186208.7kbits/s   
frame=   66 fps=1.0 q=0.0 size=   62572kB time=00:00:02.75 bitrate=186208.7kbits/s   
frame=   67 fps=1.0 q=0.0 size=   63519kB time=00:00:02.79 bitrate=186206.9kbits/s   
frame=   68 fps=1.0 q=0.0 size=   64467kB time=00:00:02.83 bitrate=186207.1kbits/s   
frame=   69 fps=1.0 q=0.0 size=   65415kB time=00:00:02.87 bitrate=186206.6kbits/s   
frame=   70 fps=1.0 q=0.0 size=   66364kB time=00:00:02.91 bitrate=186209.1kbits/s   
frame=   71 fps=1.0 q=0.0 size=   67312kB time=00:00:02.96 bitrate=186209.0kbits/s   
frame=   72 fps=1.0 q=0.0 size=   68261kB time=00:00:03.00 bitrate=186210.4kbits/s   
frame=   73 fps=1.0 q=0.0 size=   69208kB time=00:00:03.04 bitrate=186209.6kbits/s   
frame=   74 fps=1.0 q=0.0 size=   70158kB time=00:00:03.08 bitrate=186213.7kbits/s   
frame=   75 fps=1.0 q=0.0 size=   71106kB time=00:00:03.12 bitrate=186213.8kbits/s   
frame=  613 fps=1.0 q=0.0 size=  581090kB time=00:00:25.56 bitrate=186187.0kbits/s   
/Applications/raw2dng.app/Contents/Resources/script: line 40:  4661 Done                    "$DCRAW" -c -H 0 -6 -W -q 3 "$Wtemp" *.dng
      4662 Segmentation fault: 11  | "$FFMPEG" -f image2pipe -vcodec ppm -r "$FPS" -i pipe:0 -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10 -y -r "$FPS" "$FLDR$FILE_NAME".mov
Done



known issue, delete the last .dng in the folder(s). will be resolved
#5
Quote from: zmelms on June 26, 2013, 08:48:32 PM
10.8.4
QT x
CS6 all the newest stuff
and I have Apple Compressor installed for the ProRes components.

Here's the weird thing.  The only file that worked (aka was recognized by quicktime) was one that I hit the cancel button part way thru the conversion.

let's see, 1. can you open the last .dng in those folder without error?
if , this is a known issue and will be resolved. you can hack it to work by deleting this .dng while it is converting to video.

otherwise, After the conversion, click the arrow left near Details, can you copy to the content to pasteall.org or here?
#6
Quote from: zmelms on June 26, 2013, 03:05:04 AM
the prores4444 files are created but can't be ready by Premiere or Quicktime,  anyone else having this issue?  Also I can't find out how to turn off the creation of the prores files to save space since they don't work.

What os, qt and premiere version?

#7
sorry, should be: yuv444p10le

that's the "highest" i got to work.
#8
Quote from: pavelpp on June 25, 2013, 08:38:43 AM
What's the command line to convert to ProRes? I'd like first to work on dng's in Lightroom then export tif's to ProRes

ffmpeg -vcodec tiff -i &6d.tiff -r FPS -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt  yuv444p10le -y -r FPS OUTPUT.mov

cd to your folder containing tiff.
replace both FPS with your actual fps!
#9
Quote from: Gumadzon on June 24, 2013, 09:44:53 PM
Very interesting! But how to keep this dcraw to wb ratio and bring it to a prores 4444 video?What kind of correlation there's between dcraw and final wb kelvin number in final prores 4444 video? Are you trying to say that we don't need this information anymore?! Neither are we enabled to obtain this information in a different way?

sorry ;-) but i don't understand most of this...

the dng are raw bayer data, like image cr2 raw, has no wb applied. dcraw converts this raw image to a color image and there you set the wb (by multiplying the rgb (rgbg)). out of this images the video, in this case prores is made. I don't know of any (non-propiertary) video format that works with raw data. now there's the cinemaDNG format (not the same as DNG) that fills this gap, raw image data for video use.
#11
Quote from: silvertonesx24 on June 24, 2013, 05:36:12 PM
Isn't the raw data 442? If so, wouldn't Pro Res 444 be a waste of space?

the raw is even more than 444...
#12
Quote from: Danne on June 24, 2013, 04:57:03 PM
Regarding the whitebalance settings in raw to dng. Are the presets consistent kelvin-numbers? I understand auto is doing some kind of frame by frame stuff but maybe not the other presets? Would be golden with some kind of tumbnail before applying the whitebalance to the ProRes but it,s not necessary.
Awesome app guys!

what we use currently, dcraw, has no kelvin, unfortunately, but rgb multipliers. Auto setting currently does frame by frame - like to change that to take the wb setting from first (or whatever) frame and then apply this to all frames.

My version of raw2dng.app has full preview ;-) don't know if scrax is going to implement it... maybe i release my version separate...
#13
Quote from: Gumadzon on June 24, 2013, 02:17:09 PM
Previous workflow used conversion from DNGs to TIFFs in Photoshop and user was able to just select all frames in sequence WITHOUT doing any corrections. Can you add this "WITHOUT CORRECTION" feature to raw2dng to proceed prores 4444 video files? Is it clear to you?

not clear to me. There is no raw bayer to rgb or whatever conversion without some sort of "correction". After all you convert a black and white image to colors... You want uniWB? doubt it. You want fixed WB, what value then? You want adobe conversion? then use adobe...

#14
Quote from: frenchps49 on June 22, 2013, 09:47:22 PM
Yo
You are right. The last DNG is messed up. It happened to all the shots I have checked. I'd be glad to rerun one. You suggest to remove the last frame but how can I remove the last frame of the RAW file ??? The problem happens when I want the Prores 4444 from the Raw file. Thanks for helping.

prores is made from .dng anyway, so you can delete it after all the dng's are copied over and while the prores is made...

#15
Quote from: frenchps49 on June 21, 2013, 03:47:01 PM
Hi, Used 0.13. Computer says it can't open the prores sequence. It's not a video.
The end of the verbose inside the app:

"frame=  409 fps=1.7 q=0.0 size=  385499kB time=00:00:17.05 bitrate=185125.8kbits/s   
/Applications/raw2dng0.13.app/Contents/Resources/script: line 40:  2216 Done                    "$DCRAW" -c -H 0 -6 -W -q 3 "$Wtemp" *.dng
      2217 Segmentation fault: 11  | "$FFMPEG" -f image2pipe -vcodec ppm -r "$FPS" -i pipe:0 -vcodec prores_kostya -profile:v 3 -vendor ap10 -pix_fmt yuv444p10 -y -r "$FPS" "$FLDR$FILE_NAME".mov
Done"

If that can help you.

has this video 409 or 410 frames? if so try to delete the last frame and re-run. I got this error on a video, where the last .dng file is messed up.

otherwise try to open the .dng around frame 409 (408, 410) - are they ok?
#16
Quote from: meditant on June 22, 2013, 05:52:52 PM
Ok thanks for the info, in vlc 444 10 bits !

It exist a 14bits mov codecs ?

Best regards

I haven't found one yet. Currently i'm aiming at 12bit, but even this seems difficult... i've read somewhere that the setting we are using currently is 4444 12 bit, but that seem be wrong, since vlc says 10 bit...

If you want to use 14bit, use the cinemaDng converter and use those image sequences.

i personally kind of see no point in having a video that is equal or bigger in size than this cinemaDng would be..

i'm as well open for suggestions of other codecs - prores is really nice for editing, but it is soft.
#17
Quote from: jc on June 21, 2013, 07:13:07 PM
so yeah any thoughts on auto joining the 5d2 4GB files?
Thanks. James

for now you can join them manually:

open terminal then type:
cd /Volumes/bashi/Pictures/Raw (or wherever your RAW files are, you can just drag and drop the folder to terminal)
hit Enter
cat NAME.RAW NAME.R00 NAME.R01 > merged.RAW  (input as many .R00, .R01 you have)
hit Enter

then you have a .RAW that contains all raws - drop this merged.RAW to raw2dng.app
#18
Quote from: meditant on June 22, 2013, 09:01:06 AM
Hello,

With 0.13 i activate in the options ProResHQ 4444, but the generated .mov is in ProRes 422 HQ (With cmd + i or in FCPX)

What i do wrong ?

Best regards

You do nothing wrong. the movie is 4444, but it gets the wrong codec flag (its apch, shoult be ap4h) . this is an issue from ffmpeg. If you open the movie in vlc, you can see in info (cmd+i) decoded Format Planar 4:4:4 YUV. As well you can see the difference from 422 to 444 in some places, like very hard contrast, for example the canyon scene from lukas neumann. Not sure if this causes any problems - haven't found one.


#19
Quote from: cinema5D on June 19, 2013, 07:22:46 PM
Hm, nice idea, but the ProRes files I get are quite unusable. Correctly exposed RAW files turn into 3 stops underexposed .mov's that don't seem to have the color information needed to get them back up, results in extreme overall noise.

Also I'm not sure the automatic WB is needed since it should have been set correctly in camera, right? Only Green/Magenta Shift should be set to 0.

Thanks

i think the camera wb doesn't get saved - at least the dng don't have it saved in them...
#20
@all and scrax
It looks like the White Balance Automatic does apply on every image separately... This means it can change during the shot - not good.

@scrax: we might need to find a way do get the rgb multiplier from the first image (or any), by -v verbose and read/save the shell output value and set it as variable it then uses for all further conversion.

@all again
further the White Balance Presets (multipliers) are taken from 5D III. Not sure how much difference there is to other camera models.

I'm as well not entirely sure those WB Presets are really correct - so please test them and report back here.
#21
Quote from: AnotherDave on June 19, 2013, 03:40:23 PM
Is it possible to have this JUST convert to ProRes?  Any chance we could select options for the ProRes output?  It'd be great to get a ProRes 422 HQ option.

Just convert to prores - i've tried this several ways with no luck. looks like the raw2dng is not able to be piped in a way we can use the output without it being written to disk... will do some more testing, cause this feature would be great!

EDIT: more options will come, most likely 422/4444, quality (Proxy, LQ, STD, HQ).

#22
Quote from: noix222 on June 18, 2013, 04:58:43 AM
that's awesome thanks!!! its possible to batch convert multiple .RAW files with raw2dng? I went through a lot of time going one by one :P

just drag 'n drop all files on it, or folder containing them.

Quote from: budafilms on June 18, 2013, 07:55:14 AM
Hi Guys, what kind of Pro Res is the file created by RAW2DNG: 422, 4444, LT? Because in Quicktime information only said the creator´s name. Thanks!

currently it's 422 HQ, but 4444 is possible and will be enabled.
#23
Quote from: noix222 on June 17, 2013, 10:59:52 PM
just converted some files with 0.12 to me its worked pretty good... i still prefer to proRes4444 with AE. It would be amazing if we could batch convert with raw2dng and have the option to create just DNG's or DNG's and proRes... anyway its killing it. thanks guys!

"-pix_fmt yuv444p10″ specifies that you want to use the ProRes 4444 codec specifically

we can do that. ;-)

so this would be prores 4444 12bit.
(until now i had some confusion with those pixel formats)

the option to make dng and/or video will come soon.
#24
Quote from: Jason Montalvo on June 17, 2013, 04:23:39 PM
@Bashi

I just tried it again and now it seems to have converted the entire clip to a prores file. I'll try more and let you know if I discover anything.

it's bashi ;-) Good to hear, and please let us know of any issues.

@Doyle4: Thanks for the info.

#25
Quote from: Jason Montalvo on June 17, 2013, 01:20:50 PM
Hello and thank you for the new version of raw2dng. Just wanted to report that when the app is generating the prores file it doesn't seem to be able to make a file greater than 645 frames. Any else experienced this ?

Thank You Again !!

thanks for report. not good ;-) will look into it.
If you click in raw2dng.app on the Details button left, after it failed, can you copy the last part of the text output bellow to here (or pasteall.org)?