Tracktion Software

briantracktion · Post by **briantracktion** » Wed Aug 22, 2018 3:24 am

Hi everyone, just another quick update to the recent 9.3.1 beta. Let us know how it goes!

https://marketplace.tracktion.com/shop/ ... rchive?v=9

gavindi · Post by **gavindi** » Wed Aug 22, 2018 6:20 am

So far so good. Everything seems to be working the way it should.
I still have to use the LD_PRELOAD kludge to get it to start though~

PierreG · Post by **PierreG** » Wed Aug 22, 2018 7:28 am

Thanks for the quick update!

The A (automation) drag issue fix is working for me.

Here's a strange one...

I run W on an old duo core laptop with a non-dedicated GPU, so I know my graphics performance is not gonna be optimal, yet for what it's worth check this out. If I have a LFO modifier on a track and I have that track displayed on the screen, the GUI of the Auburn Sounds Couture plug stops updating. This only happens with an edit that has quite a bit of plugs in it. I created an edit with just the Couture and an LFO and the Couture GUI ran fine when the LFO track was displayed.

I frequently run into graphics performance issues (stuttering plugin GUI displays or no animation at all) with edits that contain a high density of plugins, so is seems obvious that the main issue is with my underwhelming hardware, yet I wonder if there's something particularly graphics hoggish about the LFOs, in that they seem to be the thing that frequently affects graphic performance.

I notice the modifiers are not showing up as plugs in the CPU meter. Is there any potential for adding these to the meter?

dRowAudio · Post by **dRowAudio** » Wed Aug 22, 2018 10:29 am

The CPU meter tracks audio CPU usage only.
The problem with the Modifiers is that they animate which means they're constantly repainting.

This could be a problem with multiple "dirty rects" being coalesced in to a large repaint area...
Is this on Windows or Mac?

PierreG · Post by **PierreG** » Wed Aug 22, 2018 5:18 pm

dRowAudio wrote:The problem with the Modifiers is that they animate which means they're constantly repainting.

Perhaps a silly thought, yet would an option to disable modifier animation be worth considering?

This could be a problem with multiple "dirty rects" being coalesced in to a large repaint area...

Would this "problem" be rooted in how W handles graphics? Or more of an OS rooted graphics issue?

Is this on Windows or Mac?

Windows 10

PierreG · Post by **PierreG** » Wed Aug 22, 2018 7:52 pm

Further observation of the plug GUI freezes reveals that the modifier roll over text for it's parameter controls (LFO rate, phase, offset and depth) also go away when the modifier element's track is being displayed. By "go away", I mean rolling over the control does not produce popup control labels that are typically displayed.

Again, this is only in a heavily plug populated edit.

Update: The modifier control popup text only goes away when the transport is playing and the modifier track is being displayed. The text returns when you stop the transport (modifier track still displayed).

dRowAudio · Post by **dRowAudio** » Thu Aug 23, 2018 10:35 am

These are all probably side effects of the UI thread getting clogged up.

It's kind of a combination of W and OS graphics. Different OSes handle things in slightly different ways but there are probably optimisations we can do.

Yes, I was thinking of maybe adding an option to disable animations for the mixer widgets.
That won't be a quick change though...

PierreG · Post by **PierreG** » Thu Aug 23, 2018 7:36 pm

Thanks Dave, for offering the possibility of the option to disable mixer widget animations.

Would this option be limited to the mixer view? I experience this issue in the standard transport view (mixer not open), so hopefully this could be a global setting for all views. Adding the animation disable option to each modifier instance seems a decent approach, yet perhaps I'm missing something.

I've found that it works to use the browser to hide non-essential tracks, which tends to bring the plug GUIs back to life. I assume this is because of the lowered graphics load provided by the hiding process. This method helps in the situations where I need to work with plugs in a track that has modifiers (heavier graphics animation load). It's all about opening up resources, similar to freezing tracks for regaining CPU bandwidth, hiding tracks opens up GPU / graphics bandwidth. Of course this is not an optimal solution, yet it's a good one to have when I'm stretching my old Dell laptops to the brink!

BloodyCactus · Post by **BloodyCactus** » Fri Aug 24, 2018 7:18 pm

