I can get a crash out of Podium with some of the older and flakier VSTs I’ve got. But I know that isn’t Podium’s fault.
I’m not quite sure what you want out of us, michi_mak. We’re not seeing Podium as being any more of a CPU hog than anything else. Nor are we in a position to see how your own system might be screwed up.
I made about two-dozen recordings with Podium Free on my old Pentium IV desktop comp. It worked fine. Podium actually worked better on that system than Acid Music Studio did, because it’s offline render bouncing doesn’t glitch when the CPU hits 100%.
For the stuff that’s actually on the roadmap, directly exporting FLACs and MP3s would definitely be of interest to me.
Podium is no worse a CPU hog than any other DAW I’ve used.
Whatever DAW you use, it’s just a fact of life that you have to organize big projects properly. You have to use group tracks to create sub-mixes. You have to bounce groups. You have to use aux busses for stuff like reverb. You have to record sound sources properly in the first place, so you can keep the processing you’ll need to a minimum.
It’s pretty basic stuff that most DAWs can handle. And Podium does a particularly good job of it.
but… teh shiny! 😆
Good old reliable XP 32 bit.
I don’t have reasons enough the justify upgrading.
Yeah. I used to think that too. Then I discovered how ridiculously cheap second hand computers are…
And that — at least as far as computers are concerned — second hand doesn’t mean old…
So this year I’ll be using a core i3 with 64-bit Windows 7. Although I’m still using the 32-bit version of Podium, because I still haven’t found replacements for all my old 32 bit plugins.
Sounds great.
I did notice, when I had the Reaper trial installed, that it turned up as an option for Rewire in Podium.
I might go and try the new version, though of course, I chose Podium over Reaper the first time around.
Okay. I just put one of my songs on the Podium soundcloud page.
I’m not a computer expert, and I don’t know what those three libraries actually do.
But I seriously doubt that Podium would be deleting libraries installed and used by other programs.
I had to read the wiki to wrap my head around the Inspector. And I’m still not 100% sure I understand some parts of it.
1.) On-board DITHERING.
I see that as a mastering thing. If I had to do mastering that really mattered (i.e. not just stuff to post on the internet), I’d be taking the output from Podium and sending it off to a proper mastering engineer.
2.) ON-SCREEN MIDI KEYBOARD.
It would be handy. Although the “keys” on the piano-roll editor are already playable with the mouse.
3.) PLUGINS OFF WHEN NO SOUND.
There’s an option in the preferences to turn off the plugins when you have a track muted.
I manage my CPU usage in Podium by using group tracks. For example, I usually have a drums group, a guitars group, a synths group, a vocals group, and an aux bus group. When the CPU load starts to creep up (which is almost always with my drums), I’ll bounce to the group track. That automatically mutes the tracks in the group and switches off all the plugins — neat.
4.) METRONOME PRE-COUNT.
Agreed. That would be handy.
5.) ONE-CLICK FULL IMPORT of FILES.
Yep. Although, I’ll probably end up doing it the hard way most of the time. If I’m using samples on a track, I’m generally previewing them before I’ve even loaded Podium, and I’ll copy them directly into my project folder.
I record tracks in huge numbers (averaging about 70 a year), and I’ve got my own little system going for how I like to keep things organized.
6.) Overall improvements to MIDI, namely full MIDI PLUGINS SUPPORT.
Yeah, I guess so.
I’ve used a plugin that outputs midi exactly once — an algorithmic music generator thingy, on a project where I was going out of my way to experiment with different plugins and recording techniques. On the whole, though, I much prefer to do all my own work. That’s one of my little foibles. So I’ll probably never need more out of midi than what Podium does now. But then, it’s not all about me, is it. 🙂