Infinitoar.
InfinitoarI’ll get to the point, don’t want this to sound “emotional”.
-Equips track with Kontakt[the demo version]
-Loads 3rd party library in Kontakt
-Does “composer note editing, double clicking, making notes, harmonies, and whatnot”.
-Equips the track with zReverb[which I have to admit is the BEST reverb plugin I have ever used thus far]
-Is satisfied with the sound the track creates, bounces track
-Bypasses both Kontakt and the zReverb[once bouncing is done of course], plays track but only the bounced Kontakt library plays with “no” zReverb. However if I un-bypass the zReverb, of course it echoes.
Is this Podium Free 2.40’s fault or zReverb’s fault? I pretty sure it’s not the projects fault or Kontakt’s fault.
My only solution[which I am about to try in a bit], make a new track, put Kontakt on it, make the box again, paste the midi notes in the box, put zReverb on the track, load the same library, and bounce to see if it’s the tracks overall fault. If this fails, I will then use Bionic Delay to see if it does it still.
But also when I use KORE Player FX, it does it also[not bouncing the effect of the effect plugin], so if at all Zynewave if this is a noticeable issue do you have a overall estimate of when this can be patched? If not soon, then of course “no rush”, I will just work forward until the issue is dealt with then go back and try what I’ve done.
Also is there a way I can have 2.37 back, IF the issue cannot be resolved soon?[A part of me feels very stupid for not keeping the program…]
Thank you for your time Frits, and to those who take the time to answer this.
ZynewaveOnce you have bounced a track the first time, any subsequent effects you add will be inserted after the bounce point. Check that the bounce selector is placed after (i.e. above) the zReverb plugin in the effect chain. If not, just drag the bounce button above the zReverb and redo the bounce.
Btw. you won’t gain anything by bypassing effects that are bounced. Once bounce playback is activated, any plugins that are below the bounce point in the chain are automatically bypassed/muted. You can enable the “unload plugins when bounced” option, if you furthermore want the plugins to be removed from memory when they are bounced.
InfinitoarSorry Zynewave I’ve already figured it out. But thank you for the feedback. I noticed the bounce option was “between” the zReverb Plugin and the Kontakt plugin, so in other words it only bounced the Kontakt plugin. So what I did was just move the bounce option up top and rebounced and it worked fine.
Also not to prove your “wrong” but-
After you’ve bounced a track Podium Free it still uses the active plugin and effects. It does “not” automatically bypass or “mute” any processes from the plugin “unless” you “bypass” the plugin after rendering[or bouncing] the track. This saves a lot of RAM and CPU usage and I discovered this using REAPER by accident.
Most of my projects consist of more than 20 or 30 tracks within each project. And if you do not bypass effects and plugins after rendering them, then the use of the non-bypassed plugin and effects are still being used, not just the “.wav or bounced” file. And KORE FX uses a lot of RAM and CPU, and after I’ve bounced a track and have not bypassed KORE and KORE FX the usage of the CPU and RAM is still clocked “up”.[nearly “machinegunning” at 90-100%] However if I bypass these plugins/effects the CPU is “greatly” decreased in usage and of course only uses the created bounced file.[which seems to nearly take “any” CPU/RAM]
For example my recently created song “Hope”. If not bypassed “with” bounced tracks uses almost 100% of my CPU. If I bypass all tracks that have been bounced it only uses[so far] a max of 2% in the CPU/RAM indicator. And rarely redlines.
Now if there is a option to only play bounced files, and then the tracks “with” bounced files are automatically “fully bypassed”, then I would not mind doing that. But so far I haven’t dabbed in the Preferences too much to see if there is a option of such.[maybe i overlooked it]
Thank you for your time and explanation Zynewave. Sorry if I did not post sooner explaining I have figured my issue out.[after figuring it out, I immediately started working on the project non-stop.] And still congratulations on the “z” plugins, because they are without a doubt, very impressive plugins, with useful features and presets. I am happy to have them in Podium’s possession.
druidHi Infinitoar.
Have you right-clicked the track, gone the bounce submenu and enabled “Unload Plugins when Bounced”?
I did some brief testing and CPU usage appears to reduce, from 34% to around 7-10%, however this is in a simple setup with two tracks, one with only samples and the other with a drum synth and distortion on high quality settings.
Are you using this option?
I tested by rendering then deleting the effects from the project, and it resulted in the same CPU usage.
I also tried with and without that option, but I seem to get the same results, so I’m not sure if the option does anything in my simple test. I tried enabling the unloading of plugins, but when I moved the bounce down in the list of FX, it still used the FX, so again, I’m not sure if the option actually does anythiing.
Still, if you haven’t tried that option, give that a go and see what happens. Might need further help from Frits on this one… If I weren’t working today, I would’ve loaded a proper project and tested it, sorry!
InfinitoarHey Druid,
Well I ran a bit of some tests on my own, and I was wrong and right about some things, I’ll just list them, hopefully it makes a bit more sense…
-I still have Podium Free on my old PC single core rig, but I also have 4GB of RAM[?], or 3GB on it, so I loaded and old remix I did that used a lot of Synths and Native Instrument plugins.[Note: The more I use N.I. plugins, I think the more “possessive” they become..*laughs*]
-After I loaded the project, I then proceeded to use every Kontakt Library and Kore Player Preset that spikes up CPU and RAM usage.
-After messing around a bit, I came to the quick conclusion that it just may save more on CPU usage than RAM.[although RAM usage is still used less] Sadly my new PC has 2GB of RAM and my old one has 3GB or 4. Now I could be wrong entirely, but so far whenever I click bypass on plugins it greatly decreases CPU usage and helps my workflow. RAM usage however spikes “sometimes” if the project has been stationary for a while. I suppose it’s a thing with like starting up a car in the winter, you know, Podium needs to warm up and load all of the now “.wav” files so it can run them all smoothly.
And another great discovery I found out that surprised me.
If you have a .MP3 file and you have it saved in, let’s say, “My Documents”. Ok your done with your mix and you export it to a sound file and then you select an already .MP3 file. It says the “overwrite” prompt warning, of course let’s say you click, “Yes”.
It “literally” overwrites the old .MP3 with a “NEW”[?] .MP3??? In other words did Podium render a new .MP3, or did Windows somehow do it? It doesn’t also matter how big the file was[of course] just that if you click the file and overwrite it, it renders a new .MP3. I think that was pretty good and cool. But of course I know everyone just wants the .MP3 export but I thought that would be a good discovery to mention. As long as the file has the same name and .MP3 format, you can overwrite it, and it still be a .MP3.
Well off to remixing this song…or mixing my own material.
Zynewave@Infinitoar wrote:
If you have a .MP3 file and you have it saved in, let’s say, “My Documents”. Ok your done with your mix and you export it to a sound file and then you select an already .MP3 file. It says the “overwrite” prompt warning, of course let’s say you click, “Yes”.
It “literally” overwrites the old .MP3 with a “NEW”[?] .MP3??? In other words did Podium render a new .MP3, or did Windows somehow do it?
Podium does not render to mp3. If it is overwritten, then your mp3 file is likely now transformed into a wav file, but with an mp3 file extension. Check the file-size, or the file properties in explorer, and you’ll likely see it is now a wav file.
druidInfinitoar: I didn’t look at the RAM. I’ll make a note of it to do tomorrow as I have a 12 hour work day today, starting very shortly. I’ve never paid attention because I’m not a large sample user, but I’ll find a large library and see if I can free up RAM or not using freeze.
I would like to say however that disabling a plugin from using CPU, then re-enabling it, wouldn’t take much time. However, “removing” (more like just not remembering the address and freeing the space) plugins from memory, and then placing them back, would be like reloading them again. With large sample libraries, it would take considerable time.
I think freeze has more benefit saving CPU, however, than RAM. I don’t think RAM would halt up the DAW as much as CPU if running low.
RAM is also cheap, depending on a person’s budget! 😉 And can easily be installed. My opinion is that your new computer shouldn’t have 2gb, not even if it’s a laptop. Unless it’s still running Windows XP.
As for the .mp3, I’m not sure how knowledgeable or not you are with computers, so I’ll quickly mention that filenames can have periods [.] in them. The problem with this is that some programs will assume the last period in the file name you type, or click on, is the the one after which the extension comes (.mp3, .wav, .hottoastforbreakfast). Other programs just take whatever you type there, and then add the appropriate extension, unless it’s the same as in the file.
So, in those programs, if in the file box it was saved as “scream.mp3” but the file was saved as .wav, then it would become “scream.mp3.wav” with a fiilename “scream.mp3” and filetype of “.wav”. If you don’t show file extensions (and this is why I hate this feeature) then it hides the last part, so some would only see “scream” change to “scream.mp3” and they might think it’s still an .mp3.
Hopefully you didn’t already know that, or else you might feel like I’m talking to you like a child! Better be safe than sorry, though! 🙂
druidI just tried it, and as I expected, memory usage did not go down when bounce was used. I can only assume this is deliberate; with large sample banks, even if you wanted to change one knob within the VSTi, if the plugin (and its samples) were removed from memory, re-enabling it (unbouncing) would take considerable time to load, all for one tweak.
I’m not sure if I think it’s better to unload from memory or not.
I did notice my CPU usage go down, so I know bounce was enabled as the program intended.
I really would, even if bounce freed memory up, recommend getting more RAM! Modern systems with modern OS and modern software (the newer sample sets, let’s face it, also expect lots of RAM to work with) really work better with more RAM. CPU power is much harder to come by than RAM is.
Not a lecture, only a recommendation! I hope you can sort your problem out!
InfinitoarDruid
I think if I get this job[if I’m lucky enough] I will get for starters 4GB on my Windows XP 32bit Professional System, and then eventually get Win7 64bit because I lam quite fond of Win7. But of course I would need to save money, which I am good at. But life still rolls on with bills and such, so I am sure I can find a way.
Once I buy the RAM I WILL buy the full version of Podium. It’s been bugging me to buy it,[subconsciously] and I think it’s worth it.
I have another concern but I will post another topic.