Re: [fluid-dev] Chrome Native Client

I've actually been thinking about doing the same thing (although I haven't started or done any kind of feasibility study). However, I know my way around NaCl/Pepper pretty well (I have been working with the Pepper team to add new APIs). I can't think of a reason why this would be a problem (other

Re: [fluid-dev] Default soundfont file: synth.default-soundfont

This is fantastic! I remember that conversation two years ago. Thanks for doing this. On Sun, May 5, 2013 at 7:25 PM, David Henningsson wrote: > I just pushed two commits to trunk that enables us to load a default > soundfont file if none specified, as discussed two years ago [1]. > > The defau

Re: [fluid-dev] Rendering midi to file.

Hi, Wow, I thought this was documented but I can't find it in the docs either. It's the -F or --fast-renderer command-line flag (which is in the man page). The command I use is this: fluidsynth -lni -r 48000 -F $(SONG).wav $SOUNDFONT $(SONG).mid Where 48000 is the sample rate you want. HTH O

Re: [fluid-dev] FluidSynth MIDI driver for DOSBox

Thanks Chris! ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev

[fluid-dev] FluidSynth MIDI driver for DOSBox

Since I mentioned on the RC testing program about using FluidSynth as a DOSBox backend, I thought I'd explain. I recently played through all of the King's Quest games (marvellous historical look at the evolution of adventure games) in DOSBox and I came up to King's Quest VII and the music didn't w

Re: [fluid-dev] FluidSynth 1.1.6-rc1 ready for testing!

Tested my three things: - Building on Ubuntu: Good. - Fast rendering: Good. - As a DOSBox backend: Good. I also tested that this new version plays a song up until the EOF instead of just the last note (the fix I made for this release), and that worked. Also, I note that the API document

Re: [fluid-dev] Proposal: FluidSynth tester program

A warning for anybody performing a test: you should ensure that you are testing against the RC version of libfluidsynth, not just the fluidsynth binary. This will depend on the specifics of the system, but the easiest way to ensure this is to delete any old versions of fluidsynth you have around.

Re: [fluid-dev] Proposal: FluidSynth tester program

> > Sounds good. So we are not supposed to directly edit the wiki, but rather, > send email in reply to your RC announce email? > Never mind, I just saw your other email. ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/li

Re: [fluid-dev] Proposal: FluidSynth tester program

> As for Google Doc in particular, that might be elegant, but it would also > require us to all get gmail accounts (I assume?) Yes it would. and I'd like to keep things in one place if not terribly inconvenient. > So I made a simple wiki table instead - I doubt people would mess with it, > and a

Re: [fluid-dev] Proposal: FluidSynth tester program

Hi David, Team, Sorry to be a late voice in this. If you put out release candidates, I'll test them in a couple of use cases (basically all of the cases I use FS for): - Building under Linux (I'll typically be running the latest build of Ubuntu). - Fast-rendering a collection of MIDI fil

Re: [fluid-dev] Soundfont banks

I really don't want to fuel the fire here, but I'd just like to speak with some experience on both sides of the patch/pull game. You and Pedro seem to stick with only what you prefer with the Soundfont > specs and GS-specs, both of which only deal with 128 soundbanks. > I've been observing this c

Re: [fluid-dev] Problem in fluidsynth (Ubuntu 11.10) still in Ubuntu 12.04

> The version in the of the PPA fix was "1.1.5-1ubuntu1-diwicppa", which is > (I think) the same level number as the installed software (something like > "1.1.5-2"?), so the updater may not think the fix is applicable (that the > fix is older than the installed package). > Right, that is probably

Re: [fluid-dev] Problem in fluidsynth (Ubuntu 11.10) still in Ubuntu 12.04

> So I guess we need to solve this problem yet again. > Wait, why do we have to solve it again? Isn't the problem simply that the patch hasn't made it into Ubuntu packages, and the PPA wasn't built for precise? First, a workaround. In your /etc/apt/sources.list, you probably have something like t

Re: [fluid-dev] Compiling on Windows - how to use --fast-render?

I wouldn't bother with all that Rosegarden stuff. Since Dr. Leo has already almost worked out how to use the fast exporter, it seems much easier than having to manually wire up several GUI programs. Pedro's advice is exactly what I do. Perhaps I'm biased towards command line, but I find that much

Re: [fluid-dev] Compiling on Windows - how to use --fast-render?

