[Bug]: DemoRunner Pitch Shift and Timing chipmunk effect
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- audio-video-rtc
Research direction
The demo is the 'Pitch and Time' page of the DemoRunner example app; start there and see which engine classes it drives for pitch shifting and time stretching. Check whether the tempo slider is wired to the Edit's tempo or the time-stretcher ratio, and whether pitch is passed as semitones or a playback-rate ratio — the 'chipmunk' result hints at a rate change rather than a true pitch shift. Done would be a reproducible answer on whether this is demo wiring, an engine limitation, or expected behaviour of the algorithm, then a fix or documented limitation. Note the report is 580 days old with two comments and no decision.
Written by the indexing model from the issue text.
Description
Detailed steps on how to reproduce the bug
On macOS I was testing the DemoRunner Pitch Shift and Timing demo. I loaded an audio clip that had vocals and music. When Adjusting the pitch I notice that vocals sound like chipmunks. I selected both algorithms but both had the same effect. I did not adjust the pitch by much. Also I noticed that with the timing when I adjusted the slider it will pause the audio clip for a brief moment and start back playing. Is there a way to speed up audio without the momentarily Pause? Also I noticed that while I did adjust the speed/tempo slider the tempo did not speed up or slow down.
reproduce: run the DemoRunner and select Load Demo, select Pitch and Time. load a audio file and try to adjust the sliders
What is the expected behaviour?
I was expecting to slide the pitch slider and the pitch adjust higher or lower without chipmunk effect.
I was expecting to slide the time(tempo.speed) slider and the audio speed up or slow down. Also was expecting it to do this without the audio stopping when making timing adjustment
Unit test to reproduce the error?
I am using the code from the example for pitch and time in the DemoRunner
Operating systems
macOS
What versions of the operating systems?
I am on the latest version of macOS 2025
Architectures
ARM
Stacktrace
Plug-in formats (if applicable)
No response
Plug-in host applications (DAWs) (if applicable)
No response
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
(S1 - Need confirmation)
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CleverRaven/Cataclysm-DDA#89194 ·
Maintainers usually reply within 1 day
-
reproduced
Difficulty 1/5 Under an hour Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day