AkBKukU

I have restored a Data General MicroNOVA that also uses octal. It has an emulated front panel over serial and uses octal in multi-digit commands like specifying which address you want to boot from, "33L" to book from an MFM disk controller for example. That is probably a legacy carryover from the NOVA 3 and earlier where you would be able to input the same thing into the front panel switches.

Fundamentally I wouldn't say octal is fundamentally easier to interpret other than hex because it's just half as many digits. The shorthand things about octal used in unix you mentioned all still technically apply to hex as well. The only really tricky part is where it becomes letters and you have to think if D or E is the odd value with the first bit set. If you were doing hex all day though, the 6 hex letter patterns would be pretty easy to memorize.

Personally I would say for front panel systems specifically was just about physical space for the switches. If you look up CPU trainers for something like Intel 8080 in the Altair 8800, you'll see it uses a hex keypad. Multiple 16b values would have been a lot harder to fit in single bit switches.

I think the bigger problem here is that "overloading" is specifically about providing multiple functions with the same name that take different parameters. You cannot truly overload in python, partly because it is weakly typed, and mostly because function names are a key in attribute dictionaries and must be unique.

The article is showing function overriding, not overloading, which is just standard class inheritance stuff.

Minecraft comes in two flavors, Java and Bedrock. All of the mobile, console ports, and windows store versions are based on bedrock. Java is the one you download directly from the website. Bedrock isn't really about custom hosted servers, but there is a way.

You can run a standard Java Minecraft server however you like, and then you can wrap it to also work with the Bedrock using Gyser[1] which will protocol translate it on the fly. It can require some workarounds on the more restrictive bedrock clients but it does work. That will let you setup and control the server from Java which has more options available.

[1] https://geysermc.org/

I received a response stating something similar on the git repo. It is still incorrect to blame the controller, and I suggested instead to provide some compatible drive models to use instead like they already do in the more generic sections of the article. It should even be possible to to use the Mac drives with the Greaseweazle with an adapter because the 800k drives from the Apple computers are just Sony drives with an optional eject motor installed.

Unlike the Apple II they do not have a custom Apple PCB. It's possible Apple requested some tweaks when ordering from Sony but I don't think they are all that special. So it should be entirely possible to read the disks with other drives. Based on the information in the page you linked stating any 720k drive is compatible, I suspect the higher read rate may be a vestigial feature that Sony over spec'ed during the introduction and standardization of the 3.5in disk.

I do a lot of floppy imaging and some of my work on it has previously be discussed here[1]. I do not understand where they got the idea of "there are a number of disks that the Greaseweazle struggles to capture, namely the Apple formatted disks. If you have these disks in your collection, you may need to use an Applesauce controller."

The Applesauce is a macOS exclusive tool that has a contingent of dedicated users. While I have not imaged a wide sample set of Apple II and 800k Mac disks specifically, from my current experience the Greaseweazle is plenty capable of reading them. I would speculate the author was trying to use an included diskdef(a flux to binary decoding definition) for an incompatible disk. The Zone Bit Recording[2] Apple drives use is irrelevant when you increase the sample rate of the controller to accomplish the same thing. Similarly C64 disk drives are also ZBR but change the clock rate instead of media speed. So do not think that this means you need multiple drives and controllers when getting into floppy imaging, you can use standard PC drives with a Greaseweazle to read and write Apple II and Mac disks as well as almost anything else.

I have opened an issue on their github page for this site to seek clarification on this.

[1] https://news.ycombinator.com/item?id=39495973 [2] https://en.wikipedia.org/wiki/Zone_bit_recording

> Killing some processes to free up memory

This section is disregarding a key lore element, the inhabitants of the grid are programs. Killing a process in this context more likely has an interpretation of an attempt to stop an individual such as the villain Clu. I would say an alternative explanation is is more story based, with Kevin Flynn trying to stop Clu from the outside world but being unable to and instead taking the last resort of entering the grid when he knows it would be dangerous.

> can't afford to pay one for whatever business I have

At small scales what "art" does your business need? If you can't afford to hire an artist (which is completely fine, I couldn't for my business!) do you really need the art or are you trying to make your "brand" look more polished than it actually is? Leverage your small scale while you can because there isn't as much of an expectation for polish.

And no, a band poster doesn't have to be a labor of love. But it also doesn't have to be some big showy art either. If I saw a small band with a clearly AI generated poster it would make me question the sources for their music as well.

