there’s some allright. loading older songs while a song is playing in 2.8b3 32bit will actually result in 3-4 minutes of unresponsiveness in the “releasing old song” portion, and i have actually had renoise completely crash my machine with it (i.e., you get that gray sign saying “you need to close your machine now”. It makes me wonder what’s next.
yes, loss of keyboard is a known issue - i could’ve let that go without a mention, but it really shouldn’t be forgotten about – especially if there is any kind of a possible solution of retaining keyboard input direct to tracker. buying a midikeyboard isn’t a solution
Still, I don’t understand what issue you want addressed.
In the video, it’s not clear how you opened the plugins.
If there’s an arrow in the header, then the plugin is bridged. In your video, when you opened 2.8 32bit, then the plugins, all your plugins have the little arrow. So whatever you are doing, it’s not opening correctly. I repeat, if there’s a little arrow, then that means bridged.
With keyboard shortcuts which start a script which loads a VST/AU effect. I literally pressed
FTOEWASZC (fusionfield,toraverb,ohmboyz,transientshaper,W1,syntorus,multibandsend,Pro-Q,ValhallaDSP Room)
what the heck!? thanks for this one!!! i had “Run all plugins in sandboxes (->separate process)” toggled ON. Now that I*ve unticked that box, they all load real quick and i maintain keyboard control. that’s what i was hoping for. thanks.
i guess unticking that box will do it.
i’m not sure if it will solve my “releasing the song during playback” issue tho, and i cannot actually video it because if a song causes 2.8b3 32bit to crash my whole computer, i can’t come back with a video showing it, can i?
well, this certainly helped a great deal.
Makes me wonder if a bunch of other power users turned this on and that’s where a lot of perceived slowness is coming from. Geez, why is that option even there?!
I deleted all my 32bit plugins. I don’t have any, anymore. It’s liberating.
I think I toggled that option on cos I thought it would increase / improve behaviour. It didn’t. This should really be talked of in at least cat-size letters, and told to people. I’m sure I’m not the only village idiot ticking that box. Or, if I am the only one, the rest of you can consider yourselves fortunate!
I have no idea how to get 64bit plugins of all the plugins I use, since some are fairly old. I’d love to move to 64bit, as long as that “releasing song…” doesn’t result in crashing. but one thing… is it true that 64bit, in non-sandboxed mode, has that same “loss of keyboard”? so in essence, I should probably keep to my non-sandboxes 32bit? , yep, go back to your 32bit, esa
Wow, I just quitrenoise64bit and it took it approx ~35-45 seconds to release an empty document (no playback was going on). the “releasing song” also shuts up OSX for that portion of time (you can’t move your mouse, the whole OS is unresponsive…) interestingly, i had a 32bit version running and playing a song at the same time, and the playback was flawless.
Application: Caught an unhandled exception (Thread: GUI)!
Application: Saving a backup…
Error Message: A fatal error or crash occurred (unhandled exception in thread: GUI).
Error Message: This either happened because of a bug in Renoise, or because of a bug in one of its loaded components (plugins). Please contact and report this problem, so that it can be fixed.
Error Message: Note: It’s very important that we know exactly what has happened (what you were doing before this message popped up), or the problem cannot be replicated/analyzed. Please include a description of what you were doing and which components were being used…
MIDI: Shut down: Closing all acquired MIDI devices… ```
[/details]
but this seems related to another bug, having to do with trying to script-wise add multiple tracks to one group - which causes serious crashes, saves crashbackup .xrns's, which when reloaded (and thus the file is lost from the drive when re-loaded) - cause immediate gui crashes. I didn't expect that my incomprehension of how groups + tracks operate and how to move multiple tracks (all named "H") to a group would cause these kinds of issues.
allright, i loaded a big-ish track and quit it. renoise2.8b3 64bit gave 18 seconds of non-responsive mousetime. here's the log.well, no, no log - since there's nothing especially interesting displaying in it (there's no errors etc. it just looks like a clean quit. but somehow releasing VSTfx takes so much longer with 64bit 2.8b3)
I originally posted this in 2.8 beta bugs. it was moved to 2.8 beta ideas suggestions&help.
in light of this post being in the 2.8 beta forums, i do not understand the “the place should be the beta-forum in my honoust opinion”-part of your sentence.
That option is there because it “should” prevent Renoise from crashing if any plugin crashes including the native bit versions (It supposed to be some sort of safe-button and prevent you from loosing work), however, this is currently not the case unfortunately so hopefully during this Beta all these crashes get figured out so that this button does offer this safe option.
