ZynewaveZynewaveIf I have an offending plugin both muted and bypassed (inactive), is it safe to assume that it will have no affect on audio playback on active tracks?
Not necessarily. The plugin is still receiving idle messages from the host, which potentially can use up CPU. To be sure that it is not affecting playback, you could use the ‘unload plugins when bounce is activated’ track option.
Btw. maybe the problem with Dr-008 was that it used a lot of memory for samples, which left less for Podiums audio tracks. The ‘unload plugins…’ would help with that.
ZynewaveAnother thing that often causes me some trouble is that when I drag a file from the list into the arrangement and move it, all previous clips which were selected remain selected and are moved together.
I think that a better behaviour will be that previously selected events are automatically deselected when a new file is inserted, like when I draw a new event.
Will be implemented in release 1.45
Zynewave@Joachim wrote:
I’ve always thought that Podium has way too many tools!
In the next release, the select and rearrange tools are joined into one select tool.
As of now, there’s 8 different tools It’s ok to have this many tools, but what really annoys me is that you cannot use just one key modifier to switch between a select & move tool and a draw tool.
With the new shortcuts, you can do most things with either of the select or pencil tools, so the need to switch will be reduced.
In Podium, I’m forced to edit the lenght of every note induvidually 🙁
On the plan.
Why is it that we have a segment tool? How useful is segment selections anyway?
It’s a fast way for restructuring your arrangement. Cut a few bars and insert them elsewhere. Cutting/pasting segments compresses/expands the timeline, where normal event cut/paste will not modify the timeline.
I think having a seperate eraser tool is unnessesary when the delete key does the same. Same goes for the pan and zoom tools. They already have keyboard shortcut modifiers assigned to them, which I like by the way.
You can just remove those tools from the toolbar then (in the profile properties dialogs).
Remember, whatever you decide to do, try to follow the K.I.S.S principle (Keep It Simple, Stupid!) 😉
I live by that principle every day 😉
Zynewave@acousmod wrote:
The hard part is that nearly each software use different key combinations.
I’ve tried to put together some of them at http://sonart.free.fr/logiciels/shortcuts.htm
Thanks for the list.
Perhaps that control for real copy (like you say Frits) and control + shift for “ghosts” will be good ? In Windows we can use alt or ctrl + shift for the same thing.
ctrl+shift is used for the zoom-y tool. I’m currently implementing drag+ctrl for unique copies, and drag+alt for phantom copies.
The shift key which is used for moving between tracks (in same time position) in Samplitude and Tracktion (like moving instead of copying in Windows) will be a nice addition…
Thanks for reminding me about this. I have now implemented locking by holding the shift key (after clicking). Either the time or the vertical position of the events are locked, depending on the direction of the mouse drag.
Concerning the copy itself, there is something a little bit disturbing in Podium, certainly due to the use of the same control key for duplicating and resizing : we must press the control key AFTER begin to drag the clip, wheras in other softwares we can press the modifier key BEFORE (like for resizing).
If the modifier keys used for changing drag behaviour should be available before clicking, then it would seriously limit the possible key combinations. Since the shift+ctrl+alt combinations are reserved for the zoom and slide tool shortcuts, there is only the three single shift/ctrl/alt keys available for changing tool behaviour.
ZynewaveThanks for the suggestions Max. I’ll try to put some of them into the next release.
ZynewaveI took your project file and relinked your sounds to wavefiles on my HD. I experienced no dropouts, but I do not have the plugins installed that you’re using. I removed the plugin mappings to get the audio to go through to the master.
Suggestion: Make an experimental copy of your project, and remove inactive tracks (i.e. those that you have bounce recorded), and see if this improves the dropout problem.
ZynewaveIf anything, double-clicking a track strip should open the track properties dialog. I think that using double-clicking to center zoom would be inconsistent with double-clicking behaviour elsewhere in Podium. But maybe there should be some sort of link between the mixer and the tracks region, where scrolling in one region will keep the track in focus in the other region.
ZynewaveWhat samplerate are you using?
It sounds strange that you get dropouts when you only have a few audio tracks playing. If possible, email me your project file without the audio files.
ZynewaveCan you make audio that *is* saved to wave also play from a folder on the hard drive?
Although the files saved in the cache folder are more or less a direct memory dump, it is not going to be significantly faster than loading directly from wave files.
Is there any reason why this kind of playback couldn’t occur all the time, instead of caching to RAM?
The fastest streaming is when the audio is loaded in RAM. I believe that when your arrangement plays fine, it’s because most of your audio tracks are available in RAM. It should not matter whether disk streaming occurs from the cache files or from wave files.
Possibly the version 1.43 where you’d improved disk streaming?
The 1.43 version did not include disk streaming optimizations. It had optimized audio streaming within the engine (i.e. after the audio has been streamed from disk).
After I have completed the release I’m working on currently, I’ll probably look into optimizing disk streaming.
ZynewaveThis discussion has made me think – how does Podium’s disk streaming work? When does it decide to stream from RAM, when from disk?
Podium will use up to a certain percentage of the available physical RAM for caching any audio that is loaded from file. When this limit is reached it will start to flush the oldest cached audio before loading new audio into memory. If the audio is recorded or editied, i.e. not saved to a wave file yet, then the audio is flushed to temporary files in the sound file cache folder (configured in the preferences dialog). You should make sure that this folder is located on your fast harddrive.
It even occurs when I have only one or two audio tracks playing (so, it’s not just when there are many tracks playing at once)
Did it always behave like this, or did this start with a certain release version?
ZynewaveHow much memory do you have on your laptop?
When your track plays without dropouts, it’s probably because most of the audio is cached in memory, and does not need to be loaded from disk. This is the case after a bounce-record or after a track has been played back.
I need to optimize the disk streaming in Podium at some point. I’m aware that this is not efficient when there are a lot of audio tracks playing.
ZynewaveThis is now fixed (better late than never). The problem should only be with sounds that have the ‘relative to project path’ option selected. Fix will be in release 1.45.
ZynewaveI have changed the grid line resolution to binary jumps when zoomed out. This means that gridlines shown in the time ruler always matches the grid lines in the editor area. There are still twice the gap between gridlines in the ruler, to make room for the bar numbers. Will be available in release 1.45.
ZynewaveHi Francois,
I got your follow-up email, where you said you found a solution. Let me know if you still have problems.
Frits