Waves Grand Rhapsody not loading

cdv_gabriel · March 3, 2023, 9:57pm

As I mentioned in another thread, I have a problem with Waves Grand Rhapsody Piano, the infamous 13002 error.

After some debug, I think the problem happens when Cantabile loads a preset bank for the plugin.

I have exported a bank and saved it to disk. Then I quit Cantabile and start from scratch with an empty song. I load Grand Rhapsody and it loads ok. Then I try to import the saved bank: I see that the plugin is starting loading samples and at the same time this dialog box appears:

However, after closing the dialog box, the presets are loaded correctly. I attach here a log of this session as log_norack.txt.

The trouble starts when I place Grand Rhapsody in a linked rack, create some rack states referring to the programs of the Cantabile bank and quit Cantabile. When I start Cantabile and load the linked rack, Grand Rhapsody is not correctly loaded.

Looking into the log file, I find

00019180 1191 [01292:2]: VST3- WaveShell1-VST3 14.0_x64 (#10) - Audio bus counts: 1 in 1 out
00019205 25 ! [01292:0]: Failed to load plugin ‘Grand Rhapsody Piano Stereo 2’
System.InvalidOperationException: Failed to load data because it was in the incorrect format (error 13002)
at Cantabile.Core.InteropObject.SetByteArray(Int32 id, Byte data)
at Cantabile.Core.PluginHost.LoadBank(Byte data)
at Cantabile.Racks.Plugin.LoadPlugin()
00019209 4 [01292:2]: VST3- WaveShell1-VST3 14.0_x64 (#10) - Closing…
00019227 18 [01292:2]: Unloading VST-MA module 00000000344FFB00
00019227 0 [01292:2]: Last reference released, unloading shared library
00019238 11 [01292:2]: VST3- WaveShell1-VST3 14.0_x64 (#10) - Closed.

I suspect this happens because Cantabile tries to load the bank and gets the 13002 error, thus stopping to load the plugin. Outside a rack, as I previously mentioned, I get the dialog box and I can close it. Inside the rack, the error prevents the plugin to load at all. I attach the corresponding log file as log_insiderack.txt.

@brad could you give it a look, if you have time?

Gabriel

P.S. log files are into the log.zip zipfile

log.zip (16.5 KB)

brad · March 4, 2023, 12:12am

As best I can tell this is a bug in the waves plugin. This used to be an issue in older versions of waves VST3 plugins but I thought it had since been rectified.

The issue is basically that the plugin refuses to reload the data it previously saved. For a while I thought it was a bug in Cantabile and even put in checksum checks to ensure the data it saved was identical to the data Cantabile passed back and it all checked out ok… but the plugin failed to reload. I reported this to Waves at the time, and they acknowledged the issue and said it would be fixed in a subsequent build.

But… that was all sometime ago and it looks like you’re running a fairly recent version.

Some questions:

Does this issue only happen in Cantabile - does the plugin save/restore in other hosts correctly?
Does changing the plugin preset model have any effect?
Is it just the Grand Rhapsody Piano plugin that has this issue - do other waves plugins work fine?

Let me know about the above, but I suspect I’ll need to work with Waves to get this sorted. (I’ve contacted Waves about it).

Anyone else seeing similar issues with this plugin?

Brad

cdv_gabriel · March 4, 2023, 6:56am

Hi @brad,

thank you for you prompt answer!

I have loaded Grand Rhapsody in a new song, changed the preset model to “Use plugin…”, saved the song and reloaded. Grand Rhapsody is not loaded…so it does not depend on that, it seems.

According to your suggestion, I have tested Grand Rhapsody in Cakewalk.

First, I have created a new project, inserted an Instrument track with the plugin and saved a preset within the project itself. Then I closed Cakewalk and restarted. Loding the project, my preset was recognized and loaded, but with “*” in the name, as if I had modified it (which was not the case).

Then I saved the preset to a separate file, using the VST3 menu. When I try to load the preset again, that’s what I get

So I suspect you’re right. There must be some problem with the plugin itself.

Gabriel

dsteinschneider · March 4, 2023, 3:06pm

I got a different error

waves_grand_rhapsody_error_pianoteq_not_found

cdv_gabriel · March 4, 2023, 5:14pm

Gabriel

dsteinschneider · March 4, 2023, 7:34pm

I almost bought Grand Rhapsody last month, I missed by a day being able to apply a coupon to their $25 offer so it would be been around $15. I use a bunch of Waves plugins for recording but don’t have any of their instrument VST’s.

cpaolo · March 4, 2023, 8:02pm

Tried with VST2, different error this time

cdv_gabriel · March 5, 2023, 8:44pm

Hi @cpaolo!
Your message made me realize that there is no vst2 version on my system!
I wonder where it is located (if present)! Cantabile can’t find it in my usual plugin locations (and I have listed a few in options!).
Gabriel

cpaolo · March 6, 2023, 12:46am

Funny guys at Waves! They put their VST2s in %ProgramFiles%\VSTPlugIns.

cpaolo · March 6, 2023, 6:02pm

Had to scan the entire C: to find them. After that, I have a “READ B4 install.txt” in my “waves central” storage folder.

cdv_gabriel · March 8, 2023, 7:57pm

Hi @cpaolo,

I could not find them so I searched the net and it seems that, starting from Waves 12, they only support vst3. My version is 14…

Gabriel

cpaolo · March 9, 2023, 8:07am

This is odd. I did the test with version 14. Guess vst2 is no longer supported only for new plugins from version 12 and above.

Grand Rhapsody, as part of the Keyboard Collection, is quite older.
I bought the collection for my interest in CP-80, a good choice at the time, even though I definitely prefer Pianoteq CP now.

Anyway, it’s true, when I installed the bunch of Waves plugins I own, the waveshell-xyz.dll were installed there:

C:\Program Files\VSTPlugins\.

So I just moved them to the right place, which is (for me):

C:\Program Files\Steinberg\Vstplugins\.

cdv_gabriel · March 9, 2023, 8:13am

Ah! Now I see! I expected it to be called “Grand Rhapsody something…”!

Thank you for letting me know! I have found the waveshell-xyz.dll files and moved them to the proper location and now I can load the vst2 version.

Gabriel

EDIT: And the VST2 version loads ok! Hurray!

JonFromMaine · November 25, 2023, 4:24pm

I know this is a bit of an old post, but did anyone get Waves Rhapsody (and an of the other V14 keyboards in the latest bundle) to work in Cantabile Performer? I get the dreaded ‘Failed to load data because it was in the incorrect format (error 13002)’ whenever I switch back to a song which has the plugin. When it’s added, it initially works fine, but needs to be deleted and reloaded each time you want to use it in Cantabile. Reloading the same plugin works, but doesn’t seem to bring up the interface the same way deleting and loading from scratch does. All of the keys work fine with Waves standalone host program. cdv_gabriel seems to be reporting some success but not sure it’s really working. The Waves effects plugins don’t seem to have the issue (thank goodness!)

cdv_gabriel · November 26, 2023, 5:39pm

Hi @JonFromMaine,

I had given up on using Rhapsody…to much of an headache every time! Anyway, in trying to help you out, I have checked if the plugin was still loading in C4 Performer and I run into lots of troubles (as somewhat I expected!). First, I got a 13209 error with the plugin version I had put into my rack. Then I noticed that only the VST3 version was available. By replacing the Failed plugin with the VST3, it loaded correctly. However, my Waves licenses were also gone and all the Waves plugins were running in demo mode.

I launched Waves Central, which updated itself. The licenses were all attributed to a disconnected device…how can it be? I have installed them on only one device! Anyway, I recovered my licenses (a thing which can happen only once a year, apparently…like Christmas!). After a few other attempts to get the VST2 version, including repairing all the Visual C++ versions on my system as suggested in this video (a procedure which had no effect at all…):

…I finally re-read the thread above and I found out the problem…
I checked the location of the WaveShell1-VST dll’s and found that the 14.12 version had been installed again in C:\Program Files\VSTPlugins. I had moved 14.0 and 14.1 into C:\VstPlugin64 but now a new version had been added and it seems it was needed to load the new VST.

I must have run an update at some time and the update installed the new version of WaveShell1-VST in the wrong place. I still do not understand what happened to my licenses.

So now I have the VST2 version loading again (this time I added C:\Program Files\VSTPlugins to the path list in Plugin Options) and activated.

Ok…sorry for a very long story…which anyway, at least for me, ends with the same moral: I have to stay away from Waves plugin!

Gabriel

cpaolo · November 26, 2023, 7:50pm

I know Waves plugins are somewhat hated, but I have about 20 of them and never had any issues.

JonFromMaine · November 27, 2023, 3:39am

Sorry Gabriel. It sounds like there’s a solution in there somewhere but I’m having trouble with it. Are you saying it works as a VST2? I’m running the latest V14.2 and I think it requires VST3. I’ve been in contact with Waves support and they’ve had me move the appdata roaming preferences folder to my desktop but the VST I’m using in Cantabile is the one they say to use and it’s in the folder they say to put it. Still getting the error in Cantabile when I switch back to it from another song (it initially works).

cpaolo- Are you running V14.2 of the Grand Rhapsody Piano (or any of the V14 keyboards - happens on all of the ones in the bundle)?
If so, could you please give me some info on where you have it installed and the VST file you’re using?

At this point, it’s just an annoyance for me as these VSTs are totally redundant with instruments I have licenses for from other vendors. I have a HUGE number of virtual instruments, including many grand pianos, (more than 150 Cantabile songs) and they all work in Cantabile except these Waves keyboards. If I can’t get a fix on this, I’ll just remove the Waves keyboards from Cantabile and accept the money I paid as a loss and won’t think about it anymore. But if there is a solution I’d really like to identify it. I also bought a large number of Waves plugin effects during their sale and at least those appear to be compatible with Cantabile. Waves support has pointed out to me that Cantabile is not a supported host. Thanks -Jon

cdv_gabriel · November 27, 2023, 8:41am

My Grand Rhapsody version is 4.12 (no dot between 1 and 2). I can load both VST2 and VST3 version, provided that the folder containing the WaveShell dll for VST2 (C:\Program Files\VSTPlugins ) is included in Cantabile’s list. Otherwise, only the VST3 version is seen by Cantabile.

However, I have not tried to reproduce your exact problem. What should I do? If I understand correctly, I should try loading two songs, both using the vst. When loading the second song, the plugin should give the error. Is this correct?

Gabriel

JonFromMaine · November 27, 2023, 11:19am

Sounds like we have the same version. The problem is very simple to reproduce. I create a new song and add plugin: Waves Grand Rhapsody. It plays fine. I save the song and add to my playlist. I then switch to another song. When I switch back to the Grand Rhapsody it doesn’t activate. There’s a red X next to the plug-in in the route table. When I click it I get a ‘bad format’ error message. Same problem for all of the Waves keyboards.

cdv_gabriel · November 27, 2023, 12:05pm

I can confirm that it happens to me, too. I created a song with two instances of Grand Rhapsody (a VST2 and a VST3). When reloading the song (either selecting it in the “Set list” or from the “File” menu) the VST3 version is not loaded due to the 13002 error. The VST2 version loads ok.

If I replace the VST3 plugin with itself, it loads correctly.

Maybe something for @brad to think about? I suspect that the VST3 waveshell is trying to load the VST2 plugin or something similar.

Here is a portion of my log file, when the load error happens:

00455003    16109   [02476:2]: Song loading 'C:\Users\gabpa\Dropbox\Cantabile\grandrap.cantabileSong'
00455037       34   [02476:2]:   Rack loading 'C:\Users\gabpa\Dropbox\Cantabile\grandrap.cantabileSong' (template:)
00455037        0   [02476:2]:   #174 InputPortProvider [InputPort] attaching
00455037        0   [02476:2]:   #175 OutputPortProvider [OutputPort] attaching
00455037        0   [02476:2]:   #175 OutputPortProvider [OutputPort] detaching
00455037        0   [02476:2]:   #174 InputPortProvider [InputPort] detaching
00455037        0   [02476:2]:   #176 InputPortProvider [InputPort] attaching
00455037        0   [02476:2]:   #177 OutputPortProvider [OutputPort] attaching
00455038        1   [02476:2]:   #178 Plugin [Grand Rhapsody Piano Stereo 1] attaching
00455038        0   [02476:2]:   #179 Plugin [Grand Rhapsody Piano Stereo 2] attaching
00455038        0   [02476:2]:   State loading 'null' for 'grandrap'
00455038        0   [02476:2]:   State loaded in 0ms
00455038        0   [02476:2]:   Load operation starting
00455039        1   [02476:2]:     VST2- WaveShell1-VST 14.12_x64 (1918570176) - Loading C:\Program Files\VSTPlugins\WaveShell1-VST 14.12_x64.dll>47524853 (platform: 0002)
00455039        0   [02476:2]:     VST2- WaveShell1-VST 14.12_x64 (1918570176) - Library loaded hInstance = 0x00007FFA11950000
00459934     4895   [02476:2]:     VST3- WaveShell1-VST3 14.12_x64 (#63) - Loading plugin C:\Program Files\Common Files\VST3\WaveShell1-VST3 14.12_x64.vst3 - 56535447-5248-5367-7261-6e6420726861
00459934        0   [02476:2]:     Loading VST-MA module C:\Program Files\Common Files\VST3\WaveShell1-VST3 14.12_x64.vst3
00459934        0   [02476:2]:     Already loaded, adding reference
00461059     1125   [02476:2]:     VST3- WaveShell1-VST3 14.12_x64 (#63) - Audio bus counts: 1 in 1 out
00461093       34 ! [02476:0]:     Failed to load plugin 'Grand Rhapsody Piano Stereo 2'
System.InvalidOperationException: Failed to load data because it was in the incorrect format (error 13002)
   at #=z7lk5pUUQyXh9MrWjySczjhXeUALC.#=zI_UN$28eeBna(Int32 #=z3tSVt1k=, Byte[] #=zt584gv8=)
   at #=zmQLTWkkjRcAhoRBeb1Et02_enPWn.#=zntgi$Fr2OVxv(Byte[] #=zt584gv8=)
   at #=zG$7U2sDzntWHpiMrqy0zIPL1dx2v.#=z_$$QD_OTmZ5c()
00461093        0   [02476:2]:     VST3- WaveShell1-VST3 14.12_x64 (#63) - Closing...
00461105       12   [02476:2]:     Unloading VST-MA module 000000007ED67920
00461105        0   [02476:2]:     module still referenced, not unloading
00461105        0   [02476:2]:     VST3- WaveShell1-VST3 14.12_x64 (#63) - Closed.
00461134       29   [02476:2]:   Load operation finished
00461134        0   [02476:2]:   Setting active song 'grandrap'

Gabriel

Edit: here is the song file: grandrap.cantabileSong (11.1 KB)