Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Digital Cinema Package

That is the formula for converting from linear (scene referred) levels to code values in a Rec709 coded file. It is what you get when choosing Rec709 as the output LUT in Red software. However a 'normal' HD monitor does not follow the the inverse of this function in converting the input signal to output luminance. That is what is not defined.

FilmLight have a preset in their Truelight system called "SonyHD" which approximates the response of a Sony HD monitor set up with a pluge in a dimly lit room. An inverse of this might be a good start point to create a LUT.
 
pavel klepinin said:
i didn't realy understand what are you going to say, but thanx to wolfgang, oct creators and some other good users of this forum, i've managed to transform film into dcp for free. My goal is not to get money from this transformations. I share my experiments and my script for free. Maybe my goal is opposite. Anyone could make this, even if he is from penza :blush5:
Ps your russian is awful. Shame on you if you're a russian-speaking person.
Click to expand...

Был бы я руский, давно помер от алкоголя. Кстати что ты понимаешься в етих дел что бы "поделиться" с друзьями? Ровно ничего - все время спрашиваеш и делаеш ошибки. Оставь професионалы заниматься, а ты занимайся своими делами, а то в етот кризис останешься без работы, а то и похуже. И посмотри на свой лицензионный софтуер, а то придут ребята в черном и всем будет п....ц. Кстати а ты не безпокоишься ребятам, которые занимаются етим делам на комерческой основе? Ты знаеш как руские ребята решают такие дела?
 
