Re: [LAD] Github DCMA takedown notice - VeSTige header

2018-06-05 Thread Rui Nuno Capela
On 06/05/2018 12:43 PM, Robin Gareus wrote:
> On 06/05/2018 09:45 AM, Filipe Coelho wrote:
>> On 05.06.2018 01:18, Robin Gareus wrote:
>>> Hi LADs,
>>>
>>> I was contacted earlier today by GitHub with a DCMA request from
>>> Steinberg.net to remove the aeffectx.h from VeSTige. [1]
>>

well, you all know that it was coming, just not when :)

as far I'm concerned: I have no single doubt the vestige will get killed
on sight (from qtractor tree) as soon a notice is received...

fwiw. i never agreed with the vestige stance and just indulged on some
qtractor user's requests because otherwise they are the ones to become
licensees of the required (original) VST2SDK and build qtractor on their
own...

that's it.
-- 
rncbc aka. Rui Nuno Capela
rn...@rncbc.org

ps. nevertheless, i'll stand with what has been written on README.VST
almost one decade ago, when native VST support was a new thing to JUCE
in general and qtractor in particular; and what a PITA the JUCE was at
the time, let alone the VST licensing, whatever ;)

___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev


Re: [LAD] Github DCMA takedown notice - VeSTige header

2018-06-05 Thread Robin Gareus
On 06/05/2018 09:45 AM, Filipe Coelho wrote:
> On 05.06.2018 01:18, Robin Gareus wrote:
>> Hi LADs,
>>
>> I was contacted earlier today by GitHub with a DCMA request from
>> Steinberg.net to remove the aeffectx.h from VeSTige. [1]
> 
> Oh wow, incredible timing with Microsoft buy out.

Honi soit qui mal y pense.

> Do you think renaming aeffectx.h will be enough?

The filename does match a filename of the official Steinberg VST SDK.
I've added a disclaimer and clarified that is vestige.

It may well be that this is part of a larger outreach. grep all of
github for plugins that ship aeffectx.h.

If you the DCMA notice carefully, you'll fine that they did not even
follow github's guide to do so. It may well be some semi-automated process.

I guess we'll find out, the 24h will expire 21:55 CEST today.

> It is their API, which they might feel entitled to sue over.

Only in the US of A. APIs are not (C) in the EU.
The vestige header is a pure API without any implementation.

>> I have no idea why Steinberg would target this rather low profile
>> project, but there you go.
> 
> Likely because of the name. lv2vst sounds "dangerous" :P
> 
> Sadly, if they insist on this, it will only be trouble for opensource
> applications.
> Ardour, Qtractor, Carla, MusE, LMMS and others all use this vestige
> header... making it "illegal" would mean our beloved tools will simply
> drop VST support.

Those are hosts though. Except for Carla which can be both.

> This is now how they convince developers to change to VST3 at all...

If this is indeed only about plugin (not hosts), then this would explain
it. I am curious if other plugin authors also received a notice.

For hosts, I would be able to ignore the fact the VST3 SDK is a
kitchen-sink and with a bad conscience also tolerate UTF-16, but VSTGUI4
depending on GTK on Linux is a no-go.

> rather, just makes me want to remove all VST related things from my
> system, damn bastards.

LV2 FTW!
robin
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev


Re: [LAD] Github DCMA takedown notice - VeSTige header

2018-06-05 Thread Filipe Coelho

On 05.06.2018 01:18, Robin Gareus wrote:

Hi LADs,

I was contacted earlier today by GitHub with a DCMA request from
Steinberg.net to remove the aeffectx.h from VeSTige. [1]


Oh wow, incredible timing with Microsoft buy out.

Ben (from Harrison) mentioned on IRC that this might be initiated by 
Juce having their own VST2 API implementation.


23:08 < ben_at_harrison> JUCE might be the initiator of this action.
23:08 < ben_at_harrison> they became aware that JUCE uses an alternative 
implementation ... and this causes problems ( some missing features etc )




I am planning to contest the DCMA request. This will ideally happen with
some legal counsel and support from Javier Serrano Polo who is the
original (C) holder of the VeSTige header and reverse engineered the API.


As someone who hates this kind of things, I wish you good luck!
Please keep us informed on how it goes.



Since Github requires action within 24 hours, I have meanwhile complied
and force-pushed
https://github.com/x42/lv2vst/blob/master/include/aeffectx.h out of
existence.


Do you think renaming aeffectx.h will be enough?
It is their API, which they might feel entitled to sue over.
(which of course is BS, APIs should not work like that, but what can we 
do anyway)




I have no idea why Steinberg would target this rather low profile
project, but there you go.


Likely because of the name. lv2vst sounds "dangerous" :P

Sadly, if they insist on this, it will only be trouble for opensource 
applications.
Ardour, Qtractor, Carla, MusE, LMMS and others all use this vestige 
header... making it "illegal" would mean our beloved tools will simply 
drop VST support.


This is now how they convince developers to change to VST3 at all... 
rather, just makes me want to remove all VST related things from my 
system, damn bastards.

___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev