Jump to content

Catar

Moderator
  • Content count

    2,767
  • Joined

  • Last visited

  • Days Won

    66

Catar last won the day on February 8

Catar had the most liked content!

Community Reputation

4,299 Exalted

About Catar

  • Rank
    lazy remuxer

Profile Information

  • Gender
    Female
  • Location
    In a world of pure imagination

Recent Profile Visitors

8,322 profile views
  1. SCY - Anime/Cartoon Index

    Might actually have been the other way around. Amazon's video specialist posted on doom9 about the problems he had working with the original files when making it, so it may have been handled by Amazon and not a BD authoring team. https://forum.doom9.org/showthread.php?p=1576781#post1576781
  2. A Certain Archival Index

    Make a jumplink to it in your main post, like this: https://kametsu.com/topic/61452-a-certain-archival-index/#comment-592863 will jump without reloading page.
  3. ... What on earth were you using as a player? None of that should be happening with a proper media player. The only thing you'll have is video artifacting and wrong colors if you try to hardware decode 10-bit (gotta make sure it software decodes).
  4. From my own experiments (with a pi 2 model B, not a pi 3) it can, but you have to overclock it pretty hard to get it stutter-free. You'll never find a hardware decoder for Hi10p, of course. I personally use Intel NUCs running Windows 10 (with heavy group policy action) for my media centers hooked up to TVs with a personalized custom build of Kodi, but that's probably excessive for what you're looking for. You might look elsewhere in the Pi family, like a Banana Pi. A little bit more powerful. Else-elsewhere, I have a few friends with Amazon Fire TVs (not the Stick, the full 4k version) and we tested those out with some of my releases. Playback was fine for both Hi10p and for my Ghost in the Shell x265 release. The Ghost in the Shell release did have a tiny bit of frame drop on high intensity scenes, but you really had to be watching for it to notice (or pull up Kodi's statistics =P). So if you want a simple retail pre-built box, Fire TV might be good for you as well.
  5. A call for donations

    mods can't do anything with usergroup settings, so we're stuck just banning people instead =P they'd have to give us that admin permission. Which they can do, Invision has very cool granularity on admin flags, but we'd also have to be able to verify incoming donations and so on and yeah. i'd love the admin flag for modifying boards though, so I could fix up a few things in the organization and labels and such.
  6. A call for donations

    The free one is basically just a sidebar block with a donate button and dropdown to select the amount that then links to wherever you want. I have it on my own Invision board using Paypal. The progress bar is just manually set though, and it doesn't include all the specific amount tracking or automatic perks like the DevFuse one I believe you were using. it's pretty much just a pre-written HTML box to be honest. You could make one yourself with a normal custom HTML sidebar block >.>
  7. The CTR Muxing Standards Guide

    Thanks for the rant, I always love a good rant <3 I agree that it's never quite ideal. In fact, I'd actually probably change my standard for track language tags if I weren't so entrenched at this point. Either: Signs as ZXX (No Linguistic Content), Forced, Default and first track in list Subtitles as ENG, second track or Signs as ENG, Forced, Default, first track Subtitles as ENG, second track The former uses a tag specifically set aside for use in tracks like this, which is nice. However, it's also a strange tag that I already know isn't recognized by a lot of sources, so I'd feel less secure about it compared to the ENG/ENG option. For example, Koby used ZXX for the Signs track on the LostYears AOT2 release: It shows up in Plex, but not in an ideal way. Forced would alleviate this somewhat since it'd be auto-selected, but I think the ENG/ENG choice is probably better. On top of this, ENG(Forced)/ENG is the actual retail standard, as retail releases will use an ENG(Forced) track as default and then a subtitle ENG track as second track. thanks for the input though! I have used it in the past, and I was mostly satisfied. However, I've gotten fast enough at the MKVToolNix GUI that it's barely any faster for me now =P On top of which, the MKV one lets me see all my track flags and attachments as I go as a good double-check mechanism. I've caught errors in QC that way in the past. as for your questions: The screenshot I used may not have been ideal, it was just what I had open at the time. Generally, that track is actually empty when you get it for your remux, and you fill it in with whatever you want. On most releases, I simply put in the group tag on its own, such as [Kagura] or [Yousei-Raws]. Kagura had already filled it out with full information, so I was too lazy to replace it. Unlike the audio and subtitle tracks, whose title flags are frequently seen all over the place, the video track title is pretty rare to see. So long as the most important information is there that's not otherwise automatically listed by a mediainfo dump (source encoder group and the language flag for denoting origin), it's fine to leave extra info there. Definitely fair, I'll probably add in a note about that. I actually do follow that myself, by marking any tracks I edited beyond timing and minor typos as [Groupname-Edit] (e.g. [SallySubs-Edit] all the way back on Log Horizon, my first release). However, when I did a full edit pass and new typesetting on subs in Symphogear, or the extensive weird combination of sources, fresh material, etc. on Red Garden, I just named the tracks [CTR]. After all, most fansubbing these days is just an edit of retail subs + typesetting anyway, so I was basically doing full fansubbing =P exactly right. Use your own tag if it's your work. and there's no good database to match for monogatari >.> at the end of the day, at least TVDB will give it to me in airing order, which is how I generally believe all things should be viewed. Only rare exceptions like Firefly are where the airing order should be ignored (which is, of course, signified by how they fix the order on all subsequent releases). someday i'll watch it.
  8. A call for donations

    The old donation meter was actually a paid addon for Invision, because Invision users love their paid addons. It's almost disgusting how much some of them cost ._. there is a free alternative, but it's not automated like that one. Could be added, but Koby would have to manage it all the time himself.
  9. Happy to help. I didn't quite get everything and there's a few more releases slowly trickling in from public trackers, but the majority is done. edit: @sfaxt you might enjoy this: Winter is an inaccurate count though, because I couldn't find any proper index of their releases. need a real listing before i start trying to archive it en masse.
  10. The CTR Muxing Standards Guide

    Oh it totally is =P
  11. The CTR Muxing Standards Guide

    lol. I believe in you!~ <3
  12. The CTR Muxing Standards Guide

    well that is the goal, I just don't expect it to actually catch on. fansubbing is dead after all :^) also come back we miss you.
  13. The CTR Muxing Standards Guide

    holy muffins use some line breaks ;-; anyway, regarding groupnames: There's an important distinction to be made between filenames and release names. I think filenames should always have the groupname at the end, full stop, as otherwise it makes alphabetization and storage silly and inconsistent. However, the published release title on Nyaasi/Anidex/BTN/wherever could easily have the group name at the front, either by the torrent title or by the actual torrent filename. Users casually browsing will see the groupnames they desire at the front as usual, so they can pick the subtitles they want. I don't think it's personally any different than putting it at the back for recognition, but it's not against the standard rules per se, so long as the filenames remain in proper schema. I fully expect this to never spread to the rest of the anime scene, though, so no worries =P This was actually primarily written to clarify how the naming scheme works for the users that have started to adopt it on this site, like @Maskedcape and @Karios, and any future muxers who want to join in the standard. on that note, an open offer to anyone on the forums: If you are making remuxes for Kametsu and following this schema, I offer absolutely free XDCC mirroring and long-term storage. If your release follows this standard, feel free to @tag me in your release thread and I'll come fetch your stuff and provide you mirror links to toss up. anyone can qualify! <3
  14. ~RELEASED: March Comes In Like a Lion (Volume 1)~ because SHAFT. Volume 2 sometime in April, assuming someone buys it at Aniplex prices. $130 for 11 episodes, kids :^)
  15. The CTR Muxing Standards Guide

    Sorry, that was poorly written. This is what happens when I'm writing forum posts, writing papers and working on a new release all at once =P What I meant was that every scraper understands that file naming structure, and every form of visual media uses it, except anime. Even AniDB recognizes and supports S##E##/scene naming (to my delight, since that means I can dump my stuff very easily. My AniDB groupis very thoroughly filled in). As for MPC-HC, I think that you (and everyone else who mentions this) are actually making an argument in my favor. Since MPC-HC doesn't care at all what a file is named, as you say - then why not switch to the standard that everyone else uses? If it doesn't affect you at all, but can improve a huge userbase's experience, why not do it? Same reason why I'm advocating the Forced flag. Well, no, of course not, but then neither would a lot of software. However, Plex and Kodi would only need internet once to scrape all the information, and then never again if you so desired (assuming you added no new files, of course). If you never had internet on a machine, then they would act simply as a solid customizable media center and media server with transcoding capabilities. I'd still put them above MPC-HC/MPV for ease of use in a home-theater style setup, even without any internet connection for information scraping - but in this eventuality, you are correct in that naming becomes pointless since there's nothing to scrape against. I can see a vague use-case where you have a media center hooked up that doesn't have easy reliable internet access, but that seems rather unlikely given how we're discussing pirated fansub media and large-scale solutions for identification and information scraping. If you don't have internet, it's unlikely you're downloading a lot of this media anyway, so it doesn't really affect you either way.
×