Zynewave's Forum Page

@thcilnnahoj wrote:

Also, the pivotal chapter of the guide (colors) is ready for review.

Many thanks. I’ve verified it, and made some small changes:

I see you kept the old “== Title ==” headers. These appear almost as normal text in the printed pdf guide (it’s two different layout scripts that are used for screen and print), which makes it hard to tell they are section headers. I bumped them up to “==== Title ====”, which I suggest is the smallest header format we should use. The largest “====== x ======” is for page titles, and “===== x =====” is for section titles that should go into the sidebar index.

I also replaced your // line termination with true paragraph spacing. I find it easier to read. Any reason you use the // forced line feed?

@thcilnnahoj wrote:

I guess this is intentional? It seems a little strange to me, though, if it’s like in the picture example.

Sort of intentional. Originally you could only transform a segment selection to a spline curve. When I extended it to also include event selections, the code would only search for the first and last selected event, and then transform that time range. I’ve now changed it so that Podium will divide it into smaller segments if there are “holes” in the selected events.

Thanks.

And, if you find it tedious to change grid setting to duplicate a group a certain distance, you can always use the Ctrl+Left/Right arrow shortcuts to adjust the position of the duplicated group of notes.

@LiquidProj3ct wrote:

Pressing the Insert key in the arrangement and note editor now supports duplicating a multiple event selection. If snap is enabled, the start of the duplicated events will be snapped up to the next grid line. Pressing Shift+Insert will override snap. Pressing Ctrl+Insert will snap to next bar.

I like it more that other similar functions I saw in other host, since it allows copy only certain part from bar to bar. Anyway, if you don’t have nothing selected and you press Insert (with/out modifiers) the notes are inserted in E key (without any reason, i guess).

I assume you mean “I like it more than other similar…”, in which case I take it you like the new behaviour. Otherwise let me know if something should be changed.

Podium can’t know which note you intend to insert if there are no selected events to duplicate, so the inserted new note is placed on the center note of the current zoom range. Is there any better way to do this?

Not my intention to release a beta, but since you’re wondering about the Insert key behaviour, I’ve uploaded a beta of 2.35. Changelog:

• MIDI files can be auditioned in the browser. The MIDI file will play on the focus track, at the tempo of the arrangement. If the arrangement is playing, the “audition on bar start” option will sync the MIDI file to the arrangement.
• MIDI files can be dragged directly onto the note editor timeline. This will insert the notes from the MIDI file at the mouse cursor timeline and root note position. All inserted notes will be transposed to use the new root note. Holding the Alt key will drop the notes without changing the root note.
• Added “Export Selection to MIDI File” command to the File menu in note and curve editors.
• When dropping a MIDI file or a sequence object onto a track, the end of the new sequence event will be snapped up to the next grid line.
• Pressing the Insert key in the arrangement and note editor now supports duplicating a multiple event selection. If snap is enabled, the start of the duplicated events will be snapped up to the next grid line. Pressing Shift+Insert will override snap. Pressing Ctrl+Insert will snap to next bar.
• Realtime bounce recording mode now automatically creates the sound events for the recording.
• Realtime bounce recording is no longer limited to the length of the arrangement, but will continue to record until stop is pressed.
• Made a minor design change to the browser window menu buttons.

I’ll update the Preferences chapter, print out the pdf guide, and probably release 2.35 tomorrow. Unless you find bugs, of course 🙂

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

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:

@Zynewave wrote:

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.

I see – I hope he won’t mind, then!

I took the liberty of giving the recording chapter an overhaul – phew!
As I’m still not entirely sure what’s supposed to go where, there may be some redundant information present.

Excellent 🙂 Nicely written.

I’ve added the following text about multiple take selection, which wasn’t included in the old chapter either:

If you have selected multiple composite events, and select a take on one of the selected composite events, any similar named takes in the other selected composite events will also be selected. If the **Use timestamp as name for new take events** option in **Preferences** is enabled, it is easy to simultaneously change takes on multiple composite tracks. If you for example have recorded multiple takes of a band rehearsal using multiple audio inputs, you can select all the composite events, and switch the takes for all tracks simultaneously. Since the takes are named with a timestamp of the recording start, the selected takes will always be from the same recording, even if you reorganize the take tracks.

I don’t know what to do with the paragraph surrounded by “fixme” tags…

I’ve parked it at the end of the chapter under a new “Recording MIDI parameters” section. I removed the FIXME. Even if the text do need fixing, I’m not keen on creating the installer pdf guide with FIXMEs included. 😳

I also wonder if recording plug-in & mixer parameters via the mixer faders should go here or someplace else (for now, I’ve put a reference to the parameter automation chapter up)?

That’s fine.

Plus, after this thread, I’m not certain anymore about some terms – for example, is it ‘device mapping’ now, or ‘device object’?
Some others (composite event, take selection bar), I couldn’t find an official name for, so I had to make them up! 😛

I use “device object” as a general term for any of the device mapping, device definition, preset and parameter object types.

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?