Waveform 8.2.3 Beta Available

[Uhotug]

Well... before 8.2.0 I could only blame collective for the silence bug. But since 8.2.0, Waveform under Linux is simple not usable at all for me (as I have reported, one wrong click and it consumes the whole RAM). Now there is 8.2.3 and the problem is still there.

I wish you all the best, but my decision to get Tracktion bundle for Lunux version was wrong. 2 parts, one does not work right and another does not work at all. I have offered help in case something can not be reproduced (I do not believe that is the case, but still) and there was no interest. As a free software all that is super: a partially functioning toy with nice features. Sorry, but as commercial software that is just a joke.

Sorry to hear you're experiencing problems on Linux. I have a feeling that one report may have been lost in a thread related to another issue. Can I try and clear up what problems you're experiencing?

1. You are seeing a problem with Collective going silent after a short period of playback
2. You are seeing a problem where you click somewhere and all your system RAM is utilised by the app?

Wolfram, the synth developer is still looking in to (1). He's created a build with additional logging information and set that out to a few users who are experiencing the problem. He's now collecting the results and looking in to the problem.

I have posted the log with NaNs:
viewtopic.php?f=22&t=484873&start=75#p6842700

For (2), could you perhaps start a new thread or email support@tracktion.com. I'm not quite sure what you mean by "one wrong click". Where are you clicking to see this problem? Is it in the plugin UI or directly in Waveform?

I guess you have already seen everything I could find (since you have replied to it...):
viewtopic.php?f=22&t=488486&p=6840673#p6838996

Also this not extremely populated board indicates that I am not alone with the issue.

