Recommended Posts

Just a side note... :whistle:

the picture of the rectangle and the spiral also relate to Phi/phi

Phi = 1.61803 (39887 49894 84820 45868 34365 63811 77203 09179 80576)

phi = 0.61803 (39887 49894 84820 45868 34365 63811 77203 09179 80576)

phi ^2 = phi + 1

phi * phi = Phi

Phi * Phi = Phi + 1

http://mathworld.wolfram.com/GoldenRatio.html

equation10.gif

Fibonacci sequence...

0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, 233, 377, 610, 987 etc...

the further you go in the sequence when you divide a number by the preceding number you'll keep getting closer to phi.

also: http://goldennumber.net/body.htm

5 ^ .5 * .5 + .5 = Phi

http://en.wikipedia.org/wiki/Golden_ratio

all referring to: ( http://www.vanishingpointgame.com/rpiiajsuy/ )

Edited by yanowhiz

May want to keep an eye on this page: http://www.youtube.com/profile?user=lokivanishes (found by drizjr)

Registered the same day as lokivanishes registered here on neowin. Some other registrations on other tech related discussion boards was found in #vanishing chat this evening.

Found this one: http://flickr.com/photos/36095545@N00/ (profile name: lokivanishes).

has anyone seen this?

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">'>http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >

<head><title>

Vanishing Point

</title>

<script type="text/javascript" src="js42/AC_RunActiveContent.js"></script>

<script type="text/javascript" src="js42/detection.js"></script>

<script type="text/vbscript" src="js42/flashutil.vbs"></script>

<style type="text/css">

body{

background-color:Black;

margin-top:0px;

}

</style>

</head>

<body>

<center>

<div>

<form name="form1" method="post" action="start.aspx" id="form1">

<div>

<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKMTUxMzcyMjQyN2RkbyO7jpOtE1Mb07Hm2nrpSyWWoQo=" />

</div>

</form>

<script language="JavaScript" type="text/javascript">

<!--

swfUrl = 'login_s';

myWidth = '800';

myHeight = '600';

myID = 'login';

myBGColor = '#000000';

var hasRightVersion = DetectFlashVer(requiredMajorVersion, requiredMinorVersion, requiredRevision);

if(hasRightVersion) {

var arguments = new Array('id',myID,'codebase','http://fpdownload.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=8,0,0,0','width',myWidth,'height',myHeight,'align','middle','src',swfUrl,'quality','high','bgcolor',myBGColor,'name',myID,'allowscriptaccess','always','pluginspage','http://www.macromedia.com/go/getflashplayer','movie',swfUrl,'flashvars','parse=1&homeurlparam=http://www.vanishingpointgame.com/&sslhomeurlparam=http://www.vanishingpointgame.com/');

var ret = AC_GetArgs(arguments, ".swf", "movie", "clsid:d27cdb6e-ae6d-11cf-96b8-444553540000", "application/x-shockwave-flash");

AC_Generateobj(ret.objAttrs, ret.params, ret.embedAttrs);

}

-->

</script>

</div>

</center>

<!-- PIN=5813 -->

</body>

</html>

and i an using firefox and cant see the site dono y anyone can help

and i found this i got no clue what this is but mabe something

<!--

Extensible HTML version 1.0 Transitional DTD

This is the same as HTML 4 Transitional except for

changes due to the differences between XML and SGML.

Namespace = http://www.w3.org/1999/xhtml

For further information, see: http://www.w3.org/TR/xhtml1

Copyright © 1998-2002 W3C (MIT, INRIA, Keio),

All Rights Reserved.

This DTD module is identified by the PUBLIC and SYSTEM identifiers:

PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

SYSTEM "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"

$Revision: 1.2 $

$Date: 2002/08/01 18:37:55 $

-->

<!--================ Character mnemonic entities =========================-->

<!ENTITY % HTMLlat1 PUBLIC

"-//W3C//ENTITIES Latin 1 for XHTML//EN"

"xhtml-lat1.ent">

%HTMLlat1;

<!ENTITY % HTMLsymbol PUBLIC

"-//W3C//ENTITIES Symbols for XHTML//EN"

"xhtml-symbol.ent">

%HTMLsymbol;

<!ENTITY % HTMLspecial PUBLIC

"-//W3C//ENTITIES Special for XHTML//EN"

"xhtml-special.ent">

%HTMLspecial;

<!--================== Imported Names ====================================-->

<!ENTITY % ContentType "CDATA">

<!-- media type, as per [RFC2045] -->

<!ENTITY % ContentTypes "CDATA">

<!-- comma-separated list of media types, as per [RFC2045] -->

<!ENTITY % Charset "CDATA">

<!-- a character encoding, as per [RFC2045] -->

<!ENTITY % Charsets "CDATA">

<!-- a space separated list of character encodings, as per [RFC2045] -->

<!ENTITY % LanguageCode "NMTOKEN">

<!-- a language code, as per [RFC3066] -->

<!ENTITY % Character "CDATA">

<!-- a single character, as per section 2.2 of

 -->

<!ENTITY % Number "CDATA">

<!-- one or more digits -->

<!ENTITY % LinkTypes "CDATA">

<!-- space-separated list of link types -->

<!ENTITY % MediaDesc "CDATA">

<!-- single or comma-separated list of media descriptors -->

<!ENTITY % URI "CDATA">

<!-- a Uniform Resource Identifier, see [RFC2396] -->

<!ENTITY % UriList "CDATA">

<!-- a space separated list of Uniform Resource Identifiers -->

<!ENTITY % Datetime "CDATA">

<!-- date and time information. ISO date format -->

<!ENTITY % Script "CDATA">

<!-- script expression -->

<!ENTITY % StyleSheet "CDATA">

<!-- style sheet data -->

<!ENTITY % Text "CDATA">

<!-- used for titles etc. -->

<!ENTITY % FrameTarget "NMTOKEN">

<!-- render in this frame -->

<!ENTITY % Length "CDATA">

<!-- nn for pixels or nn% for percentage length -->

<!ENTITY % MultiLength "CDATA">

<!-- pixel, percentage, or relative -->

<!ENTITY % Pixels "CDATA">

<!-- integer representing length in pixels -->

<!-- these are used for image maps -->

<!ENTITY % Shape "(rect|circle|poly|default)">

<!ENTITY % Coords "CDATA">

<!-- comma separated list of lengths -->

<!-- used for object, applet, img, input and iframe -->

<!ENTITY % ImgAlign "(top|middle|bottom|left|right)">

<!-- a color using sRGB: #RRGGBB as Hex values -->

<!ENTITY % Color "CDATA">

<!-- There are also 16 widely known color names with their sRGB values:

Black = #000000 Green = #008000

Silver = #C0C0C0 Lime = #00FF00

Gray = #808080 Olive = #808000

White = #FFFFFF Yellow = #FFFF00

Maroon = #800000 Navy = #000080

Red = #FF0000 Blue = #0000FF

Purple = #800080 Teal = #008080

Fuchsia= #FF00FF Aqua = #00FFFF

-->

<!--=================== Generic Attributes ===============================-->

<!-- core attributes common to most elements

id document-wide unique id

class space separated list of classes

style associated style info

title advisory title/amplification

-->

<!ENTITY % coreattrs

"id ID #IMPLIED

class CDATA #IMPLIED

style %StyleSheet; #IMPLIED

title %Text; #IMPLIED"

>

<!-- internationalization attributes

lang language code (backwards compatible)

xml:lang language code (as per XML 1.0 spec)

dir direction for weak/neutral text

-->

<!ENTITY % i18n

"lang %LanguageCode; #IMPLIED

xml:lang %LanguageCode; #IMPLIED

dir (ltr|rtl) #IMPLIED"

>

<!-- attributes for common UI events

onclick a pointer button was clicked

ondblclick a pointer button was double clicked

onmousedown a pointer button was pressed down

onmouseup a pointer button was released

onmousemove a pointer was moved onto the element

onmouseout a pointer was moved away from the element

onkeypress a key was pressed and released

onkeydown a key was pressed down

onkeyup a key was released

-->

<!ENTITY % events

"onclick %Script; #IMPLIED

ondblclick %Script; #IMPLIED

onmousedown %Script; #IMPLIED

onmouseup %Script; #IMPLIED

onmouseover %Script; #IMPLIED

onmousemove %Script; #IMPLIED

onmouseout %Script; #IMPLIED

onkeypress %Script; #IMPLIED

onkeydown %Script; #IMPLIED

onkeyup %Script; #IMPLIED"

>

<!-- attributes for elements that can get the focus

accesskey accessibility key character

tabindex position in tabbing order

onfocus the element got the focus

onblur the element lost the focus

-->

<!ENTITY % focus

"accesskey %Character; #IMPLIED

tabindex %Number; #IMPLIED

onfocus %Script; #IMPLIED

onblur %Script; #IMPLIED"

>

<!ENTITY % attrs "%coreattrs; %i18n; %events;">

<!-- text alignment for p, div, h1-h6. The default is

align="left" for ltr headings, "right" for rtl -->

<!ENTITY % TextAlign "align (left|center|right|justify) #IMPLIED">

<!--=================== Text Elements ====================================-->

<!ENTITY % special.extra

"object | applet | img | map | iframe">

<!ENTITY % special.basic

"br | span | bdo">

<!ENTITY % special

"%special.basic; | %special.extra;">

<!ENTITY % fontstyle.extra "big | small | font | basefont">

<!ENTITY % fontstyle.basic "tt | i | b | u

| s | strike ">

<!ENTITY % fontstyle "%fontstyle.basic; | %fontstyle.extra;">

<!ENTITY % phrase.extra "sub | sup">

<!ENTITY % phrase.basic "em | strong | dfn | code | q |

samp | kbd | var | cite | abbr | acronym">

<!ENTITY % phrase "%phrase.basic; | %phrase.extra;">

<!ENTITY % inline.forms "input | select | textarea | label | button">

<!-- these can occur at block or inline level -->

<!ENTITY % misc.inline "ins | del | script">

<!-- these can only occur at block level -->

<!ENTITY % misc "noscript | %misc.inline;">

<!ENTITY % inline "a | %special; | %fontstyle; | %phrase; | %inline.forms;">

<!-- %Inline; covers inline or "text-level" elements -->

<!ENTITY % Inline "(#PCDATA | %inline; | %misc.inline;)*">

<!--================== Block level elements ==============================-->

<!ENTITY % heading "h1|h2|h3|h4|h5|h6">

<!ENTITY % lists "ul | ol | dl | menu | dir">

<!ENTITY % blocktext "pre | hr | blockquote | address | center | noframes">

<!ENTITY % block

"p | %heading; | div | %lists; | %blocktext; | isindex |fieldset | table">

<!-- %Flow; mixes block and inline and is used for list items etc. -->

<!ENTITY % Flow "(#PCDATA | %block; | form | %inline; | %misc;)*">

<!--================== Content models for exclusions =====================-->

<!-- a elements use %Inline; excluding a -->

<!ENTITY % a.content

"(#PCDATA | %special; | %fontstyle; | %phrase; | %inline.forms; | %misc.inline;)*">

<!-- pre uses %Inline excluding img, object, applet, big, small,

font, or basefont -->

<!ENTITY % pre.content

"(#PCDATA | a | %special.basic; | %fontstyle.basic; | %phrase.basic; |

%inline.forms; | %misc.inline;)*">

