Call for testing: DISTRHO plugin ports (Updated)

Unofficial support for the KXStudio Linux distribution and applications.
More info at http://kxstudio.linuxaudio.org/

Moderators: khz, MattKingUSA

User avatar
sysrqer
Established Member
Posts: 1823
Joined: Thu Nov 14, 2013 11:47 pm
Contact:

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby sysrqer » Mon Jun 23, 2014 4:35 am

I just tried them all in renoise3 (vst versions) and these are the notes I took:

artican: zipper noise when moving the filter? Can be heard when moving the knob very quickly, seems to be present when moving very slowly but less pronounced.
cabbage bandfilter: kills all sound, no amount of playing with the controls seems to allow any audio to play play through it.
cabbage convolution reverb: kills all sound, no amount of playing with the controls seems to allow any audio to play play through it.
cabbage doppler: kills all sound, no amount of playing with the controls seems to allow any audio to play play through it.
cabbage doppler spin: kills all sound, no amount of playing with the controls seems to allow any audio to play play through it.
cabbage envelope follower: LEDs on the left don't seem to work but when clicking on them they do light up, not sure what they do.
cabbage filter lfo: I clicked on the boxes to the right of the first 4 dials and after that they showed no text at all on those boxes. I have no idea what the green box does.
cabbage flanger: gives nothing but noise with some flanger on top, none of the originnal sound at all.
cabbage frequency shifter: kills all sound, no amount of playing with the controls seems to allow any audio to play play through it.
cabbage HRTF3D: I have no idea what this does, no labels and mutes all sound on the track.
cabbage liveSndwarp: I have no idea what this does, no labels and mutes all sound on the track.
cabbage pvsBandr: crashed renoise entirely.
cabbage pvsFreeze: gui produced some strage artifacts, almost like ghosting
cabbage reverse: kills all sound, no amount of playing with the controls seems to allow any audio to play play through it.
cabbage stutter filter: crashed renoise completely when trying to bring up the gui.
distotionshaper: this crashed renoise the first time I loaded it but couldn't replicate the crash unfortunately.

I briefly tried klangfalter in bitwig, I mentioned to you in the irc the issues I was having with the existing version and this does seem to be an improvement but I think more testing is needed.


cabbage phaser: one of the nicest phasers I've come across on linux!


With the cabbage plugins I don't know if it is the gtk theme I am using (numix arch blue) but the drop downs are black and you can't see the options they contain until you move the mouse over them. I have to say that they do seem to be more stable than they were before though.

User avatar
sysrqer
Established Member
Posts: 1823
Joined: Thu Nov 14, 2013 11:47 pm
Contact:

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby sysrqer » Mon Jun 23, 2014 12:48 pm

I did try all the others as well but just didn't find any problems at all.

glowrak guy
Established Member
Posts: 1361
Joined: Sat Jun 21, 2014 8:37 pm

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby glowrak guy » Tue Jun 24, 2014 11:14 pm

The drow plugins worked fine in latest bitwig, reverb, tremolo, flanger,
I liked the sound, could adjust and drag the nice gui's about freely.
They were in the 'new in repository' section last night.
Cheers

antiesen
Established Member
Posts: 149
Joined: Sat Aug 27, 2011 3:36 pm

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby antiesen » Wed Jun 25, 2014 9:22 am

Testing on opensuse 64, vst - mainly in tracktion:

drowaudio - distortion shaper: crashes tracktion, crashes qtractor at the first time, but then works

klangfalter: don´t showing the browser in tracktion, the plugin-window must be enlarged manually, but then working.

Tal Noisemaker: hey the internal save/load presets work again! Thank you

I know these are not in the challange but new in distrho: obxd an dexed seem to work in tracktion.
(For them who want to try - delete previous plugin versions, in tracktion: clear list and then scan new)


Greetings
This was made to end all partys - Einstürzende Neubauten 1985

stanlea
Established Member
Posts: 595
Joined: Wed Apr 25, 2012 9:49 pm

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby stanlea » Wed Jun 25, 2014 1:18 pm

