|
From: | Peter Hanappe |
Subject: | Re: [iiwusynth-devel] Re: unloading a soundfont |
Date: | Thu, 28 Nov 2002 18:41:37 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 |
Antoine Schmitt wrote:
:::::::::28/11/02::::15:12 +0100::::Peter Hanappe:::::::::When? At the next load request? That might not be good enough, because the risk exists that soundfont stays in memory for a long time. At every 'noteon' and 'noteoff' event? That may not be good, too. That means that real-time threads can no longer call this function!I dont understand. What do you mean ?
At the next load request: If a user or application requests to unload a soundfont but subsequently doesn't request to load a new soundfont, the old soundfont just stays in memory. At every 'noteon' and 'noteoff' event: If the unload is done in a noteon/off function, that function mignt call to 'free()'. Real-time threads cannot invoke 'free' for risk of unexpected long delays. P
++ as
[Prev in Thread] | Current Thread | [Next in Thread] |