Also, for Linux, there are such a huge range of distros that we can't possibly test and support them all. For example, we've had people use Tracktion/Waveform on: Ubuntu 10,12,14,15,16,17, Ubuntu Studio, Kubuntu, Linux Mint, Arch Linux, Debian and Fedora.
Due to this fragmentation we can only officially support Ubuntu (16.04 for Waveform . However, as shown above, it is possible to run Waveform on other systems.

I use Ubuntu 16.04 on Dell XPS, so "officially supported" platform.

[dRowAudio]

in this beta the waveforms getting actualized instantly after making changes to an audio clip while before it took (felt) ages...

I'm not quite sure what you mean by this? Are you saying something has improved or broken?

No, sorry, just noticed that this delay of the waveform actualization happens with audio files and "Auto tempo" enabled...
Wit this option off, the waveform rebuilds much much faster...

Hmm, I'm not really seeing how I can replicate this? Could you perhaps post a short video of what you're doing to see the crash or some step by step instructions?

Also, as always with crash reports, could you upload or send us a log file? That should help us narrow down the problem and also give us vital system information (such as OS, architecture etc.).
You can get the log file by opening Waveform, clicking the "Help" button then "Show the Waveform log file".

Hopefully we can then replicate and fix the issue. Thanks.

There are a couple of crash logs created... is there any e-mail, where I can send them to???

To recreate:
- Open standard 8 track template
- Load a normal wave file in track 1 and disable (if enabled) Auto Tempo
- double click the audio clip with setting toggle small and large height to maximise it vertically
- zoom in the waveform by mousewheel that the audio clip is larger than your screen, that you need to scroll to see the end...
- grab the cursor by mouse, drag it to i.e. the second beat and split the clip using "/"...
- drag now the cursor to the right hand side that Waveform starts to scroll...

This is the moment, when it just disappears here...

If you can still not recreate it, I´ll make a vid demonstrating...
Btw.: I am on win 8.1 64bit here...

Thanks for the heads up on this. I've fixed it now so stay tuned for the next release.
Thanks!

[dRowAudio]

Well... before 8.2.0 I could only blame collective for the silence bug. But since 8.2.0, Waveform under Linux is simple not usable at all for me (as I have reported, one wrong click and it consumes the whole RAM). Now there is 8.2.3 and the problem is still there.

I wish you all the best, but my decision to get Tracktion bundle for Lunux version was wrong. 2 parts, one does not work right and another does not work at all. I have offered help in case something can not be reproduced (I do not believe that is the case, but still) and there was no interest. As a free software all that is super: a partially functioning toy with nice features. Sorry, but as commercial software that is just a joke.

Sorry to hear you're experiencing problems on Linux. I have a feeling that one report may have been lost in a thread related to another issue. Can I try and clear up what problems you're experiencing?

1. You are seeing a problem with Collective going silent after a short period of playback
2. You are seeing a problem where you click somewhere and all your system RAM is utilised by the app?

Wolfram, the synth developer is still looking in to (1). He's created a build with additional logging information and set that out to a few users who are experiencing the problem. He's now collecting the results and looking in to the problem.

I have posted the log with NaNs:
viewtopic.php?f=22&t=484873&start=75#p6842700

For (2), could you perhaps start a new thread or email support@tracktion.com. I'm not quite sure what you mean by "one wrong click". Where are you clicking to see this problem? Is it in the plugin UI or directly in Waveform?

I guess you have already seen everything I could find (since you have replied to it...):
viewtopic.php?f=22&t=488486&p=6840673#p6838996

Also this not extremely populated board indicates that I am not alone with the issue.

Also, for Linux, there are such a huge range of distros that we can't possibly test and support them all. For example, we've had people use Tracktion/Waveform on: Ubuntu 10,12,14,15,16,17, Ubuntu Studio, Kubuntu, Linux Mint, Arch Linux, Debian and Fedora.
Due to this fragmentation we can only officially support Ubuntu (16.04 for Waveform . However, as shown above, it is possible to run Waveform on other systems.

I use Ubuntu 16.04 on Dell XPS, so "officially supported" platform.

Apologies, that thread got derailed with a discussion about always on top plugin windows. When I check KVR I look at unread posts first and the few before them and must have forgot that there was a discussion about Linux resource usage above.

I do remember looking at this however and I couldn't replicate it. I was in the middle of discussing what it could be with another team member though and we thought it might be due to plugin loading to preview the preset. Do you know if you've chosen a custom plugin to do this? It could be that that is using all the resources as it tries to preview the step clip.

Could you try choosing a low-resource plugin and see if that helps? For example, load the built-in "FM Synth" on to a track with the default preset loaded. Right click it and choose "Use plugin for MIDI preview". Now when you select a Step Clip in the Search panel, does it play with that preset? Do the resources still go haywire?

Cheers, Dave

[Uhotug]

Well... before 8.2.0 I could only blame collective for the silence bug. But since 8.2.0, Waveform under Linux is simple not usable at all for me (as I have reported, one wrong click and it consumes the whole RAM). Now there is 8.2.3 and the problem is still there.

I wish you all the best, but my decision to get Tracktion bundle for Lunux version was wrong. 2 parts, one does not work right and another does not work at all. I have offered help in case something can not be reproduced (I do not believe that is the case, but still) and there was no interest. As a free software all that is super: a partially functioning toy with nice features. Sorry, but as commercial software that is just a joke.

Sorry to hear you're experiencing problems on Linux. I have a feeling that one report may have been lost in a thread related to another issue. Can I try and clear up what problems you're experiencing?

1. You are seeing a problem with Collective going silent after a short period of playback
2. You are seeing a problem where you click somewhere and all your system RAM is utilised by the app?

Wolfram, the synth developer is still looking in to (1). He's created a build with additional logging information and set that out to a few users who are experiencing the problem. He's now collecting the results and looking in to the problem.

I have posted the log with NaNs:
viewtopic.php?f=22&t=484873&start=75#p6842700

For (2), could you perhaps start a new thread or email support@tracktion.com. I'm not quite sure what you mean by "one wrong click". Where are you clicking to see this problem? Is it in the plugin UI or directly in Waveform?

I guess you have already seen everything I could find (since you have replied to it...):
viewtopic.php?f=22&t=488486&p=6840673#p6838996

Also this not extremely populated board indicates that I am not alone with the issue.

Also, for Linux, there are such a huge range of distros that we can't possibly test and support them all. For example, we've had people use Tracktion/Waveform on: Ubuntu 10,12,14,15,16,17, Ubuntu Studio, Kubuntu, Linux Mint, Arch Linux, Debian and Fedora.
Due to this fragmentation we can only officially support Ubuntu (16.04 for Waveform . However, as shown above, it is possible to run Waveform on other systems.

I use Ubuntu 16.04 on Dell XPS, so "officially supported" platform.

Apologies, that thread got derailed with a discussion about always on top plugin windows. When I check KVR I look at unread posts first and the few before them and must have forgot that there was a discussion about Linux resource usage above.

I do remember looking at this however and I couldn't replicate it. I was in the middle of discussing what it could be with another team member though and we thought it might be due to plugin loading to preview the preset. Do you know if you've chosen a custom plugin to do this? It could be that that is using all the resources as it tries to preview the step clip.

Could you try choosing a low-resource plugin and see if that helps? For example, load the built-in "FM Synth" on to a track with the default preset loaded. Right click it and choose "Use plugin for MIDI preview". Now when you select a Step Clip in the Search panel, does it play with that preset? Do the resources still go haywire?
Cheers, Dave

Thank you for the explanation, it sounds reasonable. I am ready to apologies for my harsh statements... in case we can somehow advance in this problem solving. I will be back at my usual place next week, where it is possible to connect to my computer remotely (with TeamViewer).

But your idea about FM Synth is good, there are my observations with it:

A Edit with one FM Synth, marked as the plug-in for preview, and a track with test audio clip.

8.2.3
a) New Edit with just inserted FM Synth produce sounds, from its MIDI keyboard and from MIDI track
b) Saved Edit (so, just after saving and restarting Waveform) produce NO sound from FM Synth
c) Master volume is ALWAYS reset to zero after reloading, after bringing it back, audio content sounds ok (including preview and track play), but FM Synth keep silence
d) MIDI clip preview seems like playing, but does not produce any sound
e) Step clip preview freeze (100%CPU, eating RAM) Waveform
f*) periodically "Available downloads" "Login" dialog appears on start. I could not determine conditions, but it happens even after normal restart (without version changes or crashes). Probably unrelated, but you know better (I mean that can indicate some file permission/locking issue... I have already checked permissions on related catalogs and files, but it can happened I have skipped some).

