buzz forums

This may be a stupid observation but the VU meter does not detect the noiseburst. No, that's very true - A lot of times I have noise bursts it shows up on the master VU meter as having an output of -inf db, or is that just the behaviour of Buzz representing >0db volume ? (erm, or is than not what y...

I mentioned Merzbow because this would be a good example of a type of sound that would be hard to distinguish from unintentional noise. Yes, absolutely - and back in the mid-2000s I used to do a lot of noisy experiments and had to turn off Overloader's burst protection as a result. A mixture of dc ...

Out of interest, what's the form of the data 'packets' (if that's the right word) that comes out of the Pout of a machine. If you were able to look at the stream would you be able to identify invalid data chunks or is that a) too much of a cpu hog and/or b) just impossible ?

The typical multithreading noise problem is usually down to the use of static (ie. shared between all instances of a machine) buffers in output related functions. Before multithreading came along, this was a common technique and it didn't matter because only one machine would ever access the buffer...

Is there a way to configure it to play a Florian Hecker one instead

EDIT: Is it that a machine briefly produces a sound above 0db (i.e. in headroom terms) which as a result freaks out the rest of the chain ?

This maybe one more for devs - I mean, I know what one sounds like (especially on headphones, when working on a track in the dead of the night :shock: ) but I've always took it as read that machines in Buzz sometimes go mental and make noise bursts without questioning it. I hadn't thought about it f...

All the builds pretty much - there's tiny updates with each release (see the changelog - http://jeskola.net/buzz/beta/files/changelog.txt ) but the overall workflow is the same. The version I posted is less than a month old and the only real differences are behind the scenes stuff (that's perhaps be...

Just download the installer from http://www.jeskola.net/buzz/ (stick with the x86 version to make your life easier), run it, then after it's installed copy your gear folder from your old install of Buzz to the new one, then maybe update to the latest Polac VST/i loaders ( http://forums.jeskola.net/v...

A couple of weeks ago Oskari recommended sticking with v1453 and skipping the next few builds due to various stability issues. As an end user (as opposed to a developer) would you guys advise still holding off updating it ?

domtron wrote:in the new builds it's called polac audio in.

Doh, I wondered what that was !

Yeah Polac ASIO In works but you may have to tinker with the attributes (right click on machine -> Attributes) depending on your sound card - I switch it to mono mode, then I can choose any of the 6 input from my audio interface. Make sure you don't use Polac Asio Mono In or Polac Asio Stereo In tho...

Buzztler wrote:My graphics card is one year old and so it is much too old for the new Buzz

The graphics card on my last laptop was 6 years old and was just fine for the new Buzz builds (the last release I used on it was 1453)

Hey for free that really aint bad at all. I mean, I'm gonna stick with my Pianoteq but if I couldn't have afforded it then that well would've been my piano VSTi of choice ...

For some reason that reminds me of Geometry Wars -

Prints thread.

It's a bit more complicated then that because of the difference in programming languages between the c# stuff in the current buzz and the old c++ peer system which ran on hacks to old buzz. I think the old system of peering needs to be replaced if it was going to be able to be added to anything at ...

Yeah it's definitely a theme related error, possibly an older version of Default is used in the >1454 x64 builds. Try downloading the latest 32 bit build then dragging and dropping the Default folder in the Themes directory to the Themes drriectory of the 64bit folder

Yeah, updating themes so they're compatible with the new builds is becoming an almost daily activity now (took me ages to work out how to get mine to work for versions post 1454 - I'm a little slow ...)

Isn't it just easier to set the start and end volume in a pattern then CTRL-I it to interpolate the values? Anything else seems superfluous to an already simple procedure...

I guessing it's the rather forceful second sentence that ruffled people's feathers - it made the compliment seem somewhat backhanded....