cesaref

Well, from my experience of going both seriously digital and seriously darkroom, i'd keep the two apart. Get a lovely 5x4 enlarger (or join a darkroom where one is available) and you'll enjoy making B&W prints from those negatives much more than you'll enjoy scanning them and looking at them on a screen.

Well it's good to know that once they abandoned the project, they cleared the site and left it how it was before they turned up. Oh wait, no, actually they left it with all the waste still there, under the assumption that it would be entombed 'forever' by the perpetual snowfall. Who would have thought it.

I'm not sure why you need midi 2.0 to achieve this? Recording midi on windows is totally trivial, and for this sort of application, only capturing the notes and relevant CCs (e.g. pedals) is all you need.

I believe the Logic team are still based in Germany, where the original Emagic team that produced Logic were based, so it's not that they are languishing, but an intentional decision has been made (either by them or Apple) to keep this structure.

Logic has such a long history, it's not surprising that it shows it's age, and has 'weird' behaviour that you wouldn't choose today. It's got stuff in there from the early 90s, as it started out as a midi sequencer before pulling audio into the product.

Unless you are on a greenfield project, you don't get to make these decisions like that. You start with a jumble of libraries and helper classes, or a complete app which needs its functionality amending. The right choice will alter depending on where you start if you see what I mean.

And yes, i'm an advocate for the mix and match approach.

Ah, ok. So the frequency locking was to reduce jitter on the performance tests? If so, this makes sense.

'We'd also like to thank Intel for helping with AVX-512 optimizations for aws-lc-rs recently. This was an important part of achieving our performance goals.'

Testing on an intel processor, with frequency scaling disabled, which will adversely affect non AVX-512 more than AVX-512 stuff due to the limited boost available when using this. I'm pretty sure this is a not totally fair comparison, and tuning the box to give your solution an advantage rather than tuning it for each solution to give optimal performance would be more realistic.

However, i'm not knocking it, sounds like a great achievement, and it'll spur the other solutions on to improve their implementations which is a win all round.

The problem I have with articles like this is that if we were to substitute anything in for 'Rust', it would read the same. I imagine if they had re-written it in C it would also be better than before. If it was an advert for anything, it might be chucking away a dodgy prototype and starting again (which is surprisingly rare).

Anyhow, on the other side of the coin, it's good to see newer languages getting a proper outing in real world situations. Proving stuff is 'up to it' can be a bit of a long haul, so every data point is useful.

I had an 11-23, and that had a monitor in the CPU (proper CISC!), writing to a serial port. That meant that I typed the boot loader into a terminal, and hence had a pre-recorded sequence I replayed to the port to boot the machine.

stuck doesn't mean twiddling your thumbs wondering what to do next - i'd certainly expect someone to ask if they were in that situation.

No, stuck can often only be observed by looking in, the person or team may think they are doing useful stuff, but someone coming to it fresh can see that they have missed something obvious, hence why recreating the problem seems to be impossible, or why the fix seems very involved.

So a standup can allow you to see that someone is stuck, even when they don't realise it themselves.

Breaking news - introverts don't want to have daily stand ups, whilst extroverts think it's fun and useful.

I personally found them quite helpful to ensure I could help out team members who had got stuck. It's sometimes lonely debugging a complex system, and people can appreciate someone else to either confirm it really is what they think is going on, or maybe bounce some ideas off. It's a great way for the more experienced team members to find places where they can make a significant difference by contributing a bit of their day to helping out.

Somewhere in between. It was a static composition (as in, it had a start and an end) but there were multiple loops per instrument, so more competent players would reach a more frenetic musical performance of the piece if they kept more of the balls in play.

The audio engine (the bit I worked on) was in effect a stem based mixer, but with a state transition diagram per stem, with multiple loops available. Depending on the route through the transitions (triggered by events from the game play, for example, how many balls the player is keeping in play) it was possible to reach more complex or simpler performances of the same musical piece, so the players decisions and ability would affect how the performance of the music, not the music itself if that makes sense?

Junior programmers tend to either document nothing, or document everything. With experience you realise that you just want to document the unusual stuff, and as you get more experienced, you realise there is less and less unusual stuff, so the amount of comments drop down.

So, less comments wins out, but faced with a code base without comments you have to inspect it to tell the difference between a beautifully crafted piece of brilliance or a totally flaky codebase written by a bunch of newbie hacks.

This reminds a bit of a project I coded the audio for an art exhibition around 20 years ago, which was for multiple simultaneous players. As the game got more intense it became apparent that the ball/wall sounds were playing music, and that the three players were all actually playing one musical piece.

It was based around 3 arcade cabinets pointing together, so the players couldn't see what was on each others screens.

This was achieved by modifying the ball speed/direction slightly so that it arrived at the bat/wall at a musically relevant point and triggered the correct sound.

Ah, here you go, Josh as a reference to it on his site: https://www.autogena.org/work/ping

Yeah, that's definitely an option. I've got an ethernet board for the SE/30, and also for the IIcx, and enough RAM to keep A/UX happy.

