Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterI think it just might!
Good. I’ve already made the modifications. Podium 1.76 is just released.
Hints:
Locate your MIDI input mapping in the devices panel on the project start page. Right-click and use the “New copy…” command. Give it a proper name and press OK. You now have two MIDI inputs in the track inspector input panel. Assign one on the track with NuBiPlus and the other on the track with Spinner. I hope that works.ZynewaveKeymaster- Waveform display scales after fade curve.
- Fade curves are shown on all clips.
- Right-click menu for fade curve defaults.
ZynewaveKeymasterI guess what you are looking for is a way to assign the same MIDI input (your keyboard) to both NuBiPlus and Spinner. Podium restricts a MIDI input object to only be assigned on one track, to avoid confusion, and to make it easy to drag the mapping from track to track without having to unassign it from the old track. A solution for you would be to create a second MIDI input object mapped to the same MIDI input. You can then assign MIDI1 to Spinner and MIDI2 to NuBiPlus. In effect you duplicate the MIDI input from your keyboard into the two MIDI input objects. As a consequence, both Spinner and NuBiPlus receives the notes and CC#1 messages. This may be undesirable if NuBiPlus reacts to CC#1 or Spinner reacts to note messages.
Will this setup do what you want to achieve?
Currently Podium does not allow two MIDI input objects mapped to the same MIDI input, but I can remove this restriction.
ZynewaveKeymasterThe only remaining track count issue is instrument tracks as unless I have missed a crucial step I cannot insert an FX mapping on the same track where an instrument mapping resides.
It should be possible to route both the effect and the instrument plugins in a zGrid instance, so you can do it on a single track if you want to.
ZynewaveKeymasterI’ll check my code tomorrow, to see if I can come up with a solution. I may have to do a small modification to the MIDI input mapping handling.
ZynewaveKeymasterAny mock up screens yet we can comment on?
No.
I wonder if it may be a good idea to have a zGrid built into each group track already for ease of use?
I’ve thought about building the functionality into Podium, but there are various reasons why it is a good idea to keep it as a plugin. For one, you can use the existing preset library system to store your zGrid routings.
ZynewaveKeymasterSpecifically I need to use MIDI CC #1 from a keyboard to control the speed of Spinner’s rotors and at the same time use the MIDI Note On/Off messages to “run” NuBiPlus.
Is this routing already available in Podium?
Can you set your keyboard up so that CC#1 and the note on/offs output on different MIDI channels?
ZynewaveKeymasterYes, you can automate both instrument and effect plugins with MIDI parameters. What is not supported yet, is routing MIDI output from one plugin to another. This means that plugins whose main function is to output MIDI to drive other sound generating plugins are not usable with Podium currently.
ZynewaveKeymasterWill this be for effects only? Or let me re-phrase that, will it be audio only, or will it be possible also to send MIDI through the grid. The idea is to chain or stack plugin synths with effects…
The first version may not support it, but it should be possible later on to support routing MIDI through the grid as well. You could then layer synths and play them with a single track/MIDI input.
ZynewaveKeymasterWhat would zMatrix look like? I’m imagining a window with about 8 – 16 boxes, and a clear signal path going from the first box to the last. You can load a VST effect in each box. And then drag the boxes around to rearrange the order of the effects.
That’s a good guess. It will be a user configurable X*Y grid where signal flows from the left edge of the grid to the right. Placing effects on a row creates a serial routing, and placing effects in a column creates a parallel routing. There won’t be any wires to drag. The placement in the grid decides the routing.
I’m also considering naming it zGrid (pronounced Siegried 😉 )
ZynewaveKeymasterI assume you mean the disk subfolders named after the arrangement.
These folders will only be created when saving all changes and only if there are any unsaved sounds in the arrangement. To avoid getting the subfolders you can use the “save as” command on the bounced sound before using the “save all changes” command.
ZynewaveKeymasterI could be wrong but I think being able to add an effect plugin (or two) on an existing track is an expected feature these days.
With unexpected I was referring to the routing and UI features i have planned for zMatrix.
The simplest use of zMatrix would be to chain plugins inside the zMatrix editor. You would then only need one track with a zMatrix plugin and the embedded zMatrix editor would allow you to arrange any number of plugins in serial/parallel routings. Thus you don’t have to create multiple chained tracks for individual plugins.
ZynewaveKeymasterI cannot remember where, but I think you said something about some sort of plugin chainer or rack that would do away with the need to have each FX on it’s own track. Is this still under consideration?
That is indeed the way I intend to go. Working title for the plugin is zMatrix. I have not started implementing it yet, but I have a good idea of how it is going to work. There is going to be a couple of novel features in that plugin. I would have started it a long time ago, but there have been so many requests for other “standard” features that I felt I needed to get them out of the way before starting on some of the “unexpected” features.
I could potentially use Phrazor or Energy XT but I think using either of them as an FX rack in Podium might stop Podium from delay compensating for FX hosted within them while used as an insert in Podium. Do you know if that is correct?
If the host plugin calculates the latency of its plugin processing chain and reports it back to Podium, then PDC should be ok.
ZynewaveKeymasterAfter a days work: The waveform shown on sound events are now scaled according to the event gain and fade in/out time settings. Available in release 1.76.
I think I’ll wait with the support for customizable fade curve defaults. Instead I could easily add a few fixed defaults that can be accessed by right-clicking the fade in/out handles on the event. The two obvious choices would be “Linear” and “Equal power”. Linear is -6dB and equal power is -3dB at the middle of the fade-in/out. What other curve defaults would you find useful?
ZynewaveKeymasterThis resolved the problem.
Excellent 🙂 . Sorry for the troubles it caused you.