Forum Replies Created

Page 5 of 29
  • Pfft. Microsoft has done that for decades!

  • Anyone remember Apple’s LISA?

  • Here is the new car.
    It doesn’t have an engine, so it isn’t a car.
    No, you just haven’t figured out how to make it move yet.
    But it doesn’t have an engine.
    Engines are the old the old way of thinking.
    Ok, so how does this thing move.
    Who says it has to move?
    I do, that’s how I get places.
    Not everyone has to get places.
    well, I do
    well, this car isn’t for you then.
    But professionals need to get places.
    You are insulting those people who don’t need to get places by implying they are not professional.
    But getting places is the whole point of a car and this car can’t get me places.
    well, there is an upgrade coming.

  • David Dobson

    July 9, 2011 at 6:52 pm in reply to: a rotten project

    Sounds like a memory leak. I had a project (one I am still working on) where sometimes the system was really slow. CTRL-ALT-DEL to check on system resources and ALL of the memory is being used up (but Premier is only using 3MB). Eventually, it stopped happening. This project had dynamic links to AE.

  • David Dobson

    July 8, 2011 at 2:42 pm in reply to: a rotten project

    First you can try to open the project from within a new project. So if there is something wrong with the project file, this may ignore that. You could also export an XML, then import that into a new project and then relink only what you need. You could also try consolidating the project and see if that one runs better.

  • David Dobson

    July 8, 2011 at 2:37 pm in reply to: Who was The Target For FCP X?

    Right, well who really believed they were going to get a professional NLE for $300? Right off the bat you had to spend another $50 for Compressor. So in the end, if the components you need to make the thing work for you come in around $1000, well, that at least will make sense.

    As for the tone – as a Premiere editor – that’s all I’ve heard from FCP users for years. If you are editing in Premiere you aren’t a professional editor. Not all of you, but enough real assholes to leave a bad taste in my mouth. Now you are doing it to each other, so I am mostly amused. But I feel your pain too. Adobe hasn’t always been very responsive to users needs. At least CS5 was worth the wait.

  • As an outsider (I’ve only ever owned an iMac a long time ago), but one who uses FCP on other peoples macs all the time (I prefer Premiere on a PC) my observation about the release of FCPX and why it is so hurtful boils down to a very simple thing. Apple lied about about what was coming down the pipe. They encouraged pro users to believe that FCPX would be an upgrade to FCP7. Had they been honest about FCPX, the conversations about switching would have started happening a year or more ago. FCP7 users love their program and they thought they were getting the 64-bit upgrade every other NLE has gotten – and then they would still have the ultimate editing platform. Instead, they all waited, feeling the pain of not being 64-bit, but believing that when FCP8 came out, it would be worth the wait – the most awesome upgrade to the most awesome NLE ever. Instead, they have been betrayed. So they are rightfully angry. And now they are being told to wait some more? That FCPX will get fixed.? I can understand why editors aren’t buying that line now.

  • David Dobson

    July 7, 2011 at 5:08 pm in reply to: a rotten project

    Yikes!
    If there are lot of really big files, 300dpi @ more than 3000 pixles, that can really slow things down. Sometimes even one can be a problem. Resize in photoshop to 72dpi (and adjust the pixel size back to something bigger than you need.
    Also, i have found that Premiere really dislikes CYMK files, so remove those and/or replace them with RBG versions.
    Maybe that will help. But if other projects are working fine, then it’s definitely a source file. And it doesn’t even have to be in the timeline to cause problems. Might also be a good idea to go through all the photos and see if any are damaged

  • David Dobson

    July 7, 2011 at 4:56 pm in reply to: Premiere Pro wont start but it will under admin

    Can set your profile to Admin?

  • David Dobson

    July 7, 2011 at 4:54 pm in reply to: Why are my edges jagged?

    Interlaced frames look jagged as stills on a progressive monitor – especially where there is motion.
    But during playback on an interlaced TV they can look fine.

    It’s also [possible you have the wrong field dominance interpretation for the raw source file. Upper Field rather than Lower filed first – or vice versa, depending on what the footage was captured on. (DV footage is lower filed first, HDV footage is upper filed first – I think.)

    Just some thoughts.

Page 5 of 29

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