Thrane said:
Now I have downloaded ImageMagick, but I'm not good at that kind of programs.
I need and interface... :-(
Click to expand...
Good ! You want all, usefull, easy and for FREE ! But did you wish to offer all what you do for free? If you wish , I'm willing to hire you (for free of cource). REMEMBER !!! There are NO! free lunch ! And repeat that as frequently as you can. So if you are profesional, you will not loose your time with free tools, if you are not profesional (I suppose,if you use RED....) you CAN'T work with OCT and you will try to loose somebody else time. So if you can do yourself DCP - do it. If not - don't loose peoples time and don't ask for free stuff.
 
Sadly, I imagine that many of the people on this thread are not professionals. The definition of a professional
http://education.yahoo.com/reference/dictionary/entry/professional

  1. A person following a profession, especially a learned profession.
  2. One who earns a living in a given or implied occupation: hired a professional to decorate the house.
  3. A skilled practitioner; an expert.
I am not a professional DCP creator but I am a professional film editor. Therefore I come to forums like this to share what I know and to learn from others. I don't know of any professional DCP makers and if I did want just to have a DCP, I would have already called them. Therefore, Sulev, if you feel that your knowledge is worth money, sell it and stop criticizing those that don't have your professional abilities.

Secondly, has anyone been able to compile opencinematools for macintel?

I have just about done the whole workflow on a mac, thanks to the extreme generosity of Chris Perry at http://bitfilms.blogspot.com/
Once I have managed it all, I will publish an idiots guide to making a DCP on a mac.
LONG LIVE FORUM EXCHANGE
 
2Sulio Pulev,
Yeah, I'm russian and every morning I die because of drinking Vodka then I go to the Red Square walk over my bear, then we, me and my bear, go to install pirate soft then come KGB, they kill me again for pirate soft. And then I go to sleep to see my sweet dreams about thoose whom I ruined their lives because of using and promoting open source, not their paid DCP-making software.
You watch too many television, you know nothing about real Russia. At all.

Therefore, Sulev, if you feel that your knowledge is worth money, sell it and stop criticizing those that don't have your professional abilities.
Click to expand...
BTW, I'm far from thinking that Sulio Pulev is a professional. Real professional is not intended to criticize other abilities, people who want to learn something.
All his posts unmask him as a simple troll.
 
Christopher, I have managed to compile all the necessary tools on an intel Mac and create a DCP. Let me know what errors you are getting and I'll do my best to help you.
 
Looks like this. Many thanks

sh-3.2# chmod +x ./build.tcsh
sh-3.2# ./build.tcsh
################### building opencinematools ######################
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libkumu.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libasdcp.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libcrypto.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libexpat.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libkumu.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libasdcp.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libcrypto.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libexpat.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libkumu.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libasdcp.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libcrypto.a: No such file or directory
i686-apple-darwin9-g++-4.0.1: /var/root/etc/lib/libexpat.a: No such file or directory
################### Installing OpenCinemaTools ######################
install: ../../bin/mkcpl: No such file or directory
install: ../../bin/mkpkl: No such file or directory
install: ../../bin/mkmap: No such file or directory
################### Cleaning OpenCinemaTools ######################
################### Done OpenCinemaTools ######################
sh-3.2#
 
Christopher, either you haven't installed all the needed libraries or the path to the libs is incorrect.
 
Wolfgang Woehl said:
Christopher, you seem to not have built and installed the required dependencies (kumu is part of asdcplib, etc). See the Readme for instructions.

Plus: the version of asdcplib that comes with opencinematools 1.1.2 is ancient. Latest version (1.5.32) is at http://www.cinecert.com/asdcplib/
Click to expand...


John Hurst at cinecert helped me compile (see below) and it seemed to work. But I have no idea where the install was put.
To unpack the file: $ tar xzvf asdcplib-1.5.32.tar.gz Then to build: $ cd asdcplib-1.5.32 $ ./configure $ make $ sudo make install The last step will ask for your password.
The README does not give a detail of where the files can be found and if they are in the right place. Throughout this DCP experience, my primary problem has been finding out where the elements are installed.
 
It seems that asdcplib-1.5.32 installs all its elements in /usr/local/lib
but opencinematools looks for these elements in i686-apple-darwin9-g++-4.0.1. Is this normal? should I create the files that opencinematool is looking for?
How did you all do it? Incidentally, I am installing onto a macintel 2.66ghz OS 10.5.8
Many thanks
 
There are a few places you'll find libraries are installed.

/usr/lib, /usr/local/lib, and /opt/local/lib (if using macports). These should be in your library path and be found, unless an build file specifically gives another path. I didn't use the build.tcsh file included with opencinematools, so I don't recall what it was looking for.

Try this. Create a file called Makefile in the same directory as the build.tcsh. Copy the below into. The formatting might get goofed up, but any indents needs to be TABS not spaces.

CC = g++
LIBS = -lm -lasdcp -lkumu -lcrypto
SRCS = ../../src/
BINS = ../../bin/

all : mkcpl mkpkl mkmap

mkcpl : $(SRCS)mkcpl.cpp
$(CC) -o $(BINS)mkcpl $(SRCS)mkcpl.cpp $(LIBS)

mkpkl : $(SRCS)mkpkl.cpp
$(CC) -o $(BINS)mkpkl $(SRCS)mkpkl.cpp $(LIBS)

mkmap : $(SRCS)mkmap.cpp
$(CC) -o $(BINS)mkmap $(SRCS)mkmap.cpp $(LIBS)

install :
install -v -p -s ../../bin/mkcpl /usr/bin
install -v -p -s ../../bin/mkpkl /usr/bin
install -v -p -s ../../bin/mkmap /usr/bin
 
Many thanks for your response. I created a Makefile but I probably did not do it properly. Below is the result. But before hand, I have some questions as I learn more about unix and opensource.
1. You mention indents. If there are any, where could they be?
If you have the time, you can send me a file to christopher@fearlesstv.com
2. You mention macport. I could not find opencinametools in macport. Did you? It would make life easier.
3. I found i686-apple-darwin9-gcc-4.0.1 in the usr/bin/ . Does the error below mean that it does not see the file?
4. What OS did you build this on?
5. Could this be built with Xcode?

From all I discover I will publish here a 'how to', so any neophyte details would be very helpful.


LowdenINTEL:macosx christ$ ./Makefile
i686-apple-darwin9-gcc-4.0.1: =: No such file or directory
i686-apple-darwin9-gcc-4.0.1: g++: No such file or directory
i686-apple-darwin9-gcc-4.0.1: no input files
./Makefile: line 2: LIBS: command not found
./Makefile: line 3: SRCS: command not found
./Makefile: line 4: BINS: command not found
./Makefile: line 6: all: command not found
./Makefile: line 8: SRCS: command not found
./Makefile: line 8: mkcpl: command not found
i686-apple-darwin9-gcc-4.0.1: no input files
./Makefile: line 9: BINS: command not found
./Makefile: line 9: SRCS: command not found
./Makefile: line 9: LIBS: command not found
./Makefile: line 9: -o: command not found
./Makefile: line 11: SRCS: command not found
./Makefile: line 11: mkpkl: command not found
i686-apple-darwin9-gcc-4.0.1: no input files
./Makefile: line 12: BINS: command not found
./Makefile: line 12: SRCS: command not found
./Makefile: line 12: LIBS: command not found
./Makefile: line 12: -o: command not found
./Makefile: line 14: SRCS: command not found
./Makefile: line 14: mkmap: command not found
i686-apple-darwin9-gcc-4.0.1: no input files
./Makefile: line 15: BINS: command not found
./Makefile: line 15: SRCS: command not found
./Makefile: line 15: LIBS: command not found
./Makefile: line 15: -o: command not found
usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 file2
install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 ... fileN directory
install -d [-v] [-g group] [-m mode] [-o owner] directory ...
install: ../../bin/mkcpl: No such file or directory
install: ../../bin/mkpkl: No such file or directory
install: ../../bin/mkmap: No such file or directory
LowdenINTEL:macosx christ$
 
Christopher, you don't run the Makefile but make which in turn reads the Makefile in the current dir. A Makefile lists targets and instructions how to reach those targets, like calling compilers and linkers.

make wants a Makefile with tabs for indentation or it will die and emit nasty curses in the process. Don't ask. Please :)
 
opencinemastools is not in macports. I mentioned that because you can install openjpeg, ffmpeg, imagemagick with macports rather than manually. If you installed those tools with macports, the libs would be in /opt/local/lib. If you did it manually with make, then they would most likely end up in /usr/local/lib.

Apparently, the indents didn't make into the post. The lines with $(CC) should be indented with a tab. Also, the "install -v lines ... " should be indented with a tab. The make tool is a strange beast.

Did you install xcode? I'm assuming you did since you have gcc and make. As Wolfgang mention you should run 'make' in the directory where the Makefile is located. There are some tutorials on the make process on the web, I'd suggest reading through some. You don't want anything too detailed, just a little overview. Unfortunately, building with make/configure can be stupidly complicated, fussy, and irritating at times. In the Linux days before yum or apt, you could spend weeks trying build something on regular basis.

opencinematools will build on OSX, its just a few minor details you need to sort out. I built it on 10.6, but 10.5 should work the same.

If you still can't get this to work, I'll email you over my Makefile.
 
So, speaking of OSes, what is everyone doing their workflow on? I've spent time getting it to work on Windows, Linux, and OS X. I found it was easiest to compile everything and run under Linux, but I prefer the Mac because I use Final Cut and other video tools.
 
For my part, I am a mac man. I use FCP and avid for my projects. I prefer Avid, particularly now that the version 5 is out. The primary problem with Avid is that it works in 701 colourspace, unlike everything else, that is in RGB. But in the end, either I spend my time dancing between apps in FCP or I have a slightly reduced colour space. You can't win them all. As for grading, I have used the much proclaimed Color. It looked great at first until realised how limiting it is for multipasses etc. So I am back to Avid Symphonie, with a much more fluid and integrated workflow.
Lastly, I would not be surprised if Apple is reading this thread and saying, why don't we integrate these free terminal tools into a future version of Final Cut Cinema Tools. If I am managing to get through it, it would take them but a few hours to create a GUI that does it all automatically.
 
Hi,

I tested converting RGB files to XYZ from After Effects, but the colors seem really greenish on my monitor. Is this how it should be, since a computer monitor is in RGB color space?

Also, the source files are in RedSpace gamma, so if I go the Imagemagick route I should change the matrix, right? Or export clips again from Redcine with REC. 709 gamma?
 
Terrence Meiczinger said:
opencinemastools is not in macports. I mentioned that because you can install openjpeg, ffmpeg, imagemagick with macports rather than manually. If you installed those tools with macports, the libs would be in /opt/local/lib. If you did it manually with make, then they would most likely end up in /usr/local/lib.

Apparently, the indents didn't make into the post. The lines with $(CC) should be indented with a tab. Also, the "install -v lines ... " should be indented with a tab. The make tool is a strange beast.

Did you install xcode? I'm assuming you did since you have gcc and make. As Wolfgang mention you should run 'make' in the directory where the Makefile is located. There are some tutorials on the make process on the web, I'd suggest reading through some. You don't want anything too detailed, just a little overview. Unfortunately, building with make/configure can be stupidly complicated, fussy, and irritating at times. In the Linux days before yum or apt, you could spend weeks trying build something on regular basis.

opencinematools will build on OSX, its just a few minor details you need to sort out. I built it on 10.6, but 10.5 should work the same.

If you still can't get this to work, I'll email you over my Makefile.
Click to expand...

Sadly, the makefile that I have attached just does not quite make

LowdenINTEL:macosx christ$ make Makefile
make: Nothing to be done for `Makefile'.

Have you any ideas?

Many thanks
 

Attachments

You must log in or register to reply here.
Back
Top