Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterYou can limit the bounced time range using the punch in/out range. Set the punch range around the section you want to bounce, and use the “render within punch range” command in the Bounce submenu.
ZynewaveKeymaster@thcilnnahoj wrote:
@Zynewave wrote:
You forgot to suggest alternatives 😉
Should I remove the key shortcut for power completely, or use another shortcut?
Well, I do use the shortcut intentionally too, so why not Ctrl or Alt instead. I don’t know how likely it is that you’d start playback while copying events.
I think that only moves the problem from snap override, to copy or x/y lock dragging. What about changing it to the big one: Ctrl+Shift+Alt+Space?
About all the other consistency suggestions: My main focus at the moment is the guide, so I only update the inconsistencies as I encounter them in the chapters I’m rewriting.
July 13, 2010 at 14:48 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.July 13, 2010 at 14:35 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@thcilnnahoj wrote:
Um, this isn’t an inconsistency, but I’ve come to think that Shift+Space isn’t really a great key combination anymore… Since shift is used as modifier to ignore snap, I often shift-click in the timeline to position the edit cursor, and then press space afterwards to play.
Now I have the problem that I inadvertently turn off power sometimes – which is a pain if I have lots of plug-ins to reload. 🙁You forgot to suggest alternatives 😉
Should I remove the key shortcut for power completely, or use another shortcut?
July 13, 2010 at 12:52 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymaster@omar misa wrote:
Alt+E brings up the Edit menu?!
It does, when the focus is on the editor. When any of the dialogs are open, a lot of the dialog controls have Alt key shortcuts that override the normal shortcuts.
July 12, 2010 at 23:20 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterSends must be placed in the same order on all tracks. This is a restriction to ensure plugin delay compensation will work correctly.
ZynewaveKeymaster@Trancit wrote:
do you know already something new about this mousewhell behaviour???
I got a reply from the Poise developer. He said he looked at the mouse-wheel behaviour a while back, but could not find an explanation to why it behaved differently in some hosts. He’s using a development framework that handles the mouse-wheel, so he is not directly coding the mouse-wheel support. I’ve looked at it from Podiums side, and I can’t see why it doesn’t respond to mouse-wheel messages.
ZynewaveKeymasterHi Batman,
@Batman wrote:
1st – Does podium support program change? If so where is it?
The method thcilnnahoj described is the way to get the prg. chg. parameter for a plugin.
2nd – Is there something like input transformer in Cuabse i could use to transform keyswich to program change?
Without knowing how the Cubase input transformer works, I think I will answer no to that question. There is no method for converting incoming MIDI messages into another type of MIDI message.
ZynewaveKeymaster@Conquistador wrote:
I am a bit baffled by your response to be honest. 🙂 Surely it is more important for your users preference to be taken onboard for easier use of the application (in this case the terms /words used on those buttons) than for a personal preference you have for the names, just to avoid you having to type out an extra word in your forum posts for each button?!?!?!? :-s
Well, I’m baffled that you’re baffled. I reread my post, and I’m surprised it can be misunderstood. What’s wrong with having a short concise name that can be used as reference to the menu, while the text in the menu button includes additional details? If the button text is “Devices – I/O, Busses, Plugins”, the menu can be abbreviated as “Devices menu”. I don’t intend to write “I/O, Busses, Plugins menu” in the guide, so my suggestion does not result in longer names.
I have a problem with “Plugins and Mappings”, because if you consider the purpose of the “device mapping” object, then plugins are also mappings.
IMO I still see no real problem here.
I tried to explain why it technically is not an accurate description. You may not see that as a problem, but I do.
ZynewaveKeymasterSeems like “Arrangements & Media” and “Plugins and Mappings” are the favorite. I was looking for shorter names, and I end up with longer names :-k
The reason I wanted shorter names, is to avoid having to write “the arrangements & sounds menu in the project start page” every time I refer to this menu in the guide, or on the forum.
I have a problem with “Plugins and Mappings”, because if you consider the purpose of the “device mapping” object, then plugins are also mappings.
What about this solution:
The “Arrangements & Sounds” menu is renamed to “Contents – Arrangements, Sounds”. The “Devices” menu is renamed to “Devices – I/O, Busses, Plugins”. I included “Busses” because I assume busses are not generally classified as I/O? In this case I use “Plugins” as a general term for both ReWire devices and VST plugins.
That way I can refer to the menus as “Contents menu” and “Devices menu”, yet the button labels still show the more detailed description. Objections? 😉
ZynewaveKeymaster@thcilnnahoj wrote:
Brings me to a question: what do you use the “new sound” menu entry for, anyways? It doesn’t seem possible to record or do anything else besides drawing waveforms in the stand-alone sound editor.
You can record in the sound editor. But the “new sound” menu will only be useful in rare cases.
ZynewaveKeymasterThanks for the suggestions.
So far I’ve renamed the old “Arrangements & Sounds” and “Devices” menu buttons to: “Media Objects” and “Device Objects”.
Anyone think this is a poor choice of words?
I’m out of office for the weekend, so I’ll be able to reply again monday evening.