openquicktime-devel — Developers mailing list for OpenQuicktime

Re: [Openquicktime-devel] Messed CVS + Feature Request

[Alexander L. <ale...@ve...>]

Hi Jozef!


> Von: "Jozef Hatala" <jh...@ho...>
> Datum: Fri, 12 Jul 2002 06:25:34 +0200
> An: ya...@3i..., ope...@li...,
> ale...@ve...
> Betreff: Re: [Openquicktime-devel] Messed CVS + Feature Request
>=20
>> We could implement something like "merits" in Directshow Filters : each
>> codec would register itself whith a dword merit. When encoutering a know=
n
>>  fourcc, the OQT lib would try codecs in order of merit. All the codec
>> given
>> with the OQT lib could have a NORMAL merit, then user wanting to overloa=
d
>> codecs could just register their own codecs with a higher merit ... simp=
le
>> and efficient ;)
>=20
> At registration time, if there is a codec with the same signature there,
> either
> we replace it, or we don't honor the new registration, based on merits.
>=20
> Detail: Low merit codecs should never be in a plugin with their signature=
 in
> the
> file-name, so that all plugins have to be opened, otherwise the "better"
> implementation
> has no chance to show its prooves.  Luckily enoght it's the case for the
> "simple" codecs
> and for decoding-only aliases (like DIV3 and DIV4 in DX50).
>=20
> I was thinking about this. Then I realized that it would be great to have
> different
> merits for the encoder and for the decoder (example: 3ivx decodes DIV4, b=
ut
> you
> would have to use the original codec for DIV4-encoding).
>=20
> But this seems to be difficult to do the way things are now, mainly becau=
se
> when
> a codec is loaded we can't know if it is for reading or for writing.  And
> you can imagine an application that uncompresses a file, transcodes a tra=
ck
> and recompresses it. The codec will be loaded only once.
>=20
> That's why I gave up :-(.
>=20
> But having merits at the plugin level seems interesting though.  I'll try=
 to
> do it.
>

=20
Sounds great.

>>> I agree that deregistering could be good but in this specific case
>>> why do you want new (better?) versions of RLE and RAW ? - why not
>>> just replace the exisiting code - which I'm not sure even works yet
>>> (Jozef?).
>=20
> raw  video (RGB and RGB+alpha) works, as far as I know.  RLE is independe=
nt,
> it can be added without modifying the rest.
>=20

You're right. RGB8 and RGBA8888 do work. Somehow I would opt for a slightly
faster approach, like in qt4linux. It checks if the output rows are
consecutive and then instead of row by row memcpy you can do it with one.
I am not quite sure if this is much faster.
Also, one (who volunteers?) could implement SSE or MMX or whatever memcpy
routines as in mplayer.

I also added an RGBA8888 raw decoder, because sometimes we need this for
compatibility reasons. But I realized that the colormodels stuff from
qt4linux is now in OQT. And now I realized that it is possible to decode
into a different format than supported by the codec! Thanks. Bt as far as I
know this has not been possible until some weeks ago?!

So I added an RLE decoder for RGB888, BGR888, RGBA8888, ARGB8888 based on
the one in Xanim. I think I could send you the code and somebody puts it in
the CVS (if it meets your coding requirements :-)


=20
> If there is something wrong with video codecs, please complain, I care ab=
out
> it.
>=20
...
>=20
> Jozef
>=20
> _________________________________________________________________
> Join the world=B9s largest e-mail service with MSN Hotmail.
> http://www.hotmail.com
>=20

Cheers,

Alex

--=20
Alexander.Lechner     @        vertigo-systems.de
Beethovenstra=DFe 5-13  |    phone: +49-221-2405472
D-50674 K=F6ln          |      fax: +49-221-2722510

Re: [Openquicktime-devel] Messed CVS + Feature Request

[Jozef H. <jh...@ho...>]

>We could implement something like "merits" in Directshow Filters : each
>codec would register itself whith a dword merit. When encoutering a known
>  fourcc, the OQT lib would try codecs in order of merit. All the codec 
>given
>with the OQT lib could have a NORMAL merit, then user wanting to overload
>codecs could just register their own codecs with a higher merit ... simple
>and efficient ;)

At registration time, if there is a codec with the same signature there, 
either
we replace it, or we don't honor the new registration, based on merits.

Detail: Low merit codecs should never be in a plugin with their signature in 
the
file-name, so that all plugins have to be opened, otherwise the "better" 
implementation
has no chance to show its prooves.  Luckily enoght it's the case for the 
"simple" codecs
and for decoding-only aliases (like DIV3 and DIV4 in DX50).

I was thinking about this. Then I realized that it would be great to have 
different
merits for the encoder and for the decoder (example: 3ivx decodes DIV4, but 
you
would have to use the original codec for DIV4-encoding).

But this seems to be difficult to do the way things are now, mainly because 
when
a codec is loaded we can't know if it is for reading or for writing.  And
you can imagine an application that uncompresses a file, transcodes a track
and recompresses it. The codec will be loaded only once.

That's why I gave up :-(.

But having merits at the plugin level seems interesting though.  I'll try to 
do it.

