Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@LiquidProj3ct wrote:
A question, do you need to program for each plugin this the ability of retrieve names? It’s weird
No. Poise was just returning that it did not support key names for the current program, when Podium requested the name for note #0. I’m now ignoring that return value and continue to request names for all keys. Perhaps there are other plugins that behave this way.
ZynewaveKeymaster@thcilnnahoj wrote:
The GBP top-align bug seems to be fixed in beta 8. Here’s another one, though:
– It’s aligned to the middle position of any visible drum key lanes instead of the whole editor’s height. Just deselect all but one key and it’ll be top-aligned.That’s on purpose. It will do that in the piano roll as well (if you zoom out and have a big vertical pixel resolution). My intention was to align it as close as possible to the event lines. Would it be less confusing if the panel was always top aligned?
ZynewaveKeymasterAnother idea I’m considering:
The piano roll and drum map regions share a lot of functionality, so I’m considering removing the drum map region completely, and instead make the “piano roll” region into a “note” region, which will combine the two regions into one. Some of the latest updates to the piano roll have not made it into the drum map editor, and so combining them will ensure that the event editing is similar in both the piano roll and drum map mode.
So, instead of selecting between the “piano roll” and “drum map” editor profiles, there will be one profile, and you then have a “enable drum map” option in the menu button (as introduced in the new drum map region), which will toggle between the piano roll and drum map layout.
Good/bad idea?
ZynewaveKeymaster@LiquidProj3ct wrote:
Drumazon, Nithonat and Nepheton update their names in Podium 🙂 It fails with Phoscyon, but Phoscyon fail too with other host, so I think it’s a problem of the plugin.
Poise fails with Poise, podium don’t extract the names even. Reaper does it.
Beta9 is uploaded, which works with Poise. Unfortunately Poise does not notify the host when the pad/key names change, so you will need to close and reopen the drum map editor to make Podium retrieve the updated key names. I’ve sent an email to the Poise developer about this, so perhaps a future Poise update will support it.
ZynewaveKeymasterBeta8 is up. If the plugin supports custom key names, they are now shown instead of the default GM key names in the drum map. It should also automatically update the names if they are changed in the plugin. Of all the plugins I have installed, I only found that the Drumazon demo supported this. Let me know if you find any plugins that you know should support this, yet doesn’t show its custom key names in the drum map editor.
ZynewaveKeymasterSome more thoughts:
I’m considering dropping my previous idea about global drum map files, and instead store any customized key names directly in the track properties, similar to how the note enable/solo/mute state is stored. Thus if you save a track template with your drum plugin, the imported track will automatically have the customized key names. No need for messing with drum map selection etc. The copy/paste commands in the drum map menu will also include the note names.
I also intend to implement the custom note naming in the piano roll. This will be particularly useful when you for example work with large sample based instruments that support key switches for selecting different articulations. You could name the keyswitches in the piano roll with “Legato”, “Pizzicato” etc. so that they match the key switches used in the sampler. A custom color option here would probably also be useful, in the case that you are zoomed so far out that there is no room for writing the note name on the black/white keys.
Am I getting colder or warmer? 😉
ZynewaveKeymaster@Trancit wrote:
A very elegant way I think, is the integration in the piano roll editor and to be able to switch via the “View” menu between the classic piano roll and the drum editor…the best integration at the moment is in Reaper, imho.
Is there anything in Reapers drum map handling that you prefer over the changes I’m currently making? If you want Podium to improve, you’ll need to give me some more details.
ZynewaveKeymasterBeta7:
Some UI adjustments and bug fixes.
The drum map enable/solo/mute is now added to the undo history.
The note audition will stop when the mouse is released.
I’ve given the drum kit preset feature some thought:
I developed the current drum kit preset feature many years ago, back when the focus was external MIDI modules and their proprietary ways of handling drums. Fortunately it has become much easier to work with drum plugins. I think it is time to retire the drum kit preset feature completely, and implement a simpler solution for reordering and renaming drum keys in the drum map editor.
Instead of having the drum maps in the project file, the drum maps could be stored in the global setup. One solution could be to include all drum maps in the Podium.ini file, but this means you would lose all the drum maps if you select the “restore default setup” command. A more advanced solution could be to have each drum map as a separate .ini file in a new “Drum Maps” folder, similar to how the color setup files are handled.
The drum map editor menu will then have a submenu for selecting between the drum map files found, along with commands such as “create new drum map” etc.
Comments?
ZynewaveKeymasterI’ve now changed it so that the note audition will stop when you release the mouse button. Clicking shorter notes will still only audition the true note length, even if the mouse button is still being pressed.
ZynewaveKeymaster@em32sn006 wrote:
Can you tell me whether there is a way to directly modify/edit values inside a fxp file containing presets for my VST?
The fxp file is a binary file and not a text file, so it will be very tricky to modify the fxp file directly. You’ll need a binary utility tool and some knowledge about the structure of an fxp file.
ZynewaveKeymasterBeta6 is up:
Made some changes to the button layout in the left side panel of the editors.
Added audition on/off button to the piano roll and drum map regions.
Added the grid button panel from the piano roll to the drum map region as well.
ZynewaveKeymaster@em32sn006 wrote:
I need to precisely set the values into my VST interface (I’m working with an Eigenmike32) but they only change by more or less regular steps, so I’m unable to get the desired value. Is there a way to get a more accurate control over the knobs or, even better, a way to numerically enter the desired values?
I’m guessing the plugin you are using doesn’t have its own editor, but instead uses the Podium native editor interface. If that is the case, then you can hold the Shift key down while clicking a parameter dial, to fine adjust the value. There is currently no way to enter a numerical value in the Podium native editor interface.
ZynewaveKeymaster@Trancit wrote:
And one more:
Is there any option to set up, at which level the “Level Meter Overload” starts taking effect…
In my current settings, it starts at about -6db, but I would like to set it to about -1db or -0.5db…
I think -6db is definetely to soon to start turning the master level meter to deep red (yes I know I can change the color, but red is good for showing overloads, but overloads for me are more than 0db)Trancit
I assume you mean the default master output meters. If you click the meter in the mixer, you can toggle the RMS meter scale on/off. Alternatively you can configure the RMS scale in the arrangement properties dialog.
ZynewaveKeymaster@Trancit wrote:
How to bounce the individual outputs of an VSTi like in this tutorial:
http://www.zynewave.com/videos/Podianer/offlinebounce.html
There are no “group bounce tracks” anymore, aren´t they???
A lot of things have changed since that video was made. For a more recent video of how to work with multi-output bouncing, check this YouTube video:
ZynewaveKeymaster@LiquidProj3ct wrote:
Could you consider add it as an option in piano roll options window?
Perhaps in a future update. I think there are going to be plenty of changes in the 2.31 release, that I would like people to get used to before making further changes.
