[125,0,24] GS Electronic
[125,0,25] GS TR-808
[125,0,32] GS Jazz
[125,0,40] GS Brush
[125,0,48] GS Orchestra
[125,0,56] GS SFX
[125,0,127] GS CM-64/32L
[126,0,0] XG SFX 1
[126,0,1] XG SFX 2
[127,0,0-7] XG Standard
[127,0,8-9] XG Room
[127,0,16-17] XG Rock
[127,0,24] XG Electro
[127,0,25] XG Analog
Date: Wed, 18 Feb 2009 16:16:01 +0100
From: Peter Gebauer peter.geba...@stockholm.bostream.se
Heya Jimmy!
... Ideally,
I'd like to retain XG
mode on my piano, but let fluidsynth interpret them as
simple GM program
change messages.
I've seen a few patches for GS (Roland), but none
Hi Josh,
About XG (and GS) program changes, and how missing instruments might be
handled, Here are some comments and observations I found around the web. I
think missing drum-kits should be handled similarly.
archive.cs.uu.nl/pub/MIDI/DOC/xg.txt
Both specs also operate a scheme of tone
with being in different
modes). It seems
like re-implementing this with minimal bank switching
behavior logic,
may make sense in the short term. But implementing
the complete XG
spec for example, is not a trivial undertaking.
Elimar
I agree with your assessment regarding XG
Heya Jimmy!
I've found and read the manuals, my piano has two modes of operation: GM or
XG, by default XG is on. Setting it to GM will actually change the local
DSP settings to ignore XG-specific effects. Ideally, I'd like to retain XG
mode on my piano, but let fluidsynth interpret them
, or
Hubi's Loopback. I believe they provide some virtual midi ports
or connection-points or something along that line.
Yeah, I ended up finding a virtual MIDI hub driver, which I used to
test/debug things all in a VirtualBox Windows install ;)
In another message, you said something about XG
not
convinced that just keeping the previous instrument
selection is any
better than trying to be a little smarter about it,
depending on the
mode (GM, GS, XG, etc). If a SoundFont was loaded, which
supported all
the instruments of the playing MIDI file, then there would
be no issue.
Best
. This
might be part of why you feel you don't get an answer for
some of the stuff you say. Another is lack of time on my
part.
My opinions are my interpretation of the MIDI specs. XG-mode does not break
the MIDI specs in any way. In fact, I think of it as one decent interpretation
of the MIDI
If someone has a pressing need for this patch, let us know. I can try to
revise and resubmit the simple patch, without XG support for the moment.
Otherwise, before I send the patch for drum channel, perhaps we can hash out
how Fluidsynth should deal with XG MSB, LSB, ProgChange messages
--- On Mon, 7/16/12, David Henningsson di...@ubuntu.com wrote:
Just a question here: What soundfont do you run these files
with? Is
there an XG soundfont out there (or maybe even lots of
them?), and if so
- how is that soundfont constructed? How does it squeeze
XG's drum banks
,
and it follows this as well. I assume it's somewhere in the
sf2 standard.
So bank numbers above 128 usually make no sense, which is
why MSB is
ignored for XG (and why MMA style is not the default...).
We're kind of
stuck between sf2's standard and XG's standard, and need to
figure out
how
checked
Unison.sf2,
and it follows this as well. I assume it's somewhere in the
sf2 standard.
So bank numbers above 128 usually make no sense, which is
why MSB is
ignored for XG (and why MMA style is not the default...).
We're kind of
stuck between sf2's standard and XG's standard, and need to
figure
feel you don't get an answer for
some of the stuff you say. Another is lack of time on my
part.
My opinions are my interpretation of the MIDI specs. XG-mode does not break
the MIDI specs in any way. In fact, I think of it as one decent interpretation
of the MIDI Specs, which handles 128x128
screwed something up for you.
// David
Your change is not correct in both MSB, and LSB handling for XG bank
calculation.
-
The problem with fluid_channel_set_bank_lsb():
if (style == FLUID_BANK_STYLE_XG)
newval = (oldval ~BANK_MASKVAL) | (banklsb BANK_SHIFTVAL);
is that any
found the
XG standard here:
http://web.archive.org/web/20060926124939/http://www.yamaha.co.uk/xg/reading/pdf/xg_spec.pdf
The first question is: What do we really support? GM? GM2? GS? XG? For
XG, the drum kit bank is 127, not 1.
There is also some information in this document which I think
Hi Josh,
Also, I dont know much about XG, only bit and pieces I can find on the web. I
would love to get to some of the XG docs that were available a while back. I
don't know any real info about GS, since I haven't done much searching for GS
info.
Since I play around with some Yamaha
exclusive,,10,f0 43 73 7f 4b 11 00 45
7f f7
2745,M Audio Delta 1010LT:0,Program change,1,0,
2745,M Audio Delta 1010LT:0,Control change,1,32,112
2745,M Audio Delta 1010LT:0,Control change,1,0,0
/Peter
On 2009-02-15 (Sun) 16:30, jimmy wrote:
Hi Josh,
About XG (and GS) program changes, and how
with being in different modes). It seems
like re-implementing this with minimal bank switching behavior logic,
may make sense in the short term. But implementing the complete XG
spec for example, is not a trivial undertaking.
Elimar
On Fri, Aug 6, 2010 at 7:05 PM, jimmy wg20...@yahoo.com wrote
(as far as all the additional
functionality which comes with being in different modes). It seems
like re-implementing this with minimal bank switching behavior logic,
may make sense in the short term. But implementing the complete XG
spec for example, is not a trivial undertaking.
I agree
know if this
change screwed something up for you.
// David
Your change is not correct in both MSB, and LSB handling for XG bank
calculation.
Yes, I let it stay the way Pedro wrote it. Maybe I should have mentioned
that explicitly, sorry.
Basically the problem is that Soundfont files can have
Note that
chan-sfont_bank_prog
does have the space for the full 14-bit [MSB, LSB] combination in place. And
yes, the FLUID_BANK_STYLE_MMA handles the 14-bit combination of [MSB, LSB] just
fine in those 2 functions. You and Pedro simply cripled XG-mode by rejected my
changes
I think GM support is all I can ask for, but understand how GS, XG are designed
and know how to scale them back to GM level is all Fluidsynth need to do.
About MIDI mode of GM, GS, XG... I don't have any official reference, but from
what I understand, GM only has 128 defined instrument list
to
best map CC0 and CC32 to the SoundFont's wBank value in
different GM/GS/XG/GM2 modes, which was not trivial to
answer. Therefore we have the synth.midi-bank-select
option that uses different mappings depending the mode you
select. Isn't that option working for you?
My patch specifically allows
On Monday, July 6, 2009, Graham Goode wrote:
For GM1 and GM2 specs see http://en.wikipedia.org/wiki/General_MIDI,
http://www.midi.org/techspecs/gm.php
For GS download a Roland Sound Canvas manual from
http://www.edirol.net/products/en/archives.html and see the appendix
lists
For XG try
http
On Monday, August 9, 2010, I wrote:
XG defaults and recommends channel #10 as the drum channel. Other channels
may be used as drum channels when CC#32=127 is received on any channel.
What I'm proposing is to fix *NOW* the broken behavior that is plaguing
FluidSynth-1.1.x converting any
,
Unless you want 2 or more simultaneous drum channels (as in GM2, or XG midi
files), you don't really need this patch. Even then I only made sure it still
works with existing GM-midi files. I haven't done any real tests regarding GM2
(I haven't found one out there), or XG midi files yet.
If you
On 11/28/2013 10:51 AM, Element Green wrote:
Did you see any information that indicated that mma mode was supposed to
be GM2?
When I read this old thread:
https://lists.nongnu.org/archive/html/fluid-dev/2012-07/msg00024.html,
it sounds implied. It lists GM, GS, XG, and GM2 as bank selection
the
MIDI file is expecting a GM, GS or XG MIDI device).
In summary and to check my understanding..
MIDI file selects an instrument in an alternative bank/program,
expecting a variation on an instrument. The loaded SoundFont doesn't
have the particular bank/program combination. Currently
, and also works fine in my tests with a few MIDI
files created for XG synths that I've found in my HD.
You are perceiving that there is debate around this matter,
when in fact the controversy comes from many years ago, when
the MIDI manufacturers defined those different standards
(GM, GS and XG
and CC32 to the SoundFont's wBank value in
different GM/GS/XG/GM2 modes, which was not trivial to
answer. Therefore we have the synth.midi-bank-select
option that uses different mappings depending the mode you
select. Isn't that option working for you?
My patch specifically allows XG-soundbankd
? That should map
against our default volume of 0.2. There is also no reason to ignore LSB.
About the GS/XG/GM sysex (what about GM2 reset, btw?) I think the code
would look nicer if you did a memcmp() instead of matching each
individual byte.
What do you think?
// David
On 2011-02-10 23:08, jimmy
--- On Mon, 7/9/12, David Henningsson di...@ubuntu.com wrote:
Sadly, my patch never made it to the SVN code base, so
the XG-mode soundbank selection and drumbank selection never
worked in the official FluidSynth code base.
You do have a bank selection patch merged, see:
http
Hello Jimmy,
On Mon, 2008-01-07 at 10:20 -0800, jimmy wrote:
Hi Josh,
I'm sure the different specs for GM, GS, XG, XG-lite
basically made up their own specific scenarios.
From what I see, each channel is like a patch cord
into a mixer, if the Cello-ist broke a string, it may
not be ideal
but should be maintained.
Note that DLS soundfonts are different: they have 14bit bank numbers. But
FluidSynth doesn't use DLS files yet!
There is not an universal behavior for MIDI Bank Select messages, because it
depends on several standards: GM, GS, and XG:
GM (General MIDI) does
Henningsson di...@ubuntu.com wrote:
From: David Henningsson di...@ubuntu.com
Subject: Re: [fluid-dev] Code patch for GM, GS, XG system-reset SysEx's,
and MasterVolume SysEx
To: jimmy wg20...@yahoo.com
Cc: fluid-dev@nongnu.org
Date: Wednesday, February 16, 2011, 5:39 AM
Hmm, seems this patch
the best
solution was. I should
probably read over the older thread, since I think I did
have some good
ideas of how to resolve it then (something about
determining whether the
MIDI file is expecting a GM, GS or XG MIDI device).
In summary and to check my understanding..
MIDI file selects
, gm, xg, mma, awe32 (Note: bank number for melodic channels only)
gs: ignore LSB (CC#32) messages; bank=MSB
gm: ignore LSB and MSB messages; bank=0 always
xg: ignore MSB (CC#0) messages; bank=LSB
mma: bank=128*MSB+LSB
awe32: synonym of gs
default = gs
* SYSEX MIDI mode change messages
be in the MSB, and those correspond to the bank numbers encoded in the
SoundFont banks themselves, I think FluidSynth should behave
accordingly. Namely, it should read SoundFont bank numbers scaled to
MSB. The player code should handle both MSB and LSB, and in case of XG
MIDI data setting the bank LSB
the people at the top have much time to give.
Therefore, proposing drastic changes is probably not going to be feasible,
even if it's theoretically a good idea.
Of course, I don't expect you to waste your time on XG-stuff if that's not
your area of interest, or expertise. I have done some homework
percussion channel handling
gm: Ignore note-offs for all but fast Whistle and Guiro on percussion
channel
no-off-percuss: Ignore all note-offs on percussion channel
Assuming midi.mode (or better, synth.midi-mode) will be used to change
between gm, gs, xg etc, it does not make sense to add no-off
. My question is: what would be the use of a
sysex feature in FS in addition to recalling tunings ?
Mainly to catch GM/GS/XG On/Off/Reset commands to know how the source
MIDI material is expecting the synth to behave. Full GS and XG
support would be quite a pain and I doubt it will happen (lots
, 7 bits.
That is only for General MIDI (GM) compatibility
though.
No. General MIDI (GM) doesn't use banks, CC#0 and CC#32 are
ignored in GM mode
by all standards compliant devices.
GM1 was ambiguous, but GM2 does use CC#0 and CC#32.
Maybe we can try to dig into GS and XG specs
specification, and all
the other extensions.
This is not true according to
http://en.wikipedia.org/wiki/Comparison_of_MIDI_standards - neither GS,
XG and GM2 specify channel #10 as the one and only drum channel.
You are manipulating my words. I've never said the one and only. The channel
#10
is
ignored for XG (and why MMA style is not the
default...). We're kind of
stuck between sf2's standard and XG's standard, and
need to figure out
how to mediate between them.
Agreed. This issue has been already posted and discussed in
this list, so here are some relevant excerpts and pointers
different set of instruments. I suppose that some
kind of a mapping configuration file for that
particular GM sound font (for GS, XG instruments) is
better approach. This way, people can create and
share configuration files for any common GM soundfonts
and Fluidsynth doesn't have to require specific
to do the same?
1) We skip synth.midi-mode=gm/gs/xg for now, since it seems to require
additional thought and can delay the release of 1.1.0.
2) We add synth.note-off-percuss=ignore/process which defaults to ignore
(and process will behave as today). This will ignore all note off's on
channel 10 (#9
Hi Josh,
I'm sure the different specs for GM, GS, XG, XG-lite
basically made up their own specific scenarios.
From what I see, each channel is like a patch cord
into a mixer, if the Cello-ist broke a string, it may
not be ideal but a Timpani-ist or a Guitar-ist from
the openning band wouldn't
, plain and simple. Now to support 128x128 soundbanks, just find a way to allow
loading and using 128 different soundfonts simultaneously. Assuming the current
situation as the default soundfont, index=0. For GM, MIDI2, XG, the current
soundfont should map to MSB (CC0) value 0.
Supporting
as a percussion channel map. Note-offs are
indeed ignored for non-looped percussion instruments. If that is the
proper behavior with GM/GS, I think we should follow it, but only if
GM or GS mode is enabled.
I'm not really interested in getting too involved in the whole
GM/GS/XG mess
Great, I'll try the new code a bit later.
Jimmy
--- On Fri, 2/4/11, David Henningsson di...@ubuntu.com wrote:
From: David Henningsson di...@ubuntu.com
Subject: Re: [fluid-dev] Patch for channel_type, also XG drum-channel
autoswitch
To: jimmy wg20...@yahoo.com
Cc: fluid-dev@nongnu.org
soundfonts doesn't have the prognum.
From what I understand in XG sounds, the same prognum for different soundbanks
are the same type of instrument. In the simplest case, it can simply be same
instrument with different effects.
The suggested change doesn't guarrantee the same type of instrument
into consideration. I probably should
have responded before just going ahead with implementing things, kind
of a bad habit of mine, which probably comes from many years of
working solo on projects.
I'll quote your suggestions below:
1) We skip synth.midi-mode=gm/gs/xg for now, since it seems to require
This is with this weekend SVN checkout of Fluidsynth, trying with a single
soundfont for each of
SGM-V2.01.sf2
PC51f.sf2
Unison.sf2
playing the midi file from
mmacdonald.com/midi/XG/Conquistador 3K MM.MID
wiht Unison.sf2, Fluidsynth completes the music OK.
I restart jackd, fluidsynth
On Saturday, August 7, 2010, S. Christian Collins wrote:
Another option, rather than try to guess what bank select mode to use
would be to default to the GS standard, but have an option to use XG
mode--this could even be a switch added to Qsynth easily enough for us
GUI folks.
Defaulting
.
[snipped]
Let's hear how others feel about the idea. Anything that helps playing
XG-drums without too much fuss for me would be a good thing to have.
Anyone deals with any funky GS drum stuff, which these new changes may affect?
We will need your help to test your GS stuff (to make sure
something up for you.
// David
On 2011-02-03 01:08, jimmy wrote:
It seems MSB of 127, 126, 120 have been used for Yamaha/XG drum kits.
For PSR-2000 keyboard, [MSB,LSB,Prog] for MSB 126:
[127,0,xx] Various drum kits
[126,0,0] SFX Kit1
[126,0,1] SFX Kit2
[126,0,35] Arabic Kit
/msg00024.html, it sounds implied. It
lists GM, GS, XG, and GM2 as bank selection modes, but the modes available
are 'gm', 'gs', 'xg', and 'mma'. And assuming MMA = MIDI Manufacturers
Association, the group that creates/adopts the General MIDI specs, that
leads me to think mma is supposed to be GM2
It seems MSB of 127, 126, 120 have been used for Yamaha/XG drum kits.
For PSR-2000 keyboard, [MSB,LSB,Prog] for MSB 126:
[127,0,xx] Various drum kits
[126,0,0] SFX Kit1
[126,0,1] SFX Kit2
[126,0,35] Arabic Kit
For PSR-S900 (similarly in Tyros-2, Tyros-3):
[127,0,xx
=0, then use LSB as the
soundfont bank number. This is probably going to work with most XG
songs. In any other case, we need to know if the song/player follows
the GM, GS or XG standards, either when a SYX message is received, or
with a setting.
The proposal is that this Compatibility
a different sound module, because
non-existing selection reverts to using the basic GM (bank 0) 128 instrument
sounds.
If you look here:
www.mboss.force9.co.uk/miditext/Xgvoice.txt
you can see someone had taken some notes on some XG instruments mapping there.
Note the bank and prog combination
instrument sounds.
If you look here:
www.mboss.force9.co.uk/miditext/Xgvoice.txt
you can see someone had taken some notes on some XG instruments mapping
there. Note the bank and prog combination.
I believe some Yamaha keyboard manuals do list their instrument map,
especially the more
j...@resonance.org wrote:
Quoting David Henningsson launchpad@epost.diwic.se:
If there is no difference; either just add GM (preferred), or add GS,
XG and GM2 (to indicate future improvements). Does that make sense to
you?
Its tempting to add all of them and the relevant SYSEX On/Off
Quoting David Henningsson launchpad@epost.diwic.se:
j...@resonance.org wrote:
Quoting David Henningsson launchpad@epost.diwic.se:
If there is no difference; either just add GM (preferred), or add GS,
XG and GM2 (to indicate future improvements). Does that make sense to
you?
Its
current within 3-4 months).
Here's the command I run fluidsynth with jackd, using PersonalCopy's soundfont
PC51f.sf2:
fluidsynth -a jack -j -r 48000 -g 0.40 PC51f.sf2
trying with some midi files at http://mmacdonald.com/midi/XG/ , I'm using
aplaymidi to play:
aplaymidi -p 130:0 Can't Take
--- On Thu, 2/10/11, Pedro Lopez-Cabanillas
pedro.lopez.cabanil...@gmail.com wrote:
So bank numbers above 128 usually make no sense, which
is why MSB is
ignored for XG (and why MMA style is not the
default...). We're kind of
stuck between sf2's standard and XG's standard, and
need
that just keeping the previous instrument selection is any
better than trying to be a little smarter about it, depending on the
mode (GM, GS, XG, etc). If a SoundFont was loaded, which supported all
the instruments of the playing MIDI file, then there would be no issue.
Best regards,
Josh
Date: Mon, 16 Feb 2009 19:32:41 +0100
From: Peter Gebauer peter.geba...@stockholm.bostream.se
Hi again, Jimmy!
It's hard to search for these things, 99% of the hits
are online stores
selling Yamaha products. In any case, the midi events
logged contain just
one program change event, the
special percussion channel handling
gm: Ignore note-offs for all but fast Whistle and Guiro on percussion
channel
no-off-percuss: Ignore all note-offs on percussion channel
Assuming midi.mode (or better, synth.midi-mode) will be used to change
between gm, gs, xg etc, it does not make sense
: Seems GM is fixed to
channel 10. GS can use 1 channel for percussion (but I guess it
can be any channel?). XG can have any number of percussion
channels. GM2 uses channel 10 and 11 for percussion. So it seems
we'll need to deal with this in the future to some extent.
Just to make
of which notes do we
still need note-offs for, it eliminates the risk of possible stuck
notes. It can be used for GM/GS/XG, whatever. I would even say that
you could use this technique by default regardless of whether GM/GS mode
is enabled or not, because there are *no* adverse effects. Only
jimmy wrote:
--- On Mon, 10/19/09, j...@resonance.org j...@resonance.org wrote:
First - thanks for helping out with the much needed testing!
I tried again, same midi file at http://mmacdonald.com/midi/XG/Conquistador 3K
MM.MID. Note that this is a fairly busy, quick tempo/pace.
Out
not likely to happen in 1.1.2 is behavior being dynamic, i e
changed based on GM/GM2/GS/XG sysex'es in MIDI files.
// David
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
of XG
MIDI data setting the bank LSB, the preset search fallback should search
for a bank number with the LSB masked off in the event that a MSB+LSB
match is not found. This is what I currently do in my modified
FluidSynth which I link into foo_midi.
Hmm, the bank number handling seems
patch does away with == 9, by using the added field is_drum_channel. It
doesn't really change anything regarding bank selection previously in FS.
Sure I added a touch of change on XG MSB bank select based on dum select
comment in the code, doesn't have anything to do with the hard-coded == 9
!
The MIDI file format does not support more than 16 channels - this is a
limitation in the MIDI file format, not FluidSynth. You'll have to use
special API calls in order to make use of more than 16 channels.
That said; XG level 2 and level 3 seems to support more than 16
channels. Does anybody
.
That said; XG level 2 and level 3 seems to support more than 16 channels.
Does anybody know if there is a MIDI file meta event that would switch
group of MIDI channels for this track or something? I haven't found
anything myself, but it would be very useful if it existed.
Each group of 16 MIDI
CC0
and CC32 to the SoundFont's wBank value in different GM/GS/XG/GM2 modes,
which was not trivial to answer. Therefore we have the
synth.midi-bank-select option that uses different mappings depending
the mode you select. Isn't that option working for you?
As for the soundfont spec, it both
melodic banks (just like with GS and
XG) since the 128th bank value will overflow into the type bits:
000100 /* CC0 121 */
000100 /* bank 128 */
And since percussion must set CC32 to 0, you still get 128 melodic banks
(0-127), and a percussion bank (implied 128).
Though that's
Hello Jimmy,
Quoting jimmy wg20...@yahoo.com:
Hi Josh,
I tried again, same midi file at
http://mmacdonald.com/midi/XG/Conquistador 3K MM.MID. Note that
this is a fairly busy, quick tempo/pace.
As I type this, I use the mouse to drag the scroll bar in a GUI text
editor
without restarting the
synth.
In a future release, the dynamic mode switch may be implemented listening to
some SYSEX messages, like GM on[1], GS reset and XG reset. All of them
are reset messages that cancel any sound and current state on the device,
before switching to the new MIDI mode. So
standard song files, but doesn't forbid other extensions. This
may be a MIDI player use case example.
Another group of users want to make noise with my VMPK [3] in Linux. This
program is a virtual MIDI controller, emulating one of the GM, GS or XG
standards. Linux users usually prefer to run
t whether it (sh/c)ould output its messages in color.
**QXGEdit - A Qt XG Editor [4]**
QXGEdit 0.4.1 (end of summer'16) released!
QXGEdit [4] is a live XG instrument editor, specialized on editing MIDI
System Exclusive files (.syx) for the Yamaha DB50XG [14] and thus
probably a base
offset limit to 16384 (was 128).
- Desktop entry specification file is now finally independent from
build/configure template chains.
- Updated target path for freedesktop.org's AppStream metainfo file
(formerly AppData).
**QXGEdit - A Qt XG Editor [3]**
QXGEdit 0.5.0 (end-of-autumn'17) re
build
configuration.
- When using autotools and ./configure --with-qt=..., it is also
necessary to adjust the PKG_CONFIG_PATH environment variable (after a
merge request by plcl aka. Pedro López-Cabanillas, while on qmidinet
[6], thanks).
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.6.1 (winter'19
.git
https://bitbucket.com/rncbc/qsampler.git
Change-log:
- Early fixing to build for Qt >= 5.15.0.
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.6.3 (summer'20) is out!
QXGEdit is a live XG instrument editor, specialized on editing MIDI
System Exclusive files (.syx) for the Yamaha DB50X
to CMake. [21]
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.3 (spring'21) is released!
QXGEdit is a live XG instrument editor, specialized on editing MIDI
System Exclusive files (.syx) for the Yamaha DB50XG [14] and thus
probably a baseline for many other XG devices.
Web
/qsampler.git
https://git.code.sf.net/p/qsampler/liblscp
https://github.com/rncbc/liblscp.git
https://gitlab.com/rncbc/liblscp.git
https://bitbucket.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.4 (early-summer'21) is out!
QXGEdit is a live XG instrument editor
number into the next develop cycle.
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.2 (end-of-winter'21) is out!
QXGEdit is a live XG instrument editor, specialized on editing MIDI
System Exclusive files (.syx) for the Yamaha DB50XG [14] and thus
probably a baseline for many other XG devices
/liblscp.git
https://gitlab.com/rncbc/liblscp.git
https://bitbucket.com/rncbc/liblscp.git
Change-log:
- Early preparations for the New Year develop(ment) cycle.
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.1 (winter'20) is released!
QXGEdit is a live XG instrument editor, specialized on editing
/qsampler.git
https://bitbucket.com/rncbc/qsampler.git
https://git.code.sf.net/p/qsampler/liblscp
https://github.com/rncbc/liblscp.git
https://gitlab.com/rncbc/liblscp.git
https://bitbucket.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.5 (winter'22) released!
QXGEdit
.net/p/qsampler/liblscp
https://github.com/rncbc/liblscp.git
https://gitlab.com/rncbc/liblscp.git
https://bitbucket.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.6 (spring'22) released!
QXGEdit is a live XG instrument editor, specialized on editing MIDI
System Exclusive
com/rncbc/liblscp.git
https://gitlab.com/rncbc/liblscp.git
https://codeberg.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.11 (end-of-summer'23) is out!
QXGEdit is a live XG instrument editor, specialized on editing MIDI
System Exclusive files (.syx) for the Yamaha D
/qsampler.git
https://gitlab.com/rncbc/qsampler.git
https://bitbucket.com/rncbc/qsampler.git
https://git.code.sf.net/p/qsampler/liblscp
https://github.com/rncbc/liblscp.git
https://gitlab.com/rncbc/liblscp.git
https://bitbucket.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit
dit - A Qt XG Editor [4] **
QXGEdit 0.9.8 (end-of-year'22) released!
QXGEdit is a live XG instrument editor, specialized on editing MIDI
System Exclusive files (.syx) for the Yamaha DB50XG [14] and thus
probably a baseline for many other XG devices.
Change-log:
- Just bumping into the next deve
://gitlab.com/rncbc/liblscp.git
https://codeberg.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.9 (early-spring'23) is out!
QXGEdit is a live XG instrument editor, specialized on editing MIDI
System Exclusive files (.syx) for the Yamaha DB50XG [14] and thus
probably
https://github.com/rncbc/liblscp.git
https://gitlab.com/rncbc/liblscp.git
https://codeberg.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.10 (spring'23) released!
QXGEdit is a live XG instrument editor, specialized on editing MIDI
System Exclusive files (.syx) for the
://gitlab.com/rncbc/qsampler.git
https://codeberg.com/rncbc/qsampler.git
https://git.code.sf.net/p/qsampler/liblscp
https://github.com/rncbc/liblscp.git
https://gitlab.com/rncbc/liblscp.git
https://codeberg.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.12 (winter'24
https://gitlab.com/rncbc/qsampler.git
https://codeberg.com/rncbc/qsampler.git
https://git.code.sf.net/p/qsampler/liblscp
https://github.com/rncbc/liblscp.git
https://gitlab.com/rncbc/liblscp.git
https://codeberg.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.90 (s
eberg.com/rncbc/liblscp.git
** QXGEdit - A Qt XG Editor [4] **
QXGEdit 0.9.91 (spring'24 aka. v1.0.0-rc1) is out!
QXGEdit is a live XG instrument editor, specialized on editing MIDI
System Exclusive files (.syx) for the Yamaha DB50XG [14] and thus
probably a baseline for many other X
fixed a few bugs in your patch - see the attached diff.
But there was one thing keeping me from committing the fixed version:
+
+ /* if style == XG and bankmsb == 127, convert the channel to drum mode.
+ * How should newval above be calculated (same as MMA style) ??? */
+ if (style
1 - 100 of 112 matches
Mail list logo
