-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I am considering to buy a soundcard for around 100$ and there is an
offer for a SB Audigy.
Any recommendations?
I read that the driver on Sourceforge is still experimental.
Did anyone experience problems using that driver?
What should I know or consider?
Thanks a lot,
- - Burkhard
- --
no html mail please, thank you. pub key at blackhole.pca.dfn.de
899B AFD7 14E9 D595 EA00 BE8B A348 851C 0F62 E91D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE93hdXo0iFHA9i6R0RAu6CAJ9iSrxXS0bPqCDNK93kuCvjPoL5QACdEC1U
CQymH3oCgVVjpg0DRyQxP1s=
=Kyxe
-----END PGP SIGNATURE-----
Hi,
I just got a sblive platinum 5.1. And am trying to get recording
(analog) from the live drive working. I can record fine from the line
and mic on the back and can here stuff coming in on live drive but I
can't for the life of me get it recorded :(.
If anyone has managed could they send me the mixer settings they're
using and the command line to arecord (or whatever program there using
to record).
Thanks
(alsa 0.9rc3, debian sid, 2.4.19 + low latency)
--
rob <mailingLists(a)pangolin.org.uk>
Hello,
I am looking for a way to record my minidisc using the optical output of
my Minidisc Deck. My soundcard (a CMI8738 ) has got an optical input
so it should be easy ;-) .
My problem is that I don't know how to record the sound from the optical
input so that there is a new file created for each track an my MD.
I know that there is a signal to say: this is the end of the track. So
it should be possible to detect this sort of "End Of Track" but I don't
know if it must be in hardware or in software.
If it is possible to do this in software, do you know a software
recorder that records from the optical (or digital) input (with alsa)
and that creates a new file for each track?
Thank you for your help,
JrSky.
Greetings,
has anybody gotten the Delta 410 to work with alsa (rc6 or CVS) ?
Playback appears to be clipped (a lot). I tried to set the 'Dac Volume'
with envy24control or amixer, but no luck. The controls are stuck at 0,
which probably means the driver is not handling them at all. Playback is
OK using the latest oss demo drivers, this sould exclude a faulty card or
resource conflicts.
Any pointers?
Regards,
Reiner
Hi,
I am one of two persons in Utopia Sound Division, makers of profesionally
sounding (and commercial) soundfonts since 1996.. I'm currently trying to
find out if there would be any interrest in a commercial patchset which is
natively developed for tiMIDIty. A few days ago Jaroslav Kysela (from the
ALSA dev crew) suggested me to try on this mailinglist so that's what I'm
trying right now.
In the past we've made products for many soundcards (among which was a 100+
MB patchset for the GUS PnP which the Ultrasound Driver project got native
support for) of which only a few where released under our name on our
website. My name can be found somewhere in the ALSA documentation and I've
convinced (incl. signing contracts etc.) Gravis in the past to release all
Gravis UltraSound driver sources to the public to allow further driver
development.. I'll telling this to avoid a flame after sending this email
which might be considered as an advertisement of some and to show that not
all of our interrests are purely commercially. This message is only meant to
get an idea of the interrest in the project described in this email (which
is currently vaporware).
What we've planned is a patchset sounding very similar to our current Utopia
Live! soundfonts currently available for the SB Live! and Audigy soundcards
(for information and MP3s check our website to get an idea what I'm talking
about.). Since I noticed that tiMIDIty is still widely used these days in
the Linux community I thought it might be a good idea to build a GM/GS
patchset for tiMIDIty from scrap. This would mean a full GM instrumental set
with all GS percussion kits (except for the SFX kit which only takes up
space and is seldom used these days). All samples will be 48 Khz 16 bit and
the final patchset is likely to cross the 300 MB barrier. Since the Linux
community likes getting things for free we are planning to release a lower
quality version of the patchset to the public to download for free (should
it the product ever pass the vaporware status), while the full quality set
would cost around 15$ and will below 50 MB to download (using oggvorbis
compression).
All replies on this message and the questions below will only be used by me
to determine whether or not there is a reason to start with this project. No
one who replies will be added to a mailinglist or will be contacted in the
future about this product unless he/she asks for it by sending an email to
me (roel(a)utopiasd.com). My replies on this matter will only be directly to
the mailinglist and will only go about this current topic as long as it
could be considered 'active' (or until a moderator considers it closed).
Basically my questions are:
- If you are a MIDI enthusiast of any form are you interrested in such a
product if it truly stands out. With interrested I mean, would you be
willing to buy it it would be developed ?
- If you are a MIDI enthusiast but are not willing to pay for a product like
this, do you think others would be.
- What do you dislike or like about current tiMIDIty patchsets ?
- Is there some size which you consider the maximum size of a good sounding
patchset ?
- Any other suggestions where to ask for interrest in a project like this
(e.g. regarding sequencers which use tiMIDIty etc..) ?
- Would you be interrested in beta-testing this product if it ever is made
(send a PM) ?
... and last but not least:
- Can anybody tell me what is and what is not correctly supported currently
in tiMIDIty regarding SF2 files (we are trying to decide between the .PAT
and .SF2 format). I've done some tests which have not been too promising
with the SF2 format but I'm still considering it since .PAT files only allow
single layered (mono) instruments.
I'd appreciate any comment on this email (either negative or positive)..
I hope that I've not crossed any rules in this mailinglist (I've been very
careful to avoid doing so) since I really need some feedback for MIDI
enthusiasts in the Linux community to decide whether or not it has any use
for use to develop such a product.
---
Roel / Utopia Sound Division
http://www.utopiasd.com
chris wrote:
> I have a midisport 4x4 and try to install midisport-firmware driver
> If I do make install I get:
>
> processing usb44ldr.sys ...
> loader data not found
Please try with the latest driver version.
It should work with version 4.1.16 (2002-10-15).
Mark Knecht wrote:
> I'm a little unclear whether this supports the 2X2
All MidiSport devices (including 1x1 and 2x2) are supported.
My mail was somewhat unclear on that (but the readme lists all devices).
> and whether you want that tested?
Too late, now I already know it works.
But you could simply use it instead. ;-)
Regards,
Clemens
Has any one been able to fiddle with tse3 on mandrake + alsa?
Can't get any sound but i don't know much about midi+linux
card:
snd-ens1371 ensoniq
module v_midi
when I tse3play foo.mid:
tse3play seems to play something (visually) but no output!
Something wrong in config but can't get anyclue!
Hint anybody?
Cheers
----
From: Steve Harris <S@ec...>
Re: experiences and reflections from the UK part II
2002-08-13 10:22
On Tue, Aug 13, 2002 at 12:15:37 -0400, Paul Davis wrote:
> my brother commented that the swt plugins sounded very "digital" to
> him. i bluffed by saying that i think it all comes down to the
This is very true.
Its partly a matter of taste - I like the hard digital filter sound, I
think it makes a pleasant change from analogue filters warmth.
In addition I'm a modular synthesist at heart, so if it annoyed me I would
just bung a lowpass->valve sim->lowpass on the end (this is what most VST
plugins will do).
I think I tend to use, and think of LADSPA plugins at a lower level than
most people. This became obvious at linuxtag.
But, mostly, making plugins sound warm requires more work, and no-one has
requested it (up til now).
---------
Steve, since you wrote this I have been doing a lot more work with the
ladpsa plugins and I tend to agree that the default sounds of a lot of
them are very hard.
Can you elaborate more on how and why you use "lowpass->valve
sim->lowpass on the end" to create a more warm sound?
Thanks. BTW. I think it would be a very good addition for the LAU FAQ so
I'll add this as it comes to light.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
I'm using audacity and terminatorx in a couple of
projects that I'm doing. Through the manipulation of
sound, I get a fair amount of clicks and pops. (This
is the nature of manipulated sounds, I realize that.)
but does anyone know of a good declicker for Linux? It
would speed up my process.
Art
__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com
Hi,
Since I receive this list in a 'Digest' format I'll reply to all questions
(as far as they have not been replied by by others correctly) in one email.
- Regarding from 'scrap vs scratch typo': Sorry my native language is not
English and sometimes I make some mistakes sometimes.
- Regarding: how this patchset would sound when comparing to Fluid (assuming
it's played back under tiMIDIty): Fluid is a bank in SF2 format which was
made to sound a true (realistic) as possible with all it's cons and pros.
The main problem with 'realistic' patchsets is that it's hard to make all
instruments fit together correctly. Next to often existing tuning problems
they often just don't fit together. It's true that with some MIDIs it might
some great but with others it might sound horrible or just lacking depth.
All our past Utopia patchsets have been aiming at full sound and balance.
This means (that whenever we do the job right) that 99.x% of the well
sequenced MIDI files (in other words those who use the Roland Sound Canvas
as a refference) will playback near perfectly. As a result of this our
patchsets don't sound as realistic as a soundfont as Fluid might do but it
will sound (near) perfectly balanced.
Our previous products all have been in development since 1996 in some way
when we made our Utopia Soundbank for the GUS PnP soundcards (check dejanews
for some messages about that) from scratch (using .PAT files and a
home-written editor to allow stereo voices) and thus no sample in it is used
in any other soundbank/soundfont (legally). Ever since we've been
fine-tuning and tweaking this base set of work we've done up till now.. So
I'm pretty sure that the sound is unique and quite powerfull.
To get an idea how this new patchset would sound like have a look on our
website at http://www.utopiasd.com and listen to the Utopia Live!
demonstration MP3s for the general idea and to the Acoustic Piano add-on
v1.0 demonstration MP3s to get an idea how the piano that will be included
in this new patchset will sound. Note that the Utopia Live! recordings are
still from version 1.x and some instruments like the pianos are very
outdated.
Note that the current patchsets are limited to 31.5 MB (and more recently 35
MB but no MP3 recordings have been made of the later versions) and since
size doesn't count too much with the tiMIDIty versions some instruments will
sound much more realistic (at least that is the plan).
Don't buy any of these products for use with tiMIDIty or another softsynth
or hardware other than the SB Live!/Audigy claiming to be compatible with
the soundfont format because it'll simply not work.
- The final version of this patchset will be released in the form of a
windows installer and a linux-perl installation script. So it should self
install up to a point. To make the downloadable size acceptable everything
will be compressed with the OggVorbis format. All samples will be 48 Khz 16
bit. My experience with Linux is still a bit limited (except for some
private server maintenance) so the initial beta versions will only come in
the form of a windows installer I fear.
- To get an idea how the current patchsets are layered download the free 2
MB demo version of Utopia Live! and open it in Vienna (under windows or
using an native SF2 editor under Linux). Note that the quality of these
samples (and looppoints) are very bad due to use of extreme compression (it
unpacks to about 36 MB). Still this should give you an idea how the layering
is done in our products.. E.g. our Acoustic Piano add-on (no demo available)
is in 48 Khz / 16 bit with 28 velocity layers. Layering use doesn't apply to
tiMIDIty since we are currently not happy with SF2 results.. Some examples:
Filters don't behave like they should, when playing a stereo voice you get a
phasing effect when timing is critical, early note-cuttoffs etc.. I'll have
a look at the tiMIDIty at sourceforge to see how things have improved and
will take that into consideration when determining whether to use .PAT or
SF2. If we use .PAT files make everything in Vienna in one use SF2 file and
sample it from an Audigy 2 to create a (huge) single layer set of
instruments. As a result, next to missing an stereo image the sound should
be equal or better (bigger instruments) than our current Utopia patchsets.
Regarding how they've been recorded or processed (e.g. our StereoID
percussion) I won't give any details. I know the SF2 format by head but I
don't know how tiMIDIty's implementation is. So far it seems terrible.
- Regarding .PAT implementation.. I guess that tremelo/vibrato is correctly
implemented ? From what I remember from back in 1997 it seemed to perform
nearly perfectly when comparing to the GUS Classic.
---
Roel / Utopia Sound Division
http://www.utopiasd.com