Re: Possible modifications to interface
"Jack O'Quin" <[email protected]> Mon, 17 Nov 2008 12:31:22 -0600
| Newsgroups | gmane.comp.audio.jamin.devel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Nov 17, 2008 at 5:52 AM, Sebastien Valette <[email protected]> wrote: > Hi, > > Jack O'Quin a écrit : >> >> My initial reaction is that a mastering tool like Jamin is mainly a >> hands-on interactive session. Running it in the background as a >> daemon seems pointless for its primary intended use. Other uses may >> appear over time, of course. >> > > Well, I know that closed-source drivers do suck, but in my case, I have an > issue when exporting songs with ardour with Jamin as a plugin. Using the > closed-source fglrx driver, the sound is awfully distorded while when using > the open-source (and much slower du to new hardware not being properly > handled) the sound is OK. Perhaps separating the UI and the processing would > solve this case? The audio processing already runs in real-time threads, which *should* be immune to interference from graphics software. Putting them in a separate address space would not help any with that. If the graphics *hardware* is locking out the I/O bus for long periods, then it's not going to work properly no matter what we do in software. -- joq ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/