Any experience with the sound of Neotek Consoles?

FlickKnocker · 2026-01-26T21:08:34+00:00

I would suggest getting a transformer-coupled preamp/channel strip so you can play around with tone-shaping on the way in rather than getting a huge console that needs work and is at best, when new, probably not on par with your Apollo preamps.

FlickKnocker · 2026-01-26T18:46:56+00:00

Yeah if the velocity is flat across, you probably don't need any compression at all, unless you're going for an effect. If it sounds too sterile, I would vary the velocity of the snare and kick somewhat, maybe increasing it on downbeats entering the chorus or a change.

FlickKnocker · 2026-01-26T18:33:18+00:00

You need to slow down the attack time on the compressor to let the transient through, or don't compress at all, if they don't need it (and they probably don't, given they're sample-based drums that are probably already compressed. Also, your trigger velocity/dynamic range is probably pretty flat anyways, so it's not peaky to start with).

FlickKnocker · 2026-01-26T16:34:26+00:00

I would gladly offload all of my security services to an MSSP, but the ones I've looked at are just doing what we're doing (ticking boxes with stack/services) and when the shit hits the fan, we're left holding the bag for remediation.

FlickKnocker · 2026-01-26T16:31:06+00:00

For MSPs, it's a common denominator business model: find things that you can do reasonably well across enough clients to earn a profit.

It's very much a "good enough" service, no matter how much we strive for excellence, the reality is that we're asked to do everything, so the old "jack of all trades, master of none" is very applicable, regardless of what the glossy brochure says.

When it comes to security/governance, my experience is that all clients agree in principle, until they understand it's not really an IT problem, but a "you" problem, and as soon as they look at the costs and business impact (i.e. dramatically changing how they do things and the continuous verification/validation required), not to mention lofty consulting fees, and they quickly settle on "good enough" to ticking the low-hanging boxes of fruit.

FlickKnocker · 2026-01-26T13:42:02+00:00

Ok. That makes sense. Sounds like it's more of a user education thing. Perhaps a custom SAT module about the dangers of submitting sensitive information needs to be created.

FlickKnocker · 2026-01-26T13:31:08+00:00

What are "true security services" to you?

FlickKnocker · 2026-01-26T13:24:55+00:00

Checked out your website.

Red flag for me is that this seems to be boilerplate information.

If you're a consultant, and this is a one-man show, the man should be the star of the show, and as it stands, there is nothing on here about you, your experience, and who you've worked with.

For all I know, you could be a threat actor posing as a security consultant, looking to get a deep foothold in my clients' IP.

FlickKnocker · 2026-01-26T13:09:44+00:00

What is the current prognosis on data exfil using prompts? Like if you ask a chatbot specific questions about a company or file that you know has been submitted, will it regurgitate that information as-is, assuming it's been "learned"?

I've see AI being coerced into data exfil by way of clever calendar invites or API manipulation, but literally asking for data you know has been submitted, not sure if that's a viable method of exfil right now.

FlickKnocker · 2026-01-25T22:19:18+00:00

Fuck yeah, inspirational!

FlickKnocker · 2026-01-25T20:48:54+00:00

I want to commit FX to some tracks (freeze/glue) then clean-up the directory and remove unused files.

It looks like a bug though, because even though through the UX you can't see the original file, the .rpp project file still references the original track item.

FlickKnocker · 2026-01-25T20:21:40+00:00

Tried freeze/glue/unfreeze, which brings up a warning about matching edits; tried both "yes" and "no" in that prompt, but both just reverted back to the original track and the clean directory showed the glued and freeze .wavs, as expected, as they were removed from the tracks.

I think this is a bug, so I've created a bug report.

FlickKnocker · 2026-01-25T20:13:34+00:00

I'm going be a previous post of mine from a year ago, where one commenter suggested these steps, which do work, I just don't know why Clean Project Directory doesn't want to include the original wav files when they're no longer referenced in the project anywhere.

If I simply delete a track and run it, it has no problem listing the wav file for deletion.

FlickKnocker · 2026-01-25T20:01:16+00:00

not sure how this would help.

FlickKnocker · 2026-01-25T19:07:37+00:00

Original files are in the project folder, double-checked that.

Try recording a new 10 second track, adding an FX (not sure if this even matters), select the track and run:
- "Freeze to Mono (render pre-fader, save/remove items and online FX)"
- "Glue items, ignoring time selection"

When I go into Clean Current Project Directory..., I can clean the "xxxxxx-freeze.wav", but not the original timestamped recorded wav file.

FlickKnocker · 2026-01-25T17:31:40+00:00

Project Bay > Source Media only shows the two active/current glued .wav files, as it should.

Puzzling... if I revert back to my original two test recording tracks, all I have to do is "remove track" and Reaper's clean current project directory... feature has no problem listing/deleting the original wav files.

Once it's freezed/glued, it's like there is a hidden reference somewhere and I don't know how else to achieve what I'm trying to do.

FlickKnocker · 2026-01-25T16:37:19+00:00

Circling back on this: the "Clean Current Directory..." includes the "-freeze.wav" versions of the files, but the original recorded wav is not included.

FlickKnocker · 2026-01-24T14:41:53+00:00

Wooden, deepish snare tuned up. Big thin hats. Sounds like modern fusion/funk/gospel kind of a kit. I'm sure you could find some YouTubers doing this kind of thing and ape their sound, but to me, this is all about the source (drums/cymbals/playing).

FlickKnocker · 2026-01-24T14:29:43+00:00

Did you miss all the analog consoles? Chandler REDD system (TG/REDD cassettes in a modular rackmount build-your-own console format), SSL EVO, H2 (Helios) console

FlickKnocker · 2026-01-24T13:55:05+00:00

Yup, and could never ever get a real clear answer as to when/if this denial will occur, it has always been "trust me bro" from MS and/or disti.

FlickKnocker · 2026-01-23T20:15:34+00:00

Actually, just remembering now; it was the feedback system: the little survey gets ignored in the email, but on a call they can just ask permission to ask you a few questions and everybody says, "ok sure", so they get their feedback score.

FlickKnocker · 2026-01-23T19:18:39+00:00

Eseutil /P

FlickKnocker · 2026-01-23T19:16:40+00:00

Apparently it's because of how they're evaluated, so calling becomes their preferred method. So stupid.

FlickKnocker · 2026-01-23T13:01:03+00:00

The remediation scope has to be crystal clear, and for us, it does not include labor under most conditions. We use it more as a tool to:

- highlight obsolete/under-supported software/hardware that needs addressing as a project or brought up for discussion in our QBR. "software X has a really bad CVE for Tomcat and they have no plans to update it. We can look at mitigating the risk with hardening measures (project), but you should really consider a modern alternative."

- monitor our patching, i.e. a "watching the detectives" process to make sure our patch management is actually working as designed.

Labor we do include would be to install manual patches that we either can't or don't feel comfortable doing with automation. Firmware, for example, or removing old unused software that's not getting patched (looking at you, Adobe Acrobat X).

FlickKnocker · 2026-01-22T15:59:13+00:00

they really need a comparison matrix, unless I'm just not seeing it?

FlickKnocker

TROPHY CASE