text
stringlengths
11
654
[1945.46 --> 1945.66] yeah.
[1946.20 --> 1946.56] Alright,
[1946.80 --> 1947.14] so,
[1947.28 --> 1947.98] you know what's funny
[1947.98 --> 1948.98] is there was a post
[1948.98 --> 1949.84] in this thread.
[1949.94 --> 1950.62] So this was originally
[1950.62 --> 1951.80] posted by Tech Fanatic
[1951.80 --> 1952.34] on the forum,
[1952.34 --> 1953.04] thank you very much
[1953.04 --> 1953.48] for posting,
[1953.88 --> 1954.86] that said that
[1954.86 --> 1955.32] like,
[1955.58 --> 1956.20] ha ha ha,
[1956.34 --> 1957.44] Linus was so down
[1957.44 --> 1959.38] on AMD's FreeSync,
[1959.70 --> 1960.06] lol,
[1960.36 --> 1961.12] you know,
[1961.22 --> 1962.16] goes to show him.
[1962.30 --> 1963.00] And I was a little bit
[1963.00 --> 1963.70] confused by that.
[1963.76 --> 1965.02] Was I ever at any point
[1965.02 --> 1966.12] down on FreeSync?
[1966.12 --> 1967.44] A little bit.
[1968.20 --> 1968.74] What did I say?
[1968.80 --> 1969.28] You said it wasn't
[1969.28 --> 1969.86] going to work.
[1970.56 --> 1971.10] But then I think you,
[1971.16 --> 1971.38] I think you,
[1971.38 --> 1972.16] I said it wouldn't work
[1972.16 --> 1973.10] with the scalers now.
[1973.32 --> 1973.56] Yeah,
[1973.78 --> 1974.84] and I'm pretty sure
[1974.84 --> 1975.86] specific words
[1975.86 --> 1976.74] were current form.
[1976.94 --> 1977.96] And I said that
[1977.96 --> 1978.88] that was NVIDIA
[1978.88 --> 1979.60] saying that.
[1980.16 --> 1980.44] Yeah.
[1981.26 --> 1982.08] And actually,
[1982.08 --> 1983.22] I know that you said
[1983.22 --> 1983.68] it won't work
[1983.68 --> 1984.40] in its current form.
[1984.62 --> 1985.48] And when the news
[1985.48 --> 1986.52] first broke
[1986.52 --> 1988.28] on Nantech,
[1988.40 --> 1989.54] I actually posted
[1989.54 --> 1990.32] that to Facebook
[1990.32 --> 1991.32] and I was like,
[1991.64 --> 1992.14] holy crap,
[1992.22 --> 1993.04] does this completely
[1993.04 --> 1994.84] invalidate G-Sync's existence?
[1995.72 --> 1996.04] Yeah.
[1996.30 --> 1996.66] So,
[1996.84 --> 1997.20] I don't know
[1997.20 --> 1998.20] where all this came from,
[1998.32 --> 1999.30] but I am totally
[1999.30 --> 2001.04] 100% on board
[2001.04 --> 2002.80] with AMD's FreeSync,
[2002.92 --> 2004.44] now called ActiveSync.
[2004.92 --> 2005.70] There's one thing
[2005.70 --> 2006.70] that I'm a little bit
[2006.70 --> 2008.00] sketched out about so far,
[2008.12 --> 2008.64] and that was
[2008.64 --> 2009.52] doing some reading.
[2009.82 --> 2011.96] It's not 100% clear to me
[2011.96 --> 2012.86] what cards it's going
[2012.86 --> 2013.38] to work on,
[2013.70 --> 2015.52] because it looks like
[2015.52 --> 2016.56] they're saying
[2016.56 --> 2019.22] R9 290X
[2019.22 --> 2021.28] and 260X,
[2021.52 --> 2022.62] which would basically
[2022.62 --> 2025.42] be Hawaii version,
[2025.90 --> 2026.66] whatever it is,
[2026.72 --> 2027.32] the new ones.
[2027.92 --> 2028.44] So,
[2028.58 --> 2029.72] not the rebadges
[2029.72 --> 2031.20] of the Tahiti Core ones.
[2031.72 --> 2033.14] Which would really suck.
[2033.20 --> 2033.58] Which would be
[2033.58 --> 2034.20] really sucky.
[2034.28 --> 2034.74] And then there's
[2034.74 --> 2035.38] no mention
[2035.38 --> 2036.68] of NVIDIA cards.
[2036.84 --> 2036.98] Now,
[2037.48 --> 2038.70] what I think is,
[2039.56 --> 2041.68] AMD's whole stance
[2041.68 --> 2042.86] lately has been
[2042.86 --> 2043.66] open standards
[2043.66 --> 2044.34] this and that,
[2044.60 --> 2046.22] so I sincerely hope
[2046.22 --> 2047.64] that it's an open standard,
[2048.24 --> 2049.08] but,
[2049.22 --> 2050.86] I would hate
[2050.86 --> 2052.38] to see it happen,
[2052.76 --> 2053.92] where NVIDIA's pushing
[2053.92 --> 2054.98] a G-Sync standard,
[2055.42 --> 2056.64] and AMD's pushing
[2056.64 --> 2058.04] an Adaptive Sync standard,