Let me introduce my first LUA script “MIDI Glue”, that “glues” midi regions in “G”-mode.
Here you can download the script and read installation information:
In outline this script expands Ardour’s possibilities (increases speed) to Consolidate MIDI regions.
Standard workflow requires switching from mode “G” to mode “R” or to run a command Set Range to Selected Regions, then from context menu run the command Consolidate.
The script - if you’ll make some assignments (described in the Installation in GitHub) - lets you just select the desired region/regions and simply press Alt+G & Enter combination - and you’ll get the “glued” MIDI:
PS: This is my first attempt to make a usable thing in GitHub - any advises¬es from skilled devs are welcome!! Good luck!
Thanks to: @BenLoftis @x42 @johndev
EDIT: Few conditionals for correct gluing ALL the midi notes:
All the layers must be transparent (not opaque) (Alt+0):
Hello, first, congratulations! Since you asked for tips about distributing a project from a repository (in this case, Github), here is one: even if the script specifies a license in its header (MIT) and that’s already fine for most purposes, generally it’s good practice to include a LICENSE file in the repo containing the body of the (MIT, in this case) license.
I’d like to include the acceptance of this dialog somehow into the script, but not enough knowledge at this time. May be @x42@paul@BenLoftis or somebody could help?
This could be so comfortable to “glue” without any dialog, especially since in most cases it is enough to accept the default conditions.
Thanks! Not so distributing, but just help to users like me to use the script. If I will not mention any license - does that mean - everybody can freely using the script?
PS/ If every homeless punk could use this without any asking - I’ll be happy! :))
On the contrary, not mentioning the license in any way means the opposite - that the code is to be considered proprietary, all rights reserved and that homeless punks cannot legally use it.
In this case, there is a reference to the MIT license in the script header which is sufficient, but in general, to avoid any misunderstandings, it’s always better to include an explicit LICENSE file containing the full text of the license (it would be even better to add in the README something along these lines: “All files in this repository are released under the terms of the MIT license.”). This is a general suggestion for all free/libre and open source software, not just for your specific case
Hard to say without a reference to specific country laws so let’s tackle it from an international law perspective. From my understanding (as someone who has studied a bit of law but is not a lawyer, corrections accepted!), the Berne convention makes this rule. Allow me to quote the official WIPO website
(b) Protection must not be conditional upon compliance with any formality (principle of “automatic” protection) .
Basically, when you create a work, it is automatically protected by traditional copyright. To give users some additional freedoms, you have to specifically state them. This, in the world of free and open source software, means explicitly adopting a license approved by the FSF or OSI (like the MIT license). If you don’t, the strictest possible copyright (all rights reserved) automatically applies to it.
Edit: this, of course, not for your specific case (as saying “MIT” in the license header IMHO is unambiguous) but in general.