super_crunchy@darcyb62 wrote:
Again, after having installed it again, I still find it a bit confusing
http://www.zynewave.com/userfiles/ScamArtist/index.htm
Although this tutorial is almost a year old, it should hopefully help you come to grips with all the basics 8)
@darcyb62 wrote:
The 1st is how does Podium work with VSTIs that have multiple outputs? Tracktion dos this fairly well and I find it difficult to visualize how this works within Podium (honest though, I haven’t tried it yet).
When you import a multi output VSTis, all the outputs will appear as individual mappings in the list under the mapping tab (eg. DR-008 Output 1, DR-008 Output 2)
Whenever you want to use a new output, create a new track (in the latest version of Podium, released today, you can double-click in empty space below other track headers to create a new track). Then drag the required output mapping onto the new track
More info in the Podium Guide:
http://www.zynewave.com/guide/guide20_devices.htm#multi
@darcyb62 wrote:
How does Pdium handle time/tempo changes? Can I cop and paste these through the project?
If you look at the top of the arrangement editor, at the start of the timeline (bar 1) you’ll see a tempo marker. You can create new markers anywhere along the timeline in that horizontal space where the first marker appear (ie, anywhere to the right of that marker)
More info in the Guide:
http://www.zynewave.com/guide/guide32_arrangement.htm
@darcyb62 wrote:
Oh… one other thing….. I tried to do full scan/import of my vst folder and it locked up and crashed on Betabugs Spinbug vst. I temporarily renamed it and it went through the rest fine.
This doesn’t surprise me, as not every third party plugin is going to be stable when imported into Podium. I’ve had similar crashes in Tracktion when doing plugin scan 😉
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?
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_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_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
super_crunchya setting in the sequence/sound properties dialogs would be fine IMO
perhaps a user could first set the track colour in the track header (the way we do now) and all new sequences/sound clips would be coloured this way automatically. But, then the user can later change individual sequence/clip colours if they wish – which is what I would do.
Changing the track colour header again would probably overwrite all the sequence/sound colours across the whole track, logically, but the user can “undo” if they did this by mistake
super_crunchyemail sent to info [at] zynewave
thanks
super_crunchywhat about a drop down menu item on the headers in the mixer – “Centre track in arrangement editor” for example
right click to access drop down menu
super_crunchythe samplerate I use is 48Khz. I will email the project later, thanks
super_crunchyHi Acousmod
I have no problems bouncing any material, as I always Solo the tracks I’m bouncing the CPU never overloads. Bouncing is working just fine for me.
The problem is when I try to play back all the bounced tracks (which aren’t “whole” tracks as such, but bounced clips arrangement in different positions across the timeline).
When I try to bounce before the Master Out – the equivalent of “export track to WAV” in other hosts – all the other bounced tracks play back with audio dropouts which is then recorded into the master out WAV file.
I don’t think the plugin version of Bidule will help me, as by the time the audio reaches bidule it will already be dropping out (even though the dropouts are not present in the clips I am playing).
Thanks for the suggestion anyway 🙂
Just 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?
Thanks
super_crunchyFrits, can you recommend any workarounds for this problem? I’m trying to bounce the Master Out of this track, and as the audio keeps dropping out it is recorded in my master WAV file
thanks
super_crunchy@Zynewave wrote:
The 1.43 version did not include disk streaming optimizations. It had optimized audio streaming within the engine (i.e. after the audio has been streamed from disk).
I see now that I misread it. Looking forward to any disk streaming optimizations you make. I can see it benefiting not only people like myself who bounce audio to conserve CPU, but for artists who record instruments directly into Podium (in a band type situation, ie one track for guitar, one track for bass, multiple tracks for drums…) and need it to play back correctly.
super_crunchyHi Frits
After uninstalling Podium and doing tests with version 1.42 and 1.44, at various buffer sizes, I come to the conclusion that 1.42 is as badly effected as 1.44.
The first time I played back in 1.42 it seemed remarkably better, but with further testing found that it wasn’t – guess I had just been lucky that first time. When I used 1.42 at 512 samples it seemed to behave the best, but at other buffer sizes with version 1.42 it acted as badly as version 1.44 at all buffer sizes
super_crunchy@Zynewave wrote:
If the audio is recorded or editied, i.e. not saved to a wave file yet, then the audio is flushed to temporary files in the sound file cache folder (configured in the preferences dialog). You should make sure that this folder is located on your fast harddrive.
Can you make audio that *is* saved to wave also play from a folder on the hard drive? That would be great. Now I understand why, before closing a project, that the audio played back without droputs – because it would have been playing all the audio back from the cache folder on the hard drive. Is there any reason why this kind of playback couldn’t occur all the time, instead of caching to RAM? I know other apps let you toggle between RAM and disk streaming, and for all intensive purposes I would only ever stream single samples from RAM (eg drum hits), and the rest from HD.
@Zynewave wrote:
Did it always behave like this, or did this start with a certain release version?
It wasn’t always like this. I can’t tell you what version I started getting these huge dropouts, because I have just recently been getting many of my songs to a stage where I am arranging and need to bounce all the audio to save CPU (so I can then use more VST for mixing and FX). But, it was a more recent version I’m sure. Possibly the version 1.43 where you’d improved disk streaming?
I tell you what – I’ll download version 1.42 and see if it makes a difference
super_crunchywell said duncanparsons 🙂