Whenever I want to load Reaktor(5) into the sequencer EnergyXT slows down, CPU goes to 100% and I can't proceed. ctrl+alt+del doesn't help, I have to reboot. I tried it with "auto-save ensembles on" (default setting) because at this point when loading R5 Energy XT crashed, and with auto-save by default OFF. Same thing, have to reboot.
That doesn't happen with EnergyXT 1.35! Only with the latest beta.
Strangely enough I CAN load Reaktor into an empty project, connect various effects and so on in the 26.August-beta. Not in the sequencer.
Not much of a problem, as I simply installed the older XT-version 1.35 again. But anyway, it's a bug here and I hope it will go away in the next betas.
Can any Reaktor-user confirm this, rsmus7, Sickle, Sascha or others?
BR: EXT standalone 26.8. and Reaktor
-
- KVRist
- 45 posts since 4 Mar, 2004 from New Jersery, USA
Just started using Reaktor but seems pretty ok. I'm using EnergyXt 1.4 beta 26 Aug Stand Alone as my host.
I don't have any big projects with Reaktor yet... but I do run it in the sequencer.
Occasionally I get no sound out of Reaktor.. just seems dead, can't even tell if it gets midi, but a restart or sometimes load another ensemble fixes it.
What OS etc. are you using?
Phil
I don't have any big projects with Reaktor yet... but I do run it in the sequencer.
Occasionally I get no sound out of Reaktor.. just seems dead, can't even tell if it gets midi, but a restart or sometimes load another ensemble fixes it.
What OS etc. are you using?
Phil
-
- KVRAF
- Topic Starter
- 3002 posts since 24 Nov, 2003 from Heidelberg&Hamburg
Hi there, thanks for the reply 
. i found this bug on my laptop (WinXP, Athlon2200+, where I can't use all the Reaktor-ensembles 
) and on my PC (on WinXP too). Strange, I just got back to the former beta (from 12.August or so) and it works... I install the latest one you run too and XT crashes here on both machines. Any other VSTi works without a fault. But well, as it works for you, the mistake must be here....
Thanks again for answering!
. i found this bug on my laptop (WinXP, Athlon2200+, where I can't use all the Reaktor-ensembles ) and on my PC (on WinXP too). Strange, I just got back to the former beta (from 12.August or so) and it works... I install the latest one you run too and XT crashes here on both machines. Any other VSTi works without a fault. But well, as it works for you, the mistake must be here....Thanks again for answering!
-
- KVRAF
- Topic Starter
- 3002 posts since 24 Nov, 2003 from Heidelberg&Hamburg
Thanks for the answer, Sickle. (Son? I was away for too long here it seemsSon of Sickle wrote:Sorry, Klemperer, still no R5 here, but I'm sure Jorgen will get it ironed out before too long.
) Well I got my solution anyway! This is the big advantage of XT...as I CAN load Reaktor into the "empty project". Problem occurs only in the sequencer. So I simply loaded an EnergyXt-VST into my sequencer instead of Reaktor directly. and the Reaktor then into EnergyXT as VST - and now it works
. Well, as you say, Jorgen might as usual iron this out soon (might be XT-related, as it works in other hosts). Anyway, the workaround is fine too.
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
I also have those probs lately with R5 here , mainly concerning the ensembles which are tempo synched to the host , like for example the groove boxes like Aerobic or NuSkool , and only since the last or the one before last beta version of eXT .
After the Reaktor instance is loaded with the ensemble and once I press play in eXT's seq , there's no playback and the standalone has 100% cpu usage and I have to kill it sooner or later per task manager . What wonders me though that I can still save the file - so I quickly save and reload and then the song plays fine .
Needless to say I don't find any explanation for this
It's not the only weirdness I had here lately (though OT !!), some days ago I could load two instances of standalone at the same time (I just had overseen that one instance was already open and so fired up a new one) which both - and that's the very strange thing - had the asio driver instantiated
- so playback was a mere crackling until I figured out that the other standalone.exe already used the asio driver ... 
Anyway , back to Reaktor - hope this gets fixed - it worked ok until recently .
After the Reaktor instance is loaded with the ensemble and once I press play in eXT's seq , there's no playback and the standalone has 100% cpu usage and I have to kill it sooner or later per task manager . What wonders me though that I can still save the file - so I quickly save and reload and then the song plays fine .
Needless to say I don't find any explanation for this
It's not the only weirdness I had here lately (though OT !!), some days ago I could load two instances of standalone at the same time (I just had overseen that one instance was already open and so fired up a new one) which both - and that's the very strange thing - had the asio driver instantiated
- so playback was a mere crackling until I figured out that the other standalone.exe already used the asio driver ... Anyway , back to Reaktor - hope this gets fixed - it worked ok until recently .
-
- KVRAF
- Topic Starter
- 3002 posts since 24 Nov, 2003 from Heidelberg&Hamburg
thanks for these explanations, Plastique. Strangely enough I can't even save - my EXT simply crashes (I only loaded the new "subharmonic"synth in my example). To put it more clear, I can't do anything, but every 5-10 minutes something happens, for example as I had the default-setting to save the ensemble in a folder before changing anything I could choose such a folder after 10 minutes. Strange...plastique wrote:Anyway , back to Reaktor - hope this gets fixed - it worked ok until recently .
But if you simply put your R5 into a EXT-vst in the sequencer, does it work then? Doesn't seem to take much CPU and works here as a workaround, until Jorgen has time to fix this
. Couldn't, as I said, find any other synth I have that gets EXT with sequencer to crash.
-
- KVRAF
- 3475 posts since 6 Oct, 2001 from europe-norway-oslo
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
seems to be fixed now in beta 7-okt-2005 .
Thanks jorgen !
Thanks jorgen !
-
- KVRAF
- Topic Starter
- 3002 posts since 24 Nov, 2003 from Heidelberg&Hamburg
Yes, it's fixedplastique wrote:seems to be fixed now in beta 7-okt-2005 .
Thanks jorgen !
. Thanks Jorgen!! And thanks for mentioning it, Plastique, I didn't read about the fix in the latest-beta-changes and would have used my workaround for ages I think
(by the way, I just got over the 1000 
)