Hi folks,
I'm having some really odd behaviour trying to send sysex to a synth where I can only send (using snd_rawmidi_write) in three-byte blocks. The only exception is if I send something not a multiple of three bytes but terminate the transfer with 0xf7, it will send everything including the 0xf7 - but this kills the sysex transfer.
The synth I'm trying to send MIDI to - a Casio CZ1000 - expects seven bytes of data to start a patch dump, at which point it will send a handshake back to the computer. Now if I pad the output with zeros the synth *will* handshake, but then not respond to the handshake acknowledge presumably because of the extraneous zeros.
I can't figure out what I'm doing wrong with this. Example code here:
http://dpaste.com/1361268/
This is tested with the MIDI out of my Emu 1x1 cable plugged into the MIDI in of a sound module and MIDI in on the interface plugged into the MIDI through on the module - so there is no "processing" of the MIDI messages.
Is it really impossible to just send raw bytes over a USB MIDI cable?
--
Gordonjcp MM0YEQ
http://www.kasploosh.com/projects/CZ/how_to/amidi-cz101-receive.html
:D
I missed this, since I googeld for the list ponly, so using amidi it's
possible to write a synth editor by shell script, at least sending some
commands is possible without having the knowledge how to program in a
Linux common high language such as C.
On Sat, 2013-08-31 at 07:15 +0100, Gordon JC Pearce wrote:
> On Sat, Aug 31, 2013 at 04:56:24AM +0200, Ralf Mardorf wrote:
> > http://www.kasploosh.com/projects/CZ/how_to/amidi-cz101-receive.html
> I have a proper copy of the Casio MIDI spec here. That's not the
> problem.
>
> The problem is that you can't send sysex in anything other than
> multiples of three bytes, and you need to send seven bytes and then
> wait for a response from the CZ1000. The seventh byte is never sent.
>
> It doesn't look like it's possible to do it with USB devices in Linux
> at least, because of the way that USB MIDI devices are handled -
> unless I'm missing something.
Then your MIDI implementation list is different to the one I found in
the Internet, since a dump request by this list needs different values
than those you used.
You send 44 00 00 for Casio, that's correct compared to the list from
the Internet, then you sent 70 for MIDI channel 1, that's also ok
compared with this list, but after that you sent 19, weil the Internet
claims it should be 10 to request a dump.
Than you sent 60, regarding to the Internet list its correct to request
the patch from current sound area.
You add two times 00, but the list in the Internet says that the ok
string 70 31 is needed.
On Fri, 2013-08-30 at 21:31 -0700, Devin Anderson wrote:
> You can also use `midisnoop` for this purpose:
>
> http://midisnoop.googlecode.com/
Thank you :).
Regards,
Ralf
Hello all,
REV-plugins-0.6.1 is no available at the usual place:
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads/index.html>
>From the README:
--------------------------------------------
Version 0.6.1 -- 28/8/2013
--------------------------------------------
* Plugin file renamed to zita-reverbs.so.
Any older versions in /usr/lib/ladspa must be
deleted to avoid conflicts.
* Cleanup of the 10 year old original code.
* Added
# 3701 zita-reverb
# 3702 zita-reverb-amb
These are LADSPA versions of zita-rev1 in resp. stereo
and first order Ambisonic mode.
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)
On Fri, Aug 23, 2013 at 12:48:22PM +0100, Chris Goddard wrote:
> Hi Adrian
Hi!
Let me CC Robin and LAD on this one.
> Hope you don't mind me contacting you directly, but I have a
> question regarding the RME TCO option and how it is supposed to
> work. I saw your name on some ALSA commits relating to the TCO
> recently and thought you would at least be the right person to start
> by asking.
>
> The TCO can read ltc, but once it has done that how does it
> communicate that time information tothe user space ? If I was, say,
> running Ardour and wanted it to chase this ltc what would Ardour
> need to do to make use of it ?
To be honest: I don't know, I've only fixed the kernel side of it. ;)
There are 1.5 ways to read the TCO's LTC output from userspace:
1. Via ioctl. Needs currently unreleased alsa-lib containing my
commit 4b169b05b48f4ea0196879b62b8c3fa5b050e806 and newest driver,
Takashi's sound-2.6 is fine.
Then, use SNDRV_HDSPM_IOCTL_GET_LTC. To the best of my knowledge,
that's the proper way to read the LTC and it's what I've fixed.
2. If the TCO is present, we create a MIDI output port sending the
MTC. At least I think it's MTC. Since the data is directly
generated by the TCO, the driver has no influence on it. No idea
if it helps in your case if you set this port as the MTC input
port in Ardour.
So it looks like for proper LTC support, we either need some converter
(maybe there already is one?) or ardour needs to be augmented. I have
absolutely no idea what the preferred approach is, but I'm sure Robin or
Paul do.
Maybe it's easiest to add another input path to one of Robin's LTC libs
that just runs the appropriate ioctl and parses the output. Since the
LTC is already decoded by the TCO, it should be pretty straight-forward.
Oh, and last not least: I don't own a TCO, so I cannot really test
anything. Fortunately, the ioctl is purely software, so a mockup should
do the trick.
Cheers
--
mail: adi(a)thur.de http://adi.thur.de PGP/GPG: key via keyserver
Hey All,
I've written up a blog post on allocating (audio) buffers in real-time.
The trigger was designing the record functionality for Luppp.
http://openavproductions.com/realtime-buffer-allocation
Hope its of interest to some, -Harry
CAPS Audio Plugin Suite 0.9.12
http://quitte.de/dsp/caps.html
New in this release:
Eq4p, a four-way parametric equaliser
http://quitte.de/dsp/caps.html#Eq4p
(Unlike Fons', this one uses parallel processing but lacks control
smoothening other than that provided by a continuous IIR filter
history.)
Elsewhere, a few stupid bugs have been fixed (one of them keeping
PhaserII from reaching strong effect levels), the documentation has
undergone a major revision, many plugins have been polished, some
renamed, and lots of unnecessary ones have been removed.
http://quitte.de/dsp/caps.html#Download
Enjoy!
Anybody from Europe, who still has got EPROMS used by some old
equipment?
It seems to be, that the EPROMS I burned in the stone age, without
protecting them against UV light, are still 100% ok nowadays.
I'm really surprised.
It's not completely off-topic for those who sometimes care about
dino-synth under European sunlight, when the RAMs where replaced by
EPROMS.
I'm positively surprised :).
Really, I'm stunned in a positive way :).
[Julien Claassen]
> I have been recording music for 11 years now, with Linux. [...]
> I'm not sure, if my luck is due to the commandline, it tends to eliminate
> a lot of problems, or if I'm just lucky with my Linux. :-)
I think the small applications with narrow focus you find used on the
commandline are simply a good match for the Linux audio ecosystem with
its many one-man part-time projects.
On the other hand there's a strong desire among users and developers
for applications with a rich feature set and often also a pretty
graphical interface. It can of course be done, even by just one man,
but it takes a lot of time, vast depth and breadth of skill and
dedication and a stable list of features for both the project itself
and the libraries involved to make such applications *and polish them
to professional standards*.
I watch this ambition not without sympathy, but also not without
occasionally speculating what the Linux audio landscape might look
like with less lofty and more UNIX-shaped goals.
Tim
CAPS 0.9.10
===========
http://quitte.de/dsp/caps.html
The CAPS Audio Plugin Suite, a LADSPA library comprising classic sound
effects, various signal generators and guitar tone processing, sees
another update containing some bug fixes, minor sound improvements in
various places and a new plugin, "Spice", which, strangely, appears
not to be an exciter.
http://quitte.de/dsp/caps.html#Spice
In addition, the package documentation has been revised and some
errors corrected.
http://quitte.de/dsp/caps.html#Download
Enjoy!
