Zynewave.
kagemushaHi
I have tracks wrapped into a group track with audio enabled. Infact it’s one audio track with an audio recording and it streams thrue an eq, reverb, comp to the grouptrack to which I have assigned a volume parameter.
When I move that volume slider in the mixer -of the group track- audio drops as long as I hold my mousebutton or moving the slider.
Thats a bit awkwart, because I can not hear the volume changing while dragging( and draw the volume parameter), only when I release the slider sound comes back.
If I add an other track in the group with a volume mapping and stream everything thrue that it works.
But I think it’s a bit overkill to add yet another track just for master volume of that group while it would be logical that the (audio enabled) grouptrack that holds the sounds and fxses can have the master volume for that group.
Another poundering.
When I want to set the volume of a track group or for any track to a certain percentage it is written in the parameter file as curves/peaks for that moment. but it would be useful if you could also set a global volume >> if you move the volume that it makes that percentage for the whole timeline.
I know I can use gain but its very “a-panoramic” to use different parameters for the same feature or result. Perhaps with some modifier key that you can decide if you want the volume change as a curve or as a global constant percentage. (a horizontal curve)
eg >> then you can set a global volume which you think is ok at that moment with the modifier key ; and without modifier key you can add changes. No need to mix it up with gain changes
I remember using the parameter events a “long” time ago (instead of curve) but I can not find them anymore 😥
ZynewaveWhen I move that volume slider in the mixer -of the group track- audio drops as long as I hold my mousebutton or moving the slider.
This happens because the parameter track is muted when dragging the slider, to avoid that recorded automation overrides the fader movements. The sideeffect is that any audio routing through the parameter track also gets muted. I’ll have to implement another way to bypass recorded automation when dragging the slider. Thanks for pointing this out.
When I want to set the volume of a track group or for any track to a certain percentage it is written in the parameter file as curves/peaks for that moment. but it would be useful if you could also set a global volume >> if you move the volume that it makes that percentage for the whole timeline.
I am not entirely sure I understand what you mean. Could you describe it differently?
I remember using the parameter events a “long” time ago (instead of curve) but I can not find them anymore
You drag parameter objects onto tracks to create parameter events. It may be that the level and pan mixer parameters are not active currently. I will check up on this when I start work on the curve editor improvements.
kagemusha@Zynewave wrote:
When I want to set the volume of a track group or for any track to a certain percentage it is written in the parameter file as curves/peaks for that moment. but it would be useful if you could also set a global volume >> if you move the volume that it makes that percentage for the whole timeline.
I am not entirely sure I understand what you mean. Could you describe it differently?
I found what the “problem” was:
Wat I meant was that if you move the the volume slider in for example the beginning of the region/part that not the whole volume for the remainder was increased >> eg I was getting a peak but the rest of the volume was staying low. But the reason I foundt was that , although the curve was a flat horizontal on a certain percentage, there were some break point in the curve. Of cource if I moved the volume up it went up till the next breakpoint >> a peak
I think this is a side efect of the “no read/write” method (which is pretty good). when I move the volume to check something out, the curve reacts, but when I put back the volume where it was, >> a breakpoint is created. I’m not always aware of that.
I still think you need to implement a way that you can move a volume (or any parameter) without it has effect on the curve (modifier key)
Because in the current state everything is written, and even if you don’t have curve changes they getting breack points every time you do something and roll back.
About the parameter events.
I remember that when I recorded I was getting all kind of little regions in my tracks with a dial on it for every change in the parameter. I know I could choose if I wanted a curve or a parameter event while recording.
I don’ t see the way anymore how to do this?
SardaukarHey kage,
Sorry dude, I find your posts rather confusing! 😉 . Perhaps a step-by-step explaination would be best. Then perhaps board members maybe able to help you out better.
ZynewaveI don’t find kagemusha’s posts confusing, but they occasionally deal with pretty complex stuff :). Kagemusha is a long-time beta tester so he has tried some of the more hardcore stuff in Podium.
I still think you need to implement a way that you can move a volume (or any parameter) without it has effect on the curve (modifier key)
Agreed. It’s on the list.
If you want to avoid ‘leaving’ a curve breakpoint when you drag a slider, use the right mouse button (while still holding left button down) to abort the drag action. This will reset the slider to the position before you started dragging, and undo the curve change.
I just verified that I can record both curve and parameter events with my AN1x. There doesn’t appear to be anything broken that once worked. However the parameter events so far only work with MIDI parameters. The floating point parameters such as mixer level and pan and VST parameters does not currently include a dial. I’ll get around to implement that at some point.
kagemusha@Zynewave wrote:
If you want to avoid ‘leaving’ a curve breakpoint when you drag a slider, use the right mouse button (while still holding left button down) to abort the drag action. This will reset the slider to the position before you started dragging, and undo the curve change.
Yes, … but I can’t hear (pre-listen) the result of the sliderposition. 😥
Eli
I just verified that I can record both curve and parameter events with my AN1x. There doesn’t appear to be anything broken that once worked. However the parameter events so far only work with MIDI parameters. The floating point parameters such as mixer level and pan and VST parameters does not currently include a dial. I’ll get around to implement that at some point.
Indeed. I realise now it was with midi parameters and not with audio. Would be helpfull in some circumstances to use these with audio as well.
Eli
ZynewaveYes, … but I can’t hear (pre-listen) the result of the sliderposition.
I have a pending bug on my notepad concerning this. Will look into it soon.