Hey,
in the past I used samplv1 with Ardour and everything worked fine. I didn't use it for the last couple of months.
Today I tried to use samplv1 again and after Ardour opens the GUI of samplv1 it crashes.
I would appreciate any advice!
samplv1 0.8 lv2 plugin crashes in Ardour 4.7
Moderators: MattKingUSA, khz
-
- Established Member
- Posts: 4
- Joined: Sat Nov 19, 2016 12:16 am
samplv1 0.8 lv2 plugin crashes in Ardour 4.7
Last edited by ground cover on Sat Nov 19, 2016 4:58 pm, edited 1 time in total.
- rncbc
- Established Member
- Posts: 1068
- Joined: Mon Apr 19, 2010 12:20 pm
- Has thanked: 45 times
- Been thanked: 270 times
- Contact:
Re: samplv1 0.8 vl2 plugin crashes in Ardour 4.7
check if you're really using samplv1.lv2 v0.8.0 at all... check ardour4 session startup messages...
maybe there's some left-overs from older samplv1 versions... maybe you have duplicate installs...
check where it's actually installed:
assuming it's being installed under /usr, check the install dates on /usr/lib/lv2/samplv1.lv2/* and /usr/lib/libsamplv1.so*, whether they match.
if you have other installs over somewhere else, get rid of them.
must tell that samplv1 v0.8.0 works here without any issues, but i'm testing it under ardour5.4 though.
byee
maybe there's some left-overs from older samplv1 versions... maybe you have duplicate installs...
check where it's actually installed:
Code: Select all
lv2info http://samplv1.sourceforge.net/lv2 | grep Binary:
if you have other installs over somewhere else, get rid of them.
must tell that samplv1 v0.8.0 works here without any issues, but i'm testing it under ardour5.4 though.
byee
-
- Established Member
- Posts: 4
- Joined: Sat Nov 19, 2016 12:16 am
Re: samplv1 0.8 vl2 plugin crashes in Ardour 4.7
I removed samplv1 completely from my system so that lv2info didn't find it anymore and then I did a fresh install but samplv1 keeps crashing.
I am using samplv1
Also, I have to correct myself: samplv1 doesn't crash instantly after Ardour opens up the GUI but rather after I click any button on the GUI. So I can't load a sample because then it crashes. After clicking a button I get the following mesages in the terminal:
I am using samplv1
from http://download.sourceforge.net/samplv1 ... 8.0.tar.gzVersion: 0.8.0
Build: Nov 18 2016 21:17 +0100
Also, I have to correct myself: samplv1 doesn't crash instantly after Ardour opens up the GUI but rather after I click any button on the GUI. So I can't load a sample because then it crashes. After clicking a button I get the following mesages in the terminal:
The standalone samplv1_jack doesn't crash. There are no suspicious Ardour startup messages.(ardour-4.7.0:11540): GLib-GObject-WARNING **: cannot register existing type 'GdkWindow'
(ardour-4.7.0:11540): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
(ardour-4.7.0:11540): Gdk-CRITICAL **: gdk_window_ensure_native: assertion 'GDK_IS_WINDOW (window)' failed
-
- Established Member
- Posts: 4
- Joined: Sat Nov 19, 2016 12:16 am
Re: samplv1 0.8 lv2 plugin crashes in Ardour 4.7
Just tried 0.7.5 and 0.7.4 out. Both do crash.can you try with previous leases like v0.7.6 , or even older v0.7.5 ?
Also I just installed Ardour 5 and samplv1 (the old and the new version) also crashed there.otoh. what's stopping you to upgrade to ardour5 ?
- rncbc
- Established Member
- Posts: 1068
- Joined: Mon Apr 19, 2010 12:20 pm
- Has thanked: 45 times
- Been thanked: 270 times
- Contact:
Re: samplv1 0.8 lv2 plugin crashes in Ardour 4.7
so something went terribly wrong since last time your worked with samplv1_lv2, that's for sure.
get back to the v0.8.0 install alright. make sure you first uninstall and remove all traces of those test installations you've made.
test again with a new session from scratch, for instance, with only one midi track with samplv1 as sole instrument.
you can also go the hard way: build samplv1 for debug (./configure --enable-debug --prefix=/usr ... && make install); follow ardour debugging instructions to get a stacktrace upon the crash occurence, starting by launching it from the console as:
run and dump the backtrace when it segfaults:
be patient. be prepared to make detailed bug reports, on your findings.
let me also advise you that this forum is not the place for just that
one other hint: while on the samplv1_jack, please switch "Configure... > Options > Custome style theme" away from "(default)" and most importantly, from "Gtk+" or "gtk2", quit and try again the lv2 plugin form on the ardour front.
cheers
get back to the v0.8.0 install alright. make sure you first uninstall and remove all traces of those test installations you've made.
test again with a new session from scratch, for instance, with only one midi track with samplv1 as sole instrument.
you can also go the hard way: build samplv1 for debug (./configure --enable-debug --prefix=/usr ... && make install); follow ardour debugging instructions to get a stacktrace upon the crash occurence, starting by launching it from the console as:
Code: Select all
ardour5 -g
(gdb) run
Code: Select all
(gdb) thread apply all bt
let me also advise you that this forum is not the place for just that
one other hint: while on the samplv1_jack, please switch "Configure... > Options > Custome style theme" away from "(default)" and most importantly, from "Gtk+" or "gtk2", quit and try again the lv2 plugin form on the ardour front.
cheers
-
- Established Member
- Posts: 4
- Joined: Sat Nov 19, 2016 12:16 am
- rncbc
- Established Member
- Posts: 1068
- Joined: Mon Apr 19, 2010 12:20 pm
- Has thanked: 45 times
- Been thanked: 270 times
- Contact:
Re: samplv1 0.8 lv2 plugin crashes in Ardour 4.7
no need for further investigation: it's an old and known issue and oneground cover wrote:Ok, this is definitely a bug.
I created an issue: https://github.com/rncbc/samplv1/issues/4
"When trying to load a sample in the lv2 samplv1 plugin the GUI crashes.
After unchecking "Use desktop environment native dialogs" it doesn't
crash anymore.
This issue applies to 0.8.0, 0.7.5 and 0.7.4. I didn't tried this with
other versions.
I am using Gnome shell.
I could create a gdb dump if you want."
of the reasons the "use desktop environment native dialogs" is there for
mitigation.
ps. that option and also the "custom style theme", mentioned before, (not using "gtk2" even if it's default), are indeed day savers, especially when under a gtk+ based environment (eg. gnome, xfce, etc.).
cheers