> > I agree that deregistering could be good but in this specific case
> > why do you want new (better?) versions of RLE and RAW ? - why not
> > just replace the exisiting code - which I'm not sure even works yet
> > (Jozef?).

raw  video (RGB and RGB+alpha) works, as far as I know.  RLE is independent,
it can be added without modifying the rest.

If there is something wrong with video codecs, please complain, I care about 
it.

By the way (to bounce the ball back to N), some changes broke the
audio encoding altogether, it only creates 0-sample-long tracks.  I have no 
idea
how the audio part of the lib works, so if some-one could please have a 
look...


Last thing, while we're here, contrary to the comments I think raw access to
compressed data is usefull, for copying or editing for example.  So please
do not remove it like the comments threatten.  N?

> > >Maybe someone could care about this, because OQT is really great!

I agree,

Jozef

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

Re: [Openquicktime-devel] Messed CVS + Feature Request

[Yann <ya...@3i...>]

Hi there,

We could implement something like "merits" in Directshow Filters : each
codec would register itself whith a dword merit. When encoutering a known
 fourcc, the OQT lib would try codecs in order of merit. All the codec given
with the OQT lib could have a NORMAL merit, then user wanting to overload
codecs could just register their own codecs with a higher merit ... simple
and efficient ;)

Comments welcomed,
if nobody against, I could add this ASAP ;)

Yann.

PS : Alexander, if you developped codecs that aren't currently supported in
the lib and want to share your creation, don't hesitate to send us a patch
:)
or we could even discuss about a CVS access ...

----- Original Message -----
From: "Nick Humfrey" <nj...@ae...>
To: <ope...@li...>
Sent: Thursday, July 11, 2002 11:35 PM
Subject: Re: [Openquicktime-devel] Messed CVS + Feature Request


> Hi,
>
> Yes, CVS being messed up is my fault. I got in a bit of a tangle just
> before I left for holiday and commited things I shouldn't have. But
> don't worry I haven't given up! I shall be back and working on OQT -
> almost full time hopefully when I get back from holiday - in a week
> or so.
>
> The main thing I am working on is getting audio sample sizes other
> than 16bit working and hopefully making the API/internal APIs a
> little bit nicer.
>
>
> De-registering is something that I didn't bother doing - I seem to
> remember that there are empty functions where there should be code...
>
> I agree that deregistering could be good but in this specific case
> why do you want new (better?) versions of RLE and RAW ? - why not
> just replace the exisiting code - which I'm not sure even works yet
> (Jozef?).
>
> I will look at updating the Make files to link against
> libopenquicktime when I get back...
>
>
> Cheers,
>
> nick.
>
>
> >The OpenQuicktime CVS seems messed up at the moment. I could't
> >compile it under SUSE 8.0, gcc 2.9x.
> >
> >I had to change "structs.h", because the compiler complained about
> >redefinition of
> >
> >typedef __s8 oqt_int8;
> >typedef __s16 oqt_int16;
> >typedef __s32 oqt_int32;
> >typedef __s64 oqt_int64;
> >typedef __u8 oqt_uint8;
> >typedef __u16 oqt_uint16;
> >typedef __u32 oqt_uint32;
> >typedef __u64 oqt_uint64;
> >
> >Also, in openquicktime.h some function prototypes are not in sync
> >with the code. Maybe someone forgot to commit his changes.
> >
> >Also, I'd like to see a feature for de-registering a codec or at
> >least to override an already registered codec. I developed a RLE and
> >enhanced RAW codec but it has to be loaded before the Simple plugin.
> >Of course I could set the OQT_PLUGIN_DIR to always load my codecs
> >first.
> >
> >Also, the video and audioplugins should be linked with the library
> >(-l openquicktime) again. Otherwise you could get unresolved
> >references if you use openquicktime and codecs in an external
> >application. libopenquicktime should be in the dependency list of
> >the codec, as it was in the old CVS.
> >
> >Maybe someone could care about this, because OQT is really great!
> >
> >Thanks,
> >
> >Alex
> >
> >ale...@ve...
> >
> >
> >
> >-------------------------------------------------------
> >This sf.net email is sponsored by:ThinkGeek
> >PC Mods, Computing goodies, cases & more
> >http://thinkgeek.com/sf
> >_______________________________________________
> >Openquicktime-devel mailing list
> >Ope...@li...
> >https://lists.sourceforge.net/lists/listinfo/openquicktime-devel
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> PC Mods, Computing goodies, cases & more
> http://thinkgeek.com/sf
> _______________________________________________
> Openquicktime-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openquicktime-devel
>

Re: [Openquicktime-devel] Messed CVS + Feature Request

[Nick H. <nj...@ae...>]

Hi,

Yes, CVS being messed up is my fault. I got in a bit of a tangle just 
before I left for holiday and commited things I shouldn't have. But 
don't worry I haven't given up! I shall be back and working on OQT - 
almost full time hopefully when I get back from holiday - in a week 
or so.

The main thing I am working on is getting audio sample sizes other 
than 16bit working and hopefully making the API/internal APIs a 
little bit nicer.


