The main problem when using the QuickTime C APIs is that the majority, if not
all of it, is deprecated and not available on 64-bit code. I would suggest
using the Objective-C QTKit, but apparently Objective-C code is a no-no in Wine.
On Nov 29, 2010, at 10:31 AM, Aric Stewart wrote:
---
That was true of the first set of APIs i used. But I believe the
ICMDecompressionSession APIs are available on 64-bit and not deprecated.
-aric
On 12/2/10 3:46 PM, C.W. Betts wrote:
The main problem when using the QuickTime C APIs is that the majority, if not
all of it, is deprecated and
On 12/2/10 7:06 PM, Aric Stewart wrote:
That was true of the first set of APIs i used. But I believe the
ICMDecompressionSession APIs are available on 64-bit and not deprecated.
chips-computer:/System/Library/Frameworks/QuickTime.framework chip$ nm
-arch x86_64 QuickTime
nm: file: QuickTime
Humm, Yup you are right. I was chatting with Ken Thomases earlier
today and he was talking about QTKit and how it is only Objective-C and
the next step beyond QuickTime. I had not realized that there where no
64 bit versions of the Quicktime framework.
I think we are stuck. Since we are
Aric Stewart a...@codeweavers.com writes:
---
configure |8 +-
configure.ac |5 +
dlls/wineqtdecoder/Makefile.in| 11 +
dlls/wineqtdecoder/main.c | 135 +
dlls/wineqtdecoder/qtvdecoder.c |
On Nov 30, 2010, at 6:52 AM, Alexandre Julliard wrote:
Aric Stewart a...@codeweavers.com writes:
---
configure |8 +-
configure.ac |5 +
dlls/wineqtdecoder/Makefile.in| 11 +
dlls/wineqtdecoder/main.c | 135
Sent a revised patch using the ICMDecompression apis just before seeing
your e-mail. So I figured out that part.
I will have to look into the pixel buffer copying improvement once the
base framework is in place.
thanks!
-aric
On 11/30/10 10:33 AM, Ken Thomases wrote:
On Nov 30, 2010, at
