Topic: Preview 2.36: Extended UI and mixer resizing.

😀

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. 😉

This hierarchic organization not only defines the visual track layout, but also controls the flow of audio, MIDI, and parameter automation signals. The signal flow arrows at the left edge of track headers and at the top of mixer strips provide a visual confirmation of how tracks are routed.

The basic rule to remember about the track hierarchy is that all audio, MIDI, and parameter automation signals flow upwards from the bottom tracks of the hierarchy until finally reaching the master track at the top. The only exception to this rule are send tracks, which create a branch-off to a bus track from the exact point in the signal chain where the send mapping is placed.

is it me? or these two paragraph seem very redundant with first chapter paragraphs?

http://www.zynewave.com/wiki/doku.php?id=guide:tracks#track_hierarchy

I think they must be fixed

Yeah, seems I recycled a little too much of the existing text. Also, the first sentence is just weird. 😳

Here’s a quick attempt at restructuring (with the two paragraphs removed):

@Revision attempt wrote:

The track hierarchy concept applied in Podium essentially describes that the signal flow is determined by the visual track layout, making it easily apparent at all times.

Audio, MIDI, and parameter automation signals originating on tracks flow **upwards** into parent group tracks, and, depending on the signal type, thus become affected by device mappings on the group track, as well as the group track’s gain and pan settings. Group tracks can be nested, meaning groups can be placed inside another group, and due to this, group tracks can also be child tracks of another parent group track. This allows for flexible solutions to routing and grouping, with the signal flow arrows displayed at the left edge of track headers and at the top of mixer strips additionally providing visual confirmation of how tracks are routed.

**Tip**: When an instrument is assigned to a group track, all note sequences placed on its child tracks will trigger the instrument – this can be especially useful for drum samplers.

When working on an arrangement, you might want to split it up into sections such as drums, vocals, and synths for pop songs, or violins, violas, cellos, basses for classical music. You may also create sub-sections in each section. This allows mixing on different levels: sections, sub-sections or individual tracks within a section. When mixing sections, it can be useful to collapse the section group tracks, so that the individual tracks within the section are not taking up space on the screen.

**Tip**: You can set up **track tags** to filter or organize the tracklist further, and hide tracks you are not currently working on. See the arrangement chapter for more information on track tags.

@Original wrote:

The track hierarchy concept used in Podium may seem unusual the first time you look at an arrangement.

Signals flow **upwards** from **child tracks** into parent **group tracks**, and, depending on the signal type, thus become affected by the group track’s gain and pan settings, as well as effects on the group track. Group tracks can be nested, meaning groups can be placed inside another group, and due to this, group tracks can also be child tracks of another parent group track. This allows for flexible solutions to routing and grouping, with the signal flow still being easily apparent.

**Tip**: When an instrument is assigned to a group track, all note sequences placed on its child tracks will trigger the instrument – this can be especially useful for drum samplers.

This hierarchic organization not only defines the visual track layout, but also controls the flow of audio, MIDI, and parameter automation signals. The signal flow arrows at the left edge of track headers and at the top of mixer strips provide a visual confirmation of how tracks are routed.

The basic rule to remember about the track hierarchy is that all audio, MIDI, and parameter automation signals flow upwards from the bottom tracks of the hierarchy until finally reaching the master track at the top. The only exception to this rule are send tracks, which create a branch-off to a bus track from the exact point in the signal chain where the send mapping is placed.

When working on an arrangement, you might want to split it up into sections such as drums, vocals, and synths for pop songs, or violins, violas, cellos, basses for classical music. You may also create sub-sections in each section. This allows mixing on different levels: sections, sub-sections or individual tracks within a section. When mixing sections, it can be useful to collapse the section group tracks, so that the individual tracks within the section are not taking up space on the screen.

**Tip**: You can set up **track tags** to filter or organize the tracklist further, and hide tracks you are not currently working on. See the arrangement chapter for more information on track tags.

Whoops… it’s been nearly two weeks now, sorry!

I read it again and actually think there’s no need for the sentence.
It’s hard to describe the hierarchy in simple words without starting to explain about group tracks and stuff, which this section already does anyway. 😉

So I’ve updated the tracks chapter without it. Of course you can add a new opening sentence if you like, but as I say, it’s not really needed, and your time is surely better spent on other things!