ZynewaveHi Jean-Marc,
Podium 1.43 is just released, with CPU optimizations of the audio streaming and processing in the engine. Note that this does not cover optimizations of disk streaming. With the help of CPU profiling tools I found that there were things in the way that audio is routed and mixed in the engine that could be optimized. If you only have a few tracks and plugins you won’t notice much improvement, but if you have many audio channels (like you have with the multi-channel files), the performance gain can be 30%. I tested this in an arrangement with only one stereo wave file phantom-copied onto 200 tracks (equals 400 channels) and using no plugins.
I’m interested in hearing whether these optimizations have improved the performance of your arrangements.
Frits
ZynewaveZynewavePerformanceCounter. It measures something in Hz, but what and how?
This is a value that is provided by the Windows OS. It gives the precision of a timer feature that Podium uses in measuring CPU usage. The higher the better. Your 598420000 Hz is plenty.
ZynewaveHang on, after rereading your report I noticed this line:
– ASIO sample types: 18, -1
The number 18 is a code indicating the bit resolution of the input channels. The -1 is for the output resolution, and that means that the ASIO driver has marked all the output channels as being inactive.
There should be active channels, because the line:
– Output channels: 32 (11111111111111111111111111111111)
indicates that Podium has requested all 32 output channels to be activated.
Could you post a report of the ASIO4ALL driver configured for the 01X? Remember to use the update button on the report page after you have reconfigured the ASIO4ALL driver.
ZynewaveWhat about audio inputs, are they working? Try assigning one of the 01X audio input mappings to at track, activate monitoring, and see if the meters are reflecting audio input activity.
ZynewaveAre you using the latest 01x driver version 1.5.4?
ZynewaveFor diagnostic purposes, you could try the generic http://www.asio4all.com driver. With this ASIO driver you can select WDM drivers, and offers very low latency values. It may not be an optimal solution, but it should at least determine if you can get ASIO drivers to work with Podium at all.
Frits
ZynewaveThe report seems ok, although a buffer size of 441 seems odd. I see that you have all 32 output channels enabled. Are channel 1/2 those that you use for monitoring?
When you run Podium, make sure there are no other applications running that use the audio device. This could be utilities or media players etc. Most ASIO drivers only allow access for one application at the time. The WDM drivers may be shared by several applications.
Try disabling the channels that you don’t use in the interfaces dialog. Open the ASIO control panel and check that everything is ok. Try increasing the buffer size, and if possible set it to a value such as 512, 1024, 2048 etc.
ZynewaveHi,
If the audio channels that you use for monitoring are not the first two channels in the ASIO audio driver, then you may need to adjust the channel offset in the master output mapping.
Are there any error messages appearing? Does the arrangement appear to be playing ok (i.e are the meters working)?
If the problem persists, export a report file from the interfaces dialog, and email it to me (or post it here).
Frits
ZynewaveAre there limits on the number of effects per track that you can use?
You can only assign one mapping per track, so the limit is one effect per track. Using eXT to wrap an effects chain is a way to do it. I have plans for implementing a kind of wrapper mapping, so that you can route several effects on one track.
ZynewaveHi,
Currently you can only have one mapping per track. The audio flows from the bottom of the track branches and upwards towards the master output, so you need to put the effect on a new parent track to the track with your synth. Use the ‘wrap in new group track’ track menu on the track with your synth. Select the effect plugin on the new group track.
ZynewaveThe next release will have darker edges around the tool images. Thanks to super_crunchy for doing the modification.
ZynewaveI wonder if you and Zynwave are using different aa edge smothing? Standard or ClearType?
The Standard/ClearType option you find in the display control panel only applies to fonts. I create the images shown on the tool buttons with a simple graphics program called Image Composer. I just took the old bitmaps, scaled them up in size, applied a smoothing effect to get rid of the sharp pixelization, and then scaled them down in size resulting in anti-aliased bitmaps.
ZynewaveStrange, but daHornet works fine for me in other hosts
I would guess that these hosts don’t support the ‘sizeWindow’ feature then. As I said, I could get daHornet to expand/collapse correctly in Podium if I disabled this feature. This is a good example of how difficult it can be to support all plugins correctly, due to different interpretations of the VST standard.
When I import taurus.dll in Podium, I can’t tweak the first 4 parameters of the plug (Play Mode, Octave, Decay On and Glide On). I’ve checked out the VST parameters of Taurus in the plugin definition and see that Podium on incomprehensible reason uses “range from 0 to 0” in the “Value definition” for this 4 parameters
I tried it, and it works for me. You just have to drag the mouse a little further to make the value change. The reason for the 0 to 0 value range is explained at the bottom of the Parameter Properties section on this page.
Zynewaveyou should try using a darker stroke around the icon elements so they look a bit crisper
If I email you the .png files for the tool images, could you apply the stroke effect to them?
Any opinions from other users about the darker stroke look?