[Casper Hansen]

Sorry, I didn’t notice the reply. That’s not possible, as I usually mix my drums in an empty project, save it the SD2 project and discard the Logic project — so the project doesn’t exist any longer.

[Casper Hansen]

I’m sorry, but I can provide no details on how to reproduce it, as it seems pretty random, except it usually happens when I change a label (producing the label-on-label, as shown) or when adding some effect to a bus. This occurred in 10.11.3 as well, a while back. I’m sorry, it’s not much to go on. If I can provide anything else, should it occur again, let me know, and I’ll do my best.

[Casper Hansen]

@John said:

Hi,

which OS and Logic version is this? Computer specs?

Everything is up-to-date — latest versions. Here you go 🙂

[Casper Hansen]

@Scott E said:

could this be part of the graphics issue introduced by Apple in Yosemite & continued (unresolved) in El Capitan?

people testing the new Mac OS (“Sierra”?) have suggested that it may be addressed in the new release this fall.
This graphics issue is not isolated to Toontrack or even solely to plugins.
Please Google it or check the Apple Support and forum.

Perhaps, I don’t know 🙂 First I’ve heard of it, I’ll look into it 🙂

[Casper Hansen]

@Olle said:

Well, these effects make sure that changes to their parameters
do not result in glitches. That means that they have to slowly change
internal values as rendering is done. If you turn a knob really quickly
you can see that the resulting ‘curve’ changes gradually.

I understand the advantage of that, and why you’ve put that mechanism in place.

But … hold on… I might have jumped on the explanation you gave a little too quickly. I have now seen an effect that didn’t update the graphics, and yet signal was running through it, and there was an audible change in the sound by manipulating the knobs on a filter, but the graph didn’t change. I can’t imagine that is still justified by the channel being inactive, since this instance most definitively was not the case? I’ll post a video of it when it happens again, with audio.

In any case, as you can see from the first video, even if it is intentional, the EQ display does in fact update whilst the Compression and Filter does not? Perhaps I should be more clear on what I mean by display; it’s the visual indication of what the effect does, ie. the graphs and meters.

[Casper Hansen]

@Olle said:

> having it on a bus as an insert makes it fail,

Yes, if that bus isn’t actually executing. I.e. if nothing is routed
to it then any effect sitting there is not actually running and so
any internal state of that effect is never updated.

Oh, I see! Well, that isn’t apparent that no signal would disable the graphics as well. Sorry about that. My bad 😛

[Casper Hansen]

@Olle said:

When this happens, do you still have sound? What you show
is what happens when the rendering engine is not running.

Everything else works just fine. The controls still respond and work as expected. It’s only the graphical displays/feedback that fail to update. And the plug-in still produces sound, and applies the effect expected from the controls — it’s purely the graphical feedback displays that fail.

UPDATE: I’ve found out that moving the failing effect between channels make it work and fail; having it on a bus as an insert makes it fail, but moving it to one of the input-channels suddenly makes it work. Moving it back to the bus makes it fail again. So that should give you an even better idea of what’s going on. I’m a computer science student myself, so I’m doing everything I can to give you something that pin-points the bug. Thus far it looks like the bug only affects the busses! 🙂

Here’s a video showing the bus failing, whilst inputs and outputs work fine:
https://www.youtube.com/watch?v=tCH7OU1xQko

[Author]

Replies