Nothing unusual in the log, also no Collective loading statements.

8.1.16
everything works as expected

[Benutzername]

But then I created a fresh project and a simple edit with three simple Collective tracks using stock sounds. This one also went silent after a few seconds and after a restart this edit can't be loaded at all with 8.2.x, no matter what I do (also eats up memory like crazy with 1 CPU at 100%). Opening the edit with 8.1.2 works but the Collective tracks still only produce silence after a few beats.

I just realized that I forgot to attach the project.

I've moved the plugins to ~/.vst and reset the owner and permissions of the content but this didn't make a difference. Then I played around with the entries in the collective settings file (like Multi CPU and Open GL) but this didn't help either.

[Trancit]

Thanks for the heads up on this. I've fixed it now so stay tuned for the next release.
Thanks!

Thank you

[dRowAudio]

Thank you for the explanation, it sounds reasonable. I am ready to apologies for my harsh statements... in case we can somehow advance in this problem solving. I will be back at my usual place next week, where it is possible to connect to my computer remotely (with TeamViewer).

But your idea about FM Synth is good, there are my observations with it:

A Edit with one FM Synth, marked as the plug-in for preview, and a track with test audio clip.

8.2.3
a) New Edit with just inserted FM Synth produce sounds, from its MIDI keyboard and from MIDI track
b) Saved Edit (so, just after saving and restarting Waveform) produce NO sound from FM Synth
c) Master volume is ALWAYS reset to zero after reloading, after bringing it back, audio content sounds ok (including preview and track play), but FM Synth keep silence
d) MIDI clip preview seems like playing, but does not produce any sound
e) Step clip preview freeze (100%CPU, eating RAM) Waveform
f*) periodically "Available downloads" "Login" dialog appears on start. I could not determine conditions, but it happens even after normal restart (without version changes or crashes). Probably unrelated, but you know better (I mean that can indicate some file permission/locking issue... I have already checked permissions on related catalogs and files, but it can happened I have skipped some).

