11 Mar
2011
11 Mar
'11
6:46 p.m.
You can work around it by using the following magic:
$ rm -rf debian/source
$ sed -i s/1-1/1/ debian/changelog
And then:
$ dpkg-buildpackage -uc -us
gabriel& Jeremy
thanks for the help - the magic workaround worked for building the plugs :)
I'm assuming that everything needs to move to the proper locations
indicated by the file structure in the debian directory
so...
/home/kim/Desktop/downloads/jeremysalwen-So-synth-LV2-e399ee2/debian/so-synth-lv2/usr/lib/lv2/
copies to:
/usr/lib/lv2/
and
/home/kim/Desktop/downloads/jeremysalwen-So-synth-LV2-e399ee2/debian/so-synth-lv2/usr/share/doc/
goes into /usr/share/doc/
which I did
-----------------------------------
next I tested it by
launching Qtractor 0.4.8
creating a track
added the LV2 SO-666 plug
and immediately the app crashed
also, tried with the bass and piano plugs following the same procedure
and the same thing happened
report from syslog:
kim-studio kernel: qtractor[12969]: segfault at 10 ip b366cde0 sp
b22a4f30 error 4 in libsosynth.so[b366c000+3000]
Mar 11 09:41:06 kim-studio kernel: qtractor[12988]: segfault at 10 ip
b34ec220 sp b2122f50 error 4 in libsosynth.so[b34ea000+3000]
Mar 11 09:43:04 kim-studio kernel: qtractor[13013]: segfault at 10 ip
b36ff758 sp b22d5f30 error 4 in libsosynth.so[b36fe000+3000]
11 Mar
11 Mar
10:13 p.m.
New subject: SO-666 crashes Ardour [now SO-666 crashes Qtractor]
On 03/11/2011 05:46 PM, Kim Cascone wrote:
which track type?
apparently there's this issue where qtractor crashes when one adds a
midi instrument lv2 plugin (aka synth) to an audio track (or bus), which
is a mistake to start with--i'm still investigating which fault it is,
either host's or plugin's :/
try adding a midi track and then insert the so-666 plugin to it. it
should work then, as advertised
cheers
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
You can work
around it by using the following magic:
$ rm -rf debian/source
$ sed -i s/1-1/1/ debian/changelog
And then:
$ dpkg-buildpackage -uc -us
gabriel& Jeremy
thanks for the help - the magic workaround worked for building the plugs :)
I'm assuming that everything needs to move to the proper locations
indicated by the file structure in the debian directory
so...
/home/kim/Desktop/downloads/jeremysalwen-So-synth-LV2-e399ee2/debian/so-synth-lv2/usr/lib/lv2/
copies to:
/usr/lib/lv2/
and
/home/kim/Desktop/downloads/jeremysalwen-So-synth-LV2-e399ee2/debian/so-synth-lv2/usr/share/doc/
goes into /usr/share/doc/
which I did
-----------------------------------
next I tested it by
launching Qtractor 0.4.8
creating a track
added the LV2 SO-666 plug
and immediately the app crashed
also, tried with the bass and piano plugs following the same procedure
and the same thing happened
report from syslog:
kim-studio kernel: qtractor[12969]: segfault at 10 ip b366cde0 sp
b22a4f30 error 4 in libsosynth.so[b366c000+3000]
Mar 11 09:41:06 kim-studio kernel: qtractor[12988]: segfault at 10 ip
b34ec220 sp b2122f50 error 4 in libsosynth.so[b34ea000+3000]
Mar 11 09:43:04 kim-studio kernel: qtractor[13013]: segfault at 10 ip
b36ff758 sp b22d5f30 error 4 in libsosynth.so[b36fe000+3000]
12 Mar
12 Mar
12:26 a.m.
New subject: SO-666 crashes Ardour [now SO-666 crashes Qtractor]
On 03/11/2011 09:14 PM, Rui Nuno Capela wrote:
On 03/11/2011 05:46 PM, Kim Cascone wrote:
which track type?
apparently there's this issue where qtractor crashes when one adds a
midi instrument lv2 plugin (aka synth) to an audio track (or bus), which
is a mistake to start with--i'm still investigating which fault it is,
either host's or plugin's :/
apparently again, it's a lv2 host implementation issue :) fixed on svn
trunk today (qtractor 0.4.8.39+)
you can now add midi instrument plugins to audio tracks, hopefully
without crashing the whole show, never mind it serves no real business ;)
hth
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org
You can
work around it by using the following magic:
$ rm -rf debian/source
$ sed -i s/1-1/1/ debian/changelog
And then:
$ dpkg-buildpackage -uc -us
gabriel& Jeremy
thanks for the help - the magic workaround worked for building the plugs :)
I'm assuming that everything needs to move to the proper locations
indicated by the file structure in the debian directory
so...
/home/kim/Desktop/downloads/jeremysalwen-So-synth-LV2-e399ee2/debian/so-synth-lv2/usr/lib/lv2/
copies to:
/usr/lib/lv2/
and
/home/kim/Desktop/downloads/jeremysalwen-So-synth-LV2-e399ee2/debian/so-synth-lv2/usr/share/doc/
goes into /usr/share/doc/
which I did
-----------------------------------
next I tested it by
launching Qtractor 0.4.8
creating a track
added the LV2 SO-666 plug
and immediately the app crashed
also, tried with the bass and piano plugs following the same procedure
and the same thing happened
report from syslog:
kim-studio kernel: qtractor[12969]: segfault at 10 ip b366cde0 sp
b22a4f30 error 4 in libsosynth.so[b366c000+3000]
Mar 11 09:41:06 kim-studio kernel: qtractor[12988]: segfault at 10 ip
b34ec220 sp b2122f50 error 4 in libsosynth.so[b34ea000+3000]
Mar 11 09:43:04 kim-studio kernel: qtractor[13013]: segfault at 10 ip
b36ff758 sp b22d5f30 error 4 in libsosynth.so[b36fe000+3000]
13 Mar
13 Mar
4:33 a.m.
New subject: SO-666 crashes Ardour [now SO-666 crashes Qtractor]
You should only use dpkg-buildpackage if you want to use the .deb file it
creates! If you're using a non-debian based system, just use "make; sudo
make install" to install it without any packaging. (executed from the root
directory of the folder, of course). I'd suspect that if you have
dpkg-buildpackage installed, you should be able to use the .deb file it
creates. Just check in the parent directory. That's a much nicer way of
installing it, and it makes uninstallation and upgrading so much easier.
Jeremy
On Fri, Mar 11, 2011 at 12:46 PM, Kim Cascone <kim(a)anechoicmedia.com> wrote:
You can work around it by using the following magic:
$ rm -rf debian/source
$ sed -i s/1-1/1/ debian/changelog
And then:
$ dpkg-buildpackage -uc -us
gabriel& Jeremy
thanks for the help - the magic workaround worked for building the plugs :)
I'm assuming that everything needs to move to the proper locations
indicated by the file structure in the debian directory
so...
/home/kim/Desktop/downloads/jeremysalwen-So-synth-LV2-e399ee2/debian/so-synth-lv2/usr/lib/lv2/
copies to:
/usr/lib/lv2/
and
/home/kim/Desktop/downloads/jeremysalwen-So-synth-LV2-e399ee2/debian/so-synth-lv2/usr/share/doc/
goes into /usr/share/doc/
which I did
-----------------------------------
next I tested it by
launching Qtractor 0.4.8
creating a track
added the LV2 SO-666 plug
and immediately the app crashed
also, tried with the bass and piano plugs following the same procedure
and the same thing happened
report from syslog:
kim-studio kernel: qtractor[12969]: segfault at 10 ip b366cde0 sp b22a4f30
error 4 in libsosynth.so[b366c000+3000]
Mar 11 09:41:06 kim-studio kernel: qtractor[12988]: segfault at 10 ip
b34ec220 sp b2122f50 error 4 in libsosynth.so[b34ea000+3000]
Mar 11 09:43:04 kim-studio kernel: qtractor[13013]: segfault at 10 ip
b36ff758 sp b22d5f30 error 4 in libsosynth.so[b36fe000+3000]
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
12:45 p.m.
New subject: SO-666 crashes Ardour [now SO-666 crashes Qtractor]
On Saturday, March 12, 2011 09:33:25 pm Jeremy Salwen wrote:
You should only use dpkg-buildpackage if you want to
use
the .deb file it creates! If you're using a non-debian
[snip]
> I'm assuming that everything needs to move to the
> proper locations indicated by the file structure in
> the debian directory
>
> so...
>
>
> /home/kim/Desktop/downloads/jeremysalwen-So-synth-LV2-e
> 399ee2/debian/so-synth-lv2/usr/lib/lv2/
>
> copies to:
>
> /usr/lib/lv2/
[snip]
I didn't understand what you were saying until Jeremy
replied...
The whole point of using `dpkg-buildpackage` is that it'll
create a .deb package to install:
$ dpkg-buildpackage -uc -us
$ sudo dpkg -i ../so-synth-lv2_1_i386.deb
And this will install thing using your system's package
manager. Uninstall with `dpkg -r so-synth-lv2` or `apt-get
remove so-synth-lv2` or use one of the graphical software
package managers supplied with your system.
..of course, this assumes that your on a debian-like OS. If
you're on an RPM-style OS (Fedora, SuSe)... then making the
.deb package was a waste of time. :-/
-gabriel
5006
days inactive
5008
days old
linux-audio-user@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Gabriel M. Beddingfield -
Jeremy Salwen -
Kim Cascone -
Rui Nuno Capela