De-registering is something that I didn't bother doing - I seem to 
remember that there are empty functions where there should be code...

I agree that deregistering could be good but in this specific case 
why do you want new (better?) versions of RLE and RAW ? - why not 
just replace the exisiting code - which I'm not sure even works yet 
(Jozef?).

I will look at updating the Make files to link against 
libopenquicktime when I get back...


Cheers,

nick.


>The OpenQuicktime CVS seems messed up at the moment. I could't 
>compile it under SUSE 8.0, gcc 2.9x.
>
>I had to change "structs.h", because the compiler complained about 
>redefinition of
>
>typedef __s8 oqt_int8;
>typedef __s16 oqt_int16;
>typedef __s32 oqt_int32;
>typedef __s64 oqt_int64;
>typedef __u8 oqt_uint8;
>typedef __u16 oqt_uint16;
>typedef __u32 oqt_uint32;
>typedef __u64 oqt_uint64;
>
>Also, in openquicktime.h some function prototypes are not in sync 
>with the code. Maybe someone forgot to commit his changes.
>
>Also, I'd like to see a feature for de-registering a codec or at 
>least to override an already registered codec. I developed a RLE and 
>enhanced RAW codec but it has to be loaded before the Simple plugin. 
>Of course I could set the OQT_PLUGIN_DIR to always load my codecs 
>first.
>
>Also, the video and audioplugins should be linked with the library 
>(-l openquicktime) again. Otherwise you could get unresolved 
>references if you use openquicktime and codecs in an external 
>application. libopenquicktime should be in the dependency list of 
>the codec, as it was in the old CVS.
>
>Maybe someone could care about this, because OQT is really great!
>
>Thanks,
>
>Alex
>
>ale...@ve...
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>PC Mods, Computing goodies, cases & more
>http://thinkgeek.com/sf
>_______________________________________________
>Openquicktime-devel mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openquicktime-devel

[Openquicktime-devel] Messed CVS + Feature Request

[Alexander L. <ale...@ve...>]

Hi All!

The OpenQuicktime CVS seems messed up at the moment. I could't compile 
it under SUSE 8.0, gcc 2.9x.

I had to change "structs.h", because the compiler complained about 
redefinition of

typedef __s8 oqt_int8;
typedef __s16 oqt_int16;
typedef __s32 oqt_int32;
typedef __s64 oqt_int64;
typedef __u8 oqt_uint8;
typedef __u16 oqt_uint16;
typedef __u32 oqt_uint32;
typedef __u64 oqt_uint64;

Also, in openquicktime.h some function prototypes are not in sync with 
the code. Maybe someone forgot to commit his changes.

Also, I'd like to see a feature for de-registering a codec or at least 
to override an already registered codec. I developed a RLE and enhanced 
RAW codec but it has to be loaded before the Simple plugin. Of course I 
could set the OQT_PLUGIN_DIR to always load my codecs first.

Also, the video and audioplugins should be linked with the library (-l 
openquicktime) again. Otherwise you could get unresolved references if 
you use openquicktime and codecs in an external application. 
libopenquicktime should be in the dependency list of the codec, as it 
was in the old CVS.

Maybe someone could care about this, because OQT is really great!

Thanks,

Alex

ale...@ve...

Re: [Openquicktime-devel] Movie Audio Test Files

[Capt. S. *-J. <st...@3i...>]

On Monday, June 3, 2002, at 02:25 AM, Nicholas Humfrey wrote:

> If anyone knows how to encode the missing few, please let me know...

Encode an MP3 with iTunes... both VBR and CBR, open them in QuickTime...=20=

save as movie, self contained...

then you have true VBR MP3 and CBR inside a qt file ;)

I think OQT handles this :)
--
This is only the beginning!

Capt. Stux *-Jedi                                    =
mailto:st...@3i...

3ivx=AA is a registered international trademark. Really.

**** DISCLAIMER ****

"This e-mail and any attachments thereto may contain information which =
is
misleading and/or protected by vain legally positivistic rights and are
supposedly intended for the sole use of the recipient(s) named above. =
Any
use of the information contained herein (including, but not limited to,
reading it by accident, on the loo, or word of mouth in any form) by
persons other than the designated recipient(s) is, um, well, prohibited.
If you have received this e-mail in error, accident, humour, mischievous
bcc, mailing list glitch, recursive bounce of a co-recipient, sendmail
bug, yet another winsock worm, Claire Swire, or the sender just stuffed=20=

