Mylenium
Forum Replies Created
-
Mmh, that indeed doesn’t sound too exciting. The AVI is presumably mostly just a container containing DV streams (it would read Microsoft DV as compression). This would be my first point to contend. Neither is MS’ DV implementation very “clean” nor is it very high quality. I also believe that you wouldn’t work optimally with it in Premiere, since it cannot always detect the blocks of the DV compression, thus introducing extra compression even with a simple hard cut by recalculating the edited clip (I haven’t used Premiere in a while, but I know that in older versions there always were such problems). Finally, it will also explain the lengthy rendering: Premiere (or AE for that matter) need to “unwrap” your DV streams from the conatianer, do their rendering and then pack the result back into an AVI. If you have audio, this will of course also need to be processed (though in comparison to the video it’s nearly neglectible). So to make a long story short: Most of your troubles could be resolved by getting a “real” capture card. It would bypass Windows’ own routines, use it’s own CoDecs and also have some extra benefit’s like additional software. I know it’s easier said than done, but I think you will see great improvements and probably consider the 300 bucks a good investment.
Mylenium
[Pour Myl
-
[Kim] “Do you have any suggestion to improve the quality and the sharpness of the object in movie?”
No, not really. On the DVD side you’d have to interfere with the settings for quantization and apart from the fact that the AE exporter doesn’t provide this option, it’s no trivial thing to meddle at this level. Your best bet is to try and improve image quality on the AE side which can be anything from using effects such as Find Edges on a duplicate of your layer and then blended with the original in Overlay mode to using advanced sharpening/ resizing tools such as Digital Anarchy’s Resizer.
Mylenium
[Pour Myl
-
Mmh, I suppose you could use some of those transcoding engines like Shrink also. Some of them can handle unmultiplexed system strems not contained in a VOB. I’d have to ask my colleague about it, but he won’t be in for a few days, so it may be too late for you.
Mylenium
[Pour Myl
-
I’m sure if you contact Maxon directly, they will be able to help you. The way I imagine it, they will send you the current version for 9.5 but since they are nice guys, they will pack a 8.5 version on top of it.
Mylenium
[Pour Myl
-
This “swimming” of MPEG blocks is quite common. The areas in question do not change enough so one block ist recycled across multiple frames making it look lie it is sticking or afloat from the other surrounding blocks. There is rather little you can do about it. You could add some minimum blur or noise in some areas and of course you can tweak your compression settings, but it will never go away completely.
Mylenium
[Pour Myl
-
AE is a 32 bit app and will never use more than 3 GB. It’s simple computational mathematics. It could only use more than that if it were fully 64 bit native, but that hasn’t happened so far. So there is no point in spending on more RAM just for AE.
Mylenium
[Pour Myl
-
Apart from upgrading your hardware (RAM!), you should seriously consider re-evaluating your workflow. Presumably you were only capturing DV via Firewire and then rendered it out to a “normal” AVI, right? In that case it was more or less a software-only operation, meaning your CPU was doing all the work. This would explain the long render time. That’s especially critical for the final render. Apart from the obvious things like compression to reduce data-rates there’s also a lot extra things going on like colorspace conversion from YUV to RGB that can literally load your CPU until it glows in the dark. Even with hardware support you can’t really avoid this and it won’t do you much good as all editing boards will only provide realtime functionality in there native formats. In away it’s the same in the existing scenario: Had you elected to keep your data as a native DV format and not recompress it, it should have been flying and possibly not taken longer than 5 or 6 hours (it would still take some time to render the effects, but where there is nothing to render, it would be realtime). I would give the matter some serious consideration and re-think, if it was really necessary to create the AVI. Of course this depends on what you were intending to do with it, so you may perhaps elaborate on this a bit.
Mylenium
[Pour Myl
-
Hey Chris, now that it’s official, also a thank you from me for all the work you’ve done for the COW and us other mere mortals. We will miss you and surely yearn for your insight and experience when that nasty thread lurks that just you can answer. Anyway, keep it up and have a great time.
Mylenium
[Pour Myl
-
Hey, thank you everyone. Funny what things happen while one is asleep. About the haircut: It’s not as bad as in the picture anymore and I shall endeavour to send Kathlyn a new pic so she can load it up in place of the old one soon. As an halfway fanatic cyclist I just prefer to have rather short hair, so for quite some time I had the bare minimum of 3mm length.
Mylenium
[Pour Myl
-
Hey, thank you everyone. Funny what things happen while one is asleep. About the haircut: It’s not as bad as in the picture anymore and I shall endeavour to send Kathlyn a new pic so she can load it up in place of the old one soon. As an halfway fanatic cyclist I just prefer to have rather short hair, so for quite some time I had the bare minimum of 3mm length.
Mylenium
[Pour Myl