[Bug]: Slate Virtual Mix Rack crashes both Tracktion Engine as Waveform
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 8/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- audio-video-rtc
Research direction
The report names no source file, stacktrace or unit test, so start by reproducing the crash on Windows 11 with the Slate Virtual Mix Rack VST3 in Waveform, cycling presets, and capturing a dump. The relevant entry points are Tracktion Engine's VST3 hosting and plug-in state/preset restore code plus the audio-thread callback that runs while loading. Done means a minimal reproduction (ideally a unit test) and either a fix or a clear statement that the fault is inside the plug-in.
Written by the indexing model from the issue text.
Description
Detailed steps on how to reproduce the bug
- Load VMR on a track.. 1 will do.
- start recalling presets 1 after the other.
- Both waveform and tracktion engine will crash within 30 seconds of recalling presets 1 after the other
What is the expected behaviour?
No crash.
According to Slate Digital this is not a problem on their side as supposedly this is not a problem in all their supported DAWs.
Unit test to reproduce the error?
Operating systems
Windows
What versions of the operating systems?
Windows 11
Architectures
x86_64
Stacktrace
No response
Plug-in formats (if applicable)
VST3
Plug-in host applications (DAWs) (if applicable)
Waveform and Tracktion Engine
Testing on the develop branch
The bug is present on the develop branch
Code of Conduct
- I agree to follow the Code of Conduct
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 222
- Avg merge
- 15h 44m
- Merged PRs (30d)
- 33
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Tracktion/tracktion_engine
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Tracktion/tracktion_engine#475 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Tracktion/tracktion_engine#476 · 5 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Tracktion/tracktion_engine#474 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Tracktion/tracktion_engine#473 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Tracktion/tracktion_engine#460 ·
Maintainers usually reply within 1 day
All issues in Tracktion/tracktion_engine
Similar issues
-
objdetect(mcc): CCheckerDetector leaves its chart type uninitialized 🤖🤖🤖Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
(S1 - Need confirmation)
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CleverRaven/Cataclysm-DDA#89182 ·
Maintainers usually reply within 1 day
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ClickHouse/ClickHouse#126833 ·
Maintainers usually reply within 1 day
-
clang:static analyzer
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
llvm/llvm-project#233598 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100