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

[Akash Negi]

Hello everyone,

I have submitted my final proposal. Thanks, Jonathan for the feedback once
again;).

Regards
Akash Negi

On Tue, Apr 13, 2021 at 10:24 PM Jonathan Wilkes <jon.w.wilkes at gmail.com>
wrote:

> Oops-- s/hell/hello in my previous message!
>
> -Jonathan
>
> On Tue, Apr 13, 2021 at 12:53 PM Jonathan Wilkes <jon.w.wilkes at gmail.com>
> wrote:
> >
> > Hell,
> >
> > I still see your draft proposal on the Purr Data GSoC dashboard.
> >
> > If you're going to submit it, you need to do so soon. There's less
> > than an hour left before the deadline.
> >
> > Best,
> > Jonathan
> >
> > On Sun, Apr 11, 2021 at 12:29 PM Ishan Kumar Kaler
> > <kumarkalerishan at gmail.com> wrote:
> > >
> > > Hi Jonathan,
> > >                 Thanks for the feedback. I have created a separate
> "framework" section in the draft explaining the suggested points in detail
> and have attached respective screenshots. Any further suggestions are
> welcome.
> > >
> > > Thanks and Regards,
> > > Ishan
> > >
> > > On Sat, Apr 10, 2021 at 2:48 AM 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 :)
> > >>
> > >> In the draft I read there is a section missing:
> > >>
> > >> "However this"
> > >>
> > >> and then the next section.
> > >>
> > >> One suggestion: Could you add a super simple screenshot of the
> > >> user-facing objects you have in mind? In other words:
> > >>
> > >> 1. What does a user type in a box to instantiate this?
> > >> 2. Once instantiated, how many inlets and how many outlets does the
> object have?
> > >> 3. What kind of data flows from in the inlets and out the outlets?
> > >> 3. If the user can also instantiate the individual instruments, what
> > >> would that look like, and what do the inlets and outlets like?
> > >>
> > >> You can just create one or two empty abstractions and fill them with
> > >> [inlet]/[inlet~]/[outlet]/[outlet~] inside to get a mockup of this.
> > >>
> > >> None of that has to be set in stone yet. I'm just curious what you
> > >> have in mind at this point.
> > >>
> > >> Best,
> > >> Jonathan
> > >>
> > >>
> > >> >
> > >> > Best regards,
> > >> > Ishan
> > >> > _______________________________________________
> > >> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20210413/b0a3afda/attachment-0001.html>