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

Add Red Zeppelin 5 kit #14

Open
SpotlightKid opened this issue Oct 23, 2019 · 8 comments
Open

Add Red Zeppelin 5 kit #14

SpotlightKid opened this issue Oct 23, 2019 · 8 comments

Comments

@SpotlightKid
Copy link
Contributor

The current distribution of AVLDrums also contains a version of the Red Zeppelin Kit with samples of an additional floor tom (instead of the 16" floor tom edge, I believe), called "Red Zeppelin 5".

It would be nice to add variant of the LV2 plugin for this kit too.

This would make a new UI necessary (new picture and new hit map) and maybe even a few changes to the structure of the plugin to support multiple different midnams and text overlays in the UI.

@x42
Copy link
Owner

x42 commented Oct 23, 2019

It'd likely need to be a new plugin (new URI), too.
Picture has to come from Glen (he photographed the actual kit).

Keep in mind that the .sf2 was significantly modified from the original. Panning matches the one on the image, leading silence has been cut, velocity-layered samples were aligned and exclusive groups were added.

I may sit this one out until Glen finishes his percussion-set and then schedule a long-week-end of sample-lib overhaul for the whole thing.

I also regret not using a standard-MIDI mapping for the main kit -- and adding extra samples outside that default range. if an URI update is due, I might re-do the mapping, too.

@SpotlightKid
Copy link
Contributor Author

SpotlightKid commented Oct 23, 2019

Picture has to come from Glen (he photographed the actual kit).

Yep, though I have a mind to try to render a picture from a nice Blender 3D model of a drumkit. Need to find good free model first and also for the various percussion bits.

Keep in mind that the .sf2 was significantly modified from the original.

Yes, I read the readme in the sf2folder. Did you do these edits manually? It's easy enough to export the samples with Polyphone and edit and re-import them. A comparison of the samples of original the Red Zeppelin 4 and 5 kits might show that the samples are the same except for the 18" floor tom. Then only those samples would need to be edited as well.

I also regret not using a standard-MIDI mapping for the main kit -- and adding extra samples outside that default range.

BTW, what about the Roto drums?

@x42
Copy link
Owner

x42 commented Oct 23, 2019

BTW, what about the Roto drums?

Intentionally left off, since they're not on the picture. upstream (Glen) suggested to not include them, anyway.

@SpotlightKid
Copy link
Contributor Author

I may sit this one out [...] overhaul for the whole thing.

I you do that, I think it would good to put the note-mappping and the midnam in an external file (for each drumkit), so it can be replaced more easily.

@x42
Copy link
Owner

x42 commented Oct 23, 2019

If you want to mod the kits, use drumgizmo or the .sfz.

The main idea behind the avldrums plugin is to have a consistent "works out of the box" experience.

Otherwise it's already easy to just load the .sf2 in fluidsynth along with a custom midnam.

@SpotlightKid
Copy link
Contributor Author

Otherwise it's already easy to just load the .sf2 in fluidsynth

Except that setting up multi-channel is a hassle and not as efficient.

@x42
Copy link
Owner

x42 commented Oct 23, 2019

More multi-channel will be tricky anyway. At most there are 16 individual outputs, since
the plugin uses MIDI-channels for this under the hood.

x42 added a commit that referenced this issue Nov 13, 2019
Suffix "AVL-Drumkits-LV2" with colon and 64bit unique ID
@x42
Copy link
Owner

x42 commented Nov 13, 2019

OOPS. sorry that commit should have mentioned #16

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

No branches or pull requests

2 participants