Gift links to how A.I. is shaping the use of drones in the war between Russia and Ukraine.
We're going to get this guy:
What can go wrong?
Gift links to how A.I. is shaping the use of drones in the war between Russia and Ukraine.
Thanks. I didn't read them because I don't want to give the NYT my e-mail address. I am guessing from the thumbnails in your post that what's new here is fully automated drone kills using onboard A.I. running on Nvidia chips.Gift links to how A.I. is shaping the use of drones in the war between Russia and Ukraine.
Unfortunately that wasn't exactly the case. Ukraine did field test fully autonomous killer drone with confirmed kills. They basically let loose autonomous killer drones and let them seek out any living humans and eliminate them within a specific geofenced area without any human involvement. They claimed it was a one time test. (Guess what might happen if the GPS signals get spoofed.)The AFU or the Defense Ministry of Ukraine stated this year that they have tested (in Ukraine) a fully A.I.-controlled (autonomous) kill-chain to destroy mock targets (last year if I remember correctly), but that they are not using such a system in practice.
www.audiosciencereview.com
Great choice !Thanks. I didn't read them because I don't want to give the NYT my e-mail address.
Thanks, I missed that post. My memory of what was mentioned in the videos I watched must be in error. I now watch over twenty YT videos a day about that war.Unfortunately that wasn't exactly the case. Ukraine did field test fully autonomous killer drone with confirmed kills. They basically let loose autonomous killer drones and let them seek out any living humans and eliminate them within a specific geofenced area without any human involvement. They claimed it was a one time test. (Guess what might happen if the GPS signals get spoofed.)
See my post upthread.
![]()
Master AI (Artificial Intelligence) Discussion/News Thread
Alternatively . . . You could wash the car at home. Think about all the nonsense that is eliminated by that one, simple act.www.audiosciencereview.com
Why?Thanks, I missed that post. My memory of what was mentioned in the videos I watched must be in error. I now watch over twenty YT videos a day about that war.
You're quite right. My friends and colleagues at work never understood my unhealthy obsession with the war. I guess I got emotionally invested in it from Feb 2022 onward. I knew next to nothing about Ukraine before that. The more I learnt, the more I became immersed in the complexities, the geopolitics, the history and the cultures. I feel like it is the spectacle of our times, with new developments almost every day. It doesn't help that I understand the basics of some of the technology involved on the aerospace side of things.Why?
That would do not change anything.
Weekend Room DSP Project
- Set up REW
- Install REW.
- Connect your calibrated microphone.
- Load the mic calibration file.
- Put the mic at your normal listening position, at ear height.
- Establish a clean baseline
- Measure:
- Left speaker only
- Right speaker only
- Both mains
- Sub only
- Mains + sub
- This tells us what each source is doing before we change anything.
- Investigate the ~68 Hz issue
- Compare those measurements around 60–80 Hz.
- Determine whether the dip comes from:
- the room itself,
- speaker placement,
- or sub/main phase cancellation.
- Optimize the sub first
- Adjust, as needed:
- phase
- crossover
- gain
- possibly sub position
- Re-measure after each meaningful change.
- Clean up bass with PEQ
- Use the SVS PEQ mainly to reduce genuine peaks.
- Avoid aggressively boosting deep nulls.
- Aim for a smooth bass response, not ruler-flat.
- Shape the overall response
- Use the RME DSP for broader tonal corrections.
- Target a mild Toole-style house curve with tasteful bass elevation.
- Keep mids essentially neutral.
- Be conservative with treble correction.
- Mostly ignore the extreme top end
- We’ll concentrate heavily on 20–300 Hz, then broad behavior through the mids/treble.
- Above roughly 10–12 kHz, we won’t waste much effort trying to perfect tiny irregularities.
- Verify at your real listening levels
- Check that it sounds natural at your normal ~65 dB or lower listening level.
- Also verify around 80–85 dB, where your RME loudness compensation should be doing less.
- Final sanity check
- Listen to familiar music.
- Confirm:
- vocals remain dead center,
- bass is deep but not boomy,
- nothing sounds artificially bright,
- and the system still sounds enjoyable rather than merely “good on a graph.”
The basic philosophy is:
Measure → identify the cause → fix geometry/phase first → EQ second → listen → verify.
That keeps us from using DSP to fight problems that DSP cannot really solve.
- Lock in the room layout
Speakers stay put on the 13-ft wall, firing across the 10-ft depth. The window AC and TV on the left wall mean there's really no alternative orientation worth testing. Jot down how far the left speaker sits from the AC/window unit — that's a fixed landmark we'll want to reference later.- Get REW ready
Install the software.
Hook up the calibrated mic.
Load its calibration file.
Position the mic where your head actually sits when listening — ear height, normal seat.- Capture a baseline before touching anything
Take five measurements:
Left speaker alone
Right speaker alone
Both mains together
Sub alone
Mains and sub together
This gives us a snapshot of the current state, which we'll compare everything else against.- Track down the 68 Hz dip
Zoom into the 60–80 Hz range across those five traces.
Try to pin down whether it's caused by:
room modes,
where the speakers are sitting,
sub/main phase fighting each other,
or the AC unit and window recess disrupting things near the left speaker.
No EQ yet — we want the cause, not a patch.- Dial in the sub before anything else
Work through phase, crossover point, gain, and maybe sub position.
Re-measure after each individual change so we can tell what's actually helping.- Push on the geometry we can still change
Since the AC and TV rule out relocating speakers, focus on what's left: how far off the front wall they sit (try shifting 6–18 inches), and toe-in angle. This is likely to move the needle more than the ceiling slope does.- Smooth the bass with PEQ
Use the SVS PEQ to knock down real peaks.
Don't chase deep nulls by boosting them.
The goal is smooth, not perfectly flat.- Shape the broader tonal balance
Use the RME DSP here.
Aim for a gentle Toole-style house curve with a touch of extra bass.
Keep the mids where they are — neutral.
Go light on any treble correction.- Don't bother chasing the very top end
Most of the effort goes into 20–300 Hz, then broad trends through mids and treble.
Past roughly 10–12 kHz, small wiggles aren't worth fixing.- Check it at real-world volumes
Listen at your normal ~65 dB level first.
Then check again around 80–85 dB, where the RME's loudness compensation backs off.- Trust your ears at the end
Put on music you know well.
Make sure vocals sit dead center, bass is full without booming, nothing's harsh up top, and — above all — it still sounds like music you want to listen to, not just a flat curve on a screen.
Underlying approach: measure first, find the actual cause, fix placement and phase before reaching for EQ, then confirm by listening.
Bladerunner, of course, but not to forget Brazil.
90's?... 80's?...
My dystopian prediction:
Colossus: The Forbin Project (1970)
meets
Terminator 3: Rise Of The Machines (2003)
meets
Captain America: The Winter Soldier (2014)
and, of course, Sal's "I, Robot"
OpenAI revealed a bit more about what happened in the lead up to their bots' attack on Hugging Face:
https://www.theregister.com/securit...e-bit-borg-ahead-of-hugging-face-hack/5283741
Meanwhile UK government body AISI revealed more unintended real-world effects from test environments. No sandbox escape this time as the environment had internet access, and some of the guardrails were turned off (like the ones that prevented Hugging Face using models to counter the attack from OpenAI). There are some similarities to what OpenAI revealed, like unintentionally impossible problems and agents seeking collaboration with other agents. I think that part is more interesting than the bit that most of the press coverage is leading with - the attempt at getting malware into an open source package on github that ultimately failed.
https://www.aisi.gov.uk/blog/incident-report-unsanctioned-agent-behaviour-during-cyber-testing