Out of the blue , renoise hung for a few seconds and now shows verry erratic behaviour
I had to restart it multiple times for it to see my audio driver , edirol ua @ running asio 4all
Loading certain plugins like ops7 takes 10 seconds with accompanying spinning blue , circle
Closing and re-opening the gui …same thing
Taldrum took forever , I had to shutdown renoise from the taskmanager
i’ve restarted my pc but no luck , I’ve had this exact same issue in the past (2-3 years ago ) but that was on my desktop , now using a laptop running win 10 and again only wwith renoise .
How come this issue is still only affecting renoise , it’s unusable to load plugins
This actually could be your CD-drive, if you have one at least… It can block any disk access, if it is unable to finish the detection (disconnect the drive then). But since it is Renoise only, and a notebook, this does not seem to match.
Is your Renoise content located on a specific drive, which only is accessed then?
Or simply move all plugins from vst dir which are used in the project, then move it back one by one. A filemon might help, too. Then filter by Renoise process and look, if it is stuck at a specific file access.
Try the normal windows audio driver. Disconnect your USB audio. Could be also blocked USB access.
It could be your SSD, too, starting to die. It is typical that accessing parts of the memory will then lead into a process / access block, since drive access logically cannot happen in parallel and everything else has to wait, until disk access is finished.
I’ve done mostly that
I only have one drive which is an sdd , it’s weird why renoise is affected
Issue stil happens and I really don’t know why all of asudden this happened on this verry laptop ( after a renoise crash )
It drives me crazy
All my g-force plugins (sem , oddity ) , talmod , Taldrum , plogue ops7 and Tranzistow are affectd ,10-20 seconds to show-hide the gui
Hmm … I meant Gforce the plugin developer ( not graphics card ) and it’s not just the gforce plugs ( see previous comment )
All I know is that Tal is using the Juce framework , Plogue uses it’s own framework (fermata ), don’t know about gforce
what I am most frightened of is that when it happened on my previous desktop ( around 2022 ) , a few months later it just refused to start up at all …bricked
I am making back-ups right now , just in case …perhaps I should consider a macmini , that new one looks like it packs a lot of power but then I won’t be able to run the best synth ever made ( Tranzistow )
I’m getting one and I’m sure it’ll be great but we’ll miss a few free PC only gems you know.
I think some older versions of the Juce framework had some serious flaws in it’s GUI code, don’t know if they found the issues…
BUT since this happened to you out of the blue it’s probably more likely an ‘accidental’ update to windows or something like that?
Did you use the same Audio interface on your desktop?
My old Scarlett 2i2 once got an update that made it unusable on my system and I had to downgrade the driver, I had to ask Focusrite to find an old version i knew worked as it wasn’t online anymore. Crazy this can happen with such a large company.
On my desktop I used the roland integra as ausio interface ( currently not using it ) , laptop uses an old edirol ua 25 .
Afaik , I have received the last win 10 update a week ago (win 10 22h2), and updates for win 10 should have stopped somewhere in oct .
So this shuld have been the last win 10 update ever