Waveform 11 to 13 Project Problem

[timsenpower]

Hi everyone,
I updated from Waveform 11 to 13 but can't open my 11 projects. What's the reason for this? I thought it was only difficult when going from 13 to 11.
Thanks

[Peter Widdicombe]

By "can't open"...
- files can't be found
- loads but sounds different
- loads but plugins not found
- specific error message in Waveform ?

Is this on the same computer ?

I just loaded one from 2018 (Waveform 10?), and other than I had to reassign the VST's, it played as expected.

[pough]

I don't have any problems at all opening WF11 projects in WF Pro 13.5.21 on Windows 10. It warns me that saving the Edit in WF13 will mean that it will no longer be openable in the older version but still loads fine. I do it all the time. Dozens of older Edits.

Can you be more specific about "can't open"? Is it Projects or Edits in the Projects? Is it all of them or only some? Can you create a new one in WF11 that has nothing loaded in it and try opening that one in WF13?

[edrickblade]

Hi everyone,
I updated from Waveform 11 to 13 but can't open my 11 projects. What's the reason for this? I thought it was only difficult when going from 13 to 11.
Thanks

Try opening a backup of that project, it worked for me opening a WF13 project in WF12

[21tones]

I am wondering whether to upgrade from Waveform 11 Pro to 13. I noticed that Peter said above that he had to reassign the VSTs. What I don't want to happen is that 13 won't reproduce the VST settings used in 11. Is that what you meant Peter?
I had this problem going from Tracktion 2 to Waveform 11 ( a much bigger jump I know), but don't want to have to deal with it again.
Interested to hear whether there are problems doing what I want or not.
Thanks

[Peter Widdicombe]

In most cases you don't have to re-assign VST's providing they are all the same and intact. Name/settings/patches have to match up, in which case they should load properly. I may have had some from an earlier version back in the days when 32-bit plugins were supported; so either the VST didn't exist, or had become <PluginName(64)>. SFZ didn't come out with a 64-bit one, so had to replace with another SF2 player. Going from 11 to 13 on the same computer should not be an issue. Plus, they don't get rewritten until you save; and you can have both versions installed. It may ask about converting the file from previousl release if loading in 13; YES will load it but NOT SAVE it until you save (unless maybe if you have auto-save enabled).

Like always, though, do make a backup of projects or directories where you have all your projects to be on the safe side.

[21tones]

Peter
Thanks very much for the information. I still have lots of old 32 bit plugins running under J-Bridge.
I don't think newer versions of many of these were ever produced so that may work?
Thanks again

[Peter Widdicombe]

J-Bridge requires you to have installed the translator. These should work transparently from v.11 to v.13. I think I have an ESQ emulator working (SQ8L) that way. Just tried it - I had "JBridged" it back in 2016.

[21tones]

Thanks Peter - appreciate your help.