When rendering a stereo file to a mono file panning right does nothing[Bug]:
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- audio-video-rtc
Research direction
Reproduce with the issue steps: import a stereo file, duplicate it to two tracks, pan one hard right, then use 'render selected clip and replace it' to a mono WAV. The payload names no files or tests, so start by searching the engine for the render/pan path that handles stereo-to-mono conversion and clip replacement. Done means a right-panned stereo clip renders a non-empty mono WAV that matches the left-panned result.
Written by the indexing model from the issue text.
Description
Detailed steps on how to reproduce the bug
This is a weird one. Waveform 13.0.42
Import a stereo file into a track (Channel 1). Duplicate it to another track (Channel 2). Pan one stereo track (CH1) left and the other (CH2) right.
Next render CH1 using the "render selected clip and replace it" to a mono wav file = works and shows up and works as it should.
Next render CH2 using the "render selected clip and replace it" to a mono wav file = no wav file shows up and the render is blank.
The reason I ran across this is because I am trying to take a stereo file into dual mono for editing purposes.
What is the expected behaviour?
The software should render the file whether it is panned left or right.
Unit test to reproduce the error?
No response
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)
No response
Testing on the develop branch
I have not tested against 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
-
Python PointcloudOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ArduCAM/Arducam_tof_camera#125 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
maplibre/maplibre-native#4822 ·
Maintainers usually reply within 1 day
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
ai_p2 comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ClickHouse/ClickHouse#127437 ·
Maintainers usually reply within 1 day