[L2Ork-dev] Interested in 'General Midi Mad Dash'

Wed Apr 7 14:12:08 EDT 2021

Matt, you beat me to it. ;-) Anyway, it might be possible to implement the
browse method using some stuff from the pddp library maybe?

Albert

On Wed, Apr 7, 2021 at 8:01 PM Matt Barber <brbrofsvl at gmail.com> wrote:

> The [pdcontrol] abstraction works similarly to, but not identically to the
> Pd builtin. Differences:
>
> 1. Pd builtin has a "browse" method
> 2. Pd builtin allows "dir" method with no arguments
>
> Also in Pd vanilla when you escape \$0 or any dollarsign value as an
> argument it's passed to the abstraction without expanding, but apparently
> not in Purr. And this affects how [pdcontrol] gets args.
>
> On Wed, Apr 7, 2021 at 3:12 AM ishan kumar kaler <
> kumarkalerishan at gmail.com> wrote:
>
>> [Pdcontrol] object is inbuilt in Pd vanilla(works for me in Pd version
>> 0.51.3). It was released in version 0.50 [Ref =
>> http://msp.ucsd.edu/Pd_documentation/x5.htm]. Pdcontrol inbuilt object
>> is unavailable in Purr data.
>>
>> Pdcontrol.pd patch, that Jonathan attached to this thread, works in Purr
>> Data but not in Pd vanilla, due to the absence of [canvasinfo] in Pd
>> vanilla.
>>
>> - Ishan
>>
>> On Wed, Apr 7, 2021 at 4:58 AM Matt Barber <brbrofsvl at gmail.com> wrote:
>>
>>> It wasn't inlet~ fwd – I remembered wrong. It was inlet~'s inlet, which
>>> you can pass floats to in order to initialize from inside.
>>>
>>> I'll test pdcontrol tonight after my kids' bedtime. I'd still rather
>>> stay up to date with the vanilla built-in when possible, but there might be
>>> good reasons to avoid that in this iteration.
>>>
>>> Matt
>>>
>>> On Tue, Apr 6, 2021 at 6:06 PM Jonathan Wilkes <jon.w.wilkes at gmail.com>
>>> wrote:
>>>
>>>> Also-- I think I used my `[pdcontrol]` abstraction for something I
>>>> posted on the Pd Forum, and none of the Pd Vanilla users noticed. So
>>>> please test and if it seems to work we can roll it into the build
>>>> monstrosity somewhere.
>>>>
>>>> One question-- how do we ship an abstraction as a core object? I
>>>> suppose I could make a default-loaded lib named vanilla-compatible for
>>>> stuff like this. But then if someone runs Purr without prefs the
>>>> abstraction core objects wouldn't load by default.
>>>>
>>>> -Jonathan
>>>>
>>>>
>>>> On Tue, Apr 6, 2021 at 6:02 PM Albert Graef <aggraef at gmail.com> wrote:
>>>> >
>>>> > I think that inlet~ fwd was added in 2.13.0, released in Aug 2020 (
>>>> https://github.com/agraef/purr-data/releases/tag/2.13.0). So it's been
>>>> implemented for quite a while, at least if the changelogs aren't lying. ;-)
>>>> >
>>>> >
>>>> > On Tue, Apr 6, 2021 at 8:35 PM Matt Barber <brbrofsvl at gmail.com>
>>>> wrote:
>>>> >>
>>>> >> I might be wrong about inlet fwd. I'll look soon.
>>>> >>
>>>> >> MB
>>>> >>
>>>> >> On Tue, Apr 6, 2021, 1:30 PM Jonathan Wilkes <jon.w.wilkes at gmail.com>
>>>> wrote:
>>>> >>>
>>>> >>> On Tue, Apr 6, 2021 at 1:22 PM Matt Barber <brbrofsvl at gmail.com>
>>>> wrote:
>>>> >>> >
>>>> >>> > Hello, thanks for the questions.
>>>> >>> >
>>>> >>> > I would prefer that it be Pd-vanilla-with-no-externals
>>>> compatible. That way it would have maximum usability but could still be
>>>> included with Purr by default. There are a few updates in Pd that haven't
>>>> yet AFAIK made it into Purr which could be very helpful, particularly
>>>> [inlet~ fwd] and [pdcontrol], so getting those into the architecture could
>>>> be part of this project.
>>>> >>>
>>>> >>> * `[inlet~ fwd]` wasn't in the last release of Purr Data, over a
>>>> year
>>>> >>> ago? If that's true, it will certainly be in the next release.
>>>> >>>
>>>> >>> * attached is an abstraction for pdcontrol. Could you check to see
>>>> if
>>>> >>> it actually works? If so we can just ship it with Purr Data
>>>> >>>
>>>> >>> -Jonathan
>>>> >>>
>>>> >>> >
>>>> >>> > MB
>>>> >>> >
>>>> >>> > On Sun, Apr 4, 2021 at 2:33 AM ishan kumar kaler <
>>>> kumarkalerishan at gmail.com> wrote:
>>>> >>> >>
>>>> >>> >>   Hi,
>>>> >>> >>     Thanks for your generous advice. I'll submit a draft
>>>> proposal for review asap specifying the framework. Besides that, I have
>>>> some unsureness regarding project implementation details, namely, what Pd
>>>> version we have to use in the project (pd-l2ork 2.x or pd vanilla)?  Along
>>>> with core vanilla objects, should we use objects from external libraries
>>>> (let's say [drunk] from cyclone)?
>>>> >>> >>
>>>> >>> >> Best regards,
>>>> >>> >> Ishan
>>>> >>> >>
>>>> >>> >> On Sun, Apr 4, 2021 at 1:06 AM Matt Barber <brbrofsvl at gmail.com>
>>>> wrote:
>>>> >>> >>>
>>>> >>> >>> Welcome! Since this is Pd Vanilla only, you'll want to
>>>> familiarize yourself asap with abstractions and the [clone] object. Also,
>>>> the framework for storing, loading, selecting, and playing will be more
>>>> important than actually completing all of the synths. Be sure to include
>>>> how you might tackle this framework in your proposal.
>>>> >>> >>>
>>>> >>> >>> Matt
>>>> >>> >>>
>>>> >>> >>> On Fri, Apr 2, 2021 at 4:04 PM ishan kumar kaler <
>>>> kumarkalerishan at gmail.com> wrote:
>>>> >>> >>>>
>>>> >>> >>>>   Hi,
>>>> >>> >>>>     I have created Synth from VSTs in the past. As far as
>>>> Pure-data is concerned, I have created some basic synths using AM/FM
>>>> Synthesis and effects. I'm readily exploring more on the go.
>>>> >>> >>>>
>>>> >>> >>>> Best regards,
>>>> >>> >>>> Ishan
>>>> >>> >>>>
>>>> >>> >>>> On Fri, Apr 2, 2021 at 10:59 PM Jonathan Wilkes <
>>>> jon.w.wilkes at gmail.com> wrote:
>>>> >>> >>>>>
>>>> >>> >>>>> On Fri, Apr 2, 2021 at 12:54 PM ishan kumar kaler
>>>> >>> >>>>> <kumarkalerishan at gmail.com> wrote:
>>>> >>> >>>>> >
>>>> >>> >>>>> > Hello everyone,
>>>> >>> >>>>> >            My name is Ishan and I am CS Undergrad. I have
>>>> done few development projects until now and have some Open Source
>>>> Experience. I have an interest in music production and some experience in
>>>> sound synthesis.
>>>> >>> >>>>> >
>>>> >>> >>>>> > I'm interested in contributing to the Purr Data project and
>>>> working on the project 'General Midi Library'.
>>>> >>> >>>>> >
>>>> >>> >>>>> > In the past, I have worked with DAWs and VSTs and have some
>>>> experience with Pure Data also. I'm currently exploring Purr Data in-depth
>>>> and familiarizing myself with the codebase while making contributions all
>>>> along.
>>>> >>> >>>>> >
>>>> >>> >>>>> > I wish to ask if there's an IRC channel alongside the
>>>> mailing list, as I couldn't find one. I'll be more than happy to have
>>>> suggestions from you all :)
>>>> >>> >>>>> >
>>>> >>> >>>>> > Best regards,
>>>> >>> >>>>> > Ishan
>>>> >>> >>>>>
>>>> >>> >>>>> Hello Ishan,
>>>> >>> >>>>>
>>>> >>> >>>>> Welcome!
>>>> >>> >>>>>
>>>> >>> >>>>> We don't have a chat channel atm, but you're welcome to ask
>>>> any
>>>> >>> >>>>> questions here on the mailing list.
>>>> >>> >>>>>
>>>> >>> >>>>> As for the project-- have you built any software synths
>>>> before?
>>>> >>> >>>>>
>>>> >>> >>>>> Best,
>>>> >>> >>>>> Jonathan
>>>> >>> >>>>>
>>>> >>> >>>>> > _______________________________________________
>>>> >>> >>>>> > 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
>>>> >>> >>>>
>>>> >>> >>>> _______________________________________________
>>>> >>> >>>> 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
>>>> >>> >>
>>>> >>> >> _______________________________________________
>>>> >>> >> 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
>>>> >>> _______________________________________________
>>>> >>> 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
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Dr. Albert Gr"af
>>>> > Computer Music Research Group, JGU Mainz, Germany
>>>> > Email: aggraef at gmail.com, web: https://agraef.github.io/
>>>> > _______________________________________________
>>>> > 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
>>>
>>> _______________________________________________
>>> 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
>
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev

-- 
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: aggraef at gmail.com, web: https://agraef.github.io/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20210407/3a9f5feb/attachment-0001.html>