Corwin

Why are you acting like this?

I am not “giving up” but rather just realizing that midibox is not the way forward with the project I have in mind. Part of that is how the open-source aspect is organized. It seems to work for you guys and that’s great but it’s simply not how I prefer to work and not what I’m looking for in an open-source project—I may look closer at the Mutable Instruments designs. But part of it is down to your behavior in this thread and DMs. It feels really disingenuous to tell me I just need to ask questions and you’ll help, when the only thing I’ve done is ask questions and you told me multiple times to be quiet. Please leave it alone. You were unhelpful in this thread and very rude in private messages. Hawkeye and latigidon answered my questions and the discussion needs no further elaboration.

This is what I was referring to: > You can understand that when someone spent a lot of time to design a device, he doesn't want to see it cloned and resold without his consent, yes or no? That's the reason we tend to do not share the layout of our project, just to protect it. like I said already, I am not trying to clone or sell anything. I’ve just been trying to figure out what is allowed and what isn’t, specifically so I can respect the wishes of the creators.

Please stop sending me notifications, I already got enough of them from the rude DMs you sent me.

I’m thinking I probably won’t move forward with midibox as the base for the project I have in mind. I think I understand (roughly) the hardware licensing but I would like to work with software that has a better defined license. I also have antichamber in my DMs sending me angry messages, accusing me of intentionally starting trouble and being disrespectful and telling me to be quiet. Don’t really want to deal with that every time I have a question :/ thanks to Hawkeye (edit: and latigidon) for being patient with my questions (we eventually got there!) and generally being helpful. I apologize if anyone thought I was being disrespectful. I’m not new to open source, software development or diy synths, but I am new to MIDIbox, and things seem to be handled a bit differently Here. So I hope that explains my confusion and my questions.

>So, to answer your question: assume everything listed on ucapps.de is released under a "free for personal use license", everything sold commercially has to have been "ok'ed" by TK. before and those products do not automatically inherit full disclosure obligations of every file needed to create the product. If a "vendor" asks TK., if it is ok to release a MIDIbox-based product commercially, TK. will always ask for guaranteed customer support and probably look for a good track record in the forums of the respective creator over some years. Thanks, that definitely explains things a little better. Sounds like the older projects are all open to one degree or another but that people can modify and sell the designs and keep those modifications closed? That doesn’t sound like what I read in the tapr license but maybe I read it wrong or maybe the community here just has its own conventions; either way, that’s why I was so confuses. (back to your side note from earlier, discussions like this are exactly why most open source licenses are lengthy and detailed. It’s important to know how rights/protections transfer to derivative works, whether we are allowed to share those derivative work [or are actually *obligated* to share], exactly the kind of stuff you described.)

Not escalating anything, just trying to get some clarification on what parts of the MIDIbox ecosystem are open, what parts are closed, etc. (but yeah, don’t really appreciate the insinuation from the other guy that I’m trying to do something dishonest or underhanded when it’s the exact opposite: I’m just trying to get a handle on what is and isn’t allowed.) (responding to your personals aside, licensing is important for developers. It tells us how we can use and share the existing code, the code we modify, etc. there’s good reason the open source community has settled on these detailed licenses. I don’t know anyone who would be willing to put much time and effort into something without a clear idea of how it could be used going into the future.) but anyway, what I was hoping to get information on was the hardware, and it seems like that’s a mix of open (licensed under tapr) and closed. Still trying to figure out if there’s any easy way to know what is open and what is not?

Is there really no further detail than that? Usually there are clear stipulations about how the software can be used or modified, what rights the original creator retains, etc. I’m not trying to clone or resell anything without consent. If someone doesn’t want to share their work for fear someone else will use it, that’s fine...but it also isn’t open-source. Uh, yes she does. She shares the PCB layout files, the schematics, the panel design files, and the firmware. It’s all completely open, even for commercial use. Im here asking questions, aren’t I? not interested in making a commercial product but thanks

Is there any way to tell what is open source and what isn’t? I am finding this all extremely confusing, I thought MIDIbox was always open source and collaborative. on a similar note, does anyone know the licensing for the software? I tried looking it up after reading this thread since the person above said that’s the one thing that is all completely open but couldn’t find anything about software licensing, only the hardware license (tapr?) I had hoped to base my project on some MIDIbox designs but now im concerned that I’m gonna make a mistake and some part of it is not allowed to be copied.

sorry, I’m just confused. I know about what’s on the ucapps site. But there’s MIDIbox stuff that’s not on that site. I thought MIDIbox was all open-source and non-commercial, but I actually have to buy stuff to access the documentation?

I’ve seen what’s on ucapps and MIDIbox, I am looking for the newer stuff that MIDIphy has put out. Unless I’m missing something on the ucapps site?

Sorry, I’m still confused where the open-source documentation is?

No, I was looking into DIYing a CV sequencer from scratch.

Hi, maybe I’m missing it but where are the open-source files for all the MIDIbox stuff that MIDIphy sells?