swindus@ronin wrote:
@Zynewave wrote:
I think this must be a misunderstanding. There is only one fader on the track. Moving the fader position moves the fader (i.e. gain and pan settings) from one track to another track in the chain. There aren’t separate settings for gain and pan on each effect track. Please explain why you would want it to behave differently.
when you use the expanded mode you can see and set pan and fader for every track side by side in the mixer. now we have the beautiful switch in the fader panel which could let you choose which fader is shown “on top” of the track panel. with this behaviour it would be possible to keep the hierarchic workflow and to set the level independantly for every point in the signal path by switching the fader position. this would leave some more possibilities to the user and personally i think thats the more obvious behaviour…but well…thats just my opinion ^^
That’s my opinion too and it makes more sense for me, because then it’s possible to change gain and pan between any plugin instances in a chain. Sometimes it’s important to change the gain of a plugin output and not every plugin has a volume/output gain setting.
Another thing: the current approach, when I understand it correctly, limits the user to one pre OR post fader in the chain. The other method would allow a pre AND post fader for every plugin in the chain.
But as said just my opinion.
swindus@ronin wrote:
I guess swindus is talking about the fader handler. say we have an empty track and we add one effect. the small box-switch appears and we can switch between pre/post. the fader handler should now update its position accordingly to the signal path position. example: set pre fader to -10db and post to 0db. if you switch between pre/post the fader(/pan?) doesn’t update.
Yes, this is what i mean. Just unhide all tracks of a chain in the mixer and move a fader. All faders of all tracks in a chain are linked.
And a combobox for the font size selection would be nice. Thanks!
swindusThanks for providing a beta!
All seems to work as expected but there is one thing that I don’t understand or its a bug. Clicking the little boxes (the left one) for the fader in the new miniature chain view on a mixer strip does not change the fader position when selecting another track in the chain.
Is it possible to change the font in of the peak hold value to a smaller one?
I really like the new RMS display and the K Metering, great addition.
swindusThanks for the nice update! 😀
swindusswindusYou need to create a device mapping for the midi input. Just copy another midi input device and change the midi interface in the device settings dialog.
Podium does not create a mapping for a new midi device automatically.
swindusLooks good!
swindusGreat! Looking forward to it! 😀
swindusSoweit ich da informiert bin, ist es nicht möglich mehrere ASIO Geräte gleichzeitig zu nutzen. Außer der Treiber unterstützt es, wie zB der von M-Audio für mehrere im Rechner installierte M-Audio Karten. Der Treiber gaukelt der Audio Software also vor es wäre nur eine Karte installiert.
swindusNice release, thanks!
Just curious, what are the next new features/improvements on your list Frits?
swindusProject file sent.
swindusFound another bug:
– Insert a wav file on a track.
– Open the wav file in the sound editor and copy a segment from the wav file to the clipboard.
– Create a new track.
– Create a new event on the track and open it in the sound editor.
– Place the edit cursor outside the range of the new event!
– Paste the clipboard content to the event (Ctrl+V or menu command).
– Crash.
Happens only when the edit cursor is not in the range of the event where the audio content is pasted in.
swindusThanks! Looks good now, no crash so far.
swindus@Zynewave wrote:
I intend to make the track heights pixel fixed, as Mike described.
This would be great!
swindusI did a quick test and beta 4 is still crashing when I delete the last track in the project I sent you if the inspector is hidden.