It's easy to pick up a bit of an old computer habit. I'm in the process of putting a machine I used to own back together, a Mac IIcx with Trinitron monitor, running Emagic Logic (a midi sequencer) as this was a hugely influential machine when I was getting into audio.

In the process of finding the right bits for this, i've ended up with an SE/30, a Mac LC and a Mac II, basically in order to get hold of other bits, and the price was good. They are now all running, and i've got no real use for any of them, but it's great to convert broken doorstops into fully functional doorstops :)

It sounds like geothermal without using the earth as the heat source. What benefits does this have over geothermal, which is proven and safe, and also ticks the 'non-nuclear' box which makes it considerably easier to convince a population to live next door to?

The 'pop' example given at the beginning of the article when switching on an 80s machine with built-in audio is typically caused by a DC blocking capacitor in line with the speaker. Because those machines typically only had a +ve supply rail, the output amplifier swings the output between gnd and +5v (or +12v, whatever the supply is), so there's a 1/2 rail voltage DC offset on the speaker output, and the blocking cap absorbs this during that 'pop'.

So the sound is quite analog, it's an exponentially decaying voltage as the capacitor charges :)

The final conclusion though stands without any justification - that LLM + RL will somehow out-perform people at open-domain problem solving seems quite a jump to me.

I think all the early B&W windowing systems had a stipple, as otherwise you are limited to either black or white which is pretty grim as a background.

The Alto certainly had this, from screenshots i've seen of Smalltalk demos running on it.

I interpreted this as 'don't write crappy functions taking confusing arguments'. If the function had taken 4 floating point numbers, the argument would be the same - it would be confusing to know what is what.

It's not about peers and poor, it's about immigrants, and racism within the post office - the abhorrent assumption that immigrant families who get contracts as sub postmasters were 'on the make'.

It was reported in the lords that >40% of those prosecuted were immigrants, with a high proportion of asian women, which, given the very low level of asian women in the prison population is hard to believe.

For reference, hansard has what was discussed in the lords:

https://hansard.parliament.uk/lords/2024-02-19/debates/E6D46...

Here in the UK it was pretty common up to say the 1940s for plasterers to curve the corners on outward pointing walls in hallways. This usually extends from the skirting up to the picture rail. There is a lovely transition from the curve to a point just below the picture rail, which is very elegant, but a total pain if you are hanging wallpaper, well, that's my experience anyway!

I've always felt it was one of those details that a plasterer could show off their skill, and you are right, it softens the corner in a very pleasing way.

I imagine much of the weight is for the tube to be strong enough to hold the vacuum without shattering. As the screen area increases, you need stronger electron sources, and higher HT to get the electrons to the phosphor. I think small 14 inch trinitrons are already using 20-30kV so I imagine the power supply and associated HT stuff will be quite scary in these larger sets.

There are all sorts of complex magnet arrangements to tune the beam to stay in focus across the image area, i don't know how that will scale with size, but it's probably more of a complexity when assembling the sets to calibrate the tubes.

Is there a decent overview of what the aim of mathematics solvers is these days? In light of Hilbert's effort at formalism in the 1920s, and the incompleteness theorem, I was wondering where this was going, and what the known limitations are.

Yum, global variables to avoid a call to malloc/realloc. This is not progress.

Agreed, I had a long chat with him at an audio conference years ago, and I have a LinnStrument 128.

One of the very cool things people may not know is the LinnStrument has open firmware under the Apache License, and you can download the source here: https://github.com/rogerlinndesign/linnstrument-firmware

So grab an instrument, and start hacking!

From the description of the product, I think the intention is that the tone is received electrically at the end of a cable run, so receipt of the tone indicates continuity of the speaker cabling. This high frequency has been chosen to ensure that it is low enough to be amplified and transmitted along with the audio content, and is high enough to be attenuated by the tweeters (so little energy is transmitted), and high enough in frequency so that whatever is emitted by the tweeters will be inaudible.

If this is the case, it would sound like there is no need to encode any information on the signal, just it's presence is enough to test the wiring is intact. I'm assuming this is so that if the PA is required for, say, an emergency broadcast, it is fit for purpose.

The presence of a <20Khz signal would imply that it was found that in whatever installation was being used that the bandwidth of the amplifiers or some other filter was attenuating the test tone too much to be received properly, so this bodge was put in place.

If it is a flash type circuit, the capacitor will be connected directly across the xenon tube, and a separate trigger circuit will generate a much higher voltage to start the xenon conducting, and allow the capacitor to discharge it's energy and trigger the flash.

So, it might be the 350v capacitor has failed and is not storing enough charge to generate a meaningful flash, or the trigger circuit which is not generating the initial >5kV to get the xenon conducting.

Either way, i'd check the circuit before the xenon tube.

I think you are missing the point. People do stuff because they enjoy doing it. The fact that they enjoy doing stuff you don't is their business, and frankly it would be a boring world if we all liked the same things.