<!-- form uses %Flow; excluding form -->

<!ENTITY % form.content "(#PCDATA | %block; | %inline; | %misc;)*">

<!-- button uses %Flow; but excludes a, form, form controls, iframe -->

<!ENTITY % button.content

"(#PCDATA | p | %heading; | div | %lists; | %blocktext; |

table | br | span | bdo | object | applet | img | map |

%fontstyle; | %phrase; | %misc;)*">

<!--================ Document Structure ==================================-->

<!-- the namespace URI designates the document profile -->

<!ELEMENT html (head, body)>

<!ATTLIST html

%i18n;

id ID #IMPLIED

xmlns %URI; #FIXED 'http://www.w3.org/1999/xhtml'

>

<!--================ Document Head =======================================-->

<!ENTITY % head.misc "(script|style|meta|link|object|isindex)*">

<!-- content model is %head.misc; combined with a single

title and an optional base element in any order -->

<!ELEMENT head (%head.misc;,

((title, %head.misc;, (base, %head.misc;)?) |

(base, %head.misc;, (title, %head.misc;))))>

<!ATTLIST head

%i18n;

id ID #IMPLIED

profile %URI; #IMPLIED

>

<!-- The title element is not considered part of the flow of text.

It should be displayed, for example as the page header or

window title. Exactly one title is required per document.

-->

