this post was submitted on 08 Jul 2023
4 points (100.0% liked)
Waveform
1 readers
1 users here now
A place to talk about how we organise ourselves.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So is it a website/webapp with a desktop first and mobile second approach or the other way around?
It is a website/webapp yes. I don't think it is big enough to be mobile or desktop first. It should work well on either.
Basically there will be 3 pages:
All three of these should work on mobile and desktop.
I also started a poll to figure out which themes people use. If it has a mixed outcome I may want to facilitate automatic light/dark theme switching based on browser preferences.
Oh okay, I was under the impression that you wanted to build a new (separate) website/webapp and not just augment this instance. Or not, as you were talking about embedding a widget?
I have some know how regarding UI/UX-Design, though.
I think building a full replacement for the current UI would be too involved. I am talking about an additional service to augment this instance (which would be hosted on clips.waveform.social).
So basically people will go there, drop/upload a file and get a link to be able to create a post on this instance.
Lemmy already supports embedding post content if the target site supports embedding (through opengraph metadata) which is why we can easily embed the media into the post.
If you're willing to design some pages that would be awesome.
So in essence an imgur but for audio.
Instead of a grid of images you have a list of audio clips (represented as waveforms for example), perhaps annotated with metadata, tags and or a short descriptive text (what about deaf people?).
Could people just drop-in audio without the need to register, what about deletion. What about copyright claims/DMCA? Can people edit/manipulate their uploads?
What about discoverability, would there be a search function or should it just be a dump space for which you get a link as a reference to your uploaded audio file?
It's way simpler than that. No lists, no accounts, no search. You literally just upload a file and get a link to a viewer/player. The main place to be will still be waveform.social, this clips thing is just a way to upload media to get a link to share on waveform.social.
With regard to copyright claims: a link to send an email in the footer would be enough. I can go and delete any infringing content.
If at some point people would like to do more (like delete their content) then we can add it at that point. But right now I want to do the simplest thing that could possibly work.
I see.
I guess you can just use the same look and feel of your instance. And take the
create postscreen as reference. Instead of uploading an image, you change it to acceptaudio/*instead.Once the audio is uploaded, you can process it via
ffmpegto turn it into a visually appealing waveform png you then can show the users. Next to it would be a play and pause button, and seeking is done by sliding over the waveform (it also shows the current location by graying out the given portion like a progress bar).Once an audio is uploaded, you also could generate a UUID to reference that exact post for embedding or linking.
In embedded form: you see the same playback controls as the uploader, including the waveform.