Conquistador's Forum Page

@Zynewave wrote:

Which image are you referring to?

The widest image. It has the 1+2 mapping assigned but no preset.

Thanks for spotting that. I have now changed that image so that it is consistent with the project I used and the rest of the latest changes to the tutorial.

Here are some of the things I came across while I was putting the tutorial together…

1. There is a need to refresh certain views before a drum map appears within Podium.

2. When recording drum maps in realtime using a keyboard, sometimes the notes would get dropped or not played back until the loop had restarted. (Two bar loop). This behaviour was erratic at times.

3. “The key range defined in the drum key preset properties determines which note events are displayed on the drum line.”

Selecting a key range in Program properties will *not* remove unwanted notes in a drum map. I tried this and it made no difference at all. What am I doing wrong? The only way I can see to change the notes or drum names on a drum map is to do so in the List view.

@Zynewave wrote:

I have now added the “Create Drum Kit Template” command to the preset panel menu. This should simplify/remove some of the steps in your tutorial. Will appear in 1.75.

Just caught your post…thanks! Looking forward to that 🙂

@Zynewave wrote:

Very nice. Thanks for the contribution.

Thanks! Happy to help 🙂

Some comments:

You mention in several places that you can right click below the last track to create a new track, and then either double-click a mapping or drag it to the track. Maybe it would be good to mention the shortcut; that you can drag a mapping below the last track to create a new track assigned with the mapping in one go.

Yes, good idea I have added this to the tutorial now. 😉

You describe that the 1+2 mapping matches “Output A” in the plugin, 3+4 matches “Output B” etc. It may be a useful addition to the tutorial to describe that you can rename the mappings so their name matches those used in the plugin. Right click the “StylusRMX (#1) Out 1+2” mapping, select “Properties”, rename to “StylusRMX (#1) Output A” etc. A small note describing that the (#1) refers to the plugin instance number may also avoid some confusion.

All good and I totally agree…I added your suggestions here as well to the tutorial. 8)

Seing the images in your tutorial has given me a clue to your problems with plugin settings not being saved without a library preset. It seems that the plugin import did not create the “Local Bank” library preset. This would otherwise automatically be assigned to the track when you assign the first Stylus mapping to a track.

I have modified the tutorial now, so it is probably better if you have another look at the changes as it may answer your question. I removed the reference to a New Program Library preset as it is an uneccessary additional step, as Stylus has a default Program preset assigned to it’s first 1+2 Output mapping when it is dragged to the arrange view anyway.

I thought that a Library preset would be better as I assumed it would allow me to save the kit for use in other projects which is not possible in Podium, so I have re written all references to creating a New Library preset and replaced it with instructions on how to modify the default Program 1 preset (that Podium assigns to Stylus) into a drum kit instead. I added an image to illustrate this.

The image with your stylus mapping shows no assigned preset. Could it be that you started this tutorial project using an old project created before the new “Local Bank” preset system was implemented?

Which image are you referring to? I have changed one of them this morning after reading your post.

I’m considering adding a “Create Drum-Kit Template” command to the preset panel menu. This would replace the need for opening the properties panel and clicking “Use preset as a drum kit”.

Yes please I think that will simplify things. 8)

The problem with the the way you do it, is that you convert the preset used to store the plugin settings to a drum-kit. This means you can only assign this preset to one track. This would be a problem if you wanted to use multiple tracks with the separate MIDI channel mappings.

Agreed. This is one of the observations I came across while putting together this tutorial but the process described in the tutorial is perfectly suitable for drum programming when a user wants to use one midi track to build up his drums but still hear each drum sound (Kick, Snare e.t.c) on a different output. 😉

Having a kit template preset that does not store plugin settings means you can assign it to any number of tracks. I do this with the drumatic plugin in the Freebees example project.

I’ll take a closer look at that. 8)

Your description of how to save the drum kit preset to avoid going through the setup of the kit again in the future is not possible unfortunately. As I mentioned in an earlier post, saving to a VST preset does not store information about the kit customization you make in Podium. VST preset files only stores the settings provided by the plugin.

Correct, I have fully updated the tutorial now. 😉

Ok the tutorial is ready now 8)

I already have it as a .doc file but I need to get into the WIKI. I can get into the playground and that seems ok but how do I add it to the existing tutorials Frits? Or does it need to go somewhere else?

I suggest the WIKI as the text is about 4 – 5 pages. It will be a very long post here on the forum otherwise. 8)

As for the project I have deleted tracks and made many changes so there is not much left to send you but I could create a Stylus project with a drum map quickly so you have something to see. Is that helpful Frits? ❓

I’m not sure what you mean. If you have the tutorial done, you could publish it as it is and we can discuss things that can be improved.

Good idea. I’m just tidying up a few things and adding some images.

You could also email me your project file.

Yes no problem. 😉

@pj geerlings wrote:

I won’t hold you to this schedule but this is great news!!

thanks,
pj

😆 No worries.

A question for Frits though…

I have come across a strange problem while writing the drum map tutorial. While it is possible to use the default Program as a drum kit by right clicking and converting to a drum kit there is no way to save this Program.

It appears the only way to save a drum kit is to create a Library preset even if a default Program is already there in the preset panel for that track.

It seems a bit strange to be able to create a drum kit as a Program or Library preset but only be able to save it / export, if it is a Library preset. No options exist to save / export Programs as a drum kit or am I missing something?

A simple right click on a Library preset > Properties brings up Import / Export options. Simple.

For Programs the properties page does not allow for a user to save the drum kit. What am I missing or is it just not possible to export / save a Program as a drum kit?

@soundquist wrote:

@Conquistador wrote:

Although for anyone else reading this thread, if you do not use Stylus it should be very useful as well, as the steps apply to just about any drum module. 😉

Looking forward to your tutorial!

/SQ

Not far to go now, I have pretty much finished the text. All that is left are the images for the tutorial. I will get back to finishing that early next week. 😉