Load Times
-
- KVRian
- 576 posts since 5 May, 2005 from Canada
This has been discussed before ~ but now I'm into pre-production live rehearsals and finding that some of my Multi load-times are really quite slow.
20 seconds to load a song is really a pain-in the a**.
I've adjusted my Sample Rate down to 44.1 kHz.
I've adjusted my Sample Buffer Size down to 128 Samples.
I disabled Z-load (I don't remember if it was Rick or Dan that said to do so)
I don't use DFD in instances with Kompact...
But it is ALWAYS Kompact that causes these long wait times.
I'm on Receptor 1.3 2 and was told that Kontact will run more efficiently.
HELP ME ~ my shows depend on faster changes between songs.
20 seconds to load a song is really a pain-in the a**.
I've adjusted my Sample Rate down to 44.1 kHz.
I've adjusted my Sample Buffer Size down to 128 Samples.
I disabled Z-load (I don't remember if it was Rick or Dan that said to do so)
I don't use DFD in instances with Kompact...
But it is ALWAYS Kompact that causes these long wait times.
I'm on Receptor 1.3 2 and was told that Kontact will run more efficiently.
HELP ME ~ my shows depend on faster changes between songs.
JV
-
- KVRist
- 87 posts since 23 Oct, 2005
Out of curiosty, how long does it take your receptor to boot ? My pc has long been booted and I can go get a cup of coffee waiting for my Receptor to boot. Generally 3 to 5 minutes.
Danny
Danny
-
- KVRAF
- 2017 posts since 21 Mar, 2002 from Hutchinson, Kansas
three to five minutes to boot? That doesn't seem right at all. Mine takes nowhere near as long. Maybe a minute or two. Mind you, it is stripped to the bone. I have removed every single plug-in that I don't use or can do without (sort of the opposite of Tim's Receptor...LOL). I have my premium stuff (though I haven't left some of the premium things on...I really don't need a bunch of virtual analog synths on it...got plenty of real ones), and a few odds and ends. Maybe that accounts for the faster boot.
EDIT: I just timed it. From power up to loaded multi it takes 48 seconds for mine to boot...
EDIT: I just timed it. From power up to loaded multi it takes 48 seconds for mine to boot...
-
- KVRian
- Topic Starter
- 576 posts since 5 May, 2005 from Canada
Okay ~ 49 seconds from pushing the button, to my 1st set-up being ready.
I need to hear about, Kompact, Kontact, my settings, whether 1.4 will speed things up, etcetera.
I need to hear about, Kompact, Kontact, my settings, whether 1.4 will speed things up, etcetera.
JV
-
- KVRAF
- 3971 posts since 19 Apr, 2005 from Brissie
I dunno, dude - that seems pretty quick to me...
And 20 secs between load times?? Have you tried switching songs using your DAW??
I'm not razzing you, by the way, because I had this weird idea when I first bought Receptor that it would be instantaneous switching between sounds, but then when playing my Korg Triton, which has much smaller sample material, I realised it takes longer than I remembered anyway.
These things take time!!
And 20 secs between load times?? Have you tried switching songs using your DAW??
I'm not razzing you, by the way, because I had this weird idea when I first bought Receptor that it would be instantaneous switching between sounds, but then when playing my Korg Triton, which has much smaller sample material, I realised it takes longer than I remembered anyway.
These things take time!!
I've joined Lurkers Anonymous.
-
- KVRian
- Topic Starter
- 576 posts since 5 May, 2005 from Canada
This is for stage performance, no DAW.
I don't expect instant changes (although I get them when only one plug-in is used - other than Kompact)
But I'd be much happier with 5 to 8 seconds.
I don't expect instant changes (although I get them when only one plug-in is used - other than Kompact)
But I'd be much happier with 5 to 8 seconds.
JV
-
- MUSEician
- 682 posts since 20 Aug, 2004 from California
Receptor takes about 45 seconds to boot. That is significantly faster than most computers. I said "most computers" not "all computers" because I did not time every brand of computer. Personally, I have not seen one computer that would boot faster.
After Receptor boots, it will load your last multi. If your multi is really big, that can take quite a long time. You know that receptor has finished booting and is now loading your last multi when the front panel shows "Loading..." So from the moment you pressed the POWER button and until the moment you see "Loading..." it should take approximately 45 seconds.
Try saving a document in you DAW with all the plug-ins you have in one of your bigger multis on Receptor. Also load any samples you are using. Start you computer, then double click on the save document. Time this and compare it with Receptor. Receptor will be faster.
After Receptor boots, it will load your last multi. If your multi is really big, that can take quite a long time. You know that receptor has finished booting and is now loading your last multi when the front panel shows "Loading..." So from the moment you pressed the POWER button and until the moment you see "Loading..." it should take approximately 45 seconds.
Try saving a document in you DAW with all the plug-ins you have in one of your bigger multis on Receptor. Also load any samples you are using. Start you computer, then double click on the save document. Time this and compare it with Receptor. Receptor will be faster.
Dan Timis
Software Developer
Muse Research, Inc.
Software Developer
Muse Research, Inc.
-
- KVRian
- Topic Starter
- 576 posts since 5 May, 2005 from Canada
Dan, Dan - Dan
I LOVE my RECEPTOR.
And I don't care how long it takes to cold-boot.
My concern is with Native Instruments' Kompact - damn it's slow, and switching from Multi to Multi...
I've adjusted my Sample Rate down to 44.1 kHz.
I've adjusted my Sample Buffer Size down to 128 Samples.
I disabled Z-load (I don't remember if it was Rick or Dan that said to do so)
I don't use DFD in instances with Kompact...
DAN ~ Does the above 'appear' to be the most efficient set-up?
It is Kompact that causes my long wait times.
I'm on Receptor 1.3 2 and was told that Kontact will run more efficiently.
Will Kontact 2 handle things, even a little, more swiftly?
I LOVE my RECEPTOR.
And I don't care how long it takes to cold-boot.
My concern is with Native Instruments' Kompact - damn it's slow, and switching from Multi to Multi...
I've adjusted my Sample Rate down to 44.1 kHz.
I've adjusted my Sample Buffer Size down to 128 Samples.
I disabled Z-load (I don't remember if it was Rick or Dan that said to do so)
I don't use DFD in instances with Kompact...
DAN ~ Does the above 'appear' to be the most efficient set-up?
It is Kompact that causes my long wait times.
I'm on Receptor 1.3 2 and was told that Kontact will run more efficiently.
Will Kontact 2 handle things, even a little, more swiftly?
JV
-
- KVRAF
- 3971 posts since 19 Apr, 2005 from Brissie
I was comparing the two, and saying (as Dan has said) that trying the same process on a DAW would be slower.JayVee wrote:This is for stage performance, no DAW.
I don't expect instant changes (although I get them when only one plug-in is used - other than Kompact)
But I'd be much happier with 5 to 8 seconds.
So your problem isn't Receptor at all, it's the size of your sample library...
I've joined Lurkers Anonymous.
-
- MUSEician
- 682 posts since 20 Aug, 2004 from California
I have good news and bad news. The bad news is that Kompakt will take a long time to load its samples, and there is nothing we can do to change that. I did not compare it with the new Kontakt, but even Kontakt is faster, it is still pretty slow.
The good news is that we are always working on adding new fetures and improving performance. In the upcoming version (the one after 1.4), the switching between multi patches will be greatly improved. You will still have to wait a long time for your first multi to load, but after that it will be faster.
z-load actually speeds up things. It does it by caching the plug-ins in memory. Kompakt takes a long time to instantiate, then it takes even longer to load the samples. With z-load after you instantiated Kompakt once you will wait only for the samples to load, and that is faster than waiting for both instantiation and sample loading.
The problem is that by caching instances, z-load uses memory. If your multis are very, very big, you may run into problems loading them with z-load enabled after you already used a bunch of other plug-ins. You should try with both z-load enabled and disabled. If you do not run into lots of "memory is getting low" messages from Kompakt, then use z-load and it will be faster. If you do get these message, then turn z-load off. It will be slower, but you won't run out of memory, and it will be more reliable.
Again, we will make things better and bettter with each release.
The good news is that we are always working on adding new fetures and improving performance. In the upcoming version (the one after 1.4), the switching between multi patches will be greatly improved. You will still have to wait a long time for your first multi to load, but after that it will be faster.
z-load actually speeds up things. It does it by caching the plug-ins in memory. Kompakt takes a long time to instantiate, then it takes even longer to load the samples. With z-load after you instantiated Kompakt once you will wait only for the samples to load, and that is faster than waiting for both instantiation and sample loading.
The problem is that by caching instances, z-load uses memory. If your multis are very, very big, you may run into problems loading them with z-load enabled after you already used a bunch of other plug-ins. You should try with both z-load enabled and disabled. If you do not run into lots of "memory is getting low" messages from Kompakt, then use z-load and it will be faster. If you do get these message, then turn z-load off. It will be slower, but you won't run out of memory, and it will be more reliable.
Again, we will make things better and bettter with each release.
Dan Timis
Software Developer
Muse Research, Inc.
Software Developer
Muse Research, Inc.
-
- KVRist
- 43 posts since 20 Sep, 2005 from Stockholm, Sweden
Shouldn´t DFD make loading times faster in Kompakt (because it don´t have to load the whole sample, just the first part of it)?
I have a similar issue with my Colossus setups, but not like 20 secs, more like 10. Someone mentioned that you could (if you have enough RAM) make a superbig multi with all the sounds you are using and turn off the cannels you are not using, and then on again when you need them. That way you only have to load them once. I haven´t tried that yet, it might work, but i guess that it means you have to use a monitor-mouse live too, at least to be fast. Maybe you have too many setups/set to do this and I guess that changing betweed such mega-mustis in a set is impossible, it would take forever.
Andreas
I have a similar issue with my Colossus setups, but not like 20 secs, more like 10. Someone mentioned that you could (if you have enough RAM) make a superbig multi with all the sounds you are using and turn off the cannels you are not using, and then on again when you need them. That way you only have to load them once. I haven´t tried that yet, it might work, but i guess that it means you have to use a monitor-mouse live too, at least to be fast. Maybe you have too many setups/set to do this and I guess that changing betweed such mega-mustis in a set is impossible, it would take forever.
Andreas
