Hello, I’m experiencing a consistent and reproducible crash with Traktor Pro 4 on macOS Ventura, and after two full days of troubleshooting, I’m out of ideas and need guidance from NI or users with similar setups. System * MacBook Pro (Intel) * macOS Ventura 13.7.8 * Audio interface: Native Instruments Audio 6 * Controller: X1 MK3 (not always connected) * Native Access: latest version What works * Traktor Pro 3.11.1 opens and works perfectly on the same machine * Same music library size (~30–35k tracks) * Tag writing ENABLED in Traktor 3 * Same Audio 6, same OS, same user account What does NOT work * Traktor Pro 4.4.1 crashes immediately on startup * Crash happens exactly when Traktor starts loading collection.nml * This happens:* After clean install * After deleting all previous Traktor folders * After choosing YES to “load from previous installation” * After choosing NO (empty / fresh start) * Result is always the same: instant crash What I already tried (in detail) * Full uninstall of Traktor 4 (Applications + user folders) * Removed:* ~/Documents/Native Instruments/Traktor 4 * All old Traktor 4.x folders (renamed / deleted) * Fresh reinstall via Native Access twice * Tried:* Loading previous installation → crash * Starting from empty → crash * Renamed / removed:* collection.nml * Traktor Settings.tsi * Disabled potential tag writing by renaming settings files * Tested without controllers connected * Tested with only Audio 6 connected * Tested after macOS reboot * Verified disk permissions * Verified Traktor 3 still works with the same data Crash log findings I located a crash log that repeatedly shows filesystem write operations, including: * AudioFileTags::writeTags * MediaItemServices::writeTags * filesystem::copy_file * Disk write activity over a long duration However: * Traktor 3 uses tag writing too and does NOT crash * Traktor 4 crashes even when starting from an empty setup This makes me believe: ➡️ The issue is not the collection size ➡️ The issue is not tag writing alone ➡️ The issue may be: * A Ventura-specific filesystem / permissions issue * A Traktor 4-specific bug during collection initialization * A corrupted internal state Traktor 4 creates even on first launch Why this matters I rely on: * New audio engine improvements * X1 MK3 mappings * Traktor 4 layouts Right now, Traktor 4 is completely unusable, while Traktor 3 is stable. My questions * Is this a known issue with Traktor Pro 4 + macOS Ventura (Intel)? * Are there known conflicts during collection initialization in Traktor 4? * Is there a hidden cache / database / plist location that must be removed? * Are there debug flags or safe-mode launches for Traktor 4? * Where exactly should I look for Traktor 4 crash logs if they don’t appear under DiagnosticReports? Any guidance from NI staff or users with similar hardware + Ventura would be hugely appreciated. Thank you in advance!

Traktor Pro 4 crashes immediately on startup on macOS Ventura when loading Collection.nml (clean rei

Hello,

I’m experiencing a consistent and reproducible crash with Traktor Pro 4 on macOS Ventura, and after two full days of troubleshooting, I’m out of ideas and need guidance from NI or users with similar setups.

System

MacBook Pro (Intel)
macOS Ventura 13.7.8
Audio interface: Native Instruments Audio 6
Controller: X1 MK3 (not always connected)
Native Access: latest version

What works

Traktor Pro 3.11.1 opens and works perfectly on the same machine
Same music library size (~30–35k tracks)
Tag writing ENABLED in Traktor 3
Same Audio 6, same OS, same user account

What does NOT work

Traktor Pro 4.4.1 crashes immediately on startup
Crash happens exactly when Traktor starts loading collection.nml
This happens:
- After clean install
- After deleting all previous Traktor folders
- After choosing YES to “load from previous installation”
- After choosing NO (empty / fresh start)
Result is always the same: instant crash

What I already tried (in detail)

Full uninstall of Traktor 4 (Applications + user folders)
Removed:
- ~/Documents/Native Instruments/Traktor 4
- All old Traktor 4.x folders (renamed / deleted)
Fresh reinstall via Native Access twice
Tried:
- Loading previous installation → crash
- Starting from empty → crash
Renamed / removed:
- collection.nml
- Traktor Settings.tsi
Disabled potential tag writing by renaming settings files
Tested without controllers connected
Tested with only Audio 6 connected
Tested after macOS reboot
Verified disk permissions

Verified Traktor 3 still works with the same data

Crash log findings

I located a crash log that repeatedly shows filesystem write operations, including:

AudioFileTags::writeTags
MediaItemServices::writeTags
filesystem::copy_file
Disk write activity over a long duration

However:

Traktor 3 uses tag writing too and does NOT crash
Traktor 4 crashes even when starting from an empty setup

This makes me believe:
➡️ The issue is not the collection size
➡️ The issue is not tag writing alone
➡️ The issue may be:

A Ventura-specific filesystem / permissions issue
A Traktor 4-specific bug during collection initialization
A corrupted internal state Traktor 4 creates even on first launch

Why this matters

I rely on:

New audio engine improvements
X1 MK3 mappings
Traktor 4 layouts

Right now, Traktor 4 is completely unusable, while Traktor 3 is stable.

My questions

Is this a known issue with Traktor Pro 4 + macOS Ventura (Intel)?
Are there known conflicts during collection initialization in Traktor 4?
Is there a hidden cache / database / plist location that must be removed?
Are there debug flags or safe-mode launches for Traktor 4?
Where exactly should I look for Traktor 4 crash logs if they don’t appear under DiagnosticReports?

Any guidance from NI staff or users with similar hardware + Ventura would be hugely appreciated.

Thank you in advance!

Find more posts tagged with

Accepted answers

pARty_bOy

did you log in on beatsource or beatport? Try with Wifi Off

check this post

https://community.native-instruments.com/discussion/48948/beatsource-and-or-beatport-log-in-crash-macos-monterey#latest

All comments

pARty_bOy

did you log in on beatsource or beatport? Try with Wifi Off

check this post

https://community.native-instruments.com/discussion/48948/beatsource-and-or-beatport-log-in-crash-macos-monterey#latest

Coolfever

@pARty_bOy>Confirmed!!!! Traktor Pro 4 opens consistently with Wi-Fi OFF.
When Wi-Fi is ON, the app attempts streaming login (Beatport/Beatsource) during startup and crashes.
This reproduces the issue described in NI forum thread 48948.
Traktor Pro 3 does not show this behavior on the same system.

I will check it again tonight how stable is at startup. Thank you!!!!

Coolfever

@pARty_bOy>Confirmed! Traktor Pro 4 opens consistently with Wi-Fi OFF.
When Wi-Fi is ON, the app attempts streaming login (Beatport/Beatsource) during startup and crashes.
This reproduces the issue described in NI forum thread 48948.
Traktor Pro 3 does not show this behavior on the same system.

I will check it again tonight how stable is at startup. Thank you!!!!

Sûlherokhh

https://community.native-instruments.com/discussion/comment/253734#Comment_253734

Curious to know how it went.

Friedemann_NI

Hi!
Thank you for narrowing this down to the Wifi/streaming!
We are currently looking into this and have a hard time to reproduce this in-house, we would appreciate if you could let us know, if using an older version of Traktor Pro 4 (between 4.0.0 and 4.3.0) also shows these crashes or if this got introduced with 4.4.0 and later?

Dawsy

I have exactly the same problem on Mac OS Ventura 13.1 Traktor 4.4.1 is now unusable.

Quick links

Unanswered questions