Here's Carla's log after distorsion shaper crashing it :
(Jessie 64 bits +KX repos)

Code: Select all

Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Abandon

stanlea
Established Member
Posts: 595
Joined: Wed Apr 25, 2012 9:49 pm

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby stanlea » Wed Jun 25, 2014 2:38 pm

Code: Select all

studio@studio:~$ gdb --args python3 /usr/share/carla/carla --with-libprefix=/usrGNU gdb (GDB) 7.6.2 (Debian 7.6.2-1.1+b1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/python3.4...(no debugging symbols found)...done.
(gdb) quit

stanlea
Established Member
Posts: 595
Joined: Wed Apr 25, 2012 9:49 pm

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby stanlea » Wed Jun 25, 2014 7:09 pm

falkTX wrote:I guess you never debugged a program crash before?

:? it was 20 years ago...



you need to enter "r" or "run", and let the app crash.

Code: Select all

Starting program: /usr/bin/python3 /usr/share/carla/carla --with-libprefix=/usr
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Using "carla" theme
Carla 1.9.4 (2.0-beta2) started, status:
  binary dir:    /usr/lib/carla
  resources dir: /usr/share/carla/resources
libjack.so.0 loaded sucessfully!
[New Thread 0x7fffe5941700 (LWP 19444)]
[New Thread 0x7fffe5140700 (LWP 19445)]
[New Thread 0x7fffef083700 (LWP 19446)]
[New Thread 0x7fffef002700 (LWP 19447)]
[New Thread 0x7fffe4895700 (LWP 19448)]
[New Thread 0x7fffd3188700 (LWP 19449)]
[New Thread 0x7fffd2987700 (LWP 19450)]
[New Thread 0x7fffe41e8700 (LWP 19451)]
[New Thread 0x7fffd15dc700 (LWP 19452)]
Will use LV2 X11 UI
[New Thread 0x7fffe4167700 (LWP 19453)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5454eb0 in QWidgetPrivate::getOpaqueChildren() const ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4



then type "bt" or "backtrace" to get some crash info.
(gdb) bt

Code: Select all

#0  0x00007ffff5454eb0 in QWidgetPrivate::getOpaqueChildren() const ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#1  0x00007ffff5454f50 in QWidgetPrivate::getOpaqueChildren() const ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#2  0x00007ffff5454f50 in QWidgetPrivate::getOpaqueChildren() const ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#3  0x00007ffff5454f50 in QWidgetPrivate::getOpaqueChildren() const ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#4  0x00007ffff5454f50 in QWidgetPrivate::getOpaqueChildren() const ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#5  0x00007ffff5454f50 in QWidgetPrivate::getOpaqueChildren() const ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#6  0x00007ffff5454f50 in QWidgetPrivate::getOpaqueChildren() const ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x00007ffff5454f50 in QWidgetPrivate::getOpaqueChildren() const ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#8  0x00007ffff5455020 in QWidgetPrivate::subtractOpaqueChildren(QRegion&, QRect const&) const () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#9  0x00007ffff545fcb8 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#10 0x00007ffff5623c72 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#11 0x00007ffff5455460 in QWidgetPrivate::syncBackingStore() ()
---Type <return> to continue, or q <return> to quit---
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#12 0x00007ffff54658e0 in QWidget::event(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#13 0x00007ffff5823d63 in QMainWindow::event(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#14 0x00007ffff62c37eb in ?? ()
   from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-34m-x86_64-linux-gnu.so
#15 0x00007ffff5415c0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#16 0x00007ffff541c360 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#17 0x00007ffff6448866 in ?? ()
   from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-34m-x86_64-linux-gnu.so
#18 0x00007ffff4ee77fd in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#19 0x00007ffff56256ae in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#20 0x00007ffff5455a95 in QWidget::repaint(QRect const&) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#21 0x00007ffff5455ad3 in QWidget::repaint() ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#22 0x00007ffff57cc42d in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
---Type <return> to continue, or q <return> to quit---
#23 0x00007ffff57cc544 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#24 0x00007ffff588395a in QToolButton::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#25 0x00007ffff54656c8 in QWidget::event(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#26 0x00007ffff5415c0c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#27 0x00007ffff541c4ae in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#28 0x00007ffff6448866 in ?? ()
   from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-34m-x86_64-linux-gnu.so
#29 0x00007ffff4ee77fd in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#30 0x00007ffff541bb6f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#31 0x00007ffff548e66e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#32 0x00007ffff548d022 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#33 0x00007ffff54b5212 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#34 0x00007ffff4136e04 in g_main_context_dispatch ()
---Type <return> to continue, or q <return> to quit---
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#35 0x00007ffff4137048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007ffff41370ec in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007ffff4f14f8d in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#38 0x00007ffff54b52c6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#39 0x00007ffff4ee6481 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#40 0x00007ffff4ee6795 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#41 0x00007ffff4eebef7 in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#42 0x00007ffff64046c0 in ?? ()
   from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-34m-x86_64-linux-gnu.so
#43 0x00000000004aaa1a in PyEval_EvalFrameEx ()
#44 0x00000000004aec9f in PyEval_EvalFrameEx ()
#45 0x00000000004a33d2 in ?? ()
#46 0x000000000047097e in PyRun_FileExFlags ()
#47 0x0000000000470d6f in PyRun_SimpleFileExFlags ()
#48 0x00000000005fdb93 in Py_Main ()
#49 0x0000000000484dc1 in main ()




StudioDave
Established Member
Posts: 753
Joined: Sat Nov 01, 2008 1:12 pm

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby StudioDave » Sat Jun 28, 2014 5:10 pm

Vex seems to have regressed. The sine wave sounds very distorted, as does every waveform selection. I've adjusted various parameters, no joy, the sound is borked. Is it so for anyone else ?

My build, on Fedora 19, 64-bit.

Best,

dp

distrozapper
Established Member
Posts: 17
Joined: Thu Oct 04, 2012 9:34 pm

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby distrozapper » Sun Jun 29, 2014 10:54 am

StudioDave wrote:Vex seems to have regressed. The sine wave sounds very distorted, as does every waveform selection. I've adjusted various parameters, no joy, the sound is borked. Is it so for anyone else ?

My build, on Fedora 19, 64-bit.

Best,

dp


I cannot quite confirm Vex (LV2) sounding distorted, but I can notice Vex's sine (and all other sounds too) produce a sharp click at note-on.
This click vanishes reproducibly here as soon as Vex's Amp Env Attack knob is moved and returned back to zero level.
It feels like the Amp Env ADSR isn't initialized well on a freshly started Vex lv2 instance.
In contrast, carla's internal VexSynth plugin doesn't produce such clicks.
(linuxmint 13 cinnamon/ubuntu 12.04 64bit and debian 7 KDE 64bit, latest kxstudio repo updates applied 06/29/14, Intel HDA and M-Audio USB, carla-git)

StudioDave
Established Member
Posts: 753
Joined: Sat Nov 01, 2008 1:12 pm

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby StudioDave » Sun Jun 29, 2014 12:58 pm

falkTX wrote:
StudioDave wrote:Vex seems to have regressed. The sine wave sounds very distorted, as does every waveform selection. I've adjusted various parameters, no joy, the sound is borked. Is it so for anyone else ?

What synth are you referring to? Vex?


Specifically the Vex VST plugin.

Best,

dp

User avatar
GMaq
Established Member
Posts: 1398
Joined: Fri Sep 25, 2009 1:42 pm

Re: Call for testing: DISTRHO plugin ports (Updated)

Postby GMaq » Tue Jul 15, 2014 11:08 pm

Hi there!

Not sure if you'll want to know this or not but I've been using EnergyXT 2.7 a lot lately and the DISTRHO 3BandEQ, 3BandSplitter and Nekobi VST's do not work, unfortunately running EnXT in a term doesn't say anything meaningful. Not sure if this is an easy fix or not but it would be great to have them working if possible..

Just thought I'd mention it..


Return to “KXStudio Discussion”

Who is online

Users browsing this forum: No registered users and 9 guests