I am with you guys on that. I think there are more elegant solutions for audio programming design challenges. I don't think anyone cares if it's the javax.audio API as much as they would just like to be able to run their own audio buffers in and out of the device.
Being able to chain effects or insert an effect into an arbitrary audio chain would be nice as well but those APIs tend to get very complex and difficult to work with. I'd rather not have a repeat of JMF (Java Media Framework). On Nov 20, 7:29 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > We are committed to improved multimedia support, as I've made clear in > other posts. You'll see some new features in the next major SDK > release. We just don't think that javax is the best way to support > audio. > > On Nov 20, 12:36 pm, blindfold <[EMAIL PROTECTED]> wrote: > > > Fair enough. Sorry (also to Ethan) for perhaps distracting a bit from > > javax.sound even though Java ME supports much the same javax.sound > > AudioInputStream functionality that Ethan was specifically inquiring > > about. Glad to hear that our ideas match. It should help in getting > > the actual work done. > > > Thanks > > > On Nov 20, 9:23 pm, Dan Bornstein <[EMAIL PROTECTED]> wrote: > > > > The original request was (and the subject line still is) specifically > > > about functionality in javax.sound. I responded in that context. My > > > later remarks were meant to frame the larger picture. Briefly put, we > > > agree. > > > > -dan > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
