erikschoster
Joined 15 years ago
Joined 15 years ago
Consider a random example of fair use: print an excerpt of this three panel comic you would like to discuss.
Does building a business around the automation of fair use constitute fair use? I would say no.
https://github.com/celphase/duck-pond/blob/main/src/synth.rs
To the credit of the author there is also an attribution file which describes a process of deriving the models from recordings (none of the techniques are very novel, but it's fairly impressive to see automated -- edit: I assume the project is LLM-generated) https://github.com/celphase/duck-pond/blob/main/ATTRIBUTION....
Arguably things like Cliff's Notes and "for dummies" books were sating this impulse before that, I wouldn't be surprised if the line can be traced back further.
Since dropping LLMs altogether I've made the connection to the impulse for a superficial jump to the conclusion just by noticing how I use web search, or feverishly scan some text to get to the point.
Theoretically I studied critical thinking and have learned decades ago how to recognize when this is OK and when it's a superficial placation of some addiction to closing the book on a subject or micro-subject... but boy whatever good instincts I might have developed back then have significantly eroded over time. Trying to reclaim that again is pretty humbling.
> HERTZ is a web-based Digital Audio Workstation (DAW) utility designed for instant vocal polishing.
I appreciate you have aspirations for the project beyond its current form, but this isn't an accurate description of what it is now. It:
- Uses wavesurfer + the wavesurfer regions plugin to display a waveform and allow a subsection of the uploaded audio to be selected
- Loads the uploaded audio into a buffer with the web audio API's decodeAudioData and then cuts the selected region out of it
- Applies a compression to the selection with the web audio API using hard-coded values (based on a screenshot you gave the LLM apparently according to the comment in the source)
- Normalizes the audio with the web audio API
- Encodes the audio as a WAV and then feeds that to ffmpeg to convert it to an mp3 for download
It seems complete for your use case, to me. You might consider asking the LLM to reword the readme and present it as a tool that applies these compression and normalization settings to a section of an audio file in the browser:
// 1. SETTINGS FROM YOUR SCREENSHOTS
const COMPRESSOR_OPTS = {
threshold: -20.0,
ratio: 3.1,
knee: 5.0,
attack: 0.03,
release: 0.1,
};
const NORMALIZE_TARGET_DB = -3.0;
It doesn't make a lot of sense as the basis for a web-based DAW right now. I like that you tried to keep it simple and small, though. Even so, you could improve readability by making this all a single HTML file since it's so small. As a learning exercise, you could try doing that yourself without the LLM. It would be a good way to get to know your project.Today I suppose this would get clobbered by bots but in 2016 it was fun and I still am in awe of how simple he made it.