There is currently some documentation on the different pcm plugins, but what I haven't found is a very good reference on the correct syntax to be used within asoundrc. For instance, should lines be terminated by a semicolon? I've seen esxamples with and without and both seem to work. Are there limitations to when OOP notation can be used? These are just a few questions I have, I'm sure other people have some as well.
regards
-Reuben
You can grab those same pixmaps off the Jamin project.
That is probably not the reason behind the seg fault though. I haven't been able to get JackEQ to start without immediately seg faulting ever since the project started. The more recent versions of Jamin are starting to do the same thing as well and I have no idea why.
regards
-Reuben
-----Original Message-----
From: antoine rivoire [mailto:antoine.rivoire@ntlworld.com]
Sent: Wednesday, December 03, 2003 7:52 AM
To: A list for linux audio users
Subject: [linux-audio-user] jackEQ pixmaps
Hi,
I just checkeq out today's CVS and build jackeq (0.3.7).
I set the right value for the pixmaps path in .jackeqrc.
on starting jackeq, it segfaults with the following message:
spreemachine redhat # jackeq
jackEQ 0.3.7
(c) 2003 S. Harris, P. Shirkey
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details.
Using jackeqrc file: /root/.jackeqrc
/root/.jackeqrc:64: Unable to locate image file in pixmap_path:
"brushed-steel.png"
/root/.jackeqrc:65: Unable to locate image file in pixmap_path:
"brushed-steel.png"
/root/.jackeqrc:66: Unable to locate image file in pixmap_path:
"brushed-steel.png"
/root/.jackeqrc:67: Unable to locate image file in pixmap_path:
"brushed-steel.png"
/root/.jackeqrc:68: Unable to locate image file in pixmap_path:
"brushed-steel.png"
/root/.jackeqrc:92: Unable to locate image file in pixmap_path:
"thai-gold-knobs.png"
Registering as jackEQ
Segmentation fault
indeed the pixmaps folder only contains:
spreemachine redhat # ls /usr/share/jackEQ/pixmaps/
Makefile Makefile.am Makefile.in thai-gold.png
Do the pixmaps come in another package or am I doing something dumb?
Regards
Ant-
--
antoine rivoire <antoine.rivoire(a)ntlworld.com>
DC offset is when there is a Direct Current running over the same lines that audio runs through. Since sound signals are a type of Alternating Current, the addition of the DC tends to shift, or offset, the audio signal.
regards
-Reuben
-----Original Message-----
From: Eric Dantan Rzewnicki [mailto:rzewnickie@rfa.org]
Sent: Wednesday, December 03, 2003 11:10 AM
To: A list for linux audio users
Subject: [linux-audio-user] what is DC? [was Re: Analyzing ogg files]
What is DC offset in this context? I've seen this term on this list
before, but don't really understand what it means.
Is this the same thing refered to by the ecasound options -ezf and -ezx?
-ezf
Finds the optimal value for DC-adjusting. You can use the result as
a parameter to -ezx effect.
-ezx:channel-count,delta-ch1,...,delta-chN
Adjusts the signal DC by 'delta-chX', where X is the channel number.
Use -ezf to find the optimal delta values.
or is that a different DC?
-Eric Rz.
On Tue, Dec 02, 2003 at 07:38:54PM -0800, Mark Knecht wrote:
> On Tue, 2003-12-02 at 13:06, Andrew Burgess wrote:
> > >> Is there a DC offset which the cheap card is eating?
> >
> > >A DC offset is an interesting idea. How would I test for that?
> >
> > sox <file> -e stat
> >
> > displays midline amplitude.
> >
> > Or try a highpass filter, just as a test.
> >
>
> More data, but I'm not sure there's an answer there yet. The first file
> creates a very loud glitch sound, which the second one doesn't. The
> midline value seems better on the first, assuming this represents DC
> offset.
>
> bash-2.05b$ sox gmc2.ogg -e stat
> Samples read: 26972160
> Length (seconds): 305.806803
> Scaled by: 2147483647.0
> Maximum amplitude: 0.999969
> Minimum amplitude: -1.000000
> Midline amplitude: -0.000015
> Mean norm: 0.138033
> Mean amplitude: 0.000003
> RMS amplitude: 0.189967
> Maximum delta: 0.959961
> Minimum delta: 0.000000
> Mean delta: 0.093997
> RMS delta: 0.128996
> Rough frequency: 4766
> Volume adjustment: 1.000
>
> bash-2.05b$ sox examplesustain.ogg -e stat
> Samples read: 11361130
> Length (seconds): 128.810998
> Scaled by: 2147483647.0
> Maximum amplitude: 0.649841
> Minimum amplitude: -0.661896
> Midline amplitude: -0.006027
> Mean norm: 0.069344
> Mean amplitude: 0.002177
> RMS amplitude: 0.092420
> Maximum delta: 0.784546
> Minimum delta: 0.000000
> Mean delta: 0.072115
> RMS delta: 0.095279
> Rough frequency: 7235
> Volume adjustment: 1.511
> bash-2.05b$
>
I am looking for a good laptop solution, to develop on,
but I would also like to be able to do audio work on it.
What laptops do you use if you have one ?
v
I would like to buy either a soundcard or dedicated MIDI interface for MIDI
applications on a PC, and was wondering if people had any recommendations?
My criteria are:
1) Either PCI or USB
2) Good ALSA/kernel support on 2.4.22+ and 2.6 kernels
3) Good MIDI support/reputation
4) Ideally 2 out ports, but 1 would be ok
5) 1 in port is fine
6) If it's a USB device, it would be handy if it also worked on a Mac
I've been looking at the Midisport 2x2 as a possible contender. Any
thoughts/recommendations would be greatly appreciated! I'm running Gentoo,
if that makes any difference!
Thanks in advance!
Neil
--
Neil Durant
<n.durant(a)ntlworld.com>
>From: Joerg Anders <j.anders(a)informatik.tu-chemnitz.de>
>
>I agree, TiMidity is good. But _great_ is an overstatement.
[ ... ]
>You'll find that only the Hardware synthesis sounds
>like a bigband.
Hello. Sometime ago I compared Timidity and SB Live synth with
arabic midis. Timidity played the strings good but SB Live synth
did not. (Fluidsynth refused to work, and so, it was not tested.)
Regards,
Juhana
>> This is supposed to be the functionality of the user additions section.
>> Writing up a specific .asoundrc for every card supported is an awesome
>> task. It would require the developers (usually Takashi or Jaroslav) to
>> spend the time for every device known to work. That means less actual
>> coding. However there are plenty of people who use the devices and
>> figure out the syntax for the .asoundrc by themselves. Recently I have
>> been recieving about 4 useful additions per week.
>> [...]
>what about editing of the user submitted notes?
>when the number of submissions increases, it becomes harder
>to digest the information, some of it being better than others.
>Ideally it might be nice to integrate good comments into the body
>of the page. As its obviously far too much for Takashi and Jaroslav,
>how about assigning responsibility for this to someone who owns
>one of the cards. Eg i currently use the cmi8738 and would be willing
>to be editor for this card. I can imagine there might be problems
>with this, but....
Or perhaps automate it by allowing voting (was this entry useful to you?)
then allow sort by votes.
Clemens,
Hi. I made the required change to .asoundrc to map OSS to playback 5
& 6.
pcm_slave.hdsp {
pcm "hw:0"
channels 26
}
pcm.playback_5_6 {
type dshare
slave hdsp
ipc_key 314159265 # some unique number
ipc_key_add_uid yes # "no" to let multiple users share it
bindings {
0 5
1 6
}
}
pcm.dsp0 {
type plug
slave.pcm playback_5_6
}
The results were not positive. xmms starts, but as soon as hit the play
button it exits with the following message:
bash-2.05b$ aoss xmms
xmms: alsa-oss.c:222: oss_dsp_hw_params: Assertion `err >= 0' failed.
/usr/bin/aoss: line 9: 10892 Aborted
LD_PRELOAD=${exec_prefix}/lib/libaoss.so $*
bash-2.05b$
For kicks I tried mapping it to channels 0 & 1 instead, but got the same
results.
bash-2.05b$ aoss xmms
xmms: alsa-oss.c:222: oss_dsp_hw_params: Assertion `err >= 0' failed.
/usr/bin/aoss: line 9: 11022 Aborted
LD_PRELOAD=${exec_prefix}/lib/libaoss.so $*
I checked that libaoss from yesterday's Alsa-1.0.0rc1 release and it
seems to be:
bash-2.05b$ slocate libaoss.so
/usr/lib/libaoss.so.0
/usr/lib/libaoss.so
/usr/lib/libaoss.so.0.0.0
bash-2.05b$ ls -al /usr/lib/libaoss.so*
lrwxrwxrwx 1 root root 16 Dec 1 12:19
/usr/lib/libaoss.so -> libaoss.so.0.0.0
lrwxrwxrwx 1 root root 16 Dec 1 12:19
/usr/lib/libaoss.so.0 -> libaoss.so.0.0.0
-rwxr-xr-x 1 root root 43606 Dec 1 12:19
/usr/lib/libaoss.so.0.0.0
bash-2.05b$
However, what is interesting is that my 'wrong' example before will
actually work in aoss, except it maps xmms OSS audio to playback
channels 1 & 2. This is correct, in the sense that I get only 2 playback
channels, but they are mapped incorrectly.
<WRONG, BUT WORKS SORT OF>
pcm.dsp0 {
type plug
slave pcm.playback_5_6
}
I'm confused by this. Is this an aoss problem? Is it a driver problem
WRT my HDSP 965 specifically2? Something else?
BTW - These results are vaguely familiar. I think this happened before,
and I stumbled on this 'working' option just by my trying to understand
the language and doing a bit of guessing. What I don't understand is
*why* this option that uses the language incorrectly is even allowed to
run instead of producing some message about bad parsing of .asoundrc.
Comments?
For further kicks, and it likely makes no sense at all, but I decided to
try the 'right' format in .asoundrc, but use plughw:0 instead of hw:0.
That produced an interesting message from xmms:
pcm_slave.hdsp {
pcm "plughw:0"
channels 26
}
bash-2.05b$ aoss xmms
Segmentation fault
You've probably found a bug in XMMS, please visit
http://bugs.xmms.org and fill out a bug report.
Xlib: unexpected async reply (sequence 0x6d8)!
Thanks in advance for all your help.
Cheers,
Mark
Sorry for being too newbie again but how do I play the sounds in
ZynAddSubFX with my midi keyboard? I think it's a configuration problem
since I don't get any sound even with the Virtual Keyboard.
Thank you for your patience,
Eduardo.