Forum Replies Created

  • By the way, now that the average PC sold today has a 2GB+ dual core 64-bit CPU, what is the need for an expensive video capture card anyway? If I’m not editing for analog broadcast and I’m always capturing via 1394/Firewire, can’t I do everything I need to do without one? Isn’t my money better spent on a faster processor, more ram, and some fast hard drives?

  • Hey everyone, thanks for your advice. You’re right. The bottom line is Canopus sucks. I’m really pissed I paid $1300 for that card and they don’t support it a few years later. I’m also pissed I spent so long trying to get the thing to work, when it was hopeless. They could release drivers to keep it working if they wanted to, but this appears to be strategic obsolescence. Or they could have at least responded to my email to technical support. I guess they think I’m going to upgrade to one of their newer cards. Hell no. I’m done with Canopus. Never again. I got a $15 firewire card and did what I needed to do. And if I ever buy another video capture card, it certainly won’t be from them.

  • Robert Smithlee

    June 30, 2005 at 2:42 am in reply to: Blocky Titles

    I am by no means an expert in this area, but I’ve been running into the same problem. The solution could be as easy as finding the right compression codec and compression settings. After hours of testing, making a mov using Sorenson3 gave me the best results. See the “rough fonts” thread from yesterday for more.

  • Robert Smithlee

    June 30, 2005 at 2:37 am in reply to: rough fonts in avi imported into Premiere

    thanks for your suggestions. As it turned out, part of the problem was that the fonts look much worse when previewing than in the actual rendered movie. Another problem was the compression codec and settings. Flash didn’t give me many options, but selecting the right codec and settings in Premiere was important. H.263 resulted in jagged edges, cinepak was better for the fonts but much worse for everything else, indeo5.10 fonts were ugly…. finally sorenson3 gave me the best quality. I used 100% quality and ended up with a big file. But that was on purpose, since I was going to be compressing it all again with Quick Time Pro to make the flv. I did that using 2 pass encoding, & high quality, and I’m very happy with my results.

    I would still like to learn more about codecs and compression. There are so many to pick from I always spend much more time than I should rendering tests to figure out the right one.

    And as someone else has mentioned, I should have used AE for the titles. I didn’t because it was all set up in Flash already, and I am much more familiar with that environment. I would love to learn AE — just haven’t gotten around to it yet.

    Thanks again.

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