@Zynewave wrote:
The mixer will get a major revision later on. The updates to the track management in the latest Podium releases have left the mixer lacking in some areas. I want to complete the track management features before I start on the mixer redesign
Nice, thanks.
I don’t think that is necessary when we have the new “add effect” selector in the chain. You can use that to easily add any number of effects. No need to have a predefined number of empty slots.
Well that was just example. They way how it works now, its okay. Logic have similar style. Nothing wrong there.
You have done exelent job there. I hope you keep continue in this way.
How about coding just simple compressor / duck / gate fx? It doesnt have to be good. Just that good so we can use it for sidechain.
How long it will take to code something like this? Simple duck fx? Thanks for your time.
@ronin wrote:
@Markus wrote:
Does anyone else agree?!?!?
No. You won’t know where the sends are in the signal flow + you are switching the direction of the signal flow in your example. Podium uses almost everywhere “upwards” direction. In your proposal the signal flows downwards in the FX chain (where source and input are located too) and upwards in the track hierarchy…thats fairly confusing, sorry.
well, we talk about this on vip lounge. Frits wants more customers and so on. Its not going to happen when podium learning level is so high. i’m just indicate things which make podium more easy to use.
Okay. This it how it should looks like.
Seriously. Source FIRST. Then fx list. Last we need sends. Those sends should be “balloon”. Just like those X, R, E buttons. It take less space, and its looks 10 times better. It’s not only me who want’s those “Balloons”.
EDIT
I made it more clearly now.
That “M baloon” is simple MIDI IN. Now whole view is CLEAR and EASY / FAST to discern. Does anyone else agree?!?!?
Super cool! thanks man. Keeps going! i’m happy that you change that E button much closer on playlist! 8)
@Zynewave wrote:
Besides the redesign of the group panel, the following is also implemented in beta1:
• Improved stability of plugin multiprocessing.
This involved a change to the way that the plugin processing is distributed to the available cores, so I would appreciate if you could try the beta1 and let me know if you notice any change for the worse in plugin CPU usage. Especially if you’re on XP. My XP machine is not running a multi-core CPU.
Here everything is okay. Win 7 32bit, intel quad 9550.
Hey Frits
Looking good! Right way again! :D/
Now we have little mixer here. How about that orginal? Please remove those fx in there. Main purpose was get rid of that “scrolling up and down effect”.
I also think that you should add there empty slots. Like 8 pieces. Example here
How about put VSTi first, then fx slots. That is more logical, isn’t it?
And yes. Big meter!!
Edit; That E aka Editor view button should be under that “track menu button”. Please? it is more closer that playlist. Easier and faster to navigate.
Thanks for answering. Maybe you should also make some graphical GUI changes. Make it more “future look”. Like S1. We live in 2009 now 🙂
Damn.. Why i didn’t learn to coding when i was young? :/ I would like to help you developing podium 🙄
@druid wrote:
Right click on the mixer “track” (Battery 3) and then go to “Meter” and see which it is selected. If it is metering only “Battery 3”, then any FX after this will not show. If you select in that the last FX in the chain, then the meter will use them all.
Let us know if that fixes your issue.
Also, don’t forget you can set the fader this way too, allowing you to choose how far in the chain you want the fader to affect volume!
Ye thanks. That fix it. Strange, i haven’t touch it at all. Default settings..
Maybe just do like
“save as” project command. Like in all other host’s. Then change the plug in scan to automaticly every time podium start. 🙄
So Frits, makes this topic anything sense?
@darcyb62 wrote:
My one wish would be to have this ported to Mac. I have been using Logic since I went to the Mac and although I quite Logic, I yearn for the day when Podium will run on the Mac. Until then, Logic it is.
Nice wish! However we talking about easy / fast things. Porting in Mac would be take alot time.. I think..?
@Zynewave wrote:
@kyran wrote:
1. The spacebar should always control the transport, regardless of the current focus
Some plugin editors uses the spacebar key for its own purposes, and thus steals the spacebar keypress so that it never reaches the host. Also, all listboxes in the Podium UI is using the same standard key/mouse shortcuts as used by Windows, so in that case the spacebar is used to toggle elements in a listbox selection. Using the numeric 0 and return key to stop/start is more likely to work no matter where the key focus is.
I would love to have this too. This is really annoying thing. So 1+ for force space bar thing.
@thcilnnahoj wrote:
Got another one: When adding a new track by drag-n-dropping an instrument from the inspector, it’d be good if the track was selected automatically, so auto-assigned MIDI input goes straight to the new instrument! (Saw that in a Studio One video just now :oops:)
I like this too, but it doesnt gonna happen cause i want it :clown: