DjProducerTool

DJProducerTools – Complete Wiki

Extensive documentation for using the library cleaning and organization toolkit for DJs and Producers on macOS.

1) What It Is and Who It’s For

2) Main Files

3) Quick Installation

cat <<'EOF' > install_djpt.sh
#!/usr/bin/env bash
set -e
for f in DJProducerTools_MultiScript_ES.sh DJProducerTools_MultiScript_EN.sh; do
  url="https://raw.githubusercontent.com/Astro1Deep/DjProducerTool/main/$f"
  curl -fsSL "$url" -o "$f"
  chmod +x "$f"
done
echo "Done. Run ./DJProducerTools_MultiScript_ES.sh or ./DJProducerTools_MultiScript_EN.sh"
EOF
chmod +x install_djpt.sh
./install_djpt.sh

4) Requirements

5) Basic Usage

./DJProducerTools_MultiScript_ES.sh   # Spanish version
./DJProducerTools_MultiScript_EN.sh   # English version

6) Disk Structure

7) Security and Modes

8) Menus and Advantages (Grouped View)

9) Automated Chains (Summary)

1) Secure backup + snapshot (8 -> 27) 2) Exact dedup + quarantine (10 -> 11) 3) Metadata + names cleanup (39 -> 34) 4) Media health: rescan + playlists + relink (18 -> 14 -> 15) 5) Show prep: backup/snapshot/dup/playlist (8 -> 27 -> 10 -> 11 -> 14 -> 8) 6) Integrity + corrupt files (13 -> 18) 7) Efficiency plan (42 -> 44 -> 43) 8) Basic ML organization (45 -> 46) 9) Predictive backup (49 -> 8 -> 27) 10) Cross-platform sync (50 -> 39 -> 8 -> 8) 11) Quick diagnosis (1 -> 3 -> 4 -> 5) 12) Serato health (7 -> 59) 13) Hash + mirror check (9 -> 68) 14) Audio prep (31 -> 69 -> 70) 15) Integrity audit (6 -> 9 -> 27 -> 68) 16) Cleanup + safe backup (39 -> 34 -> 10 -> 11 -> 8 -> 27) 17) Library sync prep (18 -> 14 -> 50 -> 8 -> 27) 18) Visuals health (V2 -> V6 -> V8 -> V9 -> 8) 19) Advanced audio organization (31 -> 30 -> 35 -> 45 -> 46) 20) Reinforced Serato security (7 -> 8 -> 59 -> 12 -> 49) 21) Multi-disk dedup + mirror (9 -> 10 -> 46 -> 11 -> 68)

10) Outputs and Location

11) ML/TensorFlow Notes

12) Best Practices

13) Visual Resources

14) Professional Management Strategies

The 3-2-1 Backup Rule for DJs

To avoid disasters before a gig, follow this rule using the script’s tools:

  1. 3 Copies: Your library on the laptop, a copy on an external drive (Time Machine or clone), and a “cold” copy elsewhere.
  2. 2 Media: Use an SSD for live performance and an HDD for cold storage.
  3. 1 Off-site: A copy outside your studio (cloud or a friend’s house). Script Usage: Run the A9 (Predictive Backup) chain weekly.

Audio Quality Management

Metadata Cleanup for CDJs

Older CDJs can fail with strange characters or very large artworks.

15) Artist Profiles and Distribution (Option 72)

16) License

17) Support

18) Testing and Development

The project includes a basic unit test suite to verify the functionality of the main utility functions.

Running the Tests

  1. Open a terminal and navigate to your project’s root directory. Use quotes if the path contains spaces:

     cd "/Users/ivan/Desktop/0 SERATO BIBLIOTECA/DJProducerTools_Project "

  2. Give execution permissions to the test script (you only need to do this once):

     chmod +x tests/test_runner.sh

  3. Run the tests:

     bash tests/test_runner.sh

The runner will automatically discover and run all test functions, showing a summary of passed and failed tests.

How It Works

Adding New Tests

To add a new test, open tests/test_runner.sh and create a new function whose name starts with test_. The runner will detect it automatically.

Development Scripts

These scripts automate the development lifecycle, from testing to final product creation and documentation updates.

This site is open source. Improve this page.