ZynewaveZynewaveZynewaveZynewaveZynewaveZynewaveCurve automation of tempo is not yet supported.
Zynewave@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”.
ZynewaveZynewave@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.
Zynewave@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.
Zynewave@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?
ZynewaveNo. You’ll need to automate the VST parameter for bypass, mix, wet/dry or whatever the plugin calls it (if supported by the plugin).
ZynewaveHi ZChris,
Welcome to the forum. I’m glad you like the Podium experience so far 😉
Frits
Zynewave@Pigini wrote:
I was thinking of getting the input right with the wanted duration at the chosen place in the timeline directly when creating the note.
In most apps note input is linked with the quantization as you explained above. Of course I want to put in a note of a certain length, but I want to snap it to a value, which might be different from its duration. I find it a bit confusingly difficult to explain.
As you mentioned, this would require two different snap/quantize value settings. I think the added flexibility unfortunately adds complexity for users wanting to do simple note input. They would often need to adjust both settings when going from eight to quarter note input etc.
The way it works currently, you should set the quantize value to the lowest resolution you want to work with. If you want to add quarter notes on eight note resolution, set the q value to 1/8. When you click to add notes with the mouse, the default size will be 1/8, but then simply drag right to a full 1/4 or any size before releasing the mouse.
Zynewave@Conquistador wrote:
Cheers Frits!
To save you time…I have now added a 3rd sidechain tutorial that covers your 2 track set up.
Many thanks.
I changed the name of the first tutorials to highlight the fact that they use 3 tracks (which can be useful as the 3rd OUT track can be used as a dedicated bounce track).
But your 2 track idea is quicker for those who do not need a dedicated 3rd output track. 8)
I think you can just as easily use bounce on the main track in the two-track setup. The bounce waveform may be drawn on top of the audio sources on the track, but I don’t see that as a problem.