Nothing unusual in the log, also no Collective loading statements.

8.1.16
everything works as expected

This is interesting. Do you happen to be located in Germany or another area where it is common to use a comma as a fractional separator e.g. "3,141" rather than "3.141" for Pi?

There was a short-lived bug in the framework we use which made reading numbers return incorrect values for certain locales. There's a chance v8.2.3 was built with this bug. I believe it is fixed now so I've done another build to see if the problem is resolved. I've PMed you a link, can you install that and let me know if the volume resetting is still there? It could be this was also manifesting itself in other ways that were causing the high RAM usage...

[Uhotug]

Thank you for the explanation, it sounds reasonable. I am ready to apologies for my harsh statements... in case we can somehow advance in this problem solving. I will be back at my usual place next week, where it is possible to connect to my computer remotely (with TeamViewer).

But your idea about FM Synth is good, there are my observations with it:

A Edit with one FM Synth, marked as the plug-in for preview, and a track with test audio clip.

8.2.3
a) New Edit with just inserted FM Synth produce sounds, from its MIDI keyboard and from MIDI track
b) Saved Edit (so, just after saving and restarting Waveform) produce NO sound from FM Synth
c) Master volume is ALWAYS reset to zero after reloading, after bringing it back, audio content sounds ok (including preview and track play), but FM Synth keep silence
d) MIDI clip preview seems like playing, but does not produce any sound
e) Step clip preview freeze (100%CPU, eating RAM) Waveform
f*) periodically "Available downloads" "Login" dialog appears on start. I could not determine conditions, but it happens even after normal restart (without version changes or crashes). Probably unrelated, but you know better (I mean that can indicate some file permission/locking issue... I have already checked permissions on related catalogs and files, but it can happened I have skipped some).

Nothing unusual in the log, also no Collective loading statements.

8.1.16
everything works as expected

This is interesting. Do you happen to be located in Germany or another area where it is common to use a comma as a fractional separator e.g. "3,141" rather than "3.141" for Pi?

There was a short-lived bug in the framework we use which made reading numbers return incorrect values for certain locales. There's a chance v8.2.3 was built with this bug. I believe it is fixed now so I've done another build to see if the problem is resolved. I've PMed you a link, can you install that and let me know if the volume resetting is still there? It could be this was also manifesting itself in other ways that were causing the high RAM usage...

That was it! I in fact have de_DE.UTF-8 locale settings for numbers (ru_RU for messages).

I can confirm, with PMed version everything is normal: no volume reset, FM synth works after Waveform restart, MIDI preview works and clicking on Steps no longer freeze Waveform.

EDIT: setting en_US unfortunately does not solve Collective silence bug.

PS. As promised, I apologies for my original reaction on 8.2.3. I had to just remind you about my problem politely.

[Benutzername]

Thank you very much for this hint. I'm by default on de_DE.UTF-8 too. But when I use

Code: Select all

user$ LANG=en_US.UTF-8 Waveform8

to start Waveform then I can open all tracks also with 8.2.x. This solves also several other loading problems like wrong clip lengths, cleared master levels etc.

Now we only need a working Collective implementation that runs for more than a few seconds.

But then I created a fresh project and a simple edit with three simple Collective tracks using stock sounds. This one also went silent after a few seconds and after a restart this edit can't be loaded at all with 8.2.x, no matter what I do (also eats up memory like crazy with 1 CPU at 100%). Opening the edit with 8.1.2 works but the Collective tracks still only produce silence after a few beats.

