Hey Teza,
I beilive this is due to a config file mismatch from 0.42 to 0.58. Just
remove your /home/user/.fltk/rakarrack.sf.net/rakarrack.prefs file and you
should be good to go.
Andrew.
On Mon, Jul 12, 2010 at 7:51 PM, teza <tsaliou75(a)orange.fr> wrote:
> Hi all, just upgrade from the 0.42 to 0.58 but Rakarrack won't start, in
> a terminal I've got this error,
> teza@teza-laptop:~$ rakarrack
>
> rakarrack 0.5.8_Equinox - Copyright (c) Josep Andreu - Ryan Billing -
> Douglas McClendon - Arnout Engelen
> Try 'rakarrack --help' for command-line options.
> Erreur de segmentation
> teza@teza-laptop:~$
>
> Could you tell me how I can fix that.
> Thanks for helping.
> Regards
> Teza.
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Rakarrack-users mailing list
> Rakarrack-users(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rakarrack-users
>
Just forwarding Daniel's answer...
>> > - The LEDs are controlable via the ALSA mixer/control interface (see the
>> > amixer command line control interface for example)
>>
>> But aren't the LEDs dependent on the hardware switches?
>
> No, they're purley independent. You can make them show whatever you
> like :)
Thanks!
Pedro
I was very surprised to see Jack2 working well set to realtime + soft
mode, with a normal (non-rt) kernel, giving me 2.67 ms stated latency
without kernel crashes in Fedora 13. Anyone doing it this way? Anyone
see disadvantages? So far it's pretty gravy for me.
J.E.B.
Possibly of interest to readers here thinking back to some
observations Paul and others made about live performances in the U.S.
vs Europe. No idea if Linux is in use or not and truly it doesn't
really matter for the sake of this story. It's getting harder and
harder to be an old-school instrument player. I've seen reports of
Kurtzweil being used in Chicago and here in San Jose we had short run
of Wicked where it was apparently 100% GigaStudio.
http://www.nytimes.com/2010/07/11/opinion/11woodiel.html
Assuming one just wants to route audio output directly to external
mixers or soundsystems, are there any performance advantages, or
disadvantages, to using ALSA's "dshare" plugin to treat multichannel
soundcards as a bunch of individual devices. See ~/.asoundrc (
http://nielsmayer.com/npm/ice1724-dshare-asoundrc.txt ) below which
creates five stereo alsa "devices" from a single Delta 66: 66ch12
66ch34 66ch56 66ch78 66spdif .
What is the processing load and latency-implications of such a setup,
versus the jack-equivalent (which is certainly more convenient for
patching different connections together, as well as setting up
connections not supported by the 1-to-1 alsa style connections)?
I just set this up and was playing around with it on a Delta-66, where
the ice1724 soundchips' digital mixer allows the various ALSA outputs
to be mixed directly and then sent to "mains" output that's been
patched over to the digital mixer in "envy24control". In a way,
envy24control is a substitute for jack that uses the soundcard's DSP
as digital mixer and patchbay. Wouldn't such a setup give fractionally
lower latencies for, say, monitoring a vocalist or performer, over the
jack equivalent? (more importantly, w/o jackd runninng, it's one less
thing that has to "work in realtime" allowing your softsynths and
samplers to "carburate freely" and/or each hog their own CPU.) leaving
the ice1712 to render the results w/o further intervention....
The downside is that "dshare plugin" and its "buffer_size 256 //
period_size 128" is now having the kernel copy bits, instead of jack.
Is that a good or a bad thing if you're looking for audio performance
in realtime? Does this mean formerly you could get away with just
jackd running with realtime priority? ; whereas you'd need a realtime
kernel to do the "dshare" trick reliably??
...........................
##
## Useful suggestion from
http://alsa.opensrc.org/index.php/1712_.asoundrc#2005-09-18 allowing
## M66 card to be accessed as separate devices. using dshare plugin
## ( http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html#pcm_plugins_…
)
## PCMOUT1&2: gst123 -a alsa=66ch12 http://64.12.61.1:80/stream/1046
## PCMOUT3&4: gst123 -a alsa=66ch34 http://64.12.61.1:80/stream/1046
## PCMOUT5&6: gst123 -a alsa=66ch56 http://64.12.61.1:80/stream/1046
## PCMOUT7&8: gst123 -a alsa=66ch78 http://64.12.61.1:80/stream/1046
## SPDIFOUT : gst123 -a alsa=66spdif http://64.12.61.1:80/stream/1046
##
pcm_slave.66_slave {
pcm "hw:M66,0"
channels 10
rate 44100
buffer_size 256
period_size 128
}
pcm.66ch12_dshare {
type dshare
ipc_key 18273645
slave 66_slave
bindings.0 0
bindings.1 1
}
pcm.66ch12 {
type plug
slave.pcm "66ch12_dshare"
}
pcm.66ch34_dshare {
type dshare
ipc_key 18273645
slave 66_slave
bindings.0 2
bindings.1 3
}
pcm.66ch34 {
type plug
slave.pcm "66ch34_dshare"
}
pcm.66ch56_dshare {
type dshare
ipc_key 18273645
slave 66_slave
bindings.0 4
bindings.1 5
}
pcm.66ch56 {
type plug
slave.pcm "66ch56_dshare"
}
pcm.66ch78_dshare {
type dshare
ipc_key 18273645
slave 66_slave
bindings.0 6
bindings.1 7
}
pcm.66ch78 {
type plug
slave.pcm "66ch78_dshare"
}
pcm.66spdif_dshare {
type dshare
ipc_key 18273645
slave 66_slave
bindings.0 8
bindings.1 9
}
pcm.66spdif {
type plug
slave.pcm "66spdif_dshare"
}
...........................
Niels
http://nielsmayer.com
On 07/07/2010 10:23 AM, Atte André Jensen wrote:
> On 2010-07-07 08:37, Erik de Castro Lopo wrote:
>
>> Its a vocoder. I googled and found this:
>
> Actually I think this is actually a talkbox. It's a funky thing with a
> tube that goes in your mouth:
>
> http://www.youtube.com/watch?v=VX5v-S_jGD4
>
> To add to the confusion I often use the mda_talkbox (available as native
> linux vst here: http://sourceforge.net/projects/mda-vst/) which is
> actually a vocoder...
>
> Don't know of a way to get the real talkbox sound...
>
http://www.thedaftclub.com/showthread.php?t=155http://www.youtube.com/watch?v=VX5v-S_jGD4
So it is a talkbox sound, cool, I really thought they were just using
vocoders :)
Jeremy
////////////////
Yes, I was going to mention that it's a talk box. AFAIK there is no software
talk box emulator for Linux that sounds like a real talk box...maybe not even in
the commercial software realm, either.
A talkbox would be very difficult to emulate, and of course it would be special
kind of Vocoder.
Most professional pop artists use the real thing for that sound :)
Listening to the drumkits in hydrogen - they seem nice, but not _that_
nice. I was wondering if anyone has any recommendations for giga drums
to work with linuxsampler. Ross Garfield 2 seem quite a reasonable
price: http://www.bigfishaudio.com/4DCGI/detail.html?589 However, I'm
not so sure how I would make use of the multi-layers or get them to
sound more humanised - maybe playing with a midi keyboard?
Alternatively (better) - any good soundfonts or hydrogen kits for
realistic drum sounds?
James
Greetings,
YouTube video of one of my students performing a KT Tunstall song:
http://www.youtube.com/watch?v=1hEJjHN5E4U
Audio/video edited & converted with the latest Kdenlive.
Best,
dp
