Battery 3 Polyphany or CPU cutouts

I have increased my polyphony to 128 (even though it does come close) and when i play back my song sometimes when the snare hits or any other sample for that matter cuts off half way through randomly. when this happens the CPU meter is red (around 3% usage). How do i up the usage that battery is allowed to use so it doesn't cutoff to save cpu cycles? Or is there somthing else im missing. thanks.

 

anyone have any ideas?

 

it's a bug. same problems here.

 

Sama problems here on a PPC Powerbook.

 

Re: Battery 3 Polyphony or CPU cutouts

Same problem here, usually during mixdown, even in non-DFD mode.

AMD 3200, 1 GB memory, Win XP SP2

 

Re: Battery 3 Polyphony or CPU cutouts

exactly, that's why b3 is absolutely useless to me, can't work with it because it's unable to play the sound right. horrible.

 

here the same too....

i've sold my battery2 because i've bought komplete4 with kore (btw. great package!!) and now i have problems to work with battery... all my drumsets, my work on several projects, it's horrible!

i hope to see an update fixing this bugs soon.

 

I have the same problem with Battery 3 and Kontakt. Battery 2 had been stable, no cutouts. Kontakt (any version) has always had a problem cutting off notes prematurely. I just installed the Battery 3 update, so we'll see how it works. Oddly, my NI products have always worked better in Live, and worse in Sonar.

 

the update didn't change anything, same issue @ 3.1.

in kontakt: switching off the voice killing by cpu in the options should solve the problem.

 

I bet this time next year. We will be saying the same, this is what happened with Bat 2. Bat 2 was released 10/04 and we did not get a patch till 7/06. Then in 9/06 they throw Bat 3 on us. So not this Summer but next summer we will get a patch and it will half way work. Then 3-4 months later BATTERY 4 is released. They are laughing their rearends off at us suckers. I knew we should have nuked Berlin in '45.

 

Thanks for the kontakt tip, I think that cleared up my problem! Now WhyTF can't they implement the same voice killing by cpu options in B3, as it is CPU overloads that are killing the voices?

 

Wow,

Sometimes I'm floored by how angry and vitriolic people are on this board. NI definitely has some serious issues, but comments like that above are just completely unhelpful and shitty.

If you live in the US, you should start looking around you and make sure your own country isn't turning in to "Berlin in 45."

The jackboot may just be on your neck soon. Couldn't happen?

http://www.commondreams.org/headlines05/0910-07.htm
http://www.gnn.tv/articles/2893/Merc_Army
http://video.google.com/videoplay?docid=-662148672739214615

 

same problem in here too
AMD X2 4200+ 2 GB of RAM Windows XP SP2
and i get a lot, it gets a little better when changing to 128 voices, but still happens.
hope to see a fix for this pretty soon
NI r u around??

 

i have the same problems on an iMac c2d. Battery, Kontakt, Acoustic Piano. Already know the problem from Kontakt on my old G4. Had it since version 2 I think.

 

If you live in the US, you should start looking around you and make sure your own country isn't turning in to "Berlin in 45."

Sarcasm out of frustration. So Bat 3 is working perfect for you? If you did this for a living, you might get "bent out of shape" also. We laid our money down and expect a usable product. Is that wrong in your neck of the woods?

 

Same problem here too. I think it's farcical that triggering a two bar run of 16th note snares is enough to cause a CPU overload and eventual cut out of audio. It's a drum machine for f**k's sake. Kontakt 2 is marginally better ie. opening a battery 3 kit in Kontakt 2 the triggering is marginally better. But K2 still has the occasional cut outs.

C'mon NI, you have reasonable responsibility to fix this 'fundamental' issue.

AMD Opteron Dual 2.4hgz. Komplete 4 Running as VST's inside Plogue Bidule.

 

much peoples replied in this thread, all with the same problem. so there must be something wrong.

 

yep, i was using it in FL Studio and i couldnt even use it, i tested it in pro tools m powered and havent had a problem. ive been using it there lately to make my tracks
hope they release an update soon

 

It would be nice to get any sort of aknowledgement at all. I also cannot use this in FL, or tracktion.

 

I'm actually testing battery 3.0.2 and I think this bug was corrected.
Any feedback?

Nicola P.