Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Why does Premiere suck so bad??

  • Vince Becquiot

    March 31, 2010 at 8:20 pm

    Those are typical compression artifacts. Again, keyframe interval I’m sure has a lot to do with it on the Camtasia side, so give that a shot.

    Vince Becquiot

    Kaptis Studios
    San Francisco – Bay Area

  • Zack Yoshyaro

    March 31, 2010 at 8:37 pm

    I set the key frame everywhere from 1, all the way to 2000+..

    I guess I’m screwed…

  • Vince Becquiot

    March 31, 2010 at 8:44 pm

    You could get a copy or GSpot or Super to analyse the file and see how it was encoded as well.

    Next is using h.264 instead.

    Vince Becquiot

    Kaptis Studios
    San Francisco – Bay Area

  • Jeff Brown

    March 31, 2010 at 8:44 pm

    Have you tried differing bitrates? (I might have missed that in your posts). Also, in CS3, there are 2 different FLV compressions: On2 and Sorenson. On2 has always worked better for me. I typically use a bitrate of 800 – 1600 Kbps, depending on the image size.

    One question would be: why are you using FLV video at all if most of the content is slides? Would it be possible to use FLV audio-only with cue points to trigger still-image slides?

    -jeff

  • Alan Lloyd

    March 31, 2010 at 9:52 pm

    Why are you capturing 24 fps to begin with? Especially to go to 15 fps in your Flash encode?

    There’s simply no reason to do 24 fps for something like this, first off.

    I do regular 720 x 480 DV, encode it at 320 x 240/350K in AME, and it works just fine, with real people on camera. To tell me a screencap won’t work strains credulity. Then again, 13K is barely enough for tolerable audio, let alone video. Why this datarate? How are you delivering?

    Also, I have seen strange things from Camtasia captures when some types of overlay are happening.

  • Zack Yoshyaro

    March 31, 2010 at 11:25 pm

    You could get a copy or GSpot or Super to analyse the file and see how it was encoded as well.

    Next is using h.264 instead.

    Ah! These might shed some light. I’ll check them out.

    Have you tried differing bitrates? (I might have missed that in your posts). Also, in CS3, there are 2 different FLV compressions: On2 and Sorenson. On2 has always worked better for me. I typically use a bitrate of 800 – 1600 Kbps, depending on the image size.

    Yeah, I’ve tried various bitrates, and both sorenson and on2 codecs. They all produce similar results. Unless, of course, I slam the bitrate to the top, then yeah it looks fine.

    One question would be: why are you using FLV video at all if most of the content is slides? Would it be possible to use FLV audio-only with cue points to trigger still-image slides?

    FLV is the format that we’re asked to deliver in. I guess the clients site is set up with them in mind.

    Why are you capturing 24 fps to begin with? Especially to go to 15 fps in your Flash encode?

    There’s simply no reason to do 24 fps for something like this, first off.

    You’re absolutely right. It’s normally set at 15 for frame grabs, the higher settings were from me trying to record an animation on-screen. My apologies.

    I do regular 720 x 480 DV, encode it at 320 x 240/350K in AME, and it works just fine, with real people on camera. To tell me a screencap won’t work strains credulity. Then again, 13K is barely enough for tolerable audio, let alone video. Why this datarate? How are you delivering?

    Man, I completely agree, it’s an awful data rate. But I’m a victim of employment. The client wants a specific size, fps, and data rate. They’re being delivered as online content and hard media.

    If this is an unfixable issue, what is the best format to export out of premiere with so I can later convert it with camtasia?

  • Mike Cohen

    March 31, 2010 at 11:58 pm

    [Zack Yoshyaro] “The client wants a specific size, fps, and data rate.”

    For future reference, important information like the above would have been most helpful in the original post, and would have saved you from getting criticized for a vague question.

    Granted, everyone at one time or another has posted something out of frustration only to realize later that they were reacting to emotion rather than being thoughtful.

    Good luck.

    Mike Cohen

  • Fernando Mol

    April 1, 2010 at 2:29 am

    I had problems with AVI files generated from Camtasia. I captured them on the fly and saved as AVI.

    The files had a fluid playback in Media Player, but when imported to Premiere or After Effects the frames were jumping or artifacts showed. I couldn’t find a fix.

    It’s possible that Camtasia AVI files had a buggy codec, or maybe some settings should be tweak before you capture them.

    Just sharing.

    *Always share a link to your site and rate the posts. This is a free service for you and for us.

  • Tim Kolb

    April 1, 2010 at 3:08 am

    What frame size are you outputting too?

    I assume the file is 640×480 square pixel capture?

    Give us some more information and less hyperbole.

    TimK,
    Director, Consultant
    Kolb Productions,

  • Alan Lloyd

    April 1, 2010 at 4:01 am

    [Fernando Mol] “I had problems with AVI files generated from Camtasia. I captured them on the fly and saved as AVI.

    The files had a fluid playback in Media Player, but when imported to Premiere or After Effects the frames were jumping or artifacts showed. I couldn’t find a fix.

    It’s possible that Camtasia AVI files had a buggy codec, or maybe some settings should be tweak before you capture them.”

    Likewise. I am not really a fan of Camtasia. It’s useful enough for what it does – sort of. The real problem is, better solutions cost more.

Page 2 of 3

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