ringmodwithLFO has a error message

[yugioh47]

ok i've got any error message when i tryed to use ringmodwithLFo i've got the latest one. here's a pic
https://www.dropbox.com/s/ionzbmnpjvag0 ... y.jpg?dl=0
can someone please fix this?

[cyrano]

If it's not too much trouble, could you please report your exact Audacity and Windows version. See the pink box above.

"The latest version" might be very obviously 2.1.2 today. Or it might not. But people will read this post in the future and then it won't be as obvious.

I can't read the error in your screenshot. Maybe you can copy it as text, surrounded with code tags in your message? Code tags are in one of the buttons on top of the window you write your reply in.

That makes is it a whole lot easier to research your error and it will make it more likely that one of the volunteers that answer questions, will find a solution to your problem.

[yugioh47]

If it's not too much trouble, could you please report your exact Audacity and Windows version. See the pink box above.

"The latest version" might be very obviously 2.1.2 today. Or it might not. But people will read this post in the future and then it won't be as obvious.

I can't read the error in your screenshot. Maybe you can copy it as text, surrounded with code tags in your message? Code tags are in one of the buttons on top of the window you write your reply in.

That makes is it a whole lot easier to research your error and it will make it more likely that one of the volunteers that answer questions, will find a solution to your problem.

i'm using 2.1.2 audacity right now.

Here's the error message: could not update effect "ringmod with LFO" WITH: Frequency_(Hz)="440.000000000000" Modulation_depth_(0=none,_1=AM,_2=RM)="0.000000000000" Sawtooth_level="0.000000000000" Sine_level="1.000000000000" Square_level="0.000000000000" Triangle_level="0.000000000000"

[steve]

That's not actually an "error" message, it's just a "message" (as it says at the top of the message).
The message is a bit cryptic, but after you close and restart Audacity you should not be shown that message again, at least not for the ringmodwithLFO effect. It's nothing to worry about

The reason that the message occurs is that the way in which Audacity handles effect settings has been overhauled. Previously there were inconsistencies between how "last used" settings were handled - for most effects, the last used settings were saved for next time, but for other effects the last used settings were lost when Audacity was closed. "Last used" settings should now work correctly for all effects. A side effect of this is that Audacity needs to read the old "last used" settings and migrate them to the new "pluginsettings" file. In some cases the old settings are incompatible (usually because of a fault in how the old settings were stored). When this happens, Audacity produces a message to say that it can't use the old settings. Click the OK button and the effect should appear with its factory default settings.

This does not affect the operation of the effect. It only means that the previous "last used" settings can't be loaded, so the effect will open with its factory default settings.

Once you have used the effect, the settings should be correctly stored in the "pluginsettings" file. You "may" get the message again while in the same Audacity session, but once Audacity has been closed, all settings should be written to their correct (new) settings file, so the effect should not produce the message the next time Audacity is used.

[yugioh47]

That's not actually an "error" message, it's just a "message" (as it says at the top of the message).
The message is a bit cryptic, but after you close and restart Audacity you should not be shown that message again, at least not for the ringmodwithLFO effect. It's nothing to worry about

The reason that the message occurs is that the way in which Audacity handles effect settings has been overhauled. Previously there were inconsistencies between how "last used" settings were handled - for most effects, the last used settings were saved for next time, but for other effects the last used settings were lost when Audacity was closed. "Last used" settings should now work correctly for all effects. A side effect of this is that Audacity needs to read the old "last used" settings and migrate them to the new "pluginsettings" file. In some cases the old settings are incompatible (usually because of a fault in how the old settings were stored). When this happens, Audacity produces a message to say that it can't use the old settings. Click the OK button and the effect should appear with its factory default settings.

This does not affect the operation of the effect. It only means that the previous "last used" settings can't be loaded, so the effect will open with its factory default settings.

Once you have used the effect, the settings should be correctly stored in the "pluginsettings" file. You "may" get the message again while in the same Audacity session, but once Audacity has been closed, all settings should be written to their correct (new) settings file, so the effect should not produce the message the next time Audacity is used.

I've tried it out in audacity 2.1.2 batch files it doesn't update the settings in audacity it only can be viewed with out doing the batch files settings.

[yugioh47]

i'm also using LADSPA 0.4.15. If theres is a update of this plugins. please post thanks

[Gale Andrews]

i'm also using LADSPA 0.4.15. If theres is a update of this plugins. please post thanks

There are updates if you want to compile the plugins yourself from https://github.com/swh/ladspa, fixing any build problems you encounter on Windows, otherwise not.


Gale

[Gale Andrews]

That's not actually an "error" message, it's just a "message" (as it says at the top of the message).
The message is a bit cryptic, but after you close and restart Audacity you should not be shown that message again, at least not for the ringmodwithLFO effect. It's nothing to worry about

The reason that the message occurs is that the way in which Audacity handles effect settings has been overhauled. Previously there were inconsistencies between how "last used" settings were handled - for most effects, the last used settings were saved for next time, but for other effects the last used settings were lost when Audacity was closed. "Last used" settings should now work correctly for all effects. A side effect of this is that Audacity needs to read the old "last used" settings and migrate them to the new "pluginsettings" file. In some cases the old settings are incompatible (usually because of a fault in how the old settings were stored). When this happens, Audacity produces a message to say that it can't use the old settings. Click the OK button and the effect should appear with its factory default settings.

This does not affect the operation of the effect. It only means that the previous "last used" settings can't be loaded, so the effect will open with its factory default settings.

Once you have used the effect, the settings should be correctly stored in the "pluginsettings" file. You "may" get the message again while in the same Audacity session, but once Audacity has been closed, all settings should be written to their correct (new) settings file, so the effect should not produce the message the next time Audacity is used.

I've tried it out in audacity 2.1.2 batch files it doesn't update the settings in audacity it only can be viewed with out doing the batch files settings.

I am not sure what you are saying, but have you tried restarting Audacity?

Are you saying you have a Chain containing the ringmod command but that ringmod command is not recognised when you run the Chain?

If so you can delete the ringmod command in the Chain, then insert ringmod in your Chain and set its parameters using Audacity 2.1.2.


Gale

[yugioh47]

I am not sure what you are saying, but have you tried restarting Audacity?

yes.

Are you saying you have a Chain containing the ringmod command but that ringmod command is not recognised when you run the Chain?

yes. and some of them are that way.

sorry but don't communicate very well.

gale which compiler should i use that is freeware for xml files to *.dll?

[Gale Andrews]

I am not sure what you are saying, but have you tried restarting Audacity?

yes.

Are you saying you have a Chain containing the ringmod command but that ringmod command is not recognised when you run the Chain?

yes. and some of them are that way.

But you can fix that, as I said. Delete the existing command for the effect in Edit Chains. Click "Insert" then add the effect from the list. Click "Edit Parameters" to choose the parameters you want.

which compiler should i use that is freeware for xml files to *.dll?

What are you trying to do?


Gale