<!ELEMENT title (#PCDATA)>

<!ATTLIST title

%i18n;

id ID #IMPLIED

>

<!-- document base URI -->

<!ELEMENT base EMPTY>

<!ATTLIST base

id ID #IMPLIED

href %URI; #IMPLIED

target %FrameTarget; #IMPLIED

>

<!-- generic metainformation -->

<!ELEMENT meta EMPTY>

<!ATTLIST meta

%i18n;

id ID #IMPLIED

http-equiv CDATA #IMPLIED

name CDATA #IMPLIED

content CDATA #REQUIRED

scheme CDATA #IMPLIED

>

<!--

Relationship values can be used in principle:

a) for document specific toolbars/menus when used

with the link element in document head e.g.

start, contents, previous, next, index, end, help

b) to link to a separate style sheet (rel="stylesheet")

c) to make a link to a script (rel="script")

d) by stylesheets to control how collections of

html nodes are rendered into printed documents

e) to make a link to a printable version of this document

e.g. a PostScript or PDF version (rel="alternate" media="print")

-->

<!ELEMENT link EMPTY>

<!ATTLIST link

%attrs;

charset %Charset; #IMPLIED

href %URI; #IMPLIED

hreflang %LanguageCode; #IMPLIED

type %ContentType; #IMPLIED

rel %LinkTypes; #IMPLIED

rev %LinkTypes; #IMPLIED

media %MediaDesc; #IMPLIED

target %FrameTarget; #IMPLIED

>

<!-- style info, which may include CDATA sections -->

