• CIPWTTKT&GC v0x21 (v33): Fuck Titles Edition
    67,352 replies, posted
[QUOTE=SuperDuperScoot;45448669].. Is it me or is Chrome's font rendering different? Or is my eyesight finally going bad... Edit: No it's definitely different.[/QUOTE] You might have gotten the update to use TrueType instead of the in-built garbage.
41.7 gigs of data so far this month and Verizon has only throttled me once down to 20mbps. I am happy.
[QUOTE=Amiga OS;45448718]You might have gotten the update to use TrueType instead of the in-built garbage.[/QUOTE] Oh. Yeah, probably. It does look a lot better.
What the shit, SweetTunes1 got into fucking Chrome. It's like a fly that refuses to get out.
[QUOTE=garychencool;45447620]what's the point of 10 bit anime anyways?[/QUOTE] In theory it can reduce banding but the real issue is that people who do encodes in the anime community are actually really terrible and don't know what they're doing. I've seen 1920x1080 files encoded at CRF 13, that's just insane and way out of H.264 spec. There are lots of Hi10P anime files that have banding and it's a combination of bad encoders and bad sources to begin with. The reason the ITU specified 8bit per channel for sRGB / Rec. 709 content is because if you go from zero saturation all the way out to 100% saturation of a primary color with 256 steps you shouldn't see any banding in that gradient. Even the highest end monitors for working with sRGB content are only 8bit, maybe 8bit + AFRC just in case. But the only time you really see native 10bit color depth is for working with AdobeRGB. With something encoded to 10bit high profile H.264 you have better prediction and the encoder's internal precision is better which leads to less rounding errors. In theory this more than offsets the increased size by storing color info in a 10bit per channel format and you get a reduced file size. In practice, nobody does this and they just boost the quality even more to use that space they "saved" even though at the CRF levels they encode at you basically can't see any difference anyway. People who encode anime with ffmpeg claiming they know better than display scientists at the ITU shows a lot of hubris. It can also reduce color banding by again, reducing rounding errors in the color information by storing it in higher precision 10bit per channel pixels. I have 10bit encodes that have banding and I'm currently doing my own encode of Cardcaptor Sakura in normal H.264 with 8bit precision and 4:2:0 chroma and I'm yet to see any banding 20 episodes in. The gamut seriously isn't big enough for banding issues to show up even when encoding or re-encoding to 8bit. The scenario I think 10bit would be better applicable to is retaining smooth gradients with lower bitrate content, but since many anime encoders produce bloated files with massive bitrates it doesn't really matter. What should be taken note of is that most links on wiki pages for Hi10P in the anime community go to dead links, and every single one that isn't dead goes to x264 / doom9 forums which means they're all basically the same citation of a forum. By the time you set up your MPC-HC with stuff like madVR and de-interlacing filters that doom9 recommends you'll need a GTX 660 just to decode the video without dropping frames, and I think you'd be hard pressed to notice the improvement in things like chroma upscaling. Something else to be noted is that nobody has ever complained about banding in movie encodes or on the video transmitted to their TV and we've been using the same color gamut and bit depth that we do today since 1982, it's only anime. This suggests it's either bad people doing the encodes, bad sources, or both, and not a technological issue. [editline]20th July 2014[/editline] [QUOTE=garychencool;45448605]I seem to be able to watch 10-bit on my geforce 210 the last time I tried...[/QUOTE] It's probably decoding on the CPU.
[QUOTE=Kaabii;45448859]In theory it can reduce banding but the real issue is that people who do encodes in the anime community are actually really terrible and don't know what they're doing. I've seen 1920x1080 files encoded at CRF 13, that's just insane and way out of H.264 spec. There are lots of Hi10P anime files that have banding and it's a combination of bad encoders and bad sources to begin with. The reason the ITU specified 8bit per channel for sRGB / Rec. 709 content is because if you go from zero saturation all the way out to 100% saturation of a primary color with 256 steps you shouldn't see any banding in that gradient. Even the highest end monitors for working with sRGB content are only 8bit, maybe 8bit + AFRC just in case. But the only time you really see native 10bit color depth is for working with AdobeRGB. With something encoded to 10bit high profile H.264 you have better prediction and the encoder's internal precision is better which leads to less rounding errors. In theory this more than offsets the increased size by storing color info in a 10bit per channel format and you get a reduced file size. In practice, nobody does this and they just boost the quality even more to use that space they "saved" even though at the CRF levels they encode at you basically can't see any difference anyway. People who encode anime with ffmpeg claiming they know better than display scientists at the ITU shows a lot of hubris. It can also reduce color banding by again, reducing rounding errors in the color information by storing it in higher precision 10bit per channel pixels. I have 10bit encodes that have banding and I'm currently doing my own encode of Cardcaptor Sakura in normal H.264 with 8bit precision and 4:2:0 chroma and I'm yet to see any banding 20 episodes in. The gamut seriously isn't big enough for banding issues to show up even when encoding or re-encoding to 8bit. The scenario I think 10bit would be better applicable to is retaining smooth gradients with lower bitrate content, but since many anime encoders produce bloated files with massive bitrates it doesn't really matter. What should be taken note of is that most links on wiki pages for Hi10P in the anime community go to dead links, and every single one that isn't dead goes to x264 / doom9 forums which means they're all basically the same citation of a forum. By the time you set up your MPC-HC with stuff like madVR and de-interlacing filters that doom9 recommends you'll need a GTX 660 just to decode the video without dropping frames, and I think you'd be hard pressed to notice the improvement in things like chroma upscaling. Something else to be noted is that nobody has ever complained about banding in movie encodes or on the video transmitted to their TV and we've been using the same color gamut and bit depth that we do today since 1982, it's only anime. This suggests it's either bad people doing the encodes, bad sources, or both, and not a technological issue. [editline]20th July 2014[/editline] It's probably decoding on the CPU.[/QUOTE] all this nerd shit is great but anime is best watched at 240p on youtube with spanish subtitles
well... the csgo mini-scoreboard is burnt into my monitor.... i only have 84 hours too so thats really weird..
I watch my chinese cartoons in any video quality I find. I'm used to 240p youtube videos, so I couldn't care less.
[QUOTE=Kaabii;45448859]People who encode anime with ffmpeg claiming they know better than display scientists at the ITU shows a lot of hubris.[/QUOTE] Kinda reminds me of people whose Gentoo CFLAGS/CXXFLAGS/CPPFLAGS are longer than that post of yours.
[QUOTE=paul simon;45447422]Might finally pick it up then, been waiting for that.[/QUOTE] To bad i cant use it, before it used to work with battlelog now it doesn't even though BF4 is x64 what joke.
Fuck battlelog [editline]20th July 2014[/editline] battle log-of-shit
[QUOTE=Levelog;45448356]He's probably on brain 7. Ive I've heard brain 8 fixes a lot of these power states.[/QUOTE] brain 8.1 master race
[QUOTE=PollytheParrot;45449310]brain 8.1 master race[/QUOTE] OpenBRAIN 5.5 here, represent. Most secure brain OS - only two holes in a default install in the past three decades! And it's even more open than gnuBRAIN or linBrain.
From the Elder Scrolls thread. [t]http://static-3.nexusmods.com/15/mods/110/images/55796-4-1404931368.jpg[/t]
[QUOTE=MasterFen006;45449690]From the Elder Scrolls thread. [t]http://static-3.nexusmods.com/15/mods/110/images/55796-4-1404931368.jpg[/t][/QUOTE] Eh, I prefer dual tower swords.
what the fuck does this even mean [img]http://i.imgur.com/bPpE2eF.png[/img]
[QUOTE=Banandana;45449933]what the fuck does this even mean [img]http://i.imgur.com/bPpE2eF.png[/img][/QUOTE] This program is not supposed to work by design.
You should add me on steam and help me figure this shit out [editline]20th July 2014[/editline] because WinHiip fails like almost every time
[QUOTE=~Kiwi~v2;45444887]yeah anything above 2000 is decent for 30 fps streams 3500 60 fps though is another feet.[/QUOTE] Ehh, it's subjective. I always put my regular full streams on my YT channel as an archive for people to watch. And going from 2mbps main/3.1 to 1.5-2mbps main/3.1 is not fun, so I just try to get as high as I can with most of my viewers able to receive it. It did look really clear so I might drop it from 2250 to 2000.
[QUOTE=Banandana;45449989]You should add me on steam and help me figure this shit out [editline]20th July 2014[/editline] because WinHiip fails like almost every time[/QUOTE] Sometimes HDLdumb breaks the file system of the HDD in the PS2 and you have to sort it out in winhiip.
[QUOTE='[EG] Pepper;45450618']Sometimes HDLdumb breaks the file system of the HDD in the PS2 and you have to sort it out in winhiip.[/QUOTE] Yeah, I think this enclosure is a bit buggy when mixed with this drive, so on W7 it literally won't write anything to the drive (WinHiip) but under a VM, it's super flaky with a 50% failure rate. Using hdl_dumb works better (~80%) but I just tried an older version of WinHiip (1.7.2 instead of 1.7.6) and it seems to have written all of them without issue so far. I thought it was because the drive gets super fucking hot, but I think it'll be ok and it's more of a software issue. The drive seems to be working ok.
[QUOTE=Kaabii;45448859] It's probably decoding on the CPU.[/QUOTE] yeah that makes more sense with an i5
And just to reiterate this, screw all (well a portion) of you. Got exams next week, but I've been sitting here all day watching CB.
[QUOTE=Chubbs;45448643]why are you expecting to be unable to[/QUOTE] because [QUOTE=.Lain;45448449] basically it's meant to make files smaller at the same quality as 8-bit. but in turn, hardware support is minimal for 10bit. no consumer grade GPU supports 10 bit video decoding, so it's both harder to decode and often even bigger than the 8bit counterparts because the encoders don't realise what it's actually meant to do [/QUOTE]
[QUOTE=Levelog;45448789]41.7 gigs of data so far this month and Verizon has only throttled me once down to 20mbps. I am happy.[/QUOTE] 20mbps? alright i can still pull 1TB out of that thing.
[QUOTE=~Kiwi~v2;45451575]20mbps? alright i can still pull 1TB out of that thing.[/QUOTE] Was only overnight. Back up to 60+ down/45 up by morning.
I'm going to be finishing what I needed to in Metro LL tonight. We got like 90minutes left until the church and then I will restart my normal LP from there. Twitch.tv/sircrest If anyone is interested.
[QUOTE=Levelog;45448789]41.7 gigs of data so far this month and Verizon has only throttled me once down to 20mbps. I am happy.[/QUOTE] So far on Rogers, they haven't throttle me at all, at least it doesn't seem like it at all.
[QUOTE=garychencool;45452038]So far on Rogers, they haven't throttle me at all, at least it doesn't seem like it at all.[/QUOTE] It's been a while since I last checked, but I believe Verizon's works something like after 2.5 gigs you get throttled based on traffic for your tower. Essentially less priority.
[QUOTE=Levelog;45452123]It's been a while since I last checked, but I believe Verizon's works something like after 2.5 gigs you get throttled based on traffic for your tower. Essentially less priority.[/QUOTE] Rogers seems to not care which is good. I've probably used 100GB by now from my local tower at my home.
Sorry, you need to Log In to post a reply to this thread.