Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
From: Robert Jonsson <rj@sp...> - 2005-08-21 18:02:12
|
Hi Luis, On Sunday 21 Aug 2005 17:00, Luis Garrido wrote: > Hi! > > When some of my projects that use the fluidsynth MESS end up having > some hundred MB worth of soundfonts it seems that you should wait a > substantial amount of time until the sf's are loaded. Right, the fonts are loaded in an separate thread so they can take substantially longer time to load than the rest of the song. > If you fail to > do so and press the play button too early, some of the fluidsynths > will stop working (likely those which haven't finished loading their > sf's yet, since it happens usually to those that have to load bigger > fonts). Interesting, I'll have to try this. > > The problem with this is that there are no GUI indicators of when the > synths are ready to work and that trying to use them before will break > them for the rest of the session. I suggest that the GUI gets blocked > displaying some progress indicator until the synths are ready. I think it would be hard to achieve this blocking behaviour. We should atleast be able to isolate why the synths stop working and try to fix that. > > Not a big issue if you know that the workaround is to wait some time, > depending on the size of the sf's to be loaded. Can anyone confirm > this behaviour? > > muse version is 0.7.2pre1 > > Also a midi activity indicator would be very welcome to help tracing > this (and other) kind of situations. If you start muse from a command line you can add the -m (or was it -M) switch to see all alsa messages that enter MusE. In 1.0 there will be proper indicators for midi-inputs. /Robert -- http://spamatica.se/musicsite/ |