Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • s 10:17 PM on 141122 Permalink | Reply
    Tags: magiclantern, raw

    • s 10:19 PM on 141122 Permalink | Reply

      4. Adjust color temperature using number keys 1-4 for presets, manually adjust using the colored square in the bottom, or pick any color within the image to represent white. (optional)

      5. Adjust exposure by hitting the UP\DOWN keys or by using the on-screen bar next to the color temperature square. (optional)

      *6. Hit “Shift + L” to import 3D LUTs to apply directly before import. This is GREAT if you would like to convert your footage to VisionLOG, CineLOG if you’d like to convert to a specific LOG format, or you can directly apply creative LUTS such as OSIRIS or Impulz, although I recommend saving those for your use in your NLE \ color correction application. (optional)

      *7. “Hit Shift Up/Down” to choice the LUT of your choice from your imported 3D LUTS. (optional)

      8. Hit “W” to choose the export file location of the debayered QT ProRes444 file.

      9. Hit “D” until ProRes(444) is shown as an icon, looks similar to Quicktime.

      10. Hit “T” to adjust between Rec709, sRGB, LOG, and HDR gamma curves. I recommend LOG, Rec709, or sRGB. If using a LUT to convert to LOG, such as VisionLOG or CineLOG, leave the curve at Rec709.

      11. Hit “C” to add the entire directory of MLV files to the queue with custom WB and exposure corrections automatically applied, or hit “E” to add each file manually with specific exposure and WB changes.

      12. Hit “Y” to start processing the MLV files to ProRes444 files synced with audio.

      13. Once the ProRes444 files have been created, you can start editing and color correcting your footage.

  • s 4:46 PM on 130315 Permalink | Reply
    Tags: , inspiration, ,   

    3D Map Video 

    Wide Web World from Paul Wex on Vimeo.

    On the process:

    Hi, first I tested the screen recorders – there was a huge difference between them. The iShowU HD had really the best CPU efficiency, so I began to test the highest screen resolution for the recording without too much loss of the fps. That was 1280×720. I tested my browsers too, but there was no significant difference for me, so I stayed at Chrome. After switching in fullscreen mode I selected the recording range on the screen, so there were no panels or symbols on the screen anymore. Unfortunately the crop had to be quite hard.Start-Move&Record-Stop with short keys, meanwhile 100x computer reboot/log off (the browser became slower and slower after minutes!). I recorded as ProRes422HQ at 720p/30fps and converted to 25p via CinemaTools afterwards. Postproduction, edit and colorgrading in FCP7 with standard plugs and Knoll Light EZ Lensflare.

    Then the music production followed…

    Cheers :)

  • s 11:45 AM on 130312 Permalink | Reply
    Tags: ,   

    Extras | Free Plugins, Free Scripts, Free Presets.

  • s 9:29 PM on 130311 Permalink | Reply
    Tags: fcp,   

    FCPx Project Sharing

    Many times, editors need to share projects. While Final Cut Pro X does not allow more than one editor to be working in the same project at the same time, there is a way to share the same project between editors. Event References make this possible.

    An Event reference is the ability to take a Project and point it to media in a different Event. What you are doing is changing the media that is connected to a Project by changing the Event reference.

    A Final Cut Pro X project doesn’t contain media, it just “points” to media, which is stored in your Final Cut Events folder. This media can be stored locally, or on an XSAN server – though not, however, on a standard-issue OS X Server. We can take advantage of this fact when it comes to sharing projects between editors.

    For example, let’s say two editors, in two different cities, want to both work on the same project, though not at the same time. To start, the first editor makes a complete copy of both the Project folder (stored in the Final Cut Projects folder) and the Event folder (stored in the Final Cut Events folder).

    The first editor sends the second editor both folders, and the second editor starts editing. During this time, the first editor can not be working in the Project. The original Event folder, containing the media, and the Project remain with the first editor, while a copy of the Event folder and Project folder are now also with the second editor. (For those that worry, there is no reduction in image quality when you copy digital image files.)

    The second editor can make changes to both the Project and the Event, such as, say, editing clips, adding keywords, changing clip names in the Event Browser, and flagging clips as Favorites using ratings. However, the second editor can not change the media itself, nor add new media.

    Then, the second editor sends just the Project folder back to the first editor. (Important note, he needs to send theentire Project folder, not just a single Project file contained inside it.)

    If the first editor opens the Project sent by the second editor, all the clips would be offline, because the Project is still linked to the Event folder on the second editor’s system in another city. Instead, the first editor copies the Project folder to her local system in the Final Cut Projects folder. Opening Final Cut Pro X, she selects the Project in the Project Library, without opening it in the Timeline.

    With the Project selected, the editor chooses File > Project Properties (or presses Command+J).

    Click the wrench icon (just above the Inspector button) to display the Project Properties window.

    Click the Modify Event Reference button, which opens the Modify Event Reference window.

    Navigate to the Event folder stored locally on her system and select it. The first editor’s Project now connects to this local media, rather than the media on the second editor’s system.

    By changing Event References, both editors can send this Project back and forth for additional work. Keep in mind that once the Project is sent to one editor, the other editor can not work on the Project as there is no way to reconcile the differences between two versions of the same Project.

    Both the first and second editor have their copy of the Event folder and media stored locally. Changing Event References allows repointing a Project from one Event folder to another.

    This is a very intriguing use of the media management in FCP X because it easily allows changing the Event that is referenced by a Project. It isn’t the same as relinking individual clips, but allows an editor to repoint to all the media in an entire project.

  • s 6:46 PM on 130309 Permalink | Reply

  • s 6:27 PM on 130309 Permalink | Reply

    AE tutorial list



  • s 6:12 PM on 130309 Permalink | Reply
    Tags: , ,   

    AE – make 2D layers a 3D stack 

    position+[0,0,(index-2)*thisComp.layer(“3D Control”).effect(“3D Control”)(“Slider”)]


    with the null being named 3D Control


    taken from :


  • s 6:14 PM on 130226 Permalink | Reply
    Tags: , dropbox, web   

    Use two Dropbox accounts on one computer — theTerran.

  • s 7:52 PM on 130225 Permalink | Reply  

    Drag and drop World 

    Drag and drop geo-json feature files to paint your planet!.

  • s 7:50 PM on 130225 Permalink | Reply
    Tags: , ,   

    Texture Maps of the Earth 

    Natural Earth III – Texture Maps.

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc