It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
I would ultimately get three CDs with huge digital "wav file" recordings of the various channels in each section of the operations floor, 30-some hours of material in full, covering six and a half hours of real time. The first disc, which arrived by mail, was decorated with blue sky and fluffy white clouds and was labeled, in the playful Apple Chancery font, "Northeast Air Defense Sector—DAT Audio Files—11 Sep 2001."
Originally posted by drock905
I think I got what hardstyle is doing, If im confused let me know.
If I take
DRM1 DAT2 Channel 4 ID Op.wav
DRM1 DAT2 Channel 5 ID TK.wav
Open these 2 files to two unique tracks in a DAW, sync thier start points to both be at 00:00:00:00.
I guess at some point in the recording, which is supposed to be unedited and linear, the two tracks will drift out of sync with each other. Now if these two tapes were unedited there would be no loss of sync.
Hardstlye is saying that the loss of sync is the obvious tipoff that these tapes were edited. If that is the case i'd have to agree...........
I am downloading the files now, if i have time tomorrow at work i will load them into my software at the studio i work at and see what i get.
Am i missing anything?
If anybody was wondering what an ADAT is
en.wikipedia.org...
I’ve been seeking the assistance of a number of highly qualified engineering professionals, including Ph.D. heads of Electrical Engineering departments with the time anomaly waveform. I have even requested assistance from the 84 RADES staff in identifying the time anomaly in the NEADS data, although to-date they have failed to respond. So far, I have had limited feedback with a lot of head-scratching. One EE department head offered the following, which simply reiterates what I’ve already deduced.
....
Details are too sketchy to do much with this … could be a number of things related to processor architecture including multiprocessor issues …
Initial comparisons of the radar data from the USAF and the FAA showed that an offset in time was present. The 84th RADES found that the clock for the North East Air Defense Sector (NEADS) lagged the clocks for the other sectors by 25.3 seconds… The other sectors were all in agreement with the Global Positioning Satellite (GPS) time. Therefore, 25.3 seconds must be added to the radar data from the 84th RADES.[1]
...
The source of the time anomaly is beyond the scope of this study; however it is known that multiple “war games”[4] were being conducted on 9/11 which NEADS was a participant in at least one of these. It seems reasonable that as part of those exercises the radar data was being processed through some synthesizer which permitted the injection of “false” exercise targets. The description above of how one such synthesizer operates, may explain the multiple waveforms (separate clock generators).
As each new simulation is loaded there is a “wait time” involved which may explain the obvious step changes observed.
All of the official times reported by the NTSB were adjusted to fit the NEADS data. The correction applied was according to them 25.3 seconds. This is a problem since the time differed by 0.094 seconds every 27 minutes! It is inconceivable to me that the NTSB was unaware of this time anomaly, yet they reported to the 911 Commission ONLY the average time difference without elaborating that the root cause of the time difference was suspect even when pressed by the Commission staff to elaborate[7]. To conform ALL of the time estimates to time data that exhibited such extreme special cause phenomenon is grossly incompetent at the very least.