Zynewave@ronin wrote:
There is another thing on my mind:
Personally I think the selected input should only be activated when the track is armed (no monitoring and no input metering while unarmed). The tooltip on the record button already implies this behavior.
Hmm, :-k . Doing that would mean you could not set up an audio input to act just as a live feed (perhaps from a talk-back mic in a booth). Once you start recording on other tracks, you would unintentionally record the live feed track.
Anyone have an opinion on this?
ZynewavePodium can send MTC (MIDI Time Code), so if you have an interface that can convert MTC to SMPTE, you should be able to slave an external SMPTE recorder to the Podium transport.
ZynewaveBeta3 is up. I managed to reproduce the silent recording bug with another soundcard interface I had. I’m 99% sure the bug is fixed now.
@thcilnnahoj wrote:
@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.
The meters resized with the same percentage as the strip widths. This was to ensure that even a 32-channel input meter would not grow larger than the zoomed strip width. I’ve changed it so that mono/stereo meters increase at a larger rate, and 3-8 channel meters increase at a slightly larger rate.
ZynewaveBeta2 is up. I’ve fixed a bug that I’m pretty sure is the cause for the silent recording problem. Let me know if you still have problems.
New additions in beta2:
The background of input meters are tinted with the record color.
The width of the meters in the mixer will resize according to the zoom setting.
ZynewaveZynewaveI’m taking this off my todo list, as the latest 2.36 release features a new dedicated bounce menu button.
ZynewaveZynewave@thcilnnahoj wrote:
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. 😆
That sounds complicated, so no, I haven’t thought about that. 8-[
ZynewaveZynewaveI assume the problems you mention about tempo changes, are when you adjust the BPM value of a tempo event during playback. This currently causes the play cursor in Podium to jump. I’ll improve this in the future, so that the tempo can be adjusted in realtime without problems. However, tempo changes made with tempo events on the timeline should not cause problems. If you have problems with that, let me know.
ZynewaveTested it, and it appears that Podium calculates the MIDI notes received from the plugin to be a little earlier than on the beat. That causes the first notes to be dropped, because the notes are interpreted as having been played before the recording starts. I don’t know if it is Podium that calculates the note position incorrectly. I’ll verify that at some other time.
For now, you can record the repeated loop, and then crop the sequence to the start of the second cycle.
Zynewave@elysianforest wrote:
zStereo sounds okay I suppose. I guess what might be nicer for me is if this zStereo plugin, or a lite version of it, automatically instantiated with the track, and then you could choose to bypass or remove it. It’s the extra steps for these things I use all the time (as do many other professionals I’ve seen at work) that I’m not loving.
There are various ways that allow you to easily preconfigure a track with your desired settings/effects. I don’t know if you have stumbled over the track template feature yet, but this allows you to save various channel strip configurations that you can use to create new tracks with, or to replace the effect chain on existing tracks. Another way is to use Ctrl+C to copy a track, and then Ctrl+Shift+V to replace the effect chain onto other tracks, including plugin presets etc.
Zynewave@elysianforest wrote:
Hi there! I just dicovered Podium and have been messing around with the free version a bit and you’ve really got a nice thing here. I’m really enjoying it as a compositional tool for VST instruments. It’s easy to figure out and use immediately – which is rare and a delight …
BUT, in addition to being a composer, I am a professional audio engineer, and not having phase inversion, mono summing, and Pre/Post controls in the mixer at my fingertips is a real hindrance – and an immediate dealbreaker to be honest. I don’t want to have to instantiate a separate vst (or an individual bus for Post fader FX) to accomplish these things which you’d find on most any serious mixing console from the last 35+ years.
I’m keeping my eye on Podium though. The engine sounds nice and it really seems like you’re getting close. And again I really, really enjoy much of the rest of the workflow. Cheers!
-Forest
Hi,
Thanks for the feedback. The things you mention in your post are on my future plan. So please do stick around, as I would value your input when discussing new features in the preview topics.
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.
About the pre/post. Are you talking about faders or meters? As thcilnnahoj mentioned, if you enable the grid control in the mixer menu, you can toggle meter pre/post by single-clicking the grid control on each strip. With key shortcuts you can click the squares on the grid control to set fader or meter at a specific effect in the chain.
Frits
ZynewaveHi,
Thanks for the feedback.
2/It seems to be using an awful lot of CPU at idle
(It’s idling with the same CPU hit as when it’s running)
The plugins are active also when playback is stopped. So if you have loaded plugins that use CPU even when the input is silent (reverb plugins etc.), then that explains the CPU use. To unload the plugins, switch off the power button in the transport toolbar.
Frits