What's new

Spitfire Audio - "It's all about to change" - BBCSO Core / Discover

I’m so glad I didn’t give in to getting BBC before it’s truly optimized and de-bugged. Hopefully by Black Friday.
 
Does anybody know if Spitfire has any intentions to bring a "Purge Samples" feature to their player? Afaik you can purge articulations - still, for people with limited RAM a feature to purge samples (like in Kontakt) would be very nice. It's actually one of the reasons that's holding me back from getting Core ...
 
Does anybody know if Spitfire has any intentions to bring a "Purge Samples" feature to their player? Afaik you can purge articulations - still, for people with limited RAM a feature to purge samples (like in Kontakt) would be very nice. It's actually one of the reasons that's holding me back from getting Core ...
Yep, they have stated that quite a few times, but not sure when they will release it
 
Hope this is the right place to ask. I picked up BBC Core at the sale. When i load even the "lightest" ableton template, my RAM usage spikes to 31Gb/32Gb even though the plugin itself is saying it's only using 13Gb of RAM. Is this an issue with ableton? My pro tools MIDI is completely bugged right now so i cant really test it out great on there and i don't have Cubase yet.

This is not ableton specific, but a problem of the plugin, which mainly seems to affect windows users.
See for example here and here in the other thread, or here at spitfire support.
 
I downloaded BBC SO Discover a few months ago but never really used it. Today I decided to do a quick and simple orchestration (No programming at all). I´m absolutely impressed with the quality of the sound. It just sounds so real and it is the free version. I loved the spatiality within the instruments. I was hoping to get HZS as birthday present but now... maybe I´ll go for BBC SO Pro version.
 

Attachments

  • BBC Test.mp3
    560.3 KB · Views: 90
I downloaded BBC SO Discover a few months ago but never really used it. Today I decided to do a quick and simple orchestration (No programming at all). I´m absolutely impressed with the quality of the sound. It just sounds so real and it is the free version. I loved the spatiality within the instruments. I was hoping to get HZS as birthday present but now... maybe I´ll go for BBC SO Pro version.
So funny to hear you say this. It’s exactly how I feel. I tried to write a few bars with the Discover Strings and it just sounds the way I want it to but I’m so resistant to buying more SF because of the inconsistencies. But I may cave.
 
So funny to hear you say this. It’s exactly how I feel. I tried to write a few bars with the Discover Strings and it just sounds the way I want it to but I’m so resistant to buying more SF because of the inconsistencies. But I may cave.
Yeah, i feel the same about the inconsistencies. For what I´ve seen in several demos, "virtuoso" orchestral mockups are not BBC SO strength. You know, incredibly fast legatos and ostinatos sometimes may require deeper programing as every other library to achieve realism.

When browsing through all demos I could´ve encounter, I did notice that the ones I enjoyed the most were original compositions. Most of popular songs arrangements were not too much appealing for me. Maybe it´s because we have heard this songs thousands of times that when we try to emulate them with vsts something doesn´t feel quite right. In original compositions, I think BBCSO can shine as much as your abilities to compose can reach. Simply because we are not tied to what we feel a certain piece should sound like.
 
Yeah, i feel the same about the inconsistencies. For what I´ve seen in several demos, "virtuoso" orchestral mockups are not BBC SO strength. You know, incredibly fast legatos and ostinatos sometimes may require deeper programing as every other library to achieve realism.

When browsing through all demos I could´ve encounter, I did notice that the ones I enjoyed the most were original compositions. Most of popular songs arrangements were not too much appealing for me. Maybe it´s because we have heard this songs thousands of times that when we try to emulate them with vsts something doesn´t feel quite right. In original compositions, I think BBCSO can shine as much as your abilities to compose can reach. Simply because we are not tied to what we feel a certain piece should sound like.
All of the best demos are here. https://www.spitfireaudiothepage.com

What I think I would like best is that the orchestra is within one plugin...no more searching through libraries to find sounds..granted if I had a template setup that would solve that issue..LOL
 
For me it's a change indeed.
I have BBC SO Professional (pre-ordered), but the BBC SO project I started writing on my Windows 7 machine was not playable properly on my new Windows 10 PC. Clicks and pops, CPU overloads all the time.

Yesterday I updated to the new version of the plugin, project playback was smooth, CPU load was around 35-40%. Still to be tested, but very promising for now.

Can anyone else confirm the improvement on performance?
Hi I'm new to this forum so sorry if I'm not following the correct etiquette, but I wondered what your performance is like now with BBC SO Pro? I am getting a new PC and have purchased BBC SO already so I'm hoping it is OK (multithreading etc)?! Thanks in advance.
 
