Skip to content

Use forward slashes in SFZ paths for Linux/macOS compatibility#1

Draft
endolith wants to merge 1 commit into
masterfrom
cursor/sfz-forward-slash-paths-984d
Draft

Use forward slashes in SFZ paths for Linux/macOS compatibility#1
endolith wants to merge 1 commit into
masterfrom
cursor/sfz-forward-slash-paths-984d

Conversation

@endolith

Copy link
Copy Markdown
Owner

Summary

All .sfz files used Windows-style backslashes in default_path and in Snare2’s nested sample= paths. Many SFZ players on Linux and macOS treat those literally and fail to load WAVs next to the instrument.

Changes

  • Replaced \ with / in every affected default_path and sample= line (13 instruments).

Toms.sfz was unchanged (includes only; no path separators).

Notes

The readme still mentions velocity transitions as a known limitation; that is an artistic/tuning concern, not addressed here.

Open in Web Open in Cursor 

Windows-style backslashes in default_path and relative sample paths
break or are unreliable on Linux and macOS SFZ engines. Forward slashes
are accepted on all common platforms when the WAV folders sit next to
the SFZ as distributed.

Co-authored-by: endolith <endolith@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants