Zynewave's Forum Page
Forum Replies Created
-
January 23, 2009 at 15:55 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.January 23, 2009 at 14:54 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.January 23, 2009 at 14:19 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.January 23, 2009 at 04:58 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.January 23, 2009 at 04:51 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.January 23, 2009 at 03:57 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.January 22, 2009 at 23:52 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.January 22, 2009 at 17:55 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterCurve automation of tempo is not yet supported.
ZynewaveKeymaster@swindus wrote:
Little bug: When adjusting the fade curves in the sound event dialog the curve display only updates when the focus is changed to another input field.
That’s the standard behaviour in all Podium dialogs. If the curve display should be updated for each key press, then the display would e.g. jump from anywhere between 0, 1, 2, 9, 19, 20, 201, 2019 etc. depending on how you change the value “19” to “20”.
January 21, 2009 at 20:21 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@Pigini wrote:
@Zynewave wrote:
Not true. Adding dotted notes with the mouse is always aligned at bar start when snap is on.
Hugh? I tried it yesterday and it was all over the place. Will try it again when I’m home. Well, you’re probably right, having programmed the app..
Guess I must have done something wrong as tired as I was, or my graphics shifted or whatever. 🙄However, trying to be witty with me over a minor detail, while ignoring a suggestion entirely (IMHO a very useful one), is very rude. If you had bothered reading, you would have realized just with how little an effort Podium could have the quickest note input, and not just the very same lame thing any average host has.
It’s not the first time you seem to be fighting off good ideas, esp. the original ones, and do some catching up on trivial matters instead, polishing buttons or whatever.
… Maybe programming functionality is just not so much fun as gui-stuff. Don’t you realize, just how much interest there is in functionality esp. with the piano roll?You’re such a Diva sometimes. 😆
I’m not upset btw (since it’s written, it could get misinterpreted esp. when it is confrontational), it only needed to be said. 8)
What did I do wrong to get such a reply 😕
My comment about dotted note alignment was not meant to be witty, just correcting a false statement. At the moment I’m implementing shortcut buttons to note values. Something you requested earlier. I already stated in an earlier reply in this topic that I would not reply to individual posts, but gather up the ideas and implement them as I go.
ZynewaveKeymaster@Pigini wrote:
But try another one:
A dotted quarter, that you want to put in at the start of a bar (getting it right, without moving it later) – you can’t (unless it’s the first bar of the track).Not true. Adding dotted notes with the mouse is always aligned at bar start when snap is on.
ZynewaveKeymaster@LiquidProj3ct wrote:
About the first problem is that I’d like use the Poise’s multiple inputs (and no outputs) with drums view for each input. In the example I uploaded I want use “the drums view” for both inputs, and no with the piano roll. That’s my problem.
The ! error appears because you have two tracks with a library preset assigned. That can lead to possible conflicts, since the plugin current settings then would be stored twice. You can solve it by creating a drum kit preset that is not a library preset. This requires some manual setup of the preset objects. You can see how this works with the “Kit Template” Drumatic preset in the Freebees example project. This setup is a bit complex, so it is not a solution that I can recommend.
Another possibly simpler solution can be used if you don’t need to send the two drum tracks to separate Poise MIDI inputs: Select the Poise (#1)(01) track and activate “use as group track”. Now you can create any number of child tracks which all will use the drum editor, but they will all play into the (01) input.
I’m not happy with the current method of setting up drum maps in Podium, so that is something I’m going to revise in a later update. I’m thinking about a solution where you don’t have to have the drum kit preset assigned to a track to activate the drum map editor on that track.
I’ve talked with Shannon already, and now I’ve a new version of Poise, where the bug is fixed.
Is that the bug where changes in the plugin is not saved when doing a save project in Podium?
ZynewaveKeymasterNo. You’ll need to automate the VST parameter for bypass, mix, wet/dry or whatever the plugin calls it (if supported by the plugin).