Zynewave's Forum Page

I tried your Podium.ini file, but there isn’t anything wrong there. I did however notice a higher than usual CPU usage during my test, and I located the issue to the meter drawing in the tracks region. Try to open the tracks region properties dialog and set the “audio meters” combobox to “hide meters”. Let me know how much this fixes the issue for you.

The meter update code has been optimized a long time ago, but it seems that some of the recent updates to the UI has disturbed this. I’ll profile the performance the next few days and hopefully fix this for the 2.26 release.

So, the Podium CPU indicator shows 4% while the Windows task manager shows 66%?

As soon as you stop playback, does the CPU go back to normal?

You say it glitches. Do you mean you get gaps in the sound without the Podium CPU indicator going into the red?

Do you have any VST instruments in the arrangement? If there are any sample-based instruments then that can explain the rise in memory usage.

It will depend on the ASIO buffer size and the sample rate.

Windows provides MIDI messages with with 1 ms accuracy, so that’s 44 samples jitter (at 44100 sample rate), compared to what you play on the MIDI keyboard. On top of that is all the latency added by the MIDI controller itself and the transmission to the PC.

Some hosts will try to play received MIDI messages as fast as possible, so they will queue up the events to be played at the start of the next ASIO buffer. This method will introduce a sample jitter for each note the size of the ASIO buffer. An ASIO buffer size of e.g. 4096 will add 93 ms jitter. Totally unusable. In Podium I add a latency of the ASIO buffer size to the monitored playback. That means the timing is steady and the jitter is minimal.

That latency is only added for the realtime-playback. The MIDI messages are still recorded with the timing that the MIDI events arrived at, which explains why you see a negative latency when you compare realtime-monitoring with playback. It can be argued whether the recorded events should be placed as they are performed or heard. Some may perform on their MIDI controller as a response to the timing of the arrangement playback, and others may perform on the MIDI controller in anticipation of what their instrument will sound like.

If you want sample-precise slicing, then you need to use the “linear (sample rate)” time resolution option when you create the arrangement.

When you use the bar/beat resolution the event time positions are stored with a resolution of 65536 units per bar. Depending on the tempo, that resolution does not match the sound samplerate, and so when you slice a sound event it may occur at a fraction of a single sample.

@zamrate wrote:

Just downloaded the latest Podium yesterday to try out. So far I’m quite impressed, although I had a few crashes when doing drag’n’drop from Inspector Devices to Tracks.

I would be glad if you could find a way to reproduce those crashes. If it is a plugin you’re dragging onto a track, then it may be the plugin that crashes, in which case there is not much I can do. If it is not the plugin, then it should be an easy bug to fix, if you can tell me how to reproduce the bug.

I have created a new hardware definition for my Virus B: The MIDI comes from my M-Audio Delta1010LT card into the virus and the Virus B’s output goes back into Audio In 3/4. It all works for playing’n’sequencing.

I have 2 questions:

1) When I put a few MIDI notes into a sequence that is routed to the Virus B, I press play and record another track on Audio In 3/4 (= Out 1+2 of Virus B). Afer that I can see that the audio in the Audio Track is place too much on the left, as if it would come BEFORE the notes were even playing. Seems like the latency compensation does not work correctly in this case?

If you use the normal audio input mappings to record, then Podium cannot know that this is the Virus, and thus it does not compensate for the Virus MIDI playback.

For the delay compensation to work, you need to have an audio mapping in the Virus device definition, that is linked to the Virus MIDI mapping using the device definition and global instance settings in the mapping properties dialog. If you are using your Virus as a monotimbral synth, then you can combine both MIDI and audio in the same mapping. That way your Virus will appear like any monotimbral VST instrument. Check out the AN1x definition to see how that works.

2) Is it possible to directly bounce my sequence, just as if the Virus B would be a VSTi (in that case one just presses B and everything’s perfect). (I would like to: Stop the sequencer. Position the transport to the start of the sequence, press B and it would play and record the Virus B just as easily as once offline bounces VSTi’s.)

Yes, provided that you have set up your Virus as I mentioned above. Right-click the track where you have the Virus audio mapping, and select “bounce > enable realtime record bouncing”. Currently you have to go in and manually draw a sound event for the bounced sound. That will be fixed in one of the next Podium releases, so that this is done automatically when recording starts.