Forum Replies Created

Page 17 of 150
  • Mark Raudonis

    April 20, 2012 at 5:08 pm in reply to: One year later…

    [Craig Seeman] “It would be much easier to move from Apple (and some have done that) than to move from Avid if one is invested in their more expensive hardware.”

    I don’t understand this comment. If, as everyone is saying, the Apple route is cheaper, then how/why would it be harder to move. You’re not making sense. An ISIS can support an FCP workflow quite easily. I’ve done it.

    In a software only world, the hardware drops out of the equation. There will always be faster, better, cheaper drives. Did you walk the isles of NAB? You can’t go ten feet without someone pitching a cheaperNAS/SAN.

    Mark

  • Mark Raudonis

    April 20, 2012 at 5:57 am in reply to: One year later…

    Lance,

    Delaying shipment for another year wasn’t an option. Too much pressure to Ship… something, anything. So in Vegas terms, we end up with an Elvis impersonator, rather than the King himself. Even a year later, with the updates and “restored” features currently available, my decision stands. Moving forward, you have to answer two questions: WHEN will it do what I need? and… will it EVER do what I need. I think putting $100 on the craps table gives you better odds than the likelihood of guessing the answers to those two questions.

    mark

  • Mark Raudonis

    April 11, 2012 at 5:17 pm in reply to: Voice Isolation

    Short of a NSA level super secret black ops tech device, this is NOT possible. At least not in a way that would make your client happy.

    Sure, you can play with EQ, you can do “reverse noise elimination” for the vocals, but holy cow, this will be a mess.

    Good luck.

    Mark

  • Mark Raudonis

    March 22, 2012 at 2:36 pm in reply to: Final Cut P2 Codex Problem

    … and it’s a “CODEC” not a CODEX!

    Comes from “Compression/Decompression”.

    A codex is basically a book.
    https://en.wikipedia.org/wiki/Codex

    Maybe that was the problem?

    Mark

  • Mark Raudonis

    March 18, 2012 at 5:19 pm in reply to: Clip names and multiple editors.

    Yes, we mean NEVER change the clip name within the FCP browser! Bad idea.

    FCP even has a feature which allows you to change the filename at the finder level from within FCP. This is both a cursing and bless. If you know what you’re doing, it can be helpful. In a shared storage/project environment is can create instant chaos!

    Add notes in the comments column. Assuming you’ve used a logical file/clip naming system, leave that alone! You’ll be glad you did.

    Do you really need additional opinions on this?

    Mark

  • Mark Raudonis

    March 18, 2012 at 4:03 pm in reply to: Clip names and multiple editors.

    I agree 1000% with what Matt just said.

    NEVER change the filename in FCP7! Especially in a “shared project” environment. Bad idea!

    THe comments column are where your notes should go.

    Mark

  • It isn’t always about price, Shane. Have you seen the Sony PVM -2541?

    This is truly the first affordable flat panel that compares to the old CRT’s.

    The image is really superb!

    Mark

  • We’re putting these in all of our On-line rooms to replace the aging CRTs. Using a Kona 3 to feed ’em.

    https://pro.sony.com/bbsc/ssr/cat-monitors/cat-oledmonitors/product-PVM2541/

    I think they look great!

    mark

  • Mark Raudonis

    March 13, 2012 at 5:41 am in reply to: With Great Sadness……

    [Jeremy Garchow] “Color, before Apple bought it, was pretty damn buggy. “

    We had several seats of “Final Touch” as “Color” was known pre Apple. Paid good money for it. Never regretted it! As I recall, it was quite stable. It was missing some features, but it was predictable.

    can’t say the same for “X”.

    Mark

  • Mark Raudonis

    March 10, 2012 at 3:32 pm in reply to: What if there is no new Mac Pro?

    You’ve all been putting too much “lime in the coconut” for this thread to continue!

Page 17 of 150

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