Looks the Rapture update solved the crashes with the plugin. :-k So far so good. 😉
Beta2 is uploaded. This zip file contains both an x86 and x64 version. New feature:
Added “Enable jBridge x86/x64 VST plugin wrapping” option to the preferences dialog. The jBridge third-party software can be used to load both 32-bit and 64-bit VST plugins when running Podium x86/x64 on a 64-bit Windows OS. Podium will detect if jBridge is installed, and invoke it when scanning and loading VST plugins that use a different processor architecture. It is not necessary to use the jBridger tool to create wrapped dll files.
The jBridge demo can be downloaded from:
@Conquistador wrote:
Looks the Rapture update solved the crashes with the plugin. :-k So far so good. 😉
Sounds great. Have you had a chance to evaluate whether there are any CPU performance differences between Podium x86 and x64?
After a very quick test…not noticing much difference CPU wise. I would think that is because a greater difference might be seen between Podium x86 on Windows x86 (any flavour) and Podium x64 running on a similar version / flavour of Windows but on x64 with the same project and (x64 native) plugs.
I am running Podium x86 and Podium x64 on the same OS (W7x64). That may be why there is not much difference. A percentage here or there either way is what I can see here.
For those having difficulties with MIDI Yoke on 64, I found LoopMIDI, runs fine on both 32 and 64 systems.
http://www.tobias-erichsen.de/loopMIDI.html It seems to be quicker than MIDI Yoke—
Not to sound impatient or a worrywart, but when do you expect the new version to come out? It’s been very quiet here the past few weeks-
@4mica wrote:
Not to sound impatient or a worrywart, but when do you expect the new version to come out? It’s been very quiet here the past few weeks-
I have completed the porting of zPEQ, zReverb and zPitch to x64. I need to test those a couple of days before I’ll post a new beta. The zPlugins have not been updated for years, so I also had to spend some time adjusting them for the latest version of the developer tool I am using for Podium. The good news is that this should make them more CPU efficient, and it will be easier for me to work on new zPlugins in the future.
Unfortunately I also have to spend some time looking for a new installer tool. The current installer I’m using does not support x64 distributions.
That’s great about the Zplugs – they were already decent on CPU to begin with. I tried looking up info on installer tools, but quickly learned that I don’t know what I’m doing. Good luck on all of it.
Beta3 is up. The zip contains 8 files. Podium.exe and the three zPlugins, in both x86 and x64 builds.
The Podium x86 build is not changed much compared to 2.42, but the three x86 plugins are now compiled using the same tool I’m using for Podium. I’m seeing perhaps 5% performance improvement in zPEQ. Haven’t tested performance on the other two. Please report if you notice any differences with the new zPlugin builds.
I’m done with the coding for 2.43, unless bugs appear. Now I only need to work on a new installer.
I compared my 2.42 with the x86 and x64 betas, in CPU. In all three, the Zeq stayed at 0%. The Zpitch was about 2% in all three. The Zreverb was a little different, hitting about 4% on 2.42, and 3-4% on the new x86 and x64, and 2% every so often. Opening the Zreverb GUI added about 2% in all three but the other plugs GUI made no difference.
They all run fine, so there ya go.
Beta 3 x64 testing….
I did have a crash with Geist…but I am yet to repro that after multiple efforts to reproduce the crash. But I will certainly let you know if I can reproduce it.
I am running a project (with native x64 plugs) that scales to about 30% of CPU but is running the Beta 3 x64 zPlugs, all three Spectrasonics plugs, Geist, Rapture, Z3ta+, Ozone 4, Sugabytes Turnado (add that to the list of tested x 64 plgus here), U-he Tyrell N6, AAS Ultra Analog, Inpdependence 2.5 e.t.c
I am basically trying to work far beyond the way I normally would to try and see if Podium will do something it should not. To be honest considering most devs are likely to test their plugs with the major (or better known hosts out there instead of Podium) hosts, it is quite an achievement that I can use Podium this way it can remain crash free.
So far so good here. I may have missed bugs that might appear in a different workflow but so far it appears pretty solid. Export / Render appears OK as well.
Pushing the project further up CPU wise to see what happens…
what is your PC config?
i7 920
RAM 12 GB
W7 x64
😉
Update…
Multiple Ozone 4 inserts with all six modules running on different tracks. I might try stacking them on the same tracks to see what happens 😛 Really…this is beyond what I would use Podium for. Hopefully more obvious things have not slipped through my testing net. With time permitting I cannot test everything but so far so good.
Pushing 70% CPU now…Podium is still holding up. Saving and tweaking during playback tweaking just dragged in Lounge Lizard… 😉
Might drag in a second instance of Omnisphere with 16 outputs and and 16 Midi inputs should I even be allowed to do that? 😆
Audio Clip volume adjustment, fades all holding up…realtime MIDI editing…all good.
Will try some automation….and push to 80% or 90% of CPU >gulp< 🙂
A little off-topic, yet this could add a tiny bit to the big picture…
Will try some automation….and push to 80% or 90% of CPU
I am using 2.40 Free and have two very big projects now, respectively with 65 and 82 tracks, and a ton of synths, VST effects and automations, both constantly residing in between 96-98% CPU…and without a single glitch, pop, clip, zip, freeze, artifacts during playback, or crashes in general. All runs amazingly smooth, and all this powered by only one CPU core 😯
So, I am pretty sure you will not encounter any issues in this regard, especially considering that it is a newer release and with the multicore support in the commercial version…the perspectives are bright.
Peace
CC