using either the Cakewalk wrapper or the DirectiXer wrapper results in a series of "window creation failed" error messages and a partially drawn and unuseable synth in SONAR.
using the latest version 1.4a.
any ideas?
thanks. nice synth in eXT.
BR - GalactiX windows fail to draw when wrapped
-
- KVRAF
- 2202 posts since 16 Apr, 2004 from between my ears
-
- KVRAF
- Topic Starter
- 2202 posts since 16 Apr, 2004 from between my ears
can i get a witness? 
-
- KVRist
- 70 posts since 13 Jul, 2004
It's cumbersome, but this is what I do, and it requires that you did NOT uninstall Sonar 2.2, and that you have the ORIGINAL 1st. officially released version of Cakewalk's VST wrapper available to use.
If I think something I am working on can benefit from some Galactix sounds, I do this:
First I RE-WRAP all my VSTs with the OLDER, 1st version of Cakewalk's VST wrapper.
Then I go back to Sonar and bounce down to one solo track (stereo, mono it doesn't matter)ALL of the production so far.
Then I "export" it as a generic .wav file.
In earlier versions of Sonar and the original VST wrapper version, Galactix works fine. So I open an earlier version of Sonar, and insert Galactix into the "NEW" project. Call it what you want. It doesn't matter. You will ONLY use this to create Galactix tracks.
In this project I can use Galactix to create/write the parts I envision.
When I am done. I bounce to audio all the galactix tracks and export them as .wav files.
Once I'm done with that. The galactix spawned .wav files re Imported back into the current version of Sonar in which I am working.
It's cumbersome, but once you get the hang of it. It's only a matter of a few extra minutes. Since you are NOT recreating everything in Sonar 2.2. You're just making it possible to use Galactix.
Once you do that, the Sonar 2.2 project can be deleted, or stored. It doesn't matter. What you wanted were the Galactix tracks. Once bounced to audio, the Galactix midi tracks are not needed.
Then I export it as a generic .wav file, and import it into Sonar 2.2 or any earlier version.
If I think something I am working on can benefit from some Galactix sounds, I do this:
First I RE-WRAP all my VSTs with the OLDER, 1st version of Cakewalk's VST wrapper.
Then I go back to Sonar and bounce down to one solo track (stereo, mono it doesn't matter)ALL of the production so far.
Then I "export" it as a generic .wav file.
In earlier versions of Sonar and the original VST wrapper version, Galactix works fine. So I open an earlier version of Sonar, and insert Galactix into the "NEW" project. Call it what you want. It doesn't matter. You will ONLY use this to create Galactix tracks.
In this project I can use Galactix to create/write the parts I envision.
When I am done. I bounce to audio all the galactix tracks and export them as .wav files.
Once I'm done with that. The galactix spawned .wav files re Imported back into the current version of Sonar in which I am working.
It's cumbersome, but once you get the hang of it. It's only a matter of a few extra minutes. Since you are NOT recreating everything in Sonar 2.2. You're just making it possible to use Galactix.
Once you do that, the Sonar 2.2 project can be deleted, or stored. It doesn't matter. What you wanted were the Galactix tracks. Once bounced to audio, the Galactix midi tracks are not needed.
Then I export it as a generic .wav file, and import it into Sonar 2.2 or any earlier version.