[BUG]: program can't handle overlapping timestamps #28

Closed
opened 2026-09-02 14:05:35 +04:00 by max · 0 comments
Owner

📋 Description

If timestamps are overlapping, program must give some warning (maybe it's intended, but in the most cases it's not) but continue anyway

🔁 Steps to Reproduce

cat > /tmp/overlap.txt << 'EOF'
00:00-01:30 Track 1 - Artist 1
01:00-02:00 Track 2 - Artist 2
02:00-03:00 Track 3 - Artist 3
EOF
./venv/bin/python -m audio_splitter.main test_data/png_test.opus /tmp/overlap.txt

Expected Behavior

Program throws a warning, but continues

Actual Behavior

No warning, it just works silently

📄 Logs / Screenshots

No response

📦 Audio Splitter Version

commit 25e8c0293e

💻 Operating System

Debian 13

🌍 Browser (if applicable)

No response

📎 Additional Context

No response

Submission Checklist

  • I have searched for existing issues (open and closed) that report the same problem
  • I am using the latest stable release of Audio Splitter
  • I have provided clear steps to reproduce the issue
  • I have included relevant logs or error messages (with sensitive info removed)
### 📋 Description If timestamps are overlapping, program must give some warning (maybe it's intended, but in the most cases it's not) but continue anyway ### 🔁 Steps to Reproduce ``` cat > /tmp/overlap.txt << 'EOF' 00:00-01:30 Track 1 - Artist 1 01:00-02:00 Track 2 - Artist 2 02:00-03:00 Track 3 - Artist 3 EOF ./venv/bin/python -m audio_splitter.main test_data/png_test.opus /tmp/overlap.txt ``` ### ✅ Expected Behavior Program throws a warning, but continues ### ❌ Actual Behavior No warning, it just works silently ### 📄 Logs / Screenshots _No response_ ### 📦 Audio Splitter Version commit 25e8c0293e4b8bc52984c6c6a1711f98594603d9 ### 💻 Operating System Debian 13 ### 🌍 Browser (if applicable) _No response_ ### 📎 Additional Context _No response_ ### ✅ Submission Checklist - [x] I have searched for existing issues (open and closed) that report the same problem - [x] I am using the latest stable release of Audio Splitter - [x] I have provided clear steps to reproduce the issue - [ ] I have included relevant logs or error messages (with sensitive info removed)
max added the bug label 2026-09-02 14:05:35 +04:00
max added the core label 2026-09-02 15:48:07 +04:00
max closed this issue 2026-09-02 16:07:27 +04:00
Sign in to join this conversation.