CPBSounds great! When do we get our mitts on it? 😉
@Max wrote:
And I think that would be nice to have a LP/HP filter as a part of zReverb (HP to prevent muddy reverb tails).
Seconded: Whilst I appreciate the need to keep the parameters to an absolute minimum, I think variable LP/HP filters are an essential.
CPBCPBCPBThanks Max: I’m aware of the randomize timing and velocity options, and great they are too! However, I’d like to tidy up sequences that I’ve recorded live from my midi keyboard. Unfortunately, I’m terrible at keyboard playing. Without quantization, they sound like experimental, tempo-less free jazz excursions. With quantization, they sound like Kraftwerk. I’m sure there’s a happy medium somewhere between these extremes!
CPBso you should move some of those actions into setting menu (like audio/midi in outs) and get rid of project wizard (sorry)
Not sure I agree with that – I like having the configuration options seperate because it keeps the main menu free from clutter. It’s not (usually) the sort of thing that requires a lot of changes. We don’t want Podium to end up like the nonsensical menu hell that was Logic Audio 3/4.
Just remember; Ctrl+W is your friend if you need quick access to configuration level settings!
CPBI concur, another great update, really clarifys the heirachy. However, you seem to have introduced a minor bug with panning though: If you pan any track with audio mixing fully left so the readout displays ‘L1.00’, then try and pan back to centre, Podium crashes. This occurs on both existing and newly created projects, and is easily repeated.
Fairly sure this was introduced with the new version cos I’m darned sure I’d have noticed it if this bug was present earlier! If it’ll help, I can investigate if earlier versions displayed the same issue.
CPBAnd don’t forget the new, bold-outline icons as well. Another great release, thanks!
CPBI voted for ‘Plug-in Development’, just because I want to see ReWire support.
CPBMissed the 1.35 thread due to the lightening fast update, but I’ve a few comments about some new features :
* UI drawing – So much better, the whole product feels a whole lot more responsive now.
* Randomisation of midi sequences – This is great, it fits in so seamlessly and is an easy way to liven up programmed sequences. And having it in the track info panel makes it easily to tweaked in realtime. However, I find it drops notes quite often: I have a simple 1 bar sequence, tempo 120, playing straight 16 notes. With a timing rnd of 14ms, and velocity rnd of 23%, it drops a few notes each bar.
* Ghosts in keyboard editor – Again, this works really well. However, because the vertical grid lines are drawn ‘over’ the ghost notes, it’s impossible to tell if a ghost note is one 8th note, or 4 32nd notes. Not a big problem by any means, but I think it’d be a bit nicer if the ghost notes weren’t intersected by the grid.
* Installed guide – some links appear to be wrong in the installed version of the Podium guide. They point to files in “Z:/Sites/Zynewave/guide/”
Thanks, this is another great Podium update!
CPBDevice wrapper mappings? So, does this mean you’ll be able to effectively encapsulate entire branches on the tree and map them to a single node? If this is the case, that sounds excellent!
CPBIt just feels natural to me, that painting a new note with quantize snap on will snap it to the same position that you would get if you painted with quantize snap off, and then selected the quantize edit command.
This does seem logical, but I’ve checked Reason, Energy-XT and Tracktion 2. All of them truncate when painting with snap on but round when quantized. I guess it is inconsistent, but to me at least, it feels ‘right’. I imagine the inconsistency arises due to the fact that ‘snap’ is for those who prefers to compose with a mouse, and ‘quantize’ is for those who compose with a midi keyboard.
Also the cursor display in the top toolbar will show the note position that will be snapped to, with a -/+ percentage deviation.
Wow, never noticed that before, that’s very handy!
CPBWorks fine here. Ensure you have a Battery 2 mapped track selected, expand the Param header and select Device. There should be a VST Parameters node in the tree containing all the automatable VST parameters. The first one is already set to Inst Volume, the rest are free to map as you want.
Right click on a control in the Battery 2 GUI to list all the automation mappings. Choose an unmapped id and press Set to link the parameter to this control.
The parameter can now be automated using the matching VST in the Podium browser. ID 1, for example, corresponds to VST Parameter #001. These can be renamed in the properties dialog for each node, which is recommended if you’re using a lot of automation mappings.
CPBActually, I’d like the ability to optionally use the default GUI too – I often find the interface supplied with some VSTs to be a bit fiddly and slow and so would prefer to use the Podium GUI in these cases.