On , thijs van severen <thijsvanseveren(a)gmail.com> wrote:
> any ideas ?
Yup! Tell jack to not use ALSA raw midi, use SEQ instead.
QJackCtl->Setup dialog, bottom left is "MIDI Driver", play with that..?
-Harry
Friends,
In the course of the year I did a couple of applications that I'm pretty
proud of. For some good reasons, I've withheld releasing them publicly
until now:
Ivory - a multi-touch, virtual MIDI keyboard controller
This was originally intended as a proof of concept, but
was so much darn fun that I pushed it to a beta-level
application.
I don't recall if it works with a mouse or not... but
it's not nearly as cool with a mouse.
http://gitorious.org/gabrbedd/ivory
proaudio-sound-control - one-stop shopping for Jack and Alsa control
This is a mash-up of QJackCtl and QasMixer. It discards
the GIMP-like multi-window interface of QJackCtl (which
is a major pain on a mobile device). It also adds direct
access to hardware mixer controls by re-casting QasMixer
as a widget inside QJackCtl. Say way you want about the
visual style of QasMixer, but it's the most complete GUI
interface to ALSA I've found.
https://gitorious.org/gabrbedd/proaudio-sound-control
CAVEAT EMPTOR: This code is released AS-IS, and I have no plans to
maintain them. It's released in the hope that someone can benefit from
them.[1]
DEMO: There's a video here that demos these on the Indamixx 2 (at the
MeeGo conference last spring)
http://www.engadget.com/2011/05/25/meego-conference-2011-sights-and-sounds-…
If you're in a hurry, fast-forward to about 1:13. It mostly demos
Ivory... but you also get brief views of proaudio-sound-control while
Tony is switching windows.
-gabriel
[1] For proaudio-sound-control... if someone decides to continue this
concept, you'll want to have a chat with me first. It works, but
is implemented in an unmaintainable way.
Aha,
TYOQA is finally coming to an end.
Are we getting 'pre-beta' status? No way. Not there yet. And quite
frankly, it will never be. As most of you who know my stance on this
alpha-and-omega-thing, may well rejoice: this is alphaaaaa!...
Now, let's get some more cynicism to the extreme, an activity that
I've been criticized more than often: the previous dot release nailed
the day when a bitten-fruit boss passed away. I am no prophet, but
could it be that we're witnessing the dawn of a brand 'new-age
passover'? I wonder what will happen this time.
Let's get over it, or better said, through it!
Time will tell or else, never mind.
Qtractor 0.5.2 (charlie x-ray) breaks out free!
This solstice release comes with a long overdue loop-recording/takes
'featuritis' breakout. As a matter of fact, it is actually the
relevant feature being introduced this season. BTW, happy
holidays--before's too late ;)
Well, I've tried to do something barely useful, at least for the lone,
one-(wo)man-band and over-dubber, that is. There's still a point on
the old motto, remember? That 'techno-boy(gal)-bedroom studio'? Now I
think he/she can have a guitar ;) In other words, I'm not really sure
this is going to be the best user-interface or paradigm, model,
whatever.
You tell me :)
Release highlights:
* Loop-recording/takes implementation (NEW)
* Default session file format option (NEW)
* LV2 State extension support (NEW)
* Options dialog re-arrangement (FIX)
* Improved in-flight recording display (FIX)
* MIDI clip file revision numbering (FIX)
* Clip "Unlink" option (NEW)
Cheers!
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
- source tarball:
http://downloads.sourceforge.net/qtractor/qtractor-0.5.2.tar.gz
- source package (openSUSE 11.4):
http://downloads.sourceforge.net/qtractor/qtractor-0.5.2-1.rncbc.suse121.sr…
- binary packages (openSUSE 11.4):
http://downloads.sourceforge.net/qtractor/qtractor-0.5.2-1.rncbc.suse121.i5…http://downloads.sourceforge.net/qtractor/qtractor-0.5.2-1.rncbc.suse121.x8…
- one upon the time, eons ago: user manual:
http://downloads.sourceforge.net/qtractor/qtractor-0.3.0-user-manual.pdf
Weblog (upstream support):
http://www.rncbc.org
License:
Qtractor is free, open-source software, distributed under the terms
of the GNU General Public License (GPL) version 2 or later.
Change-log:
- Fixed a probably old lurking destructive bug, which was incidental
to when an invalid or non audio file is imported, intentionally or by
mistake, into new or existing audio clips (eg. importing a MIDI file
where an audio file is expected).
- Force audio file closing to occur on the very same disk-write
(sync)thread, possibly mitigating an old random crash issue lurking in
the vorbis reference encoder (recording) re. the non thread-safetyness
of the vorbis_analysis() final call.
- Fixed extraordinary shadow-playback of audio clips which extent were
longer than the respective audio file length.
- Default session file format option now promoted (see
View/Options.../General/Session) in the way of whether file suffix
gets honored upon session open or save (.qtr, .qts or .qtz). This
brand new option also applies for default state file format on a
JACK-session salvage context.
- The View/Options... (aka. user preferences) dialog sees a new
arranjement in layout, with some options moving into this brand new
tab page called General.
- LV2 State extension support has been added, which shall replace old
LV2 Persist extension interface in the near future. It also replaces
the LV2 Files extension from now on (thanks to Dave Robillard).
- Dirty MIDI clips are now auto-saved when MIDI track properties get
changed through its own dialog.
- Fixed one probable too old crash when cancelling a new/add track dialog.
- MIDI SysEx event list editing is now fixed.
- Once again, make sure all recorded clips start and end at the very
same position when multiple track recording is turned on/off, while
playback is still rolling.
- Fixed Makefile.in handling installation directories to the configure
script eg. --datadir, --localedir.
- Possible attempt to improve in-flight recording clip display,
especially when looping and MIDI clips are involved.
- MIDI clip revision (re)numbering paranoia has been improved as much
to avoid MIDI file clashes as much as possible while editing multiple
MIDI clips which reference the same SMF and track/channel.
- Creating new or updating existing buses with exact same names of any
current dedicated inputs/outputs (which are implemented as special
covert buses) is now disallowed (preventing bug #3430406).
- Loop-recording/takes functionality is now ready for the masses and
accessible from brand new Clip/Take menu (Select, First, Previous,
Next, Last, Reset and Range...; the latter is actually being provided
as bonus feature :) as to fold any given clip into so-called takes,
simulating loop-recording mode over an arbitrary range).
- Loop-recording/takes infrastructure integration is sneaking in: all
clips recorded under a loop/cycle range may now get split (folded)
into one or more so-called takes. A new option is now provided, as to
select which take is about to retain after the recording ends, either
the First or the Last one. Just turn this mode off (None) and keep
with the old recording behavior, where clips are laid out unfolded
through the timeline, as usual (see menu View/Options.../Display/Loop
recording mode).
- Improved robustness in face of disabled audio buses when global
maximum number of JACK (audio) ports is surpassed (mitigating bug
#3421911).
- Improved single-track clip selection status logic (possibly fixing
bug #3419141).
- Clip/Unlink action is now available for detaching linked/ref-counted
MIDI clips, renaming and saving into auto-incremental SMF filenames.
- Temporary session archive directory now (pre)fixed whith program
name (eg. /tmp/qtractor).
- Fixed VST GUI editor window title on first show.
- Fixed build for ancient VST-SDK 2.3 (32bit only).
Enjoy!
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
Hi all,
Just an FYI. I am in the process of adding support for Apple's lossless
Audio Codec (ALAC) [0] to libsndfile. Should be done my the end of the
weekend.
Cheers,
Erik
[0] http://alac.macosforge.org/
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
Greetings all;
Still trying to sort reasons why a java app can't access the midi synth in
my sound card.
From an aplaymidi -l:
[root@coyote modprobe.d]# aplaymidi -l
Port Client name Port name
14:0 Midi Through Midi Through Port-0
16:0 SB Audigy 2 Value [SB0400] Audigy MPU-401 (UART)
16:32 SB Audigy 2 Value [SB0400] Audigy MPU-401 #2
17:0 Emu10k1 WaveTable Emu10k1 Port 0
17:1 Emu10k1 WaveTable Emu10k1 Port 1
17:2 Emu10k1 WaveTable Emu10k1 Port 2
17:3 Emu10k1 WaveTable Emu10k1 Port 3
Can I make the inference that a .mid file sent to 14:0 should find its way
to one of the 17:n ports? It only works if I -s to 17:0(thru 3)
Java, by its scanning methods, finds a huge list of ports, but only the
semi-broken, internal to java, synth actually makes a noise.
If I switch to amidi -l, the list is a bit shorter:
Dir Device Name
IO hw:0,0 Audigy MPU-401 (UART)
IO hw:0,1 Audigy MPU-401 #2
IO hw:0,2 Emu10k1 Synth MIDI (16 subdevices)
IO hw:0,3 Emu10k1 Synth MIDI (16 subdevices)
but sending a midi file to the latter pair, while taking the normal play
time for the file, is also silent. KMix gain is turned up quite a ways.
From the lengthy output of amixer contents:
numid=7,iface=MIXER,name='Synth Playback Volume'
; type=INTEGER,access=rw---R--,values=2,min=0,max=100,step=0
: values=72,72
| dBscale-min=-40.00dB,step=0.40dB,mute=1
But since aplaymidi works, I'm confused, does mute=1 mean it is live, not
off?
When java scans for synths, I get at the end of the listing, a
realtime_synth as device #68 in base 0. But I haven't a clue if that is
the audigy2's synths, but its silent in any event.
The target here is to somehow link this so the java system can actually use
the hardware synths in an Audigy2 Value card. But any attempt to send to a
(hw0:0) thru (hw0:3) path is silent, however aplaymidi always uses the same
amount of time to send the file.
Suggestions of what to check next?, please as I am lost in whatever
translations actually take place because there seems to be 2 different
methods of accessing a device and I can't find how they correlate.
Thank you.
Cheers, Gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene>
"The Amiga is the only personal computer where you can run a multitasking
operating system and get realtime performance, out of the box."
-- Peter da Silva
Hi everyone, I have a fairly simple, known size message format, it's just
five numbers, either ints or floats, wrapped in a structure. I guess I need
some kind of serialization to send this over a jack ringbuffer, but I've
zero experience with serialization in C++. Can anyone tell me what the
easiest or best way to do this is? Should I use the boost serialization
library? FWIW, I would like to eventually add osc messaging in too if that
affects the best choice.
Thanks!
Iain
Hello
A update release of gxtuner is available
a simple, small and lightweight guitar/bass tuner
for jack
(a break out of the guitarix tuner module)
This update is for those, who's like to use a
simple tuner with a analogue style like interface
It resolve some user requests and primary
added some more command-line options.
Also it added all configuration options to be
restored by the jack session manager.
gxtuner-1.6
changes:
* add command-line option reference pitch control
* add command-line option threshold control
* add command-line option window size
* add command-line option window position
* add all options to be restored by jack session manager
gxtuner comes with a analogue like, full arbitrary scaling interface (scale),
show the tune, the octave and the accumulated frequency in Hz,
gxtuner comes with full jack-session support.
gxtuner use a equal-tempered scale based on A4 = 440 Hz (427Hz <-> 453Hz)
gxtuner is licensed under the GPL.
for more information please read the included README file.
get it here:
http://sourceforge.net/projects/guitarix/files/gxtuner/
direct link
http://sourceforge.net/projects/guitarix/files/gxtuner/gxtuner-1.6.tar.bz2/…
have fun
Guitarix developers
_______________________________________________
Linux-audio-announce mailing list
Linux-audio-announce(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-announce
I must be missing something here.
amidi -l should list all midi out ports that are available to amidi, right?
No matter what i try with a2j and all of its variants (including j2a and
using the -e option) amidi -l never gives me any usable ports.
Same results as root.
Or should i be using the -L option to list the availabble ports? if yes,
how does that work? I cant figure it out. :-(
Another question: will a usb midi interface list the midi ports under alsa?
All help is appreciated!
Grtz
Thijs
On 9 Dec 2011 07:57, "thijs van severen" <thijsvanseveren(a)gmail.com> wrote:
Thanks guys!
I actually tried j2a but now i realise that i forgot the -e option to
expose the hw ports. Doh!
I'll give it another try tonight.
Thanks!
Grtz
Thijs
>
> On 9 Dec 2011 00:12, "Harry van Haaren" <harryhaaren(a)gmail.com> wrote:
>
> Hello Thijs,
>
> I t...
> On Thu, Dec 8, 2011 at 9:57 PM, thijs van severen <
thijsvanseveren(a)gmail.com> wrote:
> >
> > Hi all
> >
> > i'm trying to use 'amidi' to send a simple midi message to the midi out
> port of my fi...
>
>
> >>
> >> _______________________________________________
> >> Linux-audio-dev mailing list
> >> Linux-audi...
>
Does anyone have, in their old yellowed dead tree archives, a list of
instrument numbers vs instrument that would allow one to setup a
translation table to massage some very old midi files into General Midi
instrument numbers? I need a list of number vs instrument for the truly
elderly Casio CZ-101 and for the Casio MT-240.
Google doesn't seem to be a lot of help and the original users manual for
the MT-240 very carefully skips that.
Some music I moused in 20 years ago sounds terrible when played through a
modern GM player. Something has turned into a screaming Picolo and is
threatening to burn out my tweeters.
Any help will be very muchly appreciated.
Thanks.
Cheers, Gene
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene>
BE ALERT!!!! (The world needs more lerts...)
-----Original Message-----
From: linux-audio-dev-bounces(a)lists.linuxaudio.org on behalf of gene
heskett
Sent: Tue 12/13/2011 06:59
A little, but while it claims 210, the midi spec only allows 127.
+++
Hi Gene :)
I own a CASIO CT-470. It's sending SysEx to switch sound banks.
Sound Number / Prog Change
00. 10. 0
09. 19. 9
00.0 10.0 10
00.9 10.9 19
09.9 19.9 109
HEX for the SysEx F0 44 03 00 7N 51 DD F7
N is Channel (for my Casio 0, 1, 2 and 3 only)
DD 20 Bank Select on, DD 21 Bank Select off
Send data to a MIDI monitor and watch what happens if your Casio is
sending program changes.
Hth,
Ralf
