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:
I’ll update the Preferences chapter, print out the pdf guide, and probably release 2.35 tomorrow. Unless you find bugs, of course 🙂
@LiquidProj3ct wrote:
What could be the next “safe” chapter that I could translate?
I’ve translated until now: Getting started, Project, Project window, project start page, browser window, toolbars and sliding & zooming
The only remaining up-to-date chapters are:
http://www.zynewave.com/wiki/doku.php?id=guide:note_sequence
http://www.zynewave.com/wiki/doku.php?id=guide:recording
All the other chapters are scheduled for a thorough rewrite.
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).
@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?
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
Right, I wanted to mean than 🙂 The only ‘weak’ point of your system is that you cannot clone a group of notes with a empty space behind them, ie:
When what you really want is this:
So, as a solution I suggest using Alt+Insert to clone a loop, where only the selected notes are pasted.
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?
Yes, I think. Do the same thing you do in arrangement editor, if you press Insert and nothing is selected nothing is created 😉
@LiquidProj3ct wrote:
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
Right, I wanted to mean than 🙂 The only ‘weak’ point of your system is that you cannot clone a group of notes with a empty space behind them, ie:
When what you really want is this:
So, as a solution I suggest using Alt+Insert to clone a loop, where only the selected notes are pasted.
Yes you can, by setting the proper grid value. If the notes in your example are 1/8, then set the grid to 1/4. You may want to repeat the group with 5 1/8 spaces at the end, in which case you set the grid to 1/2. I can’t think of a better way to do this.
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?
Yes, I think. Do the same thing you do in arrangement editor, if you press Insert and nothing is selected nothing is created 😉
I wanted to have the possibility to add and edit notes using only key shortcuts. There is no other way you can add a new note to an empty sequence with a key shortcut.
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.
Yes you can, by setting the proper grid value. If the notes in your example are 1/8, then set the grid to 1/4. You may want to repeat the group with 5 1/8 spaces at the end, in which case you set the grid to 1/2. I can’t think of a better way to do this.
Then I think I prefer my own workaround, writting a note in a free key, clone them and deleting all the keys thanks to piano roll’s key selection method.
I wanted to have the possibility to add and edit notes using only key shortcuts. There is no other way you can add a new note to an empty sequence with a key shortcut.
I think the faster way to write notes like a tracker is khaos’s suggestion, it’s very, very, very useful.
@LiquidProj3ct wrote:
Yes you can, by setting the proper grid value. If the notes in your example are 1/8, then set the grid to 1/4. You may want to repeat the group with 5 1/8 spaces at the end, in which case you set the grid to 1/2. I can’t think of a better way to do this.
Then I think I prefer my own workaround, writting a note in a free key, clone them and deleting all the keys thanks to piano roll’s key selection method.
Why not just duplicate the events, and then adjust the position of the already selected duplicates by dragging or using the Ctrl+Left/Right key shortcuts? That seems a lot faster to me than inserting a dummy note at the last space, reselect the group of notes to be duplicated, duplicate, and then select and delete the dummy note again.
I hope you can see that Podium cannot inteligently know how many spaces you want at the end of your selection. In the example in your screenshots, you may actually want to duplicate the events as shown in the first screenshot. That’s why Podium uses the current grid value as offset for the duplication.
Frits, it doesn’t matter too much, it was just a minor suggestion, other Podium aspect (as grid drawing for me) are more critical that this tiny and small detail (and yes, I can see how it’s impossible for a software know how many spaces I want, unless I write it somewhere).
About my workaround, it works for me because I always work in the same scale (i can easily select notes I’m not using), and when I want to duplicate few notes I usually want to do it massively. I did a short gif
ahem, the ideal thing in this gif is that notes would snap automatically to the scale (up or down direction), that one of my fav fr 🙂
@Zynewave wrote:
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.
That’s nice, but I don’t think it’s the perfect cure yet… This works fine in other sequencers. Isn’t there some kind of pattern length or something specified in a MIDI file? :-k
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.
Wha– 😯
These are all awesome!
My only two complaints are that the real-time bounced waveform displays gaps (which are thankfully not present in the actual audio file) until you scroll or zoom, and there’s something weird going on with bouncing, pre- & post-fader stuff:
– Set a track’s level to -6 dB and render an offline bounce. Rendering ignores the level setting but not the pan setting (I don’t know why, but it’s always been like this, I think). So far, so good.
– Now delete the bounce track, then enable real-time bouncing, record a bit, and play it back – same as before.
– Delete the bounce track again, add an effect that doesn’t change anything on its own (like zPEQ), and offline bounce again – works fine.
– Get rid of the effect/bounce track, add the effect again, and do a real-time bounce. The recording level is half of what it should be. Switch to bounce playback, and it is again half as loud!
Unfortunately, I can’t do extensive testing right now… maybe I’ll have time later on, if Sherlock Nielsen doesn’t catch the villain first!
Also, the pivotal chapter of the guide (colors) is ready for review.
Hmm, if it works without “guide:” then I guess it will be fine. I always add it because it was like this in the first link I copied the syntax from, so it’s how I’ve learned to do it. 😆
@thcilnnahoj wrote:
@Zynewave wrote:
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.
That’s nice, but I don’t think it’s the perfect cure yet… This works fine in other sequencers. Isn’t there some kind of pattern length or something specified in a MIDI file? :-k
There is and “end of track” marker, but I don’t know how reliable that is. Do you have a couple of example MIDI beat files that you can email me? Some that has pauses at the end, and that will import with the pauses in other hosts. And of course, the MIDI files should not have been saved with Podium.
@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?