> > yamaha are willing to meet with us to discuss it. thats all the news
> > that's fit to print.
>
> Several of us met with a guy from Yamaha's mLAN department at Sounds Expo
> and he gave us the contact details ofr a guy in Japan who could provide
> specifications and so on. I dont know who has them now.
Me - I've traded a few emails with the Yamaha mLAN licencing manager and he's
been promising to get us in touch with a guy at Rhodes University who's been
working on mLAN driver support. Once I'd made contact with him I was going
to pass the details onto Bob et al. Be good for us to get all of these
contacts working together.
R
Hey LADs,
if you're looking for an easy way to add Ogg Vorbis and/or Speex support
to your apps, check this out :)
It's lightweight, callback based and uses per-channel float arrays by
default (ie. the format preferred by JACK and LADSPA). It's fully
documented, tested cross-platform, and includes examples for doing
Ogg Vorbis and Speex decoding (~100 loc) and encoding (~110 loc).
FishSound 0.6.0 Release
-----------------------
libfishsound provides a simple programming interface for decoding and
encoding audio data using Xiph.Org codecs (Vorbis and Speex).
This release is available as a source tarball at:
http://www.annodex.net/software/libfishsound/download/libfishsound-0.6.0.ta…
libfishsound by itself is designed to handle raw codec streams from a
lower level layer such as UDP datagrams. When these codecs are used in
files, they are commonly encapsulated in Ogg to produce Ogg Vorbis
and Speex files.
libfishsound is a wrapper around the existing codec libraries and provides
a consistent, higher-level programming interface. It has been designed for
use in a wide variety of applications; it has no direct dependencies on
Annodex or Ogg encapsulation, though it is most commonly used in conjunction
with liboggz to decode or encode Ogg encapsulated Vorbis or Speex files.
FishSound has been developed and tested on GNU/Linux, Darwin/MacOSX and
Win32. It probably also works on other Unix-like systems via GNU autoconf.
For Win32: nmake Makefiles, Visual Studio .NET 2003 solution files and
Visual C++ 6.0 workspace files are all provided in the source distribution.
Full documentation of the FishSound API, customization and installation,
and complete examples of Ogg Vorbis and Speex decoding and encoding are
provided in the source tarball, and can be read online at:
http://www.annodex.net/software/libfishsound/html/
FishSound is Free Software, available under a BSD-style license.
More information is available online at the FishSound homepage:
http://www.annodex.net/software/libfishsound/
enjoy :)
--
Conrad Parker
Senior Software Engineer, Continuous Media Web, CSIRO Australia
http://www.annodex.net/http://www.ict.csiro.au/cmweb/
http://www.notam02.no/arkiv/src/
SHORT DESCRIPTION
Run a vsti plugin as a jack and alsa-seq client.
HISTORY
0.0.2 -> 0.0.3
-Fixed stupid vsti init bug. Don't use v0.0.2, as it probably
won't work. (Sorry)
--
USound (the Useful Sound Daemon) is an audio I/O daemon for Unix
systems, especially GNU/Linux. It provides low-latency mixing of
multiple audio streams with resampling and limited format conversion, as
well as audio recording. The package also includes a client library, a
libao plugin, and patches for madplay and MPlayer. USound is free
software; it is distributed under the GNU General Public License (GPL),
except for the client library, which is in the public domain.
USound is somewhat similar to the Enlightened Sound Daemon (EsounD); but
as the name implies, USound aims to be more useful, particularly for
consumer desktop and multimedia applications. Applications for which
USound is suitable include media players, audio and video conferencing
software, text-to-speech software, and any application that plays the
occasional sound file to alert the user.
USound is still under development and by no means perfect, but in my
(admittedly biased) opinion, it has already surpassed EsounD and aRts in
usefulness. The USound home page is at:
http://pobox.com/~mattcampbell/usound/
Have fun!
Matt
(who is listening to an MP3 with USound and madplay right now)
Hi!
Anybodyelse been shopping around for a USB keyboard lately? How come
that the offerings available have just about all of the features and
flexibility that anyone would want, BUT when it comes to playability of
the keyboard itself, then .. how to say .. then it seems like just
another sloppy disaster.
I have one (as yet) unpatented idea for a cheap-to-build funky keyboard.
Anybody have a workshop?
/jens
What's the status of mLAN on Linux? I found a few discussions in the
archives, the latest being http://eca.cx/lad/2003/12/0084.html , but
nothing really conclusive.
It seems that there is documentation (and even an implementation) for
A/M, but nothing for Connection Management. Has anyone tried recently
to get documentation? Based on
http://www.yamaha.co.jp/tech/1394mLAN/english/ptt.html , it seems that
documentation is available for a nominal fee, but it is more than I am
willing to pay.
I am considering buying a PreSonus FireStation, which does what I need
at half the cost of an RME Hammerfall, and am willing to spend a
considerable amount of time writing a driver, if documentation is
available.
Thanks for any information,
Jody
Hello.
After years of waiting, AlsaPlayer succeeded to compile.
Here is a report. I post here so that authors of other
players can take the hints.
Given multiple files, I executed the following:
alsaplayer *wav
All files are played ok, yes. But when one hits (|<)
button the player skips two files back and plays only
the two last files.
Should it skip to the begin of the last file? Or to the
begin of the file list? Not something in between.
I also suggest a mode in which the play slider represents
the all files concatenated together:
o----file1---o----file2----o----file3----o
That way one has easier access to all files. The mode would
be specially good if one has tens of small sound samples.
Also: If I first press <stop>, then why (|<) starts
the playing? I just want move to the begin and then play
later. So, my suggestion:
If player is playing and one presses (|<), it continues playing.
If player is not playing and one presses (|<), it only skips to
the begin.
Further: The playing stops at the end of file, making it
impossible to continue scrubbing and speeding infinitely. The
player should just stay at the end at the play state. Likewise
when playing in reverse direction: player should not go to the
stop state at the begin.
More: The player played the file and stopped. I moved the play
slider to middle and started the play: the player started
playing at the begin, not where the play slider was at.
Neverending: The playing has been stopped and the play slider
is at the begin. I try grab and move the play slider, but
nothing happens. I should be able to move the play slider
at any point and start playing there. Now playing can start
only at the begin.
Infinity: After speeding backwards to the begin, the player stopped.
Then by pressing play button, I got the following errors and
nothing was played:
an ERROR occured or EOF (10793).
-*-
Given that AlsaPlayer has been developed for years now, why
I found so many problems? Most of the problems are not technical,
but artistic.
I have alsaplayer 0.99.76.
Regards,
Juhana
Hi,
> wait ... this seems to be similar to the problem i have with my hdsp ...
> i can't run it on my linux system at all, althouth it works fine with
> windows xp:
>
> can you try jack as super user with -R flag?
I will try to next week. Right now I am in a bind until this coming Sunday. I will let you know as soon as I am done.
>
> if you use an input signal, some of the input gets copied to the output
> if a sound application is running, which results some distortion ...
> could you start jack / pd, and try to use any of the input channels try
> several settings of hdspmixer...
>
> the problem with my hdsp is definitely a cardbus driver issue ... from
> what i heard from people who tried to help me is, that there are some
> problems in mapping the memory from the kernel to the buffer inside the
> cardbus bridge ...
> the problem with the kernel driver for the yenta socket is, that it's
> not properly supported ... thomas charbonnel, who maintains the hdsp
> driver and i wrote a message to both the kernel and the pcmcia-cs
> mailing-list, but didn't get any answer...
>
> of course, it could be a problem of the cardbus controller hardware,
> that the windows driver may handle differently than the yenta-socket
> module for linux my machine has an o2micro cardbus controller, that,
> conserning rme's support may produce problems ...
> i'm able to sell my notebook to my mother ;-) and get a new one, soon...
> the only reason, why i won't get an amd64 is that the notebooks that are
> equipped with this chip, have either ene or ricoh cardbus controllers,
> controllers rme warns against ... that's why i'll order a p4 inspiron,
> soon...
I would encourage you to hold off for a couple months, of course if you can afford to wait. It took me literally a good year on my old Inspiron 8000 (later replaced for 8100) before most of the quirks were resolved on it (both Win32 and Linux-side). This is pretty much the case with most of the new technology. For instance my newest toy, the aforementioned m6807 by eMachines has been on the market for barely 2 months and it is in dire need of a BIOS update. Hopefully one will be released by eMachines (although I am a bit skeptical about this one as most of their other products don't have such low-level updates available), but if not, there are plenty of other resellers that might since this model is being rebranded by over half-dozen companies across the world.
>
> anyway, when i talked to thomas a short time ago, he considered going to
> the lad conference, i'll go there, and concerning the schedule, you'll
> be there, too ... maybe we could try to track this problem down and try
> to contact the kernel mailinglist again...
Absolutely! Looking forward to meeting you!
>
> i hope that you will be more luck than i was ...
>
Thanks :-)
Best wishes,
Ico
http://www.notam02.no/arkiv/src/
vsti v0.0.2
SHORT DESCRIPTION
Run a windows vsti plugin as a jack and alsa-seq client.
REQUIRES
alsa(>=0.9), jack(>=0.94), python(>=2.0) and vstserver(>=3.0).
(might work with lover versions)
INSTALL
1. Set the INSTALLPATH and JACKINSTALLPATH variables
in the top of the Makefile.
2. make
3. sudo make install
USAGE
The name of the executable is "vsti". Run it with the plugin-name
as the last argument, and quit by pressing return. Examples:
"vsti JX220"
"vsti B4"
"vsti --help"
LICENSE
GPL
CREDITS
Made by Kjetil S. Matheussen, k.s.matheussen(a)notam02.no.
Sponsored by Lionstracs, manufacturer of Linux based musical
instruments http://www.lionstracs.com.
--
I got this today from Yamaha:
----------------------------------------------------------------------
Thank you for your e-mail about Linux community's interest in mLAN.
We think that it might be good to have a chance to meet with you or
other person from the Linux audio development community and explain
the current status and activity of mLAN.
We will be available at a couple of exhibitions such as Musikmesse,
AES Berlin soon. Or we may have a separate meeting.
Please let us know your preference.
We look forward to hearing from you soon.
----------------------------------------------------------------------
Unfortunately, the ZKM meeting is basically a 100% overlap with the
musikmesse. I don't see any feasible way to do a meeting with Yamaha
that weekend.
Is anybody else interested (anyone who considers them up enough on
1394 and associated technologies to go talk to Yamaha)? Alternatively,
does someone see a way to combine LAD@ZKM and the musikmesse?
--p