Hello?
Summer'15 release frenzy is not over yet!... well, it's only over on the equinox anyway...
QmidiNet is a MIDI network gateway application that sends and receives MIDI data (ALSA-MIDI and JACK-MIDI) over the network, using UDP/IP multicast. Inspired by multimidicast and designed to be compatible with ipMIDI for Windows.
Website: http://qmidinet.sourceforge.net Project page:
http://sourceforge.net/projects/qmidinet Downloads: http://sourceforge.net/projects/qmidinet/files
- source tarball:
qmidinet-0.3.0.tar.gz- source package:
qmidinet-0.3.0-8.rncbc.suse132.src.rpm- binary packages:
qmidinet-0.3.0-8.rncbc.suse132.i586.rpm
qmidinet-0.3.0-8.rncbc.suse132.x86_64.rpmChange-log:
- System tray icon now blinks on network send/receive activity.
- Prefer Qt5 over Qt4 by default with configure script.
- Complete rewrite of Qt4 vs. Qt5 configure builds.
- Fixed for some strict tests for Qt4 vs. Qt5 configure builds.
QmidiCtl is a MIDI remote controller application that sends MIDI data over the network, using UDP/IP multicast. Inspired by multimidicast (http://llg.cubic.org/tools) and designed to be compatible with ipMIDI for Windows (http://nerds.de). QmidiCtl has been primarily designed for the Maemo enabled handheld devices, namely the Nokia N900 and also being promoted to the Maemo Package repositories. Nevertheless, QmidiCtl may still be found effective as a regular desktop application as well.
Website: http://qmidictl.sourceforge.net Project page:
http://sourceforge.net/projects/qmidictl Downloads: http://sourceforge.net/projects/qmidictl/files
- source tarball:
qmidictl-0.3.0.tar.gz- source package:
qmidictl-0.3.0-7.rncbc.suse132.src.rpm- binary packages:
qmidictl-0.3.0-7.rncbc.suse132.i586.rpm
qmidictl-0.3.0-7.rncbc.suse132.x86_64.rpmChange-log:
- Prefer Qt5 over Qt4 by default with configure script.
- Complete rewrite of Qt4 vs. Qt5 configure builds.
- Fixed for some strict tests for Qt4 vs. Qt5 configure builds.
QXGEdit is a live XG instrument editor, specialized on editing MIDI System Exclusive files (.syx) for the Yamaha DB50XG and thus probably a baseline for many other XG devices.
Website: http://qxgedit.sourceforge.net Project page:
http://sourceforge.net/projects/qxgedit Downloads: http://sourceforge.net/projects/qxgedit/files
- source tarball:
qxgedit-0.3.0.tar.gz- source package:
qxgedit-0.3.0-6.rncbc.suse132.src.rpm- binary packages:
qxgedit-0.3.0-6.rncbc.suse132.i586.rpm
qxgedit-0.3.0-6.rncbc.suse132.x86_64.rpmChange-log:
- Single/unique application instance control adapted to Qt5/X11.
- Prefer Qt5 over Qt4 by default with configure script.
- Complete rewrite of Qt4 vs. Qt5 configure builds.
- A new top-level widget window geometry state save and restore sub-routine is now in effect.
- Added "Keywords" to desktop file; fix passing debian flags on configure (patches by Jaromír Mikeš, thanks).
- Fixed for some strict tests for Qt4 vs. Qt5 configure builds.
- Added application description as freedesktop.org's AppData.
Have (lots of) fun, always!
Summer'15 signing off.
Comments
QXGEDIT as control for db50xg
Hi,
I don't have much experience with midi. I want to use QXGEDIT to control the output sound of my DB50XG board.
I use the Roland UM-ONE as midi device to connect a midi keyboard as input and the db50xg as output via usb and QXGEDIT.
When I start qxgedit I can choose the roland um-one as input and output in the /view/options menu. But when I play on the midi keyboard no sound comes from the db50xg and I don't see the out led on the um-one blink. However, when I also start Rosegarden and there choose the um-one as input and output in the studio midi setup it is working and I can then use qxgedit to change the instrument.
What am I doing wrong? Is it possible to do this without starting rosegarden as well?
Kind regards,
Jan de Weerd
re. QXGEDIT as control for db50xg
hi Jan,
you'll have to set the QXGEdit MIDI output connected to your DB50XG MIDI input (wavetable), whichever specific to your case.
there's no use to connect (via the Roland UM-One) your MIDI keyboard controller to QXGEdit whatsoever, unless it's configured to send proper XG control messages (eg. RPN, NRPN) which i doubt--please connect it directly to the DB50XG MIDI input (wavetable).
please note that QXGedit is mainly a XG sysex editor, it doesn't produce any sound per se--it just manages to send setup commands and modify a current DB50XG configuration online (via standard XG MIDI SysEx messages).
hth.
cheers
Hi Rui,
Hi Rui,
Thanks for your quick reply.
I have build the DB50XG as a stand alone midi expander with a midi input. That's why it is connected via the UM-ONE cable (midi out) to the USB of the computer and via the other midi-in connector to the midi keyboard. My hope was that QXGEDIT would pass the key input of the midi keyboard (Roland E5) to the DB50XG along with the sysex info such as instrument change. Probably that is not so and does Rosegarden that job when both are active.
Thank you,
Jan
re. QXGEDIT as control for db50xg
My hope was that QXGEDIT would pass the key input of the midi keyboard (Roland E5) to the DB50XG along with the sysex info such as instrument change
nope.
as you might know already, QXGEdit does NOT function as a MIDI THRU device.
hth.
cheers.
re. DB50XG as a stand alone
I have build the DB50XG as a stand alone midi expander with a midi input.
omg! i've been caught sleeping on watch all this time now...
you say you have this thing built ?
i have parts (in some drawer still around) here which probably make for a couple of standalone db50xg's modules...
one, two and even maybe three. yes, i have at least 4 x db50xg specimens in store although, it has been for almost a decade now that i only get one to real use, from inside a terratec dmx6fire breakout box.
care to share your wisdom? maybe moving into the qxgedit forum for a starter ?
cheers
DB50XG as standalone midi module
Oops, I see that it is called module in stead of expander. (title edited)
Well, it is not my wisdom, I found this years ago on the internet.
Here some links:
http://www.compuzik.de/DB50XG.html in German
http://m1n1.de/html/body_midi_expander.html
http://atari.nvg.org/db50xg/
I have built something like the schematic in the last link with 2 extra inverting buffers to get a better wave-shape of the midi signal to the DB50XG.
I like the QXGEDIT program because I can use it on the Raspberry Pi, not yet the latest version though.
Is is probably possible to ad the midi through function as a feature to QXGEDIT? In this way it is possible to listen to the edited sound wile editing.
Thanks,
Jan
re. DB50XG as standalone midi module
awesome!
ftr. my reference was only and always been the primeval Elektor maganize article:
Yamaha DB250XG stand alone soundcard --Elektor Electronics, Jul/Aug 1997.
i have somewhere here around at least 2 spare elektor pcbs+parts and metal cases; i have built one but it got toasted a decade ago.
maybe it's time to revive this little gems already, as the ones i have working are on top of decommissioned pci soundcards (eg. turtle beach santa cruz, terratec dmx6fire, etc.).
re. midi through function... to listen to the edited sound wile editing.
as said, there's no real benefit nor convenience on doing this midi-thru in qxgedit, when you can connect directly and in paralell to the db250xg sound module instead--you'll certainly hear the effects of your edits while playing the keyboard.
cheers
DB50XG as standalone midi module
" when you can connect directly and in parallel to the db50xg sound module instead--you'll certainly hear the effects of your edits while playing the keyboard "
As I said in my first reaction, I'm not so experienced in midi so can you please explain what you meant with this?
Thanks, Jan
re. DB50XG as standalone midi module
maybe a picture is worth here (ascii art follows):
hth.
cheers
DB50XG as standalone midi module
Hi Rui,
After some other things I tried with midi I finally understand your hint above.
I now know that these connections must be made with qjackctl.
And then it works like you said!
I am using QXGEDIT version 0.1.2 on a Raspberry-Pi 2, later versions of QXGEDIT did not compile.
cheers, Jan
re. DB50XG as standalone midi module
I am using QXGEDIT version 0.1.2 on a Raspberry-Pi 2, later versions of QXGEDIT did not compile.
and can you tell why not?
byee
DB50XG as standalone midi module
Well, I found that I had to upgrade from QT4 to QT5 but then it still did not compile.
./configure went fine but make gave the following errors:
make[1]: Entering directory '/home/pi/Downloads/qxgedit-0.4.0'
cd src/ && ( test -e Makefile || /usr/lib/arm-linux-gnueabihf/qt5/bin/qmake /home/pi/Downloads/qxgedit-0.4.0/src/src.pro -o Makefile ) && make -f Makefile
Project ERROR: Unknown module(s) in QT: x11extras
qxgedit.mak:39: recipe for target 'sub-src-make_first' failed
make[1]: *** [sub-src-make_first] Error 3
make[1]: Leaving directory '/home/pi/Downloads/qxgedit-0.4.0'
Makefile:94: recipe for target 'src/qxgedit' failed
make: *** [src/qxgedit] Error 2
I then searched the internet for "Unknown module(s) in QT: x11extras" and found that I had to install development tools for QT.
I then did sudo apt-get build-dep qtcreator and then the make command worked fine and could finish with sudo make install.
So now I have QXGEDIT 0.4 working.
Thanks a lot, it is a nice tool!
All I need now is a tool that acts like the rhythm box in an electronic organ, a realtime arranger that can generate accompaniment and drums via the DB50XG.
Jan
Add new comment