What about the QT6/scaling issue? (was Re: [theora-codecs] Callfor bugs and suggestions)
Mauricio Piacentini
mauricio at xiph.org
Tue Apr 29 13:27:10 PDT 2003
I agree with everything you said, Dan. I have finished compiling a clean
version from the current sources, they only need some tweaking to build
resources correctly on OSX. Building the QT codec on Windows also requires a
small tweaking to reflect the location of some resource files (from QTSDK)
that is not covered in the build steps, but it is an easy one. I will update
the build instructions, and submit an archive with the sources and projects
I used.
The remaining issue is an installer: I was thinking about a simpler
installer that only creates the relevant codec registry keys on Windows, and
put the files at the correct places on the Mac. This will make it easier for
people to continue redistributing the codecs.
When this is done (after the weekend) I will post a link to the final
binaries and source packages to the list, hopefully Emmet will be able to
put them somewhere at xiph.org for download, and we can move on.
Regards,
Mauricio Piacentini
Tabuleiro
----- Original Message -----
From: "dan miller" <danbmil99 at yahoo.com>
To: <theora-codecs at xiph.org>
Sent: Tuesday, April 29, 2003 2:32 PM
Subject: Re: What about the QT6/scaling issue? (was Re: [theora-codecs]
Callfor bugs and suggestions)
<p>> My apologies for being so late to this thread. As some of you may know, I
am no longer at On2.
> However I still plan to work actively on Theora, and I believe that
keeping the legacy VP3 codecs
> working is important for Xiph as well. If nothing else, all these thorny
issues of build
> environments and platform inconsistancies will rear their ugly heads
if/when we get to the point
> of building Theora-native QT codecs.
>
> To run down the major points brought up on this thread:
>
> * Compiler problems and legacy support -- My suggestion would be to do a
final, latest & greatest
> build using the present crazy toolchain (CW 5, CW7, etc), and get these
binaries & archived
> sources up somewhere on Xiph/theora. Talk to Jack or whomever about
setting up a download page
> for this. I will convince the On2 guys to link to it since they are
clearly not committed to
> keeping their site up-to-date. Going forward we concentrate on new
platforms (See below)
>
> * Performance problems - known issues at Apple. As someone suggested,
they are not too committed
> to 3rd party codecs anymore. We're on our own more or less, though I have
found an engineer or
> two at Apple over the years who cares about this sort of thing. We (at
On2) made some changes
> according to their suggestions, which are reflected in the 3.2.6.x
releases. Obviously this is
> improving the Windows situation. I am not as familiar with Mac issues,
someone will have to
> research it further.
>
> * Platform issues -- my suggestion: lock down the old stuff & move on.
Future development should
> be OSX/QT6 (and Win/QT6) only. Apple does such a terrible job of
supporting their own API's that
> it is not feasible within our resources to try to keep backwards
compatibility. Keep the old
> stuff around on a page as mentioned, and make sure it's clear to newbies
what to download for
> their setup.
>
> * Assembly code -- now that we're only concentrating on QT6 and OSX, we
should standardize on the
> newest & most popular dev systems (Apple/GCC on Mac, VC7 on Windows). Get
clean builds going and
> the assembly shouldn't be too much of a headache. The optimizations are
done; however someone
> needs to port them to the present toolchain.
>
> These are my thoughts as of now - dan
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'theora-codecs-request at xiph.org'
containing only the word 'unsubscribe' in the body. No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.
More information about the Theora-codecs
mailing list