<!ELEMENT style (#PCDATA)>

<!ATTLIST style

%i18n;

id ID #IMPLIED

type %ContentType; #REQUIRED

media %MediaDesc; #IMPLIED

title %Text; #IMPLIED

xml:space (preserve) #FIXED 'preserve'

>

<!-- script statements, which may include CDATA sections -->

<!ELEMENT script (#PCDATA)>

<!ATTLIST script

id ID #IMPLIED

charset %Charset; #IMPLIED

type %ContentType; #REQUIRED

language CDATA #IMPLIED

src %URI; #IMPLIED

defer (defer) #IMPLIED

xml:space (preserve) #FIXED 'preserve'

>

<!-- alternate content container for non script-based rendering -->

<!ELEMENT noscript %Flow;>

<!ATTLIST noscript

%attrs;

>

<!--======================= Frames =======================================-->

<!-- inline subwindow -->

<!ELEMENT iframe %Flow;>

<!ATTLIST iframe

%coreattrs;

longdesc %URI; #IMPLIED

name NMTOKEN #IMPLIED

src %URI; #IMPLIED

frameborder (1|0) "1"

marginwidth %Pixels; #IMPLIED

marginheight %Pixels; #IMPLIED

scrolling (yes|no|auto) "auto"

align %ImgAlign; #IMPLIED

height %Length; #IMPLIED

width %Length; #IMPLIED

>

<!-- alternate content container for non frame-based rendering -->

<!ELEMENT noframes %Flow;>

<!ATTLIST noframes

%attrs;

>

<!--=================== Document Body ====================================-->

<!ELEMENT body %Flow;>

<!ATTLIST body

%attrs;

onload %Script; #IMPLIED

onunload %Script; #IMPLIED

background %URI; #IMPLIED

bgcolor %Color; #IMPLIED

text %Color; #IMPLIED

link %Color; #IMPLIED

vlink %Color; #IMPLIED

alink %Color; #IMPLIED

>

<!ELEMENT div %Flow;> <!-- generic language/style container -->

<!ATTLIST div

%attrs;

%TextAlign;

>

<!--=================== Paragraphs =======================================-->

<!ELEMENT p %Inline;>

<!ATTLIST p

%attrs;

%TextAlign;

>

<!--=================== Headings =========================================-->

<!--

There are six levels of headings from h1 (the most important)

to h6 (the least important).

-->

<!ELEMENT h1 %Inline;>

<!ATTLIST h1

%attrs;

%TextAlign;

>

<!ELEMENT h2 %Inline;>

<!ATTLIST h2

%attrs;

%TextAlign;

>

<!ELEMENT h3 %Inline;>

<!ATTLIST h3

%attrs;

%TextAlign;

>

<!ELEMENT h4 %Inline;>

<!ATTLIST h4

%attrs;

%TextAlign;

>

<!ELEMENT h5 %Inline;>

<!ATTLIST h5

%attrs;

%TextAlign;

>

<!ELEMENT h6 %Inline;>

<!ATTLIST h6

%attrs;

%TextAlign;

>

<!--=================== Lists ============================================-->

<!-- Unordered list bullet styles -->

<!ENTITY % ULStyle "(disc|square|circle)">

<!-- Unordered list -->

<!ELEMENT ul (li)+>

<!ATTLIST ul

%attrs;

type %ULStyle; #IMPLIED

compact (compact) #IMPLIED

>

<!-- Ordered list numbering style

1 arabic numbers 1, 2, 3, ...

a lower alpha a, b, c, ...

A upper alpha A, B, C, ...

i lower roman i, ii, iii, ...

I upper roman I, II, III, ...

The style is applied to the sequence number which by default

is reset to 1 for the first list item in an ordered list.

-->

<!ENTITY % OLStyle "CDATA">

<!-- Ordered (numbered) list -->

<!ELEMENT ol (li)+>

<!ATTLIST ol

%attrs;

type %OLStyle; #IMPLIED

compact (compact) #IMPLIED

start %Number; #IMPLIED

>

<!-- single column list (DEPRECATED) -->

<!ELEMENT menu (li)+>

<!ATTLIST menu

%attrs;

compact (compact) #IMPLIED

>

<!-- multiple column list (DEPRECATED) -->

<!ELEMENT dir (li)+>

<!ATTLIST dir

%attrs;

compact (compact) #IMPLIED

>

<!-- LIStyle is constrained to: "(%ULStyle;|%OLStyle;)" -->

<!ENTITY % LIStyle "CDATA">

<!-- list item -->

<!ELEMENT li %Flow;>

<!ATTLIST li

%attrs;

type %LIStyle; #IMPLIED

value %Number; #IMPLIED

>

<!-- definition lists - dt for term, dd for its definition -->

<!ELEMENT dl (dt|dd)+>

<!ATTLIST dl

%attrs;

compact (compact) #IMPLIED

>

<!ELEMENT dt %Inline;>

<!ATTLIST dt

%attrs;

>

<!ELEMENT dd %Flow;>

<!ATTLIST dd

%attrs;

>

<!--=================== Address ==========================================-->

<!-- information on author -->

<!ELEMENT address (#PCDATA | %inline; | %misc.inline; | p)*>

<!ATTLIST address

%attrs;

>

<!--=================== Horizontal Rule ==================================-->

<!ELEMENT hr EMPTY>

<!ATTLIST hr

%attrs;

align (left|center|right) #IMPLIED

noshade (noshade) #IMPLIED

size %Pixels; #IMPLIED

width %Length; #IMPLIED

>

<!--=================== Preformatted Text ================================-->

<!-- content is %Inline; excluding

"img|object|applet|big|small|sub|sup|font|basefont" -->

<!ELEMENT pre %pre.content;>

<!ATTLIST pre

%attrs;

width %Number; #IMPLIED

xml:space (preserve) #FIXED 'preserve'

>

<!--=================== Block-like Quotes ================================-->

<!ELEMENT blockquote %Flow;>

<!ATTLIST blockquote

%attrs;

cite %URI; #IMPLIED

>

<!--=================== Text alignment ===================================-->

<!-- center content -->

<!ELEMENT center %Flow;>

<!ATTLIST center

%attrs;

>

<!--=================== Inserted/Deleted Text ============================-->

<!--

ins/del are allowed in block and inline content, but its

inappropriate to include block content within an ins element

occurring in inline content.

-->

<!ELEMENT ins %Flow;>

<!ATTLIST ins

%attrs;

cite %URI; #IMPLIED

datetime %Datetime; #IMPLIED

>

<!ELEMENT del %Flow;>

<!ATTLIST del

%attrs;

cite %URI; #IMPLIED

datetime %Datetime; #IMPLIED

>

<!--================== The Anchor Element ================================-->

<!-- content is %Inline; except that anchors shouldn't be nested -->

<!ELEMENT a %a.content;>

<!ATTLIST a

%attrs;

%focus;

charset %Charset; #IMPLIED

type %ContentType; #IMPLIED

name NMTOKEN #IMPLIED

href %URI; #IMPLIED

hreflang %LanguageCode; #IMPLIED

rel %LinkTypes; #IMPLIED

rev %LinkTypes; #IMPLIED

shape %Shape; "rect"

coords %Coords; #IMPLIED

target %FrameTarget; #IMPLIED

>

<!--===================== Inline Elements ================================-->

<!ELEMENT span %Inline;> <!-- generic language/style container -->

<!ATTLIST span

%attrs;

>

<!ELEMENT bdo %Inline;> <!-- I18N BiDi over-ride -->

<!ATTLIST bdo

%coreattrs;

%events;

lang %LanguageCode; #IMPLIED

xml:lang %LanguageCode; #IMPLIED

dir (ltr|rtl) #REQUIRED

>

<!ELEMENT br EMPTY> <!-- forced line break -->

<!ATTLIST br

%coreattrs;

clear (left|all|right|none) "none"

>

<!ELEMENT em %Inline;> <!-- emphasis -->

<!ATTLIST em %attrs;>

<!ELEMENT strong %Inline;> <!-- strong emphasis -->

<!ATTLIST strong %attrs;>

<!ELEMENT dfn %Inline;> <!-- definitional -->

<!ATTLIST dfn %attrs;>

<!ELEMENT code %Inline;> <!-- program code -->

<!ATTLIST code %attrs;>

<!ELEMENT samp %Inline;> <!-- sample -->

<!ATTLIST samp %attrs;>

<!ELEMENT kbd %Inline;> <!-- something user would type -->

<!ATTLIST kbd %attrs;>

<!ELEMENT var %Inline;> <!-- variable -->

<!ATTLIST var %attrs;>

<!ELEMENT cite %Inline;> <!-- citation -->

<!ATTLIST cite %attrs;>

<!ELEMENT abbr %Inline;> <!-- abbreviation -->

<!ATTLIST abbr %attrs;>

<!ELEMENT acronym %Inline;> <!-- acronym -->

<!ATTLIST acronym %attrs;>

<!ELEMENT q %Inline;> <!-- inlined quote -->

<!ATTLIST q

%attrs;

cite %URI; #IMPLIED

>

<!ELEMENT sub %Inline;> <!-- subscript -->

<!ATTLIST sub %attrs;>

<!ELEMENT sup %Inline;> <!-- superscript -->

<!ATTLIST sup %attrs;>

<!ELEMENT tt %Inline;> <!-- fixed pitch font -->

<!ATTLIST tt %attrs;>

<!ELEMENT i %Inline;> <!-- italic font -->

<!ATTLIST i %attrs;>

<!ELEMENT b %Inline;> <!-- bold font -->

<!ATTLIST b %attrs;>

<!ELEMENT big %Inline;> <!-- bigger font -->

<!ATTLIST big %attrs;>

<!ELEMENT small %Inline;> <!-- smaller font -->

<!ATTLIST small %attrs;>

<!ELEMENT u %Inline;> <!-- underline -->

<!ATTLIST u %attrs;>

<!ELEMENT s %Inline;> <!-- strike-through -->

<!ATTLIST s %attrs;>

<!ELEMENT strike %Inline;> <!-- strike-through -->

<!ATTLIST strike %attrs;>

<!ELEMENT basefont EMPTY> <!-- base font size -->

<!ATTLIST basefont

id ID #IMPLIED

size CDATA #REQUIRED

color %Color; #IMPLIED

face CDATA #IMPLIED

>

<!ELEMENT font %Inline;> <!-- local change to font -->

<!ATTLIST font

%coreattrs;

%i18n;

size CDATA #IMPLIED

color %Color; #IMPLIED

face CDATA #IMPLIED

>

<!--==================== Object ======================================-->

<!--

object is used to embed objects as part of HTML pages.

param elements should precede other content. Parameters

can also be expressed as attribute/value pairs on the

object element itself when brevity is desired.

-->

<!ELEMENT object (#PCDATA | param | %block; | form | %inline; | %misc;)*>

<!ATTLIST object

%attrs;

declare (declare) #IMPLIED

classid %URI; #IMPLIED

codebase %URI; #IMPLIED

data %URI; #IMPLIED

type %ContentType; #IMPLIED

codetype %ContentType; #IMPLIED

archive %UriList; #IMPLIED

standby %Text; #IMPLIED

height %Length; #IMPLIED

width %Length; #IMPLIED

usemap %URI; #IMPLIED

name NMTOKEN #IMPLIED

tabindex %Number; #IMPLIED

align %ImgAlign; #IMPLIED

border %Pixels; #IMPLIED

hspace %Pixels; #IMPLIED

vspace %Pixels; #IMPLIED

>

<!--

param is used to supply a named property value.

In XML it would seem natural to follow RDF and support an

abbreviated syntax where the param elements are replaced

by attribute value pairs on the object start tag.

-->

<!ELEMENT param EMPTY>

<!ATTLIST param

id ID #IMPLIED

name CDATA #REQUIRED

value CDATA #IMPLIED

valuetype (data|ref|object) "data"

type %ContentType; #IMPLIED

>

<!--=================== Java applet ==================================-->

<!--

One of code or object attributes must be present.

Place param elements before other content.

-->

<!ELEMENT applet (#PCDATA | param | %block; | form | %inline; | %misc;)*>

<!ATTLIST applet

%coreattrs;

codebase %URI; #IMPLIED

archive CDATA #IMPLIED

code CDATA #IMPLIED

object CDATA #IMPLIED

alt %Text; #IMPLIED

name NMTOKEN #IMPLIED

width %Length; #REQUIRED

height %Length; #REQUIRED

align %ImgAlign; #IMPLIED

hspace %Pixels; #IMPLIED

vspace %Pixels; #IMPLIED

>

<!--=================== Images ===========================================-->

<!--

To avoid accessibility problems for people who aren't

able to see the image, you should provide a text

description using the alt and longdesc attributes.

In addition, avoid the use of server-side image maps.

-->

<!ELEMENT img EMPTY>

<!ATTLIST img

%attrs;

src %URI; #REQUIRED

alt %Text; #REQUIRED

name NMTOKEN #IMPLIED

longdesc %URI; #IMPLIED

height %Length; #IMPLIED

width %Length; #IMPLIED

usemap %URI; #IMPLIED

ismap (ismap) #IMPLIED

align %ImgAlign; #IMPLIED

border %Length; #IMPLIED

hspace %Pixels; #IMPLIED

vspace %Pixels; #IMPLIED

>

<!-- usemap points to a map element which may be in this document

or an external document, although the latter is not widely supported -->

<!--================== Client-side image maps ============================-->

<!-- These can be placed in the same document or grouped in a

separate document although this isn't yet widely supported -->

<!ELEMENT map ((%block; | form | %misc;)+ | area+)>

<!ATTLIST map

%i18n;

%events;

id ID #REQUIRED

class CDATA #IMPLIED

style %StyleSheet; #IMPLIED

title %Text; #IMPLIED

name CDATA #IMPLIED

>

<!ELEMENT area EMPTY>

<!ATTLIST area

%attrs;

%focus;

shape %Shape; "rect"

coords %Coords; #IMPLIED

href %URI; #IMPLIED

nohref (nohref) #IMPLIED

alt %Text; #REQUIRED

target %FrameTarget; #IMPLIED

>

<!--================ Forms ===============================================-->

<!ELEMENT form %form.content;> <!-- forms shouldn't be nested -->

<!ATTLIST form

%attrs;

action %URI; #REQUIRED

method (get|post) "get"

name NMTOKEN #IMPLIED

enctype %ContentType; "application/x-www-form-urlencoded"

onsubmit %Script; #IMPLIED

onreset %Script; #IMPLIED

accept %ContentTypes; #IMPLIED

accept-charset %Charsets; #IMPLIED

target %FrameTarget; #IMPLIED

>

<!--

Each label must not contain more than ONE field

Label elements shouldn't be nested.

-->

<!ELEMENT label %Inline;>

<!ATTLIST label

%attrs;

for IDREF #IMPLIED

accesskey %Character; #IMPLIED

onfocus %Script; #IMPLIED

onblur %Script; #IMPLIED

>

<!ENTITY % InputType

"(text | password | checkbox |

radio | submit | reset |

file | hidden | image | button)"

>

<!-- the name attribute is required for all but submit & reset -->

<!ELEMENT input EMPTY> <!-- form control -->

<!ATTLIST input

%attrs;

%focus;

type %InputType; "text"

name CDATA #IMPLIED

value CDATA #IMPLIED

checked (checked) #IMPLIED

disabled (disabled) #IMPLIED

readonly (readonly) #IMPLIED

size CDATA #IMPLIED

maxlength %Number; #IMPLIED

src %URI; #IMPLIED

alt CDATA #IMPLIED

usemap %URI; #IMPLIED

onselect %Script; #IMPLIED

onchange %Script; #IMPLIED

accept %ContentTypes; #IMPLIED

align %ImgAlign; #IMPLIED

>

<!ELEMENT select (optgroup|option)+> <!-- option selector -->

<!ATTLIST select

%attrs;

name CDATA #IMPLIED

size %Number; #IMPLIED

multiple (multiple) #IMPLIED

disabled (disabled) #IMPLIED

tabindex %Number; #IMPLIED

onfocus %Script; #IMPLIED

onblur %Script; #IMPLIED

onchange %Script; #IMPLIED

>

<!ELEMENT optgroup (option)+> <!-- option group -->

<!ATTLIST optgroup

%attrs;

disabled (disabled) #IMPLIED

label %Text; #REQUIRED

>

<!ELEMENT option (#PCDATA)> <!-- selectable choice -->

<!ATTLIST option

%attrs;

selected (selected) #IMPLIED

disabled (disabled) #IMPLIED

label %Text; #IMPLIED

value CDATA #IMPLIED

>

<!ELEMENT textarea (#PCDATA)> <!-- multi-line text field -->

<!ATTLIST textarea

%attrs;

%focus;

name CDATA #IMPLIED

rows %Number; #REQUIRED

cols %Number; #REQUIRED

disabled (disabled) #IMPLIED

readonly (readonly) #IMPLIED

onselect %Script; #IMPLIED

onchange %Script; #IMPLIED

>

<!--

The fieldset element is used to group form fields.

Only one legend element should occur in the content

and if present should only be preceded by whitespace.

-->

<!ELEMENT fieldset (#PCDATA | legend | %block; | form | %inline; | %misc;)*>

<!ATTLIST fieldset

%attrs;

>

<!ENTITY % LAlign "(top|bottom|left|right)">

<!ELEMENT legend %Inline;> <!-- fieldset label -->

<!ATTLIST legend

%attrs;

accesskey %Character; #IMPLIED

align %LAlign; #IMPLIED

>

<!--

Content is %Flow; excluding a, form, form controls, iframe

-->

<!ELEMENT button %button.content;> <!-- push button -->

<!ATTLIST button

%attrs;

%focus;

name CDATA #IMPLIED

value CDATA #IMPLIED

type (button|submit|reset) "submit"

disabled (disabled) #IMPLIED

>

<!-- single-line text input control (DEPRECATED) -->

<!ELEMENT isindex EMPTY>

<!ATTLIST isindex

%coreattrs;

%i18n;

prompt %Text; #IMPLIED

>

<!--======================= Tables =======================================-->

<!-- Derived from IETF HTML table standard, see [RFC1942] -->

<!--

The border attribute sets the thickness of the frame around the

table. The default units are screen pixels.

The frame attribute specifies which parts of the frame around

the table should be rendered. The values are not the same as

CALS to avoid a name clash with the valign attribute.

-->

<!ENTITY % TFrame "(void|above|below|hsides|lhs|rhs|vsides|box|border)">

<!--

The rules attribute defines which rules to draw between cells:

If rules is absent then assume:

"none" if border is absent or border="0" otherwise "all"

-->

<!ENTITY % TRules "(none | groups | rows | cols | all)">

<!-- horizontal placement of table relative to document -->

<!ENTITY % TAlign "(left|center|right)">

<!-- horizontal alignment attributes for cell contents

char alignment char, e.g. char=':'

charoff offset for alignment char

-->

<!ENTITY % cellhalign

"align (left|center|right|justify|char) #IMPLIED

char %Character; #IMPLIED

charoff %Length; #IMPLIED"

>

<!-- vertical alignment attributes for cell contents -->

<!ENTITY % cellvalign

"valign (top|middle|bottom|baseline) #IMPLIED"

>

<!ELEMENT table

(caption?, (col*|colgroup*), thead?, tfoot?, (tbody+|tr+))>

<!ELEMENT caption %Inline;>

<!ELEMENT thead (tr)+>

<!ELEMENT tfoot (tr)+>

<!ELEMENT tbody (tr)+>

<!ELEMENT colgroup (col)*>

<!ELEMENT col EMPTY>

<!ELEMENT tr (th|td)+>

<!ELEMENT th %Flow;>

<!ELEMENT td %Flow;>

<!ATTLIST table

%attrs;

summary %Text; #IMPLIED

width %Length; #IMPLIED

border %Pixels; #IMPLIED

frame %TFrame; #IMPLIED

rules %TRules; #IMPLIED

cellspacing %Length; #IMPLIED

cellpadding %Length; #IMPLIED

align %TAlign; #IMPLIED

bgcolor %Color; #IMPLIED

>

<!ENTITY % CAlign "(top|bottom|left|right)">

<!ATTLIST caption

%attrs;

align %CAlign; #IMPLIED

>

<!--

colgroup groups a set of col elements. It allows you to group

several semantically related columns together.

-->

<!ATTLIST colgroup

%attrs;

span %Number; "1"

width %MultiLength; #IMPLIED

%cellhalign;

%cellvalign;

>

<!--

col elements define the alignment properties for cells in

one or more columns.

The width attribute specifies the width of the columns, e.g.

width=64 width in screen pixels

width=0.5* relative width of 0.5

The span attribute causes the attributes of one

col element to apply to more than one column.

-->

<!ATTLIST col

%attrs;

span %Number; "1"

width %MultiLength; #IMPLIED

%cellhalign;

%cellvalign;

>

<!--

Use thead to duplicate headers when breaking table

across page boundaries, or for static headers when

tbody sections are rendered in scrolling panel.

Use tfoot to duplicate footers when breaking table

across page boundaries, or for static footers when

tbody sections are rendered in scrolling panel.

Use multiple tbody sections when rules are needed

between groups of table rows.

-->

<!ATTLIST thead

%attrs;

%cellhalign;

%cellvalign;

>

<!ATTLIST tfoot

%attrs;

%cellhalign;

%cellvalign;

>

<!ATTLIST tbody

%attrs;

%cellhalign;

%cellvalign;

>

<!ATTLIST tr

%attrs;

%cellhalign;

%cellvalign;

bgcolor %Color; #IMPLIED

>

<!-- Scope is simpler than headers attribute for common tables -->

<!ENTITY % Scope "(row|col|rowgroup|colgroup)">

<!-- th is for headers, td for data and for cells acting as both -->

<!ATTLIST th

%attrs;

abbr %Text; #IMPLIED

axis CDATA #IMPLIED

headers IDREFS #IMPLIED

scope %Scope; #IMPLIED

rowspan %Number; "1"

colspan %Number; "1"

%cellhalign;

%cellvalign;

nowrap (nowrap) #IMPLIED

bgcolor %Color; #IMPLIED

width %Length; #IMPLIED

height %Length; #IMPLIED

>

<!ATTLIST td

%attrs;

abbr %Text; #IMPLIED

axis CDATA #IMPLIED

headers IDREFS #IMPLIED

scope %Scope; #IMPLIED

rowspan %Number; "1"

colspan %Number; "1"

%cellhalign;

%cellvalign;

nowrap (nowrap) #IMPLIED

bgcolor %Color; #IMPLIED

width %Length; #IMPLIED

height %Length; #IMPLIED

>

Just a side note... :whistle:

the picture of the rectangle and the spiral also relate to Phi/phi

Phi = 1.61803 (39887 49894 84820 45868 34365 63811 77203 09179 80576)

phi = 0.61803 (39887 49894 84820 45868 34365 63811 77203 09179 80576)

phi ^2 = phi + 1

phi * phi = Phi

Phi * Phi = Phi + 1

http://mathworld.wolfram.com/GoldenRatio.html

equation10.gif

Fibonacci sequence...

0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, 233, 377, 610, 987 etc...

the further you go in the sequence when you divide a number by the preceding number you'll keep getting closer to phi.

also: http://goldennumber.net/body.htm

5 ^ .5 * .5 + .5 = Phi

http://en.wikipedia.org/wiki/Golden_ratio

all referring to: ( http://www.vanishingpointgame.com/rpiiajsuy/ )

Yeah, I said the same thing earlier, but you said it better :p

fibonacci numbers, phi, the golden ratio, logarithmic spirals, and e are all related - pi doesn't really relate to those, except that it's another irrational constant like e and phi

May want to keep an eye on this page: http://www.youtube.com/profile?user=lokivanishes (found by drizjr)

Registered the same day as lokivanishes registered here on neowin. Some other registrations on other tech related discussion boards was found in #vanishing chat this evening.

Found this one: http://flickr.com/photos/36095545@N00/ (profile name: lokivanishes).

Another good find! From the youtube, Loki is 22 years old. The name Gm7 could possibly be a clue.

There's another lokivanishes from dec. 20: http://www.digitalmediathoughts.com/forums...a9fe25336d92bce

not sure if someone mentioned this this one already

And another... surprise surprise, dec. 20

http://www.<< spam >>/board/member.php?u=22645

That <<spam>> should be hardwaregeeks . com... weird

About Biography page:

I tried to translate to words the formula picture, this is the result:

Continued Fraction ==> Phi ==>Golden Rectangle with Logarithmic Spiral ==> Euler?s (Napier's) constant

This page contains

phi=1.6180

e=2.7182

pi=3.1415

tried to convert these numbers to binary for possible key but nothing there that I can see:D:D

I'm guessing the reason lokivanishes has signed up to all these sites is something to do with a script that spammers use to search for forums. She just so happens to have posted on neowin only because this community is the only one (or the first) to follow this mystery

From the youtube, Loki is 22 years old. The name Gm7 could possibly be a clue.

I guess Flickr and YouTube could be considered in-game.

Gm7 could be a guitar cord, which looks a bit like a square root:

http://www.8notes.com/guitar_chord_chart/Gm7.asp

I guess Flickr and YouTube could be considered in-game.

Gm7 could be a guitar cord, which looks a bit like a square root:

http://www.8notes.com/guitar_chord_chart/Gm7.asp

nice work! yeah, with the dots connected it does look very much like a square root

Interesting... phi+pi is about equal to the square root of 22 (about 4.7)

Does anyone else see the significance of this, or am I just overthinking :p

pi and phi were both mentioned on the /biography page. the square root symbol (if Gm7 is really that) and 22 (age) were both on the youtube site

Edit: it is a bit off. using 4 decimals: 4.6904 vs. 4.7595

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • OpenAI is rolling out a major upgrade to ChatGPT memory by Pradeep Viswanathan OpenAI is rolling out a major upgrade to ChatGPT's memory, making the system more capable, current, and scalable across long-term use. Memory allows ChatGPT to remember useful details about users, including their preferences, projects, and constraints. Instead of starting every conversation from scratch, ChatGPT can use this context to provide more relevant responses in future chats. OpenAI first launched saved memories in February 2024. That feature allowed users to explicitly ask ChatGPT to save information into its memory, such as travel plans or writing preferences. However, this system had limits because it depended heavily on users giving clear instructions to remember something. Additionally, saved memories could become stale over time. In April 2025, OpenAI expanded memory by allowing ChatGPT to reference past chat context outside the saved memories list. This was powered by a background process called “dreaming,” which automatically curates memories from chat history. This made ChatGPT better at learning from natural conversation without requiring users to manually save every detail. Today, OpenAI announced a more capable and compute-efficient memory architecture built on top of dreaming. This new system improves ChatGPT’s ability to carry forward useful context, follow user preferences, and remain accurate as time passes. According to OpenAI’s internal evaluations, the new system improves factual recall from 67.9% in 2025 to 82.8% in 2026. Preference adherence improves from 55.3% to 71.3%, while accuracy over time improves from 52.2% to 75.1%. The best part of this new system is a new memory summary page where users can review ChatGPT's memories. Users can even update details, correct information, or give instructions on what topics ChatGPT should bring up and when. This new, improved memory system is available to ChatGPT Plus and Pro users in the US starting today. It will roll out to more countries, as well as Free and Go users, in the coming weeks.
    • I work for a video production company in Australia. The camera operators shoot footage and then pass the SD card over to the editors. Much easier than handing over the entire camera. Plus, on a busy day you can hand off the SD card and then pop another in for the next shoot. Or, you might have used multiple SD cards because you need the extra space for a long shoot. I also use USB cables and wifi for transferring footage, but in many cases an SD card reader is the easiest method.
    • Microsoft Edge 149.0.4022.52 by Razvan Serea Microsoft Edge is a super fast and secure web browser from Microsoft. It works on almost any device, including PCs, iPhones and Androids. It keeps you safe online, protects your privacy, and lets you browse the web quickly. You can even use it on all your devices and keep your browsing history and favorites synced up. Built on the same technology as Chrome, Microsoft Edge has additional built-in features like Startup boost and Sleeping tabs, which boost your browsing experience with world class performance and speed that are optimized to work best with Windows. Microsoft Edge security and privacy features such as Microsoft Defender SmartScreen, Password Monitor, InPrivate search, and Kids Mode help keep you and your loved ones protected and secure online. Microsoft Edge has features to keep both you and your family protected. Enable content filters and access activity reports with your Microsoft Family Safety account and experience a kid-friendly web with Kids Mode. The new Microsoft Edge is now compatible with your favorite extensions, so it’s easy to personalize your browsing experience. Microsoft Edge 149.0.4022.52 changelog: Migration to improved V2 architecture for Workspaces. Workspaces, introduced in Edge in 2022, allows users to create durable sets of tabs that can be saved and shared with others. In order to improve reliability and performance of this feature, the following changes are being made: Migrating data for saved Workspaces from OneDrive/SharePoint to Edge Sync service Removing the collaboration/share functionality of this feature For organizations who have disabled Sync through policy, the existing v1 Workspace data will still be migrated to the new architecture. New v2 Workspaces created after migration won't sync across devices and will remain local to each device. This update occurs on a progressive rollout beginning in Edge Stable v145 and will continue rolling out in Edge v149. For more information, see Getting started with Microsoft Edge Workspaces. Feature Updates Passkey Sync for Enterprise Users. Microsoft Edge is introducing support for passkey synchronization for enterprise users, enabling secure, passwordless authentication across devices. Passkeys created in Edge can now be synced seamlessly, improving sign-in experience while maintaining strong security standards. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout. Enterprise WebView2 runtime downgrade via DowngradeVersion policy. Administrators can temporarily roll back specific applications to a previous WebView2 Evergreen Runtime version (N-1 or N-2) using the new DowngradeVersion policy in msedgewebview2.admx. The Downgrade Version policy allows enterprises to mitigate critical regressions by specifying per-application exe-to-version mappings. The Edge Updater installs the target version side-by-side, and the WebView2 Loader redirects targeted apps accordingly. Downgrades auto-expire with each new WebView2 release: apps pinned to N-1 remain on the same version (now becoming N-2) and will auto-update in the next release, while apps pinned to N-2 will revert to the current Evergreen version. The policy applies only to enterprise-managed devices (domain-joined or MDM-enrolled). For more information, see Microsoft Edge WebView2 Policy Documentation | Microsoft Learn. Collections retirement. Collections has been removed in this update. Users can no longer access or use the feature. To keep saved content, users can export it, or move all pages to Favorites before updating to Microsoft Edge Stable 149. For more information, see Organize your ideas with Collections in Microsoft Edge - Microsoft Support. Modern, unified, and updated Look and Feel. Microsoft Edge has updated the Look and Feel to give customers a unified experience across all of Microsoft AI surfaces including Copilot and Bing. This changes multiple elements of the UX such as spacing, corners, fonts, default colors, etc. Clarify choices surrounding third-party cookie settings. Language under Settings > Privacy, search, and services > Cookies are clarified to better describe the choices users have in managing third-party cookies. Custom primary password retirement. Users are no longer able to create a new custom primary password in Edge Settings edge://settings/autofill/passwords/settings. Any users who are still using a custom primary password will be automatically migrated to device authentication. Additionally, the PrimaryPasswordSetting policy will no longer support the WithCustomPrimaryPassword option. For more information, see Keep your saved passwords private in Microsoft Edge | Microsoft Support. Unifying Copilot Chat policy controls. The Microsoft365CopilotChatIconEnabled policy is the standard for configuring Copilot Chat. Previously, this behavior was controlled by blocking the Copilot extension, either explicitly or by using the * wildcard via the ExtensionSettings or ExtensionInstallBlockList policies. Extension and sidebar policies no longer affect the appearance or functionality of Copilot Chat. Copilot address bar suggestions were also tied to extension policy settings. Starting in Microsoft Edge version 149, admins can use the CopilotAddressBarSuggestionsEnabled policy to manage this behavior. Intune MAM Protected Downloads. The protected downloads feature for Intune MAM is now available for BYOD (Bring Your Own Device) devices, which aren't managed by a tenant. Policy Updates / New policies CopilotAddressBarSuggestionsEnabled - Enable Copilot address bar suggestions CpuPerformanceTierOverride - Override for the CPU performance tier DataUrlInWebWorkerOpaqueOriginEnabled - Enable opaque origins for data URLs in Web Workers DefaultLocalFontsSetting - Default Local Fonts permission setting ForceForegroundPriorityForUrls - Force foreground priority for specific URLs LocalFontsAllowedForUrls - Allow Local Fonts permission on these sites LocalFontsBlockedForUrls - Block Local Fonts permission on these sites Deprecated policies WalletDonationEnabled - Wallet Donation Enabled (deprecated) EdgeWalletEtreeEnabled - Edge Wallet E-Tree Enabled (deprecated) Additional policy changes ForceForegroundPriorityForUrls - ForceForegroundPriorityForOrigins is renamed to ForceForegroundPriorityForUrls OnSecurityEventEnterpriseConnector - Add macOS platform support ProtectedContentIdentifiersAllowed - Remove macOS platform support Download: Microsoft Edge (64-bit) | 193.0 MB (Freeware) Download: Microsoft Edge (32-bit) | 170.0 MB Download: Microsoft Edge (ARM64) | 188.0 MB View: Microsoft Edge Website | Release History Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • User: "But is it good?" Microsoft: "Well, no. But it is less bad."
    • Media Player Classic - Home Cinema 2.7.2 by Razvan Serea Media Player Classic - Home Cinema (MPC-HC) is a free and open-source video and audio player for Windows. MPC-HC is based on the original Guliverkli project (which is no longer maintained) and contains many additional features and bug fixes. As the continuation of the original Media Player Classic, MPC-HC isn’t flashy but it works with nearly any media format. MPC-HC uses DXVA technology to pass decoding operations to your modern video card, enhancing your viewing experience. And MPC-HC supports both physical and software DVDs with menus, chapter navigation, and subtitles. Overview of features A lot of people seem to be unaware of some of the awesome features that have been added to MPC-HC in the past years. Here is a list of useful options and features that everyone should know about: Dark interface Menu > View > Dark Theme When using dark theme it is also possible to change the height of the seekbar and size of the toolbar buttons. Options > Advanced Video preview on the seekbar Options > Tweaks > Show preview on seek bar Adjust playback speed Menu > Play > Playback rate The buttons in the player that control playback rate take a 2x step by default. This can be customized to smaller values (like 10%): Options > Playback > Speed step Adjusting playback speed works best with the internal audio renderer. This also has automatic pitch correction. Options > Playback > Output > Audio Renderer MPC-HC can remember playback position, so you can resume from that point later Options > Player > History You can quickly seek through a video with Ctrl + Mouse Scrollwheel. You can jump to next/previous file in a folder by pressing PageUp/PageDown. You can perform automatic actions at end of file. For example to go to next file or close player. Options > Playback > After Playback (permanent setting) Menu > Play > After Playback (for current file only) A-B repeat - You can loop a segment of a video. Press [ and ] to set start and stop markers. You can rotate/flip/mirror/stretch/zoom the video Menu > View > Pan&Scan This is also easily done with hotkeys (see below). There are lots of keyboard hotkeys and mouse actions to control the player. They can be customized as well. Options > Player > Keys Tip: there is a search box above the table. You can stream videos directly from Youtube and many other video websites You can stream videos directly from Youtube and many other video websites Put yt-dlp.exe or youtube-dl.exe in the MPC-HC installation folder. Then you can open website URLs in the player: Menu > File > Open File/URL You can even download those videos: Menu > File > Save a copy Tip: to be able to download in best quality with yt-dlp/youtube-dl, it is recommended to also put ffmpeg.exe in the MPC-HC folder. Several YDL configuration options are found here: Options > Advanced This includes an option to specify the location of the .exe in case you don't want to put it in MPC-HC folder. Play HDR video This requires using madVR or MPC Video Renderer. After installation these renderers can be selected here: Options > Playback > Output Ability to search for and download subtitles, either automatically or manually (press D): Options > Subtitles > Misc Besides all these (new) features, there have also been many bugfixes and internal improvements in the player in the past years that give better performance and stability. It also has updated internal codecs. Support was added for CUE sheets, WebVTT subtitles, etc. Media Player Classic - Home Cinema 2.7.2 changelog: Updated LAV Filters to version 0.81-23-g6fadb Updated MPC Video Renderer to version 0.10.2.2540 Updated MediaInfo DLL to version 26.05 Updated MPC Audio Renderer Several crash fixes, bug fixes and small improvements. Download: MPC-HC 2.7.2 (x64) | Standalone | ~20.0 MB (Open Source) Download: MPC-HC 2.7.2 (x86) | Standalone Links: MPC-HC Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      471
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Skyfrog
      80
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!