On 9/23/2011 11:50 AM, William Zwicky wrote: > On Fri, Sep 23, 2011 at 9:04 AM, Joe Emenaker<[email protected]> wrote: > >> - Going further with the "sync" notion, we could have JSL deal, in a >> smart way, with changed patches it sees from the synth. For example, >> suppose I've got a patch called "Swoopy" in my library, and I send it to >> my synth. Then, I modify the patch on the synth (during a performance, >> say). And then, afterward, I sync a Scene with my synth and JSL would >> notice that there's a patch called "Swoopy" on the synth which doesn't >> match the "Swoopy" in the Library. I could be given a choice of: 1) >> Overwrite the one in the Library, 2) Overwrite the one on the synth, or >> 3) Make a new "Swoopy-2" in the library to hold the new one found on the >> synth. >> > I think I have to disagree .. Scenes are meant for live performance. The > time required to detect this would probably be excessive, but more > importantly we can't bug the user with dialogs in this situation. We need > to transmit the patches as quickly and cleanly as possible.
Well, I didn't say that we should get rid of the "send" command. There'd be the option to send a Scene to a synth and over-write it completely. But my reason for wanting to add a "sync" is that there have been times where I made a patch at home, with a patch editor and sent it to my device. Then, in performance or rehearsal, it turned out that it needed tweaking, so I tweaked it. Let's say that happened with a half-dozen patches. Then, I got it home and didn't remember which patches I had tweaked. Now, I guess I could have just downloaded the whole Scene from the device again, but then what? Do I overwrite my previous Scene in JSL and then lose any changes I made to the Scene since I last dumped it to the device? Or, I could download it to a *new* Scene and then I'll have a bunch of duplicate-named patches in two different Scenes and the "latest" versions of each will be distributed among them. So, I still maintain that, if there isn't a time constraint, then there's some benefit to JSL being able to detect that certain patches are just "modified" versions of previous ones. - Joe ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
