ZynewaveYou need to create a new parameter object inside your device definition. Name it ‘Prg change’ (or whatever you prefer), set the type of this to ‘MIDI Program Change’ and set the range from 0 to 127.
In the arrangement you can create a new subtrack to the track with the device mapping. Drag the ‘Prg change’ parameter object onto the beginning of this track, and you get a parameter event with a dial where you can set the program change number. You can drag any number of these events onto the timeline, to create program changes at various positions during playback. You can also edit these parameter events using the event list in the track inspector.
ZynewaveDo you want the cut action to cut through all events in the arrangement that overlap the cursor position, or just the current track, or maybe just any selected events?
What is your typical purpose of this cut; To rearrange stuff, or to silence a section, or other?
Zynewaveis hard when doin’ fine automations strictly related to the note part if you can’t see the actual notes…
If you put the parameter tracks as child tracks to the note sequence track, then the notes will be drawn on the background of the curve editor.
ZynewaveHi lalo,
I’ll consider this as another vote for ‘in-place’ curve editing in the arrangement editor. The curve sequences are not related to note sequences other than their track-relationship in the arrangement editor. So embedding a curve editor into a keyboard editor window would be a mess, both in the UI and in the code.
ZynewaveI have changed the values in the Parameter Properties (I’ve put 0 to 127 and default to 64, is there any standard better values ?).
Depends on the parameter. I assume it is VST plugin parameters you are referring to. If a VST parameter on the UI is e.g. a value from 0..100, you would enter these values as min/max in the parameter object.
Result : the last value when I stop moving is held !
Hmm, are you sure it is not set to the default value you entered (i.e. 64 ~ 0.5)?
ZynewaveConcerning my first question, perhaps the jumps to 0 during the movements with the objects are due to the fact that they are not very regular ?
So, each time that my hand makes a little stop Podium thinks that the automation has finished and puts the default value ?
No that should not be an issue. Note that even if a plugin does not support the BeginEdit/EndEdit calls, Podium still remembers the last recorded parameter change, so that when the next change is received, it will erase any old events that is recorded over. Only problem is that the plugin can behave odd, because it receives parameter changes for a control that you may be editing by mouse dragging.
ZynewaveCould you describe the situation/workflow where you would use this shortcut?
Zynewavewhen I put some parameter on a track its value turns to 0 each time Podium starts playing
It will be set to whatever default value is defined in the parameter object properties. Whenever there is a blank interval on the track without a curve sequence, then the parameter is set to the default value. If I were to change this behaviour, so that parameters were never set if there wasn’t a curve sequence, it would have other potentially confusing implications. You would have ‘holes’ in your arrangement where a given parameter could have a random value, depending on whether you have manually moved the play cursor or changed the parameter in the plugin or synth. Thus playback would sound different, depending on where you started. If you e.g. automate a pitch-bend parameter, then the pitch-bend would be left in whatever position was last played. As it works now, Podium is in control of the parameter value at any position in the arrangement.
Zynewavewhen I automate plugins values within their interface, the value “resets” to 0 from time to time
Are you recording into/over an existing curve sequence that already has events?
When you e.g. loop while recording and grab a control to change the automation, then the behaviour depends on whether the plugin supports the effBeginEdit/effEndEdit calls. If the plugin supports these, then Podium will be notified that a parameter is being held (and thus automated) and Podium will then not play back any existing automation while the control is held. If the plugin does not support the BeginEdit/EndEdit calls, then Podium has no way of knowing whether a received parameter change is the last in an ongoing automation, and will thus play back existing curve automation.
ZynewaveThere is none. You have to select the scalpel tool and use the mouse.
ZynewaveCould it be possible that it will scan the subfolders and find the dll that are presents ?
If you load a project that contains references to plugins that are placed elsewhere on your harddisk, then you can use the ‘search’ button in the project wizard plugin panel. This will also search subfolders.
If you import plugin device definition files in the project wizard, then Podium will also search subfolders, if the plugin is not found at the position specified in the definition file.
ZynewaveBut perhaps is there already a possibility that I didn’t simply don’t know
No. The events are created in bar mode, so that playback will reproduce your exact drawing actions. Rather than creating options for alternative behaviour, I would prefer to start work on ‘edit in place’.
ZynewaveI don’t remember what is the name of the left zone in the arrangement
I usually call it the ‘track inspector’, but feel free to use other names.
This feature was on the plan until I made the extensions to the object list window with file browsing. I guess it still would be useful, but it probably should be an option. Each panel tab that is added to the inspector, will reduce the height available for the active panel.
I’ll add it to the plan.
Zynewave1.23 is released. I have not yet looked at the delete event/track issue, as promised earlier in this topic, but it is next on my list.
Zynewave