All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: ld10k1-devel@lists.sourceforge.net
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: [RFC] ld10k1 roadmap
Date: Sat, 12 Feb 2005 04:51:54 -0500	[thread overview]
Message-ID: <1108201914.3647.9.camel@krustophenia.net> (raw)

OK, I have had a chance to use ld10k1/qlo10k1 lately and wanted to get
some feedback on the next development steps.

The obvious bug that must be fixed is for the DSP window to not
constantly lose the positions of the patches.  This happens whenever you
close qlo10k1 or even change settings.

Also a "Re-align plugins" function would be nice.

Rather than having to select a tool to add an in, out, or FX bus, these
should be selectable from a right click menu.

For the longer term, we will want a shared object plugin API.  This will
allow plugins to generate microcode on the fly or have custom GUIs.
Instead of loading the .emu10k1 file directly, plugins will be written
in C++ and load the emu10k1 microcode from a file or generate it.
Suggestions for the best way to do this are welcome, I am not really a
GUI programming expert and certainly have no idea how to make a QT app
load objects from a file in this way.

Lee



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

                 reply	other threads:[~2005-02-12  9:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1108201914.3647.9.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=ld10k1-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.