up
because your name was next to the proper one in his address book, please
notify the sender either by telephone or by e-mail (yeah we know, as if
you would, but then you'd be amazed, some people) and delete the =
material
from any computer. This means empty your Trash and Recycle Bin, of=20
course.
And zero the data just in case. Do it six times so the feds can't get at
it. Oh, and don't forget your RAM chips; take them out of your computer
for at least a day so the transistors can reset. And for chrissake don't
leave them in your freezer because we read on Slashdot how that can
inhibit the degenerative process. Thank you for your cooperation."

[Openquicktime-devel] Movie Audio Test Files

[Nicholas H. <nj...@ec...>]

I'm still alive - I have exams at the moment so I haven't had much 
time to do stuff...


I have been trying to create and collect some movie test files for 
*all* supported audio codecs in QuickTime. So then I can play 
them/compare them with OQT. They have all been created using 'real' 
QuickTime.

http://surge.soton.ac.uk/~njh/oqt_audio_tests/


A few more to do but I'm getting there. Still to do:

'dvca' - Digital Video Audio
'dvi ' - DVI IMA ADPCM 4:1
'lpc ' - Linear Predictive Coding 23:1
'ms$0002' - Microsoft IMA ADPCM 4:1
'ms$0011' - Intel IMA ADPCM 4:1
'QDMC' - QDesign Music 1

If anyone knows how to encode the missing few, please let me know...



Cheers,

nj.

[Openquicktime-devel] Re: Audio Codecs Added to CVS

[Jozef H. <jh...@ho...>]

>Does this mean we'd have a runtime routine where you can declare your 
>license?

Hello,

I was rather thinking of it as separate projects for different licences.  
The user decides if he/she wants to install plugins from a particular 
project based on the licence.  Projects would be similar to what 
qtcomponents is to qt.

You suggestion would mean that we're having all plugins included in the oqt 
distribution, and user options would enable them at compile/install/run time 
based on theit licence.

We have a plugin mechanism, and once the API is frozen, I think we don't 
have to maintain everything in one place, we can have independent project 
develop plugins with licences they prefere.

Jozef Hatala

--
All power corrupts, but we need electricity.
     -- Anon

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

Re: [Openquicktime-devel] Re: Audio Codecs Added to CVS

[Capt. S. *-J. <st...@3i...>]

On Sunday, April 14, 2002, at 01:25  PM, Yann wrote:

> I wonder ... for example the Gstreamer project is released as LGPL ...=20=

> and
> it has
> lot's of GPL plugins... I think we could do the same and release the
> different
> plugins with their own licence. Then it's up to the final app to=20
> decide : if
> the licence of
> the final app is GPL, then it is allowed to use GPL plugins, if it's
> different, then it's not
> allowed ... What do you think of this ?
>

Does this mean we'd have a runtime routine where you can declare your=20
license?

--
This is only the beginning!

Capt. Stux *-Jedi                                    =
mailto:st...@3i...

3ivx=AA is a registered international trademark. Really.

**** DISCLAIMER ****

"This e-mail and any attachments thereto may contain information which =
is
misleading and/or protected by vain legally positivistic rights and are
supposedly intended for the sole use of the recipient(s) named above. =
Any
use of the information contained herein (including, but not limited to,
reading it by accident, on the loo, or word of mouth in any form) by
persons other than the designated recipient(s) is, um, well, prohibited.
If you have received this e-mail in error, accident, humour, mischievous
bcc, mailing list glitch, recursive bounce of a co-recipient, sendmail
bug, yet another winsock worm, Claire Swire, or the sender just stuffed=20=

up
because your name was next to the proper one in his address book, please
notify the sender either by telephone or by e-mail (yeah we know, as if
you would, but then you'd be amazed, some people) and delete the =
material
from any computer. This means empty your Trash and Recycle Bin, of=20
course.
And zero the data just in case. Do it six times so the feds can't get at
it. Oh, and don't forget your RAM chips; take them out of your computer
for at least a day so the transistors can reset. And for chrissake don't
leave them in your freezer because we read on Slashdot how that can
inhibit the degenerative process. Thank you for your cooperation."

Re: [Openquicktime-devel] Re: Audio Codecs Added to CVS

[Yann <ya...@3i...>]

I wonder ... for example the Gstreamer project is released as LGPL ... and
it has
lot's of GPL plugins... I think we could do the same and release the
different
plugins with their own licence. Then it's up to the final app to decide : if
the licence of
the final app is GPL, then it is allowed to use GPL plugins, if it's
different, then it's not
allowed ... What do you think of this ?

Yann.

> >Another thought it maybe we should have a separate project under GPL
> >(rather than LGPL) that we can create plugins in so we can use GPLed
> >source code - ffmpeg etc... ?
>
> This might be a good idea.  There will be lgpl'ed, gpl'ed as well as
> commercial plugins for oqt.

[Openquicktime-devel] Re: Audio Codecs Added to CVS

[Nicholas H. <nj...@ec...>]

>endianess problem: on i386-linux, twos should do byte swapping and 
>sowt should not.

I put put a fix for this in CVS - hopefully it will work... there are 
a few other endian bugs around the place... I don't think 
oqtextractaudio works on little endian - and there is a problem with 
the encoder on Big Endian...

Also added 'alaw' and 'agsm' audio codecs. Real Quicktime can't even 
encode GSM 06.10... ;-)  I have managed to stream live audio using 
it. Not very useful for anything apart from speech. Almost got all 
the audio codecs done this weekend :)

I have been looking at the Ogg Vorbis codec. 
http://qtcomponents.sourceforge.net/ do a plugin to let you use Ogg 
Vorbis in real quicktime - I was looking at the headers in the Sound 
Samples Description - and they are doing something quite odd - a very 
long header... might take a bit more work than I thought. Oh well it 
is open source at least...

