Podianer.
super_crunchyemail sent to info [at] zynewave
thanks
acousmodjust out of interest, can you explain how you would use Bidule to record the output of say a VST instrument playing a midi sequence in Podium? Would you insert it on a group track and press record in Bidule?
Yes, just insert on a higher level track, this is the magic of Podium 🙂
super_crunchyjust for your info, a plugin that will allow you to record in this way (without all the extra “setting up” that seems to be involved inside the Bidule window) is SilverSpike TapeIt 2
http://www.silverspike.com/?Products:TapeIt
I own a copy of it, and used it heavily before I used Podium with it’s excellent bounce feature.
But as I said before, even if I use TapeIt or Bidule I will still be recording audio dropouts because I’m playing back previously bounced audio, and it’s during playback that I’m getting dropouts.
But maybe TapeIt 2 would be helpful for you acousmod? 🙂 Bidule looks like it takes a bit of time to set up, from what I’ve seen so far. TapeIt 2 is really quick to use
acousmodBut maybe TapeIt 2 would be helpful for you acousmod? Smile Bidule looks like it takes a bit of time to set up, from what I’ve seen so far. TapeIt 2 is really quick to use
Thank you, I know Tape iT too, but I needed to record a 16 channels file…
Your problem is really very strange.
Could it be related to the place where the files are stored ?
For example the files used in your project on a partition, and the ones which are bounced on another ?
ZynewaveI took your project file and relinked your sounds to wavefiles on my HD. I experienced no dropouts, but I do not have the plugins installed that you’re using. I removed the plugin mappings to get the audio to go through to the master.
Suggestion: Make an experimental copy of your project, and remove inactive tracks (i.e. those that you have bounce recorded), and see if this improves the dropout problem.
super_crunchyOK Frits, thanks I’ll try experimenting to see if I can find out which plugin(s) might be causing problems
It may be some mixing effects that are causing the problem. Cheers
super_crunchyHi Frits
On your suggestion, I made an experimental project. I first tried removing certain plugins to see if any were causing the problem, and sure enough it was an instance of FXpansion DR-008 that was causing it. It may have been a combination of the midi programming and the patch itself, as I don’t think I’ve had this problem with it before. Regardless, I normally use FXpansion Guru (as you know) and DR-008 was used in this older project that I was finishing off, so I’ll definitely just be using Guru in the future.
PS With Dr-008 removed I still get some very minor audio dropouts, which I’m sure your future disk streaming optimisation will fix. Until then, I mayb just mix down into more sub groups so that less WAV files have to play back at once. Not such a big deal 8)
Thanks for pointing me in the right direction. In the future I’ll try to remember to check if plugins are offending first before asking you why podium is acting up.
super_crunchyI have one more question Frits. If I have an offending plugin both muted and bypassed (inactive), is it safe to assume that it will have no affect on audio playback on active tracks?
ZynewaveIf I have an offending plugin both muted and bypassed (inactive), is it safe to assume that it will have no affect on audio playback on active tracks?
Not necessarily. The plugin is still receiving idle messages from the host, which potentially can use up CPU. To be sure that it is not affecting playback, you could use the ‘unload plugins when bounce is activated’ track option.
Btw. maybe the problem with Dr-008 was that it used a lot of memory for samples, which left less for Podiums audio tracks. The ‘unload plugins…’ would help with that.
super_crunchyI’ve removed DR-008 from the curent project after bouncing
As I’m still getting minor audio dropouts with 512MB ram, I’m going to upgrade. Going to upgrade to 1.5GB RAM (an extra 1gb) so I don’t run into any more problems… this should be considerably more than I should need, shouldn’t it? (Translation: will my arse be covered?)
I suppose it depends on how many tracks I have running in project…
For anyone who uses many tracks of audio, bounced at 32bit with higher than 44100Hz sample rate, what amount of RAM are you finding sufficient?
Cheers
ZynewaveGoing to upgrade to 1.5GB RAM (an extra 1gb) so I don’t run into any more problems… this should be considerably more than I should need, shouldn’t it?
That should be plenty. Until a few months ago I was using a laptop with 512 MB. Adding more memory does not necessarily mean that the dropouts will disappear, the first time you play through an arrangement. The extra memory will mean that the loaded audio is cached in memory, so a second play should reduce occurrence of dropouts.
super_crunchyI’ve got 1GB more RAM coming my way soon… will let you know what kind of improvements I get from this. It might even reduce audio dropouts altogether 8)
super_crunchyExtra RAM should also help plugins to perform better. Is this correct, or does it depend on the plugin? Sorry, this area is unknown to me
Edit: I already know it will help plugins like samplers that load samples into RAM, but what about VST instruments and effects?
acousmodAs I have seen since many years, the quantity of RAM is not so important with audio, except of course for samplers that do not perform direct-to-disc.
More RAM makes faster multistasking, video compositing or 3D graphics, but for audio it is better to use only application at one time, and most of the audio is processed in streaming.
I suppose this it is why the last improvements in Podium’s internal audio streaming gives an impressive improvement of audio performances with plugins, without having added more RAM…
Plugins by themselves need RAM to load and operate, but I think that vendors use the RAM argument as the response for every problem, but is rarely the real cause for audio.
The cache size seems to be more important for realtime processing, and it is certainly one reason why Centrino CPU with a 2 Mb cache are so fast with audio plugins compared to P4 CPU.
ConquistadorOk…I have had audio dropouts before but now they are back again. When I play the project back it appears to play further each time before the audio stutters and then drops in and out.
The strange thing is the CPU meter does not budge when this happens but the GUI does become unresponsive at times during dropouts.
I pretty much ignored it the first few times I came across it some weeks ago but now it just will not go away.
I really have to get to the bottom of this as there is little I can do with Podium like this. I really hope this is down to user error on my part.
Project file has been sent Frits.
Thanks in advance.