Did that to me too - eXT isn't very good at telling vST from non VST dll's.bobsled wrote:Hmmm, eXT has a problem loading 2.10.
P4 2.4ghz
The installer created two .dlls which the uninstaller simply left in my Discovery vst folder. Were these supposed to be installed elsewhere, system32-ish?
discoDSP Discovery 2.10 released
-
- KVRAF
- 37533 posts since 14 Sep, 2002 from In teh net
-
- KVRAF
- Topic Starter
- 5648 posts since 18 Jul, 2002
That's why the installer now puts them in the System32 folder and overwrites old existing DLLs, probably the culprit.
-
- KVRAF
- 37533 posts since 14 Sep, 2002 from In teh net
I've run the installer again. Only thing now is it seems to be using more CPU - not sure why but the same patch (Antidote) was using 4-6% on my dualcore system - now its using 8-16%
-
- KVRAF
- Topic Starter
- 5648 posts since 18 Jul, 2002
aMUSEd, check oversampling settings. Probably because 2X is enabled by default.
-
- KVRAF
- 37533 posts since 14 Sep, 2002 from In teh net
Maybe - I'm sure I had it on before but didn't check so maybe it was off.
How do you decide how many threads to use? I tried turning it to 4 (in Reaper) and it made strange noises but up to 3 seems Ok - should it be as many cores as you have (i.e. dualcore =2)
How do you decide how many threads to use? I tried turning it to 4 (in Reaper) and it made strange noises but up to 3 seems Ok - should it be as many cores as you have (i.e. dualcore =2)
-
- KVRAF
- Topic Starter
- 5648 posts since 18 Jul, 2002
-
- KVRAF
- Topic Starter
- 5648 posts since 18 Jul, 2002
Bump. No issues for those who have tried the demo version?
-
- KVRAF
- 9220 posts since 23 Jul, 2002 from Pequot Lakes, MN
I don't know about the demo version, George.
However, I loaded the full version into Chainer- Chainer's CPU meter reads about 15-20% on the first patch (which is where it should be with how many notes I'm playing), and Task manager's reading about 9% (which again is where it should be, I'm using a 4600x2); the 15% on one core and the rest of what's going on with the other. I went to using two threads, and while Chainer's reporting the same load as previously, Task Manager's now reporting 65% on both cores.
Now I haven't tried bumping up the latency yet, but that seems a little extreme.
ew
However, I loaded the full version into Chainer- Chainer's CPU meter reads about 15-20% on the first patch (which is where it should be with how many notes I'm playing), and Task manager's reading about 9% (which again is where it should be, I'm using a 4600x2); the 15% on one core and the rest of what's going on with the other. I went to using two threads, and while Chainer's reporting the same load as previously, Task Manager's now reporting 65% on both cores.
Now I haven't tried bumping up the latency yet, but that seems a little extreme.
ew
A spectral heretic...
-
- KVRAF
- 4687 posts since 6 Jan, 2003
i tested the discovery update in cubase SL3, project5 v2.5, and eXT 1.4. im running on an E6600 dual core.
as george mentioned, if cubase's multi processor support is enabled, then discovery needs to be set to 1 thread otherwise it will cause major problems. (especially if you try to load more than one instance.) with multi processor support turned off, discovery can be run in 2 thread mode, though i ran into some odd gui released issues.
if i boot cubase with its multi processor support off, then load discovery with 2 threads enabled, moving the gui around the screen will cause an aproximately 15+% cpu spike. there was also a 6-8% cpu spike when moving the knobs. (these problems do not happend in single thread mode.) if discovery is just assigned to a track and playing, there seem to be no problems. the issues are only related to gui movements.
interestingly, if i enable cubase's multi processor mode (going through all the steps and confirming the changes)...then go back and turn multi processor support off again...the gui related cpu problems go away. no more spikes when i move the gui, or move any knobs.
when using the first preset to test the cpu load of a single voice, having discovery set to 2 threads gives me an aproximately 4% reduction in the cpu load.
in project 5 i see pretty much the same behavior as i do when loading cubase with its multi processor support disabled. since project5 does not have any multi processor support of its own, i cant test any trick of turning it on and off. so the cpu spikes are always present when moving the gui. (as a whole, or just a knob on it.) additionally, i get some minor crackles in the audio when moving the gui around the screen. the cpu usage and reduction numbers look pretty much the same in project5 as they do in cubase - aproximately 4% reduction in cpu load with discovery in 2 thread mode.
but just as with cubase, if discovery is loaded in a track and the gui is not being moves it seems to play fine in 2 thread mode, even with multiple instances loaded.
in eXT, moving the whole gui around the screen causes the cpu meter to go all the way up to the top. not surprisingly, this also causes more crackles in the audio than it does in project5. i find eXT's little cpu meter difficult to read, so i cant give any real cpu usage examples with it. but there seem to be no problems just having discovery loaded and playing. (without gui movement.)
as george mentioned, if cubase's multi processor support is enabled, then discovery needs to be set to 1 thread otherwise it will cause major problems. (especially if you try to load more than one instance.) with multi processor support turned off, discovery can be run in 2 thread mode, though i ran into some odd gui released issues.
if i boot cubase with its multi processor support off, then load discovery with 2 threads enabled, moving the gui around the screen will cause an aproximately 15+% cpu spike. there was also a 6-8% cpu spike when moving the knobs. (these problems do not happend in single thread mode.) if discovery is just assigned to a track and playing, there seem to be no problems. the issues are only related to gui movements.
interestingly, if i enable cubase's multi processor mode (going through all the steps and confirming the changes)...then go back and turn multi processor support off again...the gui related cpu problems go away. no more spikes when i move the gui, or move any knobs.
when using the first preset to test the cpu load of a single voice, having discovery set to 2 threads gives me an aproximately 4% reduction in the cpu load.
in project 5 i see pretty much the same behavior as i do when loading cubase with its multi processor support disabled. since project5 does not have any multi processor support of its own, i cant test any trick of turning it on and off. so the cpu spikes are always present when moving the gui. (as a whole, or just a knob on it.) additionally, i get some minor crackles in the audio when moving the gui around the screen. the cpu usage and reduction numbers look pretty much the same in project5 as they do in cubase - aproximately 4% reduction in cpu load with discovery in 2 thread mode.
but just as with cubase, if discovery is loaded in a track and the gui is not being moves it seems to play fine in 2 thread mode, even with multiple instances loaded.
in eXT, moving the whole gui around the screen causes the cpu meter to go all the way up to the top. not surprisingly, this also causes more crackles in the audio than it does in project5. i find eXT's little cpu meter difficult to read, so i cant give any real cpu usage examples with it. but there seem to be no problems just having discovery loaded and playing. (without gui movement.)
-
- KVRAF
- 4687 posts since 6 Jan, 2003
ew...i see what you mean. i had only been checking the cpu meters in the hosts, not window's task manager. even though a host may be reading a normal level, just having 2 threads enabled in discovery is causing window's cpu meter to show an additional load of aproximately 40%.
) there for a second.-
- KVRAF
- Topic Starter
- 5648 posts since 18 Jul, 2002
Thanks guys, we will take those reports to check what's really going on...
-
- KVRAF
- Topic Starter
- 5648 posts since 18 Jul, 2002
-
- KVRAF
- Topic Starter
- 5648 posts since 18 Jul, 2002
Bump. 2.10 multithreading was removed for customer sanity. Sorry about it. The new installer is already available at the usual place.
On the bright side, CPUs without SSE2 can now run Discovery 2.10 without any extra hassle.
On the bright side, CPUs without SSE2 can now run Discovery 2.10 without any extra hassle.