I think encoding is still broken - something odd happened to the 
oqt_encode_audio function ;-) and it is generating the 
Sample/Chunk/Offset tables correctly...

Also I think the arguments for the oqt_encode_audio function should 
be changed so that it takes interleaved 16-bit samples as its input - 
rather than array of channels... there is code on both sides for the 
call that converts between the two formats :)

Unfortunately I have a report (thesis) to write now - so there will 
be less check-ins to CVS for a bit...


nj.
-- 
Nicholas Humfrey

Undergraduate, BSc Computer Science
University of Southampton, UK
nj...@ec...
http://www.ecs.soton.ac.uk/~njh399/

[Openquicktime-devel] Re: Audio Codecs Added to CVS

[Jozef H. <jh...@ho...>]

>I have just added support for 'twos', 'sowt', 'ulaw' and 'ima4' to

Hi,

endianess problem: on i386-linux, twos should do byte swapping and sowt 
should not.
How about registering twos as sowt and sowt as twos on little-endian 
machines?

>Another thought it maybe we should have a separate project under GPL
>(rather than LGPL) that we can create plugins in so we can use GPLed
>source code - ffmpeg etc... ?

This might be a good idea.  There will be lgpl'ed, gpl'ed as well as 
commercial plugins for oqt.

Yours,

jh

--
"Go to Heaven for the climate, Hell for the company."
	-- Mark Twain


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.

[Openquicktime-devel] Audio Codecs Added to CVS

[Nicholas H. <nj...@ec...>]

I have just added support for 'twos', 'sowt', 'ulaw' and 'ima4' to 
CVS. They are all part of the new "Simple Audio" plugin.
I would have done 'raw ' as well but I don't have any movies encoded 
using raw and Quicktime 5 won't generate them. If you have a movie 
with raw encoding can you send it to me please.... ?

I have successfully streamed live audio with my broadcasting 
application "OQT Broadcaster". I have had it working with both the 
IMA4 and MP3 codecs... There should be a public release coming soon - 
and hopefully a stream for you to tune into: 
http://www.surgeradio.co.uk.


The following audio codecs could be supported. If you have any 
information/specs/LGPLed code for encoding/decoding them please let 
me know:

'alaw' A-Law 2:1
'MAC3' MAC 3:1 - 8-bit Only
'MAC3' MAC 6:1 - 8-bit Only
'dvi ' DVI IMA ADPCM 4:1
'dvca' Digital Video Audio
'lpc ' Linear Predictive Coding 23:1 (for voice)
'agsm' Apple GSM 10:1 (Actually just GSM 6.10)
+ Microsoft variations

These codecs could be supported fairly easily as well but I don't 
know if there is any point... ? As they are all higer quality than 
the format that OQT uses internally... ?

in24	24-bit Integer PCM
fl32	32-bit Floating Point PCM
in32	32-bit Integer PCM
fl64	64-bit Floating Point PCM



Another thought it maybe we should have a separate project under GPL 
(rather than LGPL) that we can create plugins in so we can use GPLed 
source code - ffmpeg etc... ?



-- 
Nicholas Humfrey

Undergraduate, BSc Computer Science
University of Southampton, UK
nj...@ec...
http://www.ecs.soton.ac.uk/~njh399/

[Openquicktime-devel] web site updated

[Yann <ya...@3i...>]

All is in the title ;)

Yann.

[Openquicktime-devel] OpenQT Forum

[Capt. S. *-J. <st...@3i...>]

The OpenQuickTime forum is once again available at =
http://forums.3ivx.com

sorry for the ... outage :)

--
This is only the beginning!

Capt. Stux *-Jedi                                    =
mailto:st...@3i...

3ivx=AA is a registered international trademark. Really.

**** DISCLAIMER ****

"This e-mail and any attachments thereto may contain information which =
is
misleading and/or protected by vain legally positivistic rights and are
supposedly intended for the sole use of the recipient(s) named above. =
Any
use of the information contained herein (including, but not limited to,
reading it by accident, on the loo, or word of mouth in any form) by
persons other than the designated recipient(s) is, um, well, prohibited.
If you have received this e-mail in error, accident, humour, mischievous
bcc, mailing list glitch, recursive bounce of a co-recipient, sendmail
bug, yet another winsock worm, Claire Swire, or the sender just stuffed=20=

