Topic: Preview 2.34: Minor consistency updates

@thcilnnahoj wrote:

I found some time to give reformatting (just hope I didn’t mess it up) the preferences chapter a try. Lots of stuff left that I couldn’t explain very well, or not at all. 🙁

Many thanks. The bullet point list is something I plan to use for all chapters that describes UI controls and menus. I see you placed “fixme” next to a few items that already have a description. Is that because you think the text is not clear enough?

If it’s okay, I’d like to have a go at the Loop-Recording and Composite Tracks section, which looks like it needs screenshots as well.

The page is all yours. The current text and screenshots were contributed by Mike G a long time ago, so that’s why the formatting may appear different.

@Zynewave wrote:

@thcilnnahoj wrote:

I found some time to give reformatting (just hope I didn’t mess it up) the preferences chapter a try. Lots of stuff left that I couldn’t explain very well, or not at all. 🙁

I see you placed “fixme” next to a few items that already have a description. Is that because you think the text is not clear enough?

❓

I’ve updated the guide with the new features coming in 2.35:

The “Browser Window” chapter is updated with MIDI file audition. Sorry about the Spanish translation LiquidProj3ct 😳 . You can see the changes I’ve made with the “Old revisions” button.

I also updated the Note Sequence chapter with info on MIDI file drop + new improved multiple selection Insert key behaviour. The Insert key behaviour described below is also implemented in the arrangement editor.

Note events can be added by dragging MIDI files directly onto the note editor timeline. This will merge the notes from the MIDI file into the current sequence, in contrast to dropping the MIDI file on a track, which will create a new sequence object. Dropping MIDI files onto the note editor timeline enables you to build a sequence using simple elements, such as chords, arpeggios, single drum patterns, and so on. You can create your library of MIDI file elements by using the **Export to MIDI File** command in the note editor **File** menu. When you move a MIDI file over the timeline, you’ll notice that the drop highlight is cut at the note under the mouse cursor. This indicates that all the notes in the MIDI file will be offset to this root note. For example, if you have a MIDI file containing a C major chord, dropping the file on a D note will create a D major chord. Holding the Alt key will override the root note offset. Holding Shift will override snap mode.

The Insert key can be used as a quick shortcut to append duplicates of selected events. The duplicates will be placed starting at the end of the last selected event. The original events will be deselected and the duplicated events will be selected, so that pressing the Insert key repeatedly will continue to append duplicates. A duplicate event will not be created if an existing event is already positioned at the place where the duplicate should be placed. If snap mode is enabled, pressing Insert will snap the duplicates relative to the next editor grid line. Press Shift+Insert to override snap. Press Ctrl+Insert to snap to the next bar, no matter what the editor snap settings are.

@thcilnnahoj wrote:

I see you removed the “bounce recording” section that was in the old page. Was that just too out of date, redundant, or do you have other plans for that text?

I don’t know where in the guide bouncing is described at the moment, and I couldn’t tell whether the old bounce recording section dealt with real-time or offline bouncing.
Since I think bouncing is a whole new matter by itself, I’d suggest to create an entirely new chapter for it. Of course it’s your call if you think real-time bounce recording is better fit for the recording chapter, and maybe offline bouncing should be described elsewhere.

After reading it again, I think the old bounce-recording section was written before offline bounce rendering was implemented 😮

A separate Bounce chapter sounds like a good idea. I’m currently writing on the “Editor Menus” chapter, which include the Track and Bounce submenus. Perhaps it would be better to move the description of the bounce submenu into the new chapter describing the bounce feature. What do you think?

@Zynewave wrote:

@Zynewave wrote:

@thcilnnahoj wrote:

I found some time to give reformatting (just hope I didn’t mess it up) the preferences chapter a try. Lots of stuff left that I couldn’t explain very well, or not at all. 🙁

I see you placed “fixme” next to a few items that already have a description. Is that because you think the text is not clear enough?

❓

I assumed you were going to look over the whole page anyway, but I put FIXME’s where I wanted to draw your attention. So yes, they’re also in places where I think some more information (which I couldn’t give) might be beneficial.
For example ‘Release drivers when Podium does not have focus’ – I don’t know what it actually does. Reading the description, I never had a problem with running another audio program at the same time, even without using this option…

Ok, I’ll try to fill in the blanks in the Preferences chapter.

A question about inspector panels: Popup help calls them just ‘Device panel’ and ‘Input panel’, but it’s ‘Device mapping panel’ in the guide – are you going to update the chapter names or should we link to them as they’re called now? In the recording chapter, I have a link to “guide:inspector#input_panel”, which doesn’t actually go anywhere at the moment.

The guide should be updated to use the panel names in the popup help. I’m going to continue working on the Editors chapter before I’ll take a look at the Tracks chapter. You can revise the Track chapters if you want.