Description
Zero-based beat offset from the start of the pickup; measure 1 is the first full measure.
A production plan combines stage geometry, cue times, movement distances, material dimensions, and explicit scheduling or accounting rules. Signed margins reveal surplus or deficit under the chosen model. Physical clearances, execution variability, and governing requirements can require checks beyond one arithmetic term.
Zero-based beat offset from the start of the pickup; measure 1 is the first full measure.
When to use this tool
Use Music Pickup Measure Count Offset when you need this specific stage, cue, material, timing, count, or fee term under supplied production assumptions.
How to use the tool and how it works
- Enter fullMeasureBeats, pickupBeats, measureNumber, beatInMeasure. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read absoluteBeat. Use the output convention below.
For positive fullMeasureBeats, pickupBeats in [0,fullMeasureBeats), beatInMeasure in the same range, and integer measureNumber>=1 return absoluteBeat=pickupBeats+(measureNumber-1)*fullMeasureBeats+beatInMeasure.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| fullMeasureBeats | Full Measure Beats | Required. Finite number; strictly above 0. |
| pickupBeats | Pickup Beats | Required. Finite number; minimum 0. |
| measureNumber | One-based complete-measure count after the pickup. | Required. Safe integer; minimum 1. |
| beatInMeasure | Zero-based beat position inside a full measure. | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| absoluteBeat | Absolute Beat | Required. Finite number. |
{
"input": {
"fullMeasureBeats": 4,
"pickupBeats": 1,
"measureNumber": 2,
"beatInMeasure": 0
},
"output": {
"absoluteBeat": 5
}
} Limitations and assumptions
- MeasureNumber counts complete measures after the pickup and beatInMeasure is zero-based. Meter changes, multiple pickups, score notation, and tempo conversion are not handled.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.
Alternative or Complementary methods
Use a complete production schedule or equipment/layout assessment when one margin is insufficient. Check units, timing conventions, tolerances, and physical constraints before combining terms.
References
Similar or alternative tools
- Orchestra Pickup Bar Index Shift
Shift a supplied zero-based bar index under an explicit pickup-bar numbering convention.
- Dance Tempo Count Phrase Duration
One count equals one tempo beat; subdivisions must be converted by the caller.