up
because your name was next to the proper one in his address book, please
notify the sender either by telephone or by e-mail (yeah we know, as if
you would, but then you'd be amazed, some people) and delete the =
material
from any computer. This means empty your Trash and Recycle Bin, of=20
course.
And zero the data just in case. Do it six times so the feds can't get at
it. Oh, and don't forget your RAM chips; take them out of your computer
for at least a day so the transistors can reset. And for chrissake don't
leave them in your freezer because we read on Slashdot how that can
inhibit the degenerative process. Thank you for your cooperation."

Re: [Openquicktime-devel] HeaderDoc, API and oqtaudioextract

[Nicholas H. <nj...@ec...>]

Hi Yann,

I have tarziped the docs here:
http://lotto.st-andrews.ac.uk/~njh/openquicktime-docs.tgz
But here is how to generate them:

njh@lotto$ cd include/openquicktime/
njh@lotto$ headerdoc2html openquicktime.h

Processing openquicktime.h
...done


Documentation ends up in a directory called 'openquicktime' within 
the current directory.

More about HeaderDoc here:
http://www.opensource.apple.com/projects/headerdoc/


Cheers,

nj.



>OK, send me your documentation or explain me the syntax to generate it ;)
>and I will put it on the website ... and I think I will spend some time
>actualizing it as well ... hehehe ... it's really needed ;)
>
>Yann.
>
>----- Original Message -----
>From: "Nicholas Humfrey" <nj...@ec...>
>To: <ope...@li...>
>Sent: Sunday, April 07, 2002 1:12 AM
>Subject: [Openquicktime-devel] HeaderDoc, API and oqtaudioextract
>
>
>>
>>  Hello All,
>>
>>  I have finished doing HeaderDoc comments for the whole of the OQT
>>  public API (74 functions in total). The structures still need
>>  commenting some time... (less important I think). One of the main
>>  reasons I did it was because I kept wanting to refer to documentation
>>  myself and it helped me learn what is there...
>>  Should it go on the main website sometime Yann ?
>>
>>  While I was doing this I did a bit more standardization - in
>>  particular oqt_get_audio_XXX, oqt_set_audio_XXX etc...
>>  Oh and in case you didn't notice I renamed everything starting
>>  quicktime_ oqt_ - I think it makes it more clear that this is the
>>  OpenQuicktime API not a clone of QuickTime - and it is shorter :)
>>
>>  Oh and I wrote a little utility to decode the audio track from a
>>  movie and save it to .aiff. If anyone wants something else (.wav)
>>  then they will have to add it themselves - hehe :)
>>  I think that we should maybe include libsndfile into the project
>>  properly sometime (it is LGPL). Maybe just staticly linked to
>>  oqtencoder so that it can take in multiple audio formats... ?
>>
>>
>>  I had more of a play with 3ivX today - looking good guys :)
>>
>>
>>  nj.
>>
>>  _______________________________________________
>>  Openquicktime-devel mailing list
>>  Ope...@li...
>>  https://lists.sourceforge.net/lists/listinfo/openquicktime-devel
>>
>
>
>_______________________________________________
>Openquicktime-devel mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openquicktime-devel


-- 
Nicholas Humfrey

Undergraduate, BSc Computer Science
University of Southampton, UK
nj...@ec...
http://www.ecs.soton.ac.uk/~njh399/

Re: [Openquicktime-devel] HeaderDoc, API and oqtaudioextract

[Yann <ya...@3i...>]

OK, send me your documentation or explain me the syntax to generate it ;)
and I will put it on the website ... and I think I will spend some time
actualizing it as well ... hehehe ... it's really needed ;)

Yann.

----- Original Message -----
From: "Nicholas Humfrey" <nj...@ec...>
To: <ope...@li...>
Sent: Sunday, April 07, 2002 1:12 AM
Subject: [Openquicktime-devel] HeaderDoc, API and oqtaudioextract


>
> Hello All,
>
> I have finished doing HeaderDoc comments for the whole of the OQT
> public API (74 functions in total). The structures still need
> commenting some time... (less important I think). One of the main
> reasons I did it was because I kept wanting to refer to documentation
> myself and it helped me learn what is there...
> Should it go on the main website sometime Yann ?
>
> While I was doing this I did a bit more standardization - in
> particular oqt_get_audio_XXX, oqt_set_audio_XXX etc...
> Oh and in case you didn't notice I renamed everything starting
> quicktime_ oqt_ - I think it makes it more clear that this is the
> OpenQuicktime API not a clone of QuickTime - and it is shorter :)
>
> Oh and I wrote a little utility to decode the audio track from a
> movie and save it to .aiff. If anyone wants something else (.wav)
> then they will have to add it themselves - hehe :)
> I think that we should maybe include libsndfile into the project
> properly sometime (it is LGPL). Maybe just staticly linked to
> oqtencoder so that it can take in multiple audio formats... ?
>
>
> I had more of a play with 3ivX today - looking good guys :)
>
>
> nj.
>
> _______________________________________________
> Openquicktime-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openquicktime-devel
>

Re: [Openquicktime-devel] HeaderDoc, API and oqtaudioextract

[Capt. S. *-J. <st...@3i...>]

On Sunday, April 7, 2002, at 01:12  AM, Nicholas Humfrey wrote:

> I have finished doing HeaderDoc comments for the whole of the OQT=20
> public API (74 functions in total). The structures still need=20
> commenting some time... (less important I think). One of the main=20
> reasons I did it was because I kept wanting to refer to documentation=20=

> myself and it helped me learn what is there...
> Should it go on the main website sometime Yann ?

I'm sure it should :))

>
> While I was doing this I did a bit more standardization - in =
particular=20
> oqt_get_audio_XXX, oqt_set_audio_XXX etc...
> Oh and in case you didn't notice I renamed everything starting=20
> quicktime_ oqt_ - I think it makes it more clear that this is the=20
> OpenQuicktime API not a clone of QuickTime - and it is shorter :)
>

