Forum Replies Created

Page 70 of 315
  • [Chris Frantz] “For the record, Yosemite works great and El Capitan public beta is ages ahead of Windows 10.”

    For the record Ppro 2015 works great. Except when it doesn’t. Which was certainly so true of Yosemite that many editors still haven’t upgraded to it. The public outcry of Yosemite screwing up drivers and peripherals from coast to coast was/is easily as large as the public problems with CC 2015. As for “my Beta is better than your Beta” – I don’t know anyone who uses Beta software to pay the rent, and that’s why it’s called “Beta.”

    [Chris Frantz] “If you’d like to see additional tests done, then you should do them and add them to the spreadsheet, otherwise you’re introducing points without any data to back them up.”

    My point is quite simple – talking about the speed of your MBp is like talking about the speed of my Subaru Forester – interesting up to a point, but if I were interested in speed I wouldn’t be driving a Subaru.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • [Chris Frantz] “Did you check out the spreadsheet he posted?”

    Yes, I struggled through it. He had a Hackintosh, non-xeon, but no older MacPro listed. Did you check out the spreadsheet? Put a Titan in a 2010 dual quad Mac Pro and then post a score.

    [Chris Frantz] ” And you can go ahead and install Windows w/ Premiere and immediately start making compromises.”

    Life is compromise.

    [Chris Frantz] “Make sure you’re running CC 2014 because 2015 is too buggy for production work.”

    If history is any guide, that will be true till the next upgrade, out in a few weeks.

    [Chris Frantz] “Also, Windows 7 because 8 is dead, but also Windows 10 is about to come out with an aggressive update schedule so you may want to do that but not for active production work. That sounds like fun.”

    Oh yes, because every OSX update has been simple and clean. Yosemite anyone?

    [Chris Frantz] ” In the meantime, I guess we’ll all just be rendering faster in on our software optimized for our hardware by the same manufacturer. Is that the deal?”

    You have to run FCPX if you own a MBP because while it is indeed optimized for FCPX it pretty much sucks at everything else. How’s that for childish overstatement?

    Back in the real world, use whatever you like, they each have their strengths and weaknesses, and the only efficiency test that matters is the one where you compare your exact workflow to all the other options – it’s not a numbers game, I don’t edit with Geekbench3 S.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • So if your NLE is constrained to OSX, and if you you use a laptop to edit with, then FCPX is superior to Ppro when exporting – is that the deal? Fantastic, now let me get back to using PPro on my old Mac Pro, and if i want to decrease my export times I’ll buy a faster GPU, and if I want to increase my Ppro efficiency further, I’ll buy a PC workstation.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • Thank you Bill.

    It’s always satisfying to learn your childhood was well spent.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • Ordinarily I put everything on a timeline, which becomes the assembly, then duplicate that timeline and cut away what I don’t want. Then rinse and repeat. The sequences become a history of my editing process and I can always go back a few steps to look for what I have cut away. Your options for skimming and trimming are much greater in a timeline, plus you always know the total running time of all the material you are looking at.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • Herb Sevush

    July 9, 2015 at 12:09 pm in reply to: Sequence Settings – Am I stupid??

    I’m assuming you’ve tried the “new sequence from clip” option from the browser. If this didn’t give you a properly formatted timeline, open “Sequence Settings” and describe the exact settings you see in both the video and video previews areas.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • Herb Sevush

    July 8, 2015 at 7:25 pm in reply to: Multicam timecode burn in

    [C. Kauffman] “when all cameras and audio are jammed, I’m assuming you would apply TC effect to all clips as a burn-in for reference, synch with timecode and then create your multicam seq?”

    If I needed a TC reference for a client, that would work. It’s never been an issue for me, no one has requested it.

    [C. Kauffman] “I read an interesting post on a Sony forum about the importance of keeping a consistently connected genlock cable between all cameras and audio to avoid small amounts of drift even when TC is hard wired for the duration of the shoot.”

    There is definitely drift when cameras are jam-synced and then unplugged – I’m not aware of any drift when cameras are hard wired during a shoot, but then that’s not my department.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • Herb Sevush

    July 8, 2015 at 6:33 pm in reply to: Multicam timecode burn in

    [C. Kauffman] “Strangely enough, when I selected A cam for every cut and then flattened the seq. and applied Transparent Video with TC effect, I got the same random TC that’s unrelated to anything”

    Don’t use a transparent video layer, put the TC effect directly on the first flattened clip and then add the crop effect. Now copy and paste both effects onto all the other clips of the top track.

    [C. Kauffman] “Curious to hear how you guys handle multicam with matching TC from all cameras and audio since PP seems to think original TC is unnecessary. Do you go through and manually set the TC for each multicam clip?”

    I almost always shoot with matching TC and then sync with that TC in the Ppro multiclips. In those rare instances that I need to sync by audio I will often use the Clips/Modify/Timecode function to assign synchronous time code. Can’t always do this, depends on workflow, but when I can I will.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • [Tim Wilson] “My point being that, in practice, there’s no functional difference between NY and the portion of Florida from Palm Beach to Miami Beach.”

    The Pizza is much better in NYC. The beaches are better in Florida. Rats vs bugs – we’ll call that a draw. Does that make it a distinction without a difference?

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

  • It was the snow.

    As for the Entenmann’s, they only had to go to NYC for that.

    Herb Sevush
    Zebra Productions
    —————————
    nothin’ attached to nothin’
    “Deciding the spine is the process of editing” F. Bieberkopf

Page 70 of 315

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