Development update: 6.0-rc1 tagged

Which OS is that, and which CPU architecture?

I have done a quick check of 64bit nightlies, and it’s included in all of them.

Ubuntu 18.04
Linux 4.15.0-96-lowlatency #97-Ubuntu SMP PREEMPT Wed Apr 1 04:10:58 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

I compile Ardour locally, git pull is up to date.

Maybe you don’t have all the compile-time dependencies? https://libwebsockets.org/ in particular.
Compare to the nightly build and config log, line 80: Checking for 'libwebsockets' >= 2.0.0.

1 Like

Thank you, that fixed it.

This makes me wonder how hard it would to make it so that various components of Ardour could compile to both native code as well as web assembly. Would be wild if the native UI and browser control UI were built from the same code source.

The editor is unlikely to ever be able to run inside a web-browser. Web-tech is perhaps 10-20 years behind in being able to manage the complexity for Ardour’s UI.

GTK+3’s Broadway backend offers means to display a native UI in a browser, but it’s not useful in this case either.

As for other components: The big issues will be plugins. Apart from a few FAUST ones, you won’t find anything. Certainly not any professional DSP. Last but not least, you cannot get fixed latency I/O, recording overdubs likely won’t work. Buffered Disk I/O for hundreds of tracks likewise won’t fly, and with browsers adding more and more sandboxing it’s also unlikely to get better.

You can make cool stuff with webasm, HTML & JS, and certainly awesome basic sequencers. But nothing even close to the 1000+ audio tracks realtime FX processing that modern DAWs are capable of.

I am trying this in a nightly Linux 64bit demo and all I get is 404
This was with Ardour 6.0.rc1.13 Optimized as well as with rc1.2

My webb browser connects and Ardour enables the websocket but I have not managed to get anything useful.
In my console I can see
[2020/04/20 23:27:28:4737] NOTICE: Creating Vhost ‘default’ port 3818, 1 protocols, IPv6 off

This is with a session I did create a while back.

Do I have to create a new session to get websocket features working ?

Oops. Looks like the web-socket frontend (html/js) was not included with Linux and Mac binaries. Fixed just now (6.0-rc1-32).

Ok. Thanks.
I Will test again tomorrow.

Back with a fresh Ardour 6.0.rc1.34
Still only getting 404
Have refreshed Browser cache and there is no change AFAI Can See

Do I have to use a Debug version or Full version or whats the secret ?

hmm

Ok, I saw build 41 might fix this…
Let’s hope

Hi, so I gave Ardour-6.0-rc1 a try.
One thing I noticed so far is that GUI elements are smaller.

Ardour 5.12 screenshot:

Ardour 6.0-rc1:

Both are set to 100% gui scaling on a 1920x1080 display.
Is it supposed to be like this?

Edit: Found another difference now that I look at the screenshots again. This is the same project opened. But the in Ardour 6.0-rc1 the recorded tracks are displayed as if they were louder than in Ardour 5.12.
Is the volume visualized normalized now?

The default waveform scale in Ardour6 is Logarithmic. (you can change it back to Linear in Preferences > Appearance > Editor

As for the GUI size. Something is definitely wrong there. Neither A5 nor A6 look like I’d expect. Although Ardour6 layout significantly better. I don’t have an explanation for that. Perhaps translation?

For comparison:

Most notable difference is the vari-speed slider’s size.

Okay thanks.

Yes I see.
(However I have to say that I like the sizes of texts, menus and buttons of Ardour 5 on my system. Most of it is tiny now with Ardour 6.0-rc1.)
Do you have any idea how to find out what is wrong with it on my side?

I’m using Manjaro with KDE Plasma.
Ardour is self compiled from git tag 6.0-rc1.

Edit:
Just for testing, I did reset my ardour6 config (deleted ~/.config/ardour6). But this didn’t change anything.
Even the starting window has tiny font compared to Ardour 5.12 and other programs.

Edit 2:

Did want to try that. But I can’t disable them. I unchecked the ‘use translations’ checkbox in Ardours settings and restarted Ardour. However, it is still in german. (Probably another bug?)

It seems that the web sockets control surface requires a websockets library that is compiled with the LWS_WITH_EXTERNAL_POLL build option. Unfortunately, this build option has been set to OFF by default by the developers, and even has a “not recommended” note on it.
As a result, this option is not, or will not, be available on some platforms and Ardour will not be able to provide its web interface on these platforms.
This is the case with Fedora and libwebsockets version 3.2.1, YMMV.

hello everyone I wanted to report to the ardor team that the Ardor-6.0.rc1.44-dbg-x86_64-gcc5.run version crashes when it tries to import audio files. As an operating system I am using 64 bit debian buster. The previous version N.34 instead works well

Bug reports to tracker.ardour.org (in this case, preferably with a backtrace as described at http://ardour.org/debugging_ardour ; if no backtrace, then a very detailed recipe for the bug)

With open-stage-control v1 around corner I’m updating it for v6: (work in progress)

3 Likes

I’ve just installed rc1.82 and the web interface still isn’t working for me, either (I’ve tried a couple of previous iterations). I’m on UbuntuStudio 18.04. It would be a hugely useful feature, so hopefully it will be sorted at some point. ETA: I figured it out: I needed to tick websockets in the list of control surfaces. Doh!

Is there a setting somewhere so that increasing the transport speed doesn’t change the pitch of midi, but only speeds it up? I’m going through some midi captures of writing/noodling in Pianoteq and it would be nice to skip through them quicker than realtime (I have a lot to get through) and the increase in pitch makes it harder to do.

There is no such setting.

When vari-speeding pitch is now unconditionally kept in sync for audio and MIDI.
Vari-speed playback is now done by resampling the I/O. It’s not something that can be disabled.

PS.
There is a plugin https://github.com/x42/repitch.lv2 (binaries are avilable from https://x42-plugins.com/x42/x42-repitch) that can counter-act the pitch-changes that are introduced by vari-speeding. Add it to the master-bus for example.