[linux-audio-dev] [ANN] Audioscience Driver version 300 released

2006-06-14 Thread Eliot Blennerhassett
Greetings,

Version 300 of Audioscience HPI driver has been released and can be
downloaded from here:
http://www.audioscience.com/internet/download/linux_drivers.htm

There are many changes, please read the release notes for details:
http://www.audioscience.com/internet/download/drvnotes.txt

In addition ALSA has been updated to use the same source code and DSP
files.  Currently only available in the ALSA Mercurial repository:
http://alsa-project.org/download.php

If you have any problems or queries about this new driver, please email
support@ (our domain name), include info about your distro, kernel version, 
card type etc.

regards
--
Eliot Blennerhassett
AudioScience Inc


Re: [linux-audio-dev] Re: GPL Audio Hardware

2006-04-05 Thread Eliot Blennerhassett
On Wed, 05 Apr 2006 08:08, carmen wrote:
  the vendor deciding no longer to make ALSA drivers next week because 96%
  of their users run MacOSX or WinXP..

 this is a distortion. i'm not aware of any vendor actively supporting linux
 at all, so open audio hardware would definitely be welcomed.

FYI 

AudioScience has put a lot of effort into making linux drivers, firstly our 
own HPI API, then ALSA.  This is ongoing.
Driver is released under GPL, users libs under BSD style licence.

We could always do with more help from the community though ;-)

http://audioscience.com/internet/download/linux_drivers.htm

regards

Eliot Blennerhassett
AudioScience Inc.


Re: Behringer [was Re: [linux-audio-user] Re: [linux-audio-dev] RME is no more]

2004-11-28 Thread Eliot Blennerhassett

   Ah i don't know. I mean, you guys have put a lot of time into what your
   doing anyway. And in my case the trust in rme turned out to be a bummer
   just becasue i was thinking that they have trust in the open source
   developers. If they did have such trust, something like this would
   never happen. Once again, the simple answer is www.audioscience.com.
 
  Why don't the guys who do the driver development see if audioscience

Thanks for the vote of confidence!

 Do you mean the ALSA developers? Audioscience does its drivers for ALSA,
 no volunteers needed. :)

Not so fast...  we at audioscience would love to have some help with our ALSA 
driver and our underlying HPI driver.
We are a small company that supports various Micros~1 flavours as well as 
Linux 2.4 and 2.6 kernel variations.  I am the single person who does all the 
linux stuff, and would still say I don't know enough to do it easily or 
properly.

(Of course I have had help from our customers and other alsa developers, and 
kudos to Takashi Iwai for doing the work to incorporate our ALSA driver into 
the alsa tree)

So step right up...

  would be interested in producing pro audio cards (not just broadcast)
  with driver help from the OS community.  They seem like they have their
  act together.

So, what is the difference between our current offerings and what you'd like 
to see in a pro audio card?

 Seems like a good idea to me. The 5044 cards offers 8 analog i/os of
 24/192 and i wonder whether such card could not already be used for
 studio purposes.
 But in any case, they're very close.

 Marek

regards

Eliot Blennerhassett


[linux-audio-dev] [ANN] AudioScience HPK version 2.88 released

2004-08-05 Thread Eliot Blennerhassett
See the release notes and get the tarball from here
http://www.audioscience.com/internet/download/linux.htm

Many updates to specific card features, plus support for Linux kernel 2.6.x.

