Rogier Chardet
Forum Replies Created
-
In the end I just used After Effects which had no problem handling the Illustrator file in question. The file was single-layered, by the way, so even without additional multi-layer complexity, Motion was failing.
-
yes it did, thanks.
-
Had figured something like that. But in this particular case that presents a new range of issues. I’ve decided to create a more interesting transition in Motion and drop the cross dissolve altogether. Thanks.
-
Both. The file size is 16.9 MB.
-
Alright, thanks.
For some reason, as it turns out, Motion does handle other (smaller) Illustrator files just fine as vectors. Curiously, however, the original file to which my question pertained still does not work. Perhaps there is some kind of glass ceiling in terms of size and complexity.
Anyway, I’m glad there’s no problem with the other files.
-
Thanks for your reply.
But it does not make a difference in this case.
I’m wonder what information should be conveyed in order to isolate the problem? The file is a black and white image (a trace of an image in a PDF file). I’m using Illustrator CS4. For some reason Motion defines the document as a PDF in the media tab – I don’t know if that’s supposed to be…
-
Alright, thank you.
-
I mention ‘NTSC’ because it says so in the Canon manual and because the Adobe Encoder mentions it also (besides ‘progressive’) when encoding the 720p24 HDV file. Don’t know why that is.
Using 720 of 1080 enables a little more flexibility in the presentation of the image without squeezing or stretching. (It’ll be exported as 480, but at least that’s kind of symmetric.) And it allows me to cut out unwanted stuff around the edges (a piece of mic or light).
If I could get that crisp HDV feel with SD I would, but as far as I can tell that’s not possible. So the HDV choice is not so much about the format as it is about the quality of the image. I could be lacking in understanding here, but so far this seems to look best.
Anyway, as for the compression, I am happy to stick with the Adobe Encoder. I quite like it. But I wonder how favorable it rates compared to Compressor or Squeeze? I mean in terms of achieving a lower file size with the same quality? In other words, would I be able to get the same quality for less MBs? Or would there only be a noticeable difference if my footage consisted of fast action transitions?
Thanks.
-
Thanks for your response.
What I’m creating is a one-hour movie to be encoded in the Quicktime H.264 format. It will be available for download from a website and as a DVD-ROM. It consists mostly of talking head footage, captured in HDV (NTSC) on the Canon HV20, 24 fps (1080i), but also files created in After Effects CS4 and Illustrator CS4. The original footage is in 1920×1080, but it is cut down to 1280×720 (which is my sequence setting). The idea is to ultimately export a file that’s 640×480.
I would use Final Cut Pro 6, but PPro has my preference because of the integration with the Suite. Also, as much as I want to like FCP, I just don’t. However, it comes with Compressor, which I would nonetheless prefer to use for compression, rather than having to now invest in Sorenson Squeeze 5. Hence my attempts at finding some workaround that enables the exporting of PPro files for Compressor.
So, it’s not the case that I want to import FCP files into PPro, but rather the opposite – assuming it isn’t possible to create a file for export directly to Compressor.
All of this, of course, is in the assumption that Adobe Media Encoder is inferior to Compressor or Squeeze. I wouldn’t know. I just know that – according to the tutorials in ‘Internet Killed the Videostar’ – it is not recommended to use your video editor for compression.
I’ve tried to export the file in some codec that approximates the native quality (for example HDV 1080p30), but I keep getting the black bars on the side. Perhaps this has to do with square pixels being the only option in the HDV 720p30 sequence setting in PPro?
-
Thank you, good to know.