I just downloaded 1.0 and tested against the above hosts in Win XP SP2. (Bidule version 0.9677 and Reaper version 2.44). They both failed to instantiate the LittleSpacey GUI.
Bidule froze and I was able to capture this screen shot before killing the process with task manager.
http://www.esnips.com/doc/91c9ec64-1b3d ... paceyCrash
Reaper launched the Visual Studio debugger and I was able to capture the following screen.
http://www.esnips.com/doc/ba27945b-0fdd ... eaperCrash
I've only been able to test this on my laptop. I'll try to test on another machine sometime this weekend.
Little Spacey crashing both Reaper and Bidule.
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
Hi,
both work fine here (Bidule 0.9685, REAPER 2.45). I have to suspect a problem with your laptop. If you can try another machine, that would be helpful.
thanks,
os.
both work fine here (Bidule 0.9685, REAPER 2.45). I have to suspect a problem with your laptop. If you can try another machine, that would be helpful.
thanks,
os.
-
- KVRist
- Topic Starter
- 57 posts since 9 Apr, 2002 from Austin, TX. USA
Okay back from testing.
Three different machines show exactly the same results. The machines are as follows:
1. Toshiba Portege M200 running Windows XP Tablet Edition SP 2.
Plogue Bidule 0.9677
Reaper 2.44.
2. Dell D600 running Windows XP Professional SP 2.
Plogue Bidule 0.9687 (latest)
Reaper 2.58. (last version 2.x).
1. Homemade Desktop - Asus Motherboard with Xeon processor running Windows XP Professional SP 2.
Plogue Bidule 0.9687
Reaper 2.44.
All three machines exhibit the same crash errors as before. I can tell you that in Bidule, whether the LittleSpacey bidule is wired to an audio port or not makes no difference. The lock up occurs only when you click on the bidule to look at the Little Spacey GUI.
Another clue on this is that Little Spacey 1.0.0 and Warbler 1.0.2 share the same VST plugin id of ESwb. I downloaded Warbler to see if the problem occurred with other ES plugins and when I scanned the plugin directory with Bidule, I got the duplicate id error from Bidule. I found the following scan information in the bidule.log file:
C:\AllMusic\VST Plugins\Auditions\littlespacey.dll. is a VST 2.4 .I:0x 0:5512:1340810158:VSTVersion >= 2400, trying to use effSetSpeakerArrangement
I:0x 0:5512:1340810158:,45537762,ESwb,Expert Sleepers,Little Spacey,Little Spacey,19,2,2,0,1,0,0,0,1
C:\AllMusic\VST Plugins\Auditions\warbler.dll. is a VST 2.4 .I:0x 0:5512:1340810166:VSTVersion >= 2400, trying to use effSetSpeakerArrangement
I:0x 0:5512:1340810166:,45537762,ESwb,Expert Sleepers,Warbler,Warbler,15,2,2,0,0,0,0,0,1
and later...
These VST problems were encountered:
Duplicate ID : ESwb ( C:\AllMusic\VST Plugins\Auditions\warbler.dll )
Duplicate ID : G201 ( C:\AllMusic\VST Plugins\Delays\GS-201\GS-201_mono.dll )
Duplicate ID : kztn ( C:\AllMusic\VST Plugins\Filters\NUSofting_Kaotica_Stereo.dll )
Duplicate ID : ngaf ( C:\AllMusic\VST Plugins\Misc By Developer\Jeremy Evers\AtlantisFilterMono.dll )
Duplicate ID : D008 ( C:\AllMusic\VST Plugins\Vst Hosts\FLStudio6\DR-008.dll )
Could it be that you are testing with a different copy of Little Spacey than what is available on your download page?
By the way, I removed Little Spacey and rescanned and Warbler came up without a problem. Opening the Warbler GUI doesn't crash Bidule either.
Can someone else try and reproduce?
Three different machines show exactly the same results. The machines are as follows:
1. Toshiba Portege M200 running Windows XP Tablet Edition SP 2.
Plogue Bidule 0.9677
Reaper 2.44.
2. Dell D600 running Windows XP Professional SP 2.
Plogue Bidule 0.9687 (latest)
Reaper 2.58. (last version 2.x).
1. Homemade Desktop - Asus Motherboard with Xeon processor running Windows XP Professional SP 2.
Plogue Bidule 0.9687
Reaper 2.44.
All three machines exhibit the same crash errors as before. I can tell you that in Bidule, whether the LittleSpacey bidule is wired to an audio port or not makes no difference. The lock up occurs only when you click on the bidule to look at the Little Spacey GUI.
Another clue on this is that Little Spacey 1.0.0 and Warbler 1.0.2 share the same VST plugin id of ESwb. I downloaded Warbler to see if the problem occurred with other ES plugins and when I scanned the plugin directory with Bidule, I got the duplicate id error from Bidule. I found the following scan information in the bidule.log file:
C:\AllMusic\VST Plugins\Auditions\littlespacey.dll. is a VST 2.4 .I:0x 0:5512:1340810158:VSTVersion >= 2400, trying to use effSetSpeakerArrangement
I:0x 0:5512:1340810158:,45537762,ESwb,Expert Sleepers,Little Spacey,Little Spacey,19,2,2,0,1,0,0,0,1
C:\AllMusic\VST Plugins\Auditions\warbler.dll. is a VST 2.4 .I:0x 0:5512:1340810166:VSTVersion >= 2400, trying to use effSetSpeakerArrangement
I:0x 0:5512:1340810166:,45537762,ESwb,Expert Sleepers,Warbler,Warbler,15,2,2,0,0,0,0,0,1
and later...
These VST problems were encountered:
Duplicate ID : ESwb ( C:\AllMusic\VST Plugins\Auditions\warbler.dll )
Duplicate ID : G201 ( C:\AllMusic\VST Plugins\Delays\GS-201\GS-201_mono.dll )
Duplicate ID : kztn ( C:\AllMusic\VST Plugins\Filters\NUSofting_Kaotica_Stereo.dll )
Duplicate ID : ngaf ( C:\AllMusic\VST Plugins\Misc By Developer\Jeremy Evers\AtlantisFilterMono.dll )
Duplicate ID : D008 ( C:\AllMusic\VST Plugins\Vst Hosts\FLStudio6\DR-008.dll )
Could it be that you are testing with a different copy of Little Spacey than what is available on your download page?
By the way, I removed Little Spacey and rescanned and Warbler came up without a problem. Opening the Warbler GUI doesn't crash Bidule either.
Can someone else try and reproduce?
--taji
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
I found out about the vst ID clash the other day - sorry about that. I usually test in Live, which ignores the IDs, so I didn't notice the clash.
Could you test with my plug-in Oomingmak? That has the GUI that's closest to Little Spacey's.
My suspicion is that your graphics hardware is lacking some key feature that I'm relying on but not testing for.
Could you test with my plug-in Oomingmak? That has the GUI that's closest to Little Spacey's.
My suspicion is that your graphics hardware is lacking some key feature that I'm relying on but not testing for.
-
- KVRist
- Topic Starter
- 57 posts since 9 Apr, 2002 from Austin, TX. USA
I'm at work now and was only able to test Oomingmak today on the Dell laptop. Other than about a two second delay between clicking on the bidule and seeing the GUI for the first time, there were no problems. The GUI did not crash Bidule and the delay only occurred on the first redraw of Oomingmak's GUI. Of course it's a little older machine (1.8 GHz Pentium M).
Also, I demoed Oomingmak on my homemade desktop about a month ago and did not encounter any problems.
You probably already know: Oomingmak's VST Plugin ID is also ESwb.
C:\AllMusic\VstPlugins\Little Spacey\oomingmak.dll. is a VST 2.4 .I:0x 0:2276:361939:VSTVersion >= 2400, trying to use effSetSpeakerArrangement
I:0x 0:2276:361939:,45537762,ESwb,Expert Sleepers,Oomingmak,Oomingmak,40,2,2,0,1,0,0,0,1
Also, I demoed Oomingmak on my homemade desktop about a month ago and did not encounter any problems.
You probably already know: Oomingmak's VST Plugin ID is also ESwb.
C:\AllMusic\VstPlugins\Little Spacey\oomingmak.dll. is a VST 2.4 .I:0x 0:2276:361939:VSTVersion >= 2400, trying to use effSetSpeakerArrangement
I:0x 0:2276:361939:,45537762,ESwb,Expert Sleepers,Oomingmak,Oomingmak,40,2,2,0,1,0,0,0,1
Could be - the Dell has an ATI RADEON 9000, the toshiba has an NVIDIA graphics chip and the desktop motherboard has a built in XGI Z9S graphics chip.My suspicion is that your graphics hardware is lacking some key feature that I'm relying on but not testing for.
--taji
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
This is very strange - Oomingmak and Little Spacey really do have pretty much the same GUI code.
I just downloaded Little Spacey from my own download site and tested again, and it works fine.
Are you comfortable with registry hacking using regedit? If so, you could try setting
HKEY_CURRENT_USER\Software\Expert Sleepers\com.expertsleepers.LittleSpacey\Enable eye candy
to 0. This will turn off some of the advanced GUI features, which might be instructive. (Turning off Eye Candy in the Oomingmak prefs window does the same thing.)
I just downloaded Little Spacey from my own download site and tested again, and it works fine.
Are you comfortable with registry hacking using regedit? If so, you could try setting
HKEY_CURRENT_USER\Software\Expert Sleepers\com.expertsleepers.LittleSpacey\Enable eye candy
to 0. This will turn off some of the advanced GUI features, which might be instructive. (Turning off Eye Candy in the Oomingmak prefs window does the same thing.)
-
- KVRist
- Topic Starter
- 57 posts since 9 Apr, 2002 from Austin, TX. USA
Uuuh, there is no registry key
"HKEY_CURRENT_USER\Software\Expert Sleepers\com.expertsleepers.LittleSpacey\Enable eye candy"
available to set.
Are you instructing me to create this key as well as set it?
"HKEY_CURRENT_USER\Software\Expert Sleepers\com.expertsleepers.LittleSpacey\Enable eye candy"
available to set.
Are you instructing me to create this key as well as set it?
--taji
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
-
- KVRist
- Topic Starter
- 57 posts since 9 Apr, 2002 from Austin, TX. USA
Okay,
I've only tested this on the Toshiba Tablet running Bidule 0.9687 but after setting the registry value, the gui came up and bidule did NOT crash. The shadow effects for the knobs aren't available but I imagine you already knew that. Just to make sure the problem was with the registry setting, I set it to 1, reloaded bidule and little spacey crashed it as before. Then I set the value back to 0 and the problem disappeared again. I'll do a bit more testing with it and let you know how it goes.
Thanks for the help so far.
I've only tested this on the Toshiba Tablet running Bidule 0.9687 but after setting the registry value, the gui came up and bidule did NOT crash. The shadow effects for the knobs aren't available but I imagine you already knew that. Just to make sure the problem was with the registry setting, I set it to 1, reloaded bidule and little spacey crashed it as before. Then I set the value back to 0 and the problem disappeared again. I'll do a bit more testing with it and let you know how it goes.
Thanks for the help so far.
--taji
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
Thanks, that's useful information.
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
Here's something else that would be very helpful: download GLEW from
http://glew.sourceforge.net/
There are Windows binaries linked from the front page:
https://sourceforge.net/project/downloa ... -win32.zip
If you unzip that and look in the glew\bin folder, you'll see two apps, "visualinfo.exe" and "glewinfo.exe". If you run those, they'll each generate a text file. If you could send me those text files (or post the contents here), that would probably enable me to see what the problem is.
Thanks,
os.
http://glew.sourceforge.net/
There are Windows binaries linked from the front page:
https://sourceforge.net/project/downloa ... -win32.zip
If you unzip that and look in the glew\bin folder, you'll see two apps, "visualinfo.exe" and "glewinfo.exe". If you run those, they'll each generate a text file. If you could send me those text files (or post the contents here), that would probably enable me to see what the problem is.
Thanks,
os.