Forum Replies Created

Page 12 of 64
  • George Washington was released in 2000 which means it was edited even earlier. By the end of 2001 I edited a 35 mm feature and was logging footage for 16 mm short. In the summer of 2003 I helped Solvent Dreams to troubleshoot bad telecine logs for a 35 feature and the email exchange sounded routine.

    As far as I remember FilmLogic had change lists. I was a beta tester so I should remember asking Loran for them but I don’t. And I remember generating them. May be Apple removed it in the first version of CinemaTools but they were back shortly.

    The biggest film related improvement to FCP didn’t come after Cold Mountain. It came much later after Will MacNeil made a very elaborate document about FCP shortcomings and send it to Apple. I signed his petition so I know exactly what he asked for and what we got. It was 24@25 timecode support. It didn’t affect negative cutting but it was really huge for Digital Intermediate.

  • Comparing to some really tough mess like a Reality TV, feature film editing workflow is pretty straightforward. I don’t see why would anybody need a small team to edit a feature film in FCP 3 after a couple of dozens of feature films were successfully edited in FCP 1 and 2. Hollywood politics is my guess. Maybe I should read the book though.

  • Misha Aranyshev

    July 11, 2014 at 11:54 pm in reply to: Destructive edits

    If the edit was good it doesn’t usually take much time to recreate it from a scratch. That’s why I stopped using “versioning” by saving projects or keeping several sequences of the same scene with different variants long time ago. I only keep the versions with client’s comments.

  • Misha Aranyshev

    June 15, 2014 at 5:37 am in reply to: Edit desk facing the window, is it a problem?

    It sounds weird to me. With windows behind you get all the glare on your monitors. Facing windows you get none unless you paint your walls white and wear white shirts.

    On a related topic, why all you people put your preview monitor to your side? Mine is directly in front of me and I always get weeks of neck pain after working in someone’s room.

  • Misha Aranyshev

    April 25, 2014 at 2:23 am in reply to: But it’s a DRY camera heat…

    True, Red One overheating was a major factor to consider in the early days. Also the original Sony Cinealta would lose back focus after a couple of hours of work due to heat expansion of the mount plate.

  • Misha Aranyshev

    April 25, 2014 at 2:13 am in reply to: Is Resolve the NLE we’ve always wanted?!

    [Bill Davis] “that X reached a million paid seats WAY faster than legacy.”

    Sure. But the Party Line is FCP Legacy was niche and FCPX has much wider appeal, much lower price and a modern hip distribution channel.

  • Misha Aranyshev

    April 23, 2014 at 2:14 am in reply to: Location change

    Thanks. I’ll look into it.

  • Misha Aranyshev

    April 23, 2014 at 2:13 am in reply to: Is Resolve the NLE we’ve always wanted?!

    [Mitch Ives] “Interesting thought… I’d have to agree.”

    When the sales numbers are bad there are two options: improve the product or drop it.

  • Misha Aranyshev

    April 22, 2014 at 12:40 am in reply to: Location change

    I don’t get any note about JavaScript above the empty space.
    My Safari is version 7.0.3 (9537.75.14).
    I get the same behaviour in Firefox.

    I can see both links.

    There is some development. When I switch from TimeWarner Cable to T-Mobile the map on the page is loading. I can edit my location there, both the pin on the map and the name in the field above the map.. It just doesn’t show in my profile.

  • Misha Aranyshev

    April 21, 2014 at 7:30 pm in reply to: Location change

    I have JavaScript enabled, pop-up block disabled, all 3rd party extensions disabled in Safari. I emptied the caches and quit and relaunched Safari. Still there is just empty space where Google map is supposed to be at the link you provided.

    Sorry

Page 12 of 64

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy