Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymaster@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.
ZynewaveKeymaster@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.
ZynewaveKeymasterI 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?
ZynewaveKeymaster@John-E34 wrote:
Would it be possible to add an option in “preferences” to assign the default mixer configuration, or even a check box to “enable” Gain, Pan, and VU meters by default?
Can you describe the scenario where you would need that?
If a track is a MIDI track, then it would not be useful to have gain/pan/meter on the track, as these would do nothing. It’s only when you assign a sound generating source on the track, or add sound files to the track lane, that you would have a need for the mixer controls.
ZynewaveKeymasterCan you give me some more descriptions:
Is it a gain fader?
Does it happen both on the track headers as well as in the mixer?
Is it only on the UI, or is the sound slow to react as well?
Does it happen also when playback is stopped (i.e. during low cpu usage)?
ZynewaveKeymaster@LiquidProj3ct wrote:
If you want I could develop a complete shortcut map allowing this functionality, but something say me in the ear that you prefer develop it yourself 😛
You are welcome to come up with your suggestions, which the community here then can discuss. Better do that in a new topic. I ask though that you please consider consistency across the entire UI. It’s not enough to make up the perfect key/mouse behaviour for the piano-roll, if it means that the key shortcuts will conflict with behaviour in other parts of the UI. I don’t want to remember a different set of shortcuts for each editor.
ZynewaveKeymasterHi,
If you are working with MIDI files, remember to check out this MIDI file tutorial for hints:
http://www.youtube.com/watch?v=hV1Eg7zToZw
From your description, I assume that you are manually assigning instrument plugins to the MIDI tracks after you have imported the MIDI file. I just tried this, and I found that assigning the instrument doesn’t automatically enable the gain/pan on the track, as it really should. I’ll add that to the 2.30 release.
ZynewaveKeymasterHere’s a possibly weird suggestion: How about making double-tap of the Ctrl key swap between dragging phantom or unique?
So, Ctrl+click will start a phantom copy drag. While holding down the mouse button, double-tap the Ctrl key (and keep Ctrl pressed on second tap) to change the mouse cursor from the phantom copy cursor to the unique ‘+’ cursor. It’s a bit like a secret handshake, but at least it will be known to users that read the key shortcut page in the guide.
ZynewaveKeymaster@Slomo wrote:
@Zynewave wrote:
I assume you mean holding Ctrl+Alt while dropping. Could be a solution. But then we have the same possibility for confusion, as we had with the old Alt key phantom drag behaviour, which is that you need to press Ctrl+Alt AFTER you have clicked. Otherwise you would start a zoom drag.
Yes, that’s what I ment. A unique solution/behaviour to get a Unique copy, easy to remember.
Hmm, it just doesn’t add up. If Ctrl+Alt should drag unique copies, then it won’t be possible to drag a phantom copy to another track, locked to the same timeline position. Other suggestions?
ZynewaveKeymaster@Slomo wrote:
@Zynewave wrote:
The arrangement editor is special in that there has been two copy modes (unique and phantom). If both should have their own key (Ctrl and Alt), then to follow the consistency rules, the Alt key would not be usable as drag key shortcut in the other editors.
I found this to be a unique feature in Podium. My concern is that you make a phantom copy, forget to turn it into a unique copy, do some serious editing and all of a sudden end upp with an odd number of all phantom copies.
Can Unique copy be assigned to Ctrl+Alt instead of Ctrl+U?
Not much of a snapper 😉
I assume you mean holding Ctrl+Alt while dropping. Could be a solution. But then we have the same possibility for confusion, as we had with the old Alt key phantom drag behaviour, which is that you need to press Ctrl+Alt AFTER you have clicked. Otherwise you would start a zoom drag.
Anyone else have suggestions?
ZynewaveKeymaster@LiquidProj3ct wrote:
Frits, mouse snap mode doesn’t work when you set it in “Start of grid unit under cursor”
About that option: I never liked the fact that I had to place this option in preferences. Now that we have a menu for snap options, would it not make more sense to move the option to that menu?
Instead of the current “snap to grid” option, there would be “snap to closest grid line”, and “snap to preceding grid line”. This would allow you to have the “snap to preceding…” option enabled in the piano roll and drum map, while using the “snap to closest…” option in the arrangement and curve editors.
ZynewaveKeymaster@Ortac wrote:
@Zynewave wrote:
• Dragging phantom copies in the arrangement editor is now done with the Ctrl key instead of the Alt key. The phantom copy can subsequently be converted to a unique copy with the edit menu or the Ctrl+U shortcut.
What’s the point in this? It makes things more difficult as far as I can see.
@Slomo wrote:
I agree with Ortac. I have an established workflow using Ctrl and Alt all the time. It’s easier to learn new behaviour than to change old 😉
The reason for these changes can be gathered from various posts in this topic, but to summarize:
Changes to the key shortcuts was necessary to make room for a new key shortcut for temporarily overriding snapping while dragging events. This is a shortcut that is available in most other host programs, and I’ve come to appreciate it during the development of 2.30.
There are now three drag modes that are shared among all arrangement, piano roll, drum map and curve editors: Copy, override snap and lock x/y position. For consistency, I insist that the key shortcuts used to activate these drag modes are the same across all editors. It would be stupid to have for example snap override on the Alt key in the piano-roll, and on the Shift key in the arrangement editor.
The arrangement editor is special in that there has been two copy modes (unique and phantom). If both should have their own key (Ctrl and Alt), then to follow the consistency rules, the Alt key would not be usable as drag key shortcut in the other editors.
So far in 2.30, Shift is snap override, Ctrl is copy, and Alt is lock x/y. It can actually make sense to hold all three keys down if you are dragging an event you want to copy further away on the same track without snapping.
If you think this new key shortcut behaviour is bad, then please tell me what you would prefer instead.
ZynewaveKeymasterHi,
Are you trying to bounce record in realtime, or bounce render offline?
Do you have any Jamstix MIDI tracks in addition to the four stereo outs?
You can get Podium to record the MIDI output of a plugin by enabling the “Enable recording of VST plugin MIDI output” option in preferences. This option is off by default, because some plugins will send MIDI input thru to the output, causing duplicate notes when recording over an existing sequence.
ZynewaveKeymasterRather than creating a new preview topic, I’ll just add the post to this topic. 2.30 beta1 is available in the VIP lounge:
• Added “snap to grid”, “snap relative to grid” and “snap to edit cursor” options to the editor snap menu. All options can be enabled at the same time, making snapped position dependant on which snap point is closest.
• Modified the way that the Shift, Ctrl and Alt keys affect mouse drag actions. Pressing the Shift key after starting a timeline drag action will temporarily disable snapping. Pressing the Alt key after starting an event drag action will lock the dragged selection in either the horizontal or vertical position.
• Dragging phantom copies in the arrangement editor is now done with the Ctrl key instead of the Alt key. The phantom copy can subsequently be converted to a unique copy with the edit menu or the Ctrl+U shortcut.
• Pressing the Ctrl key when drawing a curve, or when dragging a single point event in the curve editor, will snap the point to the default parameter value. This was previously done with the Alt key.
• Renamed the Quantize menu to “Grid & Snap” menu. Shortcut key is Alt+G (previously Alt+Q).
• Changed the shortcut key for toggling snap mode to A (previously T).
• 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.
• Added Ctrl+E as shortcut for the “link edit cursor to play cursor” option.
• Added Ctrl+R as shortcut for resetting current event/segment selection.
• Added Ctrl+U as shortcut for converting a sequence/sound event to a unique copy.
• When a track event is selected, the Left Arrow key navigation will stop at the first event on the track, instead of selecting the track.
• Middle-click on the timeline will set the edit cursor snapped. Holding Shift while clicking will set the edit cursor without snapping.
• Added an extra decimal digit to plugin parameter value readouts in the curve editor and the mixer parameter faders.
• Fix: Unassigning an instrument from a track which had MIDI parameter tracks would cause a crash.
Let me know if you find any conflicts in the changes to the Shift, Ctrl and Alt key behaviour. I hope to release 2.30 this weekend.
May 13, 2010 at 19:48 in reply to: Why do electronic musicians keep using Logic and FL Studio? #18127ZynewaveKeymaster@tumult wrote:
Would it be possible to associate events to markers, so that when I click a marker, it automatically selects some events in the timeline?
You can do that already with the bundle events command. Select all events you want linked (you can include the marker event if you like), and then “Bundle events” (Ctrl+N). Dragging any of the events in the bundle will then drag all the bundled events, and you can use the copy drag to create phantom copies. The dropped copy will become a new bundle. Use Ctrl+N again to unbundle events.
The bundling feature also allows you to create separate bundles for handling synths and drums, as in your example. Each event can only be included in a single bundle though, so the marker event cannot be included in more than one bundle.
To further explain the idea with marker linking:
Say you have 4 copies of a 4-bar section, each with a marker event at the start. You can link the 4 marker events to sync the 4-bar patterns. You could however instead link only the first and third marker, and by doing so sync two 8-bar sections. In other words, the length of the synced sections are not determined by the distance between markers, but the minimum distance between linked markers.