Re: [sc-dev] Re: [sc-users] Why can't SynthDefs be archived?

[<rkuivila@xxxxxxxxxxxx>]

Hi Iani,

  I am a bit dubious about full-fledged recovery as there is no way to recover the
state of whatever PauseStreams are running on the language side.  There is
a similar problem for NodeProxy as you do not know the keys that have been
associated with various nodes on the client side, so there is no easy way to 
fully recover your state before the crash.  (Besides, if you fully recovered it you would 
probably crash again...)

  I think it is more of an issue of knowing where to sneak in your replacement groups
on the server.  For a single user this can just be at the tail of the root group.
The multi-user case  might be handled with application dependent fixed group 
structures.

  
RJK

 
> So, it would be not so difficult to reconstruct some sort
> of crash recovery that Ron is describing, at least a 
> basic one.  One thing would still help greatly though: 
> 
> If the node is a synth, send back an additional argument
> with the name of the synthdef of that synth. Then the
> structure of the node tree can be reconstructed in it's 
> entirety.  One could even then proceed to query values
> of parameters of synths as needed. 
> 
> Iannis Zannos
> 
> 
> On Sun, 23 Nov 2003, Julian Rohrhuber wrote:
> 
> > 
> > >s.sendMsg("n_status", 2004);
> > >
> > >where 2004 is the number of the node.
> > >
> > >The server could respond with:
> > >-1 for not existent
> > >0 for stopped
> > >1 for running
> > 
> > what about "/n_query" ?
> > 
> > the node report of Crucial.menue can also be used to solve that
> problem.
> > 
> 
> -- 
> Iannis Zannos
> 
> 
> 
> _______________________________________________
> sc-dev mailing list
> sc-dev@xxxxxxxxxxxxxxx
> http://www.create.ucsb.edu/mailman/listinfo/sc-dev
>