http://aycu14.webshots.com/image/33293/2000220174919125575_rs.jpg
If i click “add” i get the error:
http://aycu12.webshots.com/image/35011/2000201146490336358_rs.jpg
energyxt vsti version is 1.3.6
podium is 1.95
thnx
If I remember correctly, there should be a more resent version of eXT1 than 1.3.6. I would suggest updating eXT. There was a crash bug that Jørgen fixed in one of the latest eXT1 versions. Maybe this is the bug you experience. See discussion here:
yep, it’s kinda fixed, the new energyxt 2 vsti does not allow multiple audio outputs:(..
thnx anyway
another problem with multiple audio outputs
Let’s say i use one instrument (drum sampler) wich have 2 stereo outputs.
We send kick to ch 1+2 and snare to ch 3+4.
In podium we should create 2 stereo tracks and use one of them for feeding midi to the instrument, or create a 3rd one just for midi.
But if you want to solo one of this instrument outputs it also mutes the midi track, wich means no midi for the instrument. Is there a better way to do this ?
thnx again
But if you want to solo one of this instrument outputs it also mutes the midi track, wich means no midi for the instrument. Is there a better way to do this ?
If your drum sampler supports it, I think the easiest way would be to mute/solo the individual outputs in the sampler plugin editor. In Podium you will need to solo both the stereo output track and the MIDI track (or mute the other stereo output).
Yup, thats how i do it now, but is there planed any change with this?
IMHO Cubase way of importing multichannel instruments is the most logical to me, because most vstis start with a numer of channels wich is not the one u need, u always need more or less channels and this means the plugin need to be configured before loading into project.
Also manualy creating tracks for vsti’s is … is not automaticaly :D.
The workflow should be:
i add a new instrument
software should do:
-open the instrument so i can setup the number of outputs
-creates the instrument group track wich also contains midi data and is also bounce enabled in the same time (this way solo does not mute parent)
-creates the instrument tracks
-everybody is happy! 😀
thnx
edit: dynamicaly creation/deletion of tracks acording to vsti later setting would be great too, and would eliminate the first step
Yup, thats how i do it now, but is there planed any change with this?
Not in the near future. But at some point I’ll probably improve the way you add multi-mapping plugins to a set of tracks.
Frits,
Sorry to dredge this post up, but I was looking for an answer to a problem I have.
I experience this same crash that was mentioned in the original post (though I can’t see the screenshots, the way to produce it is the same).
I have the latest version of energyXT 1 before it ceased being worked on.
Some background. You can set the VSTi (or VST) to have multiple inputs and outputs by creating an .ini file with the same .dll name. So, if you copy an XT.dll to xt8.dll, then create an xt8.ini and insert some text in there, and put it in the Windows folder (such terrible practices :(, for programming), then you can create an energyXT VST that has, in this case, 16 mono inputs and 16 mono outputs (which is what I’ve done).
However, when loading this specific renamed VST .dll file in Podium and setting up the instance correctly (all global instance 1), it still opens with only one stereo input and one stereo output. And when I go to add an output, crash.
I am unsure if Podium is recognising the multiple outputs or inputs as I can’t connect anything more than the original output due to the crash. However, I did load this renamed .dll into VST Plugin Analyser and it does confirm as having 16 ins and 16 outs.
If it detects properly, and I am able to add outputs without it crashing, I wonder why Podium is crashing? Is there any insight you can give to this Frits?
My issue here is that I was relying on being able to use energyXT modularity and multiple ins and outs to perform a few things that I can’t within Podium itself, without having to use XT as a host. Currently I cannot due to this issue. Are there any other hosts I can try for free to see whether the issue is more likely Podium and the way it handles (presumably) VST inputs and outputs, or energyXT possibly doing something dodgy?
[edit]
My apologies 😳
I just tested again, and because I don’t distinguish between VST and VSTi (coming from working with modularity) I failed to realise what I was testing was inserting it as a source, and then adding outputs. Though, I still don’t see why it shouldn’t work. Perhaps because I was only telling the first instance that it could accept midi notes, but not the others?
Anyway, I inserted it on a track as FX, which is where I probably wanted it anyway, and it worked. So I apologise for that. My brain still just thinks of things modularly.