ZynewaveI’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.
ZynewaveThe 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.
ZynewaveIs 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.
ZynewaveThe 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.
Zynewave@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.
ZynewaveI’ve edited xis23 email address.
ZynewaveZynewavebut 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?
ZynewaveNow 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?
ZynewaveI 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.
Zynewavei use an audigy 2. which out puts do i realy need?
I don’t know. Probably the first mapping in the list is the main stereo out. If this is the one you use on your master track, then that is the only one you need. For the inputs there may be more mappings required, depending on whether you use microphone or line input, mono or stereo etc.
Zynewaveso is the 1+2 a multi out plugin then as wel as a stereo out?
Yes. All the microtonic mappings you see in the map panel refer to the same plugin instance. The mappings are a way to extract the proper audio channels from the multiple channel output of the plugin. To apply different effect plugins to different drum sounds, you set up tracks with the 1+2, and 3+4 etc. mappings. Then you wrap each of these tracks with a group track assigned with the desired effect plugin. Also remember to select which output each drum sound will use in the microtonic editor.
ZynewaveThese mappings are created based on information from your soundcard driver. First thing to do is to disable all the channels you don’t want to use in the interfaces dialog. Creating a new project with the wizard will then only create mappings for the enabled channels. If you already have created your project, then you can delete the unneeded mappings either in the project browser or the list panel. Look inside the ‘devices’ folder.
ZynewaveThese are probably multiple outputs. The older microtonic version only had two stereo outs. The newer version apparently has more. If you don’t assign sounds to other than the first output within microtonic, then all you need to use is the 1+2 mapping.