Funny! I cast my vote. 🙂
Things like improved project/sound file handling (automatic sound ifle import etc.) is high on my list.
Good! Thanks. 8) Really looking forward to seeing that (when you are ready). 🙂
Have you successfully used the plugins in previous Podium versions, or is this the first time you try the plugins?
I tried scanning them in the previous version and still had a crash.
Please describe how it crashes. Does it show the “a plugin has performed an illegal action…” dialog?
No. It shows the scanning box and just stops at either of the two dll files for the plugins. Windows then pops up the “stopped working” prompt with options to check for a solution online or close the program.
Is the plugin put on Podiums quarantine list, and skipped during next scan?
This part surprised me. Usually if there is a problem with a plugin(very rare) Podium will put the plug on the quarantine list…and yes it should be skipped on the next scan but…not this time or with these plugs. They seem to scan and work well with Studio One and Sonar that is why I am bringing it up here. Possibly the dev did not test with Podium but maybe there is also a problem with scanning somehow.
I don’t seem to have a problem scanning other plugs Commercial or freebies in Podium so I am not sure what to make of this problem. :-k
Hi Frits, 🙂
I am having problems scanning these plugs in Podium 3.2.0…
I’m running Podium x64 on W7 x64. Podium will crash during the scan. Any suggestions?
@Conquistador: thanks – a little sagacity never goes amiss… 🙂
🙂 8) 🙂
over here Frits is talking about 3.1.3 and some new features which were requested by users …
but it’s strange that he does not speak up here ( at least until now )
I am guessing Frits wisely does not want to get into a needless fight / confrontation with his customers 😉
@The Telenator wrote:
Okay, but you’ve brought up a third common excuse now: This sacrifice and hardship nonsense. Look, all jobs are work, time, sacrifice, and I might add to that the fact that designing software is a heck of a lot better work (especially with no boss or no deadlines) than tonnes of other jobs out there.
So I don’t buy this sacrifice nonsense for one second. Let’s all get off this sanctimonious BS and get real here.
I can understand a need for more features as I have a list of my own but comments like yours above will not make Frits (or any dev want to respond positively if at all).Infinitoar may have a point. If Podium is aggravating you that much then why not take a break from it for a few weeks, months or even totally until it has the features you want?
Sorry to say but you really do sound the same as your other post on this forum with a link to a Cubase thread you posted on. You were quite upset on your way out of that forum /product and appear to be heading the same way here. Of course you are entitled to your opinion and to express it here. (I am not a mod) but the tone you are hitting will not help at all. 🙂
I think that is why Frits ignored this thread. I doubt any dev will want to respond to comments like this…
“Let’s all get off this sanctimonious BS and get real here.”
I really don’t blame Frits for not responding to this thread. It might be a harsh truth to accept but…
a. Frits is one developer and has a life outside of his development time with Podium that appears to have affected his release schedule for it. This can happen to anyone and will require you to be more patient. Maybe far more patient than you are willing to be with Podium.
I doubt anyone has an issue with that. We are all different and have choices beyond Podium for DAW’s. We all have timeframes for features we want to see and likely a limit as to when it is time to move on.
b. Maybe Reaper is better at this time for you. It is more feature rich and developed faster. Not perfect but no DAW is. You have to make sacrifices for any DAW here and there. You just seem desperately unhappy with Podium.
Looking at the current pace of development I cannot realistically see Frits meeting your requests for MIDI features as quickly as you (or even others ) might want. Personally I am not even interested in those features.
I would put…
a. Copying imported files automatically (an option) into a Project folder
..far above those MIDI features you mentioned. Which brings me to the issue of pleasing everyone all the time. Frits has a current roadmap (even if he has largely kept it to himself) and we just have to be patient and wait and see how he develops this DAW.
Really just take a break from Podium for a time or maybe another DAW is better for you. But some of your posts are very likely to decrease the chance of the features you want ever making their way into Podium any time soon IMO.
Sometimes a DAW just does not work out for a user. But don’t leave this forum the way you left the Cubase forum. That is not going to get the features you want in Podium, / make Frits any more likely to implement them.
Yes I would love a quicker dev schedule but if Frits can manage the current dev pace and Podium stays stable then I am happy with that. I would hate to see him rush features under pressure and things end up like the XT2 development issues that seemed to run for months on end. That was terrible.
It is slow going here. Maybe very. But if it is upsetting you that much…maybe a break from it all will help you get a new perspective on things and maybe lower your expectations a bit or just try something else. 🙂
Auto-backup is another major feature that I’m surprised to see no one has mentioned yet in this topic.
“Auto Backup” there you go it just got a mention. 🙂 Very useful feature IMO along with an option to copy any clip imported into a project please thanks. 🙂
Auto Backup IMO is not a reflection of any reliability or stability issues in Podium, but a reflection of the need to have that extra layer of Project back up as plugins can cause any host unexpected problems for a variety of reasons. 😉
Merry Christmas everyone! Enjoy the break 🙂
I have to say without a doubt on many occasions too numerous to mention, Frits has gone way beyond what I personally expected from him to accommodate user requests (mine included). Honestly he has to be one of the most responsive devs out there. It would get very messy indeed if promises were made and not kept.
Anyone would likely get upset if they are told x and y happens. It would not be a pleasant situation for the customer or dev promising such things. Better to leave things open ended IMO.
There may be less info on what is coming next or what areas will be worked on for certain but I think it is a far better thing to operate within the limits of your capabilities as a dev.
I have seen some forums where promises are made and not kept…it’s not a pretty sight. I personally prefer to have little or no info (if that is what the dev is comfortable with) and have my expectations at a reasonable level that matches the devs.
I think that will create a nice halfway house between the devs attempts to please as many customers as possible and the customers attempt to gauge what is coming next in a reasonable way.
This is just my 2 cents on the matter and my opinion only. Apologies in advance if it upsets anyone. I doubt it will frankly and would be surprised if it did but just in case. Peace 🙂
Not much time for testing at the moment but did run my previous test project briefly without issue at a very high CPU load (80-90%). Installation was fine. (x64)
I’ll give the 3.0 RC a test run today. 🙂
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. 🙂
You put it much clearer than i did in my second post on the topic. Maybe this will be the best solution, a neutral one, leaving this action to the user instead of automatically copying files.
The problem I would personally have with the manual approach is having to click on a right click command *every* time I import an audio file or even after a series of imports. I would much rather have Podium manage that instead with a simple option like this…
It’s likely Frits may be able to offer 2 options manual and auto copying. Might work best that way for all. 😉