Hi, I'm on holiday right now so I can't test this suggestion, but from memory, here's what I do. FluidSynth has an option to set the sampling rate of the output. Sox has an option to specify the sampling rate of the input. Just set them both to the same value (an appropriate one is 44000, IIRC) an

Re: [fluid-dev] commercial software

Hi Christian, Hi > > if somebody wants sale a commercial software which use FluidSynth > 1 - is it possible ? > Yes, it is possible. FluidSynth uses the LGPL license, which permits commercial use, as long as you follow the rules of the license. The full text of the license appears here: https://

Re: [fluid-dev] OSX 10.6 build symbol problem

Hi Jeff, I'm not an expert on the Fluid build system, and I don't use OS X, but: > I didn't use CMake As far as I am aware, the non-CMake build system for FluidSynth is deprecated and no longer maintained. You probably need to find a way to build it using CMake. I'm sure some of the developers c

Re: [fluid-dev] Sending commands for fast renderer

> >Doesn't the -f option allow one to indicate a file containing shell > commands, > including reverb/chorus control? Sorry if I am missing that part of the > discussion. > Sorry I never replied on this. I finally got around to testing it: yes it does work, rendering my previous source code

Re: [fluid-dev] Link error for iOS

> I'm sorry to read that. The fact is that there isn't any legal uncertainty; > you can use and run FluidSynth under iOS like any other operating system. > The > only concern was raised about distributing FluidSynth in Apple's AppStore, > but > that is another matter. You only need to respect the t

Re: [fluid-dev] Link error for iOS

Hi Mingfen, I don't know enough about iOS to answer your question. But as an aside, I will just inform you, if you aren't already aware, that there is unknown legal status surrounding the use of FluidSynth on iOS due to the LGPL and Apple licenses. Please consider the following page for informatio

Re: [fluid-dev] Sending commands for fast renderer

On Wed, Nov 16, 2011 at 9:47 PM, Edenyard wrote: > > Speaking as a complete non-programmer, but an avid user of Fluidsynth, > please may I add my support for Matt's suggestion of a settings file. > > This seems to be the way that most things are configured in Linux. I > imagine that the idea is t

Re: [fluid-dev] Major degradation in sound quality & cpu usage going from Ubuntu 11.04 to 11.10

> ** > Remember also that I am using kubuntu (KDE desktop), though with the > "low-fat" settings (which seem to help a lot). I am experimenting with > kubuntu again because the missing-menu-bar syndrome of the Ubuntu Unity > desktop they are forcing on everybody (much like Microsoft attempted to >

Re: [fluid-dev] Sending commands for fast renderer

> Ordinary users are not going to want to use the command line. Although it > is useful for wrappers to use, a non-technical user will shy away from > anything done in the command line. > Well that's why there is QSynth, right? (I haven't used QSynth much personally.) What we are talking about h

Re: [fluid-dev] Sending commands for fast renderer

> > The long-term visionary thought is that we have too many ways of > controlling the server: through settings, through command line, through the > shell, through the API - all these have different semantics, and as a > result some configuration is available one way but not the other, leading > to

Re: [fluid-dev] Sending commands for fast renderer

> You can also programmatically control almost everything via midi CC > messages and a carefully edited soundfont. That would work in your > case, although it's a bit of a faff to set up. > Right, so I tried adjusting the "Reverb" knob in Rosegarden (connected to FluidSynth) and didn't hear much d

[fluid-dev] Sending commands for fast renderer

I'm just coming to terms with how to send commands to FluidSynth to control things like reverb (specifically, I want to control reverb). I'm under the impression that while a few things can be controlled from the command-line (such as gain), most things (such as reverb) cannot be. There are a few

Re: [fluid-dev] Major degradation in sound quality & cpu usage going from Ubuntu 11.04 to 11.10

> I successfully compiled FluidSynth (1.1.3) on Ubuntu 11.10, and installed > it, and the problem went away. > OK so there are four configurations of interest, and it seems that (maybe?) you've only tried three: 1. FS 1.1.3 on Ub 11.04 (i.e., default FS on Ub 11.04) 2. FS 1.1.3 on Ub 11.10 3. FS

Re: [fluid-dev] Major degradation in sound quality & cpu usage going from Ubuntu 11.04 to 11.10

Hi Aere, What process do I need to go through to have this problem evaluated as to > whether it is officially a 'bug' or not? > First we need to determine whether this is actually a problem with FluidSynth 1.1.4 or if it's caused by interaction with something else in Ubuntu 11.10, such as Jack. I

