I usually avoid a 1.0 release but this is the Waldorf Largo
Unfortunately the patch recall does not seem to work in RNS. I have no idea why. It’s probably the synth, not RNS, but maybe one of those integration issues that could be on either side.
I had a sweet track going this evening and saved it, came back later and loaded it, and the patch had defaulted to the initial sound. Still sounded cool but it wasn’t the patch I programmed.
As a test I created a new RNS song, tweaked a new patch, gave it a name in the Largo interface this time (which showed in the RNS instrument list beside the instrument name), saved the RNS song, created a new song to reset everything, loaded it again, and it’s still reverted to the default patch.
As another test, I programmed a new sound, saved the FXP, moved to another preset, loaded the FXP, and it loaded correctly. This tells me that RNS has the ability then, to recall a preset from a file.
That’s about all I can report here. Hopefully someone can offer some assistance.
It reads like the Waldorf plugin requires some more time to instantiate before it accepts patch data…
So far i have no other theories but this seems both a bug in the plugin as well as that Renoise can use an extra routine to resolve instantiate latency issues.
For now: There might be a way to recover your old settings as they are saved in the song…:
-Open the song in Renoise
-Open the song.xml from the xrns file (rename to zip then unpack) in a text-editor.
-Open another text-editor, either create an instrument instance with Waldorf or just select the one you want to recover the parameters from, then copy the instrument and paste it in the empty text-editor.
-Then find the waldorf instance in your song.xml, and copy the part from the vst plugin name property (above the splits) till the tag and paste this in between the RenoiseInstrument tag lines.
-Now select and copy the whole xml code in the texteditor and paste it back across the instance that you have lost the parameters from or try pasting into a new instrument.
I can’t guarantee it works, but you can try. You can then save your presets or banks to disc so recovering the next time will be a tad easier.
Lets simply write them a friendly mail. I will do so later. James: Could you please do so as well?
Its up the VST devs to fix such issues, not much we can and want to do. Usually it takes some time to get a plugin tested & running an all sequencers out there…
I wrote the following email to (support at waldorf.de):
Hello,
The Largo is a beautiful synth, perhaps one of the best I have heard
as a piece of software. Unfortunately there is a problem with patch
recall in my VST host. I am using a program called Renoise which is a
vertically scrolling tracker with a full VST implementation. I am
using other powerful synths such as the Virus on TC Powercore and
DiscoDSP Discovery with no issue. VST is quite mature by now in this
software and there are thousands of users around the world.
I am using Renoise 2.0 on Windows XP. P4 dual core, 2 gigs RAM. Largo 1.0.
Steps to reproduce problem:
I create a new song in RNS
instance the Largo in a track
from the layer select menu in Largo, ‘init sound’ and program my patch
save the RNS song
create a new RNS song to reset everything
load the song I just saved
result: Largo is using the patch number I started with before ‘init
sound’, but it’s one of the factory sounds - not the one I just
programmed.
Another test I did is loading/saving FXP’s, which works fine. This is
a workaround for me until the problem is fixed.
It’s possible that there may be a timing issue between Largo
instantiating and RNS sending it the patch information. The Largo
interface has been laggy and slow to update on my machine. It also
takes about five seconds to instantiate the first time when I start
Renoise - maybe that’s the copy protection at work.
I hope you can offer some assistance with this issue.
regards
James,
Victoria, Canada
Forgot to say thanks for the patch recover trick vV… that’s a good piece of information - perhaps it could be added to a ‘tips and techniques’ section somewhere?
The help&support will currently do it for now, this is just a nasty hack to circumvent a bug, i hope if the Waldorf developers release an update, this bug is then fixed. (by the way you describe the plugin lagging, sounds like it can use a lot of code optimizations)
I received this response from Waldorf today. Also tried the Largo 1.1 update and the problem remains.
Hi James,
We have another Renoise user with exactly the same problem. Our developer is in contact with the Renoise developer and it seems that the VST integration of Renoise is not perfect. So I think you have to wait for a Renoise update.
All the Best,
Holger
Waldorf Support
Waldorf Music GmbH HRB: Bad Neuenahr-Ahrweiler 20433
Neustrasse 12 USt-ID: DE250453192
D-53498 Waldorf Geschäftsführer: Stefan Stenzel, Kurt Wangard
Well, I haven’t heard anything from them, but let me sort this out. Renoise bug or Waldorf bug, I don’t care as long as it gets fixed. Let me contact them. Thanks for the response James…
Well, i hope they are still being busy with a reply or testing… They are for sure very quick in pointing and judging the cause for the issue.
And that for an issue that only regards their own plugin and none of the many other plugins that run seemlessly well in Renoise.
I’ve since tried the Largo 1.1 update and the issue remains. Here is
what the Renoise lead developer said about it: “Its up to the VST
devs to fix such issues, not much we can and want to do. Usually it
takes some time to get a plugin tested & running on all sequencers out
there…”
If Largo is running well on Ableton, Logic, Cubase etc then it’s fair
for Waldorf to say that the problem is with Renoise. However it’s
also fair to say that the problem is with the Largo, when the Virus
Powercore, the whole Native Instruments suite, Albino, Vstation,
Waldorf Attack, etc all run perfectly in Renoise! It’s an integration
issue…
I hope someone from Waldorf could take a few minutes to load the
software, reproduce the problem, see what can be done to help.
Renoise is a free download: http://www.renoise.com/download/
regards,
James
to which they responded with:
Thank you for your effort. We will investigate this.
Largo patch recall in Renoise is still broken. I haven’t had any issues with Largo recall in other hosts, could the developers please look into this again?
There are a few methods that can be used to to call presets and bank selections. There is a generic way which 99% of them supports (Parameter chunks), but some VST plugins only support one specific way of recalling presets and one of those doesn’t seem supported by Renoise.