Cakewalk SDK crash in WaveLab

Author
Victor Jach
Max Output Level: -90 dBFS
  • Total Posts : 6
  • Joined: 2004/06/24 13:44:27
  • Status: offline
2004/06/25 09:00:02 (permalink)

Cakewalk SDK crash in WaveLab

Hello

I'm using Visual C++ 6.0 with DXi SDK from Cakewalk and DirectX SDK 9.0.
There is a sample plug-in which comes with DXi SDK (AutoClip Plug-in).
When I run this plug in wavelab anything works fine until I try to change the checkbox state. When I click on that checkbox wavelab crashes. This happends also if I use a dropdown list in the plug.
Is this an incompatibility with WaveLab ? On any other host app the plug works just fine !
Thanks !
#1

10 Replies Related Threads

    bluecat
    Max Output Level: -87 dBFS
    • Total Posts : 177
    • Joined: 2004/07/02 10:04:18
    • Status: offline
    RE: Cakewalk SDK crash in WaveLab 2004/07/02 10:13:13 (permalink)
    What MFC version do you use in your Plugin?

    I had the same problem with MFC 7.2 dlls, and after debugging it seems that Steinberg applications (same bug in Cubase) do not support directX plugins developped with MFC 7. They don't manage the OLEPropertypage correctly. It has nothing to do with Cakewalk SDK.

    My solution was to write a small Patch for MFC dlls (just added a check on a pointer). You can check it out on my web page: http://software.bluecatonline.org/ , in the "Chorus" effect section. You can download the patched dll.

    I am about to write to Steinberg so that they correct their bug.
    #2
    Victor Jach
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2004/06/24 13:44:27
    • Status: offline
    RE: Cakewalk SDK crash in WaveLab 2004/07/03 18:36:06 (permalink)
    Hello,
    Thanks for your suggestion but it doesn't work even with this new mfc version. Your plug-in acts in the same way, even with the patch installed. I can't figure this out for now !
    #3
    bluecat
    Max Output Level: -87 dBFS
    • Total Posts : 177
    • Joined: 2004/07/02 10:04:18
    • Status: offline
    RE: Cakewalk SDK crash in WaveLab 2004/07/05 03:39:39 (permalink)
    Are you sure the dlls installed properly? Did you check the dll files date?
    Because my plug-in works with this patch, even on other platforms than mine. Maybe the dlls you actually use are not located in the same directory.
    #4
    bluecat
    Max Output Level: -87 dBFS
    • Total Posts : 177
    • Joined: 2004/07/02 10:04:18
    • Status: offline
    RE: Cakewalk SDK crash in WaveLab 2004/07/06 11:08:04 (permalink)
    any news?
    #5
    Victor Jach
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2004/06/24 13:44:27
    • Status: offline
    RE: Cakewalk SDK crash in WaveLab 2004/07/06 19:44:36 (permalink)
    Your plug works just fine. But can I use that dll patch as long as I use MS Visual c++ 6.0 which works with mfc42.dll. Also there are some controls like sliders which doesn't cause crash in wavelab. Please try to make a sample plug with the SDK wizard and add a check box. How can I fix that ?! How can I use the mfc71.dll version ?
    regards
    #6
    bluecat
    Max Output Level: -87 dBFS
    • Total Posts : 177
    • Joined: 2004/07/02 10:04:18
    • Status: offline
    RE: Cakewalk SDK crash in WaveLab 2004/07/07 04:02:02 (permalink)
    Only check boxes or buttons make Wavelab (or Cubase) crash. It seems Steinberg don't belong very well with MFC plugins . the only thing you can do is re-build the MFC libs (it seems that you use the 4.2 version, so my 7.1 dll won't help) and patch them the same way I did (just add a NULL pointer check in the OLE property page class).

    The other way is use MFC 7.1. To do so you need to download the latest Platform SDK from microsoft web site or the .Net SDK.

    If you need to patch the MFC yourself, I can tell you the exact modification I did (anyway it's easy to find, just debug your dll when it crashes and you'll see the NULL pointer call).

    BTW if you know how to contact the Steinberg dev teams, I'd be happy to know too, since I cannot find any email address on their website!
    #7
    Victor Jach
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2004/06/24 13:44:27
    • Status: offline
    thank you 2004/07/07 04:11:31 (permalink)
    Thank you for everything. Yes, I want to rebuid MFC42. I'm online so we can talk in realtime if you want.
    #8
    bluecat
    Max Output Level: -87 dBFS
    • Total Posts : 177
    • Joined: 2004/07/02 10:04:18
    • Status: offline
    RE: thank you 2004/07/07 09:00:25 (permalink)
    OK, I need to check again where it crashes exactly (can't remember the line number!) and i'll tell you. If you have time, just compile in debug mode and launch debugger, you'll get the ASSERT line number. Then just add a pointer check before using it and it'll work.
    #9
    Victor Jach
    Max Output Level: -90 dBFS
    • Total Posts : 6
    • Joined: 2004/06/24 13:44:27
    • Status: offline
    How to build 2004/07/07 17:55:20 (permalink)
    To apply the changes in the MFC code I must rebuild the dll. How can I do this ? I tried to use nmake for that. E.G. call nmake in the directory c:\program files\microsoft visual studio\vc98\MFC\src\ but I get few errors .
    #10
    bluecat
    Max Output Level: -87 dBFS
    • Total Posts : 177
    • Joined: 2004/07/02 10:04:18
    • Status: offline
    RE: How to build 2004/09/06 17:23:17 (permalink)
    you need to set up variables of the compiler before you launch it. Look in the MSDN, they explain how to re-build MFCs.
    What I have done in the end is rewrite the Base Property Page class in order to avoid this ~#{#~{[##| MFC bug. I don't hav eto bother with OlePropertyPage anymore.

    You can check that it works on my new plugins (http://software.bluecatonline.org). And no more MFC patch is needed.

    Hope this helps. Good luck!
    #11
    Jump to:
    © 2026 APG vNext Commercial Version 5.1