Forum Replies Created

Page 5 of 6
  • Alec Eagon

    May 26, 2011 at 9:34 pm in reply to: Can’t get a container to move over (CSS)

    Looks like it was an error in an outdated version of the source CSS.
    Thanks though!

    Alec E.

    Macbook Pro 17″ / 2.16 GHz Intel Core Duo / 2GB 667Mhz DDR2 SDRAM / 300 GB HD 5000RPM / OSX 10.5.8

    Editing with: FCP 6.0.6

    Working off of a Firwire800 500GB Glyph HD (I believe it is 7200RPM)

  • Alec Eagon

    December 31, 2010 at 8:26 am in reply to: Gamma Shift Prob (Exporting DVCpro Timeline to H264)

    for some reason x264 won’t work in my FCP even though it is correctly installed….but exported 8-bit, then opened it in mpegstreamclip and exported x264 it was fantastic…I also went a step further and imported the MPSC x264 file into Compressor and then exported to MP4.

    The x264 export from Mpeg Streamclip is bright but it looks fantastic…on Vimeo it looks almost better and has less grain than the original file on FCP.

    The Compressor MP4 export has much richer blacks but has more grain….hmm…but looks fantastic on Vimeo as well.

    Problem pretty much solved…low light was likely my biggest obstacle when dealing with videos like this: https://vimeo.com/18143666

    Thanks to everyone!

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Alec Eagon

    December 29, 2010 at 4:29 pm in reply to: Gamma Shift Prob (Exporting DVCpro Timeline to H264)

    I kind of figured that about the QT 7 option. I tried doing the x264 trick with the adjusted gamma and that ended up helping a bit…I think…but I still got way more grain in my videos and a bit of washed out greys…having said that, the Gamma Problem may have been drastically exagerated in the videos I had problems with a week ago because they are extremely low light. (ex. https://vimeo.com/18141080)

    I will do a test with the x264 method on vid I am working on with more daylight….however it gets progressively darker as it is at sunset so we’ll see how the blacks look…

    Alec E.

    Macbook Pro 17″ / 2.16 GHz Intel Core Duo / 2GB 667Mhz DDR2 SDRAM / 300 GB HD 5000RPM / OSX 10.5.8

    Editing with: FCP 6.0.6

    Working off of a Firwire800 500GB Glyph HD (I believe it is 7200RPM)

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Alec Eagon

    December 29, 2010 at 6:35 am in reply to: Gamma Shift Prob (Exporting DVCpro Timeline to H264)

    Just went to the apple store and they reinstalled QT 7 and QT X for me. Went into the options of QT 7 and enabled the color capatability option, exported a new video out of FCP, looked fantastic (no blacks turned to greys) on QT X abd QT 7, uploaded to vimeo…got the gamma shift…looks like crap.

    ….is this something I should take up with Vimeo?

    Thanks to everyone for all the help thus far, i am getting really close.

    Alec E.

    Macbook Pro 17″ / 2.16 GHz Intel Core Duo / 2GB 667Mhz DDR2 SDRAM / 300 GB HD 5000RPM / OSX 10.5.8

    Editing with: FCP 6.0.6

    Working off of a Firwire800 500GB Glyph HD (I believe it is 7200RPM)

  • Alec Eagon

    December 23, 2010 at 6:43 pm in reply to: Gamma Shift Prob (Exporting DVCpro Timeline to H264)

    Okay, ya i was just reading about that in the manual. I am really an amateur with the HVX.

    in regards to the QuickTime Preference Settings—This is were I am really in a jam. While transferring fcp to my new computer I guess quicktime X never realized fcp was there and thus QT PRO never activate. I made a really dumb move and deleted QT X thinking that I would easily be able to reinstall it from Apple….turns out I can’t do that or install QT7 from online (cause it thinks QTX is still there) and my snow leopard disc is a thousand miles away.

    – is this QT pref setting something that works into FCP or is it something for QT exports?

    – My deadline is basically tonight — is anyone familiar with any other programs that might help me get around the gamma issue so my footage doesn’t get washed out (loss of black definition) when uploaded to Vimeo???

    Thanks so much to everyone for the help.
    Really Really appreciate it.
    alec

  • Alec Eagon

    December 23, 2010 at 5:45 pm in reply to: Gamma Shift Prob (Exporting DVCpro Timeline to H264)

    You know, come to think of it I am not exactly sure why it is DVCpro 720p….the Timeline is in 23.98fps and the frame rate in the browser is listed as 23.98 / DVCPro HD 720p60….what does that mean? Should I have done some converting before I began?

    Alec E.

    Macbook Pro 17″ / 2.16 GHz Intel Core Duo / 2GB 667Mhz DDR2 SDRAM / 300 GB HD 5000RPM / OSX 10.5.8

    Editing with: FCP 6.0.6

    Working off of a Firwire800 500GB Glyph HD (I believe it is 7200RPM)

  • Alec Eagon

    July 31, 2010 at 10:01 pm in reply to: Cinema Tools: Conform 1080i 29.97 to 720p24

    I’ll give old compressor a shot. Thanks a ton Rob!

    Alec E.

    Macbook Pro 17″ / 2.16 GHz Intel Core Duo / 2GB 667Mhz DDR2 SDRAM / 300 GB HD 5000RPM / OSX 10.5.8

    Editing with: FCP 6.0.6

    Working off of a Firwire800 500GB Glyph HD (I believe it is 7200RPM)

  • Alec Eagon

    July 31, 2010 at 6:10 pm in reply to: Cinema Tools: Conform 1080i 29.97 to 720p24

    Thanks for the info and quick response Rob, now when I take the slow mo file back into compressor, what I do then is set the time frame to what it was at normal speed and have Compressor conform it back right???

    Also I am reading about programs such as Twixtor, FieldsKit, Nattress in this thread https://forums.creativecow.net/thread/8/1000022 —that allow you to do all of this in FCP?

    Is using the de-interlacer in FCP a bad idea, should I invest in a deinterlacer if I want to bypass the compressor time issue?…

    Also I found this one —JES Deinterlacer— looks like its free. (https://www.xs4all.nl/~jeschot/home.html#DEI)

    Thanks again!

    Alec E.

    Macbook Pro 17″ / 2.16 GHz Intel Core Duo / 2GB 667Mhz DDR2 SDRAM / 300 GB HD 5000RPM / OSX 10.5.8

    Editing with: FCP 6.0.6

    Working off of a Firwire800 500GB Glyph HD (I believe it is 7200RPM)

  • Alec Eagon

    March 16, 2010 at 12:47 am in reply to: Apple ProRes Render/Export Problems???

    David, Shane,

    Thank you guys so much. I am totally newbee to Pro Res and 10-bit. This helps a ton.

    I am currently rendering the PR HQ file in a SQ sequence, then I will export it.

    If I am uploading to vimeo, should I just upload the SQ pro res file and let the website convert it to h264 or should I bring the SQ file back in and export it h264?

    thanks again!

    -alec

    Alec E.

    Macbook Pro 17″ / 2.16 GHz Intel Core Duo / 2GB 667Mhz DDR2 SDRAM / 300 GB HD 5000RPM / OSX 10.5.8

    Editing with: FCP 6.0.6

    Working off of a Firwire800 500GB Glyph HD (I believe it is 7200RPM)

  • Alec Eagon

    March 16, 2010 at 12:22 am in reply to: Apple ProRes Render/Export Problems???

    awe….i just reimported the FCP exported Apple Pro Res HQ to FCP and watched it and it appears to be the same. thanks for the heads up on QT…. I was kinda wondering if that was the case.

    should I create a new sequence with that file and render it Pro Res SQ and then try to export that?

    I just need something that will have this motion on vimeo.

    Thanks!!!

    -Alec

    Alec E.

    Macbook Pro 17″ / 2.16 GHz Intel Core Duo / 2GB 667Mhz DDR2 SDRAM / 300 GB HD 5000RPM / OSX 10.5.8

    Editing with: FCP 6.0.6

    Working off of a Firwire800 500GB Glyph HD (I believe it is 7200RPM)

Page 5 of 6

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