Help us calibrate the DawSync engine
We need real-world data about how producers organize their projects. Run a simple script, upload the results, and help us build a smarter detection engine.
What is this?
DawSync needs to understand how real producers name and organize their DAW projects. This data helps us calibrate our smart detection engine so it can automatically identify your projects — even when they're named 'Track 1 v3 FINAL copy.als'.
Is it safe?
The script is 100% transparent and open source. It doesn't send data anywhere — it only saves a text file on your Desktop that you decide whether to upload or not.
If you have doubts, copy the script and paste it into ChatGPT or Claude asking: "Is this script safe? What exactly does it do?" — they'll confirm it only searches for files and generates a local report.
What the script does:
- ✓ Searches for .als, .logicx, .flp, .rpp, .ptx, .cpr, .song, .bwproject files
- ✓ Scans Music, Documents, Desktop, Downloads + external drives
- ✓ Collects metadata: file path, creation date, modification date, size, parent folder
- ✓ Counts naming patterns (v1, v2, final, etc.) and files per folder
- ✓ Saves a .txt report to your Desktop
What it does NOT do:
- ✗ Does NOT open or read the content of your projects
- ✗ Does NOT send anything to the internet automatically
- ✗ Does NOT access photos, iCloud or other apps
- ✗ Does NOT modify any files
Download the script
Double-click to run. The script will generate a text file on your Desktop.
All DAWs
Open Terminal, paste this command and press Enter:
No downloads, no permissions, no Gatekeeper warnings — just works.
How to use
On Mac:
- 1 Press Cmd + Space to open Spotlight
- 2 Type 'Terminal' and press Enter
- 3 Copy the green command above (click 'Copy')
- 4 Paste it in Terminal (Cmd + V) and press Enter
- 5 Wait 1-3 minutes until it says 'COMPLETE!'
- 6 Find 'daw_projects_report.txt' on your Desktop
On Windows:
- 1 Download the .bat file
- 2 Double-click to run it
- 3 Wait 1-3 minutes
- 4 Find the report on your Desktop
Upload the file using the button below
What we collect (and what we don't)
What we collect
- + File names and folder paths of DAW projects
- + File size in bytes for each project
- + Last modification date and creation date of each file
- + Parent folder name and number of files in the same folder
- + Whether the project is inside a backup folder
- + Drive or volume where the project is stored
- + Naming pattern statistics (version suffixes, dates, etc.)
- + Your operating system version and number of projects per DAW
What we do NOT collect
- - Audio content — we never open or read your project files
- - Personal information — no names, emails, or accounts
- - Files outside your user folder
- - Anything sent automatically — you review and upload manually
Why we collect this
- File sizes help us plan storage features and detect project complexity
- Dates help us understand session patterns and detect DAW version upgrades
- Folder structure helps us design smarter workspace detection
- Backup folder data tells us how producers already manage versions
- Drive info helps us support external drives and multi-disk setups