LiquidProj3ct's Forum Page

@Zynewave wrote:

2. Suggestion: Click on a blank spot above or below the curve points you want to edit, and then drag up/down to align your edited curve section with the existing curve.

i’ll get used at it 🙂

Thanks for new beta Frits. Please consider fix(?) these suggestions:

@LiquidProj3ct wrote:

Some automation recording problems:

1. The fader of the parameter record its movement even if track is unarmed and master record is off. This is an old behaviour (bug?) that I don’t like at all.

2. While I record, if I tweak a VSTi parameter the movement is recorded in the curve sequence (that I created before start recording with a certain curve). However if I stop of move the knob and keep it in a certain value the curve sequence isn’t updated (bug? bad behaviour?)

Thanks

@pavouk100 wrote:

No, I mean really VST plugins , but using podium’s native UI – you can force podium to bypass plugin’s UI (by ‘Use generic editor instead of plugin editor’ checkbox in ‘Device mapping properties’ of any VST plugin). In this case, podium knows very well about proper ranges and units for every tweakable (automatable) parameter, so this leads me to believe that my original requested feature is feasible. 😉

I understand now 🙂 Unfortunately I don’t think that Frits could do nothing here, except improve the interface of nongui plugins: those units come defined inside the vst. Check mda detune vs firebird:

@pavouk100 wrote:

Ah, ok. But then, how can internal VST ui editor know about correct units?

Because those aren’t VST, they’re ‘z’ plugins 😉

@pavouk100 wrote:

I know that it is relative level. and I know that I can increase main fader. Its just that it is incovnenient, if you need to raise volume for a small bit of time; you already have carefully adjusted volume for the rest of the track and you want one small piece louder – current system makes it a bit inconvenient. And I don’t see how the fact that automated volume is relative implies that it cannot go into +dB values 😕

I’m gonna try to explain it with my clumsy english. Imagine that the range of relative volume fader is 0 to 200% instead actual 0 to 100%. That’s mean you can go from mute until double the volume of the absolut volume fader, right?

Imagine now that the value of absolut volumen is between 0 and 100, and is set in 30. With our new relative value fader you can tweak this value from zero to 60.

But what’s the drawback? In a future Podium will support MIDI CC (i hope), then if you assign that relative volume fader to a physical fader of your MIDI controller and you want to record complex real time gating is too easy that you overcome the 50% of the fader and you will have undesired peaks of volume that you’ll to manually verify.

Now let’s go back to Podium 2.15beta1, the relative volumen fader is between 0 and 100%. You have the absolute fader set in 30 and you want get a volume of 60 with relative fader. How do you do it? Easy, set the value of absolut volume fader at 60, and set the relative fader to 50%. 60 * 50% = 30… so it’s the same result that if you would have an 200% relative fader value.

In the same line, with a 200% relative volume fader, I could use the MIDI controller decreasing the absolute value to half and overcome the last problem, cann’t it? 200% * 15 = 30. Yes that’s true… but there is new drawbacks:
– Frits will have to program an independent new fader for automate volume (Since other parameter as cutoff don’t overcome 100% of its value)
– You will have tons of faders (those that you wanted to automate with midi controller) in a different scale that other, 2:1, so mixer would be confusing at mixing stage. Think in your own terms, how many times do you need raise the relative volume instead decrease it? I’m sure that one or two as max.

Maybe I’m wrong, but I think that it would be annoying for mixer & mixing stage workflow 😉

Some automation recording problems:

1. The fader of the parameter record its movement even if track is unarmed and master record is off. This is an old behaviour (bug?) that I don’t like at all.

2. While I record, if I tweak a VSTi parameter the movement is recorded in the curve sequence (that I created before start recording with a certain curve). However if I stop of move the knob and keep it in a certain value the curve sequence isn’t updated (bug? bad behaviour?)

Thanks

I’m testing it right now. Big effort Frits! rewritting an entire part of the code of a program is something that is rare in vst host [like Live with its (old?) 128 parameters limitation]. Thanks 😀

1. (see picture) It’s smudged, as if it’s trying show also the big event points.

2. (see picture) I like to draw my own automation curves with pencil tool. If I try to describe a new curve with a starting point very close to an existing point is imposible draw the curve, because instead draw it you select the point and move it in its allowed range . Please, could I avoid this behaviour? maybe a button for show/hide the points, or maybe that pencil tool don’t select points, or maybe that if while you’re dragging with pencil tool a point you go out of its range and start to drag in the range of another one then the pencil write new points as usual.

But, it’s hard to imagine becuase it’s quite different from the current workflow.

I’m a newbie with Podium yet, so I understand that some people could disagree with this “new” piano roll workflow and that’s the reason because it would be nice have it as an option. I sure that 90% of newbies like this new approach. However I think that the “new” piano roll workflow isn’t “new” only improved. Because with pencil tool nowadays you can:

– Draw notes: Simple LClick
– Horizontal Zoom: Ctrl+Alt+MouseWheel
– Vertical Zoom: Ctrl+Shift+MouseWheel
– Total Zoom: Ctrl+Alt+Shift+MouseWheel
– Move windows: Shift+Alt+LClick
– Select multiple notes 1: keeping Ctrl and clicking on each them
– Select multiple notes 2: keeping Shift and dragging with LClick
– Resize notes: dragging them…
– Delete notes: Double LClick on one of them

The only feature added would be with “Unselect and delete event” option would be:
– Delete notes: Also right click on them
– Unselect all event: Right click on empty space.

I really think that it would be a really fast workflow. No need of select tools. And this would be only for piano roll and drum roll, not for sequencer (although unselect sequences would be nice also)

Q: Can you do what you can with the scalpel with the pencil tool? (i.e. Split audio and midi events)

As far i know, no, you cannot do it. It would be useful another simple shorcut. Hovewer (i don’t know if this is a bug) it doesn’t cut the piano roll event, and would be nice (but not critical imo) another shorcut for do it with pencil tool, as RightShift+LClick