Hi Joe,
I think a scene enables you to put all your gear into a state which you nee=
d
for a certain track or set. That is, it holds all relevant patches and patc=
h
locations for one of your tracks or sets. It's something like a snapshot of
the state of the devices you manage with JSynthlib.
So, if you use JSynthlib to manage more than one device and use more than
one per track/set you will need multiple, different patches in a scene. The
menu entry Library -> "Transfer Scene" can then be used to transfer
everything to the devices in one go.
Cheers,
Daniel
On 2/24/06, Joe Emenaker <jo...@em...> wrote:
>
> It appears that a scene is just a patch that also has information about
> what bank/patch-location on the synth it's supposed to go to, is that
> correct?
>
> If that's the case, then I think we should incorporate this data into
> the normal Patch class (*after* we convert from serialization to XML for
> patch storage, of course). For normal Library frames, this info just
> wouldn't be displayed (but would still be kept and could be editable via
> a dialog box). Externally, this would allow seamless drag-n-drop between
> Scene frames and Library frames (right now, bank/patch info is lost when
> you drag from a SceneFrame to a LibraryFrame). Internally, it would
> clean up a lot of the cut-n-paste and drag-n-drop code. Right now, there
> are separate classes for dragging/pasting patches and scenes.
>
> This would also allow us to address one of Robert Wirski's issues from
> his mail back on the 20th:
> > A Bank/Patch number in the scene/librarian window is not set to the
> value it comes from, just to the first field in the list. It should point=
to
> the same place by default.
> - Joe
>
>
>
>
|
