Dear all,
I got two cheap drumpads here that are _exactly_ the same, also on the
inside (PCB's have the same revision ID):
http://dx.com/p/portable-roll-up-usb-drum-kit-118841
But they get recognized differently, one as an USB MIDI device and the
other as an USB HID device. And when it gets recognized as a HID device
it's pretty useless because I can't hook it up easily to software that
accepts MIDI input.
This is the "working" drumpad (the one that gets recognized as an USB
MIDI device):
/var/log/syslog:
Mar 3 13:09:40 piertje kernel: [ 864.820341] usb 5-2: new full-speed
USB device number 2 using uhci_hcd
Mar 3 13:09:40 piertje mtp-probe: checking bus 5, device 2:
"/sys/devices/pci0000:00/0000:00:1d.0/usb5/5-2"
Mar 3 13:09:40 piertje mtp-probe: bus: 5, device: 2 was not an MTP device
Mar 3 13:09:40 piertje kernel: [ 865.123664] usbcore: registered new
interface driver snd-usb-audio
Mar 3 13:09:40 piertje pulseaudio[2044]: [pulseaudio]
module-alsa-card.c: Failed to find a working profile.
Mar 3 13:09:40 piertje pulseaudio[2044]: [pulseaudio] module.c: Failed
to load module "module-alsa-card" (argument: "device_id="1"
name="usb-UTECK_MIDI_DRUM-00-DRUM"
card_name="alsa_card.usb-UTECK_MIDI_DRUM-00-DRUM" namereg_fail=false
tsched=yes ignore_dB=no deferred_volume=yes
card_properties="module-udev-detect.discovered=1""): initialization failed.
lsusb:
Bus 005 Device 002: ID 0218:0001 Hangzhou Worlde
This is the non working drumpad:
/var/log/syslog:
Mar 2 20:49:45 piertje kernel: [ 3040.388297] usb 5-1: new full-speed
USB device number 7 using uhci_hcd
Mar 2 20:49:45 piertje mtp-probe: checking bus 5, device 7:
"/sys/devices/pci0000:00/0000:00:1d.0/usb5/5-1"
Mar 2 20:49:45 piertje mtp-probe: bus: 5, device: 7 was not an MTP device
Mar 2 20:49:45 piertje kernel: [ 3040.602562] generic-usb
0003:1941:8021.0001: hiddev0,hidraw0: USB HID v1.10 Device
[HID 1941:8021] on usb-0000:00:1d.0-1/input0
lsusb:
Bus 005 Device 005: ID 1941:8021 Dream Link WH1080 Weather Station / USB
Missile Launcher
So my questions are, why does this happen? The PCB is extremely simple
and only has one small IC. Is the USB ID determined by this IC? And the
big question, can I trick this non working pad to get recognized as a
valid USB MIDI device? I already looked into this (unbinding, binding,
new_id) but can't get it to work. And I'm 100% sure these pads are
exactly the same.
I could use this: https://code.google.com/p/drumroll/
But I get the idea this is not necessary. drumroll also already consumes
4% CPU on my notebook and I want to use this drumpad with my Raspberry
Pi, besides, it's extra overhead and only runs SUID.
So anybody any idea how I could trick my system in properly recognizing
this non working drumpad? I don't mind hacking kernel modules if that
would be necessary.
Thanks in advance,
Jeremy
Hi,
If you want to use multiple AMS patches at onces, you've to load
multiple instances of AMS right?
How should I route midi output from a sequencer or hardware controller
with one single midi output to those multiple instances of AMS without
triggering all the AMS instances? AFAIK qmidiroute has only 2 output ports.
\r
If I play a MP3 with
$ pacman -Q vlc
vlc 2.0.5-4
by jack and the volume is set to 100%, I hear and see clipping in
hdspmixer. It goes up to 0 dBFS at around 90%. FWIW the volume can be
increased up to 200%.
Anybody experiencing the same on (what distro ever)?
I just noticed this on my Fedora 17 system. I run jackd like this:
[paul@watt ~]$ /usr/bin/jackd --realtime -dalsa -dhw:0 -r48000 -p512 -n2
jackdmp 1.9.9.5
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 20
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|512|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 512 frames (10.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
Using port names patch v0.1 (07.04.2010)
Trying to load portnames from /home/paul/.config/jack/cards/M Audio
Delta 66.ss.ports.in
Trying to load portnames from /home/paul/.config/jack/cards/M Audio
Delta 66.ports.in
Trying to load portnames from /etc/jack/cards/M Audio Delta 66.ss.ports.in
Trying to load portnames from /etc/jack/cards/M Audio Delta 66.ports.in
Trying to load portnames from /home/paul/.config/jack/cards/M Audio
Delta 66.ss.ports.out
Trying to load portnames from /home/paul/.config/jack/cards/M Audio
Delta 66.ports.out
Trying to load portnames from /etc/jack/cards/M Audio Delta 66.ss.ports.out
Trying to load portnames from /etc/jack/cards/M Audio Delta 66.ports.out
Everything looks fine, and jackd claims it has realtime mode. I've
been away from Linux audio for a while, but doesn't realtime mode mean
RT scheduling? If I check the process's scheduler policy and
priority, it is NOT RT:
[paul@watt ~]$ ps -p 20370 -o cmd,class,pri,rtprio
CMD CLS PRI RTPRIO
/usr/bin/jackd --realtime - TS 19 -
I've added myself to the jackuser group:
[paul@watt ~]$ groups
paul wheel dialout wireshark jackuser
That group is already set up properly:
[paul@watt ~]$ cat /etc/security/limits.d/95-jack.conf
# Default limits for users of jack-audio-connection-kit
@jackuser - rtprio 70
@jackuser - memlock 4194304
@pulse-rt - rtprio 20
@pulse-rt - nice -20
Anyone have any idea what's going on here?
Hi,
At the moment I'm trying to bind my bcr2000 to amsynth. Midi learn works
fine so far and I understand that I need to save a preset in the
bcr2000, but when I reconnect amsynth, the binding doesn't work anymore,
so I guess I also have to save and load something in amsynth?
Anyone experience with a hardware midi controller (maybe even the
bcr200) and AMS? Does that work ok?
Best regards,
\r
-------- Forwarded Message --------
From: Ralf Mardorf <ralf.mardorf(a)alice-dsl.net>
To: linux-audio-user <linux-audio-user(a)lists.linuxaudio.org>
Subject: Re: Channel Linux - BETA
Date: Thu, 14 Mar 2013 11:58:15 +0100
PS: Firefox 19.0.2 claims that additional plugins are required to play
all media contend on http://channellinux.com/. However, it can play the
videos. Firefox claims that there's a try to redirect to another page.
Ghostery informs about e.g. a Zuckerberg connection. We know that your
website is a serious website, but if I wouldn't know you from the
mailing lists, I wouldn't stay on this website, even if I should be fine
with advertising. It's against my self-responsibility when using the
Internet to stay on sides that come with to much nick-nack.
Yesterday I finally tried the native Linux port of REAPER and posted the
following reports to the Cockos forum at
http://forum.cockos.com/showthread.php?t=83324 so I thought everyone here
would be interested too.
- danboid's 1st post to REAPER WDL dev thread -
It appears to me there was a brief resurgence of activity on the Linux
Swell port in December but little if anything has happened since? I hope
I'm wrong!
I couldn't believe it when I discovered earlier today that there has been
some sort of rudimentary native Linux port of REAPER on LoL since June
2011! I've long known REAPER was supported and ran well under wine but I
have a big issue with depending upon wine - I don't really like using
REAPER that way because I'm all too aware of the negative impact the wine
layer has on (JACK) performance and stability. I only heard about the Linux
native port in late December when my current band PistonFunkMachine used it
to record our debut album.
For yet another unknown reason, it was only today that I was inspired to
find out where the Swell port is up to and if possible give it a go myself.
Although it seems to still be practically unusable right now, I was
thrilled to see REAPER start up successfully and let me use most of the
interface. This was when using the libswell within
libSwell-x86_64-debian-wheezy-gtk3.tar.xz running under 64bit KX Studio
12.04.2.
REAPER loads and you can add tracks and browse through the menus here but I
realised I wasn't going to get much further when I discovered that the
open/save file windows don't appear when you select either option and the
same goes for the plugin window. It doesn't appear here!
I compiled Swell from git but had much less success. REAPER failed to start
at all and just barfed:
./reaper: symbol lookup error:
/home/dan/src/reaper_linux_x86_64/REAPER/libSwell.so: undefined symbol:
gdk_init_check
So, I may not be able to enjoy REAPER under my OS of choice properly just
yet but I'll be trying some of REAPERS VST plugins under qtractor soon.
When I have I'll report back here with the plugin results.
I also spotted a small error in:
http://www.landoleet.org/dev/libSwell-roll-your-own.txt
It says:
apt-get install build-essentials libgtk-3-dev
but the package name is actually build-essential without the 's'. Total
nitpick, I realise - especially at this stage!
I'm hoping Bitwig and Ardour 3.0 will give reason for more LinuxVST plugin
ports in the run up to LinREAPER. I'll certainly be buying REAPER as soon
as the Linux port works!
- Today's update re: plugins -
I have tried a few of the REAPER VST FX under qtractor but unfortunately
all I get is a stream of various 'SWELL API not found' errors.
I copied libswell (the binary from LoL that lets me start REAPER) into
/usr/lib as well as my vst plugins dir but that didn't help.
Hey all,
No question is a stupid question, as they say, so I might as well ask.
What kind of external audio hardware/JACK trickery would I need to
send a synth running on my laptop through a seperate output channel on
an audio interface with multiple ins/outs, send it, let's say, through
some outboard effects, and then back into the laptop as a seperate
input?
Cheers,
Andrew.
