Re: [Jsynthlib-devel] [Jsynthlib-cvs] SF.net SVN: jsynthlib:[1158] trunk/JSynthLib/core

[Joe E. <jo...@em...>]

On 9/20/2011 12:42 PM, William Zwicky wrote:
> How about this: jsl only saves a list of which ports were DISabled, by 
> name.

That's exactly what I was going to suggest.

> I also believe that jsl should be port-agnostic -- if a synth moves to 
> another port, jsl should assume it's the same synth and not bother the 
> user. But there's another problem (maybe) -- what if the user has two 
> copies of the same synth? Is that even a problem?

It could be. What if I want different banks on the different synths?

What I was thinking is that, if some sysex comes in on a port, and JSL 
can't find a driver assigned to that port which "claims" that sysex for 
itself, but there *is* a driver for that sysex assigned to a *different* 
port, then JSL could ask "Is this one of your current BFD-100's, or is 
this a new one?". That kinda deal.

> On a related note, I've never liked the GUI.

It's horrific.

> When I first started using jsl, I expected something more like Windows 
> Explorer 2-pane view, which shows folders on the left and files on the 
> right. In this case, the left pane would show ports, and under each 
> port would be the synths on that port. Ports blocked by the user would 
> still appear, but greyed out.

Actually, I was thinking of either something like Midiquest 
(http://www.soundquest.org/images/MQ10/MQ10.1280.png) where you have 
images of the synths, or something like a "desktop", where you've got 
icons of all of your synths which you can drag around the way you want 
to look like your studio arrangement.

Either way, I think images of the synths would be a nice improvement.

- Joe