Hello all,
anyone knows where to find a state diagram for PCM devices ?
What I want to find out in particular is
- if a device supports the pcm_resume() function, and it returns 0,
is a pcm_start() required or not (it is if pcm_resume() is not
supported) ?
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
I've started making tentative steps towards improving yoshimi - in particular
with respect to isolating MIDI, GUI and DSP.
The jack ring buffer is already used for data transfers from jack midi to the
dsp code, but I want to a) set up another buffer between jack midi and gui, and
b) if possible, try to do the same for alsa midi.
From what I've read, the jack ring buffer will happily work between any two
threads on a garbage-in-garbage-out basis.
However, around 2008 there was a lot of discussion about thread safety/memory
barriers etc. Was this ever resolved?
Also - and I don't know if this is actually a realistic situation - how would I
handle an all alsa setup? Would there be anything preventing me just linking to
the ring buffer itself?
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
Hi,
I can successfully play multiple independant tracks with html5 api. In
order to achieve sample accurate glitch free playback I am using the
prebuffer method. However, I would like to stream the media.
Looking at the various options for streaming I have not run into a perfect
solution for streaming multiple tracks with the html5 api.
I can see several potential attack vectors.
1: extend icecast to support multiple tracks/stream
2: extend the JACK API to integrate with option 1
3: extend the html5 API - possible but it would need to have more than
just me supporting the move.
4: custom solution with new/existing multichannel codec
I'm sure that others have already thought about this problem so am I
missing something obvious?
This could be useful for other services like bandcamp, soundcloud, etc...
I think we have an opportunity to guide the direction if we come up with a
solid open source solution.
*NB. This thread is intended to be a serious developer discussion. Please
do not respond to this thread if you do not have specific information to
add or discuss on this topic.
--
Patrick Shirkey
Boost Hardware Ltd
Hello,
After an intensive development of my ten year old project Wav Composer
Not toilet, from September 2013 up to the new year, I was intending to
make a new release in February, and then March, and then...
Unfortunately an official release has not materialized so I'm just
saying here is the code, do what the kcuff you like with it.
-=-=-=-=-=-= What?
Wav Composer Not Toilet is a text based non-professional non-realtime
non-interactive modular audio synthesis, sampler, and sequencer by a
hobbyist developer scratching an itch which has eased off for now.
-=-=-=-=-=-= What's new?
The main focus of recent development was intended to create greater
flexibility for the user in how modules and 'data objects' are
specified within a file. This flexibility allows:
* arbitrary ordering of items
* optional items
* optional groups of items
* multiple choice items
* self connection of optional inputs
This is available in the master branch and can be built like so:
git clone https://github.com/jwm-art-net/wcnt.git
cd wcnt
sed -i 's/DEFS=-ggdb/#DEFS=-ggdb/' Makefile
make
make examples
(the sed command above will remove debugging info that should be
removed in a release). After running `make examples` look in the
examples/ directory to see what wcnt has done.
Wav Composer Not Toilet is hardcoded to use a limited selection of
LADSPA plugins and no others, these are:
* Bode Frequency Shifter
* C* PlateX2
* DC Offset Remover
* Fast Lookahead Limiter
* Glame Low and High pass filters (+ Butterworth versions)
* Single Band Parametric EQ
The examples will fail to complete if these are not available. They
reside in the C* (formerly Caps) and SWH LADSPA plugin suites.
However, in the custom_names branch on github a generic LADSPA module is
available which allows specification of arbitrary LADSPA plugins. It is
working to a basic extent but unfinished.
Carry on.
char*s
James Morris
Hi Harry,
Do you know if there is some rule to compiling using librtaudio? Because,
there is an error..and i don't know what's wrong. I'm using g++ 4.7.2 and
i'm compiling using:
$ g++<programname.cpp> -o <programname>
The error is: undefined reference to 'RtAudio::RtAudio(RtAudio::Api)' i'm
including the lib in the program, normally!
2014-03-29 11:11 GMT-03:00 Thiago Carísio <thiago.carisio(a)gmail.com>:
> Hi, Harry!
>
> I don't know...hehe...i'm just was searching for api's and alsa seemed to
> be a good ideia. But, it's a bit difficult. I'm gonna take a look at this
> others api's
>
> Thanks!
>
>
> 2014-03-29 6:07 GMT-03:00 Harry van Haaren <harryhaaren(a)gmail.com>:
>
> Hi Thiago,
>>
>> Slightly other question: are you *sure* you want to write directly using
>> the ALSA API?
>> Generally, writing a JACK[1] client (for linux-pro-audio use-cases), or
>> RtAudio[2] is a better idea, and easier in my opinion...
>>
>> They're easier to write to, and abstract away some of the details of the
>> soundcard settings / channels etc.
>> HTH, -Harry
>>
>> [1]
>> https://github.com/jackaudio/example-clients/blob/master/simple_client.c
>> [2] https://www.music.mcgill.ca/~gary/rtaudio/
>>
>>
>> On Sat, Mar 29, 2014 at 5:00 AM, Thiago Carísio <thiago.carisio(a)gmail.com
>> > wrote:
>>
>>> Hi! I am Thiago and i'm starting to use the alsa api. I'm testing one
>>> function to make the sound capture and i got this input/output error. I
>>> don't get it why this is happening...so, please...some kind soul can help
>>> me?
>>>
>>> Thanks
>>>
>>> _______________________________________________
>>> Linux-audio-dev mailing list
>>> Linux-audio-dev(a)lists.linuxaudio.org
>>> http://lists.linuxaudio.org/listinfo/linux-audio-dev
>>>
>>>
>>
>
On Mon, Feb 24, 2014 at 12:48 PM, David J Myers <
david.myers(a)amg-panogenics.com> wrote:
> 0.121.2 is the version I got from ubuntu with apt-get install.
>
> I removed that version and downloaded and built 0.124.1, however when I
> now try to run
>
> jackd -d alsa
>
> I get back
>
> jackd: unknown driver 'alsa'
>
>
>
> What's going on?
>
Your system is missing the development version of the ALSA library. So JACK
was built without ALSA support.
What version of Ubuntu are you using? I am unable to believe that 0.121 is
the latest version available for any reasonably recent version of that
distro.
--p
