Community plugin project

[Natan]

@UD-AUDIO And one Important Thing For Your UI And The Position Of Your Zoom Combobox.

Put it Some Where In Top Left Hand Side, Instead Of Where You Decided ( Top Right Hand Side )

With This Small Change, Your End User never Miss The Box, By Selecting A Bigger Size.
On 200 Zoom, UI & Zoom Box Gets Cutted, and That Box Is Not Accessible.

Cheers

[Natan]

This post is deleted!

[UD AUDIO]

@Natan said in Community plugin project:

If You Mean Having 2 Drop Down UI Zoom Factors, Then make 2 Floting Tiles, But I Not Recommend It,You May Get Some Conflicting Issues On Setting.xml For Scale Value.

I just think about methods to make a border (in this case the desk) optional.
Cropping the whole interface with a button.
Maybe things like this are doable with vector graphics.

[UD AUDIO]

@Natan said in Community plugin project:

On 200 Zoom, UI & Zoom Box Gets Cutted, and That Box Is Not Accessible.

I didn't think about that but you're right! Thanks for the hint. :)

[UD AUDIO]

1. What is this message?
   Master Chain:! RELEASE_RESOURCES_CALLED
   (Got it without any project loaded and on any project which I do load)

---

2. I'm using master branch and VS2017. Is that fine or do I need to set VS2019?

---

3. Made an update on github.
   The resizing code (line 74) works fine in an empty project.
   But it acts like crazy with the synth.
   Seems like it's conflicting with something else.
   Or is my code bad? For example I used:
   const var Knob1 = Content.getComponent("KnbZoom");
   which does work (with glitches).
   Instead of
   const var KnbZoom = Content.getComponent("KnbZoom");which doesn't.

And also Settings.setZoomLevel(value); instead of Engine.setZoomLevel(value);
because the console said this function is deprecated for some reason.
Not so in an empty project.

Guess I should fix my structure first..

[UD AUDIO]

I guess I should stick with develop branch, IPP 2019 and VS2017?!
There is a new IPP version but it doesn't work with actual HISE right?

[UD AUDIO]

I really like to share the code and elements like knobs.
But I don't want people to rip this plugin and sell it or reuse it without making a custom design.
My plan was to release it for free but I'm not conform with the GNU v3 licence.
Is it true that anyone could rip this off because I have no copyright, even for the GUI?

[d.healey]

@UD-AUDIO said in Community plugin project:

Is it true that anyone could rip this off because I have no copyright, even for the GUI?

Not quite.

Firstly releasing under the GNU GPL means you are definitely retaining your copyright, you couldn't enforce your license if you didn't.

Secondly the GNU GPL is what's called a copyleft license, that means anyone who wants to make a derivative work must release their work under the same license. So somebody could use your images in another project (assuming they are not trademarked) but their work would also have to be released under the GNU GPL.

[UD AUDIO]

@d-healey said

(assuming they are not trademarked)

Maybe I could protect it with NFT or a whatever
https://wipoproof.wipo.int/wdts/about-wipo-proof.xhtml?lang=en

[d.healey]

@UD-AUDIO That won't have any effect on the license

[UD AUDIO]

@d-healey So I need to register UD AUDIO as trademark?
I will never understand licences. It's just to confusing.
If the HISE license systems will get a nice indie license I would go for it.
But I really have no clue..

[d.healey]

@UD-AUDIO If you register a logo as a trademark that will affect the reuse of the logo but not any other images

[UD AUDIO]

But there is another way: Be the first and be the best!
It's just hard without an already existing customer base / fanbase.
I should make music, release some EPs and get some fans :D
And true fans will protect any of my work in any area of the www and maybe darknet aswell hahah

[UD AUDIO]

@d-healey Ok but can I have a trademark on the GUI image or does the GNU license also effect images?

[Lindon]

@UD-AUDIO - you cant trademark a GUI image - its a "TRADE" mark - a mark that identifies your trading entity, also have you looked into teh cost of trademarking?

• you are down a rabbit hole - get out now.

[UD AUDIO]

@Lindon Oh yes I mean copyright. The costs are damn high. But all I do is trying to find a solution to protect a plugin from beeing ripped.
I don't think you can fully protect anything.
And there is no global system for all countries. Well...

My solution:

1. Be the first and be the best :D
2. Make your name big and get your website popular

There might be rip-offs but if people don't know where to grab the original, it wouldn't be my problem right?

[Christoph Hart]

@UD-AUDIO said in Community plugin project:

If the HISE license systems will get a nice indie license I would go for it.

There is already a commercial license system for HISE in place, but in your case I would just recommend GPL and don't bother about possible copycats.

[MikeB]

I don't really understand your intention.
If you start a community project, it should be clear to you that it is usually open source. That basically applies to all components.

Have you ever seen a stolen plugin or a stolen GUI?

If you don't want to make your work public - pay Christoph the licence fee and you can develop a closed, protected application.
Like some people do here.

[UD AUDIO]

@Christoph-Hart Thank you! I will do so :)

[UD AUDIO]

@MikeB

@UD-AUDIO said

Is it true that anyone could rip this off because I have no copyright, even for the GUI?

This is the main thing I wanted to know. And if I can protect my GUI in any way.
Yes you're right and I agreed on making the project public to everybody.
But I wish to release it as VSTi aswell. And because of that I need to know those things :)

I really never have seen a 100% identical rip-off.

I thought that open source is code only. Guess it will take at least ten years for me to get a solid knowledge for making commercial plugins.

Please don't get me wrong. I don't have a problem with that but I don't like to be uninformed.