The initial XORs of the adder don't always work if the inputs don't have about the same signal strength. Therefore your test with the levers could lead to wrong results.
That's technically true. In this specific case however, the lever test was correct. There was a reason I used inverted inputs other than just showing it off: The furnaces in the input logic are already set up to give precisely the correct signal when the input is being inverted. Good thinking though: This is something that you need to be mindful of as you build new components that input to the ALU.
@bennyscube: The vector cut-carry does not work if the generate torch of the 16-value bits overrides the signal strength. The generate torches are 1 block too high. For all bits except the lowest one you have to break the block the generate torch is on and place the torch on the block with the redstone dust that went into the block you just broke.
You need the signal inputs entering the XOR at the beginning to always have the same strength, since this type of XOR is strength sensitive. Only reason addition worked for you is because you used !A, if you used A then it wouldnt have worked.
Ah, if only noise reduction was that simple. Under the hood, noise reduction works by creating a so-called profile that tells it how loud the noise is, on average, on any given frequency. Based on that, it decreases the volume of a given frequency once it's quiet enough to be more likely noise than desired audio. If you just did that, then you get the crazy alien-sounding artifact, kinda like you hear in this video although much more prominent, as various frequencies "pop" in and out of being considered noise. If you try simply reducing the amount of noise reduction until the artifact is gone, it doesn't work: the noise comes back in almost full force before that, and you end up with both noise AND popping. Basically, there's no "golden middle" where you have minimal amounts of both artifacts and the audio is okay, instead it gets worse heading into the middle ground. That's why more advanced additions to noise reduction algorithms are used, like smoothing between frequencies to minimize the perceived "pop" when a certain frequency is considered noise but those near it are not, or using attack/decay timings on the noise gates to prevent sudden changes in what is/isn't considered noise. These can help, but they introduce a new problem: They give the noise filter a "broader brush" to what it will and won't consider noise in certain cases, and that starts removing more and more actual desired audio (in this case, my voice). Believe me, it sounds really bizarre when you're listening to someone's voice and it sounds totally normal, except when it hits one particular frequency, and then it goes completely mute. In the end, you're playing with the various parameters to noise reduction, trying to find just the right combo that leaves an acceptable balance of the 3 artifacts. The good news for the casual user is most programs have sane defaults for these advanced parameters, so they never need to touch them. The bad news for me is in my case, the defaults do not leave a very good balance of the artifacts. I haven't found an especially great balance on my own yet, but I'm optimistic on improving it, even though I don't think it'll ever be perfect.
I know from FL Studio that the noise reduction tool has a function to preview the removed sound only. It's much easier to finetune when you play around until you have no voice left, the turn the funktion off and you're done. if your program doesn't have that consider searching for one that does
it probably messed up due to how you make negative binary numbers. to make a number negative you have to take the inverted value AND add 1 to it. binary 5 is 0000 0101 the inverted value is 1111 1010 but that is not -5, that is -6 -5 is 1111 1011 so in order to subtract you have to invert the number and add 1 via the C-in
you forgot to add this to the Playlist.... awesome vid ty. would you consider rebuilding the alu from beginning to end in a single vid only explaining when you place a sign? I haven't started copying the build yet but I think with 3 visits from Future Benny in one vid I might get lost :p I really love your tutorials and am glad you are back!
Thanks for the catch! It's now added to the playlist. I don't think a rebuild is justified because 1) The corrections are pretty dead simple. (One is I built the correct component, but forgot to stack it with World Edit. In the other two, the components were correct, but a furnace was off by exactly 1 signal strength.) 2) I think Future Benny was pretty clear on what the issue is and how to fix it. I've watched the corrections back several times and I don't see a lot of potential for confusion. 3) This is the only video where I needed to issue corrections to the build. All others are fine. Of course, if you believe a rebuild is justified for reasons I haven't considered, I'd still like to hear them.
so... I thought I had broken the whole thing when I tested it for the first time after adding the accumulator logic but it turns out you have to put the signal sources the same lengths away from the first XOR gate when testing inputs.... oof. Actually, I'm just happy I didn't break it lol.
when I use inverted inputs and allow in !a, it does the calculations correctly but when i use uninverted inputs and allow it a, it practically or's the out put, anyone know whats wrong?
In addition to the 16 bit potentially lighting up from the misplace carry torches, i found that the signal strength in this configuration for the first xor is not the same for the normal and inverted inputs
@@vegawolfz4357 My fix was to set all the furnaces to strength 15 in the input logic. It seems to have worked, but I don't know if it will have any adverse effects, since benny seemed to emphasize getting exactly the right strength there
Is there any particular reason to not just use a signal strength of 15 on the furnaces for the negation comparators? I found that if I tried to power the inputs of the ALU directly, the low signal strengths from the negations were too different from the inputs from the levers so the XOR gates didn't function properly.
This is great! I'm just wondering, why is there only an invert b but not invert a, and no cut carry? It seems like you can't do a lot of logical functions because of this.
There is invert B and invert A! The second invert was obtained when copying the input control logic. An explicit cut carry isn't needed because in the two cases where it's desired, OR and Flood carry, they both cut carry automatically.
So after I built the accumulator and its mirror for the inputs, when I would turn on one lever, it's input and the input above it would both turn on. Has anybody else had this problem, and do they know what to do? I play on PS4 by the way
Will this computer have subtractors, multipliers and dividers. What will be the main functions of the computer once it's completed, and will it be simple(ish) to use once it is completed? ;D Also, how many tutorial parts do you think this computer will have once finished.
No multipliers/dividers that's apparently too complicated and slow in Minecraft. It would take up so much more space to just add these two functions. Subtraction you can just invert the B input and activate carry-in.
I'm having a big problem here. When I turn on Floof Carry, the signal still reaches to the block before the repeater that sends the first half-adder outputo into the XOR on the right. Has anyone encountered this problem? how can I solve it? (the signal strenght is right tho, the repater takes the power from the block)
i feel like an update that came later after this build causes some shenanigans to happen. i've unfortunately been unable to follow these videos because i think thats why
@@Cinnimin yup! I remeber I got it fixed but I can't remember how at the moment. You can surely find out in the ORE community or with enought internet browsing. I think it was 1.16
Which alien ship are you transmitting from?
Props to koyarno for designing this. The compactness and speed combination is AMAZING.
The initial XORs of the adder don't always work if the inputs don't have about the same signal strength. Therefore your test with the levers could lead to wrong results.
That's technically true. In this specific case however, the lever test was correct. There was a reason I used inverted inputs other than just showing it off: The furnaces in the input logic are already set up to give precisely the correct signal when the input is being inverted. Good thinking though: This is something that you need to be mindful of as you build new components that input to the ALU.
Yes, I noticed too during testing, if you sum a direct input to the accumulator value it does not sum correctly if it has to handle the carry -> 1+1=1
@bennyscube: The vector cut-carry does not work if the generate torch of the 16-value bits overrides the signal strength. The generate torches are 1 block too high. For all bits except the lowest one you have to break the block the generate torch is on and place the torch on the block with the redstone dust that went into the block you just broke.
Welcome back benny good to see you uploading again
You need the signal inputs entering the XOR at the beginning to always have the same strength, since this type of XOR is strength sensitive. Only reason addition worked for you is because you used !A, if you used A then it wouldnt have worked.
Audio messed up again :/ but still nice video, I learnt :)
Edit: and yeah, it's definitely better than last time, tho :)
It's better than last time though.
Yeah, I'm working on it as best I can.
Maybe don't go so OTT with the noise reduction
Ah, if only noise reduction was that simple.
Under the hood, noise reduction works by creating a so-called profile that tells it how loud the noise is, on average, on any given frequency. Based on that, it decreases the volume of a given frequency once it's quiet enough to be more likely noise than desired audio.
If you just did that, then you get the crazy alien-sounding artifact, kinda like you hear in this video although much more prominent, as various frequencies "pop" in and out of being considered noise. If you try simply reducing the amount of noise reduction until the artifact is gone, it doesn't work: the noise comes back in almost full force before that, and you end up with both noise AND popping. Basically, there's no "golden middle" where you have minimal amounts of both artifacts and the audio is okay, instead it gets worse heading into the middle ground.
That's why more advanced additions to noise reduction algorithms are used, like smoothing between frequencies to minimize the perceived "pop" when a certain frequency is considered noise but those near it are not, or using attack/decay timings on the noise gates to prevent sudden changes in what is/isn't considered noise. These can help, but they introduce a new problem: They give the noise filter a "broader brush" to what it will and won't consider noise in certain cases, and that starts removing more and more actual desired audio (in this case, my voice). Believe me, it sounds really bizarre when you're listening to someone's voice and it sounds totally normal, except when it hits one particular frequency, and then it goes completely mute.
In the end, you're playing with the various parameters to noise reduction, trying to find just the right combo that leaves an acceptable balance of the 3 artifacts. The good news for the casual user is most programs have sane defaults for these advanced parameters, so they never need to touch them. The bad news for me is in my case, the defaults do not leave a very good balance of the artifacts. I haven't found an especially great balance on my own yet, but I'm optimistic on improving it, even though I don't think it'll ever be perfect.
I know from FL Studio that the noise reduction tool has a function to preview the removed sound only. It's much easier to finetune when you play around until you have no voice left, the turn the funktion off and you're done. if your program doesn't have that consider searching for one that does
Hey man, glad to see you're back! You may or may not remember me from the server. May I ask what texture pack you're using?
He's using the OCD resource pack by fv disco
My copy of this got the same results when doing everything you did, but subtraction messed up. Is there a special way of doing it for this ALU?
it probably messed up due to how you make negative binary numbers. to make a number negative you have to take the inverted value AND add 1 to it.
binary 5 is 0000 0101
the inverted value is 1111 1010 but that is not -5, that is -6
-5 is 1111 1011
so in order to subtract you have to invert the number and add 1 via the C-in
you forgot to add this to the Playlist.... awesome vid ty. would you consider rebuilding the alu from beginning to end in a single vid only explaining when you place a sign? I haven't started copying the build yet but I think with 3 visits from Future Benny in one vid I might get lost :p I really love your tutorials and am glad you are back!
Thanks for the catch! It's now added to the playlist.
I don't think a rebuild is justified because
1) The corrections are pretty dead simple. (One is I built the correct component, but forgot to stack it with World Edit. In the other two, the components were correct, but a furnace was off by exactly 1 signal strength.)
2) I think Future Benny was pretty clear on what the issue is and how to fix it. I've watched the corrections back several times and I don't see a lot of potential for confusion.
3) This is the only video where I needed to issue corrections to the build. All others are fine.
Of course, if you believe a rebuild is justified for reasons I haven't considered, I'd still like to hear them.
so... I thought I had broken the whole thing when I tested it for the first time after adding the accumulator logic but it turns out you have to put the signal sources the same lengths away from the first XOR gate when testing inputs.... oof. Actually, I'm just happy I didn't break it lol.
when I use inverted inputs and allow in !a, it does the calculations correctly but when i use uninverted inputs and allow it a, it practically or's the out put, anyone know whats wrong?
In addition to the 16 bit potentially lighting up from the misplace carry torches, i found that the signal strength in this configuration for the first xor is not the same for the normal and inverted inputs
Same. Have you found any fix?
@@vegawolfz4357 My fix was to set all the furnaces to strength 15 in the input logic. It seems to have worked, but I don't know if it will have any adverse effects, since benny seemed to emphasize getting exactly the right strength there
@@ciherrera I think the use of furnaces is to get the bare minimum redstone signal to prevent lag, so 15 strength is just as useful.
I know this is late but after this episode the carry doesn't add properly. So 0101 + 0011 would equal 0100. Could you maybe make a world download?
Is there any particular reason to not just use a signal strength of 15 on the furnaces for the negation comparators? I found that if I tried to power the inputs of the ALU directly, the low signal strengths from the negations were too different from the inputs from the levers so the XOR gates didn't function properly.
I dont know if you should continue doing noise cancellation, wasnt it better when it was episode 3? anyway thank you for making these videos :)
This is great! I'm just wondering, why is there only an invert b but not invert a, and no cut carry? It seems like you can't do a lot of logical functions because of this.
There is invert B and invert A! The second invert was obtained when copying the input control logic. An explicit cut carry isn't needed because in the two cases where it's desired, OR and Flood carry, they both cut carry automatically.
+bennyscube what rank do you have on the ORE server?
blademon7 P4P Builder.
Kellan Gaming ok
So after I built the accumulator and its mirror for the inputs, when I would turn on one lever, it's input and the input above it would both turn on. Has anybody else had this problem, and do they know what to do? I play on PS4 by the way
Can this be made in 16 bit?
Will this computer have subtractors, multipliers and dividers. What will be the main functions of the computer once it's completed, and will it be simple(ish) to use once it is completed? ;D
Also, how many tutorial parts do you think this computer will have once finished.
No multipliers/dividers that's apparently too complicated and slow in Minecraft. It would take up so much more space to just add these two functions. Subtraction you can just invert the B input and activate carry-in.
have you AND function? and comparator will be in alu?
The AND is a combination of the following functions: invert A, invert B, OR (aka cut carry), and flood carry.
What's your secret for time travel?
What happens if you combine Vectorization with Flood Carry?
Nothing
How can you do a subtraction with this version of the ALU?
Dave Mullen 2 years ago, but my !B doesn’t seem to work. I THINK it’s a difference in signal strength, but idrk. Could I get your input?
I'm having a big problem here. When I turn on Floof Carry, the signal still reaches to the block before the repeater that sends the first half-adder outputo into the XOR on the right. Has anyone encountered this problem? how can I solve it? (the signal strenght is right tho, the repater takes the power from the block)
i feel like an update that came later after this build causes some shenanigans to happen. i've unfortunately been unable to follow these videos because i think thats why
@@Cinnimin yup! I remeber I got it fixed but I can't remember how at the moment. You can surely find out in the ORE community or with enought internet browsing. I think it was 1.16
@@aurelio3532 oh thanks, ive been getting reccomended that server a lot lately so
@@Cinnimin it's truly a great place, also for learning
how would you do AND on this alu?
AND is the same as !A + !B + OR + FC
Dammit wheres the fuzz gone!? I like listening to fuzz xD
10:13 Beard confirmed
I dont get it
Ze Cursed Gamer Look in the chat at 10:10 you'll understand
There were 68 comments
Why does it say there are 46 comments when I can onlycount 32?
Franz Schubert did you count the reply comments
100 likes on the video, I'ma make it 101
Your next series of videos should be "Building a better microphone" :p
Deksor that's not his Mic something went wrong in the noise reduction
blademon7 P4P yeah, but his microphone is creating a lot of noise by itself which is why he had to use (bad) noise reduction ^^
first!
Second
Minute
I read your name, but I won't like your comment. :)
diesernameistsolangdassduihndirbestimmtnichtbiszumendedurchliestwenndochlikediesenkommentar! You need a better name