I just realized that I forgot to attach the project.

I've moved the plugins to ~/.vst and reset the owner and permissions of the content but this didn't make a difference. Then I played around with the entries in the collective settings file (like Multi CPU and Open GL) but this didn't help either.

[dRowAudio]

That's great everyone. Glad we finally narrowed that down!
I'll get a build together that fixes these issues.

The Collective silence bug is unrelated, but we are making progress on that...

[Benutzername]

When I limit Waveform to one CPU then Collective doesn't go silent anymore on my system:

Code: Select all

user$ LANG=en_US.UTF8 Waveform8 &
user$ taskset -c -a 0 `pidof Waveform8`

Of course this is not practical for music production. But it shows that there is some kind of thread sync or deadlock issue.

[dRowAudio]

When I limit Waveform to one CPU then Collective doesn't go silent anymore on my system:

Code: Select all

user$ LANG=en_US.UTF8 Waveform8 &
user$ taskset -c -a 0 `pidof Waveform8`

Of course this is not practical for music production. But it shows that there is some kind of thread sync or deadlock issue.

That's interesting. Does changing the number of "CPU Cores to Use" in the "Audio Devices" settings tab to 1 have the same results?

[Benutzername]

No, this settings makes no difference at all. But I noticed some NaN messages in the console that I've never noticed before:

Code: Select all

Initialising windows...
Language: English
ACCESS:  RW_INTERLEAVED
FORMAT:  S32_LE
SUBFORMAT:  STD
SAMPLE_BITS: 32
FRAME_BITS: 64
CHANNELS: 2
RATE: 44100
PERIOD_TIME: (11609 11610)
PERIOD_SIZE: 512
PERIOD_BYTES: 4096
PERIODS: 4
BUFFER_TIME: (46439 46440)
BUFFER_SIZE: 2048
BUFFER_BYTES: 16384
TICK_TIME: 0
tstamp_mode: NONE
tstamp_type: MONOTONIC
period_step: 1
avail_min: 512
start_threshold: 512
stop_threshold: 4611686018427387904
silence_threshold: 0
silence_size: 4611686018427387904
boundary: 4611686018427387904
Gain: 145 NaN
NaturalReverb: 53 NaN
SFilter24: 3635 NaN
SFilter12: 3135 NaN
BFilter: 22333 NaN
StereoAmp: 5593 NaN
Compressor: 43 NaN
OnePole: 2057770 NaN
PlateReverb: 42 NaN
Gain: 319 NaN
NaturalReverb: 110 NaN
Compressor: 48 NaN
OnePole: 2549290 NaN
PlateReverb: 47 NaN
Gain: 573 NaN
NaturalReverb: 183 NaN
SFilter24: 10543 NaN
SFilter12: 8015 NaN
BFilter: 67309 NaN
StereoAmp: 16837 NaN
Compressor: 84 NaN
OnePole: 5360608 NaN
PlateReverb: 130 NaN
Gain: 627 NaN
NaturalReverb: 200 NaN

But this output occurred only once so it may be unrelated to this bug.

However, I've managed to get the audio back and I've got it on tape: click

Sorry for the bad audio but I've tried several screencast tools and they all refused to record the audio output of Waveform. So I had to use the built in microphone of the laptop.

[terrynoakes]

Strange behaviour of midi clips, selecting clip, then trying to double click to expand makes the clips jump all over the place!
Just trying to select clip is difficult. it jumps up a track, and forwards and backwards in a flickering manner. However using Hide /Show midi clip seems to work ok.
On the positive side, deleting all clips except for drum, randomize selected velocities works a treat and just as I'd hoped.
cheers.
Wee clip to hopefully show you what I mean.


Win 8.1 64bit / intel i3 3.30 GHz/16 ram

