thcilnnahojIt’s definitely an improvement. The only inconvenience is that you’ll have to go through the same menus a few times, whereas you could set everything up in one go in a ‘bounce dialog’ like CQSD suggested in another thread.
Two other things:
– You may want to adjust the default size of the editor window (if not related to screen size) or horizontal size of the piano keys, as the new linked velocity buttons don’t fit anymore.
– A minor inconsistency concerning the MIDI/note editor. The EE (embedded editor) will in some rare cases copy the velocity region height from the SWE (separate window editor), though they’re fine with having different region heights most of the time. Here’s one way to reproduce this:
Switch to the ‘Editor’ profile > select a MIDI sequence > in the EE, set height of velocity region with the drag-handle > double-click a MIDI sequence to bring up the SWE and leave it there (it should have a different velocity region height) > click on a sound or curve sequence, so the EE switches to a different editor > select a MIDI sequence again > the EE should have assumed the velocity region height from the SWE.
…That’s a mouthful! :-#
thcilnnahojFor your information, here’s my thread on the FF forum: http://www.fabfilter.com/topic.php?topic=949
So there seems to be an obvious way how Cubase, Live and maybe others manage to still catch key strokes. Now we need a programmer to figure out how! :-k 😆
thcilnnahoj@kingtubby wrote:
Firstly, this has probably been requested before but is there any chance of mouse wheel support for the sliders and faders? Maybe with a modifier key (shift) for fine control.
I’ve asked about this before (http://www.zynewave.com/forum/viewtopic.php?t=1964), and I think Frits was not aversed to the idea, judging from the response.
thcilnnahojMmm… With such tasty appetizers, the time waiting for the main course will fly by. 😛
With the color picker, you could go one step further and add 10 or so little boxes under it, to store and recall the user’s favorite colors.
I also like the key focus framing on the project page, that you didn’t mention.
thcilnnahojXnView (an image viewing/organizing/editing program) has an option to put all thumbnails it creates into a zip file, and it works without delay when you view a folder. It won’t get around the duplicate file names, but if there’s some other way to specify which wave a mini belongs to, it could work. XnView also has an option for cleaning up and deleting unused thumbnails.
Don’t know if something like this would be thinkable for mini files!
thcilnnahojI’m sorry, I meant to say the B key – I use keyboard shortcuts for most things in Podium. But since you’re right about the B button only showing after a bounce, it might actually be more intuitive for beginners to use the menu.
thcilnnahojYep, nice work! Five stars from me. 8)
Only criticism: you could’ve said that just pressing the ‘B’ button does a bounce automatically, without the need to go through menus.
thcilnnahoj@Zynewave wrote:
If you don’t like things jumping around, then surely you could not have liked the placement of the menu buttons between the inspector and project tabs? The menu buttons would jump every time you opened/closed the inspector. Considering that, what other options are there than to put the menus at the top of the window? Part of my decision to do this is also the fact that most people are used to access menus at this location.
Well, I wasn’t directly looking at those buttons most of the time, but at the arrangement! 🙂
I don’t find one location for the menu buttons more obvious than the other. Podium never looked like a program that uses the Windows default layout to me anyway… Insofar it didn’t really bother me where they were placed.
Is it just my imagination, or is there a little more space between the tabs and the upper screen edge now? I could’ve sworn I was able to click on them while the mouse cursor was at the very top of the screen before.
@Zynewave wrote:
How about this: F6 is browser, F7 and F8 are shortcuts for the first and second resizable region in the profile. Combined editor/mixer profiles will then still work. Numeric keys 1-9 are shortcuts for switching to a profile. Go, no go?
Sounds great – by all means, go! 🙂
thcilnnahojAhh, the menu bar delay just doesn’t agree with me…
If it’s not too much to ask, I’d appreciate if it was optional (maybe in a right-click menu on the auto-hide button). I’d rather improve my aim a bit than having to wait! 😛
Also, the mixer menu (formerly known as view) button is missing its label when ‘show control buttons’ is activated.
thcilnnahoj@Zynewave wrote:
That may distress users that still use the old layout with both the embedded editor and mixer in the same profile. What say the community: Reassign F6 to browser, and reassign F7 to either editor/mixer?
Over here! 8-[
Aww, I really have no luck, do I! 😆 Just as I’m about to say I’m happy with the round buttons you present me this.
I seriously do not like the profile bar… Still, I can see the results of this vote, so let me try to propose something: allow the user to assign F7 and F8 to switch to a profile of their choice. What good is the profile rotation currently assigned to F8 anyway now, with the profile bar and all.
By the way, when you switch from a profile that has an editor profile bar to one that doesn’t while hovering the mouse over it, prompting the pop-up help, the help bubble gets stuck.
And it would be nice if you could group elements in the region properties with ctrl/shift-click and move them up/down together. At the moment, it moves only the element last selected.
thcilnnahoj@Zynewave wrote:
Let me offer another suggestion instead of the bus send/return: Add your VSTi track as a child to a new group track, and then set up the group track for realtime bounce recording. That way you have it all neatly together. Also note that the realtime bounce recording only is working if you have some events on the timeline. So you’ll need to set a marker at the end of the timeline where you want to stop.
I thought of doing this before, but did not post because it produced unreliable results when I tried it, meaning dropouts in the audio recording. I did not set a marker, though – that’s the problem, as I found out just now. Has a little workaround feel but at least it does work – thanks!
thcilnnahoj@Zynewave wrote:
@thcilnnahoj wrote:
@Zynewave wrote:
I’m now going to start on the main 2.21 feature, which will be a new track toolbar. In the default setup it will sit right below the navigator.
Hmmm, let me ask… Do you have anything else planned then for the big empty space right above the track headers?
No, not besides the display of the marker name, tempo, time-sig and scale info that is currently displayed there. You’re of course free to remove the track toolbar, or move it directly above the tracks region. I think the track filter feature will justify using up space for the new track toolbar, but I need to experiment with that.
That’s too bad… I’m just guessing here, but I think more users would like to have a few useful buttons there instead of the info text. At least I don’t think it’s that important. Then again, it might even be a bit of a problem due to Podium’s design, assuming that the whole horizontal line is one region and cannot be easily split…?
@Zynewave wrote:
@thcilnnahoj wrote:
I’m also not keen on the bean-shaped 80’s sci-fi device look and placement of the transport bar elements. This time there’s no way to keep the old setup, so I guess I’ll have to get used to it…?
Specify please: Is it the fact that the buttons are no longer rectangular, that they are joined in a button bar, that the elements in the toolbar have been rearranged?
The placement is actually clever, as we’ve come to expect from you, but it’s just against the standards everyone’s used to even from old tape machines.
What I dislike more is the shape. With those buttons rounded on only one side, the icons look like they’re not at the center of the buttons. Just an optical illusion, probably. I can get the nice old round look back by adding in spaces in toolbars – just not in the transport bar. I really liked the rectangular buttons. However, I’d be very happy if they at least were all round like the new power button instead of bean-shapes when separated with spaces (that would probably require a bit smaller icons).
Otherwise I’ll probably go with a no-transport-bar setup when I decide to upgrade, since I mostly use the keyboard for the functions on there anyway.
The menu bar simply takes away from Podium’s aesthetics, but that’s just IMO. Auto-hide is acceptable, but will also take some getting used to.
For example, when I want to open the inspector/browser with the mouse, I usually move the cursor in a big motion to the upper edge of the screen, since it doesn’t matter if I overshoot the target there. Now I have to either be more careful and stop early, or move down a little so the bar can hide again – but not too far down, or the cursor won’t land on the button when the bar disappears… 🙄 It’ll be fine when you’re accustomed to it, but right now it’s annoying.
Also, I can’t stand it if everything that’s on screen just jumps around… That’s why I’m keeping only one timeline region instead of the default four – don’t like my arrangement jumping up and down all the time when switching on loop/punch modes.
I think the labels for the top buttons in the inspector, “Group” and “Color” could be misleading to unfamiliar users. Without the help text you could quite easily think “Uh, so do I click this button to make this into a group track? And this one to enable track colors?” They’d still fit into the minimum horizontal size of the inspector if they said “group panel” and “color picker” or similar, without ambiguity.
I feel kind of bad because I only have negative opinions and nit-picking to give again. 🙁 I guess it’s best not to worry about it if everyone else is happy. 😛 I’m still eagerly awaiting the track toolbar…
thcilnnahoj@Zynewave wrote:
I’m now going to start on the main 2.21 feature, which will be a new track toolbar. In the default setup it will sit right below the navigator.
Hmmm, let me ask… Do you have anything else planned then for the big empty space right above the track headers?
Why insert a whole new toolbar, eating up space, just for a handful of buttons, while the most ‘natural’ location (in line with the track-level buttons), where also quite many other programs – Cubase, Logic, Pro Tools, Studio One – place these functions is left unused. In my hopefully perceived and accepted as humble opinion, it’d be the best place to put those SMR buttons. But I’ll look forward to the next beta to try anyhow. 😉
I’m also not keen on the bean-shaped 80’s sci-fi device look and placement of the transport bar elements. This time there’s no way to keep the old setup, so I guess I’ll have to get used to it…?
thcilnnahoj@H-man wrote:
I found that after never using it, I have switched to using the embedded editor exclusively.
Same here! Turned out to be as nice as I imagined it when I suggested this recent change. In fact, if it’s possible at all, I would request an option to only ever use the embedded editor. By that I mean when you double-click an event, the EE should pop up (if minimized) instead of the new window.
Might be kind of silly, I know, since I’m probably the only one who still does minimize the editor/mixer! 😛
thcilnnahojNo big deal, but just for the record: whenever it’s the right time to work on this, please also make the waveform display change according to the event fade’s curve (right now it’s always linear).