[L2Ork-dev] compatibility issues between pd-l2ork and pd-vanilla

Tue Jun 20 12:20:53 EDT 2023

Missatge de Ico Bukvic <ico at vt.edu> del dia dt., 20 de juny 2023 a les
16:38:

> Hi Xavier,
>
> This may be because Pd vanilla has an inconsistent way of positioning
> iemgui objects. Namely, sometimes they are drawn up to 2-3 pixels off of
> their (0,0) origin. This causes problems with auto patching (among other
> issues). One way you can minimize problems is by enabling the -legacy flag.
> Just start the program from the command line (or adjust its shortcut) by
> typing "pd-l2ork -legacy" (without the quotes).
>

Hi Ico,
Now i understand better the problem...also i didn't know about this flag
i'm gonna check it to see how it works

>
> This should reposition all iemgui objects to how the vanilla looks. Please
> note if you have edited the patch using non-legacy options and repositioned
> objects, reenabling -legacy will move those objects in a way that may make
> them look out of place. In other words, if you want to keep vanilla
> compatibility with iemgui object positions, make sure to edit the patch
> with the -legacy flag enabled.
>
> BTW, on the screenshots, is the left one pd and right one pd-l2ork (the
> right one looks correct) since the consoles behind them suggest that? Or is
> it the other way around?
>

yes it is correct : left is vanilla and right l2ork.
As far as i tested, the problem occurs in the programming 'order' or
sequence :
When you program first in l2ork and reopen the patch later in vanilla, the
problem occurs but not the opposite :
if you make a patch in vanilla, and then reopen it in l2ork, doesn't occurs
the patch distorsion.
The problem in this second case is that programming in vanilla give u the
speed of a horse, meanwhile programming in l2ork gives u the speed of a
train or even a plain. In other words programming with l2ork is easier and
much faster, spetially for GUI UX issues.

All this behaviour is done without the flag u mention before, so im gonna
try with the flag and make some tests.
I'll keep you informed about those tests...

thanks a lot
Xavi

>
> Best,
>
> Ico
>
> --
> Ivica Ico Bukvic, D.M.A.
> Director, Creativity + Innovation
> Director, Human-Centered Design iPhD
> Institute for Creativity, Arts, and Technology
>
> Virginia Tech
> Creative Technologies in Music
> School of Performing Arts – 0141
> Blacksburg, VA 24061
> (540) 231-6139
> ico at vt.edu
>
> ci.icat.vt.edu
> l2ork.icat.vt.edu
> ico.bukvic.net
>
>
>
> On Tue, Jun 20, 2023 at 8:38 AM xavier manzanares <freequencies at gmail.com>
> wrote:
>
>> Hi everyone,
>>
>> I have a question related to the compatibility between pd-l2ork and pd.
>> I am teaching at university (Barcelona context), different courses
>> related with generative/algorythmic music and therefore i'd need to have my
>> pd toolkits* as stable as possible, also in order to fit several OSs.
>>
>> *You can see both examples here :
>> https://github.com/xamanza/GNRTV.CELLS
>> https://github.com/xamanza/GNRTV.BOTS
>>
>> As far as i know, when you program in pd-l2ork, (that frankly is a much
>> improved way to program in Pd due to the js Gui implementation), and then
>> you open it in Pd vanilla, the patch is partially distroyed. I attach a
>> screenshot with an example of the same patch opened both in pd-l2ork and
>> pd-vanilla.
>> Questions here appear :
>> Why this happens?
>> Is there a method or trick to avoid it and get always a robust
>> compatibility?
>>
>>
>> The reason i want the most compatibility as possible, responses to
>> several years of developing with this language, related to research &
>> academic issues, but also in the High potential of Pd in embed systems
>> (Raspberry stand alone musical applications), audio engines for game design
>> (libpd & unity etc), and other newmedia projects or even in the modular
>> synths constellation (like programmable modular synths such as Befaco's
>> Lich or Witch).
>>
>>
>> Any answer of those questions will be useful )
>> Thanks
>> Xavi Manzanares
>>
>>
>> ///////////////
>> details of the screenshot :
>> OS : Linux Mint 21.1**
>> Pd version 0.52.1
>> Pd-l2ork-2.16.0 20230415-rev.dc26e65f
>>
>> **note i detected the problem described before, not only in linux, but in
>> MacOS (mac Intel) and Windows.
>>
>> [image: SamePatchwithVanillaandL2ork.png]
>>
>>
>> --
>> Xavier Manzanares
>> [0034] 659 243 481
>> Recerca / Arts Electròniques
>> http://xavimanzanares.oneshaptiques.space/
>> <http://noconventions.mobi/daax>
>> http://oneshaptiques.space/ <http://noconventions.mobi/oneshaptiques>
>> _______________________________________________
>> L2Ork-dev mailing list
>> L2Ork-dev at disis.music.vt.edu
>> https://disis.music.vt.edu/listinfo/l2ork-dev
>>
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev
>

-- 

Xavier Manzanares
[0034] 659 243 481
Recerca / Arts Electròniques
http://xavimanzanares.oneshaptiques.space/ <http://noconventions.mobi/daax>
http://oneshaptiques.space/ <http://noconventions.mobi/oneshaptiques>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20230620/722cc41e/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SamePatchwithVanillaandL2ork.png
Type: image/png
Size: 1030379 bytes
Desc: not available
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20230620/722cc41e/attachment-0001.png>