[L2Ork-dev] new alpha release of pd-l2ork
Ivica Bukvic
ico at vt.edu
Mon May 30 13:38:02 UTC 2016
OK, I added [list fromsymbol] and [list tosymbol], and made
iemguts/initbang and iemguts/closebang as additional creators. I guess I
should update the iemguts. Is there anything else?
I could use help updating help files for (using the pddp format, see what
comes with pd-l2ork):
*list (to add fromsymbol and tosymbol)
*pddp compatible vesion of the documentation for [text], [array define]
(and its variants), new [netsend] and [netreceive]
*anything else?
Best,
Ico
On Mon, May 30, 2016 at 9:02 AM, Liam Goodacre <liamg_uw at hotmail.com> wrote:
> This would solve the problem, if you can make it work, ie. PD would need
> to know that [iemguts/initbang] is NOT located in the initbang folder.
>
> BTW I think I was wrong about the "try" method working. [iemguts/try
> initbang, iemguts/initbang] is coming out blank for me in Vanilla, unless I
> have loaded [iemguts/initbang] before. This seems like a bug, but not one
> for the L2Ork list...
>
>
> ------------------------------
> Date: Mon, 30 May 2016 08:37:29 -0400
> From: ico at vt.edu
> To: l2ork-dev at disis.music.vt.edu
> Subject: Re: [L2Ork-dev] new alpha release of pd-l2ork
>
> I think I finally understand what you're asking. Would possibly creating
> an alias for initbang that can be created using iemguts/initbang solve the
> problem you've identified?
>
> On Mon, May 30, 2016 at 8:34 AM, Ivica Bukvic <ico at vt.edu> wrote:
>
> I just tried [initbang] and [closebang] in pd-l2ork and they work as far
> as I can tell as expected (only under an abstraction). Are they behaving
> differently than new initbang in the iemguts?
>
> On Mon, May 30, 2016 at 8:24 AM, Liam Goodacre <liamg_uw at hotmail.com>
> wrote:
>
> Vanilla has been made compatible with initbang and closebang from 0.47,
> but the objects are not built in. Instead, they've been moved to the
> iemguts library. So to create them in Vanilla, you either have to do
> [iemguts/initbang] or [declare -stdpath iemguts] [initbang]. Initbang is
> only useful in abstractions, and [declare] is discouraged in abstractions
> as per the help file, so that option is out. That leaves
> [iemguts/initbang], but this will render the patch incompatible with L2Ork
> (unless L2Ork is updated with the new version of iemguts...)
>
> [try] is a great and underrated object. It creates a fallback object, in
> case the first one you create can't load, so for example [iemguts/try
> gumbo, float] will create a float, as there is no object called "gumbo".
> [try] is obscured by the fact that you can't call its help file from the
> canvas; if you try, you instead get the helpfile for whatever object it
> created. You have to go through the browser to get to its helpfile, and I
> don't know how to do that in 2Ork.
>
> You can use [try] to solve the initbang incompatibility problem, by
> creating the object [iemguts/try initbang, iemguts/initbang]. In L2Ork this
> will give the object [initbang] and in Vanilla it will give
> [iemguts/initbang]. This works, but I doubt it will occur to most users, so
> it might be wise to come up with a better solution.
>
>
>
>
> ------------------------------
> Date: Mon, 30 May 2016 07:29:56 -0400
>
> From: ico at vt.edu
> To: l2ork-dev at disis.music.vt.edu
> Subject: Re: [L2Ork-dev] new alpha release of pd-l2ork
>
> I will gladly include new objects. I am confused about initbang and
> closebang. I thought new vanilla has those hooks built-in much like what
> pd-l2Ork has inherited from the extended. We also have externals you
> mentioned in the iemguts. Are they not working for you? Can't you simply do
> initbang and closebang without prefixes? I am also not sure what you mean
> by "try initbang".
>
> Best,
>
> --
> Ivica Ico Bukvic, D.M.A.
> Associate Professor
> Computer Music
> ICAT Senior Fellow
> Director -- DISIS, L2Ork
> Virginia Tech
> School of Performing Arts – 0141
> Blacksburg, VA 24061
> (540) 231-6139
> ico at vt.edu
> www.performingarts.vt.edu
> disis.icat.vt.edu
> l2ork.icat.vt.edu
> ico.bukvic.net
> On May 30, 2016 02:33, "Liam Goodacre" <liamg_uw at hotmail.com> wrote:
>
> I'm enjoying the new release Ico, thanks for your work as always.
>
> I'd like to make a case for including the most recent version of iemguts
> in the next L2Ork release. Aside from some bug fixes and new features, the
> main difference is that iemguts now includes initbang and loadang, and this
> is the only way of accessing them in Vanilla (0.47 and above). This means
> that the objects [initbang] and [closebang] are currently incompatible
> between Vanilla and L2Ork. In Vanilla, you have to create
> [iemguts/initbang], but this won't be found in L2Ork. Using "declare" isn't
> an option, as [initbang] is only useful in abstractions, and declare
> doesn't work here.
>
> There is a workaround of creating the object [iemguts/try initbang,
> iemguts/initbang], which seems to be working for me. However, I don't think
> that most users will think of this.
>
> Currently, the new version of iemguts is not available on deken and has to
> be compiled: https://git.iem.at/pd/iemguts
>
> Would you be willing / able to include it in L2Ork?
>
> ------------------------------
> Date: Mon, 30 May 2016 01:28:04 -0400
> From: ico at vt.edu
> To: l2ork-dev at disis.music.vt.edu
> Subject: Re: [L2Ork-dev] new alpha release of pd-l2ork
>
> OK, I just committed a series of patches that should hopefully address all
> of these problems and will be releasing a beta sometime tomorrow...
>
> On Sun, May 29, 2016 at 12:09 AM, Ivica Bukvic <ico at vt.edu> wrote:
>
> Thank you for the report, Albert. Below is the current update (I haven't
> uploaded anything yet):
>
>
>
> On Sat, May 28, 2016 at 1:57 PM, Albert Graef <aggraef at gmail.com> wrote:
>
>
> I can open these patches now, but text-object-help.pd still gives me a
> segfault when I close the patch window. Also, there's
>
>
> This should be now fixed in the latest git commit.
>
>
> some stuff missing when I open these patches. With array-object-help.pd I
> get (console messages):
>
> scalar
> ... couldn't create
>
>
> Scalar is a non-issue. It is currently an object that has no purpose (yet)
> according to Miller's comments in the code. I have opted not to implement
> it yet and in these patches it is merely listed as a related object.
>
>
> error: text define: no method for 'float'
> ... you might be able to track this down from the Find menu.
> error: text define: no method for 'float'
>
>
> This is something I will have to investigate further. Any help/leads is
> most appreciated.
>
>
>
> With text-object-help.pd I get:
>
> drawtext z 16 -3 0
> ... couldn't create
>
>
> This one is a bit of a pickle that will take some effort to reconcile.
> Miller's drawnumber/drawsymbol and Pd-L2Ork's are starting to diverge
> significantly. I am thinking I may just implement drawtext as a separate
> object altogether.
>
>
> scalar
> ... couldn't create
>
>
> See comment above.
>
> Making progress. Slowly. Progress nonetheless :-)
>
> Best,
>
> Ico
>
>
>
>
>
> _______________________________________________ L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu http://disis.music.vt.edu/listinfo/l2ork-dev
>
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> http://disis.music.vt.edu/listinfo/l2ork-dev
>
>
> _______________________________________________ L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu http://disis.music.vt.edu/listinfo/l2ork-dev
>
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> http://disis.music.vt.edu/listinfo/l2ork-dev
>
>
>
>
> _______________________________________________ L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu http://disis.music.vt.edu/listinfo/l2ork-dev
>
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> http://disis.music.vt.edu/listinfo/l2ork-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20160530/94fa271d/attachment.html>
More information about the L2Ork-dev
mailing list