debug would not load any session. I did launch the session with plugins disabled and it crashed. I had to edit the .ardour file to launch session.
because of the debugging issue, I reinstalled Ardour and LSP and now I get this in the log:
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
that warning is streaming. I removed the Limiter and it stopped. Debug is still not launching any sessions but Ardour is fine now without the limiter.
sadko4u wrote:I also want to ask you about what plugins do you use in your session. I still can not reproduce the problem with both LV2 and VST versions of Limiter.
In that session I'm using LSP compressor and parametric eq. eq10q eq and compressor, and zam compressor and x42 eq.
Currently LSP plugins have AUR packaging, so not everybody knows that project needs donations.
What do you think about adding a dialog window that will provide a link and ask for donations on the UI startup?
I'm thinking about showing the window once per version update. Won't it be annoying?
sadko4u wrote:Currently LSP plugins have AUR packaging, so not everybody knows that project needs donations.
What do you think about adding a dialog window that will provide a link and ask for donations on the UI startup?
I'm thinking about showing the window once per version update. Won't it be annoying?
not at all. Someone requested that the maintainer added that in AUR.
with my issue, no time to mess with audio today but will do like you say tomorrow.
funkmuscle wrote:Someone requested that the maintainer added that in AUR.
Yes, that is true, but I have my doubts about it since it is not customary practice in the AUR. Adding a message to that effect to my PKGBUILDs is not exactly in line with the AUR etiquette. Packages are supposed to be made available in the AUR based on usefulness, while my adding that message sounds like distributing the plugins for advertising purposes. So, yes, I think the best solution is applications providing that functionality themselves – at least as far as Arch is concerned.
funkmuscle wrote:Someone requested that the maintainer added that in AUR.
Yes, that is true, but I have my doubts about it since it is not customary practice in the AUR. Adding a message to that effect to my PKGBUILDs is not exactly in line with the AUR etiquette. Packages are supposed to be made available in the AUR based on usefulness, while my adding that message sounds like distributing the plugins for advertising purposes. So, yes, I think the best solution is applications providing that functionality themselves – at least as far as Arch is concerned.
Maybe then do the same option like ardour does after exporting. And for it not to be annoying you give the option to opt out of it.
funkmuscle wrote:Maybe then do the same option like ardour does after exporting. And for it not to be annoying you give the option to opt out of it.
Of course, showing the dialog on each UI startup is very annoying. I think, it should be shown only once on first startup or version update (up or down).
funkmuscle wrote:debug would not load any session. I did launch the session with plugins disabled and it crashed. I had to edit the .ardour file to launch session.
because of the debugging issue, I reinstalled Ardour and LSP and now I get this in the log:
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
[WARNING]: tempo map was asked for BBT time at frame -240
that warning is streaming. I removed the Limiter and it stopped. Debug is still not launching any sessions but Ardour is fine now without the limiter.
made a snapshot copy of my session and loading the lxvst Limiter I get the above warning. Loading the lv2 Limiter, it freezes Ardour then crashes