@Zynewave wrote:
if I should delay the release of 2.23 so that it includes the changes to the mixer?
Although 2.23 is already a huge and very promising update I would say “Yes” too because the mixer changes would make the whole UI consistent. Excited! 🙂
@michi_mak wrote:
Hi Ronin, thanx for answering – well done for explaining the preroll issue ( but hold it Sir, me = bassplayer 😆 ).
Damn! Sorry 🙂 But I guess you understood what I was trying to say.
@michi_mak wrote:
so, there is no keyboard shortcut for “quantize note start” right now?
cheers, michi
I’m not 100% sure on this. I know you can’t configure shortcuts right now but maybe someone else knows if there is a shortcut for “quantize note start”. If not, maybe Frits can implement this in 2.23. Ask him. It seems to be a tiny wish.
Hi Michi,
no you can customize keyboard shortcuts right now. Its planned but not done (I think).
Preroll is a good thing but I just don’t get why people have to record at bar 1? Who cares on which bar you are in a DAW? There are plenty of them 🙂 Just move your arrangement a little bit. It doesn’t hurt. Yes, compared to other DAWs its unusual but I think this concept is just a differnt one. It is not simply counting you in, it is automaticly playing back a few bars (like automatic preroll or like a band when the bass player fu**ed it up the 20st time to start at the right part of the song 🙂 ) .
@LiquidProj3ct wrote:
About CPU usage. Podium, at least with one track, only use one core in my PC. Take a look to this screenshot, where I use Nithonat, Toraverb and Redoptor with maximun quality settings:
(click on picture until you see it at real size)
edit: I’m on Xp home, 32bits
Hmm that depends on on which level multithreading is implemented. I guess you could process plugins in separate threads or you could process whole tracks in separate threads. The second example would probably explain your observation liquid. Separate plugins are difficult I guess because the input of the second plugin depends on the output of the first one so you can’t process the second if the first hasn’t finished. This results in sequential processing but Frits knows better for sure 🙂
@Frits: The “new” multiprocessing works nice here. I’m noticing less spikes and seem to have a better overall performance.
@Conquistador wrote:
1. Signal flow
The Heirachic mixing engine flows upwards right? So it surely makes sense to maintain the consistency of it in terms of workflow. You add one effect then another on top. Simple standard practise. Everything flows up. With the current choice every new effect slot is added before the first. Huh? Makes no sense.
Yes! It would be very nice to change this behaviour. FXs should be added at the end of the signal path.
@LiquidProj3ct wrote:
You could change mute button and do it a knob and then you should remove the send faders. This knob would be a Volume knob for instrument, a Dry/Wet knob for insert effects, and a Send Gain for send effects. If the knob is zero then the effect is bypassed. If you right click in the knob you alternate it between its original value and zero.
In theory thats a really good idea liquid but the problem is that you can’t really bypass the plugin in this case. I’ll try to explain wait I think would be the problem:
You have to distinguish between muting the plugin (turn the dial to zero -> no signal passes through) and unloading (bypassing) it. Usually you want’ the dial to work seamless but unloading the plug will result in a short pause or something. For the solution with the dial you can just lower the wet-path to 0 but the plugin is still processed.
Usually I could live with that but sometimes I just want to free some resources for a short time….maybe Frits can shed some more light on this
Markus, you gave noone a chance to give you an appropiate answer to this post. If I agree, I would have to lie. If I’ll try to explain your issuses
you probably just get your fan-boy-attitude verified. Thats not a starting point for a useful discussion.
Try to stay openminded. Almost everyone in this forum is open for a good and useful feature discussion but please understand that some things just take some time…
@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.
I like the idea of the “live-rack” too. Maybe this could be a separate panel in the inspector? With a select-box to choose which live-rack (one for each plugin and a global one where all track-vst-parameters can be mapped to the eight dials) is shown.
@Group Panel: To put it short: What do all these buttons do? I think some of them can be removed or integrated. I’ll try to give an example.
First there was an empty track 🙂 Gain and pan are set to the only valid position. To distinguish track gain/pan from the effect/send region stuff the panel should use some graphical elements like
****gain & pan****
A D/W knob is a useful thing. The FX-chooser should be a combobox to select the different plugins (it looks already nice in the current screenshots). To show the state of the plugin it could use different colors (red – bypassed, green – editor open, yellow – solo, grey – default). The FX-chooser should have an item “no plugin”. Right-clicking the chooser opens a context menu which shows things like “Add Parameter -> VST ParameterList” and “Bounce” etc.
Drag & drop inserting/reordering should be available too (or these tasks have to be added to the context menu). Left clicking the “fx-name part” of the chooser opens the plugin editor. Left clicking the small triangle on the right (+ a few pixels 🙂 ) opens the menu where the device mappings/plugins can be selected. Maybe this should be two separate buttons which are “glued together” like it is possible with the new transport controls.
And maybe thats all it needs.
I’m not sure about how the initial layout should look like. Somehow you have to add synth, fx and midi/audio input. Three initial/empty slots would probably clutter the layout…
Some package has arrived. Its probably yours (and UncleAge) but its still at the depot. I’ll try to get it tomorrow morning. greetings
Sorry Liquid. I looked at three stores but none of them sold the magazine. I’ll check some other stores tomorrow and if I can’t find it I’ll order it directly.
@LiquidProj3ct wrote:
Uhm, if you don’t want it I’d really grateful and I’d donate to Zynewave the money. That plugin is very useful for me, for do detroit techno music. So, if you don’t need it… 😀
Yes, please do that.
@kyran wrote:
I ordered it on their site. International shipping is 2 euro extra. So it’s about 7.9 to get it shipped anywhere in the world (instead of the german 5.8 euro price)
@Liquid: If you want to order it, just tell me. Else I’ll try to buy a copy later this day….btw. I don’t want that money (donate it or buy me a drink when I’m in spain 🙂 )
Thank you Frits! Profile switching is really fun now. Works fast and flawlessly here.
Something I thought about:
I’ve integrated the switch-buttons into the transport-toolbar to preserve more space for the arrangement-editor. Since you can switch with the number key now, I think there is no real need for a large profile-bar(because you don’t have to click the buttons)…maybe this integration should be standard but on the other hand this integration may not very useful for small resolutions. I’m working with 1680×1050 and have enough space left in the transport-bar.