big issues with Tracktion waveform using 3 display monitors, emails to support being ignored
-
dave the panda dave the panda https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=620934
- KVRer
- 4 posts since 27 Jul, 2023
So I been using Traction waveform for about 16 months now and i do like the work flow and lots of other features it is simple that's what I like I can just get on with things but always had niggling issues
I am currently testing Beta version of Cakewalk next and I am impressed really easy to use great functionality still lot of work to do on this DAW but on Beta 85% there for me, yes crashes a bit but its a beta, but good start for cakewalk next
Anyway been having issues with waveform
i have a 3 monitor display system, same set up used on Cakewalk by bandlab for years and now on Cakewalk Next with no issues with lag as i do with waveform and this is with midi and WAV
so to waveform
Screen 1 = tracks, Screen 2 =mixer and midi editor , Screen 3 VST plug in
when using i found waveform was stalling, slow to respond, freezing could not adjust VST on the fly, metering mixers lagging, program not responding to stop commands, look as if i had CPU issues but CPU meter really low usage,
i have rendered most track from midi to WAV to reduce this issues
I have 2 xenon 10 core CPU that's 20 core, 40 threads, 32 gig ram, 6 monitor graphic card with 4 gig Vram, so more than enough
so went on to this forum and others forums and found other users with the same issue using multi monitor set up
I have concluded its a video rendering issue that Waveform DAW is not handling the rendering very well
i have reduced this issue by changing it from open GL rendering to software rendering and it is a bit better so it is a video rendering problem
this has made the DAW very difficult to use to a point where i am looking at other DAW
so i had some email comms at the beginning with Tracktion now they are just ignoring me multiple emails sent no response
its a shame and I am disappointed I like the DAW, but really Tracktion not responding to emails
Tracktion is never in the top 10 for DAW list ever, i think i heard 15th, if Tracktion keep ignoring customers with issues, you wont have any customer at all
guys let me know if anyone is having the same issues using 2 or more display monitors
I am currently testing Beta version of Cakewalk next and I am impressed really easy to use great functionality still lot of work to do on this DAW but on Beta 85% there for me, yes crashes a bit but its a beta, but good start for cakewalk next
Anyway been having issues with waveform
i have a 3 monitor display system, same set up used on Cakewalk by bandlab for years and now on Cakewalk Next with no issues with lag as i do with waveform and this is with midi and WAV
so to waveform
Screen 1 = tracks, Screen 2 =mixer and midi editor , Screen 3 VST plug in
when using i found waveform was stalling, slow to respond, freezing could not adjust VST on the fly, metering mixers lagging, program not responding to stop commands, look as if i had CPU issues but CPU meter really low usage,
i have rendered most track from midi to WAV to reduce this issues
I have 2 xenon 10 core CPU that's 20 core, 40 threads, 32 gig ram, 6 monitor graphic card with 4 gig Vram, so more than enough
so went on to this forum and others forums and found other users with the same issue using multi monitor set up
I have concluded its a video rendering issue that Waveform DAW is not handling the rendering very well
i have reduced this issue by changing it from open GL rendering to software rendering and it is a bit better so it is a video rendering problem
this has made the DAW very difficult to use to a point where i am looking at other DAW
so i had some email comms at the beginning with Tracktion now they are just ignoring me multiple emails sent no response
its a shame and I am disappointed I like the DAW, but really Tracktion not responding to emails
Tracktion is never in the top 10 for DAW list ever, i think i heard 15th, if Tracktion keep ignoring customers with issues, you wont have any customer at all
guys let me know if anyone is having the same issues using 2 or more display monitors
-
- KVRist
- 359 posts since 21 Jun, 2020
Hmm, there are such problems. There are friezes. But I don't think it has anything to do with the number of monitors. Plugins cause such freezes for me. For example, using Auburn Sounds Lens and Minimal Audio Rift together on the screen causes such problems. And there are several other plugin combinations.
- KVRist
- 147 posts since 22 Oct, 2016
I have two video cards and three monitors, surprisingly, but apart from the fact that I can't distribute individual windows across different monitors, I have never noticed any difficulties with video rendering.
We discussed in the next topic the problem of rendering the processor inside Waveform, the program never fully loads the processor power. You can read the next topic, we discussed it there
viewtopic.php?p=8743033#p8743033
We discussed in the next topic the problem of rendering the processor inside Waveform, the program never fully loads the processor power. You can read the next topic, we discussed it there
viewtopic.php?p=8743033#p8743033
цвет волшебства
-
- KVRAF
- 1597 posts since 9 Jan, 2018
I'm using three monitors with Waveform (very similar to what you're doing) and am having no issues. What version of Waveform are you running? What's your OS? Older versions of either may be your culprit.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
dave the panda dave the panda https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=620934
- KVRer
- Topic Starter
- 4 posts since 27 Jul, 2023
so as stated no issues on 3 monitor system with cakewalk by bandlab, cakewalk next or reaper all without issues, i can run 10 plugins all DAWS except waveform, so 2x Zeon 10 core processors , that's 20 core 40 threads, 32 gig ram 6 output graphics card, windows 10, been using cakewalk for over 20 years on 2 monitors without a problem
also on xp, W7 , so it is a waveform issue, it cannot be the lack of processing power plus others on this forum have similar issues, i am running the same tracks through same plugin on all 4 DAW's in-fact all tracks are now rendered, so just using a meter plug in which is only stuttering on waveform, drag it to the main screen and it preforms a bit better take it to another screen and starts to freeze, waveform on latest version 12.511
also on xp, W7 , so it is a waveform issue, it cannot be the lack of processing power plus others on this forum have similar issues, i am running the same tracks through same plugin on all 4 DAW's in-fact all tracks are now rendered, so just using a meter plug in which is only stuttering on waveform, drag it to the main screen and it preforms a bit better take it to another screen and starts to freeze, waveform on latest version 12.511
- KVRist
- 36 posts since 27 Jun, 2018
Waveform Just has bugs everywhere. It's not even about how many monitors you're using in your setup. It's just Waveform's buggy nature.
I'm running the latest version of Waveform 13 on a single monitor with a Windows 11, Core i7 processor, 24Gigs of RAM and 4Gb VRam Graphics Card and yet moving clips around is a problem. It gets much worse when I try to move a bunch of clips around like say, duplicating sections (chorus and verses) to make the arrangement. Waveform becomes almost unusable doing this.
I went online to research the issue and read somewhere that this usually happens on large projects with lots of plugins and to test this theory, I deleted all the plugins and instruments on the beat I just made, leaving behind just the midi clips in the arrange view. There was literally no difference in behaviour when I tried to duplicate the chorus section of the beat.
So, like I said, it's not about your monitor setup or CPU power. Waveform's just a bug fest.
I'm running the latest version of Waveform 13 on a single monitor with a Windows 11, Core i7 processor, 24Gigs of RAM and 4Gb VRam Graphics Card and yet moving clips around is a problem. It gets much worse when I try to move a bunch of clips around like say, duplicating sections (chorus and verses) to make the arrangement. Waveform becomes almost unusable doing this.
I went online to research the issue and read somewhere that this usually happens on large projects with lots of plugins and to test this theory, I deleted all the plugins and instruments on the beat I just made, leaving behind just the midi clips in the arrange view. There was literally no difference in behaviour when I tried to duplicate the chorus section of the beat.
So, like I said, it's not about your monitor setup or CPU power. Waveform's just a bug fest.
- KVRAF
- 19808 posts since 16 Sep, 2001 from Las Vegas,USA
I know that post is from 2023 but the lack of response from Tracktion "support" continues to this day.dave the panda wrote: Sun Oct 15, 2023 10:56 pm so i had some email comms at the beginning with Tracktion now they are just ignoring me multiple emails sent no response
It's going on three months since I put in a support ticket and still no meaningful response other than "we'll pass it on to someone else".
Their response on social media when called out on the lack of response was "we're a small team". Yeah well you've got no probelm spamming social media with advertisements ad infinitum so maybe redirect some of your manpower to supporting your product instead of constantly flogging your product.
I really like Tracktion but it seems more like someone's after school project than a DAW that is under serious development. Yes I know there are betas being released so there is some development but without a willingness or ability to acknowledge and work on fixing bugs there will always be issues.
Shame as it could be a much more popular and bug free DAW in the hands of a larger more dedicated team.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe
