MPEG Streamclip 1.2 / .mov output not playing on wmp

[B-Twien Bytes]

Hello everybody,

It has been a long time since last visiting this website / forum. It feels good to be back

I've a question for people using MPEG Streamclip 1.2, to get my Avid / Quick Time Reference exported as a .MOV/Quicktime ...
I am getting so confused by all the compression options, that I choose the default one, which is: Apple Motion JPEG A.

So far, so good I was thinking, but not so ... Output file is working well with VLC MediaPlayer, QuickTime Player etc. but not with Windows Media Player. It only gives audio and not video.

Anybody here that could help me out choosing the right 'compression' out of the whole list, so people trying to watch it with WMP could also do that, without getting an error code for missing codecs?

I am grateful for any input on this issue, or link towards good info / website,
Ewien

[Baldrick]

Wmp does not support the mov container. Use mp4 with h264 video and it should work in latesr wmp.

[Cornucopia]

Agree with Baldrick. Also, QT Reference movies don't really work correctly on PCs, so you should always export flattened & self-contained, though if yo are going to go direct to MP4/h264 anyway, the point is moot. Best to avoid MpegStreamClip altogether, if possible.

What platform are you doing this on? Mac? PC? Mix of both?

Scott

[B-Twien Bytes]

Thank you Baldrick and Scott for your clarifications ... Is there another free program like MPEG Streamclip Scott? And why, avoid it if possible?

I did export as h264 btw before posting this message on this forum. Is one of the compressions (.MOV or .MP4) preferable over the other?

Platform used: Linux and/or Windows ... but others I think mainly on PC/Windows.

[Cornucopia]

MOV is a container that can have one or more of a wide variety of compression types & rates. MP4 is also a container (originally based on MOV), but is much more restrictive of what types of compression can be incorporated into it. Because of this restriction, however, it is much more cross-platform and equipment-friendly.

While it still has its uses, MPEGStreamClip hasn't been updated in years, it has known bugs when dealing with DV & MPEG stream types (which haven't been fixed ever, even after having them be brought to their attention), and it is locked into relying on the old QT infrastructure (which is quite deprecated and facing obsolescence, along with many performance & feature bugs). This forum is full of free or cheap tools, many of which are alternatives for MPEGStreamClip.

I think a better way to decide what you need is to see what you have to start with (media content, equipment/apps/devices, budget) and tell us what your intended target is (workflow, audience, equipment/apps/devices) and your priorities, and that can get you a much more straightforward, and almost invariably quality-improved, method with which to achieve your goals.

For example, you mention AVID. Are you using Media Composer? If so, which version and in what capacity?
And, are you sending your h264s to a user's PC to play? a general media player to display on TV? youtube submission?

Scott

[B-Twien Bytes]

Thanks Scott for your thorough reply ... sorry for not answering earlier, I've been swamped with other work

I do use Media Composer, version 8.3 (I believe) ... need to change this on my signature too. Not sure what you mean with capacity.
Most of the times, the end product will be used on either tv, internet / youtube or on the big screen in church or other gatherings.

Will answer more thoroughly when more time ... thanks!

[smrpix]

Withn Mpegstreamclip you can output to h.264, assuming you have QTPro 7 installed on your system. It is horribly slow but works. (For that matter, you can export h.264 mp4s straight out of Avid with the same provisos.)

Avid comes with a free version of Sorenson Squeeze. (Though the latest Lite version has so few output options it's almost useless.) It can read your QT Refs. All of the other decent commercial encoders Adobe Media Encoder, TMPGenc Mastering Works Compressor, etc can handle QT Refs as well.

I've had good luck with ffmpeg front ends like Winff, and feeding it simple Avisynth Scripts such as : QTInput("MyMovie.mov", audio=1