kyranI disagree with thcilnnahoj.
I think the new way of handling editor profiles is a very good improvement: it makes them much more discoverable for new users, and the configuration menu is now in a very sensible space.
Great work 🙂
kyranI’m actually wondering what you’re asking here.
When I read your post I get the impression that you want the interface to be layed out differently, but you ask for the hierarchical engine to be revamped.
I don’t think the hierarchical engine is a problem, it’s actually podium’s strength. It is not that difficult to grasp and very powerful.
In tracktion and live the signal flows from left to right, in most other sequencers it flows from top to bottom, in podium it flows from the bottom to the top. When you think about it, the approach of podium makes more sense really.
Maybe the interface can use a bit more clues that the signal flows from the bottom up.
Personally I think the foundations are very solid in podium, but the ui can use some tweaks. A lot of minor things might go a long way. I’ve got a sort of image of the perfect podium interface, but I’m lacking the time to mock it up.
kyran@Zynewave wrote:
I may skip the check-box option in the region properties dialog. I could just detect if the selected embedded editor profile has a timeline ruler in it, and if so then detach the timeline lock with the arrangement editor.
But it wouldn’t really be obvious to new users I think. Nothing really indicates that this will detach the zoom resolutions. So people will still request the feature, not knowing it’s there, or will report bugs about the decoupled zooming, not knowing it’s intended behaviour.
It’s a nice and elegant solution otherwise 🙂
kyran@Zynewave wrote:
@Markus wrote:
Nothing.. Why i even try?
What? 😕
As I replied to you in another topic, I read all forum posts. You can’t expect me to reply to every single post. I work 10-14 hours a day, 7 days a week, on Podium. I hope users understand, that when I’m not online on this forum, I’m busy developing on Podium.
If it takes some time before you answer a question, I’m kind of happy: it means nice things are being added to podium 😀
kyranIn a hypothetical world, what I think would be nice is some sort of feature like live’s racks or mulab’s modular environment:
You drag in some plugins (or just one) in the modular view and then drag in native podium gui elements, like an xy and buttons. Connect the midi cables to the synth, connect in and output.
This rack unit would then show the gui you made in the track inspector like all the other native zynewave plugins do.
It would also get around the midi vst problem (just drag in an arp).
It will most likely be a lot of work though, because it’s modular host in vst format that needs to be able to change it’s gui and tap into the api that fritz has to make it appear in the track inspector.
(and sort of needs to be paired with the feature where you can see all elements on the current fx chain instead of just the currently selected fx track)
In short: I think docking gui’s creates just as many problems as it solves. It is probably better to think of a good way to solve the problem that fits in neatly with the current podium platform before implementing a feature. A bit like ableton does: either do it right within the scope of the program or don’t do it.
kyranNice little tweaks.
I’ve got some minor ones
1. The spacebar should always control the transport, regardless of the current focus
2. A single keyshortcut to zoom in/out horizontally (like +/-), without needing to use the mouse.
3. Quick create new arrangement: just makes a new arrangement with all the default settings, no popup windows. Make this the default option. Most of the time I only have one arrangement in a project. If I change a setting on them it’s the name. The rest is nice to have, but it just intimidates new users.
I’ve got some idea’s for the track inspector and browser, but they probably don’t fall under quick improvements and are food for another topic.
Also, maybe we should do the following excercise a bit more formal:
1. What steps are taken to get from a fresh podium install to recording a vsti with a midi keyboard. Make a flowchart of this.
2. Mark the steps that contribute to the end goal green: without these it won’t work
3. Mark the steps that you should be able to skip red
4. Make a flowchart of how it should be done.
This is normally a very enlighting excercise. It should allow us to get a good workflow for new users, with good default settings, without sacrificing the tweakability.
kyrankyrankyrankyranYou should look how live does this. They are just another snap setting you can choose “narrow, normal, wide”, but you can still select the standard (or no) snap values too.
kyrankyrankyran@Markus wrote:
1. Like a swing / groove control. YES
Actually, not like a swing groove feature. Just make the snap resolution smaller as you zoom in.
Having a swing/groove grid would be nice, but it’s probably much harder to do and it’s something I wouldn’t use. (I tend to nudge the hits snapless until they sit right)
kyran@Vonbrucken wrote:
there is no demo project installed and had to create the following folders manually :
Podium Projects
Project Templates
Track Templates
During the first startup it should ask you if you want to manually set them or have them created for you, didn’t this happen?
kyran