Trouble Running BBC SO?

Comments

31 comments

  • Ben

    Hi Fenton, we'll get back to your support ticket, do not worry. It is a little backed up during this busy time, but we never leave a support ticket knowingly unanswered.

    0
    Comment actions Permalink
  • Steve Bryson

    I've been having similar problems with Logic Pro X and BBC SO using the hybrid template.  Once I got beyond 6 tracks I started losing notes in the highest number tracks during playback.  I increased the preload buffer to 50000 and no longer get lost notes.  (I tried increasing it to the max 1000000 but that blew out my memory.)  We'll see what happens as I add tracks.

    The lost track problem did not occur during bounces, but that doesn't help when creating the music.

    2009 mac pro flashed to 2010 firmware (5,1), 2 x 3.46 GHz 6-Core Intel Xeon, 96 GB Ram, MacOS 10.14.6 Mojave.  BBC SO and OS resident on separate SSDs.

    0
    Comment actions Permalink
  • Javier Gonzalez Garces

    I don't know if it is related, but I think the plugin has issues (at least in Windows 10 pro, x64) because all instances are using a single CPU core rather than being distributed among all of them.


    This is a screenshot of my CPU usage (studio one 4) after playing a section, which means that when I load multiple mics I get lots of dropouts too :(

    0
    Comment actions Permalink
  • Steve Bryson

    Interesting, Javier.  On MacOS it seems to be properly parallelized, with all processors firing about equally when I run many tracks.  I think in my case it's an issue of memory bandwidth.  My 2009 (hacked to act like a 2010) mac pro memory is 1333 MHz DDR3, which is a little low by modern standards.  

    0
    Comment actions Permalink
  • Bastien Agussol

    I'm having issues too with BBC SO. I've made a Logic session with 28 BBC instruments, playing fine without any problem. Close the session, return the next day and half of the BBC instruments didn't want to play. 

    I noticed a extreme Memory usage with BBC SO. I use a 2018 Mac mini with 6 Core i7 and 32Go of RAM, BBC SO on spitfire SSD. No problem with another library on Kontakt (lot of heavy sessions with 56+ tracks).

    I didn't notice any CPU overusage, but definitely RAM usage issue. I've seen some Mac users with iMac pro and 64Go of RAM having the same issue, so I hope it could be resolved soon with an update.

    The BBC SO sounds great, but it will be unusable and very frustrating if I can't handle more than 5 instances in a session...

    0
    Comment actions Permalink
  • Steve Bryson

    Update: My project now has all 22 tracks in place, and with the preload buffer set to 50,000 samples I still have no problems (see my first comment for my system configuration).  In this case the sample memory footprint is 16.7 GB.  I'm using the spitfire hybrid template, so many of those tracks have many articulations.

    I did some experimenting: with the preload buffer set to 40,000 I still have no dropouts and a sample memory takes 13.3 GB.  With the preload buffer set to 30,000 I start to have dropouts and the sample memory takes 10.0 GB.  

    I made a version of the project removing all unused articulations (I currently only use one or two articulations on any track with one exception that uses three articulations), but that didn't really help: even though the memory footprint is much smaller I still had dropouts with the preload buffer set to 30,000.  I also observed that in this case with the preload buffer set to 50,000 I load 22.2 GB of samples, which tells me that some samples are way larger than others.  Apparently when I preload only the articulations I use I get larger samples.  So finding the best settings for a project will probably involve trial and error.

    A couple more things I learned: a) give the preload buffer time to load, which can take a couple minutes.  My project is unplayable until that is complete.  b) Mac OS X starts paging out memory when half of the physical memory is used, and once that happens playing the project in logic becomes impossible (though bouncing still works fine).

    But once I figured out the preload buffer, I'm finding BBC SO to be absolutely fantastic!  My project sounds great even though I have not finished refining the expression and articulations.

    0
    Comment actions Permalink
  • Steve Bryson

    Update: after installing today's BBCSO update (v1.0.5) and optimizing the samples, I now have no dropouts when I set the preload buffer to 20,000 samples, which is a big improvement.  This has a memory footprint of 6.7 GB.  I do, however, still get dropouts when the preload buffer is set to the default value of 12,288.  I'll probably keep the preload buffer set to 30,000 samples.

    0
    Comment actions Permalink
  • mj mynarski

    Steve Bryson - Thank you for the info in this thread.

    Early in the thread you mention a Logic hybrid template.  Is this something you created or have I missed something that's part of Spitfire/BBCSO?  

    Cheers

     

    0
    Comment actions Permalink
  • Steve Bryson

    Hi mj - the template is from https://www.spitfireaudiothepage.com.  That whole page is worth looking at, including the videos.

    Cheers

    0
    Comment actions Permalink
  • mj mynarski

    Steve Bryson - Much obliged.  Thank you.

     

    Cheers

    0
    Comment actions Permalink
  • Rupert Smith

    Hi,

    Very helpful posts above. For what its worth I am also experiencing lots of problems running BBC SO.

    I am running BBC SO on a slave PC (128gb) and into logic on a new MacBook Pro (16GB ram) using VEP6. 

    There are numerous drops and clicks with this library although the slave's CPU is very low and there is lots of headroom on RAM. I wondered if Logic's settings might need adjusting but this has not changed the position. I have other spitfire libraries on other instances and have never had any problem.

    I am now experiment with the preload buffer after reading the posts above. However, increasing it to 20000 is leading to a template size of 75GB and it is still loading. I did experiment with changing the voices to 900 which might be causing the problem. 

    Did anyone on this post resolve the problem?

    At the moment I am rather losing confidence in the product which is a shame as the articulations I have got to work sound excellent. 

    Cheers Rupert

     

     

    0
    Comment actions Permalink
  • Ben

    Hi Rupert, I can see you have a support ticket open with our team. Please bear with them, they should respond to you soon.

    0
    Comment actions Permalink
  • Erik van der Horst

    Hi people,

    This is exactly the reason why I'm hesitant to buy the BBC SO; I don't know if my specs will hold up to comfortably make some good sounding music. I have 32gb of ram with a i5 7600 quadcore in a Hackintosh, but I'm still in the dark if this will work out or not. 

    I'm sorry to budge into this thread with a new question, but I thought this would be the right place to get some feedback. Is it wise to buy the BBC SO (and work with the tips mentioned here), or should/can I choose for a 'lighter' orchestra (like the spitfire studio core), and take the loss of expression/sound?

    Looking forward to your reply!

     

    Best,

    Erik

     

     

    0
    Comment actions Permalink
  • Mark Ireland

    To Erik,

    The BBC SO Discover should work I am on a 2010 MacBook Pro i7 with 8gb ram but have Core installed on another machine.

    Regards

    Mark Ireland

    0
    Comment actions Permalink
  • Michael Walters

    Having huge problems with BBC SO Pro. Running an i-9 8 core mac with 64Gb with BBC SO Pro on an external Samsung T5 via usb 3.1. Catalina, Logic, Ozone and SSD firmware all bang up to date. Too many problems to mention, some of the above on instruments loading but not sounding, random crashes (with error report blaming BBC SO), Logic not wanting to close (having to continually force quit). At the moment I'm having to create a new project and import tracks from other projects/previous versions where I know the plug ins having been OK just to get started in the morning.  Have had an open ticket for a few days but no response hence any advice would be very welcome as I can't/won't continue with the current situation.  Great shame as it sounds great for the odd hour here and there where I can work without problems.

    0
    Comment actions Permalink
  • Mark Ireland

    To Michael,

     

    I currently have BBC SO Core but also find problems with it on a late 2013 Mac Pro 64Gb 2TB Internal SSD. I had to put a support ticket into spitfire as I could not get it to play samples via my Korg Kronos MK2 using usb the library would not sound.

    I have just updated to Dorico 3.5.1 and see the plugin inside the notation software but still need to get it playing with Nuendo and ProTools I would say this issue should not be happening on a professional level sample library and the developer would need to look at this for bugs and provide a product that works.

    If you have any thoughts contact me at vivid ireland at bt dot com

    Regards

     

    0
    Comment actions Permalink
  • Alek Vila

    I bought the BBCSO Professional edition yesterday on Black Friday. Now you can add me to the list of people who are having trouble. I have a mid-2010 MacPro 12-core 3.33 GHz with 64 GB RAM. This library seems to be unusable on my computer.

    I made a template and then imported tracks from a previous Discovery edition score. The Discovery Edition versio works beautifully, but with Professional I'm experiencing dropped audio and incredibly long latency. Help!

    0
    Comment actions Permalink
  • Angus

    Hi Alek, 

    I've created a ticket for you so we can investigate further. 

    Best,

    Angus

    0
    Comment actions Permalink
  • Alexander Tudor

    +1 on this! 

    Here is what I posted on the Dorico forum today!

    "
    I just updated from Dorico Elements to Pro with the specific purpose of using my SA BBCSO core.
    The playback template is straight from https://www.spitfireaudiothepage.com/ .

    My Mac has 16GB RAM with a 4 core i7 running at 2.3 GHz; the samples reside on a disk with a transfer rate of 240 MB/s (AJA Systems and BlackMagic Disk Speed Test).

    Several posters have mentioned problems, but I feel that the system I have is unusable across the board; loading and playing.
    The load time and playing responsivness difference between LPX and Dorico Pro 3.5 is remarkable. As expected, the CPU load (Activity Monitor) the Dorico's VST Engine is off the charts.

    "

    0
    Comment actions Permalink
  • Roger Cheveux

    My computer is a MacBook Pro 2019 16Gb RAM i9 8 cores. I bought this configuration because I am a musician beginner...Really, a library for $1000 that doesn't work with "standard" equipment? My appreciation for the Spitfire has been shattered.
    The question is: what is the minimum system required to work seamlessly with BBC Orchestra Pro?
    Maybe one day when I can afford it, I will be able to use it!
    It's a pity because from the little I could try, it sounds very good and much better than anything I've tried so far. I would like to know from someone who can work with this wonderful library to tell me what equipment I should use.

     

     

     

    0
    Comment actions Permalink
  • Alex Marouf

    Same issue than you guys.

    I have Windows 10 X64 , I7 7700K , 32 Go RAM (3200 MHz), library installed on a SSD , Studio One 4 . 

    Juste bought this wonderfull library but unfortunately unusable ! When I run more than 6 instruments I start to losing notes and this is unplayable :'( .

    599 € to be unable to use this library, it's really ... really frustrating !

    Just creat a ticket , I hope there will able to fix that issue

    0
    Comment actions Permalink
  • GREGOIRE LANCELOT

    +1

    Just bought BBCSO some days agao and experiencing same trouble :((

    I run on Windows 10, i7 8700K, 32 GB RAM, SSD, Cubase 10 Pro, Focusrite Saffire Pro 40.

    5 BBCSO instances running together => clicks and pops.

    Tried to set 40000 the preload but nothing changed.

    Really annoying !!!

    What i noticed is that multiple instance run like a charm under Vienna Ensemble Pro ! (why ??)

    Until now i was only playing, not recording on cubase yet, so i got the issue this evening.

    It's a shame Spitfire engine cannot handle many channels on single instance (like Kontakt or Play).

    Unless maybe i didn't understand how to use it properly.

    No apparent CPU/RAM saturation.

    No VST i use products the same issue.

    1
    Comment actions Permalink
  • Alex Marouf

    To Gregoire

     

    Is your Cubase 10 installed on a HDD or SSD ?

     

    Agree ! Kontakt is running really good compare to BBCSO core and I don't really know why ...

    0
    Comment actions Permalink
  • GREGOIRE LANCELOT

    Cubase is installed on NVME SSD :)

    Yesterday i made the test using a Vienna Ensemble Pro instance under cubase this time, and it works !!!

    But i cannot call that a solution :)

    0
    Comment actions Permalink
  • daniel desmoulins

    Hello,

    Similar problem ... I work on MacBookPro 16 ", I7, 16GB RAM, Sound libraries on dedicated external Crucial 1GB SSD, with Dorico and Logic. Extremely long charging time, often without effect, apart from frequent crashes. Discover is the only one to pass, Core is ok for four or five instruments and Pro is impossible. I am extremely disappointed. What machine do you really need to run the pro version? In real time?

    0
    Comment actions Permalink
  • Richard Judge

    I have recently purchased BBC SO Core having tried BBC SO Discovery, I have not been disappointed.

    I only run a modest i5-Quad Core but with high speed 16GB DDR-4 and mixed disk layout.  500GB nvme SSD (WD Black at 3200MB/s) and Mass Storage 2 x 1TB WD Black SATA, and use Samplitude DAW.

    I haven't had issues loading multi-instruments, have 14 loaded using quite a few GB and takes a while to load but loads and works, can play, record etc.  This is along side approx 14 other VSTs actively loaded and running including (Massive X / Syncmaster / Several Magix Smaplitude Plugins and lots of Convology XT)

    What I have got is a slight glitch with tuning, having created a project with multiple tracks, (14 Core instruments) I have Violins 1 / 2 and Celli playing Legatos beautifully, however, when I save the project and close the DAW when I come back to it and open the DAW then reload the project I am finding that my Legatos are out of tune and have dropped by almost 1 semitone.  Has anyone else had this or is it a quirk with my DAW?  Midi notes are still correct but play back is detuned. If I up the tuning of each Legato instrument 0.91st then all sings beautifully again.

    For those with loading issues / HDD or SSD issues, check formatting of the drive, also check the block size you are formatted as. Put exceptions into AV software to bypass checking the spitfire samples in realtime (you should be able to leave them checked during full scan).  Not all SSDs are the same, sustained throughput and not peak throughput is what you need.  You can get a free SSD benchmark tool which will perform proper checks for performance.  When I tweaked my system for BBC SO Discovery Disk and RAM this made significant improvement and I have the same set-up now for Core.

    0
    Comment actions Permalink
  • wesley peterson

    I've looked around and haven't seen a recommended block size. Could you tell me what it is? Thank you.

    0
    Comment actions Permalink
  • Frank Opolko

    Was going to purchase BBCSO but after reading these comments am not so sure. Have a 2019 iMac running MacOS Mojave 3GHZ Intel Core i5 with 8GB / 2667 Mhz DDR4... I've got Logic Pro and Pro Tools....  

    Do I need the full Kontakt ?  Hoping to create video soundtracks. Do you recommend this library over Albion 1?

    Are there other orchestral libraries you like?

    0
    Comment actions Permalink
  • wesley peterson

    Hi Frank Opolko. BBCSO runs in it's own plug-in, not Kontakt. I don't know how BBCSO runs on a Mac but 8GB of RAM is a bit too low to run Pro. Depending on your budget and what kind of soundtracks you want to make there's a large array of libraries. For dry I like Cinematic Strings, Cinematic Solo Strings, and Cinematic Brass (especially Cinematic Brass, I blend it with BBCSO). For a lush soundtrack sound Spitfire Symphonic Orchestra is fantastic but it's expensive. A lot of people really like Berlin Strings, but I haven't used it, Cinestrings, Cinewinds, Cinepercussion (it's great!), there's just so many great libraries out there. But I would recommend picking up BBCSO Discover, it's fifty bucks or free if you take a survey, and just mess around with it. It's really light on your system, so just have fun with it and decide from there.

    0
    Comment actions Permalink
  • Angus

    Richard Judge I've not come across this particular issue you mention RE: Legato Tuning. If you want us to look into it on your behalf, by all means please contact us via the Help widget below. A screen recording, or audio files, will be helpful here. 


    Frank Opolko as mentioned  on your other forum post, no BBC SO does not require Kontakt Full. It runs in its own dedicated plugin, which is freely available as part of the install for each library. You should however consider upgrading your RAM to at least 16GB RAM. Pro Tools in particular can use a lot of RAM prior to adding software instruments. If you plan on scoring to film in Pro Tools with BBC SO, I would recommend 32-64GB of RAM. 

     

    0
    Comment actions Permalink

Please sign in to leave a comment.