Dan,
Thanks for the information.  I hope to submit a piece for the NYC Pd Con using 
PdParty.  
Mitch


> On Aug 8, 2016, at 3:17 PM, Dan Wilcox <[email protected]> wrote:
> 
> Also, note that subfolders inside libs are added the your search path 
> automatically so:
> 
>     libs/my_cool_patches/cool_patch.pd
> 
> can be used in any PdParty patch via:
> 
>     [cool_patch]
> 
> There is a chance this could lead to conflicts between different abstractions 
> with the same name, but then again, it’s something we have to deal with in 
> Desktop pd as it is. If that is the case, you can always but things in 
> another subfolder and add the folders name:
> 
>     libs/more_libs/another_abs_lib/cool_patch.pd
> 
> via:
> 
>     [another_abs_lib/cool_patch]
> 
> I’m finally porting some patches over to PdParty and, so far, the results are 
> pretty great performance-wise. I can essentially run my entire setup from 
> PdCon 2007 on an iPhone minus the graphics (although I could port that and 
> run it locally too). Cool to see my thesis hopes for tech more or less coming 
> true. In any case, I’ll have some new stuff for PdCon 2016!
> 
> --------
> Dan Wilcox
> @danomatika <https://twitter.com/danomatika>
> danomatika.com <http://danomatika.com/>
> robotcowboy.com <http://robotcowboy.com/>
>> On Aug 8, 2016, at 1:11 PM, Dan Wilcox <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> The simplest answer: both. It’s up to what you need / how you work. 
>> 
>> RjDj encouraged people to package *all* the libs needed by a scene within 
>> the scene itself. This ensures you can pass a scene to someone else and know 
>> it has all of it’s dependencies. The downside is that then you end up having 
>> *alot* of redundant abstraction lib copies.
>> 
>> The libs folder is kind of like Desktop pd’s extra folder so you have a 
>> central place to put commonly used abstractions. Bundling libs within a 
>> scene will still work of course as, like Desktop pd, the local scene copy 
>> should override the libs copy. A secondary reason PdParty has the libs 
>> folder is to allow users to override/modify the few built-in abstractions as 
>> there is a secondary copy kept internally. I may remove having a direct copy 
>> already placed in libs in the future.
>> 
>> In any case, one of the important points for me is that, generally, PdParty 
>> scenes should work on Desktop. This is partially experience for being able 
>> to run a backup set on my laptop if the hardware setup fails :P
>> 
>> --------
>> Dan Wilcox
>> @danomatika <https://twitter.com/danomatika>
>> danomatika.com <http://danomatika.com/>
>> robotcowboy.com <http://robotcowboy.com/>
>>> On Aug 8, 2016, at 10:21 AM, mitchell turner <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> Dan,
>>> I have finally gotten around to trying out PdParty and absolutely love it.  
>>> Thanks for all of the work you did getting this to run.  I’m sure I’m not 
>>> the only one who appreciates your work.
>>> 
>>> I have a question regarding how best to use my own abstractions within 
>>> PdParty on iOS.  I have been successful using my abstractions two ways:
>>> 1) copy my abstraction into the PdParty directory that contains my main 
>>> patcher.  
>>> 2) copy my abstraction into the main “lib” directory inside PdParty.  
>>> 
>>> I guess my question is: what is the best place to put user-created 
>>> abstractions within the file structure of PdParty.
>>> 
>>> For those interested, I’m using the latest version of PdParty on iOS 9.3.4 
>>> and Pd Vanilla 0.47.0. 
>>> 
>>> Thanks again,
>>> Mitch
>>> 
>>> 
>> 
> 

_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Reply via email to