Helpful Replybussing issue

Author
Post
Essentials Only Full Version
Vokalzz
Max Output Level: -89 dBFS
  • Total Posts : 87
  • Joined: 2013/07/27 18:29:40
  • Status: offline
2013/12/12 01:41:02 (permalink)

bussing issue

I have two guitar tracks (pan hard left and hard right) and record a dry signal. This way I can open up pod farm and experiment with different sounds for guitar. I then find my tone and want to apply it to both tracks. So instead of opening up pod farm on both tracks, I decide to create a bus to save on cpu. This way both tracks will have the same sound/effects ect. When I do that, I find that that panning is messed up, Also, The original tone is different then when pod farm was applied to both individual tracks.
 
Some one please help/ I'm sure its a simple fix but am at a loss on how to maintain the original tone and panning while using a bus.
 
Thanks to al that can help.
#1
List Solutions Only

3 Replies Related Threads
    Bristol_Jonesey
    Max Output Level: 0 dBFS
    • Total Posts : 16775
    • Joined: 2007/10/08 15:41:17
    • Location: Bristol, UK
    • Status: offline
    Re: bussing issue 2013/12/12 03:49:55 (permalink) ☄ Helpfulby Vokalzz 2013/12/13 05:34:22
    I'm pretty sure Pod Farm will simply see your 2 guitar signals as mono in / stereo out, so there's no way it can retain the original panning.
     
    I would definitely apply a separate instance of PF to each track individually. This might  or might not cause system issues, but nobody here can help you with this unless you post your system specs. CPU, RAM, OS etc.
     
    If it does cause problems, you can always freeze the track after the event, removing Pod Farm from the equation

    CbB, Platinum, 64 bit throughout
    Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
    #2
    Vokalzz
    Max Output Level: -89 dBFS
    • Total Posts : 87
    • Joined: 2013/07/27 18:29:40
    • Status: offline
    Re: bussing issue 2013/12/13 05:52:25 (permalink)
    System specs.
     
    i 5 intell processor, 8GB ram, windows 7, 650 watt power, 1 Tb hard drive.
     
    I am getting crackling and popping on the track. I believe it is because I have so many instances of pod farm running at once.
    This is how many tracks I have so far that have pod farm plug in on individual tracks.
     
    Bass - 2 tracks, 2 pod farm plug in
    Guitar-
    Intro- 4 guitars tracks, 4 pod farm plug in
    verse- 3 guitars tracks, 3 pod farm plug in
    chorus- 8 guitar tracks, 8 pod farm plug in
    outro- 2 guitar tracks, 2 pod farm lpug in
     
    When you add all tracks together that adds up to 19 pod farm plug in that are simultaneously working together. That doesn't include other plug ins like reverb, delay, percusions strip, vocal strip ect. , that are also working in conjunction.
     
    If i delete the guitar track folder with all guitars tracks, the cracking and popping goes away. So, I deduce the issue would be because of so many pod farm plug ins playing together simultaneously. So, it would be nice to condense the plug ins if possible. 
    If I cant, then would you recommend me upgrading to 8 more gigs of ram, that would make a total of 16 gb of ram on my computer. My motherboard can handle up to 16 gb so it is possible. I will be working with pod farm for the whole album i am recording so making this work or finding a work around is essential.
     
    Also, what exactly does freezing a particular track do?
     
    Thank you very much for your help and patience Bristol. You always have great responses.  I really appreciate it.
     
     
     
     
    #3
    Bristol_Jonesey
    Max Output Level: 0 dBFS
    • Total Posts : 16775
    • Joined: 2007/10/08 15:41:17
    • Location: Bristol, UK
    • Status: offline
    Re: bussing issue 2013/12/13 17:45:57 (permalink)
    19 is a lot - but I'm not entirely convinced that a system with 8Gb of RAM should introduce these problems.
    But as you say, if you delete them, the problem goes away, so try freezing a few tracks and see what happens.
     
    You can freeze track by either clicking the Snowflake icon, or by right clicking the track header and select Freeze
    Both options also give you access tot he Freeze options dialog where you can make a limited set of choices. The important one for you would be "Track Fx". This will print any Fx in the Fx bin and the Pro Channel and switch both off. This switch is not permanent - you can easily turn the Pro Channel back on and also un-bypass the Fx bin. You would need to be careful here as this would "double up" the Fx. It does of course reduce CPU load as well as release more RAM to the system.
     
    You can easily monitor the amount of RAM your system is using in the Performance Module in the Control Bar.You should see it teadily reducing as you freeze more & more tracks with Pod Farm on them.
     
     
    One possible suggestion to get around this is to use fewer instances of PF but have them on a bus rather than individual tracks, where you can set up sends from tracks with similar processing to the bus. In this case, set your track outputs to none so that you don't get a blend of processed and unprocessed tracks

    CbB, Platinum, 64 bit throughout
    Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
    #4
    Jump to:
    © 2025 APG vNext Commercial Version 5.1