ZynewaveI’ve now added support for the Del key in the file browser. It will be included in Podium/Podium Free 3.0.3.
I’ve checked the bounce rendering, and I don’t find a problem with rendering within a punch range. Remember that you must have both punch in and out mode enabled, and that you must use the “render within punch range” command. The normal render command will disregard the punch range.
ZynewaveOn the website there’s a tip but only for Cubase, here’s the link:
http://www.soundsonline-forums.com/showthread.php?t=15355
Whew, I gave up reading this. I feel this is too complicated without having the plugin to test with. If it doesn’t work in Podium x64, then what about Podium x86?
ZynewaveThanks for the file. I can load the project and start the arrangements ok with my RME ASIO driver. I of course do not have any of your sound files and plugins, so playback does not produce sound on my system.
The mappings in your project are quite messy. Both your audio inputs and outputs have duplicate (redundant) mappings, and you have three “Devices” folders, each with their own set of bus mappings and plugins.
Unless you already tried the “Merge Project” feature, I would suggest you create a new project with no arrangements, but with a clean set of audio/MIDI/bus/plugin mappings, and then merge your old project into the new one. Perhaps that will clear up some of the redundant mappings.
ZynewavePlease email the .pod file to me. All the driver stuff is encapsulated in the Device Mapping objects. Podium should of course not freeze even if there is something wrong with the mappings. I’d like to take a look at that.
Zynewave@michi_mak wrote:
EDIT : kingtubby provided his/her own shoot out with a different plug in on a different machine and came to the same conclusion …
Please reread my post earlier on this page, where I explained why kingtubby observed higher CPU usage.
Zynewave@michi_mak wrote:
@Zynewave wrote:
…The most important comparison factor IMO ought to be how many plugin instances you can run simultaneously before the CPU overloads…
this is where i started – as a rather small project overloaded Podium but not the other hosts i tried for comparison …
Then please reread my posts in this topic. I asked you twice which plugin was causing this, and I still haven’t gotten an answer. I suggested a method you could use to figure out which plugin caused the CPU overload. If you experience 100% constant CPU load, then the problem is most likely due to denormals in a plugin, and not a general problem with Podium performance.
Zynewave@michi_mak wrote:
latest cpu shoot out :
1 wav file played in loop with 1 vst effect ( KUASSA Creme )Zynewave : avg 18%
energyXT : avg 9%
REAPER : avg 2%EDIT :
Studio One Pro : avg 11%
Live Lite 8 : avg 12%i rest my case …
If those percentages are from Windows Task Manager, then the percentages include the entire application, including UI updating. That is why kingtubby notices that running Podium minimized results in lower CPU usage, because the UI in that case does not need to be animated. The Podium UI has been programmed to use available CPU power to animate the UI smoothly. The UI thread is lower priority than the audio engine, so if the audio processing takes a lot of CPU, then the UI CPU usage is reduced. You need to measure plugin CPU usage at a higher total percentage, to get comparable numbers. The most important comparison factor IMO ought to be how many plugin instances you can run simultaneously before the CPU overloads.
ZynewaveZynewave@michi_mak wrote:
what do you hope to gain by changing presets?
Depending on the plugin, some preset settings may cause a higher CPU load, possibly leading to denormals. If you see 100% usage, then it is most often caused by denormals.
atm it seems that Podium suffers from cpu spikes when various plug ins have been changed / added / deleted for some time – but why does Podium use so much more cpu power ( charged by Windows Task Manager ) than say REAPER?
To repeat myself, try to pinpoint which plugin is causing you trouble. When we know that, it will be easier to go from there.
Zynewave@michi_mak wrote:
the exact same plug ins with the exact same presets in the exact same project don’t overload other hosts …
If you want help with diagnosing the problem, then you’ll need to provide more info than that. What plugins? What hosts?
You could try to pinpoint which plugin causes the high CPU usage. Bypass/remove your plugins one by one, until you find the one that causes the high CPU usage. Once you find the plugin, try changing preset. Etc. etc.
Zynewave@michi_mak wrote:
issue might be related to “left overs” when changing / swapping plug ins …
One way to find out, is to save your project, reboot, load Podium and the project again, and check if the CPU usage is lower?
Zynewave@frollo9386 wrote:
a little off topic but how you can create multiple master track?
Drag audio output mapping(s) onto the blank area below the last track.
Zynewave@electricmuffin11 wrote:
It should of course be possible to manually create a new arrangement from scratch, using only MIDI tracks, to replicate the way a MIDI file is imported.
To clarify, do you mean that it ought to be possible but isn’t at the moment, or that it is possible and I’m doing it wrong? 😕
It ought to be possible. Until I get this fixed, you’ll have to import a MIDI file, and modify the imported tracks.
ZynewaveThanks for the detailed screenshots. This is a bug. It should of course be possible to manually create a new arrangement from scratch, using only MIDI tracks, to replicate the way a MIDI file is imported. The inspector and track menus expect to have a “master” audio track in the arrangement. I’ll fix this so that it skips the master track requirements, if there are no audio outputs defined in the project.
Zynewave@thcilnnahoj wrote:
The strange problem I remembered (and now confirmed) is that I have trouble getting the first input note recorded at all if it is played close to the start of a bar.
This happens only when a new sequence is created by the recording – NOT when I record with a sequence already present on the track and the recorded notes get added to it. (Frits, if you need any more info, just tell me once you get back!)Other than that, I didn’t notice any timing-related problems… If and when the first played note was recorded, it was on time. 😕
Thanks. I managed to reproduce and fix this problem. It happens when recording short notes that starts before the bar line and ends after the bar line. I just released 3.0.2 with a fix for this. I could not detect any “bad” timing, only the occasional dropped first note.