Re: [fluid-dev] Major degradation in sound quality & cpu usage going from Ubuntu 11.04 to 11.10

Hi Aere, Thanks so much. I wasn't expecting you to be this helpful! I skimmed the guide -- it looks like it will be of use to me. To the mailing list: I apologise for diverting this thread off from a bug report. Hopefully others will find it helpful too. Matt

Re: [fluid-dev] Major degradation in sound quality & cpu usage going from Ubuntu 11.04 to 11.10

> I need JACK because I include audio files in my sequences. I can even use > it on a 450 megahertz machine. I've learned a lot about using it in the > past few years. I use Rosegarden, and it's easiest to record audio tracks > using Rosegarden. > Okay. I might try it again if I need to include

Re: [fluid-dev] Major degradation in sound quality & cpu usage going from Ubuntu 11.04 to 11.10

Aere, thank you for reporting this issue. I'd be willing to test this out but I actually have a deadline soon for some music I need to compose with FluidSynth. I can't have FluidSynth break in the next few weeks. Therefore, I'm very glad you warned me and I'll hold off upgrading to 11.10 until I fi

Re: [fluid-dev] Sustain long fadeout a property of the synth or the font?

Just on a side (musical) note. With Piano, the "Sustain" pedal undamps all > the strings so you do get sympathetic resonances AND the notes die away > slowly with the pedal held. So it seems the Yamaha is modelling this. But > then, on a piano, the notes die away even if you hold the keys; one o

Re: [fluid-dev] Sustain long fadeout a property of the synth or the font?

> But to simulate the other piano strings resonating in sympathy when the > sustain pedal is pressed then you want to have some chorus/echo effect at > the same time as the sustain pedal is pressed. > > If the piece has been recorded from live keyboard playing then removing the > sustain pedal will

Re: [fluid-dev] Sustain long fadeout a property of the synth or the font?

> It wouldn't be that explicit. You would do it by hooking a modulator > to some CC input and using it to extend the volume decay phase - you > can do that in the soundfont or the synth. > > However, I don't see a way to do it with the sustain pedal, since that > suppresses all noteoff events while

Re: [fluid-dev] Sustain long fadeout a property of the synth or the font?

> On Roland midi pianos they simulate the effect when the sustain pedal is > down of the other undamped piano strings resonating in sympathy when a piano > hammer strikes a single note? > I suppose it could be that. For me it works on non-piano instruments too. I have a Yamaha PSR-550. Well, this

[fluid-dev] Sustain long fadeout a property of the synth or the font?

Hi fluid-dev, I have a question about the synth. I've noticed that my music keyboard's built-in synth has a particularly nice property that if the key is released while the sustain pedal is pressed, the note will begin to fade out. In other words, pushing a key and holding it is *not* the same as

Re: [fluid-dev] Determining midi file track for an event

It looks like there is no way to do that. The tracks contain events, but the events don't link back to the tracks. That could easily be added, but at a cost of, I suppose, 4 bytes per event. ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.no

Re: [fluid-dev] Should playback_callback receive MIDI file events?

> > So the question is what to do about the SET_TEMPO event? I think the most > reasonable at this point would be to both handle it and pass it on to the > callback, even if that would disable the callback's possibility to > override/handle the set_tempo event itself. > Yes, but a more general que

Re: [fluid-dev] Fast renderer end of track

