Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Project scope limits?

  • David Grantham

    January 30, 2009 at 2:28 am

    Thanks. I think I can get the discspace. I just don’t want to lose the flexibility in that final output. It’s only about 14 mintues long and I’d like to have an editable version to refine. BUt I”m going to keep this on the list of workarounds. Thanks for the thought.

  • David Grantham

    January 30, 2009 at 2:30 am

    I have no got a used 8400 as on the business forum I was advised it is very stable. But there’s this on the matrox website about it:

    “This system includes an Intel ICH6R controller in RAID or AHCI mode. These modes are not supported with a Matrox RT.X system because they can cause dropped frames. You therefore need to configure the Intel ICH6R controller to work in a mode supported by Matrox RT.X. For instructions on how to do this, click here2 (if you’re an advanced user), or contact Dell Technical Support.”

    THe link doesn’t work and I’m having trouble contacting Dell. Any thoughts?

  • Alan Lloyd

    January 30, 2009 at 6:55 am

    That’s the good part about uncompressed. Do all your submastering that way, and you can get away with a few more things. All it does is eat up drive space. Flexibility preserved.

    Can’t help on the machine problems – that’s something else again…

  • David Grantham

    January 30, 2009 at 9:25 am

    i got a tech-suport guy too through this (he sold it to me) and it looks like as long as the system isn’t raided (it isn’t) it’ll be okay.

    Thisnew systme appears to solve some problems. Scrubbing the timeline in adobe mode is a completely differnt experience from the previous machine – more than another .8 GHz would suggest to me. SO I’m hoping this is a better config all round. Have to roll back the OS to SP2 for matrox compatibility before I can run this project, though.

    The two stage output solution is in my hip-pocket if this config doesn’t solve it. I think it will. My project isn’t that complex, and I can’t help but think that if PPro is written properly my twenty or so sequences of a few minutes average lenght isn’t going to break things on a machine that’s worht it’s salt. The bins list is huge but it’sjust a big dumb list of addresses and shouldn’t hold things back either.

    My schedule is of course a wreck. BUt that was inevitable at this point.

  • John Kis

    February 2, 2009 at 11:20 pm

    Hi, I had a problem with a big project similar to yours. I had approx 600 source clips and before they could all be imported Prem crapped itself.

    What I did was use VirtualDub to join the source clips together using a ‘direct stream copy’ which doesn’t recompress – so no loss of quality. I did this for different categories of clips, so I would join the clips together in groups of approx 50. That way, when I imported into Prem, I only had 12 source clips! Then you bring those clips into the timeline and cut them back up. A pain, I know, but a way around your problem.

    Good luck!

  • David Grantham

    February 2, 2009 at 11:42 pm

    Someone local has been suggesting that upgarding to 2.0 might solve the problems, which stil remain on a replacement computer.

    Anyone have any thoughts?

Page 2 of 2

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