New countdown, new release? [Aphex Twin Warp Store]

The countdown changed.

It's a lot slower now, lol!

The final xx.yyy part seems to complete a cycle from 05.999 to 00.000 in about 400 seconds. Which means the (presumed) dd.hh.mm countdown only moves at a rate of 0.15 of regular time, or, inversely, time is 6.6666 times as slow. Evil numbers!

If this reading is correct, the countdown point lies around October 1st or 2nd.

Or, rather, August 9-ish. It's too early in the morning for calculation.

So nothing special next thursday ? Damn.

We could have predicted something like this would happen, right? It couldn't have been so straightforward, not coming from him.

This countdown is super-accurate yet unreliable.

It seems we have been trolled

phuking apples wins! 

Haha

LooooooooooooL

lol

I guess someone at Warp HQ didn't make his/her deadline.

  On 7/1/2017 at 12:40 PM, Hail Sagan said:

You nailed it

The orbital period of Mars is about twice as much as ours.

I feel deflated. Please someone crunch the maths so i stop staring at this timer now. Maybe this is why there was little fanfare associated with this timer, lack of confidence in the timetable?

  On 7/1/2017 at 2:58 PM, Hijexx said:

The orbital period of Mars is about twice as much as ours.

That would be beyond amazing

"Look Richard, the crowd is growing impatient. We need to give them something of a hint as to when you're gonna drop something. And no funny business this time. For once, could you please, pretty pretty please, be a little conventional in your approach? You stand to lose a lot of fans by pulling their leg all of the time."

"Okay, let's see. What do you think of a timer on my web page? I have a pretty good idea of when I can come out with what I have. That conventional enough for you?"

"Sure, that's great! People know what to expect from a countdown. Good thinking, Rich ol' buddy."

function a() {
    var distance = countDownDate - now;
    var result = distance / (1000 * 60 * 60 * 24);
    console.debug('a: ' + result);

    return result;
}

function f() {
    var result = (6 - a()) * 0.85;    
    console.debug('f: ' + result);
    return result;
}

function x() {
    var result = -1 * Math.pow(Math.max(0,2*(-1.7 - a())),2)/200;
    console.debug('x: ' + result);
    return result;
}

var countDownDate = new Date("Jul 6, 2017 17:00:00").getTime();

Date is the same, but there seems to be some fuckery added to make the countdown go slower or something, I havent done the math. Seems like a hackjob judging by such descriptive function names as f() and x()

  On 7/1/2017 at 9:21 AM, psn said:

It's a lot slower now, lol!

 

The final xx.yyy part seems to complete a cycle from 05.999 to 00.000 in about 400 seconds. Which means the (presumed) dd.hh.mm countdown only moves at a rate of 0.15 of regular time, or, inversely, time is 6.6666 times as slow. Evil numbers!

 

If this reading is correct, the countdown point lies around October 1st or 2nd.

  On 7/1/2017 at 9:29 AM, psn said:

Or, rather, August 9-ish. It's too early in the morning for calculation.

Jul 20, 16:05, i think

the distance var is now the sum of a(), f() and x().

code:

the old code if anyone's curious:

Seems a bit random at the moment. 

L.O.L...!..........N.O.T.....!..........

I actualy took that day off,to sitt around waiting/drinking nxt to my laptop with my friend. ha ha ha............HA!

dammit RICHARD

Something tells me that when the countdown ends on the 20th the timer will just restart