65 DIRT BIKES

The NAGRA IV-S can be delivered in three different versions, all of which are available in either NAB or CCIR equalization. These versions are: NQS-LSP (Non Pilot), NQS-L (Pilot), and NQS-TC (Time Code). Each version has three speeds: 38 cm/s (15 ips), 19 cm/s (7 1/2 ips), and 9.5 cm/s ( 3 3/4 ips) with the following standards: NAB, CCIR, and the NAGRAMASTER (at 15 ips only).
The NAGRA IV-S is a stereo recorder with 2 mm audio tracks (2.75 mm tracks on the NQS-LSP non-pilot machines) and a central track for pilot or time code uses, depending on the machine type.
The two audio channels may be used with either the internal microphone pre-amplifiers (switchable between Dynamic, T power, and Phantom power), or with a current line input via the QCSE cable. The two potentiometers on the front panel may be mechanically "GANGED" together for easier control by moving the small white lever located on the green control.
The NAGRA IV-S also contains a switchable limiter, a built-in loudspeaker, provision for connection to an external noise reduction system, and an internal reference generator for line up, and calibration purposes.
The machine can be fitted with either the NAGRASYNC pilot option or the SMPTE/EBU 80 bit time code option. The machine may also be powered from either an external supply (ATN-3) or internal batteries. The IV-S may also be used with the QGB 10" reel adapter to allow the use of larger reels for longer recording and playback.

* Tape transport speeds 38 cm/s (15 ips), 19 cm/s (7 1/2 ips), and 9.5 cm/s (3 3/4 ips) accuracy are governed by a closed loop servo system (PLL quartz Xtal sync reference).

** Film sync sound resolving (speed variations) are governed by the Pilot track (in NQS-L), or TC track in (NQS-TC model) via appropriate accessory units. TC tracks act as Pilot tracks.

NQS-TC SPECIFICATIONS

TIME CODE
Time code recording level
700 nWb/m peak-to-peak +/-3 dB (250 nWb/m equivalent sine wave rms)
Rise and fall time
65 µs +/-10 µs
Time code readback
.5 to 6 times the nominal speed
Coincidence error between time code and audio track
Max. 1 time code bit (less then 500 µs in EBU standard) (tape travel time compensation made by micro proc)
Time code input
Unbalanced
Input level
Min. 250 mV peak-to-peak Max. 24 V peak-to-peak
Input impedance
> 100k ohms
Time code output
CMOS logical level + 5V
Time code
+/- 1 ppm from -10 to +40?
generator stability
C corresponding to a variation of +/- 1 frame in 9 hours of operation at 30fps or in 11 hours at 25fps (+/- 2 ppm from -10 to +60? C)
TAPE TRANSPORT
Switchable tape speeds
15 ips = 38.1 cm/s 7.5 ips = 19.05 cm/s 3.75 ips = 9.525 cm/s
Wow and flutter weighted peak-to-peak value:
- to DIN 45507 standard at 15 ips
+/- .05% (.07)
- to NAB standrad at 15 ips
0.28%
AUDIO RECORD AND PLAYBACK
Nominal recording level
0 dB = 510 nWb/m
Max peak recording level
+ 4 dB
Erase efficiency at max peak level
83 dB (80 dB)
Frequency response, recorded at -20 dB 15 ips from 30 Hz to 20 kHz
+/- 1 dB (+/- 2 dB)
Signal-to-noise ratio, record and play at max peak level ASA A weighted:
- 15 ips NAGRAMASTER
NAB 74.5 dB (72 dB)
- 15 ips STD
NAB 70 dB (68 dB)
Cross talk between audio channels
0 dB modulometer 1 kHz 70 dB (65 dB) 0 dB modulometer 10 kHz 60 dB (50 dB)
Residual time code signal on audio tracks (2 mm) referenced to max peak level
Below -88 dB
POWER SUPPLY
Power supply voltage necessary DC positive to chassis
10.5 to 30 V (performance can be slightly reduced between 10.5 and 12V)
Current consumption on "RECORD"
276 mA
Time code circuit only
26 mA full operation 2 mA standby, "STOP" (560 µA STOP without continuous memory and time code generator stopped)
GENERAL
Overall dimensions
13.2 x 9.6 x 4.5"
Weight (with ordinary batteries and 5 inch reel/tape)
15 lbs.
Tape width
1/4"
Audio track width
2 mm
Central time code track width
0.35 mm

Day 198 / 366
Wed

Another late night. Just tweaking my query string parser. This really is quite high level coding compared to what I normally do. OMG I'm turning into a web developer.

I guess it gives me a chance to flex my C++ muscles.

Lol, I've just notice that I spelled QueryTokens wrong. People can usually recognise my code by its inconsistent and generally wrong spelling of things. But at least it builds.