@thcilnnahoj wrote:
Is this something you have considered adding to the (distant) future plan, Frits?
Yes, but it can be a bit tricky considering that mouse-wheel is already used for scrolling/zooming. Say for example you use mouse-wheel to scroll the track list up/down. What happens if during the scrolling a gain/pan slider moves under the mouse. Should the mouse-wheel then start moving the fader instead? Similar problem in the mixer.
@Mike G wrote:
Q: Can you do what you can with the scalpel with the pencil tool? (i.e. Split audio and midi events)
BTW I’m talking about all parts of podium (arrangement window too) not just piano roll.
Ctrl+T is the key shortcut for splitting all selected events at the edit cursor. You don’t need the scalpel tool if you can get used to that shortcut. You can then remove the scalpel tool from the toolbar and thus won’t risk confusing it with the eraser tool.
@thcilnnahoj wrote:
If possible, could this be changed to make them work like the Inspector/Browser tabs – always show/hide with a single tap?
The F1 to F5 keys for the inspector also works like F6/F7, where they first set focus to the inspector panel (if not already in focus) before doing a close action.
Is there a need for a double-click? Why not make them show/hide with a single click on the whole header (not just the arrow to the right) instead.
Resizing would be compromised a bit by this… Maybe it’s possible to detect a ‘grab-action’ if you don’t let go of the mouse button immediately? :-k
Single-clicking the title is also a shortcut for setting the key focus to the mixer/embedded editor. It works similar to a normal window titlebar, where double-clicking also toggles between restore/maximize state. Making single-click on the title automatically open/close goes against expected windows behaviour I think.
@koolkeys wrote:
I restarted my system yesterday, so maybe it reset whatever went bad.
How long had your PC been running since your last restart? If it has been running for 40+ days there is a common bug that involves wrap around of a system timer counter. Lots of software will fail due to not taking this wrap around to zero into account when doing timing comparisons.
@koolkeys wrote:
I’m assuming that Podium supports MIDI drag and drop from a plugin. But maybe I’m wrong?
That is supported. What happens if you drag a MIDI file from a Windows explorer onto a Podium track?
The moment it touches the edge, I get my debugger popping up.
Which debugger is that? Is it one you have running in the background?
When you render the bounce sound on the master track, you capture a copy of the mix you are hearing on your master output speakers/headphones.
Not sure if that is of any help to you. Otherwise you’ll have to provide more specific questions.
This is not implemented yet. It has previously been requested by acousmod, so it is on my plan for the future.
Interesting. If this product becomes a success, I won’t have to make my own bit-bridge implementation when I start working on a Podium x64 version.
I’ve added WASAPI support to the future plan.
This can be achieved by using project templates:
You create the different device setups that you use in different circumstances, and then save each to a project template. Then you use the “load device setup” submenu in the project templates menu to switch between the different device setups.
Thanks 🙂
There is no way to clear all sounds in one command, but a quick way to clear each individual sound is to open the sound properties dialog and enter 0 in the length.
@Conquistador wrote:
It appears to be a Project Properties name that is not changed after the Save Project As… command is used.
Correct. The name entered in the project properties dialog is not linked to the file name. That also applies to the name entered in the sound properties dialog. My original thought behind this was that it would make it possible to enter a more specific name for the object, also allowing the use of chars that are illegal in filenames. The option to ignore the object name and just always use the filename has been requested before by acousmod, and it is a FR that is creeping up on my todo list. Improved file management is also on the list, but right now all my attention is on the new automation system.
How can I get the Source option to come up again with my track so I can add an instrument? Note I can insert fx, just not instruments.
The source submenu is only available on the track at the bottom of the chain. It could be that the track on which you open the menu is a parent effect track.
If you still have problems, please email your .pod project file (no need to attach audio files) to info at zynewave.com (email is also listed on the home page).