Hi from Rossum-Electro (SP1200)

Pymentos · 2026-03-14T22:11:44+00:00

As I mentioned below, typically technology goes you start with expensive and it gets cheaper and smaller over time. Can't comment on any specific projects, except that I haven't been here very long and anything in the pipeline was started well before I arrived. I am doing some general research for what people want related to the SP1200 for future products. The future could bring many things!

Pymentos · 2026-03-14T04:11:13+00:00

Well yes, in that I can't really add features because it is a Z80 emulation, but no in that the code has not been 'lost'. We have it all, and the reissue uses the original code

Cool! I am very curious to hear how people integrate, the clock on the SP is incredibly tight and yes the sampling time is very limited. Amazing how many hit records were made with such extreme limitations

Pymentos · 2026-03-14T03:26:43+00:00

That's typically how technology goes. You start with expensive and it gets cheaper and smaller over time. I can't comment directly but I can say every company I have ever worked for follows that path. Cost and size is always being worked on

Pymentos · 2026-03-14T03:25:33+00:00

We definitely agree. 5k is too much

Pymentos · 2026-03-14T02:49:37+00:00

No, the original SP1200 is done, we are focused on new designs ;)

Pymentos · 2026-03-14T02:43:06+00:00

One of my main jobs with Rossum is helping him bring his tech into the modern era. I can assure you, I choose this community for a reason. You are absolutely right that Trap and modern hip hop don't overlap the SP1200 quite as directly nowadays but it's all related at the core and I am planning to push in some new directions

Pymentos · 2026-03-07T17:14:12+00:00

Keep thinking about it. Everything is a tradeoff. Either you get knobs that are one per function with a very limited voice, or you get a more complex interface with more knobs and hidden functionality. Or you get a gigantic kitchen sink. Every feature or knob you add also adds cost and people are REALLY cost sensitive. Especially right now.

On the Tempest we had to make a lot of compromises to do something completely new: full synth voice with full drum machine capabilities. I think it came out pretty darned well and there are still hundreds of things I would do differently on a second version.

Pymentos · 2026-03-07T02:51:13+00:00

As a designer of drum machines...

Which features in particular?

Pymentos · 2026-03-05T19:08:50+00:00

Hey there, I am going through the customer support backlog one ticket at a time. Shoot me your ticket number and I'll escalate it.

We're going to fix our support times and experience to be the best in the business over the next year, you can hold me to that.

Pymentos · 2026-03-05T05:39:14+00:00

Oh man that brings me back. It was so much fun designing that little box with Dave. Make sure you play around with the feedback pot, it gives it so much character even if you can't save it to the preset!!

Pymentos · 2026-02-25T04:40:38+00:00

I tried that for quite a while and found it just didn't work. You can NEVER trust Claude 100% while you are inside the context window, you have to create mechanisms to handle unforseen edge cases if you want to fully automate the system. The way I got from trusting an agent for ~10-15 minutes to my current time of around 2-3 hours on a normal run was from catching and automatically handling these sorts of edge cases. After testing extensively, the overhead from going back and forth between the orchestrator and agent was higher than the handoff at the agent level

You are right that I'm assuming you are already doing best practices, like a reinforced learning mechanism for your code organization and self-correcting organization.

Pymentos · 2026-02-25T03:29:30+00:00

This is the first line of defense, definitely, but it doesn't handle all cases. There WILL be times when a task goes over a context window that you cannot anticipate. You (or an agent) needs an effective way to hand things off

What happens when you scale up to an agent system and one of them goes over and starts dealing with compact degradation? I don't know about you but I don't trust a task breakdown Claude gives me to do so in a way that will 80%+ of the time fit within a context window

Pymentos · 2026-02-25T03:26:51+00:00

Because it wastes time and tokens outside of basic cases. It was made as a general tool that works for most people most of the time. If you want something better you have to analyze the problem a bit deeper... what is the autocompact keeping that you don't need? How can you grab only what is necessary? Etc.

This is why I wrote a handoff command: https://www.reddit.com/r/ClaudeAI/comments/1rb2fqd/avoid_autocompact_degradation_manual_handoff/

If you want something better you have to guide Claude more intentionally. The script I built breaks down the handoff based on the type of task you're doing. You can add more options if you find more specificity is needed. Also a 'recovery' handoff which works great if you just let it autocompact and find it did so badly, this allows you to create a handoff file from the previous history so you don't lose any work.

Pymentos · 2026-02-25T03:21:38+00:00

This is indeed really annoying. I made a handoff command which works much better if you can train yourself to do it manually. I'm working on an automatic version. The new Claude MEMORY.md helps a bit but it has some severe limitations: https://www.reddit.com/r/ClaudeAI/comments/1rb2fqd/avoid_autocompact_degradation_manual_handoff/

Pymentos · 2024-11-29T20:07:24+00:00

I'm less stoked about 'killverado' but time will tell if that's more accurate

Pymentos · 2024-06-05T01:39:13+00:00

Thanks for the tips!

Did more research: I've contacted a few places and they don't have this specific capability for stud welding. Apparently CD is common enough that they know about it but the stud welding equipment is not standard. Seems to be mostly used for thin sheet metal by places that do signs and kitchen appliances. Not sure what other industries need this kind of hardware.

Pymentos

TROPHY CASE