@betaflame posted:
mka (mkv) container with just subs and audio?
mka doesn't have browser support, but that's not even the bigger issue. We want the various audio formats and the caption files to be completely separate, so that the user can choose any combination they like (or even
can run, because
audio format support is all over the place across different browsers). In our case it's counterproductive to embed subs to a specific audio file. There's no need to upload several copies of the exact same audio for each translation of the same, single track.
@Bloodnose posted:
I've started working on a drama CD translation. The way I've been doing it has been to use Ren'Py to create a sort of VN visualization that people can watch while they listen to it.
But I wonder if a DramaDex could support that kind of video embedding?
We won't, I see no reason to. As fun as some kinds of visualizations or image slideshows may be, alternative translations of the same track wouldn't have the same content and more importantly it's not present in the original product. As a concept, I see this as little to no different from fan colored manga, and we separate those away from the "real" manga for a reason.
@SNSbu posted:
What will it look like from the uploader's side? Will it ask for a muxed audio/sub file or will it want separate .mp3/.FLAC/etc. and .ass/.srt files? Will it strip any styling out to show the player's default text or will it allow for some visual flair? Will there be a way to support accompanying images?
As far as the player goes, it would be good to define where the subs are going to show up visually since there are often significant periods of silence in these. Two-line parts should also expand up from the baseline, not down.
Good questions. My plan is that first a user would create the drama collection much in the same way that a new manga is added to the site, inputting basic information, adding the cover etc. Additionally,
all of the tracks should be added as separate entities - and by tracks, at this point I mean only the basic information, as in track number and the original title (probably in both the native script and romaji, but we'll see about that). Unlike with manga chapters, all of the tracks of a single collection are already known, so they can all be added no problem.
After a collection and its track info has been created, a user would choose a track and upload (an audio file if none exists for that track yet, and) a subtitle file along with the translated title and group information. This is why the track itself uses the native name – various translations in different languages have different titles. No muxed audio/sub file. Ideally, I'm envisioning having to only upload a FLAC while the server converts the rest of the format options however we configure it to, since that would allow us some quality control, but whether that's realistic we'd have to figure out.
As for the subs, the prototype is currently using the WebVTT (.vtt) format for reasons of combatibility and javascript library availability. ASS isn't an impossible option, but it's not quite as convenient. I have to remind that we're not dealing with a standalone video player here but a web browser. If we want to get fancy, we'll have to either rely on existing native technology, libraries or implement our own subtitle renderer.
@sprite-1 posted:
The subtitle text should always be visible while scrolling around the page (think a floating footer)
There should be an easier way to navigate through the player especially on mobile (for example, tap + backwards drag to go back a few seconds depending on the drag distance, same with tap + forward drag)
The player and the subtitle rendering area in relation to the rest of the page is the biggest design question I have right now. A fixed footer did pop to my mind but that feels like it would have some problems of its own, with subtitles potentially rendering over other text especially on mobile and so on, so I went with the simple option for this introduction. I'll definitely try out new designs in the future.
As mentioned in the OP, the actual audio player itself is your browser's own native implementation that I can't influence without designing and implementing a full replacement. It's most likely something I'll have to do eventually, but for now you'll have to direct your UI issues with the audio player to your browser vendor, lol.
@kaza_hesto posted:
Maybe have an Opus encoded option? Since it's mandatory for WebRTC, browser support should be broad.
I figured Ogg Vorbis was good enough, it's got better support anyway.
@givemeabreak432 posted:
Perhaps you might want to include quality of life changes - the ability to change fonts and font sizes seem like a high priority for usability. Other things like a pop up box option, or someway to view subtitles while you're browsing the rest of mangadex (or even other websites).
Subtitle size and style options are definitely something that I was going to add eventually, along with options like audio format preference. Due to the way the site currently works it's not possible to keep the player up while browsing the site, although that might not be completely impossible once we get far enough into the development of the site. With other websites, it's quite certainly never happening.