Topic: ..

If you disable the “link edit cursor to play cursor” option in the view menu (or the timeline right-click menu), then Podium will restart from where you place the edit cursor. In fact you don’t even have to stop playback. Pressing play repeatedly will restart playback from the edit cursor. This also works with the numpad enter key.

About the play cursor grabbing:

If your mouse has a middle button, pressing that in any of the timeline areas will place the edit cursor.

You can also configure the timeline ruler to work as a single-click positioning of the edit cursor, instead of the default timeline slide action: Open “editor profile properties” in the view menu. Select the “timeline ruler – cursor” region, and press “properties”. Disable the “left-click to slide timeline” option.

@moikkelis wrote:

@Zynewave wrote:

If you disable the “link edit cursor to play cursor” option in the view menu (or the timeline right-click menu), then Podium will restart from where you place the edit cursor. In fact you don’t even have to stop playback. Pressing play repeatedly will restart playback from the edit cursor. This also works with the numpad enter key.

Like i said, i can always move those markes, but in longer run this just slows down your working…

Maybe I misunderstood you. What I was talking about had nothing to do with setting markers, loop and punch ranges. I was talking about the edit/play cursor.

If your mouse has a middle button, pressing that in any of the timeline areas will place the edit cursor.

Yes i have, when i press it, nothing happen?

If you click within the timeline area of for example the tracks region, it should position the edit cursor when you click+drag the mouse.

You can also configure the timeline ruler to work as a single-click positioning of the edit cursor, instead of the default timeline slide action: Open “editor profile properties” in the view menu. Select the “timeline ruler – cursor” region, and press “properties”. Disable the “left-click to slide timeline” option.

done, no luck there. I want to use just one left mouse click to change that play cursor. fast and easy way you know.

Note that you have to click on the timeline ruler. If you followed my descriptions, then you should see a normal mouse cursor instead of the hand cursor when you move the mouse over the timeline ruler. Single clicking here (and click+drag) will position the edit cursor. Note that if you have snap activated, then the cursor may snap to a grid line outside your current zoom range.

And i found another thing, which i mention before. I found on that mixer setup, there is different things. Douple click option, can i have there “reset default value” option??? This would be very useful on reseting mixer values.

Those actions only apply to the device selectors, and not the other slider/dial controls. The default behaviour is to use ctrl+click to restore a control to its default value. That applies to all controls in the entire Podium UI. I’d like to keep that behaviour consistent. Double-clicking a control will in some places open the properties dialog with key focus set to the value input for the double-clicked control.

When i set up those volumes, where is values? Yes i can make bigger that volumebar, but again, is this necessary? If pianoroll or that info window can tell the value automaticly, its save’s time (again).

Adding popup display of the value is on my future plan.

@moikkelis wrote:

But.. I notice podium use even more cpu than FL Studio. Both, in my primary computer and laptop. Really dont know why. I cannot bealive it cause everyone keep saying that podium is light on cpu 🙄

My primary computer is intel 6700 Quad @ 3.2 ghz and 4 gig ram. Using Xp32bit. Laptop (my wife’s) is core2duo 1.6ghz and 2gig ram. Its using 32bit vista.

And that cpu mixing meter it’s jumping alot! example in 10% suddenly in 30%. Am i only one?

The only reliable way of comparing the CPU efficiency of different hosts, is to create identical projects with similar setup of plugins, and then see how many tracks/plugins you can add before you hear glitches in the sound.

I have coded the CPU indicator in Podium to be very sensitive to CPU spikes. Other hosts may show a CPU usage that is averaged over a longer period. That doesn’t mean the Podium engine is less efficient, just that you get a snappier indication of potential CPU spike overloads.

Looking at the CPU usage in the Windows Task Manager can also be misleading, as this will show the CPU usage of both the audio engine and the UI. Podiums UI may use more CPU than other hosts, but it has been programmed to reduce this CPU usage (resulting in less fluent animations) if the audio engine requires more CPU.