so-rose
/
convmlv
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 3 Wiki Activity

Some good fundamental fixes & clarifications. v2.0.2

master v2.0.2
Sofus Albert Høgsbro Rose 2017-12-03 17:02:41 -05:00
parent 1f6f5ef572
commit 04c480a8fd
Signed by: so-rose
GPG Key ID: 3D01BE95F3EFFEB9
16 changed files with 1833524 additions and 1832751 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
CHANGELOG
View File

@ -1,5 +1,21 @@
[code]
[b]v2.0.2[/b]: Some fundamental & bug fixes, as well as now being tested to work with new compressed output.
[size=8pt]*Fixed some mlv_dump versions wouldn't detect # of frames.[/size]
[size=8pt]*Added set +f to ensure globbing is always enabled. Added a commented set -e to kill on error, which I intend to activate for 2.1.0.[/size]
[size=8pt]*Removed all for-loop globbing and replaced with 'find' subcommands. Should remove a class of 'set +f'-related bugs.[/size]
[size=8pt]*Added --relaxed to every mlv_dump invocation, so it won't freak out and develop nothing at the slightest touch of corruption.[/size]
[size=8pt]*Updated help page & PDF for clarity.[/size]
[size=8pt]*Fixed the LUTs - they were processing a too large (extended) range, at 0 benefit to color fidelity and to the detriment of output quality.[/size]
[size=8pt]*Clarified that convmlv's (really, dcraw's) XYZ output is a D65 space, not D50 as it's specced to.[/size]
[size=8pt]*We now depend specifically on @bouncyball's mlv_dump, as that's the only one I can guarantee works with compressed footage.[/size]
[size=8pt]*Get the required mlv_dump here: https://www.magiclantern.fm/forum/index.php?topic=18975.0 .[/size]
[b]v2.0.1[/b]: I'm back! Did some quick fixes. Also, there is now a bundled tarball available - no need to mess around with manual dependencies yourself anymore.
[size=8pt]*Updated PDF with all new features. Nothing is unexplained, now![/size]
[size=8pt]*Added some Mac compatibility.[/size]
[size=8pt]*DNG sequences now use symlinks instead of copying.[/size]
[size=8pt]*Fixed DNG sequence bug.[/size]
[b]v2.0.0[/b]: I think convmlv is the stablest it's ever been! Though I'm sure there's plenty more bugs to discover :).
[size=8pt]*Color Management: Real, 3D LUT-based gamma/gamut choices! See -g/-G. There is now minimal quality loss from sensor to image. Adds a dependency: color-core. [/size]

2
DEPENDENCIES
View File

@ -18,5 +18,5 @@ Binary Source Code:
mlv2badpixels.sh: http://www.magiclantern.fm/forum/index.php?topic=16054
raw2dng: http://www.magiclantern.fm/forum/index.php?topic=5404.0
mlv_dump: http://www.magiclantern.fm/forum/index.php?topic=7122.0
mlv_dump: http://www.magiclantern.fm/forum/index.php?topic=7122.0 & https://www.magiclantern.fm/forum/index.php?topic=18975.0
cr2hdr: http://www.magiclantern.fm/forum/index.php?topic=7139.0

674
LICENCE_BINARIES 100644
View File

@ -0,0 +1,674 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<https://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<https://www.gnu.org/licenses/why-not-lgpl.html>.

0
licence → LICENCE_CONVMLV
View File

524048
color-core/lin_xyz--lin_argb.cube
View File

File diff suppressed because it is too large Load Diff

523056
color-core/lin_xyz--lin_rec709.cube
View File

File diff suppressed because it is too large Load Diff

523056
color-core/lin_xyz--lin_srgb.cube
View File

File diff suppressed because it is too large Load Diff

524288
color-core/lin_xyz--lin_xyz.cube
View File

File diff suppressed because it is too large Load Diff

523986
color-core/lin_xyz--rec709_rec709.cube
View File

File diff suppressed because it is too large Load Diff

523034
color-core/lin_xyz--srgb_srgb.cube
View File

File diff suppressed because it is too large Load Diff

523732
color-core/lin_xyz--y2*2_argb.cube
View File

File diff suppressed because it is too large Load Diff

173
convmlv.sh
View File

