← Back to Dashboard

Q&A - Frequently Asked Questions

Answers to the most common questions about ModusPractica.

How do I use the practice page? What is the difference between "Failed Attempts" and "Total Failures"?

The practice page is where you log the results of your session. This data is crucial for the algorithm to calculate your progress and schedule your next review. Here’s a breakdown of the key concepts:

Understanding "Failed Attempts"

When you first learn a section, you are exploring. It's normal to make mistakes. The Failed Attempts counter is for logging the errors you make within the current practice streak.

The goal is to play your chunk (e.g., one measure, or even just a few notes) slowly and consciously without mistakes. If you play it correctly on the first try, leave the counter at 0. If you make a mistake, increment it to 1 and try again. It is crucial to minimize mistakes, as every error is stored in your brain.

"Correct Repetitions" vs. "Total Failures"

Each time you make a mistake and have to restart your streak of correct repetitions, you should click the reset button (the circular arrow). This action does two things:

  • It increments the Total Failures counter by one. This is a high-level metric for the entire session.
  • It increments the Repetition Streak Reset counter, showing how many times you broke a successful streak.

After a reset, you enter 1 under Correct Repetitions once you play it correctly. If you play it twice correctly in a row, you increase this to 2, and so on.

Important Note on Initial Practice

A new section will automatically be scheduled for three consecutive days, regardless of your performance. This initial phase ensures a solid foundation in your memory. After these three sessions (on different days), the intelligent scheduler will take over completely.

Experience Feedback & Progress Graph

From the second session onwards, a progress graph will appear. This graph shows a moving average of your last 7 sessions to visualize your performance trend and smooth out daily fluctuations.

What does the `(avg X)` value next to my score mean?

The (avg X) value represents the average number of attempts required to achieve a single correct repetition. It's a measure of your practice efficiency: a lower number is better.

The formula is: (Failed Attempts + Correct Repetitions) / Correct Repetitions.

Example 1: Perfect Score

You play 3 correct repetitions in a row.

  • Failed Attempts: 0, Correct Repetitions: 3
  • Calculation: (0 + 3) / 3 = 1
  • Result: (avg 1). On average, it takes you exactly one attempt to play it correctly. This is the ideal outcome.

Example 2: One Wrong Start

You make 1 mistake, then play 2 correct repetitions.

  • Failed Attempts: 1, Correct Repetitions: 2
  • Calculation: (1 + 2) / 2 = 1.5
  • Result: (avg 2) (rounded up). You now need more than one attempt per correct repetition.

Example 3: Difficult Start

You make 4 mistakes, then play it correctly once.

  • Failed Attempts: 4, Correct Repetitions: 1
  • Calculation: (4 + 1) / 1 = 5
  • Result: (avg 5).

In short, avg is not an average of your score, but an average of the effort (in attempts) needed for each success. A higher value indicates you are struggling more with the section.

How should I structure my chunks to build a complete piece?

One of the most common questions from new users is: "How should I break down a piece and structure my practice?" ModusPractica uses a three-tier chunking system that mirrors how the brain naturally builds complex skills—from small components to integrated wholes.

⏱️ Important Note on Timelines

The examples below use specific day counts for illustration purposes. In reality, your progression speed depends on many factors: piece difficulty, your experience level, available practice time, and how quickly you master each chunk. Some users may progress faster, others may take longer—both are perfectly normal. The key principle remains the same: build from small chunks to larger structures, regardless of your personal timeline.

The Three-Tier System

  • Tier 1: Micro-Chunks — Small building blocks (2-4 measures). Focus: technical accuracy and initial memorization.
  • Tier 2: Integration Chunks — Combined sections (4-8 measures). Focus: smooth transitions and musical flow between components.
  • Tier 3: Maintenance Chunks — Complete pages or passages (8-16 measures). Focus: long-term retention and performance readiness.

Example Workflow: 8-Measure Passage

Phase 1: Build Micro-Chunks (Typically 1-2 weeks)

Start by creating four separate chunks:

  • Chunk A: Measures 1-2
  • Chunk B: Measures 3-4
  • Chunk C: Measures 5-6
  • Chunk D: Measures 7-8

Practice each chunk through its foundation phase (Stage 0→1→2→3). Once a chunk reaches Stage 3, it enters the adaptive Ebbinghaus phase with expanding intervals. Goal: All micro-chunks at Stage 4+ (solid memorization and technical command).

Phase 2: Create Integration Chunks (Typically 1-2 weeks after Phase 1)

When both components of a pair reach Stage 4+, create integration chunks:

  • Integration 1: Measures 1-4 (when Chunks A and B are both Stage 4+)
  • Integration 2: Measures 5-8 (when Chunks C and D are both Stage 4+)

These chunks focus on practicing smooth transitions and musical flow. Because the individual components are already well-learned, you'll likely rate these sessions as "Good" or "Excellent" from the start, causing the algorithm to accelerate progression. Goal: Integration chunks reach Stage 3-4 (secure connections between sections).

Phase 3: Build Maintenance Chunk (Ongoing)

Once both integration chunks are secure (Stage 3-4+), create your maintenance chunk:

  • Full Passage: Measures 1-8 (complete section for long-term retention)

This chunk represents the finished product and will be your primary maintenance tool going forward. As it progresses through stages, intervals will extend to weeks or even months, providing efficient long-term retention with minimal practice overhead.

Phase 4: Archive Earlier Chunks (Optional)

Once your maintenance chunk (1-8) reaches Stage 3+, you may optionally archive the micro-chunks and integration chunks. Archiving stops their scheduling but preserves all data, keeping your dashboard focused on active maintenance tasks.

Key Principles

  • Build foundations first — Don't rush to create integration chunks until components are solid (Stage 4+).
  • Avoid redundancy — Don't create overlapping chunks at the same tier. Use the three-tier progression instead.
  • Trust the dashboard — Let the algorithm tell you what to practice. Your job is to provide honest performance ratings.
  • Archive strategically — Once maintenance chunks are active, archive earlier chunks to keep your dashboard clean.
  • Scale the system — This approach works for 8 measures or 64 measures. Simply add more micro-chunks and integration layers as needed.

💡 Real-World Example

For a 16-measure Chopin Nocturne first page, you might create 8 micro-chunks (2 measures each), then 4 integration chunks (4 measures each), then 2 half-page chunks (8 measures each), and finally 1 full-page chunk (16 measures). After 6-8 weeks, you'd have one maintenance chunk scheduled every 3-4 weeks, efficiently preserving the entire page in long-term memory.