Has it always acted this way, or did it start with a particular version of Podium?
If you incrementally reduce the size of the timeline area (by resizing the window or the inspector/mixer), will it at some point jump to normal speed or does the speed slowly improve?
How about if instead of resizing the timeline area, you zoom in on the timeline and the vertical track size. Perhaps scroll the timeline so that the loop section is outside the displayed range. Any sudden jump in speed?
@thcilnnahoj wrote:
So is there no quick way for you to ‘patch’ the meter update rate? 😉
They are processed for each buffer for CPU efficiency reasons. It would take more than a day of coding to make it independent of the audio buffer size. For all normal purposes, there is no urgent need for this I think.
The meters are updated once for each buffer. So that’s why they are slow to update with large buffer sizes.
What screencast program are you using?
I have been checking out various screencast recorders these last few days, and I found that BBFlashback Express (freeware) has an option to record the soundcard output, although that didn’t work for me.
With my RME soundcard, I’ve physically cabled the audio output back into a stereo input. With the RME mixer software I can route the mic directly to the output, so I’m able to record both the mic narration and playback in Podium (with ASIO).
@Vonbrucken wrote:
the following folder directories appeared in red …
And no demo project were created …
Currently there is no demo project bundled in the installer. The old demo projects were removed because they were hopelessly out of date. I’ll probably add a new demo project again at some point.
@Vonbrucken wrote:
@kyran wrote:
@Vonbrucken wrote:
there is no demo project installed and had to create the following folders manually :
Podium Projects
Project Templates
Track TemplatesDuring the first startup it should ask you if you want to manually set them or have them created for you, didn’t this happen?
it did but strangely it only managed to create the “Hardware Definitions” folder …
Did Podium automatically pop up the preferences dialog with warnings for the folders you created manually? If not, then it must be because these folders in your Podium.ini setup already pointed to valid folders.
If you have plugins that introduce delay on a bus return, then any track that has the corresponding bus send will be delay compensated. The only way to get rid of this is to either remove the bus send on the track you want to monitor real-time, or to remove the delay-introducing plugin from the bus return. Same thing with delay-introducing plugins on the master bus.