Also on the same page can be found the patch for alsa 1.0.5a 
(I know, I'm lagging behind)

regards

Eliot Blennerhassett
AudioScience Inc.


[linux-audio-dev] [ANN] AudioScience HPK version 2.88 released

2004-08-05 Thread Eliot Blennerhassett
P..S to the previous message:

Many thanks to Fred Gleason of Salem Radio Labs http://www.salemradiolabs.com/ 
for his assistance with this release.

regards

Eliot Blennerhassett
AudioScience Inc.


Re: [linux-audio-dev] Audio over Ethernet / Livewire

2004-06-21 Thread Eliot Blennerhassett
On Tue, 22 Jun 2004 09:25, Frank van de Pol wrote:
 While surfing the web I came across an interesting paper regarding Audio
 over Ethernet in low-latency low-jitter professional studio environments.
 I don't know to what extent the proposed scheme is open or patented or
 whatsoever.

 http://www.telos-systems.com/techtalk/ethernet4audio/NAB03_CHURCH_FINAL_2.p

See also http://www.peakaudio.com/

- Eliot



Re: [Agnula-Developers] Re: [linux-audio-dev] Request to audio related LiveCD packagers

2004-05-10 Thread Eliot Blennerhassett
On Mon, 10 May 2004 06:44, Fernando Pablo Lopez-Lezcano wrote:
  so far, alsa-firmware package is released from the understanding of 1
  as data.  but if someone insists it as program, yes, it can be a
  problem.

 I tend to look at it (very conveniently, of course) as neither. I view
 it as part of the hardware device we're dealing with. Without it the
 device does not work. It is distributed as a separate file (inside the
 driver disk that actually comes with the device) because it is
 convenient for the manufacturer for updates, avoiding a flash rom in the
 device, and so on and so forth.

Replying as an audiocard manufacturer (www.audioscience.com),  this is exactly 
true for us.

We have one external box (ASI2200) that can theoretically run standalone from 
internal flash, but for convenience of update, the firmware is downloaded by 
the driver every time.

Firmware is supplied as a binary data file.  As our linux driver is open 
source, the means of loading the data is there for all to see.
All the code that runs on the host computer is open under either GPL or BSD 
style licence.

But there is no way the company would release the source code for the 
firmware!
(in fact we are contractually prevented from doing so in some cases).

 Most probably very few people will agree with this viewpoint :-)

Obviously some do...

- ELiot



Re: [linux-audio-dev] Cross platform mixer API?

2004-03-14 Thread Eliot Blennerhassett
  Eliot Blennerhassett [EMAIL PROTECTED] wrote:
   Greetings,
  
   I am aware of PortMixer, which is a simple API that abstracts volume
   controls.
  
   Is anyone aware of any other crossplatform, cross-API mixer abstraction
   layers out there?

 I think Eliot's after a hardware mixer abstraction, ie. something to
 abstract away the hardware gain controls etc.

 Remix is an application library for multitrack/multchannel pcm sequencing
 in software; I don't think it's what Eliot's after.

 Conrad.

Correct on both counts Conrad.



[linux-audio-dev] Cross platform mixer API?

2004-02-26 Thread Eliot Blennerhassett
Greetings,

I am aware of PortMixer, which is a simple API that abstracts volume controls.

Is anyone aware of any other crossplatform, cross-API mixer abstraction layers 
out there?

AudioScience is looking for/considering building a library that will wrap 
ALSA, audioscience HPI, windows WAVE, WDM mixers in a common API.

If such a library doesn't exist, why is that?
1) Too hard
2) Too easy
3) No use
4) other?

I'd welcome your comments.

regards

Eliot
AudioScience Inc.





[linux-audio-dev] Writing a driver for this card: your thoughts?

2002-05-23 Thread Eliot Blennerhassett

Hello,

I work for AudioScience (www.audioscience.com) 

We make excellent (how could I say otherwise) audio cards.

The emphasis within the company has been on microsoft windows drivers.
... but we have a Linux driver, currently proprietary, closed source, that 
exposes this (http://www.audioscience.com/internet/download/spchpi.pdf) API.

(It may be possible to release the host side code, but never the DSP code on 
the cards.)

I think it would be much better if we had an ALSA driver.

I'd like some idea how hard it would be to write an ALSA driver either as a 
compatibility layer on top of our existing driver, or from the ground up.  I 
realise that this is rather a broad question, so please consider this an 
invitation to enter discussion, rather than a request for you to go off and do 
a lot of work for me.

Oh - what do you think of the cards' feature set?  


Some distinctive things about our cards (not all have all features)
- they have on board DSP.  Code is downloaded by the driver.
- they have a lot of on board buffer memory (hundreds of K at least)
- on board DSP handles decompression/compression
- mixing
- samplerate conversion or multiple outputs at different rates
- analog and digital audio I/O, balanced drivers

=
Eliot Blennerhassett   *:-{)
AudioScience, Inc. (New Zealand Office)
6 Centaurus Rd 
Christchurch 8002  Mobile: +64 21 1183531
New ZealandPh/fax: +64  3 3327818
[EMAIL PROTECTED]
http://www.audioscience.com
=