Hello everyone, someone could guide me about the workflow with crop_rec under Windows, thank you very much.

Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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 MenuQuote from: g3gg0 on April 30, 2014, 08:31:23 PM
well...
Quote from: g3gg0 on April 30, 2014, 04:03:12 PM
you are sure that this is a .dng generated from raw2dng or mlv_dump?
or was it made with some other tool?
if not -> use raw2dng / mlv_dump
Quote from: g3gg0 on April 30, 2014, 03:11:12 PM
a) never use directories with spaces -> try somewhere else
b) use a obviously wrong value like 1024 to check if it has any effect
Quote from: Audionut on April 30, 2014, 12:08:19 PM
Did you bother to read my post at all?
Quote from: g3gg0 on March 24, 2014, 09:30:46 PM
i added a workaround for that black level issue. (next nightly)
i am not sure why the raw backend has trouble in detecting the correct black level so often now.
did you all use zoomed modes?
a) mlv_rec will by default fix that value to 2048. depending on your camera this may be wrong.
iirc alex told me that there may be some models which have 4096. (maybe i mixed smth up)
for this reason there is a menu option to disable that black-fix if you need it.
b) mlv_dump has an option --black-fix to override black level to 2048. for existing footage just run
'./mlv_dump in.mlv --black-fix -o out.mlv' and your footage in out.mlv will have black level set to 2048.
(for windows users: here is a version with the fix)
the changes will take effect with the next nightly.
Quote from: g3gg0 on March 24, 2014, 05:15:20 PM
these are the files i need to check what the problem is.
will report tonight.
Page created in 0.132 seconds with 13 queries.