Conquistador's Forum Page

Very nice changes so far. 🙂

@Zynewave wrote:

The timeline changes in 2.07 were only UI changes. The change you suggest requires some work in the engine, so it’s a fair bit more than a “whisker” away :wink:. It will have to wait.

Ok…from my user perspective in terms of functionality it is very close but that clearly is a bigger job than it appears…judging y your comments… 🙂

Oh well, it was worth asking for…Cheers Frits. 🙂

Echo Audio have drivers for Vista x86 (32bit) and Vista x64 (64bit). I have been using the Echo Audio Fire 4 interface with Vista for over a year, very good indeed.

@Zynewave wrote:

[As I understand input quantization, it is quantization applied to MIDI input before it is recorded into a sequence. Aren’t you talking about automatic quantization applied to playback of already recorded sequences?

Hi Frits,

No I was referring to input quantisation. I still think global and track level options are the best way forward.

I mentioned the drum track example as I would for instance record a kick part on a separate track but would not want a 16 note quantise setting for that. The Kick track would be a whole or half note setting to do the trick there.

Hi hats might have a 8th or 16th note setting on a second track.

A simple Q button could be added to each track that one could switch off or on. That button might not even have to appear if a user does not want per track input quantise settings or if they have disabled per track input quantise globally.

As for Automatic playback quantisation per track that is actually also useful IMO. It is certainly more flexible than that global setting currently available.

I would certainly make use of both. I might simply be noodling around on the keyboard browsing sounds on a VSTi and play something I like on different tracks. I would not want to lose the per track quantise option at that point.

The performance is done but I would then have to switch back and forth between quantise settings on those tracks as currently a change on one track (quantise settings) is reflected immeadiately in other tracks.

Yes I could save a track template with input quantise settings all present and correct but…I dont always work with project templates and might start a new song or variation of it while still working in the same arrangement. If I create a new track those input quantise settings (as things stand now) would not be there.

I would also be interested in something like Swing and Strength settings for input quantise. Very much so please. 8) Being able to set those before hand would be great.

I like Dfusions idea for a button on the transport (I would add especially the large transport) maybe as he said with IQ on it or as I suggested for the tracks simply Q.

Ronins tri state idea is nice as well…

how about a tri-state button close to the snap button at the arrangement window? (with a combobox for the quantization values)
first click, green: only playback is globally quantized
second click, yellow: recorded and played notes are quantized
third click, red: only recorded notes are quantized

That idea might even be extended to the Q button I suggested for tracks for consistency. 🙂

Unhiding tracks is easy enough but I *really* like your idea for a new track that is auto created for bounced clips. Great.

@Zynewave wrote:

Pressing B without Shift or Ctrl will alternate between rendering and deactivating, just like a freeze button.

I like that idea. Keeps things very simple. Nice.

@Zynewave wrote:

I agree that the tiny font used on the readout sliders are of little use when it’s hard to read. I’ve tried using a slightly larger font, as seen on the screenshot below. To be consistent with the track header sliders I’ve also added the missing dB decimal to the gain faders in the mixer strips.

Is this good enough to be the new default Podium setup?

I think that does look nice. The text was just a bit too small before but your adjustments I think would now make a nice default setting.

Width of Vertical Meters:
I think Acousmod suggested thinner vertical meters…well to be honest I really don’t think there is much room for change there. 😐

Any thinnner than it is now and it might be very difficult to see the indicator lines (at -6dB, -12dB and -24dB) even now they are not that easy to make out. A thinner vertical meter might make them less than practical for any real use.

H- Mans idea for “assignable colour notches” for the indicator lines, a few posts above this one (which I agree with) somewhat highlights how difficult it can be to see them even now.

Of course an option could be added here anyway for the width of the vertical meters, but my inital thought is to keep the width of the vertical meters *as is* personally.

On another note…

Frits…you had a groovy idea…:P
I noticed that the colours used for the groove in the sliders in your screenshots do not really show case how clever this idea of yours really is…
@Zynewave wrote:

Another change is that the groove for the slider is filled with the parameter graduation colors (similar to the dial fills).

An example: Send 1 for the Guitar track in Screen shot 2 has a value of -22.00 now there should be some kind of change in the colour here.

Going all the way up to +1.12 on Send 2 for the Vocal track and again the same colour.

I used this setting…

…to get a very nice change in colour as I move the slider. Maybe a similar default setting would make this particular feature stand out much more. This setting also works very well with *any* kind of dial in Podium, Sends, zReverb, zPeq e.t.c please try it.

It provides a nice visual indicator for lower, mid or high values.