I've been editing on linux with resolve since the launch of the BMPCC4K in 2018, were you trying to import MP4 footage? BMD can't be bothered to pay for the AAC audio codec for linux users even if they buy studio. So if you pay for studio you can read the h264 video stream but not the AAC audio. I end up converting everything to MOVs with pcm_le16 audio as a workaround.

The ALSA issues are beyond aggravating at this point. You do not want to actually run ALSA directly, you need it to connect to pulseaudio on 24.04. But I still have never been able to record audio within resolve. I've had mixed luck on newer wayland+pipewire setups with having to install the bridge packages to connect the different backends. Linux audio is cursed on its own so I don't fully blame BMD.

I exclusively run Kubuntu and have been using makeresolvedeb[1] for installing resolve and it has been pretty good.

[1] https://www.danieltufvesson.com/makeresolvedeb

> Some games are designed around content and "extraction". Many are not.

While I think the parent post leaves a lot of open ended questions, I think they are spot on about the tightness of design in games.

In many open world RPGs, or something like GTA, you cannot open every door in a city. In street fighter you can't take a break to talk to your opponent. In art games like Journey you cannot deviate from the path.

Games are a limited form of entertainment due to technical and resource restrictions, and they always will be. Even something as open ended and basic as minecraft has to have limits to the design, you wouldn't want the player to be able to collect every blade of grass off of a block just because you could add that. You have to find the balance between engaging elements and world building.

Having a LLM backed farmer in an RPG that could go into detail on how their crops didn't grow as well last season because it didn't rain as much seems good on paper for world building. But it is just going to devalue the human curated content around it as the player has to find what does and does not advance their goals in the limited time they have to play. And if you have some reward for talking to random NPCs players will just spam the next button until it's over to optimize their fun. All games have to hold back from adding more so that the important parts stand out.

> Yes - some things go out of fashion for a while, but trends almost always cycle back.

Exactly, this is even supported by Nintendo's own services offering emulation of their older systems. There is clearly demand for the ability to older games.

Capitulation to an "inevitable" fate of download only games is just taking the easy way out by not sticking to your own core values. I have personally pre-ordered a Switch 2, but I will not being purchasing any online only cartridges or download only software.

We haven't had the watershed moment that brings it into focus for gamers at large yet, The Crew was close. But Nintendo has kept the download servers going for all of their systems which has provided a false sense of security. Once those start being shut down maybe we'll see some actual response. Though with the introduction of Gamecube emulation on the Switch 2, they are only a small step away from emulating the Wii and giving people another scapegoat for their lazy acceptance of lack of ownership.

This was decided in court[1] over two decades as acceptable fair-use and that thumbnail images do not constitute a copyright violation.

[1] https://scholar.google.com/scholar_case?case=137674209419772...

It looks like FFmpeg does support reading from sockets natively[1], I didn't know that. That might be a better solution in this case, I'll have to look into some C code for writing my output to a socket to try that some time.

[1] https://ffmpeg.org/ffmpeg-protocols.html#unix

I have a project that uses a proprietary SDK for decoding raw video. I output the decoded data as pure RGBA in a way FFMpeg can read through a pipe to re-encode the video to a standard codec. FFMpeg can't include the Non-Free SDK in their source, and it would be wildly impracticable to store the pure RGBA in a file. So pipes are the only way to do it, there are valid reasons to use high throughput pipes.

Look into the Domesday Duplicator project for Laserdiscs as an example of how what ssl-3 is talking about can be done using a high sample rate input. That exact process is possible and with enough storage and processing power can be used to get the most "low level" access to the data. It is not for the faint of heart though, and can take around 1TB of storage and hours of CPU time to process full movies in this way, I know because I've done it.

I believe I've seen there is work being done to attempt this on CDs but it would have still been in the exploratory phases and not yet ready to start archiving with. It might seem like overkill to do this to something meant to be digitally addressed but I've experienced enough quirks with discs and drives when ripping that I would 100% be willing to switch over to a known complete capture system to not have to worry about it anymore. Post process decoding also allows for re-decoding data later if better methods are found.

Even BIN/CUE is not enough. It cannot store subchannel data like CD+G and is only able to hold a single session which breaks bluebook CDs with audio and data.

We do not currently have a widely supported CD standard for storing data from a CD that can properly hold all data. Aaru [0] is close, but still has to output back to other formats like BIN/CUE to use the contents of the disc.

[0] https://www.aaru.app/#/

I'm curious if you have a specific example of an album with the crowd noise between tracks like that? I collect and rip hundreds of CDs and am always on the look out for edge case discs to further hone my tools.

