thcilnnahoj's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 241 through 255 (of 815 total)
  • in reply to: Preview 2.36: Extended UI and mixer resizing. #19160
    thcilnnahoj
    Participant

    Sigh… I think I’m over the initial shock now. That was quite something.

    I guess there’s no way you could be convinced to make the button roundness setting also apply to all the things on track headers, mixer strips, and the rack…? I understand the implications it would have.

    @Zynewave wrote:

    I’d appreciate your feedback on the new design.

    Are you sure?
    Well then, time to put on your graphic designer flame suit, Frits! I hope it has rounded corners. :mrgreen:

    – I find it weird that buttons on track headers, mixer strips, and in the rack don’t have (noticable) shadows anymore, whereas all other buttons still do. Personally, I liked it better with shadows, as in 2.35.

    – What happened to the frame on mixer strips!? 🙁 Personally, I don’t care whether the selector buttons overlap the frame, or the frame overlaps them – I don’t want to have to look at the top of mixer strips every time to see which one is selected. Besides, it looked really neat. 😉

    – I don’t like how the group level color strips are so distinctly separate from the track headers now. I much, much prefer the 2.35 look.

    – I don’t like that the space between the input/source selectors and effects is gone.

    – It’s funny that the gain/pan fields now always use that small font, even though you said before that better readability compared to the small font on faders was one of the fields’ main advantages. 😉

    – I think a logical consequence of mixer strip resizing is that the BSMR buttons should just be centered when they are drawn on top of the meters. I’d say this should also happen on MIDI tracks (that have no meters).

    – There’s some space wasted where the B button usually is. Maybe this space could be reclaimed when you don’t actually have a track visible on which bouncing is enabled. If there is one, it would push down the SMR buttons so they’re aligned again on all tracks.

    – With the line separating the name and selector buttons on track headers gone now, I think it’d look better if the whole header was colored with the selection color again whenever it’s small enough so that the input, source, etc. buttons aren’t visible. Incidentally, since the separator is gone, there’s no indication of where you can drop things, so would it be possible to change it so that devices can be dropped anywhere on track headers?

    – I think hiding the handles in the zPEQ editor miniature when reaching a certain zoom level would be worthwhile. That way you could at least see the EQ curve (you can’t reasonably edit it anyway using that tiny editor).

    – Have you ever thought about using dials for pan again? It’s just easier to see, and definitely easier to adjust values on small strips. Unless everyone hates dials. 🙂

    – About moving the glass slider option away from color settings… I think it’s something that is more closely related to color setups. This is a really minor thing, though.

    Looks like my design preferences just differ greatly from yours sometimes. I apologize for all the bitching. Possibly more to come as I notice things, though 😛

    in reply to: Zynewave, your Vid for Drum templates #19158
    thcilnnahoj
    Participant

    I’m not 100% sure this is what you asked for, but I hope it helps. 😉

    The Kore Player instance in the video is not part of a multi-out mapping, as far as I can tell… There are no device mappings on the child tracks, so the MIDI data that is written on them flows up into the single Kore Player instance.

    If you want to use a multi-out instance, Podium creates the MIDI inputs and audio outputs separately. I think what you want to do is have audio outputs 1+2 routed to the track that sends MIDI on channel 1 (for example), and so on. This is possible if you edit the device mappings – look for the MIDI and audio configuration:

    After you configured everything, you can remove unneeded mappings and maybe save it as a template. Keep in mind that the device mappings’ audio/MIDI assignments are fixed, and can only be changed in the device mapping properties window. It’s therefore not possible to quickly reassign audio out 5+6 and MIDI in 4 to track X, as it’s all dependent to the device mappings.

    in reply to: Preview 2.34: Minor consistency updates #19147
    thcilnnahoj
    Participant

    @Zynewave wrote:

    @thcilnnahoj wrote:

    Also, Alt+clicking doesn’t unassign auto-assigned inputs.

    Correct. Would you expect Alt+Click to disable the “auto-assign to focus track” menu option? If you move focus to another track, then the auto-assign will thus no longer be effective.

    I would expect it to remove the input, and naturally don’t assign it anymore when selecting another track. However, I can see the point of keeping it like it is.

    Edit: Also also, what about the source/track menu mixup (the last fixme remaining)?

    I haven’t looked at this yet. Perhaps it’s best to make the shown menu a full track menu instead of a source menu?

    I guess so. The track menu has a few things not very relevant to the inspector (insert new track, move…), though.

    The mixing chapter should be mostly finished now, apart from a few fixme’s and those inevitable things that I forgot to mention.
    I haven’t touched the levels section because it seems to be a mix of general mixer stuff, parameter automation, and of course relics from extended mode. 🙂 As such, I don’t know what to do with it yet.

    When it’s done I’d like to try my pen on the sequence events chapter.

    Oh, and I think, when everything else is finished, we could do with a chapter for all things related to surround sound. You know what wouldn’t hurt either? A Zynewave surround panner. O:)

    in reply to: Preview 2.34: Minor consistency updates #19136
    thcilnnahoj
    Participant

    @Zynewave wrote:

    Let me know if you find a description of a standard. I also call the main return key for “Return”, and the enter key on the num pad for “Enter”. But when I look at the menus in various Microsoft applications, they all show the key shortcut as: “Properties Alt+Enter”.

    Well, it looks like ‘enter’ is often used when any of the two keys can be pressed, due to their similar function.
    You could try if shortcuts in those MS programs also work with both keys, in which case it would be called correctly.
    Since the Enter key doesn’t work for shortcuts, but controls playback most of the time in Podium, it might be better to use Return in shortcut descriptions, too. :-k

    I’ll revert to calling it Return in the guide chapters I already did, at least when it’s used on its own.

    Also, Alt+clicking doesn’t unassign auto-assigned inputs.

    Edit: Also also, what about the source/track menu mixup (the last fixme remaining)?

    in reply to: Preview 2.34: Minor consistency updates #19123
    thcilnnahoj
    Participant

    Minor thing: I see you use Enter rather than Return in pop-up help and such. So I changed all my returns to enters in the inspector chapter, although I only know this key as return… going to look it up now. 😉

    in reply to: The Podium Music Lounge #19113
    thcilnnahoj
    Participant

    @LiquidProj3ct wrote:

    And yes, the guy in the video it’s me (and no, usually I don’t wear chains, (it’s a fantasy video), that’s my pc, my city, my car and my roommate’s XXXXXX enjoy 🙂

    http://www.youtube.com/watch?v=QMQimSs_b8Y

    😆
    Very cute – I enjoyed it a lot. It’s good that the teddy already put the song on a CD, otherwise he’d be very mad at you for deleting his hard work! 😉

    in reply to: Preview 2.34: Minor consistency updates #19111
    thcilnnahoj
    Participant

    Thanks.
    I now added the rack section and uploaded correct screenshots. It’s now ready for review and corrections (especially the fixme-tagged stuff that I’m not sure about)!

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

    in reply to: Preview 2.34: Minor consistency updates #19100
    thcilnnahoj
    Participant

    I got around to updating the inspector chapter a bit. I’m not done yet with some things (haven’t started yet on the rack), but all relevant info from the old page should be there, so I hope you don’t mind me putting an unfinished version up.

    I totally messed up with the screenshots this time. 😳 Please delete all the images called “inspector_xxx_panel…”
    The images “inspector_2010_08.png” and “inspector_rack_2010_08.png” are fine and don’t need to be deleted. Sorry for the trouble!

    Noticed some things during testing:

    – When you open the track/source menu with the menu button on the track panel, or by right-clicking the track panel header, the embedded plugin editor options are present even with editors hidden in the rack.

    – Creating level automation with the track fader set to post effects enables automation on the first effect track…?

    – The Ctrl key doesn’t work when dragging sequences from the track panel.

    – The X button is not shown in the input panel when an input is only auto-assigned.

    – Pressing X doesn’t bypass auto-assigned inputs (may be on purpose).

    in reply to: Restricted to Podium license owners
    thcilnnahoj
    Participant
    This content is restricted to Podium license owners.
    in reply to: 2.35 #19088
    thcilnnahoj
    Participant

    I think I traced it back to the start: http://www.zynewave.com/forum/viewtopic.php?p=16579#16579
    …continued just last month: http://www.zynewave.com/forum/viewtopic.php?t=2352 😳

    The problem back then was that those parts of a curve enclosed in curve sequences ignored selection colors, which you bravely fixed not long ago. I don’t remember any problem with curve visibility where there were no curve sequences (I believe the track color was used for the whole curve before?).
    You could try it and see if you like it – I only did a few primitive tests recoloring the curve in screenshots, but found the results pleasing. 😉

    in reply to: 2.35 #19078
    thcilnnahoj
    Participant

    Hey, I just noticed that duplicating stuff with the Insert key now stops adding new copies as soon as you hit an already existing event.

    It previously continued to insert notes/sequences past already existing ones, and even filled in gaps between events, even it that meant the inserted one was cut short. I really, really liked the way this worked… 🙁

    Also, I think if the automation curve used the track color instead of timeline text color, it’d be less obtrusive.
    Somehow I get a feeling of déjà vu – was there some problem with it that I just can’t remember about…?

    in reply to: Preview 2.34: Minor consistency updates #19071
    thcilnnahoj
    Participant

    I’d be OK with calling it just note. At the moment, we have sound events, note events in note sequences, and points in curve sequences.
    We have to keep some ‘objects’ though (device objects), if we don’t want to list inputs, outputs, device mappings, presets, and parameters every time.

    I haven’t seen ‘track object’ used anywhere yet. Are you sure it refers to the track itself? I think it’s possible that it means the object (instrument, bus, effect, etc.) that is on the track (back in extended mode, where all tracks were still visible in the arrangement). The guide is a historical document after all! 😆

    in reply to: Restricted to Podium license owners
    thcilnnahoj
    Participant
    This content is restricted to Podium license owners.
    in reply to: Few feedback request in one screen shot #19060
    thcilnnahoj
    Participant

    @LiquidProj3ct wrote:

    I don’t think you’d necessarily need another checkbox in the tags dialog (though it might be helpful), or a second check button on tag buttons.
    What better place to tag tracks to be shown/hidden in the mixer than the mixer itself!

    I was talking about ‘hiding’ not ‘tagging’ 🙂 They’re different things. Hiding can be perfectly compatible with tagging. Hiding means ‘hide’ the mixer OR track strip, never both. Try Sonar or Reaper and right click in one of their tracks, you could ‘hide’ them in the mixer or in the arrangement view. Sonar allows you hide them in both, but we don’t need such thing because we’ve the tag system.

    Okay, so you mean something like a new “show in arrangemtent and/or show in mixer” setting for each track, totally unrelated to track tags? I just assumed the feature request was connected to tags because I remember you brought it up it from the tags preview thread!
    Such a setting would go nice with track templates…

    in reply to: Few feedback request in one screen shot #19056
    thcilnnahoj
    Participant

    @LiquidProj3ct wrote:

    1. In arrangement view I’ve selected one single clip. I barely can remeber where the others phantom clips are, so I could screw it up (and I did it several times). Please, highlight (no active selection highlight) all phantom copies when you select one.

    How about something like this?

    It won’t work, of course, if Frits already has plans to change the look of normal event selections. Come to think of it, I think it also won’t work if you have those event headers enabled. :-k
    Anyways, I’d prefer any kind of phantom copy highlighting to be optional, as I don’t need it personally.

    2. Grid should be more helpful, I had an small problem moving a clip (it isn’t easy see the bar numbers while you’re dragging), also a lot in editors.

    To more easily align sequences and events, I still like the idea of optional bars reaching down from the timeline ruler displayed at the beginning and end of events while moving/resizing them. Coloring even/odd bars differently is nice, too, but I’d prefer to have a blend setting to tone it down or even turn it off (already said that in the other thread).

    3. Hiding unuseful tracks from arrangement or mixer. Nowadays if you hide a track in the mixer you hide it too from the arrangement view. Those outputs called Drumazon Out could be hided from the arrangement, obtaining extra vertical space. In the mixer few tracks can be minimized, it helps but it isn’t enough.

    I don’t think you’d necessarily need another checkbox in the tags dialog (though it might be helpful), or a second check button on tag buttons.
    What better place to tag tracks to be shown/hidden in the mixer than the mixer itself!

    Think about it – what if tracks that get tagged would be shown in both the arrangement and mixer at first. When you remove a tag from a track in the arrangement, it stays visible in the mixer. The same happens the other way around. Since active selection in the mixer means the track isn’t actively selected in the arrangement anymore, I think there’d be little room for mixups. To again show a track that was, for example, accidentally hidden in the mixer, you could either select it in the arrangement, switch to the mixer region and re-tag it, or deselect the tag to show the track, and re-tag it like usual. You could add a modifier key for the check button to remove a track from both arrangement and mixer if you think it’s going to be cumbersome. Or remove tags from both if the mixer isn’t visible, and remove them only from the arrangement if the mixer is visible and you’re untaggin an arrangement track.
    Does any of this sound good or is it still too confusing?

Viewing 15 posts - 241 through 255 (of 815 total)
© 2021 Zynewave