bfloyd6969's Forum Page

@druid wrote:

I do not wish to sidetrack too much, so my apologies in advance, but you should seriously look at energyXT 1.41. If you’re into Reaper or Podium, I’d recommend looking at the VST version. It allows more easy routing of signals. I basically use Podium as a track and MIDI editor, and all my VSTs and routing goes on inside energyXT VSTs. It’s pretty flexible. And the first version (VST) is more stable than the second.

Anyway yeah, more info on not being able to reload would be good!

Heh, I found v1.4. to be much better than v2.5 too. I was just going to use 1.4 and call it good but then got to thinking that I would like to use a DAW that had a good continuous developement going on and I didn’t see that in XT (obviously). I still have the vst version of 1.4.

@Zynewave wrote:

@bfloyd6969 wrote:

Hi Fritz, I tried the tasks you mentioned and the delay is still there. I also tried as others mentioned by checking my anti-virus and all is good there. I don’t know why I’m getting this. Could this be from being in demo mode? Should I try a re-install due to a possible bad .ini?

This should not be an issue of the demo version, and it should not be necessary to do a reinstall.

As suggested in the posts above, please try to temporarily disable your virus/spyware tools, and check if this affects the delay when opening and closing Podium.

Thanks Fritz, will do.

You’ve been a great help to me Druid. In regards to item 1 – I found what was causing this to happen. In the very beginning of an automation event is an already inserted node (very small and very hard to see if you’re not looking for it). I created nodes additional to this and was using those. Everytime the automation was over it would default back to that original (almost hidden) node. Once I set that to the value I wanted to be default all was well again :)!!

Yeah, eXT just crashed way too much for me, and this is when I was just using the native plugs. If a native plug causes crashes I hate to think what 3rd party plugs do 😯

@druid wrote:

You’re used to how energyXT does it, clearly. 🙂

Podium is .. er .. a little different than that, at least visibly.

If you WANT to use the different outputs, you must use each stereo pair as a DIFFERENT VST instrument.

Now, this is going to sound weird, and there might be a better way to do it, but here’s how I’ve done it so far:

I usually create a group, called percussion or drums or whatever. Within that I create three tracks, one for outputs 1+2, one for 3+4 and one for 5+6. I then also put it’s VSTi output to those channels (in my case Drumatic 3 1+2 for the first one, Drumatic 3 3+4 for the second, so on). I then can either create MIDI parts on each of those lines just for those outputs, or I can just use one of them. Let’s say 1+2 is for kick, 3+4 snare and 5+6 hats. In one of my tracks, I have got ALL MIDI just on the kick’s (1+2’s) MIDI lane. However, I have the other two in that group with no MIDI parts in order for it to play through those channels, and also so I can adjust their volume from the mixer.

I know it sounds weird. But anyway, even if all your MIDI is all on the one lane, each sound will route to where it was told to in the plugin. But you MUST have tracks for each output you want to use, even if there is no MIDI in some of those tracks.

Depending on your needs, you can also do what I do in other songs, which is to say, use energyXT 1.41 as a VSTi, and then have all the routing you need in there, and treat as a collected unit when output back through Podium.

Hope that helps.

Thanks Druid, and it does help. Actually, I am used to the way Reaper does it (I never really got that far into eXT before I decided I didn’t like it anymore). In Reaper I could put VirtuaDrum on a single track. Inside of that tracks FX editor, I could choose the pin connectors and select them all to have all the multi channels playing on the same single track. In other words I could assign channels 1&2, 3&4, 5&6 to all sound on just channel 1 and still be in stereo. This could be an abnormal way to do it but it was the only way I knew how until now. I do like the idea of being able to have more control over each individual drum for fx purposes:).

Thanks again Fritz. Yes, Podium created two versions of VirtuaDrum for me. One is a regular stereo version and then there are several sub version each for channels 1&2, 3&4, etc. When I selected the stereo version I could only get channels 1&2 to sound and not the others. I need to change the plugin connectors to allow the other channels to be heard on output but I don’t know where that is… Thanks.

Thanks for the tip. I’m using Nod 32 but never had this problem with any other apps. 4~5 seconds I could live with but I’m more like 45 seconds. I’ll have to check the things that Fritz mentioned. Thanks again.

@Zynewave wrote:

Closing should not take this long.

Were you saving the project when the delay occured?

Please try these things before closing Podium and check which step is the cause for the delay:

Switch off the power button in your arrangement. It could be the unloading of plugins that takes time.

Select “new project” from the project menu, to remove your current project from memory.

Now exit Podium. Still a long delay?

Thanks for the quick reply. I’m at work now so I can’t check the above mentioned yet – however, I do remember that I also tried checking the closing time again after I first opened Podium. The start up page opened first as always and I tried closing before doing anything else. Again there was this same delay.

I didn’t think I could save in the demo mode so I didn’t try that.