On your pregap + 99 indexes remark, the "pregap" is the space between index 00 and 01 which continues on up to index 99. Players seek to index 01 as the start point of the track. There is no separate pregap designation. I've paid special attention to this because it is a difficult problem to solve as many discs have space between tracks stored in index 00-01 but rarely is there anything audible in there after the first track. The only example I have of this is a specialty music sample disc, Rarefaction's A Poke In The Ear With A Sharp Stick, that has over 500 samples on the disc accessed by track + index positions.

As a sidebar based on the later comments in the thread, I've made it a habit to rip and store every audio CD as BIN/CUE+TOC using cdrdao. This allows me to go back and re-process discs I may have missed something on. But that is imprecise even because it usually breaks bluebook discs with multiple sessions to store data due to absolute LBA addressing. Also the ways different CD/DVD drives handle reading data between index 00-01 on track 1 is maddening. Some will read it, some will error, and the worst is those that output fake blank data.

I became "pro-net neutrality" back in the 2010's when Verizon was trying to charge an extra $20/mo for hot spot functionality on my provider locked android phone.

After some rooting and side loading I was gleefully working around that until FCC came down on them for it [1]. Net Neutrality was passed after that and only seemed like a logical response as a means of consumer protection.

It has always been a user facing issue, it's just not one that many people seem to want to expend the energy to think about how it impacts them. Netflix isn't using that bandwidth, the users are. Without users, Netflix would use low/no bandwidth, just as it did when it was renting DVDs. The users are paying for their own access and speeds to be able to watch netflix over the internet instead. And in turn Netflix is paying their ISP to be able to provide that data. Punishing either the users or the web hosts for finding a more effective use case for the internet than just sending static pages is the ISPs either trying to find a way to blame someone else for having over provisioned their network. Or they are trying to strong arm web hosts into paying more because they have regional monopolies and can get away with it. As a consumer if I had a choice between two ISPs and one of them throttling Netflix to try and extort them for more money, even for self centered reasons I would pick the other just to have better service. But there are a lot of areas where that isn't the case and there is a single major broadband provider who has free reign.

[1] https://www.cnet.com/tech/mobile/what-verizons-fcc-tethering...

Not OP, but to provide some historical perspective, RTX hardware raytracing is very firmly a gimmick and it isn't AI nonsense that's going to be the end of it. It's going to go the way of PhysX, 3D Vision, and EAX audio. Cool, but complicated and not worth the effort to game devs. Game designers have to make all the lighting twice to fully implement RT, and it's just not worth the effort to them.

Nvidia's own site[1] lists a total of 8 Full RT compatible games, half of which they themselves helped port. There are far more games that "use" it, but only in additional to traditional lighting at the same time to minimize dev costs. Based on that and past trends, I would personally predict it to be dropped after a generation or two unless they can reuse the RT cores for something else and keep it around as a vestigial feature.

[1] https://www.nvidia.com/en-us/geforce/news/nvidia-rtx-games-e...

Apple doesn't need to support it, they need to not block it and let the user decide if they want to participate in a beta.

I am deeply steeped in the history of computers and the biggest three things I can point to as the reason (MS-)DOS won are:

- Licensing: Most computers either had custom operating systems that were not shared with other hardware vendors, or in the case of BASIC frequently, were licensed themselves.

- IBM letting the genie out: The BIOS on the IBM PC 5150 was cloned, quickly and legally, and other companies started making compatibles. This caused an explosion of computer variety in a few short years for a single platform.

- Microsoft: DOS usually means "Microsoft DOS", Microsoft also was responsible for many of the BASIC environments of early systems as well. The ability to buy your OS from someone else lowered the pressure on hardware makers. IBM also favoured Micorsoft's DOS over CP/M-86 and stopped supporting it quickly.

All this meant the PC compatible ecosystem with Microsoft DOS became easy to make from a hardware side, and lacked a single point of failure like Apple, Radio Shack, Commodore. Atari, etc. There were other MS-DOS compatible DOS's out there, but MS-DOS was usually the one shipped with computers to be as "IBM compatible" as they possibly could and gained dominance through that.

EDIT: To those who may not be aware, BASIC did become more OS like before going away. HP BASIC was extremely feature packed before HP-UX replaced it and was more capable than MS-DOS in many ways. It evolved far beyond just a programming language.

(I am the video/page creator)

This is the eternal struggle of trying to write about something like this on the modern internet. The video is the flashy thing that gets attention (and revenue which allows me to do this as my job) but the written part is just talking into a void and hoping someone notices. I agree this type of information is best presented in text which is why I made an effort to produce a written component as well. But there's no way that article would have ended up linked somewhere like here.