@ -1,31 +1,38 @@
#!/bin/bash
#TODO:
#PLANNING:
# Except for openlut integration, CM fixes, and the last throes of Mac compatibility, I consider convmlv feature-complete. As in, only bug fixes and error checking.
# New developments, like special ffmpeg filters, or new techniques from the ML world, may change that. But that's nothing compared to the 2400 lines this pushes at the moment!
# Any further effort is better focused on compatibility, bug fixes, error checking, more bug fixes, and finally a GUI app described in FUTURE.
# Constant bug fixes, compatibility, error checking. Pushing thousands of lines of only-decent bash isn't very stable.
# All releases must be documented in the PDF. Major releases should have a video.
# convmlv 2.X has some features left for itself.
#~ TOP PRIORITY
#~ --> Fix Color Management; -o 5 is broken. Use -o 0, supplemented by current paradigm of Rec709 -> Whatever LUTs, instead of XYZ -> Whatever LUTs.
#~ --> Fix Color Management pipeline, with the help of OCIO.
#~ * New pipeline: RAW --(Demo/WB)--> Cam Space @ WB --(ICC)--> CIE XYZ --(Color)--> Final Space ( --(Filter)--> Final Look --(Encode)--> Output)
#~ * The Demo/WB application is mlv_dump/mlvfs, maybe cr2hdr, then dcraw.
#~ * The ICC application is convert (ImageMagick).
#~ * The Color application is OpenImageIO.
#~ * -I: Specify a number to assume the Camera's Space, or (better) the path to an ICC profile profiling the camera's response.
#~ * -G: Specify the Final Space (as a string matching the OCIO name).
#~ * -g: Force the Final Space into linearity (0 means use the normal Final Space, 1 means force linear).
#~ --> Move MLV - Specify --move-mlv to move the MLV file into "mlv_<TRUNC_ARG>", for organizational reasons.
#~ --> Store Development Config - By default, we should store a config file "<TRUNC_ARG>.conf" containing all the settings needed to redevelop the same way from the same file.
#~ --> MLVFS backend - run the mlvfs command, passing whatever options it supports, then rewrite ARG. Give an option to choose mlv_dump or mlvfs, and an option for a custom path to mlvfs.
#~ *Consider using dcraw for darkframing, through the -K option. Requires a develop from MLV, then a convert to raw PGM, first.
#~ --> Darkframe library - place in $HOME/.local/convmlv, perhaps.
#~ * Give the -k option some more power when using MLVFS: Link MLVFS' instant DNGs into dng_<TRUNC_ARG>.
#~ * If -k is specified, and --move-mlv is not specified, copy the MLV into mlv_<TRUNC_ARG>.
#~ * 'convmlv -U': Run in the folder of the <TRUNC_ARG> mounting DNGs, at dng_<TRUNC_ARG> to unmount the DNGs & delete the links.
#~ * 'convmlv -U': Run in the folder of the <TRUNC_ARG> not mounting DNGs, to remount at dng_<TRUNC_ARG>, relying on "<TRUNC_ARG>.conf" to reproduce settings.
#~ * Why copy the MLV? Wanting DNG access means keeping the raw footage around in some way. If that's not going to be the DNGs, it has to be the MLV.
#~ HIGH PRIORITY
#~ --> Retest Darkframe subtraction with preaveraged/naked darkframe MLVs.
#~ --> Integrate openlut for 1D LUTs. 3D LUTs would only be used for gamut transforms, not gamut/gamma.
#~ --> More error checking.
#~ --> Test Mac compatibility with a *working* (with 10.7) mlv_dump...
#~ --> Documentation: PDF and Videos.
#~ --> Anamorphic Resizing (just add '-resize (100 * resize_fac)%x100%' to any 'convert', where resize_fac is 1.33, 1.5, or 2.0).
#~ --> Cut output Audio based on start/end frame.
#~ --> CR2 Support
#~ MEDIUM PRIORITY
#~ --> Integrate openlut for gamut ops. Matrices would replace standard 3D LUTs altogether, and openlut would handle 3D LUTs.
#~ LOW
#~ --> Stats for .RAW files.
#~ --> Move helper scripts/binaries to "binaries".
#~ --> Calibration frame library, located in $HOME/convmlv/cali_lib. See Issue #12.
#~ --> Preview Mode - live-update a preview window.
#~ FUTURE
@ -60,11 +67,11 @@
#~ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
#~ SOFTWARE.
## Ensure globbing is enabled.
set +f
set +f ## Ensure globbing is enabled.
#~ set -e ## Stop script if something dies.
#BASIC VARS
VERSION="2.0.1" #Version string.
VERSION="2.0.2" #Version string.
INPUT_ARGS=$(echo "$@") #The original input argument string.
if [[ $OSTYPE == "linux-gnu" ]]; then
@ -257,32 +264,47 @@ Usage:
$(head "INFO:")
A program allowing you to develop ML files into workable formats. Many useful options are exposed.
--> Defaults: Compressed 16-bit Linear EXR. 10-bit Prores4444 MOV.
--> Color Defaults: Linear (1.0) Gamma on sRGB Gamut, using Camera White Balance.
--> $(cVal Defaults): Compressed 16-bit Linear EXR. 10-bit Prores4444 MOV.
--> $(cVal "Color Defaults"): Linear (1.0) Gamma on sRGB Gamut, using Camera White Balance.
--> Acceptable Inputs: MLV, RAW (requires raw2dng), Folder containing DNGs.
--> Option Input: From command line or config file (specify with -C).
--> $(cVal "Acceptable Inputs"): MLV (10/12/14 bit, compressed or not), RAW (requires raw2dng), Folder containing DNGs.
--> $(cVal "Option Input"): From command line or config file (specify with -C).
--> Forum Post: http://www.magiclantern.fm/forum/index.php?topic=16799.
--> A note: BE CAREFUL WITH OPTIONS. Wrong values will give very strange errors. Read this page well!!
--> $(cVal "Forum Post"): http://www.magiclantern.fm/forum/index.php?topic=16799 .
--> A note: $(iVal "BE CAREFUL WITH OPTIONS"). Wrong values can give $(iVal "very strange errors"). Read this page well!!
It's as simple or complex as you need it to be: 'convmlv -m <mlvfile>.mlv' is enough for good-looking output!
convmlv is as simple or complex as you need it to be: 'convmlv -m <mlvfile>.mlv' is enough for good-looking output!
Thank you to the entire Magic Lantern community! This tool merely strings together their tools, without which,
convmlv would have been entirely impossible.
$(echo -e "$(head VERSION): ${VERSION}")
$(head "MANUAL DEPENDENCIES:")
Place these in RES_PATH (see OPTIONS, BASIC). Keep in mind you also need dist. and pip packages.
Place all of these in RES_PATH (see OPTIONS, BASIC). Keep in mind that you will also need dist. and pip packages.
--> See 'Dist Deps' and 'Python Deps'
-- mlv_dump: Required binary. http://www.magiclantern.fm/forum/index.php?topic=7122.0
-- color-core: Required folder of LUTs. See convmlv repository.
-- sRange.py: Required script. See convmlv repository.
-- $(cVal "mlv_dump (@bouncyball's)"): Required; binary. $(iVal "YOU NEED THIS SPECIFIC VERSION.").
--> Only download @bouncyball's version: https://www.magiclantern.fm/forum/index.php?topic=18975.0 .
--> $(iVal "IF YOU DO NOT DOWNLOAD THIS SPECIFIC VERSION, YOU MAY BE UNABLE TO DEVELOP COMPRESSED MLVs!")
-- $(cVal color-core): Required; folder of LUTs.
--> See convmlv repository.
-- $(cVal sRange.py): Required; script.
--> See convmlv repository.
-- raw2dng: For DNG extraction from RAW. http://www.magiclantern.fm/forum/index.php?topic=5404.0
-- mlv2badpixels.sh: For bad pixel removal. https://bitbucket.org/daniel_fort/ml-focus-pixels/src
-- cr2hdr: For Dual ISO Development. Two links: http://www.magiclantern.fm/forum/index.php?topic=16799.0
-- balance.py: For Auto White Balance. See convmlv repository.
-- color-ext: Extra LUTs, providing more color resources. See convmlv repository.
-- $(cVal raw2dng): Optional; for DNG extraction from RAW.
--> Original forum post w/source code: http://www.magiclantern.fm/forum/index.php?topic=5404.0 .
--> Linux users can download from: http://www.magiclantern.fm/forum/index.php?topic=9335.0 .
-- $(cVal mlv2badpixels.sh): Optional; for bad pixel removal. Thanks to @dfort!
--> Download from the scripts_archive folder at this link: https://bitbucket.org/daniel_fort/ml-focus-pixels/src
-- $(cVal cr2hdr): Optional; for Dual ISO Development.
--> Original forum post w/source code: http://www.magiclantern.fm/forum/index.php?topic=7139.0 .
--> Linux users can download from: http://www.magiclantern.fm/forum/index.php?topic=9335.0 .
--> Mac users can find the Mac binary in the latest zip: https://bitbucket.org/kichetof/lr_cr2hdr/downloads/ .
-- $(cVal balance.py): Optional; for Auto White Balance.
--> See convmlv repository.
-- $(cVal color-ext): Optional; extra LUTs, providing more color management resources.
--> See convmlv repository.
$(head "OPTIONS, BASIC:")
-v, --version $(bVal version) - Print out version string.
@ -291,19 +313,19 @@ $(head "OPTIONS, BASIC:")
-C, --config $(bVal config) - Designates config file to use.
-o, --outdir <path> $(cVal OUTDIR) - The path in which files will be placed.
-P, --res-path <path> $(iVal RES_PATH) - The path in which all manual dependencies are looked for.
--> Default: Current Directory.
-P, --res-path <path> $(iVal RES_PATH) - The path in which all Manual Dependencies are looked for.
--> Default: Current Directory (.) .
--dcraw <path> $(cVal DCRAW) - The path to dcraw.
--mlv-dump <path> $(cVal MLV_DUMP) - The path to mlv_dump.
--raw-dump <path> $(cVal RAW_DUMP) - The path to raw2dng.
--badpixels <path> $(cVal MLV_BP) - The path to mlv2badpixels.sh (by dfort).
--badpixels <path> $(cVal MLV_BP) - The path to mlv2badpixels.sh .
--cr-hdr <path> $(cVal CR_HDR) - The path to cr2hdr.
--srange <path> $(cVal SRANGE) - The path to sRange.py.
--balance <path> $(cVal BAL) - The path to balance.py.
--python <path> $(cVal PYTHON) - The path or command used to invoke Python 3. Default is python3 on Linux, python on Mac.
-T, --threads [int] $(cVal THREADS) - Override amount of utilized process threads. Default is MAX - 1.
-T, --threads [int] $(cVal THREADS) - Override amount of utilized process threads. Default is ALL - 1.
$(head "OPTIONS, OUTPUT:")
@ -318,7 +340,7 @@ $(head "OPTIONS, OUTPUT:")
--> 0: No proxies (Default). 1: H.264 proxy. 2: JPG proxy sequence. 3: Both.
--> JPG proxy will always be in sRGB Gamma/sRGB Gamut. H.264 proxy is color managed.
--> JPG proxy *won't* be developed w/o IMAGE. H.264 proxy *will* be developed no matter what, if specified here.
--> JPG proxy *won't* ever be developed w/o IMAGE. H.264 proxy *will*, if specified, be developed no matter what.
--> Why? JPG is for potential use in editing. H.264 is for a quick visual preview of convmlv's output.
-s [0%:100%] $(cVal PROXY_SCALE) - the size, in %, of the proxy output.
@ -330,11 +352,11 @@ $(head "OPTIONS, OUTPUT:")
-r <start>-<end> $(cVal FRAME_RANGE) - Specify to process an integer frame range.
--> You may use the characters 's' and 'e', such that s = start frame, e = end frame.
--> Indexed from 0 to (# of frames - 1). Develops from 1 to ($ of frames)
--> A single number may be writted to develop that single frame.
--> $(cVal "If a single # is written"), without a -, that frame alone will be developed.
--> DO NOT try to reuse DNGs while developing a larger frame range.
--uncompress $(cVal UNCOMP) - Turns off lossless image compression. Otherwise:
--uncompress $(cVal UNCOMP) - Turns off lossless image compression. Otherwise, this compression is used:
--> TIFF: ZIP, EXR: PIZ, PNG: lvl 0, DPX: RLE.
@ -345,12 +367,13 @@ $(head "OPTIONS, RAW DEVELOPMENT:")
-f $(cVal FOUR_COLOR) - Interpolate as RGBG. Fixes weirdness with VNG/AHD, at the cost of sharpness.
-H [0:9] $(cVal HIGHLIGHT_MODE) - Highlight management options.
--> 0: White, clipped highlights. 1: Unclipped but colored highlights. 2: The defail of 1, but adjusted to grey.
--> 0: White, clipped highlights. 1: Unclipped but colored highlights. 2: The detail of 1, but adjusted to grey.
--> 3-9: Highlight reconstruction. Can cause flickering. Start at 5, then adjust to color (down) or to white (up).
--> Option #2 is mostly the best - the desaturation of highlights is very filmic, and preserves the most detail.
-c [0:3] $(cVal CHROMA_SMOOTH) - Apply shadow/highlight chroma smoothing to the footage.
--> 0: None (default). 1: 2x2. 2: 3x3. 3: 5x5.
--> MLV input Only.
--> MLV Input Only. Won't trigger for other input types.
-n [int] $(cVal WAVE_NOISE) - Apply wavelet denoising.
--> Default: None. Subtle: 25. Medium: 50. Strong: 125.
@ -359,7 +382,7 @@ $(head "OPTIONS, RAW DEVELOPMENT:")
--> A: 0 to 0.3. B: 0 to 5. A reacts to abrupt noise (splotches), B reacts to noise over time (fast motion causes artifacts).
--> Subtle: 0.03-0.04. High: 0.15-0.04. High, Predictable Motion: 0.15-0.07
-Q [i-i:i-i] $(cVal HQ_NOISE) - Apply 3D denoising filter.
-Q [i-i:i-i] $(cVal HQ_NOISE) - Apply Handbrake's 3D denoising filter.
--> In depth explanation: https://mattgadient.com/2013/06/29/in-depth-look-at-de-noising-in-handbrake-with-imagevideo-examples/ .
--> Spacial/Temporal (S/T). S will soften/blur/smooth, T will remove noise without doing that but may create artifacts.
--> Luma/Chroma (L/C). L is the detail, C is the color. Each one's denoising may be manipulated Spacially or Temporally.
@ -373,9 +396,9 @@ $(head "OPTIONS, RAW DEVELOPMENT:")
--> See https://ffmpeg.org/ffmpeg-filters.html#removegrain for list of modes.
--> Option Value: <mode1>-<mode2>-<mode3>-<mode4>
--> I truly cannot tell you what values will be helpful to you; there are too many... Look at the link!
--> I truly cannot tell you what values will be helpful to you, as there are too many... Look at the link!
--shallow $(cVal SHALLOW) - Output smaller, 8-bit files.
--shallow $(cVal SHALLOW) - Output smaller 8-bit files.
--> Read why this is a bad idea: http://www.cambridgeincolour.com/tutorials/bit-depth.htm
@ -387,12 +410,12 @@ $(head "OPTIONS, COLOR:")
--> "Standard" grades to the gamut specification, and to 2.2 if that's not given.
-G [0:6] $(cVal GAMUT) - Output gamut. The range of colors that can exist in the output.
--> 0: sRGB (Default). 1: Adobe RGB. 2: Rec.709. 3: XYZ (Always Linear Gamma).
--> Requires color-ext: 4: Rec2020 5: DCI-P3 6: Sony S-Gamut3.cine
--> 0: sRGB (Default; D65). 1: Adobe RGB (D65). 2: Rec.709 (D65). 3: XYZ (Always Linear; D65).
--> Requires color-ext: 4: Rec2020 (D65) 5: DCI-P3 (D65) 6: Sony S-Gamut3.cine (D65)
-w [0:2] $(cVal WHITE) - This is a modal white balance setting.
--> 0: Auto WB (requires balance.py). 1: Camera WB (default). 2: No Change.
--> AWB uses the Grey's World algorithm.
--> 0: Auto WB (requires balance.py). 1: Camera WB (default). 2: No WB Scaling of RAW output.
--> AWB uses the Grey's World algorithm. Other algorithms are not currently available.
-A [i:i:i:i] $(cVal SHARP) - Lets you sharpen, or blur, your footage.
--> BE CAREFUL. Wrong values will give you strange errors.
@ -406,28 +429,32 @@ $(head "OPTIONS, COLOR:")
-l <path> $(cVal LUT) - Specify a LUT to apply after Color Management.
--> Supports cube, 3dl, dat, m3d.
--> Specify -l multiple times, to apply multiple LUTs in sequence.
--> LUTs bigger than x64 or smaller than x17 are not supported, and won't apply.
-S [int] $(cVal SATPOINT) - Specify the 14-bit uint saturation point of your camera. You don't usually need to.
--> Worth setting globally, as it's a per-camera setting. Must be correct for highlight reconstruction/unclipped highlights.
--> Lower from 15000 if -H1 yields purple highlights, until they turn white.
-S [int] $(cVal SATPOINT) - Specify the integer saturation point of your camera. Adjust if you're getting purple highlights.
--> It's worth setting in a config, as it's a per-camera setting. Must be correct for highlight reconstruction/unclipped highlights.
--> How To Use: Start at & lower from a value of 15000 if "-H 1" yields purple highlights, until the highlights turn white.
--> This setting is sometimes called "Raw White Point".
--> You can determine the optimal value using the max pixel value of 'dcraw -D -j -4 -T'.
--white-speed [int] $(cVal WHITE_SPD) - Manually specify samples used to calculate AWB.
--white-speed [int] $(cVal WHITE_SPD) - Manually specify the # of samples used to calculate AWB.
--allow-white-clip $(cVal WHITE_CLIP) - Let the White Balance multipliers clip.
--allow-white-clip $(cVal WHITE_CLIP) - Let the White Balance multipliers clip. Usually no effect.
$(head "OPTIONS, FEATURES:")
-D $(cVal DESHAKE) - Auto-stabilize the video using ffmpeg's "deshake" module.
--> You may wish to crop/scale the output later, to avoid edge artifacts.
-u $(cVal DUAL_ISO) - Process as dual ISO.
-u $(cVal DUAL_ISO) - Process the footage as Dual ISO.
--> Requires cr2hdr.
--> Doesn't work for alternating frame HDR Video, where every other frame has a different ISO.
-b $(cVal BADPIXELS) - Fix focus pixels issue using dfort's script.
--> Requires mlv2badpixels.sh.
-a <path> $(cVal BADPIXEL_PATH) - Use your own .badpixels file. Does NOT require mlv2badpixels.sh
--> Why? Pixels die on your camera, and show up in footage. This lets you interpolate around these pixels.
--> How to: http://www.dl-c.com/board/viewtopic.php?f=4&t=686
-F <path> $(cVal DARKFRAME) - This is the path to a "dark frame MLV"; effective for noise reduction.
@ -446,16 +473,17 @@ $(head "OPTIONS, INFO:")
-K [0:3] $(bVal "Dist Deps") - Output package dependecies, for use with common package managers.
--> 0: Debian, 1: Ubuntu, 2: Fedora, 3: Homebrew (Mac)
--> Deps Install (Debian): sudo apt-get install \$(./convmlv.sh -K 0)
--> Deps Install (Ubuntu): sudo apt-get install \$(./convmlv.sh -K 1)
--> Deps Install (Fedora): sudo yum install \$(./convmlv.sh -K 2)
--> Deps Install (Homebrew Mac): brew install \$(./convmlv.sh -K 3)
--> Install Sys Dependencies (Debian): sudo apt-get install \$(./convmlv.sh -K 0)
--> Install Sys Dependencies (Ubuntu): sudo apt-get install \$(./convmlv.sh -K 1)
--> Install Sys Dependencies (Fedora): sudo yum install \$(./convmlv.sh -K 2)
--> Install Sys Dependencies (Homebrew Mac): brew install \$(./convmlv.sh -K 3)
-Y $(bVal "Python Deps") - Lists Python dependencies. Works directly with pip.
-->Install (Cross-Platform): sudo python3 -m pip install $ (./convmlv -Y)
--> Install Python Dependencies (Cross-Platform): sudo python3 -m pip install $ (./convmlv -Y)
--> It may complain about numpy not being found. To fix, just run this first: sudo python3 -m pip install numpy .
-M $(bVal "Manual Deps") - Lists manual dependencies, which must be downloaded by hand.
--> Manually place all in RES_PATH. See http://www.magiclantern.fm/forum/index.php?topic=16799.0 .
--> Manually place all in RES_PATH. See Manual Dependencies above.
$(head "COLOR MANAGEMENT:")
@ -1484,7 +1512,8 @@ mlvSet() {
FPS=`echo "$camDump" | grep FPS | awk 'FNR == 1 {print $3}'`
CAM_NAME=`echo "$camDump" | grep 'Camera Name' | cut -d "'" -f 2`
FRAMES=`echo "$camDump" | awk '/Processed/ { print $2; }'` #Use actual processed frames as opposed to what the sometimes incorrect metadata thinks.
#~ FRAMES=`echo "$camDump" | awk '/Processed/ { print $2; }'` #Use actual processed frames as opposed to what the sometimes incorrect metadata thinks.
FRAMES=`echo "$camDump" | grep 'Frames Video' | sed 's/[[:alpha:] ]*: //'` #Some mlv_dumps don't show "Processed". In which case, yay metadata!
RES_IN=`echo "$camDump" | grep "Res" | sed 's/[[:alpha:] ]*: //'`
ISO=`echo "$camDump" | grep 'ISO' | sed 's/[[:alpha:] ]*: //' | cut -d$'\n' -f2`
APERTURE=`echo "$camDump" | grep 'Aperture' | sed 's/[[:alpha:] ]*: //' | cut -d$'\n' -f1`
@ -1513,7 +1542,7 @@ dngSet() { #Set as many options as the RAW spec will allow. Grey out the rest.
if [[ -z $dngLoc ]]; then dngLoc="${ARG}"; fi
for dng in $dngLoc/*.dng; do
for dng in $(find $dngLoc -maxdepth 1 -name "*.dng" -print0 | sort -z | xargs -r0 -I {} echo {}); do
dataDNG="$(pwd)/.datadng.dng"
cp $dng $dataDNG
break
@ -1792,7 +1821,7 @@ for ARG in "${FILE_ARGS_ITER[@]}"; do #Go through FILE_ARGS_ITER array, copied f
setRange
i=1
for dng in $ARG/*.dng; do
for dng in $(find $ARG -maxdepth 1 -name "*.dng" -print0 | sort -z | xargs -r0 -I {} echo {}); do
ln -s $dng $(printf "${TMP}/${TRUNC_ARG}_%06d.dng" $i) #Since we're not touching the DNGs, we can link them from wherever to TMP!!! :) Super duper fast.
let i++
if [[ i -gt $FRAME_END ]]; then break; fi
@ -1886,7 +1915,9 @@ for ARG in "${FILE_ARGS_ITER[@]}"; do #Go through FILE_ARGS_ITER array, copied f
start=$(echo "$range" | cut -d'-' -f1)
end=$(echo "$range" | cut -d'-' -f2) #Get start and end frames from the frame range
$2 $3 $4 -o "${tmpOut}/${9}_" -f ${range} $6 --dng --batch | { #mlv_dump command. Uses frame range.
# -c -c (-p in @bouncyball's version) passes the DNG data through pretty brutally, but makes compression work (dcraw is OK with LZMA/LJ92).
# Perhaps make --relaxed a user trigger? After all, it might be better to be strict about things.
$2 $3 $4 -o "${tmpOut}/${9}_" -f ${range} $6 --dng --batch --relaxed | { #--relaxed makes it not freak out and develop nothing when it hits a corrupt block.
lastCur=0
while IFS= read -r line; do
output=$(echo $line | grep -E 'V.*A' | cut -d':' -f2 | cut -d$' ' -f1) #Hacked my way to the important bit.
@ -1919,7 +1950,7 @@ for ARG in "${FILE_ARGS_ITER[@]}"; do #Go through FILE_ARGS_ITER array, copied f
count=$FRAME_START
for range in "${fileRanges[@]}"; do #Go through the subfolders sequentially
tmpOut=${TMP}/${range} #Use temporary folder. It will be named the same as the frame range.
for dng in ${tmpOut}/*.dng; do
for dng in $(find ${tmpOut} -maxdepth 1 -name "*.dng" -print0 | sort -z | xargs -r0 -I {} echo {}); do
if [ $count -gt $FRAME_END ]; then echo "ERROR! Count greater than end!"; fi
mv $dng $(printf "${TMP}/${TRUNC_ARG}_%06d.dng" $count) #Move dngs out sequentially, numbering them properly.
let count++
@ -2067,7 +2098,7 @@ for ARG in "${FILE_ARGS_ITER[@]}"; do #Go through FILE_ARGS_ITER array, copied f
#Develop every nth file for averaging.
i=0
t=0
for file in $TMP/*.dng; do
for file in $(find $TMP -maxdepth 1 -name "*.dng" -print0 | sort -z | xargs -r0 -I {} echo {}); do
if [ `echo "(${i}+1) % ${n}" | bc` -eq 0 ]; then
$DCRAW -q 0 $BADPIXELS -r 1 1 1 1 -g $GAMMA -k $BLACK_LEVEL $SATPOINT -o 0 -T "${file}"
name=$(basename "$file")
@ -2086,7 +2117,7 @@ for ARG in "${FILE_ARGS_ITER[@]}"; do #Go through FILE_ARGS_ITER array, copied f
elif [ $CAMERA_WB == true ]; then
echo -e "\033[1m${TRUNC_ARG}:\033[0m Retrieving Camera White Balance..."
for file in $TMP/*.dng; do
for file in $(find $TMP -maxdepth 1 -name "*.dng" -print0 | sort -z | xargs -r0 -I {} echo {}); do
#dcraw a single file verbosely, to get the camera multiplier with awk.
BALANCE=`$DCRAW -T -w -v -c ${file} 2>&1 | awk '/multipliers/ { print $2, $3, $4 }'`
break

105
docs/MANPAGE
View File

@ -6,29 +6,44 @@ INFO:
--> Defaults: Compressed 16-bit Linear EXR. 10-bit Prores4444 MOV.
--> Color Defaults: Linear (1.0) Gamma on sRGB Gamut, using Camera White Balance.
--> Acceptable Inputs: MLV, RAW (requires raw2dng), Folder containing DNGs.
--> Acceptable Inputs: MLV (10/12/14 bit, compressed or not), RAW (requires raw2dng), Folder containing DNGs.
--> Option Input: From command line or config file (specify with -C).
--> Forum Post: http://www.magiclantern.fm/forum/index.php?topic=16799.
--> A note: BE CAREFUL WITH OPTIONS. Wrong values will give very strange errors. Read this page well!!
--> Forum Post: http://www.magiclantern.fm/forum/index.php?topic=16799 .
--> A note: BE CAREFUL WITH OPTIONS. Wrong values can give very strange errors. Read this page well!!
It's as simple or complex as you need it to be: 'convmlv -m <mlvfile>.mlv' is enough for good-looking output!
convmlv is as simple or complex as you need it to be: 'convmlv -m <mlvfile>.mlv' is enough for good-looking output!
VERSION: 2.0.1
Thank you to the entire Magic Lantern community! This tool merely strings together their tools, without which,
convmlv would have been entirely impossible.
VERSION: 2.0.2
MANUAL DEPENDENCIES:
Place these in RES_PATH (see OPTIONS, BASIC). Keep in mind you also need dist. and pip packages.
Place all of these in RES_PATH (see OPTIONS, BASIC). Keep in mind that you will also need dist. and pip packages.
--> See 'Dist Deps' and 'Python Deps'
-- mlv_dump: Required binary. http://www.magiclantern.fm/forum/index.php?topic=7122.0
-- color-core: Required folder of LUTs. See convmlv repository.
-- sRange.py: Required script. See convmlv repository.
-- mlv_dump (@bouncyball's): Required; binary. YOU NEED THIS SPECIFIC VERSION..
--> Only download @bouncyball's version: https://www.magiclantern.fm/forum/index.php?topic=18975.0 .
--> IF YOU DO NOT DOWNLOAD THIS SPECIFIC VERSION, YOU MAY BE UNABLE TO DEVELOP COMPRESSED MLVs!
-- color-core: Required; folder of LUTs.
--> See convmlv repository.
-- sRange.py: Required; script.
--> See convmlv repository.
-- raw2dng: For DNG extraction from RAW. http://www.magiclantern.fm/forum/index.php?topic=5404.0
-- mlv2badpixels.sh: For bad pixel removal. https://bitbucket.org/daniel_fort/ml-focus-pixels/src
-- cr2hdr: For Dual ISO Development. Two links: http://www.magiclantern.fm/forum/index.php?topic=16799.0
-- balance.py: For Auto White Balance. See convmlv repository.
-- color-ext: Extra LUTs, providing more color resources. See convmlv repository.
-- raw2dng: Optional; for DNG extraction from RAW.
--> Original forum post w/source code: http://www.magiclantern.fm/forum/index.php?topic=5404.0 .
--> Linux users can download from: http://www.magiclantern.fm/forum/index.php?topic=9335.0 .
-- mlv2badpixels.sh: Optional; for bad pixel removal. Thanks to @dfort!
--> Download from the scripts_archive folder at this link: https://bitbucket.org/daniel_fort/ml-focus-pixels/src
-- cr2hdr: Optional; for Dual ISO Development.
--> Original forum post w/source code: http://www.magiclantern.fm/forum/index.php?topic=7139.0 .
--> Linux users can download from: http://www.magiclantern.fm/forum/index.php?topic=9335.0 .
--> Mac users can find the Mac binary in the latest zip: https://bitbucket.org/kichetof/lr_cr2hdr/downloads/ .
-- balance.py: Optional; for Auto White Balance.
--> See convmlv repository.
-- color-ext: Optional; extra LUTs, providing more color management resources.
--> See convmlv repository.
OPTIONS, BASIC:
-v, --version version - Print out version string.
@ -37,19 +52,19 @@ OPTIONS, BASIC:
-C, --config config - Designates config file to use.
-o, --outdir <path> OUTDIR - The path in which files will be placed.
-P, --res-path <path> RES_PATH - The path in which all manual dependencies are looked for.
--> Default: Current Directory.
-P, --res-path <path> RES_PATH - The path in which all Manual Dependencies are looked for.
--> Default: Current Directory (.) .
--dcraw <path> DCRAW - The path to dcraw.
--mlv-dump <path> MLV_DUMP - The path to mlv_dump.
--raw-dump <path> RAW_DUMP - The path to raw2dng.
--badpixels <path> MLV_BP - The path to mlv2badpixels.sh (by dfort).
--badpixels <path> MLV_BP - The path to mlv2badpixels.sh .
--cr-hdr <path> CR_HDR - The path to cr2hdr.
--srange <path> SRANGE - The path to sRange.py.
--balance <path> BAL - The path to balance.py.
--python <path> PYTHON - The path or command used to invoke Python 3. Default is python3 on Linux, python on Mac.
-T, --threads [int] THREADS - Override amount of utilized process threads. Default is MAX - 1.
-T, --threads [int] THREADS - Override amount of utilized process threads. Default is ALL - 1.
OPTIONS, OUTPUT:
@ -64,7 +79,7 @@ OPTIONS, OUTPUT:
--> 0: No proxies (Default). 1: H.264 proxy. 2: JPG proxy sequence. 3: Both.
--> JPG proxy will always be in sRGB Gamma/sRGB Gamut. H.264 proxy is color managed.
--> JPG proxy *won't* be developed w/o IMAGE. H.264 proxy *will* be developed no matter what, if specified here.
--> JPG proxy *won't* ever be developed w/o IMAGE. H.264 proxy *will*, if specified, be developed no matter what.
--> Why? JPG is for potential use in editing. H.264 is for a quick visual preview of convmlv's output.
-s [0%:100%] PROXY_SCALE - the size, in %, of the proxy output.
@ -76,11 +91,11 @@ OPTIONS, OUTPUT:
-r <start>-<end> FRAME_RANGE - Specify to process an integer frame range.
--> You may use the characters 's' and 'e', such that s = start frame, e = end frame.
--> Indexed from 0 to (# of frames - 1). Develops from 1 to ($ of frames)
--> A single number may be writted to develop that single frame.
--> If a single # is written, without a -, that frame alone will be developed.
--> DO NOT try to reuse DNGs while developing a larger frame range.
--uncompress UNCOMP - Turns off lossless image compression. Otherwise:
--uncompress UNCOMP - Turns off lossless image compression. Otherwise, this compression is used:
--> TIFF: ZIP, EXR: PIZ, PNG: lvl 0, DPX: RLE.
@ -91,12 +106,13 @@ OPTIONS, RAW DEVELOPMENT:
-f FOUR_COLOR - Interpolate as RGBG. Fixes weirdness with VNG/AHD, at the cost of sharpness.
-H [0:9] HIGHLIGHT_MODE - Highlight management options.
--> 0: White, clipped highlights. 1: Unclipped but colored highlights. 2: The defail of 1, but adjusted to grey.
--> 0: White, clipped highlights. 1: Unclipped but colored highlights. 2: The detail of 1, but adjusted to grey.
--> 3-9: Highlight reconstruction. Can cause flickering. Start at 5, then adjust to color (down) or to white (up).
--> Option #2 is mostly the best - the desaturation of highlights is very filmic, and preserves the most detail.
-c [0:3] CHROMA_SMOOTH - Apply shadow/highlight chroma smoothing to the footage.
--> 0: None (default). 1: 2x2. 2: 3x3. 3: 5x5.
--> MLV input Only.
--> MLV Input Only. Won't trigger for other input types.
-n [int] WAVE_NOISE - Apply wavelet denoising.
--> Default: None. Subtle: 25. Medium: 50. Strong: 125.
@ -105,7 +121,7 @@ OPTIONS, RAW DEVELOPMENT:
--> A: 0 to 0.3. B: 0 to 5. A reacts to abrupt noise (splotches), B reacts to noise over time (fast motion causes artifacts).
--> Subtle: 0.03-0.04. High: 0.15-0.04. High, Predictable Motion: 0.15-0.07
-Q [i-i:i-i] HQ_NOISE - Apply 3D denoising filter.
-Q [i-i:i-i] HQ_NOISE - Apply Handbrake's 3D denoising filter.
--> In depth explanation: https://mattgadient.com/2013/06/29/in-depth-look-at-de-noising-in-handbrake-with-imagevideo-examples/ .
--> Spacial/Temporal (S/T). S will soften/blur/smooth, T will remove noise without doing that but may create artifacts.
--> Luma/Chroma (L/C). L is the detail, C is the color. Each one's denoising may be manipulated Spacially or Temporally.
@ -119,9 +135,9 @@ OPTIONS, RAW DEVELOPMENT:
--> See https://ffmpeg.org/ffmpeg-filters.html#removegrain for list of modes.
--> Option Value: <mode1>-<mode2>-<mode3>-<mode4>
--> I truly cannot tell you what values will be helpful to you; there are too many... Look at the link!
--> I truly cannot tell you what values will be helpful to you, as there are too many... Look at the link!
--shallow SHALLOW - Output smaller, 8-bit files.
--shallow SHALLOW - Output smaller 8-bit files.
--> Read why this is a bad idea: http://www.cambridgeincolour.com/tutorials/bit-depth.htm
@ -133,12 +149,12 @@ OPTIONS, COLOR:
--> "Standard" grades to the gamut specification, and to 2.2 if that's not given.
-G [0:6] GAMUT - Output gamut. The range of colors that can exist in the output.
--> 0: sRGB (Default). 1: Adobe RGB. 2: Rec.709. 3: XYZ (Always Linear Gamma).
--> Requires color-ext: 4: Rec2020 5: DCI-P3 6: Sony S-Gamut3.cine
--> 0: sRGB (Default; D65). 1: Adobe RGB (D65). 2: Rec.709 (D65). 3: XYZ (Always Linear; D65).
--> Requires color-ext: 4: Rec2020 (D65) 5: DCI-P3 (D65) 6: Sony S-Gamut3.cine (D65)
-w [0:2] WHITE - This is a modal white balance setting.
--> 0: Auto WB (requires balance.py). 1: Camera WB (default). 2: No Change.
--> AWB uses the Grey's World algorithm.
--> 0: Auto WB (requires balance.py). 1: Camera WB (default). 2: No WB Scaling of RAW output.
--> AWB uses the Grey's World algorithm. Other algorithms are not currently available.
-A [i:i:i:i] SHARP - Lets you sharpen, or blur, your footage.
--> BE CAREFUL. Wrong values will give you strange errors.
@ -152,28 +168,32 @@ OPTIONS, COLOR:
-l <path> LUT - Specify a LUT to apply after Color Management.
--> Supports cube, 3dl, dat, m3d.
--> Specify -l multiple times, to apply multiple LUTs in sequence.
--> LUTs bigger than x64 or smaller than x17 are not supported, and won't apply.
-S [int] SATPOINT - Specify the 14-bit uint saturation point of your camera. You don't usually need to.
--> Worth setting globally, as it's a per-camera setting. Must be correct for highlight reconstruction/unclipped highlights.
--> Lower from 15000 if -H1 yields purple highlights, until they turn white.
-S [int] SATPOINT - Specify the integer saturation point of your camera. Adjust if you're getting purple highlights.
--> It's worth setting in a config, as it's a per-camera setting. Must be correct for highlight reconstruction/unclipped highlights.
--> How To Use: Start at & lower from a value of 15000 if "-H 1" yields purple highlights, until the highlights turn white.
--> This setting is sometimes called "Raw White Point".
--> You can determine the optimal value using the max pixel value of 'dcraw -D -j -4 -T'.
--white-speed [int] WHITE_SPD - Manually specify samples used to calculate AWB.
--white-speed [int] WHITE_SPD - Manually specify the # of samples used to calculate AWB.
--allow-white-clip WHITE_CLIP - Let the White Balance multipliers clip.
--allow-white-clip WHITE_CLIP - Let the White Balance multipliers clip. Usually no effect.
OPTIONS, FEATURES:
-D DESHAKE - Auto-stabilize the video using ffmpeg's "deshake" module.
--> You may wish to crop/scale the output later, to avoid edge artifacts.
-u DUAL_ISO - Process as dual ISO.
-u DUAL_ISO - Process the footage as Dual ISO.
--> Requires cr2hdr.
--> Doesn't work for alternating frame HDR Video, where every other frame has a different ISO.
-b BADPIXELS - Fix focus pixels issue using dfort's script.
--> Requires mlv2badpixels.sh.
-a <path> BADPIXEL_PATH - Use your own .badpixels file. Does NOT require mlv2badpixels.sh
--> Why? Pixels die on your camera, and show up in footage. This lets you interpolate around these pixels.
--> How to: http://www.dl-c.com/board/viewtopic.php?f=4&t=686
-F <path> DARKFRAME - This is the path to a "dark frame MLV"; effective for noise reduction.
@ -192,16 +212,17 @@ OPTIONS, INFO:
-K [0:3] Dist Deps - Output package dependecies, for use with common package managers.
--> 0: Debian, 1: Ubuntu, 2: Fedora, 3: Homebrew (Mac)
--> Deps Install (Debian): sudo apt-get install $(./convmlv.sh -K 0)
--> Deps Install (Ubuntu): sudo apt-get install $(./convmlv.sh -K 1)
--> Deps Install (Fedora): sudo yum install $(./convmlv.sh -K 2)
--> Deps Install (Homebrew Mac): brew install $(./convmlv.sh -K 3)
--> Install Sys Dependencies (Debian): sudo apt-get install $(./convmlv.sh -K 0)
--> Install Sys Dependencies (Ubuntu): sudo apt-get install $(./convmlv.sh -K 1)
--> Install Sys Dependencies (Fedora): sudo yum install $(./convmlv.sh -K 2)
--> Install Sys Dependencies (Homebrew Mac): brew install $(./convmlv.sh -K 3)
-Y Python Deps - Lists Python dependencies. Works directly with pip.
-->Install (Cross-Platform): sudo python3 -m pip install $ (./convmlv -Y)
--> Install Python Dependencies (Cross-Platform): sudo python3 -m pip install $ (./convmlv -Y)
--> It may complain about numpy not being found. To fix, just run this first: sudo python3 -m pip install numpy .
-M Manual Deps - Lists manual dependencies, which must be downloaded by hand.
--> Manually place all in RES_PATH. See http://www.magiclantern.fm/forum/index.php?topic=16799.0 .
--> Manually place all in RES_PATH. See Manual Dependencies above.
COLOR MANAGEMENT:

BIN
docs/docs.pdf
View File

Binary file not shown.

103
docs/docs.tex
View File

@ -13,7 +13,7 @@
}
\author{\textit{by Sofus Rose}}
\title{\textbf{Using convmlv 2.0.1} \\ {\large Developing Magic Lantern footage with ease}}
\title{\textbf{Using convmlv 2.0.2} \\ {\large Developing Magic Lantern footage with glee}}
%^^^ Title \\ Subtitle. Subtitle is \large, as opposed to \huge.{}
\begin{document}
@ -23,25 +23,28 @@
\newpage
\section{Introduction}
Processing the output of Magic Lantern for maximum quality is a technical balancing act, at best. Certain functions approach impossibility,
\textit{especially} on Linux. convmlv aims to make the development of MLV, RAW, and even DNG sequences as easy and as featureful as
possible, with equal amounts of help and technical depth.\\
Processing the output of Magic Lantern for maximum quality is a technical balancing act. \textit{Especially} on Linux, many
neccesary programs simply don't exist for open source development of raw video, never mind MLVs!\\
I've used earlier versions of convmlv in my own short films: \url{https://www.youtube.com/watch?v=a7iSjEfch5s&t=5s} and \url{https://www.youtube.com/watch?v=yi-G7sXHB1M&t=1s}.
So you may judge for yourself, I suppose ;) .
convmlv aims to change that, and to make the development of MLVs, RAWs, and plain DNG sequences as simple and as featureful as
possible in the same program, with equal amounts of help and technical depth.\\
I personally use it! Earlier versions of convmlv feature in my own short films:
\url{https://www.youtube.com/watch?v=a7iSjEfch5s&t=5s} and \url{https://www.youtube.com/watch?v=yi-G7sXHB1M&t=1s}.
\subsection{Important Links}
The Forum Post: \url{http://www.magiclantern.fm/forum/index.php?topic=16799.0}\\
The Git Repository: \url{https://github.com/so-rose/convmlv}\\
This Release: \url{https://github.com/so-rose/convmlv/releases}\\
The Dev Repository: \url{https://git.sofusrose.com/so-rose/convmlv}\\
Releases: \url{https://github.com/so-rose/convmlv/releases}\\
\subsection{What can it do?}
This entire document is dedicated to the answer! In short, it is a program \textbf{allowing you to develop .RAW, .MLV, or sequences of .DNGs
into workable image and video formats}. Many useful options are exposed.\\
into the highest quality image and video formats}. Many useful options are exposed to facilitate that, and a good editing/grading experience afterwards.\\
It can be as simple - 'convmlv -m footage.mlv' is valid - or as complex as you need it to be, for example with automation and color management.
It can be as simple - 'convmlv -m footage.mlv' to develop the MLV to an MOV - or as complex as you need it to be!
\subsection{Terminal: Not So Scary! I swear!}
\subsection{Terminal: Not So Scary! I swear! (A Crash Course)}
I swear, it's actually quite intuitive! Here's a crash course. First, open it up. You'll see a prompt, something like this:
\begin{lstlisting}[language=bash]
@ -54,7 +57,13 @@
ls #List - Press enter!
\end{lstlisting}
Look at all those files! But let's say I wanted to go to Desktop:
Look at all those files! Let's add a couple of "flag" to get a better idea:
\begin{lstlisting}[language=bash]
ls -l #The l flag lists things much nicer.
\end{lstlisting}
But let's say I wanted to go to Desktop:
\begin{lstlisting}[language=bash]
cd Desktop #Change Directory, with one option: Desktop!
@ -78,25 +87,33 @@
\begin{enumerate}
\item Download the latest .tar.gz release from \url{https://github.com/so-rose/convmlv/releases}, and put it in its own folder.
\item Open up a Terminal, and cd to that folder containing only the downloaded .tar.gz file.
\item Extract the release using your favorite utility. In the terminal:
\item Extract the release using your favorite utility. In the terminal you can do:
\begin{lstlisting}[language=bash]
tar -xvzf *.tar.gz
\end{lstlisting}
\item Install all the distribution dependencies. The commands for Ubuntu, Debian, Fedora, and Mac can be found in the DEPENDENCIES file. On Debian:
\item Now, if you're on a Mac (\textbf{ONLY IF YOU'RE ON A MAC}), you need a package manager called "Homebrew". Installation of it is easy;
run the one-line command over at \url{https://brew.sh/}.
\item Install all the distribution dependencies. The commands for Ubuntu, Debian, Fedora, and Mac can be found in the DEPENDENCIES file.
On Debian you can run the following; replace the 0 with a 1 for Ubuntu, 2 for Fedora:
\begin{lstlisting}[language=bash]
sudo apt-get install $(convmlv -K 0) #$Only for Debian.
sudo apt-get install $(convmlv -K 1) #$Only for Ubuntu.
sudo apt-get install $(convmlv -K 2) #$Only for Fedora.
sudo brew install $(convmlv -K 3) #$Only for Mac.
\end{lstlisting}
\item Install Python dependencies. The command is the same everywhere (make sure you're using Python 3.X!)
\begin{lstlisting}[language=bash]
sudo python3 -m pip install numpy #Make sure numpy is installed
sudo python3 -m pip install $(./convmlv -Y) #$Use pip to install things!
\end{lstlisting}
\item You're all set! If you want to use convmlv as a commmand, you can type this:
\item Finally, to be able to use convmlv as a commmand by itself, you can type this:
\begin{lstlisting}[language=bash]
ln -s $(pwd)/convmlv.sh /usr/local/bin/convmlv #$Can call it normally now.
@ -108,44 +125,52 @@
\subsection{Introduction}
convmlv comes in the form of a ``.sh'' script. Installation is a little hairy, but bear with me, and you'll be done in max 10 minutes!\\
convmlv comes in the form of a ``.sh'' script. Installation is a little hairy, but bear with me, and you'll be done soon.\\
Besides the script itself, several \textbf{dependencies} are required. How to best get these varies by system.\\
To begin, download or clone the entire source from \url{https://github.com/so-rose/convmlv}.
To begin, download or clone the source code from \url{https://github.com/so-rose/convmlv}.
\subsection{UNIX}
On UNIX systems, everything is easy. There is certain setup that must be done, however. Open up a terminal, navigate to the folder containing
convmlv and balance.py, and type each line:
\subsection{Linux}
On Linux systems, everything is easy. There is certain setup that must be done, however. Open up a terminal, navigate to the source code (
containing convmlv and balance.py), and type each line:
\begin{lstlisting}[language=bash]
chmod +x convmlv.sh balance.py sRange.py #Let convmlv execute.
chmod +x convmlv.sh balance.py sRange.py #Allow the scripts to execute.
\end{lstlisting}
You can run the script now, but it won't work! This is because you must install the dependencies. First off, these are the package
dependencies, which your system has a unique way of providing. Type the command below, then type '/-K' and Enter to search for '-K'.
Check that you can load the help page with './convmlv.sh -h'.\\
Now, you must install the dependencies. First off, these are the package
dependencies, which your system has a unique way of providing. Type './convmlv.sh -h' to access the help, then type '/-K' and Enter to search for '-K'.
Next to each supported distribution is a command; copy this command with Shift+Ctrl+C !
\begin{lstlisting}[language=bash]
./convmlv.sh -h
./convmlv.sh -h #The help page
\end{lstlisting}
Find and install the corresponding packages on your machine by typing the command you just copied. Note that you must have installed
Homebrew on your Mac for this to work (See Mac instructions below). On Debian this would be:
Homebrew on your Mac for this to work (See Mac instructions below):
\begin{lstlisting}[language=bash]
sudo apt-get install $(./convmlv.sh -K 0) #$Only for debian.
sudo apt-get install $(convmlv -K 0) #$Only for Debian.
sudo apt-get install $(convmlv -K 1) #$Only for Ubuntu.
sudo apt-get install $(convmlv -K 2) #$Only for Fedora.
sudo brew install $(convmlv -K 3) #$Only for Mac.
\end{lstlisting}
Next, you must install the Python dependencies. This is easy, and works the same everywhere:
\begin{lstlisting}[language=bash]
sudo python3 -m pip install $ (./convmlv -Y) #$Python 3 version of pip.
sudo python3 -m pip install numpy #Make sure numpy is installed
sudo python3 -m pip install $(./convmlv -Y) #$Python 3 version of pip.
\end{lstlisting}
Finally, you must install the manual dependencies made by the talented Magic Lantern community. You can list these
by typing './convmlv.sh -M'.\\
'convmlv -h' lists all the URLs that you need.\\
\textbf{How To Do It}: Download each item in the list, making sure you put it in the same folder as convmlv.sh. 'chmod +x' each
file by itself, or just run this after downloading them all:
@ -171,16 +196,16 @@
\subsection{The Basics}
The development of an mlv named "footage.mlv" in the current directory into a ProRes video is very, very simple:
The development of an mlv named 'footage.mlv' in the current directory into a ProRes video is very, very simple:
\begin{lstlisting}[language=bash]
convmlv -m footage.mlv
\end{lstlisting}
A folder named 'raw-conv' will be created, inside of which a folder named 'footage' will be created, inside of which you'll find your
high-quality, ready to edit ProRes video! Plenty more features, however.\\
high-quality, ready to edit ProRes video! Feature-wise, however, this is just the tip of the iceberg.\\
Image sequences, used for highest quality color grading and VFX, can be outputted like so (compressed losslessly):
Image sequences, used for the highest quality color grading and VFX, can be outputted like so (compressed losslessly automatically):
\begin{lstlisting}[language=bash]
convmlv -i footage.mlv
@ -222,16 +247,21 @@
convmlv -i -r 100-500 footage.mlv #From Frame 100 to 500.
\end{lstlisting}
The characters 's' and 'e' can be used instead of numbers. They represent "start frame" and "end frame". If you write
a single number without a -, then it will only develop that frame.\\
The characters 's' and 'e' can be used instead of numbers. They represent "start frame" and "end frame".\\
DO NOT try to reuse DNG sequences using this feature! It will break!
If you just want a fast preview of the work convmlv is doing, you can develop a single frame very quickly:
\begin{lstlisting}[language=bash]
convmlv -i -r 105 footage.mlv #Develop frame 105!
\end{lstlisting}
DO NOT try to reuse DNG sequences when using frame ranges! It will break!
\section{RAW Development}
\subsection{General}
convmlv uses dcraw, a powerful RAW development tool, and as such inherits its features! I'll go through them in detail here:
convmlv relies on dcraw, a powerful RAW development tool, and as such inherits its features! I'll go through them in detail here:
\begin{itemize}
\item Demosaicing, -d: RAW images represent data the sensor spits out. As such, it's neccessary to process
@ -245,7 +275,7 @@
\item Four Color Mode, -r: When the VNG and AHD demosaicing modes get strange, this option tends to fix things.
\item Highlight Reconstruction, -H: Highlights are values too bright for detail. A mode of 2 will attempt to fix them up a bit,
while modes of 3 to 9 tries to regain the detail using varying color tones. A mode of 1 will let colored highlights through; this will
usually look nasty unless you tune the Saturation Point (see below).
usually look nasty unless you tune the Saturation Point (see below). Mode 2 is almost always the best option.
\end{itemize}
\subsection{Noise Reduction}
@ -319,7 +349,8 @@
convmlv -i -l lut1.cube -l lut2.cube footage.mlv #Two LUTs applied.
\end{lstlisting}
If you want to grade to your own gamma/gamut, I suggest using LUTCalc (https://cameramanben.github.io/LUTCalc/) to generate a corresponding LUT.\\
If you want to grade to your own gamma/gamut, I suggest using LUTCalc
(https://cameramanben.github.io/LUTCalc/) to generate a corresponding LUT.\\
Currently lacking is 1D LUT support, and x65 3D LUT support. Once openlut is integrated, these problems will go away.

2
docs/workflow.txt
View File

@ -1,4 +1,4 @@
The convmlv Workflow is a powerful one.
The convmlv workflow is a powerful one.
Shoot Footage -->