Sounds good to me :)

>
> I had more of a play with 3ivX today - looking good guys :)

Thanks Nick :)

--
This is only the beginning!

Capt. Stux *-Jedi                                    =
mailto:st...@3i...

3ivx=AA is a registered international trademark. Really.

**** DISCLAIMER ****

"This e-mail and any attachments thereto may contain information which =
is
misleading and/or protected by vain legally positivistic rights and are
supposedly intended for the sole use of the recipient(s) named above. =
Any
use of the information contained herein (including, but not limited to,
reading it by accident, on the loo, or word of mouth in any form) by
persons other than the designated recipient(s) is, um, well, prohibited.
If you have received this e-mail in error, accident, humour, mischievous
bcc, mailing list glitch, recursive bounce of a co-recipient, sendmail
bug, yet another winsock worm, Claire Swire, or the sender just stuffed=20=

up
because your name was next to the proper one in his address book, please
notify the sender either by telephone or by e-mail (yeah we know, as if
you would, but then you'd be amazed, some people) and delete the =
material
from any computer. This means empty your Trash and Recycle Bin, of=20
course.
And zero the data just in case. Do it six times so the feds can't get at
it. Oh, and don't forget your RAM chips; take them out of your computer
for at least a day so the transistors can reset. And for chrissake don't
leave them in your freezer because we read on Slashdot how that can
inhibit the degenerative process. Thank you for your cooperation."

[Openquicktime-devel] HeaderDoc, API and oqtaudioextract

[Nicholas H. <nj...@ec...>]

Hello All,

I have finished doing HeaderDoc comments for the whole of the OQT 
public API (74 functions in total). The structures still need 
commenting some time... (less important I think). One of the main 
reasons I did it was because I kept wanting to refer to documentation 
myself and it helped me learn what is there...
Should it go on the main website sometime Yann ?

While I was doing this I did a bit more standardization - in 
particular oqt_get_audio_XXX, oqt_set_audio_XXX etc...
Oh and in case you didn't notice I renamed everything starting 
quicktime_ oqt_ - I think it makes it more clear that this is the 
OpenQuicktime API not a clone of QuickTime - and it is shorter :)

Oh and I wrote a little utility to decode the audio track from a 
movie and save it to .aiff. If anyone wants something else (.wav) 
then they will have to add it themselves - hehe :)
I think that we should maybe include libsndfile into the project 
properly sometime (it is LGPL). Maybe just staticly linked to 
oqtencoder so that it can take in multiple audio formats... ?


I had more of a play with 3ivX today - looking good guys :)


nj.

Re: [Openquicktime-devel] HeaderDoc

[Capt. S. *-J. <st...@3i...>]

On Friday, April 5, 2002, at 06:22  PM, Capt. Stux *-Jedi wrote:

>
> BTW, I looked at your website, cool too, I remember writing something=20=

> called HyperTurtle in HyperCard in about... 1996, looked very=20
> similar... cool :)

Actually, it was 1991 :)

My time flies :)

--
This is only the beginning!

Capt. Stux *-Jedi                                    =
mailto:st...@3i...

3ivx=AA is a registered international trademark. Really.

**** DISCLAIMER ****

"This e-mail and any attachments thereto may contain information which =
is
misleading and/or protected by vain legally positivistic rights and are
supposedly intended for the sole use of the recipient(s) named above. =
Any
use of the information contained herein (including, but not limited to,
reading it by accident, on the loo, or word of mouth in any form) by
persons other than the designated recipient(s) is, um, well, prohibited.
If you have received this e-mail in error, accident, humour, mischievous
bcc, mailing list glitch, recursive bounce of a co-recipient, sendmail
bug, yet another winsock worm, Claire Swire, or the sender just stuffed=20=

up
because your name was next to the proper one in his address book, please
notify the sender either by telephone or by e-mail (yeah we know, as if
you would, but then you'd be amazed, some people) and delete the =
material
from any computer. This means empty your Trash and Recycle Bin, of=20
course.
And zero the data just in case. Do it six times so the feds can't get at
it. Oh, and don't forget your RAM chips; take them out of your computer
for at least a day so the transistors can reset. And for chrissake don't
leave them in your freezer because we read on Slashdot how that can
inhibit the degenerative process. Thank you for your cooperation."

Re: [Openquicktime-devel] HeaderDoc

[Capt. S. *-J. <st...@3i...>]

On Friday, April 5, 2002, at 11:53  AM, Nicholas Humfrey wrote:

> I have made a start at documenting the OpenQuicktime API:
> http://lotto.st-andrews.ac.uk/~njh/openquicktime/
>
> Not much there so far :)
>
> HeaderDoc is like JavaDoc but for C style languages.
> I think it makes sense having the documentation embeded into the =
header=20
> files - and it generates nice HTML for us...
> There are other (GPL) implementations that can parse the same =
headers...

Tis Cool :)

