Waveform 13.5.6 Bug Report
-
- KVRist
- 106 posts since 10 Oct, 2005 from St. Louis, MO USA
The comping feature is not running correctly for me in the new release. It is not producing any sound. Comps work perfectly fine in 13.3.13. See screenshot.
You do not have the required permissions to view the files attached to this post.
MacBook Pro M3, 16GB RAM | UAD Volt 2 | Tracktion Waveform 13 Pro/Cockos Reaper 7/Ableton Live 12 Standard/Presonus Studio One 7 Pro | A multitude of paid-for and free VST plugs/samples
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
I have submitted this as a bug through Tracktion Support. I reported it here at KvR earlier but since it was a beta version I didn't use their support system. Now, however, it's a bug in an official release version.
Surely there must be consensus by now...
-
- KVRist
- 223 posts since 23 Mar, 2015 from Ontario, Canada
The midi "Auto update on note resize" option still doesn't work. It's always on whether this option is selected or not. This was sent to support a while ago. Last I heard is it was being sent off to the developers to sort out. Radio silence since. This is all too common.
I was hoping it would be fixed in this release but apparently not.
You guys really need to come up with a better support system. What's the point of users submitting bugs if they just get ignored.
Check out Mulab. It's a one man show and that guy is super involved with his user base. Time to move on, I guess.
d.
I was hoping it would be fixed in this release but apparently not.
You guys really need to come up with a better support system. What's the point of users submitting bugs if they just get ignored.
Check out Mulab. It's a one man show and that guy is super involved with his user base. Time to move on, I guess.
d.
-
- KVRist
- Topic Starter
- 106 posts since 10 Oct, 2005 from St. Louis, MO USA
Let me clarify: it recognizes and plays pre-existing comps just fine. It's when you initiate a comp with raw takes that this bug appears.cjayconrod wrote: Fri Jul 04, 2025 9:59 pm The comping feature is not running correctly for me in the new release. It is not producing any sound. Comps work perfectly fine in 13.3.13. See screenshot.
Screenshot 2025-06-30 at 6.18.53 PM.png
MacBook Pro M3, 16GB RAM | UAD Volt 2 | Tracktion Waveform 13 Pro/Cockos Reaper 7/Ableton Live 12 Standard/Presonus Studio One 7 Pro | A multitude of paid-for and free VST plugs/samples
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
Yes, it seems to no longer be writing new selections to the comp take. I have reported this bug and received a response that it has been forwarded to the dev team. I would hope that this particular bug will be addressed relatively promptly and considering it's something that used to work fine might be a simple fix.cjayconrod wrote: Sat Jul 05, 2025 3:15 pm Let me clarify: it recognizes and plays pre-existing comps just fine. It's when you initiate a comp with raw takes that this bug appears.
BTW, there is another way to do comps, which is Comp Groups. And it still works. It was introduced way back in T6. So if you need to comp NOW you can either go back to 13.3.13 or split your comp takes into tracks and then group them.
Don't listen to him when he teaches you the helpful tip about using Tab to name your track. It's no longer true; now it opens the Mixer. I never use the Mixer but I always rename my tracks, so I miss that.
Surely there must be consensus by now...
-
- KVRer
- 8 posts since 14 Apr, 2020
I too am finding that comps are not working in 13.5.6, but these are existing comps not new ones.
When Show Takes is selected, the last take is highlighted but the comp is no longer there and nothing plays. Selecting a single take works as expected, but then creating another comp silences everything again.
I'm on Win 10.
When Show Takes is selected, the last take is highlighted but the comp is no longer there and nothing plays. Selecting a single take works as expected, but then creating another comp silences everything again.
I'm on Win 10.
-
- KVRer
- 8 posts since 14 Apr, 2020
Just to add to the previous post, after going back to 13.3.13 I have now found that an edit I opened in 13.5.6 but didn't change or save, is exhibiting the same problem with silent/missing comps. Clips with a single take selected work fine.
It seems that the comp is corruped/removed as soon as the file is opened.
It seems that the comp is corruped/removed as soon as the file is opened.
-
- KVRer
- 8 posts since 14 Apr, 2020
Definitely fixed in 13.5.8 for me too...
Thanks to the devs for fixing it so quickly!
Thanks to the devs for fixing it so quickly!
