Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterHey,
are 1+2-15+16 related to microtonics 8 multiouts
Yes. The microtonic 2 plugin supports 8 stereo outputs, so Podium has paired the channels into these 8 mappings. You can rename the mappings so that 1+2 becomes 1, 3+4 becomes 2, … 15+16 becomes 8, if you prefer it that way. Somewhere in the microtonic UI there must be a selector which allows you to assign each drum sound to one of the 8 outputs.
why is there a pianoroll for each group track instead of one?
You should only create note sequences on one of the tracks assigned with a microtonic mapping. The other tracks with the multiple output mappings should just be left blank on the timeline. The purpose of these tracks are only to insert the multiple output of the plugin into the Podium mixer.
how do i save my project so when i load it up again its kept the sounds i used
On one of the tracks with the microtonic plugin you should create a library preset. I recommend you do this on the track with the 1+2 output mapping. The microtonic plugin may require that its entire bank and not just the current preset is stored in the Podium project, so instead of using the ‘new’ button in the preset panel, try using the ‘new bank library preset’ in the track context menu.
ZynewaveKeymasterNevermind Frits, I’ve found the problem now
Ok. Maybe I should implement a warning-popup when a mapping has no connected device definition.
ZynewaveKeymasterwill 1.55 solve the problem alone
Yes
ZynewaveKeymaster‘plugin presets’ option isn’t showing at all, but it’s there for other tracks.
That’s weird. Could you email me a trimmed down version of your project file?
ZynewaveKeymasterI’m not able to store presets for the zPEQ.
Is the plugin editor visible in the track inspector?
‘plugin preset’ right-click menu options aren’t showing
You mean they are greyed out? This sounds like the plugin is not loaded. Are you sure that you have enabled monitoring?
ZynewaveKeymasterI’ve been in touch with Luxonix, and we have sorted out the problem. The latest LFX-1310 1.1.5 release introduced a change in the preset recall system, to fix a “total recall problem with VST-RTAS Adapter”. This unfortunately broke compatibility with Podium and possibly other hosts. I’ve now added an extra security call in Podiums preset recall procedure which fixes this. Hopefully this doesn’t break compatibility between Podium and other plugins. Will be released in version 1.55. Luxonix is also considering a revision of their preset recall system, which may appear in a future update.
ZynewaveKeymasterThe reason I was using the pencil tool to draw in a sound event is that if I didn’t do this the recording would just add to the previously recorded event instead of treating it as a seperate event
If you use punch-in it will create a new sound event at the punch-in position and not append to the previous event on the track.
ZynewaveKeymasterIs your arrangement using sample or bar/beat time resolution?
draw in a segment
Note sure what you mean with this. If you mean you draw a sound event with the pencil tool, then you don’t need to do this. Starting recording will automatically create the events.
If playback is started after the punch-in location, then the recording is not activated. Make sure you position the punch-in with quantize snap enabled.
ZynewaveKeymasterThe timeline segment you are trying to record should be highlighted in red if all is set up properly. If you are using punch-in then move it to the start of the segment you want to record.
ZynewaveKeymaster@Zynewave wrote:
but the cpu got stuck at 100% and i had to x then un-x the plugin and it was fine again.
This sounds like a denormal issue. Do you have a P4 processor?
I checked the code and my un-denormal protection code may have to be inserted a little sooner in the processing. Could I email you an updated zPEQ version so you can check if this fixes your problem?
Whoever designed the denormal number handling on Pentium processors, and deciding not to put in an option to disable it, should be rolled in tar and feathers 👿
There’s just no way to completely avoid denormals, without doing something that essentially degrades the sound quality, or eats up unnecessary CPU cycles. I’ll need to work a little longer on this.
ZynewaveKeymasterI’ve edited xis23 email address.
March 27, 2006 at 08:23 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterbut the cpu got stuck at 100% and i had to x then un-x the plugin and it was fine again.
This sounds like a denormal issue. Do you have a P4 processor?
I checked the code and my un-denormal protection code may have to be inserted a little sooner in the processing. Could I email you an updated zPEQ version so you can check if this fixes your problem?
ZynewaveKeymasterNow I found a problem. When setting up two tracks with insert instances of 1310, and storing a different library preset on each track, upon deactivation/reactivation of monitoring (to reload the plugins) they both were set to the same preset value, but still showing different preset names. It appears that the plugin is using some global data that spills over between the various instances. Soon after this occurred I managed to make the plugin perform an illegal action. It does not seem to be a healthy release. Could you revert to a previous version?
ZynewaveKeymasterI downloaded version 1_1_5 and so far I have found no problems with it. I did not have the previous version, so I cannot check preset compatibility between the two versions.