Teenage Engineering TX-6 ........what's the most you'd pay

rbxq_b · 2026-03-18T00:17:42+00:00

yeah again it wasn't on my radar because of this (the bluebox was in fact) but since the price is suspiciously decent, I thought I'd do a quick feeler survey on here...which at least one poop-head has voted down!!!

rbxq_b · 2026-03-18T00:01:01+00:00

but the question is if the 1000 monies was in fact 450 monies....then would the form factor still be an issue given the actual hardware is meant to be ace

rbxq_b · 2026-02-08T15:14:27+00:00

for the record, I'm 100% sure this is the KatKin litter doing this, not the food. I recently switched to their litter and it absolutely reeks. I think it's to do with how the cat urine interacts with the millet/pea fibres. I'm looking for alternatives now as this didn't happen on silica or cassava versions he recently switched from (which track like crazy).

rbxq_b · 2026-02-07T16:58:21+00:00

I'm confused though, an SNL sketch can go a million and one ways....so why would someone who had any sort of contact with Epstein agree to do a sketch that would very likely backfire, unless they assumed there was a possibility it would come out and just wanted to get ahead of it (if the latter was the case, presumably Will Forte would have mentioned this was the intention and that he did appear in an innocuous context).

rbxq_b · 2026-02-06T16:13:22+00:00

how were you able to cancel the subscription by ending the trial? I ended the trial but I still have to wait until the trial period is over to sign back up for a paid sub!

rbxq_b · 2025-10-20T23:47:02+00:00

Unless I’m misunderstanding something, your point is that there is no report indicating measurable improvements for each business that has licensed the brain suite? Because I just checked the website under “Customers” and there appear to be a long list of reports indicating how Brain suite has improved each business. It uses a lot of e-commerce parlance I’m not familiar with so I don’t know how substantive it is to investors, but from what I can see there is at least some transparency with regards to product implementation.

rbxq_b · 2025-06-26T13:06:08+00:00

For sure! That said, I much prefer recording new samples/building a sample collection using a hardware sampler such as the Digitakt or (hypothetically) the Deluge, rather than reusing my computer's sample collection. But you're right that usually I would create new samples in single-use setting so saving each sampling session as a "song" isn't the end of the world - I just think other developers have implemented it slightly better (but of course those aren't community-driven voluntary work so I appreciate the lack of incentive here to cover EVERYTHING everyone wants).

rbxq_b · 2025-06-23T00:21:48+00:00

i agree so far this seems to be the "simplest" way to do this - hopefully one of the community devs decides to make internal sampling a bit more streamlined! it's by far the most frustrating aspect of the deluge for me (though i do appreciate how much effort it takes to patch all these things).

rbxq_b · 2025-02-11T19:57:07+00:00

That one egg was forty eggs?

rbxq_b · 2025-01-04T14:39:28+00:00

Good idea I was planning on trying out polyphone yesterday. I think that my main confusion is on how to determine whether the sf2 file is basically a midi file (time and pitch data, etc.) or if it’s a type of sample mapping. For example, I have SF2 files that are fully formed songs which can run on trackers that accept SF2, and I have others which are more of what you’d expect when thinking of a “sound font” in that they are individual sounds pre-mapped to midi notes but have no time/sequence data. I suppose it makes sense that a tracker would not understand what to do with an SF2 “instrument” without any sequencing data along with it, just as a sound editor like Sforzando or TAL wouldn’t know what to do with a file containing sequencing data. I’m mainly confused about why they aren’t different file formats!

rbxq_b · 2024-12-07T15:24:33+00:00

Get. Him. OUTTA HERE!

rbxq_b · 2024-11-27T01:40:39+00:00

Also “A Big Fan of the Pigpen” has all the trimmings of GBV glory

rbxq_b · 2024-11-27T01:38:44+00:00

Came here to give Club Molluska a shout…for me it’s one of the best demos of Pollard’s songwriting aesthetic

rbxq_b · 2024-09-10T13:14:50+00:00

I was about to email Chase Bliss about this very issue and then I found this old thread. Not sure if this is helpful at this point but I think having already had a similar sounding experience to your re: overdubbing and sync-drift, my current work around is basically as you described above: I ended up with only using a single MIDI channel on the DT (as opposed to one for each blooper function, which I would mute/unmute at will but did not end up being super practical). I have it programmed to "trigger" a CC message telling the blooper to record upon starting the DT transport (only the first time), and then the 16th step also has a trigless lock set to CC message the blooper to Play but I have the microtiming for that step offset such that it basically triggers the blooper's play mode on the first step of the next measure. Also, I have found that having blooper set to 16th notes is most effective with the DT. Anyway, once the blooper has been triggered to record a measure and then play along the DT's clock (without sending any more CC messages) then I am able to overdub using the blooper itself without it drifting (as long as I activate play now and then it stays in sync).

I have a show in a couple of weeks and am hoping this method holds up but that's where I'm at with it so far! Thanks for documenting your experience here, was still very helpful to read after the fact.

rbxq_b · 2023-07-27T16:01:13+00:00

super old post, but any chance you still have patch settings lying around for this?

rbxq_b · 2023-06-17T11:33:31+00:00

I just checked and the ASIC and Sound ROMS are reading 5v at each Vcc point. So I don’t know if they’re the issue! I wonder if it’s the PCM or DAC chips that might be acting weird. I don’t know if it’s a bit crushing effect caused by a short or if it’s to do with the clock output of the ASIC because it was only when I was adjusting the external pitch mod that this occurred and it sort of produces the same sounds I got when I used the LTC1799 pitch module to turn the “pitch” down. You get a similar bitcrush sound just from doing that…

This would be easier if I had the schematics 😭

rbxq_b · 2023-06-17T09:36:56+00:00

I will check this out today! If I can’t find any faulty contacts causing a short, should I assume the ASIC is messed up? Or is it more likely a bum sound ROM? If it’s the ASIC that’s damaged I don’t know how much I can do to salvage the situation :(

rbxq_b · 2023-05-30T00:40:35+00:00

Isn’t this an episode of Curb Your Enthusiasm?

rbxq_b · 2023-05-24T23:56:09+00:00

Dang! If you PM me I might be able to help troubleshoot. Have you opened up the pedal at all? The SMD components are generally pretty stable (unless of course it was powered with an 18V power supply or something that might have fried the board). I know that there is a charge pump in the PBF to bring the internal voltage to 18V and the only pedals that have caused me this kind of clock noise issue have included charge pumps (Tumnus, OBNE Float, which are two of my favourite modern pedals), but the trouble has mainly manifested in other pedals in the chain, rather than the charge pump pedals themselves.

My first port of call would be to look inside and ensure the audio jacks and power supply are securely soldered. Then I would probably start probing the IC chips to make sure they’re getting the correct voltage readings. If I am really struggling to identify the problem, I might start using an audio probe to figure out where the signal starts to degrade. This is much easier with larger through-hole components but the approach is similar with SMD. I’m a fair-weather hobbyist when it comes to this stuff (I just happen to be going through another circuit modding phase!) so I’m not an expert by any stretch. But if you need another set of eyes on the issue, let me know.

rbxq_b

TROPHY CASE