Zynewave@LiquidProj3ct wrote:
Small suggestion, not as critical as the reset suggestion but it could be good, I think it’s a good idea allow that marquee work with Ctrl+LMB with pencil tool. Nowadays if you keep down control and LMB in a empty area you write an event, the same that if you simply press LMB. So the suggestion is that Ctrl+LMB start a marquee that doesn’t reset the existing selection with pencil tool.
Done. Applies to the tracks, piano roll, drum map and format regions.
ZynewaveBeta4 is up. This will probably be the last beta, and if no serious bugs are reported, I’ll release 2.30 within a couple of days.
Additions to beta4:
Shift+clicking to start a marquee selection will reset existing selection first. Ctrl+clicking an empty area will start a marquee selection adding to the existing selection.
Assigning an audio-enabled device mapping to a non-audio track will automatically enable the fader and meter on the track.
Fix: A child track that is tagged can now be collapsed if the group track is also included in the tag selection.
Please test that the fix for the tagged child tracks behaves as you expect.
Zynewave@thcilnnahoj wrote:
The problem is that the events are cut off at the end of the last note: GIF animation (this one consists of 32th notes, and is cut off one 32th early). It is created correctly in other hosts. The same seems to be happening when dragging events from the inspector’s track panel…
I take it that the bit that is cut off contains silence. So it doesn’t actually corrupt the playback, but it is an annoyance when you want to repeat the pattern snapped to bars?
Zynewave@thcilnnahoj wrote:
Something I came up with:
Ctrl – Create phantom copy
Alt – Lock x/y position
Shift – Override snap
Ctrl+Alt – Create unique copy
Ctrl+Shift – Create phantom copy and override snap
Alt+Shift – Create phantom copy and lock x/y position
Ctrl+Alt+Shift – Create unique copy and override snapIt’s not great either, especially Alt+Shift is weird, and there’s no shortcut to create a unique copy while locking the x/y position.
I don’t know of any programs that add the right mouse button as a modifier, and think I’d find it uncomfortable…
Thanks for the effort. You’re right that Alt+Shift is weird, because suddenly the Ctrl is not used for dragging copies.
The way I approached it was to make the three modifier keys have a specific function, and not deviate from that. After you have memorized these three modifiers, you could easily figure out what combinations of the keys would do. The downside is that there are some key combinations that may be less useful.
Zynewave@thcilnnahoj wrote:
Middle-click on the timeline will set the edit cursor snapped. Holding Shift while clicking will set the edit cursor without snapping.
I really like(d) this one. 🙁
Moving the cursor with snapping enabled can already be simply done by clicking on the timeline. I think not everyone uses, or even has a middle button available, so I preferred it doing something special.
Hmm, I actually was annoyed by the old behaviour. I use middle-click to quickly position the edit cursor on the grid when I’m editing events. Though this change may be a minus to you, I hope you overall find more plusses in this release.
Modified the behaviour of the Q/W key shortcuts: Q/W moves the edit cursor in steps of the grid value. Shift+Q/W steps the edit cursor between marker events and active loop, punch and segment ranges. Ctrl+Q/W will set the edit cursor to the start or end of the current event selection.
Hmm, this is fine, but you also seem to have swapped the actions of the numpad home/pgup and left/right arrow keys…?
They were swapped automatically by the change I made to the commands, but I’ve now swapped them back to their previous numpad keys. I’ve also added numpad 1/3 as shortcuts for setting the edit cursor at the start/end of the current selection. I don’t use the numpad myself. Would you perhaps prefer a different setup? Maybe the shortcuts you use the most should be on 1/3.
Edit: The help text for the note editor’s velocity buttons, and the curve editor’s draw mode buttons should be returned back to point to Ctrl instead of Alt.
Fixed. Thanks.
Zynewave@LiquidProj3ct wrote:
When you import zReeverb the Mono version is confused as a Mono In version with one input and two outputs
The “Mono In” indicates that it is stereo out instead of mono in/out. I’ve never heard of a reverb plugin that had mono output ❓
ZynewaveBeta3 is up. This fixes two bugs:
@LiquidProj3ct wrote:
I don’t understand the point of “snap to previous grid line”, but “snap to closest grid line” works for me, it seems more consistent bacause when you drag a note horizontally it doesn’t “dance” (behavior that seems buggy).
Even though the jumping back and forth was highly confusing, I found it was actually correct behaviour when I debugged it. It happened because snap relative was still snap to “closest” relative position, so you would get a jump backwards when dragging across the grid line because that suddenly made the “snap to previous grid line” closer than the relative position. I’ve fixed this confusing behaviour by making the relative mode snap to “previous” relative position when the “snap to previous grid line” mode is enabled.
Maybe you’re aware of this: If snap is on, and you click in the border of a note, then press shitf and you move the note you can do the note as tiny as you want. But if you start to resize the note without keeping down shift key and while resizing you press it you cannot do smaller than snap value.
I was aware of it, and it is now fixed. Thanks.
Zynewave@confusador wrote:
ok, that all makes sense. is there a thread somewhere about how to show the hidden track and draw the event to enable realtime bounce?
1/ Enable the “realtime record bouncing” mode on the group track.
2/ Right-click the empty “effect” button on the track header or the inspector, and select “options > hide track lane”. That should reveal the hidden bounce track with the “B” button on the track header.
3/ Draw the sound event on this track.
4/ Hide the bounce track lane again, to tidy up.
5/ Select “Arm bounce recording” from the bounce menu.
6/ Enable record mode in the transport toolbar.
7/ Start playback.
Step 2 to 4 will not be needed once I implement the automatic creation of the sound event.
is it possible once you’ve drawn the events for the realtime bounce recordings to save the whole setup as a track or track group template?
It should be. If you enable the copy events option when saving the group track as a template.
i’m not sure about rendering offline with jamstix. i haven’t been able to get it to work as far as i can tell, but i’m clearly missing something here, so it may well be possible. thanks for the detailed response regarding the presentation of the multi-out instance of jamstix. i think this is related to the global/insert plugin architecture detailed in the manual yes?
Yes.
ZynewaveBeta2 is up. Some bugs are fixed, but there are still a few left that I’ll look at tomorrow.
The “snap to previous grid line” option is added to the snap menu.
When an event drag operation has started, each press of the Ctrl key will toggle between phantom and unique copy. I think it works ok. Let me know what you think.
Zynewave@LiquidProj3ct wrote:
RMB modifier: (only after dragging started) Lock X/Y movement
Not possible. Right-mouse click (while holding down left mouse button) is used to abort (undo) any kind of drag action in the entire Podium UI. It’s probably the one shortcut I use the most.
I reserved for that task ESC key. Now that you have an hypotetic right system to select events, a simple right click to delete them and the old friend undo, I thought it wouldn’t be a critical shortcut because you wouldn’t do mistakes, except the rare case you select another events. If you think isn’t enough and you do tons of mistakes choosing the event/sample drag (hint: get a new mouse!! 😛 ) I can think in another alternatives.
I can not emphasize enough how important the right-click drag cancel shortcut is to me. I use it constantly, and often when I don’t have my hand on the keyboard, so the ESC key is not an option for me. Often I do a temporary drag operation with the intent of aborting it (to return to the UI state before the drag started), such as: Zooming out on the timeline to get a overview. Zooming in to check the details of crossfades or rapid short note sequences. Dragging faders to hear how a track affects the mix. Dragging up the editor panel, mixer, velocity region, and practically any other resizable panel, in order to temporarily get a more detailed look at events, meters, EQ curves, and the list goes on and on. I also use right-click to quickly abort unintentional drag operations such as when you hit the wrong event or drag handle etc. It’s a lot quicker to right-click than to use the undo command.
… Letters, as single stroke modifiers, can do the job of Cancel since is the only single stroke modifier. And other weird modifiers as MMBaD (Middle Mouse Button after drag), Casp Lock aD [this key is weird due to its toggle nature but can be use as a modifier] or AltGr aD (too far to be usable).
So I can think in these alternatives using another key:
1. Esc Key, as I suggested in the original map
2. Z/A/X key doing the job of cancel
So, you are holding Ctrl down, and then press A or Z or X to cancel? 😉 (hint: select all, undo, cut).
It’s also not good to rely too much on middle mouse button. I think most of the mouse models on the market have middle click on the wheel, and it’s easy to accidentally move the wheel when clicking. And then there are laptop users, where the trackpad does not have a middle button.
Zynewave@confusador wrote:
hi zynewave. thanks for the quick response. if i understand the difference correctly, i would like to bounce record in realtime. i have the option to enable recording of vst plugin midi output checked, but i can’t figure out how to select jamstix midi output as the record source for the top group track “drums” – it should also be monitoring all it’s child tracks of course – but it’s doing that currently. the parent group track is the only jamstix MIDI track in the sense that it’s the only track where i want to print the midi output of jamstix (at least until it eventually gets replaced by the final drum submix). i can always freeze a midi arrangement in js though, so what is more important to me right now is figuring out how to get the child tracks to record the audio they’re receiving from js four stereo outs.
Unfortunately setting up realtime-bounce recording is a bit cumbersome at the moment. You need to manually draw in the sound event for the recording, on a track that is hidden by default. I have an item on my todo list concerning this, and I really should deal with this soon 😳 . Is it not possible to render offline with JamStix?
also, i have a question about the way it presents the multi-out incarnation of jamstix as a separate instance on each child track. this is a little disconcerting as i’m used to the parent or folder track containing the vsti, and the child tracks just getting receives from it, whereas in podium it seems the vsti is not represented at all on the top group track where all it’s output is routed in the mixer, but is instead shown on each individual child track receiving it’s inputs. i think i can adjust to this presentation, but i would like to confirm that this is simply the graphical presentation of a single multi-out instance of jamstix? there are not actually four instances of js running simultaneously right?
You have multiple mappings, but they all relate to the same instance of the plugin, indicated by the “#1” in the mapping name. This gives you the flexibility to set up tracks only with the outputs and MIDI channels that you actually need to use. If you want to use additional plugin instances, you use the “new instance” right-click command in the device list, which will give you an identical set of mappings with “#2”, “#3” etc. in the name.
The signal flow in the Podium engine follows the visual arrangement of tracks: Everything (audio, midi, parameter automation) flows from the bottom track branches, towards the topmost master root track. The output of child tracks inside a group track is mixed together and routed up through the group track. When you want to bounce a multioutput plugin, with the intent to save the CPU usage of the plugin, then you should enable the bounce mode on the group track. That will bounce the mixed output of all the multi-outs. When the group track is bounced, it will mute all child tracks, and this is what reduces the CPU usage. All tracks that have mappings for the plugin instance need to be within the bounced group to reduce the CPU. If you just bounce an individual output track inside the group, you will not reduce the CPU usage by much, as the plugin MIDI tracks are still playing.
I’ve made a note to myself, that I need to create a YouTube video showing how to set up and bounce multi-out/multitimbral plugins. It is simple enough to use once you get the hang of it, but it can be difficult to break through for newcomers that are accustomed to other DAWs.
ZynewaveThanks for the suggestions. I assume you’d like some feedback so that you can modify the list to fit the needs of most users.
SUPR: delete selected events
Is “SUPR” the Spanish name for the delete key?
RMB modifier: (only after dragging started) Lock X/Y movement
Not possible. Right-mouse click (while holding down left mouse button) is used to abort (undo) any kind of drag action in the entire Podium UI. It’s probably the one shortcut I use the most.
Zynewave@John-E34 wrote:
@Zynewave wrote:
If you are working with multitimbral instruments, then you have separate MIDI channel mappings, which do not produce audio. Having faders on these tracks would be confusing.
I often work with multitimbral instruments, and always need to adjust levels…
Surely you don’t adjust the audio gain on MIDI only tracks? You would do that on the tracks that have the plugin audio output mapping assigned.
But, it seems stupid to have a mixer, that by default, has no faders (as you put it), even Reaper defaults to a standard mixer layout.
If I have to manually enable the VU, Volume, Pan etc, etc – for every track, every time I import a midi file, then I give up…
The fader/meter will be there by default if you create new tracks. You encountered the problem that converting an imported MIDI only track to an audio track will not automatically enable the fader. As I said earlier, I’ll change that for the next release.
Zynewave@John-E34 wrote:
If it’s a midi track, I would assign a vsti anyway, otherwise, it would do nothing…
If you are working with multitimbral instruments, then you have separate MIDI channel mappings, which do not produce audio. Having faders on these tracks would be confusing.
ZynewaveI just tested, and it seems there is a higher than usual CPU usage when the inspector is open. I’ll look into optimizing this.
What kind of CPU do you have? A single-core?
