Why I'll Never Use Copper Bulbs
Vložit
- čas přidán 20. 05. 2024
- Patreon: / mattbatwings
Discord: / discord
My socials: linktr.ee/mattbatwings
My texture pack: modrinth.com/resourcepack/mat...
World Download: (JAVA 1.21 SNAPSHOT) www.planetminecraft.com/proje...
-------------------------
Want to get more involved in the logical redstone community?
Learn Logical Redstone! • Logical Redstone Reloaded
Open Redstone Engineers (ORE): openredstone.org/
0:00 Intro
0:37 What's a Copper Bulb?
1:54 User Interfaces
6:09 Memory
9:56 Binary Counters
12:14 Screens
15:40 Subscribe!
Music (in order):
Harris Heller - Tokyo Rain • Tokyo Rain
LAKEY INSPIRED - Chill Day • LAKEY INSPIRED - Chill...
Infraction - Serotonin • Vlog Lo-Fi Chill by In...
LAKEY INSPIRED - Blue Boi • [No Copyright Music] C...
Harris Heller - Guilty Spark • Guilty Spark
PRNV - Happy High • Happy High || happy lo...
Harris Heller - Streamline • Streamline
Sascha Ende - Finger ins Ohr • Sascha Ende Finger ins...
Harris Heller - Path Less Traveled • Path Less Traveled
LuKremBo - "biscuit" • (no copyright music) l...
Harris Heller - Golden Age • Golden Age
Harris Heller - Iridescent • Iridescent
Mellowind - Haii - Hry
What do you think? What do you agree/disagree with?
Btw, this is the first time I’ve ever made an opinion/rant style video, so please let me know what you think! :)
Have a great day!
I understand all of your points. I also think that its cool that mojang is bringing more components that arent useless. (Skulk sensor, im looking at you 😂)
feel like everyone else in the community is doing the rant videos, this ones so much better than that though, actually discussing why it's not ideal for your field of redstone piece by piece
review every redstone component like an unboxing video now!
Basically this video = my thoughts, but I think it’s a bit more useful in silly small circuits where you just need a t flip flop.
I feel that the reset is the most annoying feature about the copper bulb. The copper bulb will probably be used more in Bedrock for counters as the Java synchronous counter design doesn't work. Without a good way to reset the bulb, designs are very large which is unfortunate. I would have liked if any additional Redstone pulses also toggle the counter, even if the bulb is being powered. The pulse shortening to 0 ticks is a bit of a weird change. I would have preferred if they make the normal bulbs 0 ticks, the exposed bulbs 1 tick and the weathered bulbs 2 ticks. This would give the other blocks more use that just light levels and also appease the general Redstone community.
For computational Redstone, I think most people will just switch to these as t-flip-flops as they are easy to build.
I don't really know much about redstone, but it sounds like copper bulbs are a perfect replica of secondary storage. Most of your arguments against copper bulbs are about them being difficult to reset, but I think this actually gives a greater correlation to real life computing. Redstone lamps are volatile (like RAM) and need a signal (power) to stay on but copper bulbs are non-volatile (specifically secondary storage) and something like barrels is read-only memory as you mentioned. Resetting/flushing your redstone storage is the equivalent of turning it off and back on again! Taking this into account, they would all have great uses in computation, it's just that secondary storage happens to not be used as much in redstone projects since if a redstone engineer wanted to save the state they'd probably just save it as a schematic or make a backup of the world
So copper bulbs are the SSDs of the Redstone world?
Oooh… drum memory (multi-level piston tape). Early drum memories soved the persistent state problem by erasing the drum after the read head and before the write head, copying the data forward if it didn’t need to be over written.
@@lilyofluck371 Considering that HDDs are impossible to make in Minecraft...
non volatile memory is great in real life because it can preserve data in the case of a power outage, and that it allows machines to save data without being powered on 24/7. Redstone fortunately don't have this problem. They don't have a power source, so power outage isn't a thing, and it's not like you'll ever need to "turn a redstone machine off to save power". So in minecraft, volatile memory is just as good as non volatile memory, with the added benefit of not being annoying to work on
thats a fantastic way to put it!!
"I don't want my screen to have state"
That's a great point
this is also a good reminder of how compute shaders work in real life too. for the gpu to have performance, the shader has no state. the cpu sends whatever it needs to the gpu as a parameter, then each pixel computes and spits out the color before moving on to the next step just as quickly. no time for storage, so no time for sending anything back either.
@@Wilker_uwuWell, the GPU _does_ have storage, but you shouldn't be sending it back to the CPU because it's extremely time inefficient and laggy
It's not really, but tbf he couldn't have known that if you have a three tick repeater into an observer then a bulb, you can treat them like a redstone lamp. This would be worthless, except that now you can wire displays with observers, which makes matrix displays and dense segmented displays easier to wire
9:43 is a Turing complete machine. Increase the size of the feedtape and allow it to reverse and you basically have a full computer. Its not just memory.
it is quite literally a turing machine if made to infinite size lol
@@edwardmighetto7327
But can one do it? How big and can you reverse it?
you still need some form of instruction set to be a real turing machine, but this is basically the tape part of one
@@edwardmighetto7327also it can easily run regular br@1nf✓(k
Composters and cauldrons could already do this
Mattbatt in his video: tbh, it's just that I wont use them that much.
Mattbatt in the title: I will NEVER EVER touch one of these things...
"mattbatt" i like it
But hey, thats just a clickbait. A GA-
I think you're heavily underselling just how useful T-flip-flops/inverting bit patterns are, especially when movable. They can also be used as extremely compact XOR, if the inputs don't arrive at the same time (if no signal arrives, they stay OFF, if one signal is ON they are ON, and if both signals are ON in sequence they turn OFF again). I use un-synchronized counters all the time since they are so compact (even more so with copper bulbs) without issues. It should also be possible to use that piston-square trick with moving bulbs to make a super compact buffer/queue/de-serializer, where inputs are saved at on point, read at a later point, and then reset with an observer. I like how they clearly show their state visually as well, I tend to have to put lamps all over my latches to visualize which bits are set, now that is built into the storage block!
instead of using barrels, i use lecterns with 15 pages (it leaves room for other items in a saved hotbar, and can be switched on a whim)
I myself find it easier to sacrifice two saved hotbars, because I never needed ten of them, and you can't build on lecterns, so they aren't as compact.
But do whatever you find easiest!
@@caspermadlener4191 if you shift-right-click on a lectern, you can actually build on one (you cannot place redstone on it, but still)
Lectern are far more laggy but if you replace it by barrel once you finish it will be better.
@@antoinespadone7834 that is a fair point, but i do not notice the lag, as i usually do not use them by the hundreds
There is his redstone tools mod
I think the problem with all these examples is that you're only using them to try and replace lamps, which wasn't their intended purpose in the first place. Once people find niche uses for them (e.g. HDD storage, programming) it'll become that much more useful for those things
I just think of copper bulbs as a completely different thing than redstone lamps. Both can be used for different purposes and both are still useful.
6:50 I can definitely see the Copper Bulb be used for Rom, specifically programmable ROM. Provides a really easy way to change the memory of the device while debugging without having to break or place blocks just by pressing a button.
me and a friend developed an instant 0 ticking rom feed tape, so I think the copper built would be great for fast r/w memory
2:36 if the user knows the slightest bit about the copper bulb then they know it can only exist in 2 states. Even if they didn't know that, they'd realize it after clicking it once makes it stay on
Right? What about a floor display with buttons on the front? Levers could be placed either way, which is infinitely more confusing than having a button that lights up a lamp. Who the hell would use a toggle light to send a single pulse?
@@eli334-1 Even with levers on walls, it can still get confusing because many people are used to the idea that up is on, and levers are the opposite. Even if someone is used to the way levers work, the person building the circuit could still have inverted the signal to make them work like light switches.
There's also nothing preventing a lever from being used as a pulsed input, they're actually better at it than buttons are because buttons give a long signal but lever+observer gives a 1 tick signal.
it's not about Minecraft knowledge, it's about user experience design. Everyone on the computer knows by experience that little things going side to side is a yes or no choice. That's because it follows an unspoken standard you'd notice everywhere, like the settings app on your phone.
While both options work fine if the player is focused on the lamp, the lever option is more clear about the purpose, and a button that toggles (unlike normal buttons) is ambiguous.
@@erich_ika And then there are checkboxes.
The idea that a button + lamp that stays on is less intuitive than a lever is nonsense. The only possible argument there that isn't garbage is that the button might be harder to see than the lever, except the lever being disconnected from the light actually makes it harder for people to make the connection between the two.
@@SirSpence99 well hold on, no need to get heated. I'm not here to argue, I'm here to argue, just showing a different perspective.
Let's put it this way: All I'm saying is that if there's a lever, I know it's a toggle. If there's a button, it might do anything. And this property is valuable.
suggestion: build "wireless" data transmission by sending a flying machine with copper bulbs storing data and then receiving them at the other end
That's stretching the definition of "wireless" lmao (I love it)!
That's actually so clever
Thats acually a good idea/project
Thats acually a good idea/project
Thats acually a good idea/project
i do really like the rotating storage at 9:27, if it was on a piston, you could switch data sets, meaning you could even make a select screen, and if you use your extendable piston logic, you could have a virtually infinite amount of data sets.
Thats pretty much how hdds work irl!
9:51 drum memory was one of the older methods of storage as was magnetic tape so this might actually be pretty useful .
"Use the right tool for the job." In this case the tool in question is basically a T-flip-flop, so don't try to use it where you need a different logic component. Personally, I will probably only use bulbs where I need a TFF
T latches are actually somewhat popular for real life memory. the advantage is that it reduces the number of i/o lines. SR and gated D each require 2 inputs, T only needs 1. of course that means you now have to read every time you write, and writing is rather slow. so it's only useful if you plan to read a lot more than you write. if you don't have to write fast, why dedicate more wires to writing?
main uses i have planned for the bulb are cases where you need a toggle state but the state itself doesn't actually matter (mainly observer tech), and off pulses (also observer stuff).
one other nice thing is that bulb -> comparator -> observer makes a very simple monostable. which actually makes me kinda annoyed that observers can detect the little red dot changing. if observers could only detect the lit state, it'd be the ultimate monostable.
5:39 I immediately asked myself, why wouldn't you just use a copper bulb in this design to make it look better?
There's no point in replacing the note blocks with copper bulbs because then you need to add an input like buttons which will then dilute the image anyway. Might as well just use note blocks because those are already player-interactible
@@nichard101 Replacing the note block might not make much sense (just slap a button on a bulb though, it still looks nicer than janky pixels) but you could replace the lamps with bulbs so you don't need to store and repeatedly send the current state, which should make for a more compact screen.
@@GremlinSciencesthat is pretty ironic that his example against copper bulbs could’ve been improved with copper bulbs.
One bulb with a button and 3 bulbs that get toggled with the button as well and voila, a readable 2x2 light-up display without constant observer ticks
Having made one copper bulb computer and working on a second, I have to say that copper bulbs can be used for really interesting data storage and computation systems, it requires a very different non traditional kind of architecture. I used the bulbs to make a really interesting hybrid 16x16 screen with 8x8 inputs, but then in order reset it without command blocks I have to give it much longer input pulses and might need to limit how often the screen updates. I also made a better rippling up/down binary counter, I should probably make that it's own video soon.
Lots of really weird trade offs, some of the UI stuff is up to preference but it is disappointing how many things have a clear and final answer.
Thanks (again) for featuring my build. Now that I watch the full context, I can say more. I'm researching copper bulb as RGB screen and I don't really thing resetting is a problem for copper bulb screen. Well, we can just use observer to observe redstone torch behind them. This is actually not very useful and inefficient because we can just use redstone lamp which is faster and smaller. But it's very useful if you want to make RGB screen using copper bulb.
The actual problem is RGB screen only work if it is big enough and you are far enough. So for fellow redstoner who want to research this block as RGB screen, good luck.
"Wow, we really like this thing you added! Thanks!"
"No."
"What?"
"It's gone."
mojang doesn't fail to disappoint
3:00 i think that by using copper bulbs you are signifying to the user that you are using a toggle
for reset, you may be able to make it small by just running its output back into itself (if you did that i’m sorry i missed it)
you know the copper bulb is bad when they nerfed it AND it's not even that great as a t flip flop
see last chapter of the video?
why isnt it a good t flip flop, i thought it was great as it made t flip flops 1 block
@@MenaVoldey you still need a comparator output lol. and you could already make tiny tffs with a comp reading a dispenser with powder snow
I feel ya dude. :(
CRAFTY PLEASE JUST WATCH BEFORE YOU SPEAK YOU SAY THIS EVERYWHERE, UNDER EVERY DEVS TWEET, AND CZcams?
Actually what about reading(/write) a sequence of data? Because a copper bulb can be pushed it might be better.
The pushing mechanic makes me think of old turing machines. Like the simple sequence of 0's and 1's moved back and forth. I wonder if anyone has made it yet
@zelioz848 several people in CraftyMasterman's discord have made copper-based Turing machines, and my latest video is a demo of my own design.
Ultimately I feel like copper bulbs are never the perfect fit for a lot of computational redstone stuff because they are stateful. The standard in computational redstone is to work with direct values of 1 and 0 to avoid state, and generally to work with copper bulbs you want pulses and observers and stuff.
For memory, I'm guessing the copper bulb will overall not be good for making the standard type of memory more compact, but the piston based stuff would be really cool for making a slower but vastly more compact memory (like a hard drive compared with RAM). If reading things sequentially, it probably wouldn't even be slower, given the bulbs would arrive in order. So, perhaps good for large files that are processed sequentially but can be modified? Or could be used to store large amounts of memory that are bulk-loaded into a cache by spinning one full slice of the disk.
There are plenty of cases where you want state, even if it isn't the majority of cases, I see them coming in very handy in those special cases!
@@Takyodor2 i just know you dont for basic gates. one person was like "yeah you can make a tiny xor with these" and its like you *can*, but its a terrible idea, will fail on bad input timing, overall not the right move
@electra_ There are cases where you know two values to be XOR'ed will arrive at different times, though. Copper bulbs aren't an obvious replacement for something existing in all situations, but they are better under some circumstances.
Friendly reminder that Kingbdogz said on Twitter that the 1gt tick delay was intentional from the very beginning
I agree with your point, but they can be used for one thing: screenshotting a redstone display. You just write the data to a blank copper bulb sheet and it'll stay there.
ram memory with copper bulbs are smaller because the xor is commun at the end , you don't need a xor for each bit , treat it like a destrictive write xored although speed get a little hit because of the write back if the bit doesn't change
Terraria's wiring (its version of redstone) actually works similar to copper bulbs - in the way that power works in pulses so everything gets toggled instead of constant power like redstone does it.
9:50 makes it possible to have video storage without massive data modules - and I'm sooo going to test this
I feel like copper bulb feedtapes are just begging to be made into a Turing machine
Not sure how plausible it would be to build because of solid lamps, but what if you combined the display at 5:40 with the copper bulb approach, allowing you to press a button on the bulb to get instant feedback as well as pressing directly on the screen, but it doesn't remove one block per screen pixel like the noteblock would?
Maybe due to the input? With noteblocks it's a pulse, but with bulbs, it's a constant output. Maybe the redstone was a little more difficult? But i dont know for sure, it does sound like a good solution though
@@zelioz848 I doubt it, since the only block that can read the playing of a note block to activate redstone signal is an observer, which would react to seeing the block state of a copper bulb change just the same as it would react to a note block. But, depending on how the other 3 lights get powered, one may need to worry about the solid lamp blocks causing the bulb to get powered again, turning it off. But that's but a best guess based on the hunch that it's for some other reason than "I didn't think of it".
could maybe do the 1x1 pixel version with normal lamps by using skulk sensors at max distance from the buttons
Very interesting take on these blocks!
The 1gt delay was really nice because of the limited ways to make a delay that short without making a difference 4/6gt - 5gt circuit
really a shame Microsoft removed it
woke up literally 2 minutes ago and i’m blessed with a mattbat video 🙏
*i'm in bed next to you*
same
Using T-latches in RAM can be a bit annoying, since you have to read the register before writing to it. But I think it's worthwhile tradeoff if it makes the RAM highly compact, especially if you're using it as a large secondary storage. I can easily see this sort of thing being used to store kilobytes of data.
But using T-latches also means that you can do inversions directly in-memory, with no data transfer. You can perform these operations during both read and write. This would allow you to perform some of the ALU logic in memory, and do the rest in a simplified near-memory ALU. You can also do XOR and XNOR in-memory in certain cases.
My first thought when the copper bulbs came out was a read-write memory tape haha
TLDR: Copper bulbs are not redstone lamps, and copper bulbs don't behave like redstone lamps.
You could also use a small bulb tape that cycles as the RAM is supposed to update, so it writes a 1 and pushes it into the read position when it's supposed to write a 1, and just pushes a 0 into the read position when it's supposed to write a 0. If you run this tape vertically, you can stack 4~5 bits vertically on one tape if you wipe the tape right after it gets read and before it gets written, and if you invert the read/write positions then a single vertical loop could handle 8~10 bits. This design would limit the ability to update any single bit on it's own and would require all bits on the tape to update at once, but it should still give a smaller footprint, and each bit could also be made to use its own smaller bulb tape if independent updates are required.
EDIT: found a more compact way to write and wipe the bulb data, you can stack up to 14 bits on each leg of the tape without issues on that front, just need a _lot_ more pistons and a good timing circuit.
Copper bulbs can be used for:
-Ram
-XOR Gate
-displays
and more
Reset lines for the bulbs are super easy and expandable when dealing with feed tapes, and while the circuit isn't super small you can read out thru it.
Hold up. If you can move copper bulbs without them clearing what is stored, could you make something like a magnetic tape that can store info.
What if they made a redstone lamp with 16 different states? give it redstone signal of 0 being off, and 15 signal being full brightness. So you could have displays with shading.
One use I've found for copper bulbs is that you can make a 2 tick downwards vertical infinite one-way or/and gate with them, if you use wallstone. You can use trapdoors to pillarize a tower of walls, and read the change in wall state with an observer. Hook that observer up to a copper bulb and boom, you just turned an observer pulse into an on/off toggle. Could be very useful in reduction operations for more than 8 bits.
Genuinely even if it's completely impractical, the visual look of a spinning memory disk is so cool.
The only think i've thought about that wasn't covered here is an "infinite" storage system using 0tick piston extenders to push a byte of data to and from the read/write head, but haha that's way beyond me. Good video! Really insightful.
I may not know too much about redstone, but I will say, this video did such a good job of honestly covering a lot of the strengths and weaknesses of the copper bulb I feel like, obviously you did a great job showing how it's not going to be optimal for your set ups, but it just makes me excited to see what does get made with them! Whether that being interesting use cases that are found with redstone, or just really compact nice setups that can be used in builds!
I understand the point of the video, but I feel like you're somewhat missing the point. You take the bulb, try to replace the lamp in circuits that were designed for lamps and wondering why it's worse. The circuits were originally made for active displays and not toggles, so of course it will be worse. I feel that people just haven't yet discovered the ways that the bulb is better, since it's so new. I like the video, but I'd like if it could show that this is only an opinion considering the things thus far, but the future could show more uses for them when they're discovered
I love your content! Thanks for being a fantastic youtuber and an inspiration to me
Just got a working turing tape machine with heavy use of copper bulbs, here are my initial thoughts:
- I was able to make a 1 wide tileable d-latch using copper bulbs. It was fun to make but repeater locks still make better d latches of course
- Bulbs work great with wall stone, just because their such good t-flip flops
- The copper bulb xor is very nice
- Bulbs are good for small counters since you can usually get around the delay issue just by adjusting your repeater timings
- You end up with combinational blocks that are made with synchronous components, which can mess things up if accidentally toggled
Over all I would agree with most things you said; other than as a dense form of tape memory I think traditional components still have the edge over copper blocks in logical redstone.
9:43 oh that one is so cool, reminds me of the memory drums from those vintage computers the size of a wardrobe. or, just a worse hard drive lol
5:36
Would be cool to have connectable lamps and copper bulbs
i made read-write memory using copper bulbs, but to solve the issue of not being able to set a 1 or a 0 easily, i just attached a bitwise xor to the start of the unit. so to write a byte to an address it reads the address, does XOR with the value on the main bus, then writes to the address.
11:50 Incrementing with lamps changes the number from 7 to 15 to 8.
12:01 Incrementing with bulbs changes the number from 7 to 8.
I like the bulb version better because it lacks the awkward moment of having a rogue output of 15.
Most of the time your point boiled down to “don’t use copper bulbs where a lamp would be appropriate”.
Note: A XOR 0 = A - hence to clear a copper bulb screen, simply set each bulb to it’s current value - is that easier than clearing a lamp screen? No but see previous point.
More generally, I actually agree that after my initial excitement died down, I’m having a hard time seeing what, if any, circuits they would improve. However, I expect to be surprised over the next few months.
A spinning read/write design is basically a rudimentary type of disk. We already are getting disk writing capabilities inside of minecraft
Using it as a hard drive though could be useful for timing or maybe as tapes so you can play music as it would make it more compact for anything that needs to be played and I could see it useful for concrete powder screens and I’m considering using it on my internet system I am trying to build in survival
The very nanosecond I saw the spinning memory setup, my first thought was "somebody is going to make a music box with an actual song scroll now"
And I'm already impatient to see that happen.
it would be cool if like, if it recieves a 1 tick pulse or a low signal strength or something it would reset to off
but theyre never gonna do that..
or if they could store signal strengths and light up with different brightnesses depending on it
The whole “levers signify toggles better” thing is very overstated, contextually you can almost always tell if it’s a toggle or not, like if it’s a binary input you can assume it’s a toggle. Plus buttons look better.
"Actually, one of your personal reasons for not using them is very overstated and I can with context tell if something is a toggle therefore you must too; following that my opinion (which as stated, is correct) - which is that buttons look better"
If you can't tell what I'm getting at: this is somebody's own opinion about why THEY are not going to use it. Not only does it not really not affect you in the slightest but also also you are telling them your opinion as a counter to theirs because you have a bias to it thinking it's correct, AKA Get a life.
@@hellvet3 It's almost as if Mattbat asked for opinions in the comments. Imagine whining over someone explaining their take in the comments as a response... 🤦
@@hellvet3 yes well you see, the point of the comment section is to tell people your opinion for no fucking reason with very little chance of it ever being seen. (Also mattbat says in the pinned comment that he wants to hear what we agree/disagree with)
This video was very informative. I learned a lot. Not just about copper bulbs but a lot of other stuff about Redstone logic circutry. Very good overview of Redstone logic circuits! I think copper bulbs was a good addition because they have nice features but they are not to advanced. To advanced meaning making Redstone to easy.
I find this very similar to coding. Adding more features doesn’t necessarily mean better code, often in means more complicated and confusing code. The copper block will definitely see use in bit storage, however I don’t see it as a target block 2.0 or any other big game changer.
a button looks like more of a toggle than a note block
I needed a non glowstone (non nether) solid light block that looked…well not blue and ugly like the sea lantern. Something logical and preferably with the ability to turn on and off.
After years the core game is giving me exactly what my build needed, so I am very happy.
love this video matt i do agree with lots of this
As someone who deals with UX design frequently, I disagree about the lever feeling more like a toggle. It feels the same. Most toggles online are checkboxes, so just a small button, and everyone intuitively knows how that works.
I wanna see a video where you do redstone in Minecraft Beta 1.7.3! XD
with the jukebox's being able to co-op with redstone you can now store binary in in shulkers, just requires alot of discs
and instead of sending it one signal at of time you can send a hopper cart filled with shulkers with binary so you can send data between places
shulkers are the new floppy discs
If you have a copper bulb binary counter and set the comparators to subtract mode before putting a repeater into the side, if you toggle all repeaters at once it inverses all bits but the least significant.
Thanks for your uplosd scedule
One major thing: copper bulbs are by far the best binary counter in the game, and since they are movable, it gives you a way to count an input, store it, move to a different location, and read it, which is pretty major for binary storage. It also makes bit shift operations stupidly easy as you can literally shift the bits. Timing isn't really an issue as you really should be using a clock circuit for your read/write operations, so unless you have a really large binary counter the delay shouldn't affect it too much.
Levers don't work on copper bulbs? Some of your arguments against copper bulbs seem to apply more to levers vs buttons.
There's no reason to use a lever on a copper bulb instead of a button, and would make it more annoying since you would have to flip it twice.
Thank you for your work. through your Videos my interest in Computer Science became so much higher than it was before!!! Realy Thank you very Much!!
As a general redstoner, I really like the bulb, and it's really fun to experiment with. What you're saying makes a lot of sense though. It's surprising, because I thought this would be one of the fields where the copper bulb would shine, but you explained very well why it won't. Oh well, maybe in the future people will find uses in this type of redstone too. I remember people being disappointed about the observer when it came out because it seemed useless xD
You make so many cool redstone builds, but never tutorials on them. that would be so cool
We NEED a way to set it to off, regardless of if it is on or off. It should just become 0 no matter what whenever it receives a redstone signal
The read/write memory for copper bulbs is the same reason it's downright impossible to make computers in Astroneer: the devs want you to use count repeaters, but they don't act like nor latch, they act like toggles; ultimately, this makes set/reset an absolute nightmare. Combine this with lackluster duplication tools (can dup platforms, can't dup the wiring), making a basic computer means you don't have a life. Funnily enough power switch became more useful, but the dup issues still applies and large scale applications are better left to modders.
Yeah I made a calculator on that game once.
@mattbatwings can the next video be on memory banking and segmentation. It's a very interesting technique that I need help understanding. Hopefully you read this message. Love your content never stop.
I think it would be a good idea to make it so that the copper bulb would work in a way where the more oxidized it is the more delayed there is (no delay before oxidization, 1 at stage 1, 2 at stage 2, 3 at stage 3)
For the screen part with redstone build, it's not very complexe to reset it, you just need to resend the signal for the last screen and it will shut erase all
Instead of a Xor latch, it's easier if you just use the signal to wipe the cell and then one tick later write the new value. Repeater latches already have a tick of delay for write so it doesn't even change the timings. And the wiping circuit is easy and can be done in 0 ticks now that the bulb has no delay. Just connect the output to the input for one tick, then connect the input for one tick. You can even create a massive memory array and using a timing circuit to wipe one row of memory and then write to only that row, allowing for a single input bus that writes to an entire array as long as you time your inputs to match the clock circuit.
My thought when you showed the circular read-write design is that copper bulbs are actually great for at least one thing: "hard drives" or "tape reels". you could write data to the blocks with a single "write head" or a "read-write head", and then push the blocks into a space for storage. Of course the push limit of pistons makes this a bit complicated, but it's certainly not impossible to create an "infinite" track of blocks pushed by pistons, or to arrange those blocks densely, and then pull them back out of that dense arrangement. As long as the blocks don't get out of order, you could save a lot of data to them. This probably isn't a super high priority, since this kind of data storage would be slow, far slower than the "solid state" read-write memory currently in use in most logical redstone. But, say you want to, idk, build a text editor that can display and edit the entire script of the bee movie, for whatever reason. this might be a more reasonable way of handling higher volumes of data in that sense?
You can use a copper bulb to double the length of a clock and I used it to make the smallest SR Latch that i know of (4 x 3 x4), and a 3 x 3 x 3 XOR gate
You were actually really close to the answer with your reset operation on the feed tape. All you need to do is have a comparator output feed back into a locked off repeater that is then unlocked for 2 ticks when you press the clear command, or when you press the write command while delaying the write function until the clear function is completed (a delay that can be achieved with a single repeater). This is relatively compact and easily tileable vertically.
Copper bulbs are basically an in-game equivalent to optical media. You can write to it only once, but at least it's somewhat convenient to read from. And with the fact that they can be pushed by pistons, they can basically be used as a DVD. Theoretically, you could write to them and then use the read cycle thing to both read and reset them, allowing you to load multiple programs into the same machine. Don't know how useful that is, though.
i dont really plan on usinng redstone for the purpose of a computer, just farms and doors XD. so a simpler t flip flop is nice. (aka a copper flopper) it’s exactly what i need.
they should add stained glass bulbs so you can have multi color displays not that it's really needed cause it's possible to use pistons and stained glass already but it would be simple to use when building them next to each other making 16 by 16 screens or it could be possible to use lightning rods on copperbulbs to have a red green blue screen
You just accurately summarized all of my conflicting thoughts about Copper Bulbs. I want them to be cool, but there's little that they can do that can't be done by something else, often better.
Even programmable piston-tape already existed, just have a block-swapper insert/remove solid/transparent blocks.
It can also store 4 states instead of 2. Using observers, that means you get two updates per press.
This can be further increased with the 4 weathering states, and the wax on wax off states.
Im not a logic redstoner, so im not sure how that could be used, but it may prove useful for something.
in computational redstone i found they're great as a redstone block alternative that doesn't bud pistons and still gives a 15 redstone output
1) with the aesthetic aspect of toggling, the bulb lights up when active, and is in the same place (for the player) as its respective button.
2) not using them for interactive screens is fair enough. (Edit: control panels I like, but the screens are more-less as you described.)
3) copper bulbs as memory is something that even I am undecided on. I still think that memory would benefit from the decorated pot. achieving any given signal strength is easier (using items that only that to 16 for obvious reasons), as long as you mind the increment delay with item 9 (I use a dropper triggered by a strength of 8), and I have used a simple hopper system to rewrite the signal strength (although I expect this aspect to go unused).
4) I have made several automated binary counters. It lead to me (on your ORE server) discovering a twin-hopper clock that can lock super easily. By themselves they could be useful, but it's too early to know for sure.
5) I saw that Mumbo video, too, and he's why I first started messing around with Redstone with more serious intentions. I agree with you on this one quite definitively. "And don't forget: please ubscribe..."
6) that is a _very_ misleading title.
Jooo Matt, i am following your videos for quite a while now and i am currently trying to Upgrade your 8 Bit Calculator to 16 Bit, but i am struggleing with the synchronyzing between the 2 8 bit Modules, is there by chance any possibility that you could make a tutorial for that? Would realy help me alot because you have a so amazing style of explaining / tutoring things
For the reset problem, couldn't you store the data on another array of copper bulbs, and then read from that onto the original screen?
i also thought about it; if you had 2 sets of copper bulbs, flushed the data to the "buffer", and then flushed the data to the actual screen, then it would automatically store current state and xor everything properly. i'm not much of a redstone person tho, so i don't know if there are hidden problems with that
edit: okay i'm stupid, it only works for 2 writes 💀
edit2: you could do that with some "classic" redstone, but then it becomes kinda like reading the copper bulb state, you just have more convienient access to it
6:09
When it came out I had decided to continue with my repeater-lock Memory because of how simple it is to write a 1 or 0 regardless of the state
I disagree with the idea that copper bulbs don't make good screens. by hooking up a screen signal to an observer and then a copper bulb, you can functionally treat copper bulbs as redstone lamps. this would be worthless, if it werent for the fact that now you can wire the screen with observers, meaning now you can miniaturize those old 2 by 2 redstone lamp screens to be 1 by 1 with this observer to copper bulb setup. there is a limitation that the signal can't change once, and then again the next tick, but you can filter this signal with a 3 tick repeater
3:30 i was hoping he would say he uses "item frame with Redcoder" instead. I fell in love with this component, Just put an arrow in the item frame and 8 Signs around it. It is small and the user immediately knows it can only be in 1 of 8 states
An eloquently put and logical argument
Well thought out 🏆
The tape disk is cool and all, but if we're going for read-write sequential serial access memory, a similarly sized comparator loop can probably do the same job much better, especially if you're willing to preserve the full signal strength information in the bus, at which point it should read and write 20x faster.
Of course you would not use copper bulbs instead of normal redstone lamps. But I bet there are some circuits that use copper bulbs and were not possible before. Just like we use hoppers for clocks, bulbs have more mechanics than just input/output
i use them as compact t-flip-flops and XOR gates. i really wish there was a way to set them to 0 consistently, though.
they are VERY good when something else just wont fit- for example, i was able to make an inverter for my ALU in a 2x2 space using copper bulbs.
I see the bulb as a way to store data in this context, it would be easier to read and more compact for more advanced computational builds.