Another one is Texture, I bought it but I’ve never used it, so I don’t really miss it. Sign of the times though.
Yes it makes more sense to convert the sample rate of the file in most cases. Any free wave editor should be fine eg Audacity. MP4 files are trickier due to Apple proprietary format.
Zynewave Podium is still gold. It is still my most used DAW.
Because, it’s a pleasure to use.
It is probably the sample rate of the file being different to the sample rate of the project. Check the sample properties and adjust the project accordingly.
Thanks Levendis. That does solve some situations. Sometimes when using Podium I notice little things that could be consolidated to make the workflow a bit tighter. I post these on here as observations that might be adressed in future releases.
Thanks Levendis. I’m aware of those features, but was referring to assigning pre/post gain-pan-metering when right clicking on a channel. After setting any one of these the dialog box closes & then has to be re-opened to set another of these for the same channel. It would be more efficient to have the dialog box stay open so these can be set at once.
“Media files” is a broad term. Podium only uses wav/aif audio files.
also a sticky note icon for track headers that have information on the sticky note.
And, a “render selected tracks” as an alternative to
the “render all…” command.
ok, that’s 3.
Got it. Thanks Fritz. Am liking the new updates.
Erm…I can’t find the “Save As” button. As in for saving a new version of a project with a slightly different name or number. Am I missing the obvious? Any help welcome.
I have another (slightly off topic) feature suggestion for 3.3. Would it be possible to add an option for colour coding the track markers? i.e. verses are red, choruses are blue (I know I know there’s a song in there somewhere 😉), bridge yellow etc.
This would be immensely helpful when recording at a distance from the computer screen. I think that even if I had a young person’s eyes I would still struggle to read the markers from half way across the room, & it’s probably simple enough to code without taking time away from the main features of the update.
There are so many different ways of working within a DAW. I personally find samples to be overly static sounding, & avoid them for the most part in preference to “Romplers” which often provide round robin triggering, & allow for MIDI control.
I am specifically referring to rubato – not a tempo automation curve, but literally a section of time where the musical phrase is played in an interpretive free time. For instance, the song stops for a moment, a little lick is played in free time & followed by the beat/bars becoming “a tempo” at the end of that section, such that a MIDI drum clip could kick back in at that point. An automation curve for tempo would certainly be useful, but your previous solution is closer to the mark for this situation. Cheers ☺
Thanks Levendis. This is pretty much what I’m doing, & practically speaking, it works. Being somewhat “old school”, I actually rather like inventing workarounds. This was normal in the days before automation etc. The idea of just inserting a given amount of time in seconds, independent of bars & beats seems like a simple feature to implement, & certainly would find use in many genres. I wonder if it might be useful to survey Podium users to see how many people use strict bar/beat time & how many have a use for more organic time requirements. There are times when I’ve been producing,say, Hip Hop & it’s all tightly synchronized. Other times when I use Podium more like a digital tape machine with no adherence at all to the tempo grid.
Thanks Fritz. I tried Podium x86, and Sample Tank 2 is 32 bit only, but still no go. And I have a policy of not dithering about with complicated problematic software. One of the reasons I love Podium in fact. Most of the sounds in question are orchestral, so I’m using my ears to re-assign patches in Sample Tank 3, based on earlier mixes. But still welcome any solutions.