Thanks! So, 'deterministic' here would mean that, no matter what, it does what it is asked for in the given order, waiting every time until each step is done?
I guess that if I ask for a 'list' of all events, I mean the fully determined sequence of commands that happen throughout the execution of a patch. This would look like an overloaded and fully verbose log file that shows every step of the patch. I think a log like this might be useful for debugging or for increasing efficiency. I have used [text sequence] to record performances, for example, in order to replicate a performance. However, a log like the one above might serve different purposes, but I have no idea where or how it could be implemented (perhaps something like `pd -log -open main.pd` would just output the log instead of running the patch) On Tue, Jan 29, 2019 at 2:20 PM Roman Haefeli <[email protected]> wrote: > On Tue, 2019-01-29 at 13:55 +0100, Fede Camara Halac wrote: > > Thanks Christof and Claude for your replies. > > > > My question need some clarification, namely that I am not using any > > object calling clocks (delay, metro, pipe, etc) or dsp objects. I am > > only interested in 0-time ordering, for example: > > > > [loadbang] > > > > > > > [t b b b ] > > I I I > > I I (load many large arrays/soundfiles) > > > (analize arrrays/sounds and write them to disk) > > > > > > > [; pd quit( > > That should work as (I believe) you expect it. It loads files, analyzes > them, writes results to disk and quits Pd. Pd _is_ deterministic, as > Claude already pointed out. > > BTW: I guess the common convention is that ASCII art works for > monospaced fonts. > > Roman > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > -- http://fdch.github.io/tv
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
