Re: AudioFileOpen
Re: AudioFileOpen
- Subject: Re: AudioFileOpen
- From: William Stewart <email@hidden>
- Date: Mon, 7 Nov 2005 16:15:05 -0800
Points taken, but I would really encourage you to file bugs just as a
general approach.
As for the copyright notices - the notices on the files are the
standard SDK license - if you are concerned about the terms of this
license, you should get a legal opinion. You will never see anything
from any company these days without some kind of legal notice...
I can certainly sympathise with your points and I am raising the
issue internally.
Thanks for your comments, I appreciate your candour.
Bill
On 07/11/2005, at 2:41 PM, Bob Lang wrote:
Hi Bill
Java's run anywhere philosophy only works when the implementation
provides a suitable level of support. Java Sound support is
inadequate for the Mac implementation, and we require the com.apple
classes to fill in the gaps. We're doing this to support the "run
anywhere" philosophy - not subvert it ;-) We're also giving free
support and development to Mac OS X and getting little or no
recognition from Apple for it. I suppose no good deed ever goes
unpunished.
I filed bug number 3202451 on 19th March 2003 (two and a half
years ago!) concerning the inability of Java Sound on Macs to
access Midi devices. It seems to have remained open all that
time. Makes bug filing look like a pretty pointless activity.
Unfortunately, the java-dev mailing list is inhabited by trolls and
I have no intention of subscribing to that particular list again :-
( There has been a fair amount of criticism of Apple's
implementation of Java Sound on the Java Sound discussion list
(email@hidden)
The com.apple SDK may well be open source, but i think it still has
Apple's copyright notices. I would certainly consider taking over
its maintenance if I could be certain that a few years down the
line, Apple weren't going to sue me for infringing their copyright.
Sorry if these last couple of mails have turned into mega-moans,
but there's two or more years of frustration to get of my
chest ;-) And perhaps you realise now that all is not well in the
world of Mac Java...
Cheers
Bob
--
On 7 Nov 2005, at 18:29, William Stewart wrote:
Sure.
Very few developers were using it that we could ascertain. The
time involved for us to continue to maintain and develop this just
didn't seem to be worth it. To offset any difficulties for
companies that were using it, it seemed like a good solution to
just provide the source in the SDK as a starting point.
It is also in a somewhat ambiguous situation with Java's general
run-anywhere philosophy, as these classes would only work on X. I
can certainly see your point about the poor support for javax.*
frameworks and I'll make sure I forward your comments to the Java
Dev team here. It seems to me that the real problem you are facing
is exactly this. Please make your opinions known on the java-dev
list, and I would also advise you to file bug reports
(bugreporter.apple.com) - it always carries weight that developers
are prepared to document their concerns and problems.
Thanks
Bill
On 05/11/2005, at 3:11 PM, Bob Lang wrote:
Hi Bill
Can you shed any light on the decision not to support the CA Java
API? This decision seems short-sighted to me as it closes off
the avenue which allows SPI extensions to the Java language.
This is particularly important given Apple's pathetic
implementation of pure Java Sound. For example, Apple's
implementation of javax.sound.midi does not support Midi input/
output from midi devices - an astonishing, outrageous and
completely indefensible omission. However, by leveraging Core
Midi via the CAJava API I was able to fill in this gap with
"Plumstone", which allows pure Java programs to access MIDI I/O
devices. This was made possible only by accessing the CAJava API
- now deprecated!
Going further, the current pure Java audio output implementation
on Macs has a terrible latency problem, especially when compared
with the newest implementation on XP, and I know that Sam's final
intention is to create a replacement output "mixer" for Macs;
however, Apple really doesn't make it easy to bring "the best
Java on the planet" (we all know who said that!) so that it
matches the audio performance of XP.
Making the API open source might seem like a good idea, but it's
imposing a gigantic learning curve on whoever tries to extend
it. A tiny number of external developers (like Sam and myself)
are trying to bring Apple's Java audio up to scratch so that it
can compete with XP, but Apple is not helping us at all - in
fact, it's putting obstacles in the way.
Bottom line - I love Macs but I'm committed to Java Sound. My
iBook is nearing the end of useful life and I'm facing the
decision on whether to upgrade to a new iBook, or buy a cheaper
XP laptop that will handle Java Sound better! What a dilemma.
Bob Lang
--
On 4 Nov 2005, at 23:16, William Stewart wrote:
we're no longer maintaining the CAJava API. The code for it is
in the 1.3.X core audio SDK's (developer.apple.com/audio) - you
can add code to interface to the AudioFile API..
In general though, I would be more inclined to use the Java
languages and libraries (java. and javax.) - there is a java-dev
list hosted at lists.apple.com for developers using Java on the
Mac - aside of course from the many lists, books, etc that are
around for general java development.
Bill
On 04/11/2005, at 12:30 PM, sam aspin wrote:
Hi guys,
I'm trying to open a file using the CA Java API. I was hoping
to use the Java equivalent of the AudioFileOpen function found
in AudioFile.h part of the audio toolbox.
Within the java toolbox there are java equivalents for much of
the C API such as AudioHardware.java which is the java
equivalent of AudioHardware.h, unfortunately there doesn't seem
to be a corresponding version for AudioFile.h.
Can anybody shed any light on this or offer any alternative
methods?
any help would be greatly appreciated
thanks
Sam
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
--
mailto:email@hidden
tel: +1 408 974 4056
___________________________________________________________________
_______
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry
Pratchett
___________________________________________________________________
_______
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40blueyonder.co.uk
This email sent to email@hidden
--
mailto:email@hidden
tel: +1 408 974 4056
_____________________________________________________________________
_____
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry
Pratchett
_____________________________________________________________________
_____
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden