These are just general observations, not legal advice.
I am fairly sure that under U.S. law there is copyright in a MIDI file only to
the extent that it represents a creative expression. That creative expression
would still be present in an audio file, so the copyright would persist. If the
n. If you can arrange to mix only a few
MIDI channels into one of a large number of speakers, then your final mixing
is air mixing, which doesn't distort. Everything before you get into the air
is subject to electrical distortion that can be challenging to manage.
Best,
Jim Henry
___
Of the various on-line explanations I looked at, I thought this was the
best:
http://www.philrees.co.uk/articles/midimode.htm
Jim Henry
_
From: fluid-dev-bounces+jim.henry=sbcglobal@nongnu.org
[mailto:fluid-dev-bounces+jim.henry=sbcglobal@nongnu.org] On Behalf Of
CERESA
e
the note to legacy MIDI hardware.
Jim Henry
-Original Message-
From: fluid-dev-bounces+jim.henry=sbcglobal@nongnu.org
[mailto:fluid-dev-bounces+jim.henry=sbcglobal@nongnu.org] On Behalf Of
R.L. Horn
Sent: Tuesday, March 10, 2015 11:09 PM
To: FluidSynth mailing list
Subject: Re: [
expression control, then you can use CC 11 to control the channel
volume to mix the channels.
Jim Henry
On 1/18/2014 1:58 PM, Martin Larsson wrote:
Yes, I can confirm that this is the case for my midi files (which are
generated from Lilypond). My CC commands aren’t printed anywhere, but
in the
The effect of the sustain pedal is determined by the sound font.
On 11/14/2013 10:39 AM, Eric Gagnon wrote:
EG:
I think (and hope) it is the expected behavior.
In performing with such an instrument sound (oboe, for example), I
sometimes use the sustain pedal to hold out a note while I shift m
On 10/19/2010 12:27 PM, David Henningsson wrote:
On 2010-10-19 09:47, Graham Wykes wrote:
Would there be value in looking at the patch than Jim Henry mentioned
(given that it has been effectively tested for many years by hundreds of
users of Miditzer) to see whether it is compatible with the
an playing
them, I certainly support such an effort.
Jim Henry
On 10/18/2010 3:02 PM, Pedro Lopez-Cabanillas wrote:
Talking about my personal interests, MIDI applications often need to
parse
MIDI files to manipulate MIDI events (sometimes interactively) before sending
the events to the MIDI
There are no reports of problems from any of the 9 Miditzer testers.
Jim Henry
On 8/28/2010 5:55 AM, David Henningsson wrote:
A few more weeks have passed and I've had a lot to do (both work-wise
and family-wise), but I've updated the documentation, and I don't think
we have an
re as short as those that Bernd suspect are causing the crackle he
observes.
Jim Henry
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
is so difficult to anticipate what they will try to do and to grasp the
level of understanding or lack thereof. I do front line support of the
Miditzer, which has a lot of users who know almost nothing about MIDI.
The experience gives you a very different perspective on what software
needs to
ntended to continue using MSB unchanged?
Jim Henry
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
The Miditzer testers confirm the fix for increasing polyphony.
Thanks for the quick work with such minimal information!
Jim Henry
On 8/4/2010 1:58 PM, David Henningsson wrote:
2010-08-04 04:07, Jim Henry skrev:
We have also discovered that there is probably something more required
as a
s. Can anyone make a
suggestion of what that might be?
Thanks,
Jim Henry
___
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
ddity. Initially I got "Detecting C compiler ABI info -
failed". I had the FluidSynth and build directories down in my directory
tree about 5 levels. Moving these directories to the top, i.e.
C:\fluidsynth, made the problem go away.
Best Regards,
Jim Henry
On 7/26/2010 10:34 AM, Pedro L
at is, not the ocean. Well I do know where the ocean is
too. OK, maybe this explains why I got VS2010 all screwed up.)
Best Regards,
Jim Henry
On 7/26/2010 10:34 AM, Pedro Lopez-Cabanillas wrote:
Hi,
I've tried VS2010 Express to build FluidSynth, without incidents. I've used a
Visual Studio uses the Windows system environment variable INCLUDE to
set the directories for included headers. Can Cmake find those files or
do the include directories need to be on the PATH?
Jim Henry
___
fluid-dev mailing list
fluid-dev
"__inline"
succeeds? This change also made the big endian check fail, which failed
originally but worked when I used the VS command prompt.
Jim Henry
Check for working C compiler using: Visual Studio 10
Check for working C compiler using: Visual Studio 10 -- works
Detecting C compiler ABI
that are needed
for Windows.
Thanks,
Jim Henry
On 7/25/2010 5:32 AM, Pedro Lopez-Cabanillas wrote:
On Sunday, July 25, 2010, Jim Henry wrote:
Performing Test _have_inline - Failed
Performing Test _have___inline__ - Failed
Performing Test _have___inline - Failed
There is a problem
When I run CMake I got the report below. Are the various "not found"
messages things I need to correct? Or just the error messages in red?
Any thoughts on where I should be looking for my problems?
Thanks,
Jim Henry
Check for working C compiler using: Visual Studio 10
Check for work
This sounds good to me.
Jim Henry
On 7/16/2010 11:02 AM, Graham Goode wrote:
Hi Guys,
With Pedro's help I was able to generate an MSVC build system and
succesfully build fluidsynth today. So I think that it should be ok to
get rid of the winbuild directory so long as there was a small H
arily."
Unfortunately I won't have time to do any testing of FluidSynth with the
Miditzer before this release but if MSVC is not supported that will
likely defer updating FluidSynth with the Miditzer until the MSVC side
of things are addressed.
Jim Henry
On 7/16/2010 12:13 AM, Elimar Green wrot
I add a hearty second to this advice.
Jim Henry
Miditzer author
On 5/18/2010 2:11 AM, Pedro Lopez-Cabanillas wrote:
I would like to advice against using another random hosting service,
risking
to lose control again in the future. It's better to be stuck in some
stablished service provider
doesn't give you a percentage but it does tell you that
there are quite a few users who need low latency. One thing that helps
us is that real organs have a noticeable latency too. So sometimes we
just tell people to suck it up.
Jim Henry
Louis B. wrote:
Does any body have an any idea
release before I'd care to comment on
anything as I suspect that most if not all of these things have already
been addressed. The version of FluidSynth we are using is at least 2
years old. Obviously nothing is terribly wrong as we have many happy users.
Best,
Jim Henry
Miditzer author
. The
integration of FluidSynth with the Miditzer has taken the Miditzer to
new heights of ease of installation that will open this program to a
whole new class of users who previously found the task of using sound
fonts daunting.
Jim Henry
nnels" where the result is obvious.
Hope this helps,
Jim Henry
CERESA Jean-Jacques wrote:
After building FluidSynth 1.0.5 (from the .tar files) using VS 6.0 on
a Win 98 plattform and
lauching FluidSynth.exe from a command line requesting to play a
midifile has the following behavior:
The
27 matches
Mail list logo
