but I still don’t know how to delete some notes/programs from the drum map. Is this possible?
Yes. You can delete individual drum key presets, by locating the presets in the list panel/window (not the preset panel in the track inspector). If you enable the ‘drag-reordering’ list option, you can reorder the drum key presets any way you like.
And what about the “automatic mapping for multiple out VSTi”?
If you mean that the first program preset should automatically be assigned to the track once a global plugin instance is assigned to the track, then that is going to be implemented in a future update.
Hi Max,
Podium tells me to create a library preset. As I assume, I need to create a bank preset in order to save the state of all 5 programs, right?
Yes, you need to use a bank library preset. If this is a new project you created since the new preset system was implemented, the program presets you see in the preset panel should be children of a ‘local bank’ preset. You can verify you have the ‘local bank’ preset with the list browser. Just assign the desired program to one of the tracks with the Halion player, and the project should automatically store the plugin settings on the track. No need to create a new preset object.
EDIT: I have edited the drum map created by Podium.
I assume this means you have found the answers to your questions about the drum kit presets.
P.S. Is there a ZComp planned?
Yes. I’m still working on zReverb. After that I think the next plugin will be zMaster, which will have a limiter, dithering, mono/stereo and mid/side monitor options and possibly specialized level metering. Before I start on that, I’ll do some work on other Podium features.
I assume plugins that don’t work on P4HT wouldn’t like P4 dual core either?
Most likely. However multi-processing crashes are highly dependent on timing issues, so unstable plugins may behave differently on HT/dual processors.
but i had a crash after few minutes telling me that it may have corrupted my project file
Are you using the updated plugin dll file? What ASIO buffer size are you using?
As i was working on some project i did not go further
The risk that a plugin may actually have corrupted the project is very little. Next time it happens, save your project to a new file, keep the old project file as backup, restart Podium and check that the project is intact and plays like previously.
I’ve been reading some of the replies over at productionforums, and a lot of the talk seems to question why buffer underruns would occur. Let me just state that I don’t think actual buffer underruns occurs in the E-MU ASIO driver. I rather suspect that it is a problem with the samplePosition counter that is not updated correctly.
Thanks for testing it acousmod.
An option for two distinct microphones instead of a XY couple will be also usefull.
The focus with zReverb was to create a flexible reverb with as few parameters as possible. There are many internal parameters that could be exposed in the UI, so perhaps later on I will create an advanced reverb plugin with more options. Speaking for myself I am often discouraged from making my own presets in synths and effects if I’m presented with a huge number of options and parameters. With a small set of parameters like in zReverb, perhaps people will be more inclined to design their own rooms.
– ASIO sample position gaps: 35 (440)
Slightly different yes. Your samplePosition skips forward instead of backward. It is possible that if you had let it run a little longer that you also would see a jump in the opposite direction, like Max’s report showed. At least it appears that the interval between the gaps are the same as those Max experience.
Crash-bug fixed. It was caused by odd-sized ASIO buffers. A zip file with the updated zReverb plugin can be downloaded from the VIP lounge.
Hmm, good thing I called it a beta release of zReverb. I just made the plugin crash when trying it out on my low-end internet PC. 🙁
Use it at your own risk! I’ll start hunting for the crash bug.
Max sent me a report with his E-MU ASIO driver diagnostics. In that report these details are of importance:
Log period: 17.05.2006 22:36:52 – 17.05.2006 23:00:34
– Current sample rate: 44100
– Input/Output latency, buffer size: 486/492, 440
ASIO driver status:
– ASIO sample position gaps: 38 (-440..47080)
The sample position is provided by the ASIO driver and it should be a continously running counter that increases with the buffer size on each buffer called by the driver. Some ASIO drivers use this samplePosition counter to notify the host if buffer underruns have occurred in the ASIO driver code. Podium checks the samplePosition only to notify in the UI that a supposedly buffer underrun has occurred, and that is why you won’t hear any clicks in the sound or see any CPU spikes in the Windows performance graphs.
In the report above it appears that the samplePosition provided by the E-MU ASIO driver occasionally is offset from -440 and up to 47080 samples. With a buffer size of 440 samples, -440 means that the samplePosition is not advanced at all. I’m guessing that the -440 is occurring at regular intervals and at some point the 47080 sample forward jump occurs to correct the accumulated sample offset error. So to me it seems that the E-MU drivers internal counter for the samplePosition is updated incorrectly.
Apparently not that many hosts check the samplePosition at all, since the E-MU drivers are not reported to cause problems in Cubase and other major hosts. I would prefer not to degrade the error check in Podium, so if someone at E-MU could look into this it would be super. Since the samplePosition jump occurs at regular intervals, it should be simple to track down what is causing this.
Technophobia, could you post your interface report here to verify yours is the same problem as Max? Also if you have contact to someone at E-MU on the productionforums site, maybe you can paste this post or post a link to this topic over there?
Thanks for looking into this Frit’s
Just a slight correction: It’s spelled Frits (without the ‘) 🙂
