cocoaforge

I love how people here are trying to say what is easy and what is not when they understand very little about how codecs really work in the QuickTime architecture. If you think it is so easy, then do it yourself and they you will discover that your claims are wildly inaccurate. It is far, far easier ...

For the fourth time: this is not the responsibility of a codec and thus is not the responsibility of Perian. This is solely and completely the responsibility of the browser.

Hmmm... I now have to ask if this truly works at all. I was using handbrake last night, and I ripped with the DTS passthrough to M4V. Nothing I could find would detect that the track was present, not even mkvmerge saw it. I have to question now whether handbrake is actually putting the track in there.

I was referring to the ISO standard when I said illegal; I stand corrected. M4V opening is significantly more complex than other formats due to the fact that Apple's importer provides such good support. In order to replace it, Perian's would have to support every single feature that Apple's supporte...

M4V files are opened by Apple's components. IIRC, DTS is illegal in M4V/MP4 and that is why handbrake didn't allow it.

I believe that somewhere in the 1.2s we increased the number of libraries against which we link. Try running otool (-L I think) to see which libraries it uses (I'm not on a Mac ATM, so I can't run it here).

Honestly, this issue is not related to Perian other than the fact that your dyld is having issues with that binary. You likely have a corrupt file located somewhere in your system.

Yes. While the new Xcode is still a terrible POS, it does compile Perian.

http://trac.perian.org/changeset/1500

It doesn't seem to work with the compress one. I wonder if ffmpeg doesn't support it.

We really need a sample to diagnose further.

This site is English only.

As best I can tell, you are asking about Perian for Windows, which has been answered already.

Patches welcome.

drdoom567 wrote:i have read through this thread.

Then I shouldn't have to repeat myself. For the third time, this is not the responsibility of a codec and thus is not the responsibility of Perian.

If it doesn't decode without Perian, then Perian's doing the decoding and Apple's refuses to do decoding, so the DecodeAllProfiles means nothing.

Are you sure that Perian's doing the decode? By default, most, if not all, H.264 decoding is being done by Apple's codec. You may want to try setting/unsetting the DecodeAllProfiles preference. I'm not aware that H.264 can be made lossless. I thought some of the transforms used where inherently loss...

That may be. None of the developers have access to Compressor, but I remember seeing reports of video being at too high a framerate in Compressor on interlaced content. Not sure what the best course of action would be.

could you tell me how you "see" the file being screwed up? In the debugger, I examined the samples being sent to the codec. I would like to push the information back out in the right places so folks, if they continue to use .avi will at least correct their screwed up packetization. It's t...

Same lousy packetization as in http://forums.cocoaforge.com/viewtopic.php?f=25&t=24052 I wish people would stop using this lousy file format. Remux it using avidemux or similar tool to fixed the broken file.

Perian has issues with interlaced content, partially because it's not easy in ffmpeg. Anyway, that's the source of the problem you are experiencing. Can compressor read MPEG2 video without Perian?

Is the MPEG2 Video interlaced?