BTW, I looked at your website, cool too, I remember writing something=20
called HyperTurtle in HyperCard in about... 1996, looked very similar...=20=

cool :)

--
This is only the beginning!

Capt. Stux *-Jedi                                    =
mailto:st...@3i...

3ivx=AA is a registered international trademark. Really.

**** DISCLAIMER ****

"This e-mail and any attachments thereto may contain information which =
is
misleading and/or protected by vain legally positivistic rights and are
supposedly intended for the sole use of the recipient(s) named above. =
Any
use of the information contained herein (including, but not limited to,
reading it by accident, on the loo, or word of mouth in any form) by
persons other than the designated recipient(s) is, um, well, prohibited.
If you have received this e-mail in error, accident, humour, mischievous
bcc, mailing list glitch, recursive bounce of a co-recipient, sendmail
bug, yet another winsock worm, Claire Swire, or the sender just stuffed=20=

up
because your name was next to the proper one in his address book, please
notify the sender either by telephone or by e-mail (yeah we know, as if
you would, but then you'd be amazed, some people) and delete the =
material
from any computer. This means empty your Trash and Recycle Bin, of=20
course.
And zero the data just in case. Do it six times so the feds can't get at
it. Oh, and don't forget your RAM chips; take them out of your computer
for at least a day so the transistors can reset. And for chrissake don't
leave them in your freezer because we read on Slashdot how that can
inhibit the degenerative process. Thank you for your cooperation."

[Openquicktime-devel] HeaderDoc

[Nicholas H. <nj...@ec...>]

I have made a start at documenting the OpenQuicktime API:
http://lotto.st-andrews.ac.uk/~njh/openquicktime/

Not much there so far :)

HeaderDoc is like JavaDoc but for C style languages.
I think it makes sense having the documentation embeded into the 
header files - and it generates nice HTML for us...
There are other (GPL) implementations that can parse the same headers...

If anyone want to do a bit of documenting, please do :)


nj.

Re: [Openquicktime-devel] Makefiles in CVS

[Yann <ya...@3i...>]

I aggree, basically, the CVS version doesn't need any of this one, only the
ones needed to build the second are required ... the CVS version is not
intend for final users ... at all ;)

Yann.

----- Original Message -----
From: "Nicholas Humfrey" <nj...@ec...>
To: <ope...@li...>
Sent: Tuesday, April 02, 2002 2:52 AM
Subject: [Openquicktime-devel] Makefiles in CVS


>
> Which Makefiles should be in CVS ?
>
> It seems silly to put new versions of Makefile.in, configure etc. in
> CVS every time someone runs ./bootstrap...
>
> Is it reasonable to expect all oqt developers to have autoconf,
> automake etc. installed ? in order to build from CVS ?
>
>
> Cheers,
>
>
> nj.
>
>
> _______________________________________________
> Openquicktime-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openquicktime-devel
>

[Openquicktime-devel] Makefiles in CVS

[Nicholas H. <nj...@ec...>]

Which Makefiles should be in CVS ?

It seems silly to put new versions of Makefile.in, configure etc. in 
CVS every time someone runs ./bootstrap...

Is it reasonable to expect all oqt developers to have autoconf, 
automake etc. installed ? in order to build from CVS ?


Cheers,


nj.

[Openquicktime-devel] Re: interested in CVS access for OpenQuicktime

[Yann <ya...@3i...>]

Hi Joseph,

I just looked at your work and it seems very good (I can't tested it for the
moment though)...
As you maybe know, 4 of the 5 current developpers of OQT are also member of
3ivx, and because a (kickass) new version of our codec will be
released very soon, we have no time to work on OQT for the moment . Anyway,
Nicholas, the fifth guy ;),  is doing an awesome job with all its new
features and re-organization of the lib. As far as I know, he was planning
to create a Vorbis plugin and maybe an IMA4 codec for OQT ...

I must admit that I wasn't planning to create an OpenDivX codec for OQT
myself ... ;) ...but I don't see any objections to add it to our CVS....
We are all aggree to say that OQT as it is now is great but it still clearly
lacks codecs. So, I will really be pleased to give you CVS acces :)
Just give me a few minutes ;)

Welcome :)

Yann.

PS: no test needed, just put your great work into the CVS yourself ;)

----- Original Message -----
From: "Jozef Hatala" <jh...@ho...>
To: <ya...@3i...>
Sent: Tuesday, March 26, 2002 7:59 AM
Subject: interested in CVS access for OpenQuicktime


> Hello Yann,
>
> The mailing list archive says that somebody has delt with RAW and
> TWOS codecs but this effort doesn't seem to have made it into cvs.
> What codecs are people currently working on?
>
> There I submitted on sourceforge a simple patch to oqtencoder that
> makes it accept audio from a WAV (login: jhatala).  I thought about
> porting codecs: RAW a/v, TWOS and RTJ0 (might be cool for video capture).
> For now I ported the slow DIVX implementation from qt4l for comparison,
> although I know you're not exessively fond of this idea...
>
> So are there some simple ports no-one is dealing with?  Could I get a
> write access to CVS, or are there tests I have to go through first ;-?
>
> Yours,
>
> jh
>