thcilnnahoj@Zynewave wrote:
Is the problem only the location of the new editor bar? If so, you can just add a new toolbar above the transport troolbar, and move the editor bar there. I did not do that in the default setup, because I think it takes up too much space. But it would make it more similar to Logic Audio.
I tried that, too, but then I thought why have two bars taking up space when it could be just one.
Now:
Idea (don’t mind the blue lining like in the inspector too much :wink:): 
And when you click on the selected ‘tab’ again it gets minimized.
Just an idea! Sorry for posting fantasy pictures all the time! O:)
By the way, are we going to be able to choose which profiles appear in the toolbar?
@Zynewave wrote:
@thcilnnahoj wrote:
P.S.: I see the profiles for ‘split timeline’ and ‘split mixer’ are not present in beta 3 anymore – I’m sure they’ll come back, right?
No, I did not plan to put them back in. Why do you want them? The only difference to the new Tracks/Mixer profiles is that you don’t have the dual mixer and the transport and edit toolbar are not merged into one toolbar.
I don’t need them, but I think they may have given people with two or more monitors a starting point to see how to configure Podium to work with their setup.
thcilnnahoj@Zynewave wrote:
About “editor profiles”: My intent with using the word “profile” was originally to try to separate the setup of the editor from the actual editor. Editor in this case being a window or the embedded editor. You can have several profiles that you can switch between in one editor. I’m now thinking about skipping the use of the word “profile” altogether. It’s a bit much to refer to the “editor profile properties dialog”. Anyone think reducing “editor profile” to “editor” is a good/bad idea?
Probably less confusing to new or occasional users, but it might take away from the notion that you can have many different profiles/setups for each editor/region. Can’t decide on good or bad right now…
thcilnnahojPhew… looks like 2.20 is going to bring some pretty big changes again… 🙂
Zooming issues in the editor are fixed, as far as I can tell!
The new profile buttons… I think they need some more thought, and maybe user input (hint, hint… to everyone reading :wink:).
You have to agree it’s not very ergonomic to open the editor/mixer by clicking on a button in the top right corner, move the mouse 3/4 across the screen to perform edits, and back again to close it. It’s quicker with F6/F7*, sure, but over time I’ve read from many users on this forum that they prefer not to use keyboard shortcuts. Having the buttons up there unnecessarily makes the user work more.
If you definitely want to go in this direction then I really think how Logic handles this is the way to go, like Markus (I think!?) said in the other thread.
That means: get rid of the different profiles for the embedded editor and the mixer and consolidate them into an “all-containing box” profile instead. Put the new page-switching buttons on a header or footer bar belonging to this profile.
* Speaking of, what about the hide/show function on the F keys – it will become kind of deprecated now, I think. Since why would you minimize the editor/mixer when you can just jump over to the new ‘tracks’ page and back? Maybe change it so they open the ‘editor’ or ‘mixer’ page and press again to close it, returning to the ‘tracks’ page.
P.S.: I see the profiles for ‘split timeline’ and ‘split mixer’ are not present in beta 3 anymore – I’m sure they’ll come back, right?
thcilnnahojThough it’s a trade-off, you might want to set a minimum height for the embedded editor and mixer in the default setup. I was fooling around a bit and accidentally moved the mouse during double-clicking the editor’s header while it was minimized, click-dragging it instead just one or two pixels up. That resulted in not being able to open it anymore by F6 or double-click but had to drag it up to a usable size again. Most users would probably see what happened, but I think the German saying that you should always have the “DAU” (dumbest user imaginable) in mind is applicable.
Alternatively, add a standard help text when hovering over the headers, if that’s possible.
thcilnnahojHere are some of the many ways to zoom:
– Use the mouse wheel to scroll on the navigator or the timeline
– Select the Zoom X/Y tool and click-drag over the arrangement
– Hold CTRL+ALT and use mouse wheel or click-drag to scroll only horizontally
Otherwise you can also get the old scrollbar back, of course. Go to the arrangement view menu > editor profile properties > insert new > scrollbar > move it to where you want with the up/down buttons!
thcilnnahojDo you mean in the curve/automation editor? It should only display the notes on the track you’re automating so you can better sync your automation.
As far as I know, they’ve always been there and you can’t disable them.
You can only set the curve opacity to 100% (editor’s view menu > editor profile properties > curve > properties > curve fill opacity.
If you’re talking about the MIDI editor however, then right-click on the piano keyboard in the editor from which you want them removed > piano roll region properties > set ghost note contrast to zero.
thcilnnahoj@Zynewave wrote:
@thcilnnahoj wrote:
Simply try de- and reselecting an event – it uses the right profile but the zoom level is still locked (I tried with the default setup).
I’m not sure I understand. When you select an event, and the embedded editor shows a timelined profile, then the initial timeline zoom is set to the duration of the event. You can then change the zoom of the embedded editor without affecting the arrangement zoom.
Yes, meanwhile i noticed this, too. I spoke too soon 😳 – it first confused me that the zoom setting changed when I selected a different event, and as luck would have it, it changed precisely to a zoom level at which it looked as if it was still time-locked.
I’ve put a short video in my box, maybe it explains what confused me better – I guess those zoom jumps are not the intended behaviour.
thcilnnahojDo you quantize other instruments that you play before/after laying down the drums? I’d guess not, if you want it to sound more organic. Sometimes a ‘missed’ beat can sound quite good if it doesn’t stand out all by itself. But then again, I like (acoustic) drums that have not-so-great timing. 🙂
Right now I do it the same way as you: go through parts and move notes by hand.
One way would be to use something like groove templates (not in Podium, though), but that would in essence just quantize other instruments to the ever-so-slightly off beat drums, which kind of misses the point.
You could also try playing with the ‘randomize note timing’ setting in the track properties. However, it has very little effect on short notes – and since I guess nobody holds their drum notes… 😆
Also, Frits pretty much said he’d remove those options once MIDI fx are implemented, as that offers many more possibilities.
Otherwise, a flexible quantize option sounds like a good idea for a feature request.
thcilnnahoj@Zynewave wrote:
The embedded editor view menu now includes editor profiles that has a timeline ruler. Selecting a profile with its own timeline ruler will detach the timeline zooming from the arrangement editor. The embedded editor remembers if the last selected profile had its own timeline.
Wow, that was quick! 😮
Looks very nice but it’s not there just yet. Simply try de- and reselecting an event – it uses the right profile but the zoom level is still locked (I tried with the default setup).
More suggestions:
– Add a default track color to the default setup color settings. Grey events/notes on grey background are not the prettiest thing to look at, and totally new users might be turned off. The coloring feature could be nicely displayed if all tracks were colored already, and it would also automatically activate the color picker in the inspector, which you can’t miss then on opening your first project ever.
– Add a right-click menu to the power button with a checkbox for “activate power when opening arrangement” and a shortcut to MIDI/Audio interface options.
– A little cosmetics: Maybe add a seperate option for how much the track color is applied to note events when ‘colorize notes with track colors’ is enabled. As it is now you can’t have nicely saturated notes without setting an over-saturated track color, as the notes are always less colorized than the track. If you were to set ghost note contrast to 100%, even the ghosted notes become more saturated than the actual notes when you select A MIDI event.
Also found a little spelling error: On the ‘create new project’ page, the help for both ‘scan and import plugins’ buttons says: “[…] import of VST plugins that supports […] configurations.”
@Mike G wrote:
With new timeline it’s not as easy to scroll to the right, past the end of the arrangement. (Was easier with scroll bar also present due to beind able to zoom out past full width of tracks and also being able to click > arrow)
If you have activated ‘left-click to slide timeline’ (on by default) it shouldn’t be a problem to do that. Otherwise you can zoom out infinitely with the navigator, though it’s not exactly the same as just scrolling right of course. You can also use shift+mouse wheel to scroll horizontally… Guess I’m not telling you anything new here. 😉
Edit: Scratch the other post. Dumb mistake on my part. 🙄
thcilnnahojHow could I forget this one:
Allow resizing of multiple selected events in the arrangement! It sounds simple enough to do, but of course it may not be…
(Extended version: also apply this to multiple events’ fade/gain handles)
thcilnnahojBrowser favorite folder buttons should always pop-up help displaying folder location, even if help is disabled – like sends in the mixer. That way you don’t have to play memory with your favorite folders.
thcilnnahoj@druid wrote:
Send another one. Almost two months? Too long. 😛
Two months…? Take another look at the posting dates 😯 – shame on IK, I’d say.
thcilnnahoj@Zynewave wrote:
I’m not dismissing it. I’m just explaining why I have made an effort to avoid wasted vertical space. I’ll consider adding an option in the embedded editor region properties, to enable non-embedded editor profiles as well.
That’s great – thanks! 🙂
I would really appreciate it because then I could edit parts scattered all over the arrangement (when zoomed out) without having to drag the floating editor (which I don’t find ugly at all) out of the way or constantly close and re-open it when switching parts. I see now that some of you like working with the editor as it is – however, this would be just an option that looks like it could be easily added, and I think it’d be worth it.
Markus:
Maybe it’s just a language barrier sometimes…? Frits said he’ll consider it – that’s what I was hoping for. He’s not going to jump through hoop and get it done tonight. To put words in a song:
This was a triumph
I’m making a note here: Huge Success
It’s hard to overstate my satisfaction 😉
thcilnnahojI don’t remember adding the timeline region (like I said, I never use the editor), maybe it carried over from an old default setup? If not, then I guess I must have, at some point. And while there’s no horizontal scrollbar in my setup, yes, of course there’d have to be one for this to work.
Vertical space… Hmm, If you look at that Logic screenshot (the overall element size isn’t so much different from Podium), I think it works just fine with scrollbars, timeline, markers and shiny wasted space – and the whole picture isn’t even 900 px tall. Of course there are space problems when you have the mixer open as well (can’t have both in Logic), but that will always be the case, whether there are 40 pixels more or less. However, neither the timeline nor the scrollbar would even have to be there in the time-locked editor. You could, for example, make this a different editor profile and everyone could quickly switch between them in the view menu.
Some of us are simply arguing for more horizontal space without having to zoom all the time. Please don’t dismiss it just yet… 🙁
Good night!
thcilnnahojI don’t exactly remember when this changed but I’d like to see the old behaviour back on this one:
– Double-clicking an event’s volume handle should set focus to gain offset in the properties window, not event name.
And one more, may not be as easy to do:
– When “Set minimum track height to fit contents” is disabled, resizing tracks hides the bottom of the hierachy, whereas it should scroll upwards to hide effects further up the chain instead, IMO.