Forum Replies Created

Page 2 of 3
  • Ryan Early

    June 26, 2011 at 12:00 pm in reply to: Trying premiere and it keeps crashing on a macbookpro

    Thanks for your reply, I did try repairing permissions but not verifying the disk. When I did it showed an error that required me to boot with the install disk. Just have to dig it out and hopefully that will sort it out.

  • Ryan Early

    June 24, 2011 at 1:38 am in reply to: is the pro hardware next ?

    Is premiere also platform agnostic like avid ?

  • Ryan Early

    June 24, 2011 at 12:49 am in reply to: Apple refunded my money!

    This sets an interesting precedent !

  • Ryan Early

    March 20, 2011 at 3:24 pm in reply to: My project is cursed…

    Is the copy and pasted sequence in a new project ? Id the project file contains too many sequences that can I think cause trouble.

  • Ryan Early

    March 20, 2011 at 2:43 pm in reply to: My project is cursed…

    I had a similar headache on a large documentary project. Like you I got fcs maintenance pack, I ended up
    Buying it.

    My issue was with a few jpegs in the sequence. Is the project file massive ? You did mention that you copied and pasted the sequence into a new project which should counter the big project file issue.

    What about creating an offline version of the project file then relinking the media? Thats worked for me in the past.

    Anyway I feel your pain by the end of my feature length doco edit I was ready to buy a copy of premiere.

  • Ryan Early

    January 2, 2011 at 8:41 am in reply to: mpeg2@main level export from final cut pro

    Thanks for the replies, looks like I am off to a post facility then ! Don’t want to buy the new fcs at the moment with the new fcs not far away.

  • Ryan Early

    January 2, 2011 at 3:13 am in reply to: mpeg2@main level export from final cut pro

    I saw that post too, it must only be in the latest version of compressor – I have compressor 3.0.5 which doesn’t have that option for 422 export of mpeg2.

  • Ryan Early

    June 22, 2008 at 3:20 am in reply to: motion templates

    Thanks Richard, I wasn’t modifying the templates I think that may have been the problem. Be nice if the templates automatically adjusted for the sequence settings in fcp.

  • Ryan Early

    February 26, 2008 at 2:15 am in reply to: is the hpx 500 really a hd camera ?

    Thanks for your post Ron, most of my work is corporate and training dvd’s for national companies and government departments, we tend to light and stage everything so not a lot of run and gun. I think xdcamex would be difficult in an ENG environment. Being an older cameraman I much prefer the form factor of the 500 because it is what I am used to but what I am really after is an indication of image quality differences between the cameras. If I can get a camera for under 10k that produces images of a higher quality than one that costs 3 times more (fully kitted out) then the ergonomics of the higher priced camera are harder to justify. Especially if the camera that costs 3 times more is closer to SD than HD in resolution which means I might as well keep shooting with 2/3inch broadcast cams in SD.

    I am planning to hire both and do my own test and compare the workflows but I would like to see a resolution chart comparison between the two, has any one seen a resolution chart for the 500 ?

  • Ryan Early

    February 25, 2008 at 2:28 pm in reply to: is the hpx 500 really a hd camera ?

    I plan to demo both cameras however I would like to see a resolution chart shot by the 500. Does the spatial offset technology give the camera the same level of detail as a native 1920 x 1080 sensor ?

    I have looked on dvx user but I haven’t found a side by side comparison with the ex1. My preference is for the 500 over the ex1, but I want to be sure that it is in fact HD and not an SD camera made a little sharper. If it can resolve enough detail to qualify it as HD then I really don’t care how it gets there.

    Thanks

Page 2 of 3

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