> One would rather expect this sort of functionality implemented in a high level operating system function

Almost counterintuitively, floppy drives were actually very fast compared to the CPUs early on. The DMA transfers were more to bypass the CPU than anything. For the CHS addressing some formats would implement interleave of the sectors (ie: 1,6,2,7,3,8,4,9,5). This would purposefully space sequential data apart so the CPU would have time to process it while passing over out of sequence data before encountering the next section of it. Putting more load on the CPU compounds this and was why dedicated FDC chips never went away.

Also fun fact,the usage of the ISA DMA interface is why you can't have full featured native floppy controllers on modern motherboards, that doesn't exist any more.

One problem is Blender's multithreaded rendering doesn't scale well to VSE work because it focuses on breaking up each frame and as a result doesn't well utilize multiple cores. I've experimented with making a plugin [1] in the past to start multiple render jobs different points in the timeline in separate processes and was able to massively speed up renders.

I have since switched to Resolve on linux as well but due to using Blackmagic cameras that work better with it.

[1] https://github.com/AkBKukU/blenderSubprocessRender

This missed all of the PC VR headsets from the mid-late 90s somehow which was where all of the interesting innovation was happening. PC VR and 3D was a huge market compared things like the relatively terrible VirtualBoy.

If you want to get your fix of probably the most influential era of VR, http://www.mindflux.com.au/index.html has been around forever as a timepiece of what was happening on the PC then.

That's a you issue if a show you like gets canceled from lack of profitability due to pirating. It is your problem.

> Fairness doesn’t mean that the system should be stacked in favor of anyone who uploads a video.

Agreed, however if a creator repeatedly violates copyright and gets the three Copyright strikes (which I recognize are distinct while will related to claims) it is deleted. For the the issuer though. there is no penalty for invalid copyright removal requests. This is the type of unfairness that is an issue. Additionally, the claim issuer needs zero proof they even have the right to file a claim. The DMCA is mostly unfair to the companies that host the content forcing them act against the uploader and have zero ability to push back against bad faith actors. So the system Google has implemented can only legally pass the problem onto the content creators.

> Do you have any evidence that a claim negatively impacts search and discovery?

No. Can anyone truly have a confident stance that X == Y when it comes to how Youtube presents videos to potential viewers through its black box "algorithm"? I've seen plenty of inexplicable things happen with video recommendations as both a creator and viewer that both make me question what can/can't influence and never make an absolute statement about it, hence the "likely".

> that sounds to me like a very pro-creator outcome

You glanced over the unfair part there. Having 10s of music audio in a 10m video because you walked past a restaurant while filming a conversation can cause drastically disproportionate amounts of revenue to go to the claimant. This part is Google's fault and is an overreaction erring on the side of caution to appease the claim issuers.

I also make my living from Youtube and I would strongly disagree that it is fair.

On the absolute most simple basis, false claims can be damaging to the creator but the same false claims are completely risk free to the issuers.

The problem shown in the OP is an additional layer of complexity where another company is contacting the creator on behalf of Disney which muddies the waters on who exactly is filing the claim and whether they have the right to.

The only thing in the Content ID system that is built in favor of the creator is if the claim issuer doesn't progress the counter claim and it is automatically dismissed.

This doesn't even get into the likely diminished recommendations the video will get after being flagged, the time wasted by the creator to manual fight things that can be spammed with the API (0), and the unfair revenue splits that can result if the creator did make an honest mistake.

(0) https://developers.google.com/youtube/partner/identify_conte...

Mine (I run Tech Tangents) is a 16500C and the interface is basically identical. The problem with remote access for these is that they draw traces to the screen using direct framebuffer access rather than X11 calls meaning you can't see them remotely. So the best you can do send them commands remotely and read the numerical results. That's why I went the VGA capture route.

The Greaseweazle can directly read/write KyroFlux stream files as well. The KryoFlux files are my preferred "archival grade" backup format because they also store multiple reads of the disk tracks in each file to get a consensus on a "good" read.

You can easily convert to other formats with the HxC Floppy Software.

(I'm the video author)

The focus was more on how the Sony drive became the standard and less about all the competing formats. The CFD was the only serious competition and, in the US at least, it never reached the levels of putting up a fight like the ZipDisk vs. SuperDisk or Blu-Ray vs. HD-DVD.

The Amstrad was the only system OEM I found that really used it, so while it did have some market it definitely wasn't wide spread to other systems like the BBC Micro, Acorn, or (Proper) Sinlcairs.