around the 9/9/05 toekneearm mentioned about [videoblogging] Re:
MPEG-4 settings that:
FYI QuickTime is not a compression format but rather a container
for compression algorithms. MPEG-4 is just one of the many
compression formats QT
accommodates. Ben Waggoner has written an excellent book about
FWIW - I just finished encoding another long 52.5 minute
presentation. Used a new Panther 10.3.9 + QT 6.5.2 + 3ivx 4.5.1 Dual
Pass setup with FCP 4.5 from Canon XL-1 DV source. The image quality
is great even in QT 6.5.2.
When I used 5 fps the file size came out to 116.6 MB which I decided
You're feedburner feed at http://feeds.feedburner.com/FutureMedia says:
This publisher's original feed was not available so FeedBurner cannot
present their content at this time.
...
HTTP Error Code: 500
Detail: There was a problem retrieving the feed: Error getting URL:
502 -
If I go to your feedburner feed in a browser, I get an fee
dunavailable error:
'HTTP Error Code: 500
Detail: There was a problem retrieving the feed: Error getting URL:
502 - Source feed is too large'
I dont know much about feeedburner, maybe it has a maximum size of
page it will parse, and you
OK I decided to test some other encoding methods at 1fps.
I tried photo jpeg and mjpeg-A codecs. With footage at 1fps, they do
get much much closer to mpeg4 filesizes than is normally the case, so
my theory was roughyl correct. But they are still a bit bigger than
your mpeg4 file, so I dont
It was bogus HTML generated by the Compose part of Firefox's
interface with Blogger. The bugger had an infinite number of fake
font and span tags all over it. I fixed it. And now all my vids
no longer download without a click and they all open in QuickTime
Player now. Finally figured out
--- In videoblogging@yahoogroups.com, JD Lasica [EMAIL PROTECTED] wrote:
Today I spent a little while experimenting with MPEG-4 settings.
Because some people prefer MPEG4 to QuickTime
FYI QuickTime is not a compression format but rather a container
for compression algorithms. MPEG-4 is just
Im delighted to hear you are planning a knowledgebase, because these
encoding issues get complex and theres plenty to say on the subject. I
reckon on average I spend at least a few hours every week talking
about various encoding issues, usually in response to specific questions.
Ive never tried
