[L2Ork-dev] Bad source tarball

[Jonathan Wilkes]

----- Original Message -----
> From: Ivica Ico Bukvic <ico at vt.edu>
> To: "'An open mailing list for a world-wide network of aspiring L2Orkists, L2Ork developers, contributors, and supporters.'" <l2ork-dev at disis.music.vt.edu>
> Cc: Jonathan Wilkes <jancsika at yahoo.com>
> Sent: Monday, July 16, 2012 11:25 AM
> Subject: RE: [L2Ork-dev] Bad source tarball
> 
> Did you try it through gui or via commandline (tar -jxf <filename>) as
> opposed to the gui? I had this reported a few times before and am wondering
> if this has something to do with 32 vs. 64-bitness. Are you using 32-bit OS?
> 
> That said, I'll share a little secret--I am just pushing a new release
> (today's date--look into the data/pd folder) that has some super-exciting
> new additions ;-) Check out the pd/src folder of the dev/core tarball (not
> full) for a .pd file that shows off something really cool :-) (this is not a
> doc, just a quick summary of one of the new features, once the release if
> finalized it will definitely have the appropriate doc). Speaking of docs,
> Jonathan, would you like to take a stab at this one? ;-)

Ok, I see now...

I feel like you've left out the #1 most convenient use case here, and like
every other extant preset system in Pd it remains nearly as cumbersome
for this specific use case as someone just rolling their own preset system
with abstractions.  Here's the use case I'm talking about:

I get an idea for a patch.  I start building it.  After experimenting with the state
for about 30 minutes I get a sound I like and want to save all the values
I've set to get it.  But oops, this was just supposed to be a quick experiment
and I didn't set it up for state saving.  At this point it is nearly as easy to put
in a bunch of [loadbang]--[set some_value( as it is to retrofit the patch with
your preset system.

I'm making this specific critique because your object current fails to create if I
don't give it any argument.  So why not make preset_hub apply to all canvas
local objects that you support when no arg is given?  That way someone who
just wants to quickly remember the state can create two objects and be done
with it in 10 seconds.

Or if that seems hacky, maybe having another creator name for triggering
canvas-wide state, like [canvas-preset]. Then no args = all supported
objects, iemgui = iemguis, and so on as you add categories of objects.

Anway, neat class!  I'll have to play with it some more...

Best,
Jonathan

> 
> Cheers!
> 
> More soon...
> 
>>  -----Original Message-----
>>  From: l2ork-dev-bounces at disis.music.vt.edu [mailto:l2ork-dev-
>>  bounces at disis.music.vt.edu] On Behalf Of Albert Graef
>>  Sent: Monday, July 16, 2012 9:43 AM
>>  To: An open mailing list for a world-wide network of aspiring L2Orkists,
> L2Ork
>>  developers, contributors, and supporters.
>>  Subject: [L2Ork-dev] Bad source tarball
>> 
>>  Hi Ico,
>> 
>>  it seems that the latest source snapshot available as
>>  http://l2ork.music.vt.edu/data/pd/Pd-l2ork-dev-20120607.tar.bz2 has gone
>>  bad. I tried downloading it twice, but I always get this error message
> when
>>  trying to unpack it:
>> 
>>  bzip2: Data integrity error when decompressing.
>> 
>>  Could you please check it and/or upload a new one?
>> 
>>  TIA,
>>  Albert
>> 
>>  --
>>  Dr. Albert Gr"af
>>  Dept. of Music-Informatics, University of Mainz, Germany
>>  Email:  Dr.Graef at t-online.de, ag at muwiinfa.geschichte.uni-mainz.de
>>  WWW:    http://www.musikinformatik.uni-mainz.de/ag
>> 
>>  _______________________________________________
>>  L2Ork-dev mailing list
>>  L2Ork-dev at disis.music.vt.edu
>>  http://disis.music.vt.edu/cgi-bin/mailman/listinfo/l2ork-dev
>