Hi I'm new to this forum so sorry if I'm not following the correct etiquette, but I wondered what your performance is like now with BBC SO Pro? I am getting a new PC and have purchased BBC SO already so I'm hoping it is OK (multithreading etc)?! Thanks in advance.
Hello Dom!
I couldn't figure out what was causing the problem, I did everything the Spitfire support team suggested and even custom performance modifier settings, but I still experience clicks and pops, especially with the legatos or if I make a complete template and play fast short passages with many instrument goups.
(The libray runs on a Samsung 860EVO)
If I save the project and restart my machine, it's better for a while. Well this is also experienced with Cinestrings solo library, so I can't tell that the problem caused by the Spitfire player.
And many users can use it without problems on windows 10 machine.

Maybe I will try it with Studio One instead of Cubase.

By the way, the issue appears with the new Abbey Road plugin as well, so I think it is some compatibility problem with my machine.
 
Hello Dom!
I couldn't figure out what was causing the problem, I did everything the Spitfire support team suggested and even custom performance modifier settings, but I still experience clicks and pops, especially with the legatos or if I make a complete template and play fast short passages with many instrument goups.
(The libray runs on a Samsung 860EVO)
If I save the project and restart my machine, it's better for a while. Well this is also experienced with Cinestrings solo library, so I can't tell that the problem caused by the Spitfire player.
And many users can use it without problems on windows 10 machine.

Maybe I will try it with Studio One instead of Cubase.

By the way, the issue appears with the new Abbey Road plugin as well, so I think it is some compatibility problem with my machine.
Thanks for such a quick and detailed response tadam! That sounds positive. On a related note, my current PC has 128 Gg RAM and a 4-5 yr old i7 processor running Windows 7. The new machine will be very powerful, either 14-18 core i9 (with up to 256 Gg RAM), or one of the very latest Ryzen 5950X processors (probably limited to 128 Gg RAM), both with M2's/SSD's. The Ryzen is probably more powerful, especially single core speed (and looks like it will outperform on the different Dawbench tests), so wondering which to get (Threadripper has recently been blacklisted for now by Steinberg)? I can sometimes use, say 100 Gg on my current orchestral projects with the i7, but the processor really does struggle. Whereas with a new Ryzen, I might be able to optimise BBC SO to use less RAM (and also things like Kontakt with Purge), so I use less RAM, but have more power, especially for playing fast rhythms live at lower buffer settings? Not sure if you have a view on this from your own experience (or whether I should really start a new thread?!). I have also looked at VEPro, which I may add to the workflow, but will keep things in Cubase for now (using VST instruments seems to spread the load well currently). Anyway thanks again and of course happy to give an opinion on anything your side from my own experience.......
 
So funny to hear you say this. It’s exactly how I feel. I tried to write a few bars with the Discover Strings and it just sounds the way I want it to but I’m so resistant to buying more SF because of the inconsistencies. But I may cave.

Its truly impressive. So impressive that I ran off and bought the Core. Built my own template with freeze tracks for rapid launch and have really enjoyed it. The playability and the sound is a treat!

MOMA
Stockholm, Sweden
 
Its truly impressive. So impressive that I ran off and bought the Core. Built my own template with freeze tracks for rapid launch and have really enjoyed it. The playability and the sound is a treat!

MOMA
Stockholm, Sweden
I have long since bought the Pro version....making a template with it now in fact.
 
Not sure, but the one upgrade I would get with an M1 MacBook Air is 16Gb RAM for $180 USD.

It could be tight with 16GB ram. My BBC core template runs around 10~12GB with 20~30 tracks including plugins...etc with Logic on MBP.
 
It could be tight with 16GB ram. My BBC core template runs around 10~12GB with 20~30 tracks including plugins...etc with Logic on MBP.
16 is no where near enough...once you have those tracks filled with data, you would be freezing tracks a lot. Doable of course, but limited for sure...don't bother with the M1 Macs..they are not tested and to be avoided for audio...wait until they get at least 32 gigs minimum allowed, and are supported by all developers.
 
Then again, I’m reading interesting things about the use of RAM in that new M1 chip. Maybe it just needs less RAM while streaming is optimized...
 
Then again, I’m reading interesting things about the use of RAM in that new M1 chip. Maybe it just needs less RAM while streaming is optimized...
Yes this is true according to Apple...but we have yet to see how it works and is optimized for Audio. There is a thread on FB I think in the Pro Tools or Audio Production groups...the consensus is a big NO! LOL. ONLY if it is an absolute must, and possibly as an experiment for a second mobile rig...but definitely not as your main computer.
 
Yes this is true according to Apple...but we have yet to see how it works and is optimized for Audio. There is a thread on FB I think in the Pro Tools or Audio Production groups...the consensus is a big NO! LOL. ONLY if it is an absolute must, and possibly as an experiment for a second mobile rig...but definitely not as your main computer.

They're just starting. Give it time.

Message brought by a Windows 10 user! :)
 
Top Bottom