H-man's Forum Page

@thcilnnahoj wrote:

Uhh, self-ban maybe… 🙂
I haven’t used my account there for over a year, and can’t remember my password. Different e-mail address, too… 🙄
I could probably get a second account or ask a moderator for help, but I don’t think I’ll bother, as I never particularly liked the place anyway.

hahahahah ….to quote that guy in the editing room from the movie Boogie Nights “It is what it is!”.

The new skin is fantastic, great (and a lot of) work.

It’s interesting that Shannon went with such a basic skin for what amounts to a very cool little instrument/sampler. The library of available skins is now probably larger than for any other VST/VSTi.

This is definitely a new favorite tho.

Ben

@Malcolm Jacobson wrote:

I would like to see support for composite MIDI tracks added at some stage.

+1

The composite track feature for recording audio is really strong now. It would be great to have these tools for recording MIDI as well. Those 280 bar keyboard jams are fun but editing-down is a bit of nightmare 😉

@Zynewave wrote:

@H-man wrote:

At the risk of sounding like a broken record, would this be a good time to add the option of different colours (ie. lighter colours for darker themems) for the markers on the level meters?

Are you talking about the dark 0, -3, -6, -12 dB indicator lines within the meter? If so, would the solution be to use the configured text color instead of black to highlight the lines?

Yep, they’re the ones.

That would work well 🙂 as the panel and text colours would always be in contrast to each other, thanks.

Happy New Year Frits.

Nice work on the enhancements to the colour options. It’s fun and looks good (or terrible depending on the colours one chooses :P)

At the risk of sounding like a broken record, would this be a good time to add the option of different colours (ie. lighter colours for darker themems) for the markers on the level meters?

@thcilnnahoj wrote:

Question: Since the selected embedded parameters remain the same across different arrangements, I assume they stored within the project (or the device definitions) then. If so, would it be possible (without too much trouble on your end) to export such a parameter list setup to reuse in other projects?

I’m assuming that you’re talking about existing projects that use the same plugins.

As far as I can see from limited testing, the state of the embedded editors is saved as part of a track/effect chain templeate 8).

@H-man wrote:

Also, setting a minimum strip width in the mixer seems to disable the Collapse button (in the mixer only).

Okay scratch that. I had the “Expand all groups” option ticked on the mixer drop down menu…

Frits,

I have noticed that while multiple automation tracks can be viewed in the mixer, the rack (inspector) only shows the active one.

Is this on purpose? :-k

Also, setting a minimum strip width in the mixer seems to disable the Collapse button (in the mixer only).

@LiquidProj3ct wrote:

Question, what does mean 5.0, 5.1 and 7.1 tags? I see them in zPEQ and zPitch

Surround sound? 😉

Edit: Try this for an overview:

http://en.wikipedia.org/wiki/Surround_sound