Topic: Preview 2.43: Podium x64 (for 64-bit Windows)

Yes now at 90+ CPU here and it is still holding out. 🙂

Frits some observations…

When I wanted to drag in another instance of Omnisphere (Global instance) I got the Error message telling me it is already active on another track. I normally don’t use more than one global instance of say Omnisphere or Trilian but…for the sake of testing Px64 out, I thought I would try. I was a bit puzzled about this but of course there are up to three options that will give me what I want (right clicking on the mapping from the project page listing), it just depends what I want to see in a new plugin instance. 😉

At track level
The only problem I see with this at track level where the error will appear is that a new user will not likely figure out how to solve this problem themselves. I would suggest if possible to add a prompt or additional text to the error message that pops up in the arrangement view that might say…

“This mapping is already active on another track would you like to create a new instance?” With a simple OK / Cancel button option to choose from. Yes you can right click the instance in the inspector but…I was scratching my head for a bit. 😛 That additional text / prompt would snap in /lock the user experience in nicely. No need to sit wondering what that error means and or how to solve it :-k

A few other things…

1. The ZPEQ did not scan (after a previous successful scan) and crashed Podium but…when I attempted a re- scan there was no issue. I removed it from the quarantine list first. Works fine inside Podium.

2. I got a few messages about J – Bridge not being able to run as Podium is not being run as an admin. This popped up as a result…

“MLSemaphore…” I think is dev speak for “Yikes this code door needs to be closed asap?” 😀

Once I changed that (admin rights) there was no problem. Not seen that pop up since the admin change or any other warnings about J- Bridge. All in all…great work Frits 8)

“This mapping is already active on another track would you like to create a new instance?” With a simple OK / Cancel button option to choose from.

Well, I am one of those who scratched their heads for a decent amount of time trying to figure out how to work around this issue.

So a big +1

Peace

CC

64bit Podium 😯 8) 😀 😀

@creativeforge wrote:

@koalaboy wrote:

64bit Podium 😯 8) 😀 😀

OK, so translation please? 😉

That’s easy 😉

😯 – Wow, how did I miss this !!
8) – This is great news as I’ve been hoping for native 64bit podium for a while.
😀 – It runs my 64bit plugins nicely (limited testing)
😀 – It integrates nicely with jbridge for the remaining 32bit plugins.

What’s not to understand 😆

@Zynewave wrote:

Just a quick update on my progress:
To get with the times, I plan to change the version numbering for the next release. Using the version number 2.4.3 would cause a conflict when installing over the previous Podium release (2.42 is larger than 2.4.3), so I thought this would be a good time to bump up the version number to 3.0.0. Seems fitting with the introduction of the x64 version. I’m not planning to change the way I implement features and fixes bugs in the future, but with the x.x.x style I can indicate whether a release contains new major/minor features, or just maintenance/bug fixes. Any opinions on this?

I think with DAW’s a major number bump will draw in added expectation for features but with Podium and Reaper (for instance) that is not really the case. Even with Reaper 4 on the horizon the dev pace IMO for features and fixes is exactly the same as it was outside of the v.4 beta cycle over there.

Podium is similar in a way as a version number increase does not mean 100 new features. But x64 support is major IMO for Podium so bumping it up to 3.0 is not a bad idea if you want to do that. 🙂

Another cause for the delayed release, is that I’m setting up my new PC. I developed the previous Podium x64 betas on a borrowed laptop, but I’ve finally purchased myself a new Windows 7 x64, i7, 16GB RAM PC. I also purchased Kontakt 4, so that I’ll be able to fill up those 16GB of RAM 🙂

The speed increase is crazy eh? Have fun. :D/

I hope to have the release ready within a week. Still need to fix one remaining installer bug.

I would love to have had this x64 release months ago but as ever I am very happy to wait until you are happy to release it. The x64 addition of course will not be huge for everyone but for me it’s simply massive. 🙂

Im am envious now! 😉 On your system! Congrats!

I think Podium does not have to follow the rest of the DAW. If you feel like changing anything is fine, but don’t really feel you should do that because how the things are with the others.

On the other hand, changing now to 3.0.0 is a good time. I hope we’ll see x.X.x as often as possible! 😉

Best to you!