Sorry, no suggestion at the moment, just a quick bug report: If you minimize Podium while plug-in editor windows are open, their selector buttons reset to ‘not open’ state when you restore Podium.
Hmm, I don’t know… How would you play along to a song without recording any audio or MIDI data? That always got me in Reaper, where you have to record arm tracks to monitor them, and there’s an extra mode that arms a track so you can monitor it, but recording is disabled on it – quite confusing. Also, what should bypassing the input do in this case?
Oh, and beta 3 looks lovely! 8)
Very nice! It’s an interesting way of working, thank you for sharing. 8)
I couldn’t help but notice as you were adjusting the amp envelope in Poise at around 8 minutes in… you actually have to enable the envelope first (with the circle button above the envelope knobs)!
Yes, there’s indeed a problem with dropouts in bounce renders when using plug-ins that need latency compensation (which is automatic, and can’t be adjusted manually currently). It’ll hopefully get fixed soon… In the meantime you can get around it by using realtime bounce recording.
Here are two threads in which it’s analyzed a little:
http://www.zynewave.com/forum/viewtopic.php?p=16942#16942
http://www.zynewave.com/forum/viewtopic.php?t=2404
@Zynewave wrote:
The width of the meters in the mixer will resize according to the zoom setting.
Nice, but personally, I wouldn’t say no to even wider meters. 😉 It’s also a shame that the currently biggest meter size is only available when the strips are zoomed to 300%, because they would fit inside strips at a smaller zoom level already, and thus you could save some space.
I’m not sure if it’s really needed that they get smaller though, at least in stereo projects. It might be useful for surround projects.
Hi and welcome!
Even though the answer to all but one of your questions unfortunately is “no” at this moment, these are all things that are on the plan!
As for the mixer – it’s as Liquid described. Just ask if you need any help with the editor profile stuff. 😉
Side note to Frits: would it be hard to add a ‘New Mixer Window’ command, like for the browser and inspector? That would make it infinitely easier to split the mixer off to another screen, and also get rid of the (unnecessary?) menu and tab bars in the second window. Also, if you go the old editor profile route to get a mixer on another screen, the profile is also present on the editor profile bar, serving not much use there, in my opinion.
@LiquidProj3ct wrote:
Personally I don’t see it very useful since this seems to be obsolete, almost all plugins developer are creating its own preset selector inside the plugin.
I think this is a shame sometimes. I would much prefer browsing presets in Podium than using a different preset browser system for each plug-in (FabFilter and u-hu plug-ins are the only ones I use that do this).
Yep, I’ve had it happen too now. As ronin described, the input meter (armed track) acts normally, but only short clicky sounds come out, which the output meter (unarmed track) also shows.
It doesn’t help to uncheck the inputs in the setup, but the problem goes away after you switch to another audio interface and back again, and let it rebuild the input/output mappings.
Loading my normal setup file last saved with 2.36 brings the problem back again. The same setup that is broken in 2.37 works fine in 2.36…
I can’t confirm it, unfortunately. Recording with or without monitoring works fine so far… 😕
Something unrelated: When you change the output device mapping speaker configuration to none while the arrangement is powered on, this causes a crash.
Nice! Finally an easy way to tell mono from actual multi-channel inputs.
@Zynewave wrote:
I’d like to keep the track concept simple, so my plan is to support mono/stereo, phase invert, L/R dual panning, M/S, and phase correlation/goniometer display through a new zStereo plugin. This plugin will embed into the mixer strips the same way the current zPEQ editor embeds in the strips.
The best thing about making this a plug-in is that it’s easy to move it around in the signal chain.
A downside might be that, for example, it’d make the normal pan controls on tracks useless, and would probably take quite some space with all that functionality. Also, you’ll have to keep embedded editors visible, which you might not always want, as other editors besides the EQ and zStereo are possibly not needed as much during mixing.
Have you thought about making track controls a lot more customizable? I mostly mean showing/hiding buttons individually. A simple example… you could have a track template called “audio track”, which had SMR buttons, gain and stereo pan controls, just an input selector, and additionally a phase invert button on the mixer strip.
Or a “MIDI track” template with SMR buttons, MIDI level and pan controls, input, source, and preset selectors on the track header.
I guess this would be the exact opposite of “keeping the track concept simple”, however. 😆
Well, here’s hoping for a zSurround someday. 😉
The parameter automation chapter got revamped! I’m sure I’ve missed things, but it should be ready for review anyway. I’ve changed my screenshot naming scheme to include the version number instead of the date.
Things I noticed:
– Using the pencil tool, if you try to create a curve point in a series of line or bar points, you get a line point instead. You only get a curve if you create at least two or more curve points in one go (creates line points too, but they are converted to a curve on releasing the mouse button).
So, it is impossible to create single curve points with the pencil tool unless you create it inbetween other curve points. I almost never use the pencil tool, but this can be quite confusing, I think.
– It would be useful to be able to right-click sequences in the track panel list, to edit their properties, copy, or delete them.
– It would be useful to be able to Ctrl-click parameter faders in the mixer in order to reset their value.
See you again soon in beta land, I hope. 😉
Can’t disagree with that, unfortunately. Glad you still like it, though. 😉
Try enabling the Fader & Meter Grid in the mixer (using the menu button in the top left of the mixer) – this gives you an overview of fader and meter position on every track, and you can very quickly set them using the grid. Of course you could also use the Fader and Meter submenus of the track right-click menu for this.
Note that the grid won’t be available if mixer strips are zoomed below 100% (only applies to version 2.36 and up).
Another mini bug: When you change text color or load a color setup while the browser is closed, the icon on the refresh button will not update to the new color.
I was about to start updating those chapters again, but there seems to be no need! You would indeed do well not letting the guide fall that far behind anymore. 🙂
I’m taking the parameter automation chapter home over the weekend, to get back into it… After that, sequence events, probably. Just let me know if I’m crossing over into your guide territory again, Frits.
A super-tiny thing, not even worth being called a bug: When an effect track is selected in the rack, and you’re creating or deleting track notes, the sticky note button isn’t updated until you select another track. It’s immediately updated when the source track is selected in the chain.
Thank you very much for another great update!
Wow, it’s already out… let me bump these anyway, for future reference. 😉
– It’s good that you restored the dimmed so/in labels. However, they disappear awfully early during zooming. I think that even at the smallest strip size, at least labels like “So” and “In” would make them more discernable and an easier target.
– By the way, something that’s always irked me is that automatic solo is disabled when you enable normal solo mode on top of it… the two should be unrelated, in my opinion. Muting should of course mute the track, but restore automatic solo again afterwards. Anyone disagree?
– I think the control type and gain/pan fader options are quite confusing, and some of them possibly obsolete. Examples: Selecting “disable” for the faders doesn’t really disable them, but shows them inside the chain panel instead. For gain/pan controls, “show value on knob” can’t be properly used anymore with smaller strips.
– If you choose “control type: dial”, the pan dials are a little too big for the smallest possible strips.
– Due to the rounded corners, track headers look a little weird when using horizontal meters or no meters at all.
– I think that the mixer zoom setting should be saved with each arrangement instead of the editor profile. I’d actually say the same goes for the minimize audio/MIDI/parameter tracks options.
Zoom settings for all editors except arrangement are also stored per profile – it makes more sense there, but not so much with the mixer, in my opinion.– A first quick test shows that the GUI still ‘freezes’ for about half a second when I click (and hold) a window title bar but don’t move the window. Also, when I click and move a floating window (that did not already have key focus), there is always a little ‘jump’ when I start the move. It’s always been like this, unlike in other hosts, and isn’t a problem… it might be related, though. This also causes the rest of the GUI to hickup.
– With the round corners gone on selector buttons, it has become even harder to see the line when you’re dragging effects with some color schemes. It seems the color of the line changes automatically depending on the panel background color…
Comparison (my theme, Nightfall, Paper):
Maybe it could be drawn on top of selectors?
– (Not related to 2.36) Likewise, the color of the event resize overlay box thing (you know what I mean) is also chosen depending on some background color, making it very hard to see sometimes. The move and time-stretch overlays are always black, it seems, which works much better for me.
– Bug: (not related to 2.36) With the select tool, left-clicking shortly after selecting a menu option that closes the right-click menu results in an event being added. Looks like Podium sees it as the second click of a double-click for some reason. This happens sometimes because I often just click somewhere to deselect events.