Just upgraded from 9.2.1 to 9.3.2... it dies and wont even load.

GDB says;

Thread 11 "AnalyticsThread" received signal SIGSEGV, Segmentation fault.

the process dies. No waveform9.

9.3.1, same issue.
9.3.0 works

*edit* ok from other threads;

for me I did
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libcurl.so.4.4.0 /usr/bin/Waveform9

and 9.3.2 works with that. ugh.

PierreG · Post by **PierreG** » Sat Aug 25, 2018 2:07 am

Scanning plugins: The popup message that appears at the end of the Scan for new or updated VST plugs titled Scan Complete, has it's text shifted right and being cut off by the right side of the text box border, thus I can't see all of the text.

Scan for VST3 Seems OK, yet that message is way less verbose than my VST2 scan results, which list a bunch of failures. To replicate this, you'll likely need to generate a large list of failed plugs.

Update: Graphics issues are far deeper than what I described above. I just tried to change the Display Scale in the Settings / Appearance tab to see if this would help with the popup message text issue and discovered that changing the display scale completely throws off mouse pointer location mapping. I had to poke around for a good bit to get back into the scaling box to get it back to 100%, which resolves the mapping issue.

I also notice that typing in 90% scale does nothing. Is this feature limited to set increments (say 25% chunks)?

Update 2: Been adding a lot of plugs today, and this seems to have resolved the clipped text issue... at least for now. The display scaling issue is still present.

Update 3: After more plug scans, the text clipping returned...

fullbackup · Post by **fullbackup** » Thu Aug 30, 2018 1:14 pm

Hi, I have ubuntu 18.04 and it was impossible to run until I erased the tracktion folder inside .config scanned for plug ins and setup audio again like if you installed it for the firs time. Now everything is perfect...

gavindi · Post by **gavindi** » Thu Aug 30, 2018 8:28 pm

PierreG wrote: Update: Graphics issues are far deeper than what I described above. I just tried to change the Display Scale in the Settings / Appearance tab to see if this would help with the popup message text issue and discovered that changing the display scale completely throws off mouse pointer location mapping. I had to poke around for a good bit to get back into the scaling box to get it back to 100%, which resolves the mapping issue.

Actually I noticed this too but I forgot to mention it. So, +1 here.....
But,if I immediately close W9 after setting the new display scale and the restart W9, It's at the new size AND the mouse pointer location is set correctly. It seems it only fully sets the rescale correctly upon start rather than when the scale change occurs.

dRowAudio · Post by **dRowAudio** » Fri Aug 31, 2018 8:03 am

I think the crashing at startup is a race condition on the initialisation of libcurl (i.e. when two threads try to use it at the same time). I'm going to have a look in to this today.

dRowAudio · Post by **dRowAudio** » Fri Aug 31, 2018 8:05 am

gavindi wrote:
PierreG wrote: Update: Graphics issues are far deeper than what I described above. I just tried to change the Display Scale in the Settings / Appearance tab to see if this would help with the popup message text issue and discovered that changing the display scale completely throws off mouse pointer location mapping. I had to poke around for a good bit to get back into the scaling box to get it back to 100%, which resolves the mapping issue.
Actually I noticed this too but I forgot to mention it. So, +1 here.....
But,if I immediately close W9 after setting the new display scale and the restart W9, It's at the new size AND the mouse pointer location is set correctly. It seems it only fully sets the rescale correctly upon start rather than when the scale change occurs.

@gavindi, are you seeing this on Linux or Windows? I think this is a problem with the new per-monitor DPI awareness features which is causing problems if the global scale factor changes whilst the app is open. Restarting should fix this (and keep the scale factor you set). I think this is a JUCE issue though and the person who works on this area is on holiday at the moment so will have to wait a week or so...

gavindi · Post by **gavindi** » Fri Aug 31, 2018 8:13 am

Hey @dRow

I'm seeing this under Linux. But yes, a restart sets the mouse pointer to the correct position-scale so it's no biggie. Easy workaround.
That said, I only found it by mucking about with settings. I run at the normal 100% zoom level anyways. Still, smaller increments/decrements would be nice

Cheers,
G.

Tracktion Software

KVR Audio

Waveform 9.3.2 Public Beta Available