Yeah I guess that would work (although I'd prefer to properly detect when all the sound has died out, rather than than just waiting "a few seconds"). I hadn't thought of that. But there's still something "dishonest" about being told (by the MIDI file) "this song ends right now," and FluidSynth goi

Re: [fluid-dev] Should playback_callback receive MIDI file events?

> Please do send all events (including meta events). Perhaps you don't need > them with your Midi files, but I have work with Midi segments that changes > tempo (perhaps even time signature 3/4 <-> 4/4) on the fly. So looping back > will need the meta events (tempo...) to play properly. There ar

[fluid-dev] Should playback_callback receive MIDI file events?

This continues a discussion started in the bug ticket #101 ( https://sourceforge.net/apps/trac/fluidsynth/ticket/101) (between myself and David Henningson). Recently, a feature was added allowing the user of the FS API to register a custom playback_callback function, which is called every time a M

Re: [fluid-dev] Fast renderer end of track

> > Fixing it on the FluidSynth side seems ugly to me: What if EOT occurs with > a everlasting note on? What about time to let the reverb decay after > playing? > > The issue has been brought up before, and I vaguely remember that I saw > some other implementation had added a parameter, something

Re: [fluid-dev] Another application using FluidSynth announced

> > Would the following text be suitable to put on the wiki, and represent the > sort-of consensus: > === iOS and the App Store === > > It is questionable whether iOS and the App Store can fulfil the > requirements of the LGPL. From a long thread on the fluid-dev mailinglist > [insert link to archi

Re: [fluid-dev] Another application using FluidSynth announced

> I get an iPhone, and somehow I purchase the Wesnoth game from the App Store > paying $3.99, enjoying the experience (of playing, not paying). Some time > after, I discover some rough edges in the game that I would like to soften, > and have read that Wesnoth is released under the GPL, so I get th

Re: [fluid-dev] Another application using FluidSynth announced

> I wasn't suggesting that remaining LGPL would negatively impact > FluidSynth.  I was simply trying to find a solution to the issue at > hand, since I've worked a lot with embedded systems and thought that > the discussion may have just been about the "static library" issue.  I > probably should h

Re: [fluid-dev] Another application using FluidSynth announced

Pedro: > I find it disgusting the attitude of > Rusty Russell regarding the Wesnoth game. I can understand his disagreement > against selling the game in the App Store, but what bugs me a lot is the > arrogance of thinking that his license interpretation is the only valid > against the rest of the

Re: [fluid-dev] Fast renderer end of track

I finally got around to looking at this issue (thought I'd take a break from arguing about licensing and actually contribute!) It turns out this issue is really easy to "fix", but much harder to *really* fix. To elaborate: 1. To "fix" the issue, all I had to do was change fluid_midi so it doesn't

Re: [fluid-dev] Another application using FluidSynth announced

> A BSD license is not equivalent to a liberal interpretation of the LGPL, that > is: allowing the distribution of FluidSynth and derived works by any channel, > including the App Store, with the conditions (required by the LGPL, not by the > BSD license) that 1) when the source code is modified, i

Re: [fluid-dev] Another application using FluidSynth announced

> For point 3, I think it fails because you can choose to distribute the > modified source code outside App Store, and it'll be available to use for > anyone who fulfils points 1. and 2. That's a good point, but I think it's all about whether you're distributing the binaries or the source. Remembe

Re: [fluid-dev] Another application using FluidSynth announced

OK thanks for correcting, Graham, > So point 2 is false and point 3 is true if ONLY using the App Store... > I can get the sourcecode, compile it myself in my OSX environment and > connect and upload the app to 100 iOS devices... Well we are assuming use of the App Store (jailbroken devices are l

Re: [fluid-dev] Another application using FluidSynth announced

Pedro: > Yes, you can release a GPL application that requires proprietary operating > systems and compilers. Nothing is said about money, though. Yes, you can release a (L)GPL application that requires proprietary operating systems and compilers. That is why it is valid to release FluidSynth for W

Re: [fluid-dev] Another application using FluidSynth announced

> I don't agree. His interpretation of free software licenses is unacceptable > for me, so please don't use FluidSynth > Wiki to express that personal opinions in the name of the whole project team. OK, I won't change anything. ___ fluid-dev mailing li

Re: [fluid-dev] Another application using FluidSynth announced

>> You said that Xcode is free. > > I've said that it is "gratis". And that GCC, the compiler included is also > free software. Sorry. When I said "free" I meant "gratis". > You are wrong with the assumption that free software implies "gratis" as well. The "free as in freedom" of free software

Re: [fluid-dev] Another application using FluidSynth announced

> You are assuming too much here. We don't know under which license Rouet > Production is going to release his product in October. Hmm, I possibly side-tracked this thread a bit. In my post, I was speaking generally about coming up with a consistent policy for this sort of behaviour, not specific

Re: [fluid-dev] Another application using FluidSynth announced

> I would agree that an official stance from the project would be a good > thing. As it stands, we don't have a legal entity owning all the code, and > I'm hesitant to try to assemble one given the difficulties collecting > copyright assignments for both past and future contributors. > Therefore, t

Re: [fluid-dev] Defining a standard directory for soundfonts Was: First Try Failure

> David: > But I'm not completely sure about the SOUNDFONTPATH thing - how would that > be used? Is that just to make people write foo.sf2 instead of > /usr/share/soundfonts/foo.sf2? It still wouldn't give FluidSynth itself > something to load as fallback. Oh I see. I thought you were suggesting a

Re: [fluid-dev] Another application using FluidSynth announced

This issue has come up several times on the mailing list. It might be helpful to have a statement on the FluidSynth trac page explaining the project's position on use of the software in the Apple App Store, and similar restricted environments. There is already an FAQ question about this: http://so

Re: [fluid-dev] Defining a standard directory for soundfonts Was: First Try Failure

>> Question is whether this stuff should actually be in FluidSynth or in >> its clients. If the client does not specify a soundfont on the command >> line, it might be that he/she wants to load it as a shell command. >> Maybe yet another switch --load-default-soundfont (and corresponding >> API thi

Re: [fluid-dev] Defining a standard directory for soundfonts Was: First Try Failure

That's a good idea. That way, you would be able to just type 'fluidsynth ' to play a song. Can I also recommend having a standard environment variable SOUNDFONTPATH or similar which contains a colon-separated (semicolon on Windows) list of paths to search for soundfonts. That would be similar to L

Re: [fluid-dev] First Try Failure

I have never got FluidSynth working with Jack. (I think I have once but the sound wasn't right and Jack itself was quite crashy.) I just use the ALSA back-end, which should be fine on Linux machines unless you seriously care about real-time (from what I understand). Just use -a alsa as a command-l

Re: [fluid-dev] FluidSynth Integration in iOS

rs have indicated that it might be a problem.) Matt Giuca ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev

Re: [fluid-dev] SONAME Bump?

I agree with Andrew's first paragraph (and I don't know enough about libtool to endorse the second). > Is it something that alone calls for a new release (1.1.5) or can we just > update svn? What implications does bumping the SONAME have? The Fluidsynth soname is currently libfluidsynth.so.1. As

Re: [fluid-dev] [ANNOUNCE] FluidSynth 1.1.4 released!

I'm not familiar with CMake or Fedora, but I do know how Debian packages work. It sounds like a difference of opinion between the upstream (FluidSynth) and distro (Fedora) -- these sort of differences happen all the time. In Debian, there is a system in place for maintaining patches against the ups

Re: [fluid-dev] [ANNOUNCE] FluidSynth 1.1.4 released!

Great work, David. Thanks for keeping everything going. It is definitely a useful tool for a lot of musicians and game writers (of which I count myself in both categories). Matt ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mai

Re: [fluid-dev] Fast renderer end of track

Good point, I've always had this problem and it would be good to get it fixed. There is a specific End Track message in the MIDI file so it shouldn't be too hard. As a workaround: when I write music for FluidSynth, I always create a note about a bar after the last "real" note and set its velocity

Re: [fluid-dev] Juggle act using fluidsynth.

Wow, that's great. I will have to show my juggling friends; they'll be quiet impressed. ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev

Re: [fluid-dev] Patch for handling midi note events

Wow, that sounds like a fantastic use of FluidSynth. If you perform it, can you post a video to this mailing list? ___ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev

Re: [fluid-dev] FluidSynth backend for SDL_mixer

Great work, James. I will have to try it out some time. ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/fluid-dev

Re: [fluid-dev] Building with -ansi

> It doesn't build, though. FluidSynth source code is not ANSI C compliant. > MSVC is C90 with a few additional features of C99, but not including the > "intermingled declarations and code" syntax. See: > http://en.wikipedia.org/wiki/C99 > OK, that makes sense. Instead of the "-ansi" flag, you ma

[fluid-dev] Building with -ansi

Hi, My apologies for causing bug #97. Judging by plcl's fix: http://fluidsynth.svn.sourceforge.net/viewvc/fluidsynth/trunk/fluidsynth/src/midi/fluid_midi.c?r1=408&r2=411 I declared a variable not at the top of a function and didn't cast a vo

Re: [fluid-dev] LicensingFAQ

> I'm not exactly sure what you mean here. There is no problem in statically > linking BSD with LGPL code as long as you redistribute the entire source > (BSD + LGPL parts) with your binary, right? So then it would not be the > linking or the license combination that's the problem, it becomes only

Re: [fluid-dev] LicensingFAQ

That's a good summary. I would just add one thing: > Can I include FluidSynth in my closed-source commercial project I would add to this section "The same advice applies to projects released under permissive licenses (e.g., BSD or MIT). Because such licenses permit closed-source redistribution, th

Re: [fluid-dev] Making MIDI player read from a buffer

Thanks very much David. It was great working with you throughout the concept and implementation of this new feature. Also the adding an example in the documentation and for providing easy links > in the email above was much appreciated! > No problem. I love Launchpad. I really recommend anyone w

Re: [fluid-dev] Making MIDI player read from a buffer

I have updated the midi-buffer branch with the previous two suggestions: 1. fluid_player_add_mem now copies the buffer before it stores it, so the caller can now free it immediately (and it is now the caller's responsibility to free). 2. Internally, fluid_midi_file now uses int buf_len and buf_pos

Re: [fluid-dev] License question

Hi Chris, Note that FluidSynth is licensed under the GNU Lesser General Public Licenseversion 2 (LGPL), not the main GPL. This is a slightly different license which specifically allows what you are trying to do (linking the LGPL library

Re: [fluid-dev] Questions about soundfont, voice rendering, pitch shift...

> I'm trying to make a soundfont from a single audio sample (somewhere > between octave C3-C4). The sample is about 4 seconds. So it is set to the > whole range of notes (0-127). > > What happens is the lower octave notes seems to lose some volume. > > More problematic are the upper octave notes,

Re: [fluid-dev] Fluidsynth stops playing when stdout is piped

> > So when you > > disconnect, suddenly all the music will come rushing out (do they get > > played in the correct time, or do you hear all the notes literally at the > > same time?). > > All at once. > OK, so FS is probably trying to play all the notes at a certain time offset from the start of

Re: [fluid-dev] Fluidsynth stops playing when stdout is piped

> subprocess.Popen(["fluidsynth", "-sli","-a", 'alsa', "-j", > '/usr/share/sounds/sf2/FluidR3_GM.sf2'], stdout=subprocess.PIPE, > stderr=subprocess.PIPE) > > This renders the screen output invisible, but if I have a number of > simultaneous connections sending commands, after a short time the audio

Re: [fluid-dev] Stopping fluidsynth via a socket

I've never used Fluid with sockets, so I'm trying it out now. What you're doing really is nothing to do with Python (I don't think), so we can simplify it just by running it on the command-line, and using netcat(or telnet) to communicate over the socket: $ flu

Re: [fluid-dev] Propose changes for drum channels support

> The code has been 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. > OK cool. What I meant was, if a comment says "this might need to be fixed" and you

Re: [fluid-dev] Propose changes for drum channels support

> I mean that the (channel==9) has been the hard-coded hack at the time, and > is now replaced by the new hack "is_drum_channel" field. At initialization, > the new code still hard-code a 9, but not anywhere else as they were > previously. > Yeah, but the comment was about bank selection (and tha

Re: [fluid-dev] Propose changes for drum channels support

> I'm not a FS dev either. Just seeing something I may want to use isn't > there, so I just take a crack at it. Everyone on this [fluid-dev] list is > one way or another interested in the coding/development side of FS one way > or another. That's why I ask for opinions instead of contacting just

Re: [fluid-dev] Propose changes for drum channels support

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 value. Given that your new flag will default to 0 for all channels and 1 for channel 9, it

Re: [fluid-dev] Making MIDI player read from a buffer

Hi David, In response to your post here: http://lists.nongnu.org/archive/html/fluid-dev/2011-01/msg3.html > Well, for the memory allocation issue it sounds like we both are leaning > towards #5 as in copying the memory. I don't think the > inefficiency is an issue and it gives FS the most op

Re: [fluid-dev] FluidSynth backend for SDL_mixer

Hi David, Thanks for replying. If you don't mind, I'll take this conversation (about MIDI buffers) to the other thread ("Making MIDI player read from a buffer"), and stop CCing James, Sam and Ryan. PS. Ryan, if you're reading this, I heard your FLOSS Weekly interview a couple of years back (on SD

Re: [fluid-dev] FluidSynth backend for SDL_mixer

> Matt, how are things on your end? Were you waiting for some feedback? Hi James, Yes, I wasn't sure how to proceed, because I basically finished the patch. There was a discussion about the memory allocation strategy (since the memory needs to be allocated by the user) which was never decided on,

Re: [fluid-dev] Building the Doxygen documentation

> This README file instructions belong to the auto-tools based build system. > I've updated it with the specific details for each build system. > Ah that works now. Thanks. I must have been trying to run it from the root directory, rather than the build directory. _

Re: [fluid-dev] Making MIDI player read from a buffer

> Many thanks for this. I never did find the time to finish up my > SDL_mixer patch and send it upstream because life has taken over but > this looks great. Tell me about it ... took a long time to get this buffer patch done as well. > I look forward to cutting my patch in half. :) > Well the

Re: [fluid-dev] Making MIDI player read from a buffer

Note that in my example, I was forced to malloc and copy the buffer; this copying approach would let me simply send a pointer to the global buffer in to FluidSynth. Matt Giuca ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/fluid-dev

[fluid-dev] Building the Doxygen documentation

I had a bit of trouble building the Doxygen docs for FluidSynth. I've sort of resolved it now, but I'll still report the problems I had. It looks like it has undergone "CMakeization" but I can't get it to work properly on Ubuntu 10.10 (doxygen 1.7.1). I tried the following: 1. cd doc ; cmake .

Re: [fluid-dev] syncing fluidsynth with sampled audio

> I would like to find a way to sync midi playback with some recorded audio I > have. I'm not planning on using any audio driver. I want to pull the audio > data using fluid_synth_write_s16(). > I'm not quite sure how the fluid_synth_write_s16 interface works, but I don't think it does its own tim

[fluid-dev] Incorrect error semantics in fluid_midi.c

I have opened a new ticket for a minor issue in fluid_midi.c (which I bumped into trying to merge to my midi-buffer branch ( https://code.launchpad.net/~mgiuca/fluidsynth/midi-buffer)). https://sourceforge.net/apps/trac/fluidsynth/ticket/94 I got an email from SourceForge when I registered the ti

Re: [fluid-dev] MIDI files cannot be rendered using certain svn revs

It still works fine for me, on Ubuntu 10.04. Are you on a Mac? I'm guessing you might be, because the commit log for r388 (which you claim to be the start of the breakage) is "Mac CoreAudio driver adapted to AuHAL." > MIDI file rendering works in revisions 387 down to 385 Do you mean it is also b

[fluid-dev] Re: fluid_midi: Bug handling invalid MIDI files

So this bug (ticket #92) was fixed in r392. There's a slight problem with the fix. In the patch I supplied, I had it "return -1" in the event of no characters being read. Since it's emulating getc, I perhaps should have returned the constant EOF (-1), but since all the calls to this function check

Re: [fluid-dev] About the trac tickets

Hi David, Thanks for that good clarification. I've been confused as to whether we were supposed to be using trac or not. Perhaps we can create some kind of "virtual" sf.net user, that owns all new > tickets, and has the fluid-dev list registered as his "home email" so that > all ticket notificati

[fluid-dev] Re: fluid_midi: Bug handling invalid MIDI files

Since I was told off for not using the bug tracker (even though it doesn't seem to be very much in use...) ;) https://sourceforge.net/apps/trac/fluidsynth/attachment/ticket/92/ ___ fluid-dev mailing list fluid-dev@nongnu.org http://lists.nongnu.org/mailm

Re: [fluid-dev] Making MIDI player read from a buffer

I have started making the changes (the major internal change to fluid_midi is done; it now loads the file to memory at the start and does all the parsing from the memory buffer). It currently "owns" the pointer (garbage collection choice #2), but we can discuss that further. The code is in a branc

[fluid-dev] fluid_midi: Bug handling invalid MIDI files

tch is attached. An alternative fix is to add FLUID_FGETC to fliudsynth_priv.h, and use that instead. Matt Giuca example-eof.mid Description: MIDI audio === modified file 'fluidsynth/src/midi/fluid_midi.c' --- fluidsynth/src/midi/fluid_midi.c 2010-07-28 20:21:17 + +++ fluidsynth/src/midi

Re: [fluid-dev] possible 1.1.3 bug

> > (Btw I am not a FluidSynth developer, I'm just interested.) > > Oh? Should I also post a bug report somewhere then? > There is a bug tracker here: http://sourceforge.net/apps/trac/fluidsynth/report I don't think it gets used much though. It only has 6 active tickets. I get the feeling that bu

Re: [fluid-dev] possible 1.1.3 bug

> Okay, what I did was change Ubuntu 10.04 32-bit -> 64-bit sometime > this year (to be clear, I'm speaking about VirtualBox VMs, none of my > Ubuntus are/were on host machine). I tried to render the midi file in > 1.1.1 and it had piano bug. I updated to 1.1.2 from your unofficial > ppa on launchp

  1   2   >