Beta v13.0.42 released - nothing mind blowing in this one

[FigBug]

Just a few crash fixes and JS improvements

https://marketplace.tracktion.com/downl ... chive?v=13

Code: Select all

13.0.42
- Javascript:           Fixed spelling (arrangmentmixer -> arrangementMixer)
- UI:                   Fixed UI layouts not saving clip launcher state
- Controllers:          Improve controller autodetection on Windows
- Controllers:          Add filtering to log window
- Windows:              Fix deadlock on high fps displays
- Windows:              Fix crash dragging windows between displays

13.0.41
- Bugs:                 Fixed crash click + dragging new SysEx event
- Javascript:           Added moveTransportToMarker
- Javascript:           Added more UI components to toggleVisibility()
- Javascript:           Added getMixerViewState() and getMidiViewState()
- Controllers:          Add marker jump commands to custom control surface
- Sampler:              Fixed crash if trying to sample from audio inputs if no inputs configured
- UI:                   Added menu item to hide or show controllers log window

[FigBug]

Somebody was asking how to write a script to show clip launcher, this now works. You can have a macro to show the mixer in Clip Launcher mode or in Mixer mode.

Show clip launcher

Code: Select all

var ev = Tracktion.getViewState();
var ms = Tracktion.getMixerViewState();

var showing = ev.getProperty('mixerPanelShown') && ms.getProperty('clipsVisible');

if (showing)
{
  ev.setProperty('mixerPanelShown', false);
}
else
{
  ev.setProperty('mixerPanelShown', true);

  
  ms.setProperty('overviewVisible', false);
  ms.setProperty('smallMetersVisible', false);
  ms.setProperty('inputsVisible', true);
  ms.setProperty('clipsVisible', true);
  ms.setProperty('modifiersVisible', false);
  ms.setProperty('bigMetersVisible', false);
  ms.setProperty('pluginsVisible', false);
  ms.setProperty('outputsVisible', false);
  ms.setProperty('levelsVisible', false);
}

or Show Mixer

Code: Select all

var ev = Tracktion.getViewState();
var ms = Tracktion.getMixerViewState();

var showing = ev.getProperty('mixerPanelShown') && ms.getProperty('outputsVisible');

if (showing)
{
  ev.setProperty('mixerPanelShown', false);
}
else
{
  ev.setProperty('mixerPanelShown', true);

  ms.setProperty('overviewVisible', false);
  ms.setProperty('smallMetersVisible', false);
  ms.setProperty('inputsVisible', true);
  ms.setProperty('clipsVisible', false);
  ms.setProperty('modifiersVisible', false);
  ms.setProperty('bigMetersVisible', false);
  ms.setProperty('pluginsVisible', true);
  ms.setProperty('outputsVisible', true);
  ms.setProperty('levelsVisible', true);
}

[Maarid]

I know I'm familiar, I hope they don't start hitting me.
Figbug, if you yourself (I'm sure) used the program as a working tool, I think you couldn't help but notice
It is not very convenient to manually change the size of the track height, even with a low dpi of the mouse, there is a slight discomfort, perhaps a weak adhesion to the edge between the tracks would save the situation? Double-clicking is great, but not too convenient, especially if there are three states in a circle, I'll just spend time playing with the size of the tracks.

[pough]

Code: Select all

- UI:                   Fixed UI layouts not saving clip launcher state

Can you also add the state of the master track?

[unholyeyebrows]

Hi - any news on solving the missing libjavascriptcoregtk-4.0-18 dependency in Ubuntu 24.04? The bug raised with Canonical (https://bugs.launchpad.net/ubuntu/+sour ... ug/2061914) is likely not to be fixed (i.e this is a legacy library removed from the 24.04 release) and as such applications may need to switch to a newer version. Thanks.

[dajonaga]

Hi - any news on solving the missing libjavascriptcoregtk-4.0-18 dependency in Ubuntu 24.04? The bug raised with Canonical (https://bugs.launchpad.net/ubuntu/+sour ... ug/2061914) is likely not to be fixed (i.e this is a legacy library removed from the 24.04 release) and as such applications may need to switch to a newer version. Thanks.

Upgrading to webkit2gtk-4.1 seems to be the solution, although there might be some concerning issues/bugs...

More info about Canonical/Ubuntu and Debian removing webkit2gtk4.0

https://ubuntu-archive-team.ubuntu.com/ ... tintesting
https://discourse.ubuntu.com/t/desktop- ... 24/42754/3
https://release.debian.org/transitions/ ... k-4.0.html

[dellboy]

Somebody was asking how to write a script to show clip launcher, this now works. You can have a macro to show the mixer in Clip Launcher mode or in Mixer mode.

Show clip launcher

Code: Select all

var ev = Tracktion.getViewState();
var ms = Tracktion.getMixerViewState();

var showing = ev.getProperty('mixerPanelShown') && ms.getProperty('clipsVisible');

if (showing)
{
  ev.setProperty('mixerPanelShown', false);
}
else
{
  ev.setProperty('mixerPanelShown', true);

  
  ms.setProperty('overviewVisible', false);
  ms.setProperty('smallMetersVisible', false);
  ms.setProperty('inputsVisible', true);
  ms.setProperty('clipsVisible', true);
  ms.setProperty('modifiersVisible', false);
  ms.setProperty('bigMetersVisible', false);
  ms.setProperty('pluginsVisible', false);
  ms.setProperty('outputsVisible', false);
  ms.setProperty('levelsVisible', false);
}

or Show Mixer

Code: Select all

var ev = Tracktion.getViewState();
var ms = Tracktion.getMixerViewState();

var showing = ev.getProperty('mixerPanelShown') && ms.getProperty('outputsVisible');

if (showing)
{
  ev.setProperty('mixerPanelShown', false);
}
else
{
  ev.setProperty('mixerPanelShown', true);

  ms.setProperty('overviewVisible', false);
  ms.setProperty('smallMetersVisible', false);
  ms.setProperty('inputsVisible', true);
  ms.setProperty('clipsVisible', false);
  ms.setProperty('modifiersVisible', false);
  ms.setProperty('bigMetersVisible', false);
  ms.setProperty('pluginsVisible', true);
  ms.setProperty('outputsVisible', true);
  ms.setProperty('levelsVisible', true);
}

It took me a while to figure out how to import this script and make a macro,but I have it working now with the mixer and clip launcher assigned to different buttons. Is there a reason that this should not be included in the default list or even the default behaviour?

[nowgad]

...

There is a problem with the Arranger function (at least for me) in Waveform 13 latest versions, Win10. When dragging a fragment, the Copy/Move Section does not work. Instead of Copy/Move, the entire fragment is highlighted and nothing happens. On a subsequent reboot, the DAW works fine, but the newly created fragment does not work again.