Back from my holiday, I have re installed 8.2.3 Beta.
I am still experiencing the same problem, as shown in the video. I have tried 3 different mice, mouse's ?? , 2 x usb wireless and one usb wired
Still messing around with beta, when I click on a clip it seems to jump up 2 tracks, ie: if I click on clip on say track 6, the clip will jump up to track 4 etc. this is with midi and audio.

Started Fresh edit in 8.2.3, imported a midi file, exhibited the afore mentioned problems. Reinstalled 8.2.0 opened the edit and it worked fine, no jumping about clips etc.

[madrang]

I tried the 8.2.3 beta, but the plugins now seems to close instantly after being opened.
Before once in a while i had this issue, now it always does it....

Code: Select all

7 Sep 2017 16:34:51  Opening VST UI: #TStereo Delay
7 Sep 2017 16:34:51  Closing VST UI: #TStereo Delay
7 Sep 2017 16:34:57  Opening VST UI: #TStereo Delay
7 Sep 2017 16:34:57  Closing VST UI: #TStereo Delay
7 Sep 2017 16:34:58  Opening VST UI: #TStereo Delay
7 Sep 2017 16:34:58  Closing VST UI: #TStereo Delay
7 Sep 2017 16:34:59  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:00  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:00  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:01  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:02  Opening VST UI: #TStereo Delay
7 Sep 2017 16:35:02  Closing VST UI: #TStereo Delay
7 Sep 2017 16:35:03  Opening VST UI: #TCompressor
7 Sep 2017 16:35:03  Closing VST UI: #TCompressor
7 Sep 2017 16:35:04  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:04  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:05  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:05  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:05  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:05  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:06  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:06  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:07  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:07  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:07  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:08  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:08  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:09  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:09  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:09  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:10  Opening VST UI: #TEqualiser
7 Sep 2017 16:35:10  Closing VST UI: #TEqualiser
7 Sep 2017 16:35:11  Opening VST UI: #TStereo Delay
7 Sep 2017 16:35:12  Closing VST UI: #TStereo Delay
7 Sep 2017 16:35:12  Opening VST UI: #TStereo Delay
7 Sep 2017 16:35:12  Closing VST UI: #TStereo Delay
7 Sep 2017 16:35:13  Opening VST UI: #TStereo Delay
7 Sep 2017 16:35:13  Closing VST UI: #TStereo Delay
7 Sep 2017 16:35:14  Opening VST UI: #TStereo Delay
7 Sep 2017 16:35:14  Closing VST UI: #TStereo Delay
7 Sep 2017 16:35:14  Opening VST UI: #TStereo Delay
7 Sep 2017 16:35:14  Closing VST UI: #TStereo Delay

Edit: Just noticed that leaving the mixer view open in a second tab is causing this. If i close it, the plugins will stay open, BUT if i dare to try to reopen it after opening a plugins, the plugins windows start to blink and become unusable....

Code: Select all

7 Sep 2017 16:52:14  Opening VST UI: #TStereo Delay
7 Sep 2017 16:55:33  Closing VST UI: #TStereo Delay
7 Sep 2017 16:55:38  Opening VST UI: #TEqualiser
##Opening Mixer in new tab with #TEqualiser already on screen, but not touching the plugin...
7 Sep 2017 16:56:04  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:04  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:04  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:04  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:04  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:04  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:05  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:05  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:05  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:05  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:05  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:05  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:06  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:06  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:06  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:06  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:06  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:06  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:06  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:07  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:07  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:07  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:07  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:07  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:07  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:07  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:08  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:08  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:08  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:08  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:08  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:08  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:09  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:09  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:09  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:09  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:09  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:09  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:10  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:10  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:10  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:10  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:10  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:10  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:10  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:10  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:11  Closing VST UI: #TEqualiser
7 Sep 2017 16:56:11  Opening VST UI: #TEqualiser
7 Sep 2017 16:56:17  Closing VST UI: #TEqualiser

Also i don't know since when, but i noticed not too long ago that the input/output list using Jack are reversed....

trckjack.png