Quite a big disadvantage in Cubase SX3 !!!!!

[Sascha Franck]

- WL4E doesn't even report what dll caused trouble - in the help file they recommend using drwatson

Yeah, great - if it'd only create something through DrWatson. But it's all the way straight back to the desktop for me.
And, believe it or not, WL3 started scanning ALL *.dll files on my C: partition after I altered the vstplugins path in SX.
Freaking A L L !
I wonder when I told it to do so. And I wonder about when I told SX to communicate with WL, too.

Great marketing tactics at the b0rg house. They want me to update WL in case I want to run SX on the same machine. I'll just stuff that f**king dongle up their asses instead. Sorry.

[Sascha Franck]

btw, Sascha, does WL3 have the Audio Montage feature? maybe that would be worth the upgrading for?

Yes, it has. It's the first WL version with audio montage.
And it's all working mighty fine as well. Unless SX tells it to scan certain plugins that is.

f**k, really, I'm losing money right now (or time, however you put it). Have to cut/loop some samples. As a temporary solution I'll just uninstall that SX f**ker. But I'm absolutely clueless about what to do after that. I need SX as well. At least sometimes. And I also need those plugins making WL crash "natively" (not through Energy XT that is). Under SX.
No idea about what to do. Seems I have to install a crack (I assume newer WL versions offer defineable plugin directories). Great idea!

[cptgone]

don't you have that "plugins to ignore.txt" file then?

[Sascha Franck]

don't you have that "plugins to ignore.txt" file then?

Oh yes, just found it (never been aware of that, don't even know where I put the printed manual anymore, it's just too long ago since I got WL3).
What do I type in there? The exact path and plugin name? Such as D:\Programme\Emagic\vstplugins\Native Instruments\Kontakt2.dll?

Whatever it might be, seems like quite some work, especially since I simply don't know which plugins are causing the crash.

[cptgone]

don't you have that "plugins to ignore.txt" file then?

Oh yes, just found it (never been aware of that, don't even know where I put the printed manual anymore, it's just too long ago since I got WL3).
What do I type in there? The exact path and plugin name? Such as D:\Programme\Emagic\vstplugins\Native Instruments\Kontakt2.dll?

Whatever it might be, seems like quite some work, especially since I simply don't know which plugins are causing the crash.

in WL4E, i just have to list the names, path not included:

Code: Select all

boneskiller.dll
trollspace.dll

add all your VSTi's, if that doesn't fix it you can watch the status bar as WL scans the plugs. if you have a lot of VSTi's, and they're all in the same (parent) folder, you can use

Code: Select all

dir /w c:\vstfolder\myvstis\ > c:\vst-list.txt

to get a list.

[Sascha Franck]

Thanks mate, I'll try that! First I need to reinstall WL anyways, as right now it's in the "let me scan all DLLs on your C: partition" loop. Hmpf.
Gonna get back with the results tomorrow, the GF seems to want something. Not a crashing DLL I hope.

[cptgone]

Gonna get back with the results tomorrow, the GF seems to want something. Not a crashing DLL I hope.

for that kind of DLL, try viagra

[Sascha Franck]

Pffff... who was talking about plugins?

[G-Ro124]

wait cptgone are you saying that there's a way that I can create a .txt file of all the .dll's in a certain folder???

[cptgone]

wait cptgone are you saying that there's a way that I can create a .txt file of all the .dll's in a certain folder???

yep:
Start / Run / type: "cmd" and hit <Enter> / type the dir command i posted earlier, with adapted paths of course. i don't know if there's a way to have it list only the dll files, you might google "dos command dir" for more info. (i edited my textfile manually)

[cptgone]

Pffff... who was talking about plugins?

[soulata]

Pffff... who was talking about plugins?

hope yours didn't crash during the scanning routine....


btw, you experienced Cubase users: is it possible to have arrange window maximized all the time?

explanation: After arranging you feel like mixing a bit, you press F3, do your thing, press F3 once again...arrange window isn't maximized anymore, so you can't see little zoom handles in the lower right corner until you click maximize window again.

I've tried with screensets and well... (might be completely my fault, can't say).


Agreed on the need for a complete rehaul: vst channels in mixer, yes please (I never ever need those midi channels - is there a way I'd turn them off by default - globally?)

thanks

k

[Sascha Franck]

hope yours didn't crash during the scanning routine....

Ah well, it only sorta did.

btw, you experienced Cubase users: is it possible to have arrange window maximized all the time?

Yes. Just set all other windows to "always on top" status.
There's also a general preference, so that all plugin (and mixer, too, I think) windows will automatically be opened as "always on top". Also, most (if not all) other windows, such as the plugin rack, remember their last status globally (so, they'd open as "aot" windows in new songs as well).
Of course there's a downside coming with it (it wouldn't be a Steinberg product if there wasn't...): The keycommands usually assigned to, say, the mixer (i.e. solo) will now be valid in "project window mode" - this means they're acting pretty much different, the reason being that Steinberg doesn't manage to actually "focus" float windows. Because of this, it's also impossible to use any letters used by whatever keycommands, to type in, say, a new patch name into Guitar Rig.
Oh yes, there's some clever programmers in the b0rg house...

[ericj23]

alternatively just stretch your main window to the needed size and never use always on top

ctrl and tab are your friends

[Sascha Franck]

alternatively just stretch your main window to the needed size and never use always on top

I hate that, because it's wasting an incredible amount of space for additional title bars and whatever.