Topic: Preview 2.34: Minor consistency updates

Viewing 15 posts - 16 through 30 (of 122 total)
1 2 3 … 7 8 9
  • July 12, 2010 at 21:15 #18810
    Zynewave
    Keymaster

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

    July 13, 2010 at 06:09 #18818
    Levendis
    Participant

    @Zynewave wrote:

    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?

    “Contents” and “Devices” on buttons and in the manual are appropriate abbreviations.

    Personally I liked andyy815‘s suggestion of “project elements”. Adapted, this would leave you with “Elements” and “Devices”, a less prosaic alternative.

    July 13, 2010 at 09:08 #18821
    Conquistador
    Participant

    No worries Frits it’s just too small an issue to spend too much time on, (over analysing a misunderstood post or two)…so please carry on. In a nut shell some nice suggestions have been made and hopefully simple and descriptive suggestions will be used. As far as this topic goes I think I will sit this one out going forward. 😉

    July 13, 2010 at 13:10 #18835
    thcilnnahoj
    Participant

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

    July 13, 2010 at 14:06 #18837
    Zynewave
    Keymaster

    @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 14:32 #18838
    LiquidProj3ct
    Participant

    I’m in favor of remove it, you almost don’t need use that button.

    If you allow me, I’ll tell you some consistency changes, feel free implement them 😀 or none 😳 (maybe they’re difficult to program and they would be out scope for this update)

    – SpaceBar should start/stop playback independtly where you’ve the focus.
    – The minimun note size while resizing should be the relative snap value (not 1/128)
    – Drag’n’drop from browser to vsts
    – Option in browser’s menu to refresh it
    – Adjust absolute & relative snap points, so when they’re close it will be easy choose one or another
    – Double clicking in zPEQ should enable the nearest band
    – Alt+Intro to rename audio clips (as you do with curve and midi clips), instead shift+Intro
    – Alt+Mouse wheel to scroll horizontally, instead shift+MW, since Ctrl+Alt+MW is horizontal zoom. Same behavior in mixer.
    – Allow user save the plugin database from menu
    – Composite tracks for midi too
    – Allow split editor events, not only clips in arrangements

    July 13, 2010 at 15:45 #18847
    kingtubby
    Participant

    @LiquidProj3ct wrote:

    – SpaceBar should start/stop playback independtly where you’ve the focus.

    – Allow user save the plugin database from menu

    a big +1 for these two.

    July 13, 2010 at 15:59 #18849
    thcilnnahoj
    Participant

    @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’ve tried suggesting this a few times already – always show the popup when the cursor is on a favorite folder button in the browser, so you at least know which is which.

    July 13, 2010 at 16:37 #18851
    Zynewave
    Keymaster

    @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 16:47 #18852
    thcilnnahoj
    Participant

    Ctrl+Shift+Alt+Space – Wow, is that a secret 30-hit combo finishing move!?

    Ahem… Sounds good to me. 😉

    July 14, 2010 at 11:38 #18855
    Zynewave
    Keymaster

    I have rewritten the “project start page” chapter in the guide:

    http://www.zynewave.com/wiki/doku.php?id=guide:project_start_page

    If you have the time, please browse through it, and let me know if something should be corrected. Note that the chapter describes some UI changes that will appear in Podium 2.34.

    I plan to use bullet point lists more extensively throughout the guide. I’m going to continue updating other chapters.

    July 14, 2010 at 12:10 #18856
    Levendis
    Participant

    @LiquidProj3ct wrote:

    Composite tracks for midi too

    Great suggestion!!!

    July 14, 2010 at 21:28 #18860
    Trancit
    Participant

    @LiquidProj3ct wrote:

    – SpaceBar should start/stop playback independtly where you’ve the focus.

    Yes with only one limitation: to be able to send all keyboard inputs to a plugin (selectable in a menu for example…Reaper does this in a very comfortable way)

    Otherwise it would not be possible to enter names containing space for presets in plugins like Kore 2, which doesn´t open a text box for text input…

    Trancit

    July 15, 2010 at 18:13 #18868
    Andrzej
    Participant

    @omar misa wrote:

    @LiquidProj3ct wrote:

    Composite tracks for midi too

    Great suggestion!!!

    YES! YES! YES!

    July 16, 2010 at 00:36 #18869
    Zynewave
    Keymaster

    The “project window” chapter is now updated:

    http://www.zynewave.com/wiki/doku.php?id=guide:project_window

Viewing 15 posts - 16 through 30 (of 122 total)
1 2 3 … 7 8 9
  • You must be logged in to reply to this topic.