Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterI noticed you have all 16 delays numbered, except for the one I can see as “Delay 1”. Instead, you call it “Delay time”. Will this be the internal pre-delay for the entire reverb?
Not exactly. The delay 1 time defines both the length of the first delay line and also is an offset for the remaining delay lines. Furthermore the room size parameter will also scale the delay times for delay 2-16.
ZynewaveKeymaster16 delay parameters! Bloody hell, thought you were keeping it simple lol
Yeah, I know, I tried my best to avoid it 🙂
why not have a user library for the presets, so if anyone turns out to be adept at tuning the settings they could send in presets themselves?
If anyone comes up with interesting presets, I can host them on zynewave.com. Maybe even include them as extra fxb bank files in the Podium installer.
I’ve also considered a small competition, perhaps on KvR, where I will give a Podium license to the one that can come up with the best zReverb presets. That way I would also get some presets for the default zReverb bank. You think that’s a good idea?
ZynewaveKeymaster
The latest face-lift, shown with a dark-grey color scheme. The image also shows the new brushed-metal texture that will be all over the next Podium 1.60 release.
I’ve replaced the diffusion module with a new algorithm. The sound quality is hugely improved, at the cost of a slight increase in CPU usage. You’ll notice that there are 16 new parameters for the diffusion delay lines. I spent days trying to tune a golden set of delay times, but this is one of the trickiest secrets to good reverb design. So I decided to let the preset designers be responsible for setting the delay times 😛
But seriously, a lot of different sound scapes can be modeled by juggling the delay times. There is not a single set of tunings that will fit all purposes. I’ve added a ‘tuning pad’ XY click-pad which allows both randomizing and automatic correction of the delay times so ringing tones can be elliminated.
May 31, 2006 at 22:50 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymasterThe Drum Map Preset is a bank, and thus should save all programs, right?
Ok, I think I understand what you want to do now. Have you created a new preset configured as a ‘drum kit’ or have you converted one of the existing programs?
Check out the ‘Song B’ in the freebees demo project. The Drumatic plugin is set up with multiple outputs and a ‘kit template’ preset (which is just an empty program preset) is assigned to the Drumatic MIDI tracks.
ZynewaveKeymasterbut 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.
ZynewaveKeymasterHi 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.
May 30, 2006 at 22:15 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.May 30, 2006 at 06:09 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymasterI 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.
May 26, 2006 at 09:03 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.May 24, 2006 at 17:16 in reply to: Restricted to Podium license owners
ZynewaveKeymasterThis content is restricted to Podium license owners.
ZynewaveKeymasterbut 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.
ZynewaveKeymasterI’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.
ZynewaveKeymasterThanks 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.
