More plugins please! :)

16 views
Skip to first unread message

deadbeatguitarist

unread,
Mar 13, 2012, 11:50:57 AM3/13/12
to studi...@googlegroups.com
It would be great to see more audio plugins show up in the studiopkg package repo...

TAP
SWH
Invada

Thanks :)


B Watson

unread,
Mar 13, 2012, 12:38:03 PM3/13/12
to studi...@googlegroups.com
On 3/13/12, deadbeatguitarist <steve...@gmail.com> wrote:
> It would be great to see more audio plugins show up in the studiopkg
> package repo...
>
> TAP
> SWH
> Invada

All 3 of these are on slackbuilds.org. AFAIK, the StudioWare project
allows submitting packages from other sources like SBo, so you could
submit these yourself (someone correct me if I'm wrong?)

David Woodfall

unread,
Mar 13, 2012, 12:43:48 PM3/13/12
to studi...@googlegroups.com
On (12:38 13/03/12), B Watson <yal...@gmail.com> put forth the proposition:

If the sbo maintainer wants to submit them then that's fine. Otherwise
it needs a ground up slackbuild built from scratch if someone else
wants to do it. It's easier if the maintainers of our scripts are
close to us.

Having said that I use mkslack to build my slackbuilds, which uses the
standard sbo templates so our scripts will mostly look the same.

http://www.dawoodfall.net/index.php/mkslack

This speeds things up a _lot_

--
Studioware. We provide the tools - You make the music.
http://www.studioware.org

B Watson

unread,
Mar 13, 2012, 1:28:39 PM3/13/12
to studi...@googlegroups.com
On 3/13/12, David Woodfall <da...@studioware.org> wrote:
> If the sbo maintainer wants to submit them then that's fine. Otherwise
> it needs a ground up slackbuild built from scratch if someone else
> wants to do it. It's easier if the maintainers of our scripts are
> close to us.

Hm. For TAP, invada, and the LV2 version of SWH, the maintainer would
be me (a fact I had forgotten). I guess I should go through all the
audio-related stuff I submitted to SBo and resubmit to studioware...

Seems like a lot of extra work though. Have to edit the default TAG in
the script, and choose a proper StudioWare category (since they're all
just "audio" on SBo). Not even sure how to submit stuff to StudioWare
(I don't see a "submit" page on the site, do I use git?)

How about if I just make this public statement: StudioWare is welcome
to import any of my SBo SlackBuilds. (Actually, my builds don't bear
a copyright notice, because I don't consider them copyrighted, so the
statement might be redundant. IANAL, YMMV, HAND)

Someone else can do all the submitting (and maintaining, if needed). I
write SlackBuilds because I need them (and because I enjoy writing
them), I upload them to SBo so others can hopefully benefit from my
work. I don't much care if those "others" are getting my scripts from
slackbuilds.org, studioware.org, whatever. All I ask is that whoever
adds my stuff to StudioWare also adds a "modified for StudioWare.org by
(whoever)"... but I'm only asking, not demanding it.

> Having said that I use mkslack to build my slackbuilds, which uses the
> standard sbo templates so our scripts will mostly look the same.
>
> http://www.dawoodfall.net/index.php/mkslack
>
> This speeds things up a _lot_

Heh, I use a (completely different, dumber) script I wrote, also called
mkslack. I should think of a different name...

David Woodfall

unread,
Mar 13, 2012, 1:32:34 PM3/13/12
to studi...@googlegroups.com
On (13:28 13/03/12), B Watson <yal...@gmail.com> put forth the proposition:

>On 3/13/12, David Woodfall <da...@studioware.org> wrote:
>> If the sbo maintainer wants to submit them then that's fine. Otherwise
>> it needs a ground up slackbuild built from scratch if someone else
>> wants to do it. It's easier if the maintainers of our scripts are
>> close to us.
>
>Hm. For TAP, invada, and the LV2 version of SWH, the maintainer would
>be me (a fact I had forgotten). I guess I should go through all the
>audio-related stuff I submitted to SBo and resubmit to studioware...
>
>Seems like a lot of extra work though. Have to edit the default TAG in
>the script, and choose a proper StudioWare category (since they're all
>just "audio" on SBo). Not even sure how to submit stuff to StudioWare
>(I don't see a "submit" page on the site, do I use git?)
>
>How about if I just make this public statement: StudioWare is welcome
>to import any of my SBo SlackBuilds. (Actually, my builds don't bear
>a copyright notice, because I don't consider them copyrighted, so the
>statement might be redundant. IANAL, YMMV, HAND)
>
>Someone else can do all the submitting (and maintaining, if needed). I
>write SlackBuilds because I need them (and because I enjoy writing
>them), I upload them to SBo so others can hopefully benefit from my
>work. I don't much care if those "others" are getting my scripts from
>slackbuilds.org, studioware.org, whatever. All I ask is that whoever
>adds my stuff to StudioWare also adds a "modified for StudioWare.org by
>(whoever)"... but I'm only asking, not demanding it.

Ok I'll add those to my todo list and submit myself.

No problem

Dave

unread,
Jun 3, 2012, 5:19:45 PM6/3/12
to studi...@googlegroups.com
I've uploaded some - had some problems with invada since the download link is dead. Looks like they're working on a new site or something. I did though get the invada ladspa built.

Also had problems building tap - seems that reverbed is missing. Builds fine without it. I think they have a separate source for that.

Reply all
Reply to author
Forward
0 new messages