buzz forums

https://www.dependencywalker.com/ download this and open ninereads softy.dll in it, you will see what msvcrt version is missing. most likely 7,7.1 or 8 or so with these old machines. those old versions don't come with redistirbutable installers (before 2005 iirc), so you'll have to hunt down the fil...

I tried to fire parameter changes from Work() to make it more accurate but that seems to cause issues. Something hangs in SetValue. Maybe not a good idea to do this in audio thread and stress the call too much. this should work i think, at least in native machines it does, but you might want to wai...

set scaling to 100%... hope you have a big enough screen hehe

7F in decimal is 127, so that's correct.
but yeah if note off sends velocity 1 instead of 0 it won't work.

Can anyone think of a reason why pVST would be sending F#4 instead of NoteOff? there are two ways to define / send note offs in midi: 1) note off messages 2) note-on messages with 0 velocity from midi spec: "A receiver must be capable of recognizing either method of turning off a note, and should t...

open the dll in this and see which msvc version it's missing, then install that (or drop the msvc dll into buzz root)
https://www.dependencywalker.com/

Willy wrote: ↑

Wed Jul 22, 2020 5:48 pm

PayPal is pretty mainstream and secure, Bitcoin on the other hand is super sketchy.

pretty much the other way round, but not going to argue if you don't already understand why bitcoin is far superior, just that it's worth learning about it.

if you have a logitech mouse, you can set your "Signalrate" to the lowest possible (125) to somewhat mitigate the problem, the cpu load is still much to high, but it doesn't max out the GUI thread at least. At 500 (which is the default and feels smoother too imho) the GUI thread is completely maxed ...

On my PC, when i move the mouse in buzz quite fast, buzz uses a whole core... also tested it on my laptop, the problem is there, but less pronounced, i think it's something to do with mousemove events firing more often for high dpi mice, but probably something in response to mousemovements is not ri...

dnafrequency wrote: ↑

Fri May 22, 2020 6:00 am

I found #buzz on Efnet but no one is home...

you quit just as someone replied just come back.

sometimes (very rarely) when i start buzz, in the debugger i get a break and this message in the output: <mda:msg xmlns:mda="http://schemas.microsoft.com/CLR/2004/10/mda"> <!-- Attempting managed execution inside OS Loader lock. Do not attempt to run managed code inside a DllMain or image initializa...

here's what i don't understand, let's assume these are the two first work calls to happen and the auxbuffer is 256 in size: work1: numsamples: 16 -> Send 16 samples to aux buffer work2: numsamples 200 -> Receive 200 samples from aux buffer well, obviously we never even wrote 200 samples yet... accor...

IXix wrote: ↑

Mon May 11, 2020 9:15 pm

...and this...

yes, i used that as a starting point... it works if i just copy the the input to the aux, but just doing slightly more seems to break it..

Despite my obsessive compulsive machine source hoarding instincts, I don't have any of ld's machines but I do have this... thanks' this is what i'm already looking at to get a clue of how auxbus.lib (which i'm linking in and using auxbus.h header) works... i can get it to somewhat reliably send the...

also i'm wondering how this can possibly even work reliably in a multi-threaded environment? i guess it relies on the guarantee that effects are processed after generators, even when multi threaded, so the aux return is always 1 buffer late? But surely, effect chains are put on different threads so ...

so far i got sending working, and using ld auxreturn to return it, but there is a problem: parts of the buffer are missing sometimes, it looks like the return machine reads it too soon or a multithreading issue, but when i try it with ld auxsend, it works... so not sure what auxsend does different.....

anyone knows if these are open source? would need to take a look to implement aux.

thanks for these, very helpfull!

can you find the thread where it says "see THIS THREAD" too ?

i'll have to test this some more, as i think it's possible to make it even a bit smoother, for some reason some work() calls don't seem to get updated parameters yet i think, have to properly timestamp / count and see. all in all: it might not be worth the effort to change anything in peer machines....

here it is at 10hz in time domain. peerlfo at the bottom.