Hi,
QMidiArp 0.5.2 has just seen the light of the day. It brings mainly
two improvements. One is a comeback, that of tempo changes on the fly,
and that now includes also tempo changes of a potential Jack Transport
master. Also the Jack Transport starting position is finally taken into
account, so that QMidiArp should be in sync also when starting the
transport master not at zero.
The second one is Non Session Manager support, mainly thanks to the work done by Roy Vegard Ovesen!
Note that for compiling in NSM support you will now need liblo as dependency.
Enjoy, and enjoy LAC in Graz this year
Frank
________________________________
QMidiArp is an advanced MIDI arpeggiator, programmable step sequencer and LFO.
Everything is on
http://qmidiarp.sourceforge.net
qmidiarp-0.5.2 (2013-05-09)
New Features
o Tempo changes are again possible while running, both manually or by
a Jack Transport Master
o Jack Transport position is now taken into account when starting,
QMidiArp used to start always at zero
o Muting and sequencer parameter changes can be deferred to pattern
end using a new toolbutton
o Modules in the Global Storage window have mute/defer buttons
o Global Storage location switches can be set to affect only the pattern
o Non Session Manager support with "switch" capability (thanks to
Roy Vegard Ovesen)
General Changes
o NSM support requires liblo development headers (liblo-dev package)
Hi Daniel,
I notice that I cannot help you without enough logs with which I can
realize what happens.
At lease, 'verbose' options for aplay/arecord, '#' nodes in
/proc/asound/cardX and dmesg.
Additionally, would you please add 'LANG=C' when you get output from
software.
I cannot read Spanish language...
> hi, it does not work.
Try in following steps:
1. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16
(I expected you receive 'Available formats' output)
2. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16 -f (here the format,
maybe S32_LE)
(I expected you receive 'rate is not accurate' output)
3. $ arecord /tmp/test.wav -D hw:UFX1604 -c 16 -f (the same above) -r
(got rate)
(I expected it will run correctly.)
I hope you to do these test when killing pulseaudio. The way is here:
https://wiki.ubuntu.com/PulseAudio/Log
Regards
Takashi Sakamoto
o-takashi(a)sakamocchi.jp
Hey Everybody,
I'm happy to announce OpenAV productions: http://openavproductions.com
OpenAV productions is a label under which I intend to release my
linux-audio software projects. The focus of the software is on the workflow
of creating live-electronic music and video.
The release system for OpenAV productions is one based on donations and
time, details are available on http://openavproductions.com/support
Sorcer is a wavetable synth, and is ready for release. Check out the
interface and demo reel on http://openavproductions.com/sorcer
Greetings from the LAC, -Harry
Hello everyone,
lately I had to fight big XRUN troubles, and thanks to this forum I
finally solved that. This excellent thread saved me:
http://linuxaudio.org/mailarchive/lau/2012/9/5/192706
On my long quest, I tried to see a little bit more what happened with
the IRQs on my system. I searched for a kind of 'top' utility to monitor
the interrupts, but the only apps I found were either deprecated, or
missed some cool features.
So, I ended up writing my own tool to monitor the file /proc/interrupts.
It's available a this address:
https://gitorious.org/elboulangero/itop
As its name indicates, it behaves pretty much like top, but for interrupts.
It's quite a simple thing, that I tried to enhance a bit with some cool
features:
+ refresh period can be specified.
+ two display modes: display interrupts for every CPU, or only a sum
of all CPU.
+ display every interrupt (sorted like /proc/interrupts), or only
active interrupts (sorted by activity).
+ in case the number of interrupts changes during the execution of
itop (due to a rmmod/modprobe), it's handled without any fuss.
+ command-line options are also available as hotkeys for convenience.
+ at last, the program display a summary on exit. The idea is that
this summary could be copied/pasted in emails to help debugging.
If anyone is interested, feel free to try and comment !
Cheers
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
Hi all,
We're excited about the upcoming Linux Audio Conference, featuring a
tightly packed diverse schedule with 77 events by over 100 persons!
The conference schedule has just been published at
http://lac.linuxaudio.org/2014/program
Apart from presentations, there are workshops, a poster-session and five
concerts in 3 days. The 4th day of the conference is dedicated to an
excursion: http://lac.linuxaudio.org/2014/excursion a simple overview of
the complete schedule can be found in the printable version of the program.
If you want to attend and have not yet done so, please register at
http://lac.linuxaudio.org/2014/registration
Looking forward to seeing you all in May at the ZKM.
yours truly,
robin - LAC'14 team
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
hello,
thanks to nama and ML archive, i now know about
https://github.com/navicore/Jacks perl api
I'm missing a callback to know the current transport position (either
in seconds or BBT).
Is there any way to get it from perl ?
(i'm currently having trouble to make jack.osc doing the same job)
thanks,
Raphaël