Activity for scott
-
scott posted a comment on ticket #24
This plugin is having the same error as the v1 plugins I filed about a month ago which got fixed for the same issue. The plugin needs to be self-contained otherwise it will take down the daw. The status now for v1 plugins is that its xstatic branch has been merged with the master so here is no longer an issue. https://sourceforge.net/p/samplv1/tickets/15/ The reason why ardour doesn't use plugin crash-protection is explained over here, -- the same thread is used as the plugin (further explains why...
-
both plugin and standalone run with this compile, thanks for providing a fix for this.. it's been several months since these plugins last worked on this system for ardour and you're helping other users who may be in the same boat.. (pp receipt because you took the time in fixing this :)) good times ahead for opensource :)
-
an interesting undertaking thanks.. I am able to install .deb files directly from those kxstudio resources -- however I'd also like to be able to compile from the source but if you may want to check on where it is failing I can provide more detail upon further inspection -- because here I have all dependencies, the ./configure fails after autoconf with something related to pkg_config -- it seems as though there's a problem with the macro definition relating to aclocal.. thanks for getting back to...
-
an interesting undertaking thanks.. I am able to install .deb files directly from those kxstudio resources -- however I'd also like to be able to compile from the source but if you may want to check on where it is failing I can provide more detail upon further inspection -- because here I have all dependencies, the ./configure fails after autoconf with something related to pkg_config -- it seems as though there's a problem with the macro definition relating to aclocal.. thanks for getting back to...
-
an interesting undertaking thanks.. I am able to install .deb files directly from those kxstudio resources -- however I'd also like to be able to compile from the source but if you may want to check on where it is failing I can provide more detail upon further inspection -- because here I have all dependencies, the ./configure fails after autoconf with something related to pkg_config -- it seems as though there's a problem with the macro definition relating to aclocal.. thanks for getting back to...
-
wouldn't know what to recommend and hope whichever side would ultimately fix the missing piece needed, I am not a developer and just relaying the above message. thanks
-
wouldn't know what to recommend and hope whichever side would ultimately fix the missing piece needed, I am not a developer and just relaying the message.
-
-
Nobody should be coming on here and start pointing fingers, it's not the purpose of bugtrackers. Users and developers can collaborate effectively when there are no distractions. Information gets posted and users need to respect decisions developers take to improve their project. thanks
-
I was looking for extra help on understanding how recompiling ardour would fix working with your plugin and I was given some information as to why this may not work as troubling as it may sound -- but I am posting this for information for other users who are in the same boat as I am for understanding why some plugins do not work and why ardour will not fix it. The ardour staff wrote up a new explanation on why plugins do not work and why they will not bother to fix it -- it is more so going with...
-
it would be nice if devs can work together for a common goal because there's just clustering on half-baked solutions when devs start going their own way like this. I'm not pointing the finger at anyone, but just a user perspective -- I mean maybe if there was some kind of Linux-audio alliance community or something you know.. anyways I think I'm going to put a close on this report and I fully appreciate your feedback for this. thanks.
-
it would be nice if devs can work together for a common goal because there's just clustering on half-baked solutions when devs start going their own way like this. I'm not pointing the finger at anyone, but just a user perspective -- I mean maybe if there was some kind of Linux-audio alliance community or something you know.. anyways I think I'm going to put a close on this report and I fully appreciate your feedback on this..
-
it would be nice if devs can work together for a common goal because there's just clustering on half-baked solutions when devs start going their own way like this. I'm not pointing the finger at anyone, but just a user perspective -- I mean maybe if there was some kind of Linux-audio alliance community or something you know.. anyways I think I'm going to put a close on this report and I fully appreciate your timely feedback on this..
-
actually the calf plugins(0.90.1-2) do work on Ardour6 beta.. they got their act together and got things working like they should, but you on the other hand didn't. ;-) lol thanks I thinked I learned something from here and the ardour forums good luck with the plugin, but I'm letting plugin authors know about Ardour6... currently it is like in mix-stage as ardour6 is still in beta and not officially released -- when it becomes released expect a little more traffic for reporting this issue. lol
-
Capela, in case you didn't know I am using Ardour6 the last many months .. https://discourse.ardour.org/t/samplv1-users-does-it-work-for-you/101617 the above thread was asked last week and is something the ardour developers are not going to fix because it is not regarded as a bug on their side. It is rather a new paradigm going into Ardour6 that upstream plugins now need to be more self-contained, https://tracker.ardour.org/view.php?id=7291 "Known issue and won't fix. Arodur will drop support for...
-
ardour's response to this is pointing the finger to libraries that enable plugins to see each other and that they won't fix it and instead let plugin authors to remedy this. Your plugin does not work with the latest ardour builds, so just letting you know that more users are likely to face the same. The reference to the drumkv1 workaround was an example reference pointed by ardour developers (back on a post that I also tried with your plugin). Possibly with the right manifest your plugin works, but...
-
ardour's response to this is pointing the finger to libraries that enable plugins to see each other and that they won't fix it and instead let plugin authors to remedy this. Your plugin does not work with the latest ardour builds, so just letting you know that more users are likely to face the same. The reference to the drumkv1 workaround was an example reference pointed by ardour developers (back on a post that I also tried with your plugin). Possibly with the right manifest your plugin works, but...
-
I reported on the thread of ardour's tracker, a similar issue like this has been occuring since there was some change with one of the libraries.. Are you familiar with this issue-->> "the line where it reads (for instance, in drumkv1.ttl): lv2ui:ui drumkv1_lv2:ui, drumkv1_lv2:ui_x11, drumkv1_lv2:ui_external ; just remove the "drumkv1_lv2:ui, " particle so that line reads like this, thereafter: lv2ui:ui drumkv1_lv2:ui_x11, drumkv1_lv2:ui_external ;" from https://www.rncbc.org/drupal/node/1918#ardour...
-
yes, it does load in qtractor... I will contact the ardour folks thanks -- Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: https://tutanota.com 6 Sep 2019, 15:36 by rncbc@users.sourceforge.net: which lv2 host is that? if ardour5.12 then you're busted ;) ie. the ardour build is way too old for the new matter at hand. try loading samplv1 under jalv or qtractor, and if they work alright please do file a complaint to ardour.org for making it a build that includes a more recent compliance...
-
samplev1 exits with undefined symbol
1