Renoise x64 / win7 x64 etc etc…
Each time when Renoise crashes (either it plugin scan or simply project crash for some reason like glitchy vst gui) now renoise.exe hangs for like 15-20 minutes! And since i use MIA midi in ASIO which means that when asio enabled - no other audio can be used…So i have to sit silent for 15-20 minutes.
And i must add that i have never had that experience with previous versions of Renoise.
But you always can kill it by force?
If you know a way how to replicate this, with a buggy VST or whatever else, it would be know about this, so we can try this here.
taktik
No way!
That’s the problem, i can’t even kill process, it have to hang for 15-20 mins, doesn’t matter how much times i’ll try to kill it 
I know how to replicate this very easy by just rescan my plugins and Renoise hangs on Betabugs Spinbug, after that only way is to obey windows app-hang
But this plug works fine with previous versions of Renoise and with this x32 version and also with Reaper x64 without any issues, which leads it not to buggy plugin i guess…
it’s related to this topic http://www.renoise.com/board/index.php?/topic/33099-problems-with-bridged-betabugs-spinbug-and-widebug-vsts/
And Reaper x64 is strong proof that it’s not buggy plugins.
I can make a video of crash proces if you want, but it’s easyer to just say it on words i guess:
The thing is either it’s plugin scan or project crash - result same, since i installed b2 and then b3 i’ve never seen Renoise crash (wish i won’t seen it crash at all, but still 
) without this hang…
Maybe it’s some incompatibility with ASIO drivers of my card and renoise can’t kill audio?
upd #1 You can try to download and try to recreate it with Betabugs Spinbug, it’s free!
http://www.betabugsaudio.com/plugs.php
This problem starting to get on me hardly, it always hangs for a looooooong time…
If I have a crash with plugins using asio drivers, I can’t kill the Renoise process in the taskbar and have never waited long enough to see if with patience, I could kill it later on. Rebooting solves the problem here.
Using directsound drivers however, I can kill the Renoise process in the taskbar right away!
Maybe this is the same for 64 bit version Renoise?
Hmmm…Well maybe, but thing is that i have never ever seen this before with asio or with direct sound on any previous version on Rns / audio hardware / OS, i could kill process in every possible situation before.
intresting topic about the ASIO behaviour: if renoise crahs in my wxp sys (32 bit) i always can kill the process (i use processexplorer as task manager), BUT the asio driver is locked and cannot be used until reboot
wow…that’s heavy
must be driver-specific error than
Which audiocard do you have?
When renoise crashes here , and killing the proces doesn’t help , I unplug my soundcard ( usb edirol ua25) , no need to reboot
Hope you that helps
i have a pci DSP2000 hoontech ;( (now hoontech, he have buyed sta back in time, or was it reverse…dunno)
http://www.st-audio.de/products/dsp2000/info.html
driver failure… ofcourse… but the driver CAN initialize the soundcard during reboot ;(
unfortunately the “Reinitialize” button inside renoise doesnt take effect, and the bad driver software does not help 
Looks a lot like the ESI ESP1010 (I have the 1010e edition)
I can recommend the card. Don’t know if the card would swallow the ESP1010 drivers though, but i guess trying doesn’t hurt…
hmm, intresting: reading the datachard gives the same technically facts ^^ maybe i can try it on a second installed windows ^^ thanks for the hint!
yould you do a screenshot of the control panel ?
this how it looks on my card
For the 1010e it looks quite different, but you also have a separate SPDIF module with it.
Also the ESP1010 (Normal PCI version) is not the same as the ESP1010e (X-pci version)
Here’s the one for the 1010:
so i try the ESP1010 (Normal PCI version) and not the ESP1010e version! thank you for the screenshots and the hint!
edit:
lol: fourth sentences in the link i’ve posted:
Replacement doesn’t mean that the hardware setup and addressing mode is compatible to your old hardware. If a one on one setup works it means they at least added compatible support in these driver for your older hardware yet even in that case: that is no guarantee everything you could do with the original driver, is still available in the alternative driver.
But it is a card from the early 2000 and troubles already started for a lot of drivers out of this era when Windows XP SP2 came out and with SP3 this went worse from where SP2 ended.So i think it is time to put this card in your museum.
Not really sure that this is equally for all drivers problem, coz why i haven’t seen such behaviour for years with same card than?
