• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Jack (or something) at the OS level...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Jack (or something) at the OS level...


  • Subject: Re: Jack (or something) at the OS level...
  • From: JJB <email@hidden>
  • Date: Mon, 22 Jan 2007 22:20:53 -0800

Over the past few months I have been involved in one way or another with facilitating the development of a Bonjour aware, Mac-compatible application for the PC, trying to integrate new products into my own recording studio, and using Jack to accomplish various tasks that otherwise could not be done quickly, for instance:


* Using Jack, I simultaniously exported multiple softsynths in Cubase for 15 songs so that they could be mixed in Protools. Cubase only supports one-track-at-a-time bouncing of VST instruments.


* After much experimentation, I was able to get Windows VST's running on my Intel MINI under Crossover with MiniHost - sound output through JACK, broadcast via AUNetSend/Receive to my G4 Laptop. Not Ready for Prime Time due to lack of MIDI support in Crossover, but still cool.

* Made some recordings on my G4 using my Intel MINI as an AU server via AULab with AU NetSend/AUNetReceive and the Network MIDI functions built into Tiger. This worked, but the audio connection was not very stable at best - even though 100megabit ethernet should support many streams of stereo 24bit 44.1khz uncompressed audio.




The thing is, Apple has already built in inter-application MIDI, and inter-computer IP midi, and thrown in the useable AUNetSend/Receive. Since they decided to include the patchbay paradigm already, shouldn't it be carried to the logical next steps?:


1. Inter-application audio

2. Develop AUNetSend AUNetReceive into a built-in OS function that works seamlessly as part of the interapplication patch bay - no one should have to jump through all the hoops I've been jumping through in my studio to get audio and MIDI routed between multiple computers.

3. Release the spec for AUNetSend and AUNetReceive, so that compatible apps can be easily developed for Linux and Windows (perhaps even some useful apps for Mac) without having to do too much reverse engineering.

While I have partially solved my inter-computer networking problems with some optical - sp/dif converters, an ADAT optical card and some cables, it is only a partial solution to networking Macs for audio purposes. Developing these functions will have a powerful impact on how people use computers for music and sound.

Joel Braverman


_______________________________________________ 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
  • Follow-Ups:
    • Re: Jack (or something) at the OS level...
      • From: "Angus F. Hewlett" <email@hidden>
References: 
 >Jack at the OS level? No way! (From: Mikael Sundström <email@hidden>)

  • Prev by Date: Re: Jack at the OS level? No way!
  • Next by Date: how to release file handle?
  • Previous by thread: Re: Jack at the OS level? No way!
  • Next by thread: Re: Jack (or something) at the OS level...
  • Index(es):
    • Date
    • Thread