Hi !
This is is my first post to the list, I hope the topic is appropriate.
I'm an application developer and I've been using RtAudio/RtMidi for
years as cross-platform backend for audio and MIDI.
It never failed to work on me beautifully... until last week.
I've recently installed a raspberry pi 2 with the latest arch linux
distribution available and, for some reason, RtMidi doesn't report
connected interfaces. However, amidi does show them which makes me
think that alsa is properly configured.
[root@piewzei tests]# amidi -l
Dir Device Name
IO hw:1,0,0 MS-20 Controller MIDI 1
[root@piewzei tests]# ./midiprobe
Compiled APIs:
Linux ALSA
Current input API: Linux ALSA
There are 1 MIDI input sources available.
Input Port #1: Midi Through 14:0
Current output API: Linux ALSA
There are 1 MIDI output ports available.
Output Port #1: Midi Through 14:0
I could bother the nice people at McGill but I guess there's something
very specific to my setup and I'd like to debug it myself.
Would anyone have an idea of what could lead to this behavior ?
Thanks for any pointers,
Marc.
--
http://marc-nostromo.com
Hello list,
I just put PyNSMClient 2.0 on my github page.
https://github.com/nilsgey/pynsm2
It is a Non Session Manager Client-Library in one file with no
dependencies except Python3 (and NSMd of course).
It is designed to make it easier for your program to support non
session management.
There is an example file which is a complete program with a PyQt5 GUI
and a JACK noise generator output. Both the example and the lib-file
are documented. Additionally there is a small README.md
License is LGPL.
The client is largely untested and there are some NSM-API features
missing, but it should be easier to use and be more stable than version
1.
Real testing and a proper release will begin once I use my own lib
with Laborejo2 ( in development behind the scenes).
Have a nice day,
Nils
http://www.nilsgey.de
irc: #laborejo on freenode.
I thought I would post this since there was a big conversation here a while
back about AES67 and the slow death of AVB due to lack of support.
Well I was talking with a guy from Meyer Sound who told me that AVB has been
resurrected from the dead. Apparently Cisco and other large network hardware
vendors were willing to back it as long as it was made more generic to
accommodate industrial uses that are also time-sensitive.
So apparently it has been re-branded as “Time-Sensitive Networking” and has a
lot more momentum behind it.
http://en.wikipedia.org/wiki/Time-Sensitive_Networkinghttp://www.commercialintegrator.com/article/rebranding_avb_4_key_takeaways_…
So make of it what you will. :) I just found it to be interesting.
-Reuben
Hi all,
I'm a ALSA developer. I currently focus on developing sound drivers for
devices on IEEE 1394 bus. In this developing period for Linux 4.3, I'm
working for TASCAM FireWire series such as FW-1884 and FW-1082.
Well, are there some developers who have enough knowledgement about MIDI
messaging rule for Mackie Control or Mackie Human User Interface(HUI)?
As long as investigating FW-1082 and FW-1884, these two models transfer
control messages over IEEE 1394 isochronous packets, The shape of these
messages is similar to bitmap. In detail, see my RFC on alsa-devel:
[alsa-devel] [RFC][PATCH 26/37] ALSA: firewire-tascam: add MMAP support
to show status and control message
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-July/094817.html
To enable userspace applications to handle these messages, a converter
to MIDI messages is required, as Windows/OS X drivers did. In my
original plan, I off-load this task to userspace driver applications by
adding mmap(2)ed page. While, due to some reasons, it's better to
implement the converter into kernel driver.
As long as I know, for these models, there're three types of the
converter; usual MIDI messages such as Control Change (CC), Mackie
Control and Mackie Human User Interface, while I have a little
knowledgement about the latter two types.
For this occasion, I want to know the details. If a cost to implement
one of these two types, I'll use it for the converter. Else, I use usual
MIDI messages for my patchset to ALSA upstream.
Thanks
Takashi Sakamoto
Hi all,
as in through the hottest of summers--as southerners can't even
wait--here comes part one:
QjackCtl 0.4.0 (summer'15) is out!
though aside that everybody knows this already,
QjackCtl is a (maybe not so any more but) simple Qt [3] application
to control the JACK [2] sound server, for the Linux Audio infrastructure.
website:
http://qjackctl.sourceforge.net
downloads:
http://sourceforge.net/projects/qjackctl/files
- source tarball:
http://download.sourceforge.net/qjackctl/qjackctl-0.4.0.tar.gz
- source package:
http://download.sourceforge.net/qjackctl/qjackctl-0.4.0-23.rncbc.suse132.sr…
- binary packages:
http://download.sourceforge.net/qjackctl/qjackctl-0.4.0-23.rncbc.suse132.i5…http://download.sourceforge.net/qjackctl/qjackctl-0.4.0-23.rncbc.suse132.x8…
Change-log:
- Some windows fixes added (patch by Kjetil Matheussen, thanks).
- Most advanced Setup/Settings are moved into new Setup/Advanced
settings tab; limit range for the real-time priority setting, now having
6 as absolute minimum valid value (after patches by Robin Gareus, thanks).
- A new top-level widget window geometry state save and restore
sub-routine is now in effect (EXPERIMENTAL)
- Delayed geometry setup for widget windows upon startup has been
deprecated and scrapped altogether.
- Setup/settings dialog tab is going into some layout changes; also got
rid of old patchbay auto-refresh timer cruft, which was previously
hidden/disabled.
- New socket names are now automatically inferred from selected client
names while on the Patchbay widget, Socket dialog.
- Fixed for some strict tests for Qt4 vs. Qt5 configure builds.
- German (de) translation update (by Guido Scholz, thanks).
License:
QjackCtl stands free, still open-source software, distributed under
the terms of the GNU General Public License (GPL [4]) version 2 or later.
Weblog (upstream support):
http://www.rncbc.org
See also:
http://www.rncbc.org/drupal/node/912
References:
[1] QjackCtl - A JACK Audio Connection Kit Qt GUI Interface
http://qjackctl.sourceforge.net
[2] JACK Audio Connection Kit
http://jackaudio.org
[3] Qt framework, C++ class library and tools for
cross-platform application and UI development
http://qt.io/
[4] GPL - GNU General Public License
http://www.gnu.org/copyleft/gpl.html
Enjoy && have a whole hot'ta Summer'15 fun!
--
rncbc aka. Rui Nuno Capela
Hi all
GSequencer has a new minor release v0.5.0. Some highlights are:
* concurrent audio tree processing
* Multi-Output
* Improved notation & pattern editor
* Add custom LADSPA widgets to control ports
* ...
Please visit:
http://gsequencer.org
cheers,
Joël
Srinivasan S wrote:
> Am facing overrun & underrun issues, when I run the the above GSM application with the attached asound.conf
The sound card and the GSM streams are not synchronized.
You need to compensate for the drift between the clocks, typically by resampling.
(Jack's alsa_in/alsa_out would automatically do this.)
Regards,
Clemens
Hello!
The Linux Audio Berlin meetup happens every first Wednesday of the month.
This month's meeting will be (again) at C-Base at 19:30.
For more info please join the mailing list:
http://linuxaudio.berlin/mailman/listinfo/discuss
(sorry for cross-posting!)
Hope to see you all,
--
Bruno Gola <brunogola(a)gmail.com>
http://bgo.la/
Hi all,
This is a call-for-testing of my new ALSA driver for Digidesign 002/003
family. If you have these devices, would you please test the driver with
your devices and report your experience about it.
Especially, I want you to test MIDI port for machine control, because
developers have no 'console' models, just tested with 'rack' models.
When installing and testing, please follow this instructions:
https://github.com/takaswie/snd-firewire-improve
Patchset was already posted to alsa-devel and confirmed to
playback/capture PCM samples/MIDI messages by ALSA applications.
[alsa-devel] [RFC v2][PATCH 00/11] digi00x: new driver for Digidesign
002/003 family
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-March/089708.html
Several issues are still remained:
* The port for MIDI machine control message is not tested yet, because
002/003 console model are required.
* When allocates 2 or more channel numbers for the device, after 15 to
20 seconds from playbacking, any PCM samples causes noisy sound. Then,
all of LED on the front panel light. The streaming still continues
correctly.
* The actual effects of external clock source is not clear. When set
the clock source is somewhat external, even if stopping the clock
source, the device continues to sound PCM samples against my expectation.
* The meaning of asynchronous messages is unknown. This patchset adds a
functionality to receive it in userspace. You can test it with updated
libhinawa sample script.
https://github.com/takaswie/libhinawa
In my plan, this patchset will proposed for Linux 4.2. But these issues
need to be clear till the merge-window.
Regards
Takashi Sakamoto