Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Midnam #78

Merged
merged 6 commits into from
Feb 26, 2020
Merged

Midnam #78

merged 6 commits into from
Feb 26, 2020

Conversation

jpcima
Copy link
Collaborator

@jpcima jpcima commented Feb 25, 2020

This adds the ability for LV2 to export MIDNAM information to Ardour.

The controllers should show in the automation menu with their adequate labels.

It's maybe worth noting that if no controls have labels, nothing will be shown in the menu, so maybe we want to do something about it.

Adds following external code

  • Ardour LV2 extensions (ISC) ­— LV2 midnam interfaces
  • Pugixml (MIT) — structured XML writer library

@jpcima jpcima force-pushed the midnam branch 2 times, most recently from fa5cb48 to 3df1e14 Compare February 25, 2020 14:26
src/sfizz/Synth.cpp Outdated Show resolved Hide resolved

Sfizz LV2 plugin

Copyright 2019-2020, Paul Ferrand <paul@ferrand.cc>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not the author of this file 🙂
On a side note I think there's no real need to track file copyright since we have a version control system, so we can just maintain the LICENSE.md file and author's list globally. I realize now that I updated the C++ library like this but kept my name in the lv2 plugin, I think this is unnecessary.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not about the authorship, but copyright assignment.
When a project is assigned to one single person, it facilitates such things as update the license in the future, if there is ever need.

As I recall, GNU for instance requires copyrigth assignment from their contributors.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I see your point, but I'm not super comfortable asking for copyright assignments. Since we're discussing code style and contibution guidelines in general, I propose we move the discussion on this there since it's not really the heart of the PR.

@paulfd
Copy link
Member

paulfd commented Feb 26, 2020

I need to try it out! Does this work with Ardour 5 or 6? I put minor comments in there, I can correct this myself if you want.

Reading the Ardour extension header, I am wondering if we could use the "Bankpatch" along the MIDNAM to indicate the currently activated keyswitch?

@jpcima
Copy link
Collaborator Author

jpcima commented Feb 26, 2020

Based on a quick check, it works in 6 only.

There is one limitation to expect now, as noted in the OP, only CC which are labelled are listed in the menu.

I will edit later, or you can do so immediately yourself if you prefer.

Reading the Ardour extension header, I am wondering if we could use the "Bankpatch" along the MIDNAM to indicate the currently activated keyswitch?

Possibly, as I have only filled one subset of Midnam related to the controllers.

@paulfd
Copy link
Member

paulfd commented Feb 26, 2020

I added an issue for the unlabelled CCs in #80 since it's going to be easier soon. For the bankpatch as there's no handling of the keyswitch names for now it's less relevant but it could be an interesting addition. I'll be able to change this tonight at the earliest, but otherwise I'm good to merge!

@jpcima jpcima merged commit 3bfa573 into sfztools:develop Feb 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants