y the Linux kernel can be compiled for a cell phone with no supports,
or dependencies on PCI, PCI-X, PCI-E bus, VGA, XGA display, IDE hard drive,
parallel port... Knowing that it can be done, but you probably don't want that
as your default boot-up kernel for
--- On Sun, 8/5/12, jimmy wrote:
> If you still don't understand what I have written, it would
> still be a big baffling mistery for you.
Sorry, "mystery" not "mistery".
More on decoding "apt-get" command you used. From the info you posted:
>>
ise, none of jack 2.x would get installed on that
system, and you should have problem with the currently being tested FluidSynth
-- because current Fluidsynth requires jack 2.x for testing (I believe).
If you still don't understand what I have written, it would still be a big
baffling mister
ad and install
"somepackage".
So yes, while you were removing and purging some of those packages, it finally
remove enough of jack 1.x packages to let you install jack 2.x in the system.
The reverse is also true. If any packages which explicitely require some
before using the GM-default in FluidSynth XG-mode). Such soundbank sounds
much better than the GM-mode default soundbank in those hardwares. So they can
claim that XG harwares/softwares sounds much better than GM sounds. Pure
marketing B.S, it's their mapping that make GM-mode sound
to be tested again, reset the testing time period.
After a few rounds, we would have an idea of how many test-reports and what
environments each "release candidate" got tested, along with how many problems
found...
Not quite as formal as some automated test-suite, but would help along the way.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
om
FluidSynth to deal with the various info.
Outside the XG-mode via my earlier patch(es), there's no way to use multiple
drum channels, except adding the full 16-channels, remember to differentiate
those channels, may have to add rules to MIDI router of some sort, just to use
that one extra drum channel. Talking about twisted logic by some people with
their GM-specs interpretation. Sad, but true.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
ent intrepretations, configurations and
variations even years down the road. It comes down to having a flexible
interpretation to begin with. If "drums was said to be on channel 9 by the GM
specs" was the only interpretation, then the
oesn't make any difference,
so we won't change the code".
Hey, if I won't be around, at least the correct code is in there, saving
someone else the trouble of understanding the XG stuff and code it years down
the road. Heck it's been almost 1.5 years since I submitted that patch and
nothing has been mentioned. I might see Harley's Comet swing by before I see
anything new in FluidSynth at this pace.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
ons.
My other changes that you quoted, was applied for allowing any channel to use
as Drum-channel. I had patches for several different things back then,
including some SysEx patches for XG, some typo in existing code, some
inconsistent commandline parameter of volume "gain" of 5 max
about Soundfont specs, don't
care for MIDI specs, then that's your perrogatives. I do want MIDI supports.
Implementing that would take some work, but not if patches are ignored. My
rejected patch deals with that broken handling of [MSB, LSB] in a limited way
in XG-mode, but was rejected b
--- On Mon, 7/9/12, David Henningsson wrote:
> From: David Henningsson
> Subject: Soundfont banks (was: Re: [fluid-dev] OSC support)
> To: "FluidSynth mailing list"
> Cc: "jimmy"
> Date: Monday, July 9, 2012, 6:55 AM
> On 07/09/2012 03:07 PM, jimmy
quot; here.
Not in the Soundfont specs? No sounds for you!!! No where near the "old,
old" Roland GS specs for Win95/Win98 sound card hardware? No sounds for you!!!
To hell with MIDI specs, let alone MIDI-2, or anything else new.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
erest to you. This
approach helped me quite a bit.
I suppose other soundfont editors should have similar functionality. There
might be other soundfont <-> xml converter/extractor out there. I tried a
soundfont to XML extractor (written in Python) sometime a
ooping back will
need the meta events (tempo...) to play properly. There are other meta events,
too.
If you think the extra "setup time" may take too long for your usage, perhaps
an option to specify whether to play all events, or allow omitting of certain
event type(s).
Jimmy
for the volume calculation. With the default being 0.2, the
scale is already way-off to start with. If someone finds a better way to
calculate master-volume, go right ahead. I only want/need a way to adjust it,
as long as it's in there, everyone can use it however they want.
Jimmy
--- On
ulation for XG,
> I'm just not convinced that it's the right way to do.
>
So how do you suggest we handdle GM specs regarding MSB? Ignore it altogether,
just because Roland GS folks don't use it?
Jimmy
_
s, that's exactly what MSB means
in XG, and MMA calculation. Don't let LSB be the limit of sound banks
available in the system. You can use MSB to multiply your LSB up to 127 times,
assuming MSB=0 is the current default situation.
One simple way to do that is have a configuration file, for example:
different
soundfont.
How about Fluidsynth uses a configuration file to map some chunk of
128-LSB-bank-set to one of the MSB number? In other word, using multiple
GM-soundfonts files, each would have a separate MSB number. What's wrong with
that? Nothing. If anything, it opens up a whole new world of MSB to us. And
can work fine with XG MSB's, too.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
devices.
With Timidity configuration file, one can use a virtual bank mapping to select
a specific bank in one soundfont to override another bank in a different
soundfont.
How about Fluidsynth uses a configuration file to map some chunk of
128-LSB-bank-set to one of the MSB number? In other wo
ot;gain"
from 5 to 10. Let me know if those need to be left alone.
Jimmy
diff -pur fluidsynth.svnRev405.20110207/doc/fluidsynth.1 fluidsynth.svnRev405.20110207.jnSysex/doc/fluidsynth.1
--- fluidsynth.svnRev405.20110207/doc/fluidsynth.1 2011-02-07 20:29:49.0 -0500
+++ fluidsynth.s
f a bank could not be found, the channel went completely silent.
Since then, for XG midi files that uses drum bank 126, I will hear Piano. It
doesn't sound good, or right, but at least now I know something needed to be
changed (the midi file), or fixed (in the soft synth), rather than
> figure out
> how to mediate between them.
By the way, no problem running my code here. It works just fine with
Unison.sf2 . Multiple drum channels and all.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
I now get:
>
> fluidsynth: warning: Instrument not found on channel 6
> [bank=128
> prog=1], substituted [bank=128 prog=0]
>
> ...which is what it actually did, both before and after
> r406.
>
> // David
>
Hmm
> Hey jimmy,
>
> Thanks for the research. I've committed the patch now (with
> some trivial
> changes). Thanks for your contribution!
>
> And to the rest of you - this bank select handling seems to
> be a never
> ending debate, and it's not my area o
) that somebody has to work on, and there
> may be a few issues more than bank changes involved.
>
> Regards,
> Pedro
I'm about done with the SysEx's for GM/GS/XG reset, as well as the Master
Volume SysEx. Need to do a
Great, I'll try the new code a bit later.
Jimmy
--- On Fri, 2/4/11, David Henningsson wrote:
> From: David Henningsson
> Subject: Re: [fluid-dev] Patch for channel_type, also XG drum-channel
> autoswitch
> To: "jimmy"
> Cc: fluid-dev@nongnu.org
> Date: F
h 44.1 kHz, does Fluidsynth scale the sample to the appropriate pitch using
192 kHz, then resample to 44.1 kHz? Or, how does Fluidsynth do that right now?
What's recommended in this case to get better sound out of a single sample to
be use as the only sample for all 128 notes?
,0,0] always there, this is also GM-drumkit.
PDF manuals for the keyboards are available online if folks want to take a
closer look.
Jimmy
diff -pur fluidsynth.svn399.20101221/include/fluidsynth/synth.h fluidsynth.svn399.20101221.jnDrumChannel/include/fluidsynth/synth.h
--- fluidsynth.sv
uld not set LSB=0 at all --
especially if MSB is less than 64. Should Fluidsynth try to handle this
sequence of messages for XG mode at all?
-
All the above are only to set/save MSB, LSB, ProgChange values, needed for
recording Midi. Not dealing with instrument substitution portion afterwa
You are right, this patch won't work. I have to think and try again later.
Jimmy
--- On Sun, 1/30/11, David Henningsson wrote:
> From: David Henningsson
> Subject: Re: [fluid-dev] Revised patch for allNotesOff, allSoundsOff
> To: "jimmy"
> Cc: fluid-dev@nongnu.
--- On Fri, 1/28/11, David Henningsson wrote:
>
> On 2011-01-28 23:07, jimmy wrote:
> >
> > Here's the revised patch file for the new channel
> field "is_drum_channel".
>
> Thanks, but you're missing the patch :-)
>
> //
course, I prefer not having to call allNotesOff/allSoundsOff once per
channel.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
Here's the revised patch file for the new channel field "is_drum_channel".
The comment regarding GM-mode bank select is left in there. If things look OK,
can someone apply the patch? Thanks,
Jimmy
___
fluid-dev mailing
Attached is the revised patch file for handling allNotesOff, allSoundsOff for
all channels at once.
If it looks OK, can someone apply the patch? Thanks,
Jimmy
diff -pur fluidsynth.svn399.20101221/src/synth/fluid_synth.c fluidsynth.svn399.20101221.jnAllSoundsOff//src/synth
working this way all along, no behavior changes regarding FS
handling of GM-mode bank select in anyway, with or without that comment.
I will leave that part of the comment back in there.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
on what I can understand from various
bit and pieces of GM-spec docs and related documents. Basically, FS can do
whatever in this case. GM specs, and official stand on this issue is a wash,
water under the bridge, nothing, nada.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
lp to test your GS stuff (to make sure they aren't broken)
if these new changes made it into FluidSynth.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
r XG midi files yet.
If you want to override the current drumkit in the default soundfont (SF2), you
can specify both soundfont files. I believe the second soundfont will override
any soundbank/drumkit in the first soundfont.
Jimmy
___
fluid-d
t;= -1 && chan < synth->midi_channels,
FLUID_FAILED);
I didn't see similar 2 checks in the other function, and wasn't sure if I
should add those. Perhaps we could add them now that we are at it.
Thanks,
Jimmy
___
fl
--- On Tue, 1/25/11, Matt Giuca wrote:
> Hi Jimmy,
>
> I am not a FluidSynth developer, just an interested person,
> so my opinions don't represent the view of the
> FluidSynth project.
>
> This seems like a valuable generalisation of a previously
> hard-coded va
on somewhat dated fluidsynth.svn399.20101221 (5 week old)
code.
Let's hear if this is a reasonable change to the code base, or not.
Jimmy
- Patch starts below: -
diff -rup fluidsynth.svn399.20101221/src/synth/fluid_chan.c
fluidsynth.svn399.20101221.jnDrumChannel/src/synth/fluid_c
t too bad, but looking at the implementation, it is just not effecient at
all.
This patch is based on somewhat dated fluidsynth.svn399.20101221 (5 week old)
code.
Let's hear if this is a reasonable change to the code base, or not.
Jimmy
- Patch starts below: -
diff -ur fluidsynth.sv
--- On Sat, 8/7/10, Elimar Green wrote:
> From: Elimar Green
> Subject: Re: MIDI Bank Select proposal (was Re: [fluid-dev] Re: Son of ticket
> #65)
> To: "jimmy"
> Cc: fluid-dev@nongnu.org
> Date: Saturday, August 7, 2010, 9:51 AM
> This was all basicall
-introduction-midi.php
www.heikoplate.de/mambo/index.php?option=com_content&task=view&id=431&Itemid=63
www.heikoplate.de/mambo/index.php?option=com_content&task=blogcategory&id=75&Itemid=57
http://www.soundonsound.com/sos/sep98/articles/
here are fairly short sys-ex messages for XG-reset, GS-reset and possibly
GM-reset.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
fe
(similar, if possible) instrument voice or drumkit. Our only common
denominator is GM1 sound set as a required set of features.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
still have those)
will have to be part of the textual description anyway (accounts from different
systems).
Let me know if you want me to try it, give me the new web site and URL for
creating new ticket(s).
Jimmy
___
fluid-dev mai
BTW, about instrument loading fall-back scheme... my requested changes were
released as part of 1.0.9, not quite sure if it was in 1.0.8. But definitely
has nothing to do with 1.1.x changes.
Jimmy
___
fluid-dev mailing list
fluid-dev
s,
especially for soundfont (especially non GM soundfont) designers to be able to
hear at least some instrument. If they don't want to hear from a channel,
perhaps a channel mute option would be more appropriate.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
t this moment:
> http://userbase.kde.org/KMid2
>
Thanks, Pedro. I'll check it out when I got a chance.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
. But for a movie-like environment, or studio-session, should
the cache keep presets longer than 30 minutes? Or the cache is so large that
looking up a preset takes longer than allocating a new preset, then it becomes
counter productive.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
#x27;
-- with 'left', 'right' audio channels
under the Jack-MIDI tab:
'fluidsynth-mid'
-- with 'midi' port below it
or, under the Alsa-MIDI tab:
130:FLUID Synth()
-- 0:Synth input port()
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
d also parse and display
lyrics/midi-text.
It may be interesting if it (or its library) also has a separate output port
(output-only ???) for lyrics/midi-text events separately from the normal midi
port. This way, people can make their own UI, or even network-UI if they want.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
be more cache misses. This seems a little bit
> far-fetched though (not only for the CPU, ha ha). Would be
> interesting to know if prefetch instructions could improve
> the situation.
It is much more detectable on slower hardware like older PCs or laptops --
combination of slower RAM, CPU, H
--- On Mon, 10/19/09, David Henningsson wrote:
> From: David Henningsson
> Subject: Re: [fluid-dev] Re: lost connection to Jack server (svn Rev 243,
> over the weekend)
> To: "jimmy"
> Cc: j...@resonance.org, fluid-dev@nongnu.org
> Date: Monday, October 19,
--- On Mon, 10/19/09, j...@resonance.org wrote:
> From: j...@resonance.org
> Subject: Re: [fluid-dev] lost connection to Jack server (svn Rev 243, over
> the weekend)
> To: "jimmy"
> Cc: fluid-dev@nongnu.org
> Date: Monday, October 19, 2009, 11:25 AM
&g
--- On Mon, 10/19/09, jimmy wrote:
> From: jimmy
> Subject: lost connection to Jack server (svn Rev 243, over the weekend)
> To: fluid-dev@nongnu.org
> Date: Monday, October 19, 2009, 9:28 AM
>
>
> This is with this weekend SVN checkout of Fluidsynth,
> trying wit
consistent) with Fluidsynth "-v" (verbose)
option.
The machine is 2.4GHz, 1 GB RAM, fairly recent Debian Sid. May be more
problematic on slower hardware.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.
[bank=16256 prog=86],
substituted [bank=16256 prog=0]
I haven't had time to tried more files on that site yet.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
oses a default minimum-note-duration for now, and
allows for using configuration file and/or a way (passing configuration
settings via some API, or commandline arg) to change it. This way, folks can
also test against their own MIDI files and set it to their liking, or give us
feedback/suggestion as to what the better default minimum note duration shoud
be for future releases.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
, and Roland doesn't seem
to get any better brainshare with GS. Those existing MIDI files out there
still only sound best on the hardware they were created on, Fluidsynth only
need to sound the appropriate voices as the notes are played. The rest depends
on having a superb GM soundfont a
sf2 yamaha-xg-sound-set.sf2
yamaha_xg_sound_set_re-map.sf2 yamaha_xg_sound_set_re-map.sf2
Bennet's AnotherXG.sf2
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
cnically advanced, or detail specific users.
Anyone wanting the more customized/advanced feature that Fluidsynth offer would
be spending time to learn and tweak their MIDI's for the "advanced" mode in
Fluidsynth anyway. So for them to specify the "advanced" mode
course, for people who work with soundfont, or some particular instrument
range and want to try to tweek and listen to to all the samples with such
adjustments, then the per bank/program selection might be the way to go for
them.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
e simulated by running
in a separate instance of FS.
So if per channel SFX is possible, please do allow for ways to specify which
channel(s) these SFX processors should work on. You may also want to allow
users to define/specify, or loaded-on-the-fly (maybe some sample code to use)
these SFX
You are right Pedro, my bad. I remembered that wrong. I got that mixed up
with jackd and qjackctl combo.
Jimmy
--- On Sat, 5/23/09, Pedro Lopez-Cabanillas
wrote:
> From: Pedro Lopez-Cabanillas
> Subject: Re: [fluid-dev] Re: What is the best way start fluidsynth with
> zero/lo
response time settings. Bump
it up 2-4 times the minimum should get rid of most underruns with just a slight
compromise on real-time playing, which may be no worse than playing "strings",
or "synthesized voice" instruments.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
n, IRQ interrupt priorities, and
jackd info.
http://sarigama.namaste.jp/micro/la.txt
http://www.rosegardenmusic.com/wiki/low-latency_kernels
http://code.goto10.org/projects/puredyne/wiki/KernelAndSystemOptimization
https://help.ubuntu.com/community/HowT
> Date: Tue, 19 May 2009 07:28:07 +0200
> From: David Henningsson
> Here's an answer for you, jimmy, and anyone else whose
> questions can be
> shortened to "you won't break anything, will you?" :-)
>
> First, to me it seems like the current synchroni
of running multiple apps and multiple
hardware sequence players (drum machine, background sequences, and midi
keyboards... at the same time) that connect through jackd to FS playing in live
(in real time, low-latency)?
Jimmy
___
fluid-dev ma
> Date: Sun, 19 Apr 2009 12:25:30 +0200
> From: Bernat Arlandis i Ma??
> Thanks Jimmy for caring about the fate of my efforts. You
> might not know
> that everything I've done is in the public trac repository
>
> (http://fluidsynth.resonance.org/trac/browser/branche
y issues.
Not only that, document the design of these new features for 1.1.0, then having
to possibly re-explain, or changed totally in the new code base of 2.0 because
of new API would cause lots of headache for everyone involved.
Best regards,
Jimmy
___
> Date: Thu, 16 Apr 2009 20:01:04 +0200
> From: David Henningsson
> I think a wrapper (as jimmy suggested) is an almost
> must-have. I don't
> know how much incompatibilities there will be, but we have
> 10-30
> projects depending on us, so if we don't, my guess is
> Date: Wed, 15 Apr 2009 05:15:31 -0700 (PDT)
> From: jimmy
> And I don't think gleamsynth is not API compatible at all
> with fluidsynth, mostly because of data structures.
Uh, typo on my part. What I mean to say is GleamSynth is not API compatible
with FluidSynth, from wh
a real forked project because
his code can't seem to see the light of day in the code repository.
I could feel Bernat's worries. I only had a simple hack and didn't want to
re-patch FS everytime a new version comes out. His changes are major
restructuring, or morphing of sort...
und too
> restrictive for the new programming forces we should decide
> whether we
> hold to the old 2.0 plan or refrain from it and start
> another one. You
> should understand that doing long-term work on a project
> that might
> shift direction anytime isn't pleasant.
>
> --
> Bernat Arlandis i Mañó
I can see your pain :-(
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
vote of confidence on where to put most of
our efforts next.
My vote is let's go for 2.0.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
sound/seq/timer
before and after starting jackd and note any differences.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
ckward compatible. I
think that's how we call these the Most Significant Bits (higher bits) and
Least Significant Bits (lower bits) in the same 16-bit integer.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
> Date: Sun, 15 Mar 2009 18:51:06 -0700
> From: Josh Green
>
> Hello Jimmy,
>
> Sorry for the delay. I looked over your proposed
> changes. It doesn't
> seem like that is really the proper place for them though
> (would affect
> the default SoundFont
> Date: Wed, 18 Feb 2009 16:16:01 +0100
> From: Peter Gebauer
>
> 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
> Date: Mon, 16 Feb 2009 19:32:41 +0100
> From: Peter Gebauer
>
> 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
> Date: Mon, 16 Feb 2009 16:30:05 +0100
> From: Peter Gebauer
>
>
> Hi Jimmy,
>
> migth this be what happens with my Yamaha P-85 when I
> change istrument?
>
> Logged midi events when changing:
>
> 2754,M Audio Delta 1010LT:0,System exclusive,,10,f0 43 73
o.html
The voices in the extra banks align with those in the standard GM bank, thus
providing variants on the standard voices. This means that a MIDI file composed
for use with a GS or XG device will sound okay when played using a standard GM
device (because a GM device will i
th: [bank, prog: %d, %d]", bank, num,
fallback_preset->bank, fallback_preset->num );
return fallback_preset;
}
return NULL;
}
<<<<<
Please don't forget
fluid_ramsfont.c : fluid_ramsfont_get_preset()
Best regards,
Jimmy
___
till return NULL if no prog_number is found.
Of course it is just my hack at the code. It may or may not be the
appropriate place, but is the most efficient from the little that I could
understand. If it looks OK, you may want to put in the changes as appropriate,
and similar change for
f
d/Unstable). Plus some of those have versions
that only work with some older tools like (GCC 3.3) or so.
That was more hassles than I had the time to deal with.
Best regards,
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
ent the system using linear
link-list, but can be very inefficient for look up time.
Best regards,
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
o try overriding some instruments so I load up
>multiple soundfonts with FS (which qsynth shows), or on the Creative SB 5.1
>Live (which I don't know how to query).
Thanks,
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
ce and tempo at times... Rather than saying, I don't
have a viola or a flute, just butcher that section and wait for the the part
with my instrument, which is what FS does right now.
Best regards,
Jimmy
___
fluid-dev mailing list
fluid
> Hi Jimmy,
>
> Just keeping the already selected instrument when an
> invalid selection
> is received seems strange to me. Do you think that would
> create the
> desired effect in most MIDI files? It is a case of the
> MIDI file
> expecting an instrument to be p
a
PCI SB 5.1 Live! and it doesn't have any muted-channel problem I currently have
with FS.
Best regards,
Jimmy
--- On Wed, 1/28/09, Josh Green wrote:
> From: Josh Green
> Subject: Re: [fluid-dev] invalid instrument/drum selection
> To: wg20...@yahoo.com
> Cc: fluid-dev@nongnu
ore if I can help it.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
or so midi test files of the time.
I only notice the problem with this one midi file because several of the
instruments did not sound, and one instrument is panned off-center so it
sounded odd, and I took a closer look.
Best regards,
Jimmy
--- On Tue, 1/27/09, Josh Green wrote:
> Fro
t guarrantee the same type of instrument, just keep
the already loaded instrument in that channel. Currently it sets the channel
to point to invalid, non-existing instrument.
Preferably, FS should try to find any soundbank with that prognum and use that
instrument instead. Maybe you can decide what bes
od thing to look forward to if someone can
add that, it doesn't guarrantee anything regarding spontaneous crashes.
I have seen one or two midi's that plays extra fast tempo that causes FS to
crash, not sure if I have the time to track it down for the time being to even
report it.
Jim
s.
I have seen many places in FS code that assigns variables blindly, i.e. midi
program change, soundfont bank change that causes invalid instrument selection
and FS messed up that midi channel, and that channel is silenced.
Jimmy
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
"preset" variable above is NULL, the channel got set to
a NULL-preset.
Jimmy
--- On Mon, 1/26/09, jimmy wrote:
> From: jimmy
> Subject: Re: [fluid-dev] invalid instrument/drum selection problem
> To: "Josh Green"
> Cc: fluid-dev@nongnu.org
> Date: Monday, J
ou have a chance? This is low priority, casual
listening for me. Let me know if you can reproduce the problem, or if I could
be of any further help. Thanks,
Jimmy
--- On Wed, 1/9/08, jimmy wrote:
> From: jimmy
> Subject: Re: [fluid-dev] invalid instrument/drum selection problem
1 - 100 of 117 matches
Mail list logo
