Reaktor Main Page | Tutorials | Modules | Synthesis |
NTF stands for "Native Table File", which contains values in a format acceptable by Event Table
NTF file structure
editThe structure of NTF file was not officially published, so below information may be wrong.
Data Type | Start Hex | Start Byte | End Byte | Len | Description |
Int-32 | 0 | 0 | 3 | 4 | Always zero? |
Int-32 | 4 | 4 | 7 | 4 | Always zero? |
Int-32 | 8 | 8 | 11 | 4 | Always One? |
Int-32 | C | 12 | 15 | 4 | X-Size - Int32 |
Int-32 | 10 | 16 | 19 | 4 | Y-Size - Int32 |
Float-32 | 14 | 20 | 23 | 4 | Value Min |
Float-32 | 18 | 24 | 27 | 4 | Value Max |
Float-32 | 1C | 28 | 31 | 4 | Step Size |
Float-32 | 20 | 32 | 35 | 4 | Default |
Int-32 | 24 | 36 | 39 | 4 | Display Units, values = 0,1,2 |
Int-32 | 28 | 40 | 43 | 4 | Always 0? |
Int-32 | 2C | 44 | 47 | 4 | Always 0? |
Int-32 | 30 | 48 | 51 | 4 | Always 0? |
Int-32 | 34 | 52 | 55 | 4 | X-Units, values = 0,1,2,3 |
Float-32 | 38 | 56 | 59 | 4 | Samples / Sec - in millisecond mode??? - Tied to pos 0x40 |
Float-32 | 3C | 60 | 63 | 4 | BPM |
Float-32 | 40 | 64 | 67 | 4 | Samples / Tick - in tempo ticks mode??? - Tied to pos 0x38 |
Int-32 | 44 | 68 | 71 | 4 | Ticks / Beat |
Int-32 | 48 | 72 | 75 | 4 | Always 4? |
Int-32 | 4C | 76 | 79 | 4 | Always 0? |
Float-32 | 50 | 80 | 83 | 4 | Always = 1? |
Float-32 | 54 | 84 | 87 | 4 | Always = 1? |
Int-32 | 58 | 88 | 91 | 4 | Y-Units values = 0,1 |
Float-32 | 5C | 92 | 95 | 4 | Always = 48? (default samples/sec?) |
Float-32 | 60 | 96 | 99 | 4 | Always = 120? (default BPM?) |
Float-32 | 64 | 100 | 103 | 4 | Always = 1? (default samples/tick?) |
Int-32 | 68 | 104 | 107 | 4 | Always 24 (0x18)? (default ticks/beat?) |
Int-32 | 6C | 108 | 111 | 4 | Always 4? |
Int-32 | 70 | 112 | 115 | 4 | Always 0? |
Float-32 | 74 | 116 | 119 | 4 | Always = 1? |
Float-32 | 78 | 120 | 123 | 4 | Always = 1? |
float-32 | 7C | 124 | 127 | 4 | Start of table data stored as Float-32's. Data is saved by row. So...First row = (y0, x0), (y0,x1), (y0,x2)...(y1, x0), (y1,x1), (y1,x2)…etc |