There's probably a reason for this behavior that perhaps someone who knows more than I do can elaborate on
This is on a PC, Win7/32, although it does the same thing in XP. I don't have a mac, but I'd be curious if the same thing happens
You'll need to have Live 9 installed "along side" Live 8, on the same computer, or you'll have to find a way to get the Live 8 "Construction Kits" folder on to the machine w/ 9.
1. Easiest way is to open Live 8 >>> Library>>>Clips>>>Construction Kits.
2. Right Click the "Construction Kits" folder, select "Open In Explorer".
3. Close 8, wer're done with it.
4. Open Live 9.
5. In the browser, navigate to Places>>>User Lbrary.
6. Create a new folder, call it "Sets"
7. Create a folder inside Sets called "Construction Kits".
8. Arrange the Live 9 & Windows Explorer windows so that you can select all of the .als files in the Live 8 "Construction Kits" windows explorer folder and drag them into the newly created "Construction Kits" folder in the Live 9 browser.
9. Drag 'em in.
Both of my system pretty much poop their 'jammies as soon as the mouse cursor moves over the Live 9 window. The cores peg, the hardisk goes into warp factor 7, and the fans come on & stay on.
After about 5 minutes, Live 9 becomes responsive again, and displays a dialog indicating that the files are actually being copied, which, eventually they are.
Go ahead & delete the Construction Kits folder & the .als files in Live 9's browser.
1. Create a new folder in Sets called "foobar".
2. Right-click it, and Open In Explorer.
3. Go to the Windows Explorer from Step 2 in the previous section.
4. Select all the .als files and drag them into the other Explorer window (foobar).
5. NOTE: You have MOVED the files here so don't delete them yet!!
On my systems, the move is instantaneous & they show up (get indexed, I guess...) in the Live 9 browser within about 20 seconds or so.
Wierd.
But wait, there's more!
1. Drag those files BACK to the original folder they came from.
2. Now, select the all, but this time Copy & Paste them into the Windows Explorer "fubar" folder.
On my system, Live 9 is still out to lunch, 15 minutes later.
But it gets even better!
If, in the previous section, you Select All, Right-Drag the files to the foobar window, and choose "Copy Here" from the context menu, it works properly with no cpu/harddisk torture...
I'm baffled.
Can anybody confirm/explain this?
Why Does This Bring a Quad Core CPU to it's Knees?
Re: Why Does This Bring a Quad Core CPU to it's Knees?
Are you monitoring CPU usage as this happens? Are you sure its not the HDD locking up?
Re: Why Does This Bring a Quad Core CPU to it's Knees?
We're talking about 19 files that are less than 1 megabyte apiece. There isn't a hd you can buy today that doesn't have 10 times that in cache alone, so I'm at a loss to understand why transferring those files would strain a modern hd.
Not sure what you mean by a HDD "locking up". Unless paging is involved, that shouldn't lock up the entire desktop, should it?
The machines in question have 4gb of RAM, no other apps running, so nothing should be paging out. Also, there are no temperature sensors on the HD per se in these computers, so the I'm guessing that the fans roaring is CPU related.
I can work the hd hard, i.e. un-raring a 100 part 4gb file, etc., and although the little hd is breathing pretty hard, the system is still responsive, albeit sluggish. What I've described above is different, more of a temporary "crash".
Regardless, I'm trying to see if anyone else can replicate this behavior, more specifically whether they see a difference between drag/drop vs copy/paste, dragging between windows vs dragging into Live's browser, etc.
I'm thinking there might be some issues w/ the new browser, particularly this new layer of abstraction added on top of the file system. Like others, I'd be happy if they'd just give us back the functionality of the 3 "File Browsers" in the 8xx Library.
It looks like they've tried to do something similar to what NI attempted w/ Kore2. It became such an Achilles heel and created such a support nightmare for them that I really believe that's why it got shelved, not to make room for Maschine as many speculate. Kore2 was a fantastic idea that was crippled by a non-sustainable filesystem/Library abstraction layer. Every upgrade or 3rd party install potentially murdered your meticulous filing/categorization of your sounds often creating duplicate/triplicate entries, and frequent (and long...) database rebuilds were routine. Sounding familiar?
I'm aware of the folks saying Live 9 is cooking their USB HD's w/ terabyte-plus sample libraries taking entire days to catalog. This is different. These are test installs of the 9x trial on freshly formatted, empty hd's. I was just trying to put some 8.xx content back in to play with. So not sure what's up...
Not sure what you mean by a HDD "locking up". Unless paging is involved, that shouldn't lock up the entire desktop, should it?
The machines in question have 4gb of RAM, no other apps running, so nothing should be paging out. Also, there are no temperature sensors on the HD per se in these computers, so the I'm guessing that the fans roaring is CPU related.
I can work the hd hard, i.e. un-raring a 100 part 4gb file, etc., and although the little hd is breathing pretty hard, the system is still responsive, albeit sluggish. What I've described above is different, more of a temporary "crash".
Regardless, I'm trying to see if anyone else can replicate this behavior, more specifically whether they see a difference between drag/drop vs copy/paste, dragging between windows vs dragging into Live's browser, etc.
I'm thinking there might be some issues w/ the new browser, particularly this new layer of abstraction added on top of the file system. Like others, I'd be happy if they'd just give us back the functionality of the 3 "File Browsers" in the 8xx Library.
It looks like they've tried to do something similar to what NI attempted w/ Kore2. It became such an Achilles heel and created such a support nightmare for them that I really believe that's why it got shelved, not to make room for Maschine as many speculate. Kore2 was a fantastic idea that was crippled by a non-sustainable filesystem/Library abstraction layer. Every upgrade or 3rd party install potentially murdered your meticulous filing/categorization of your sounds often creating duplicate/triplicate entries, and frequent (and long...) database rebuilds were routine. Sounding familiar?
I'm aware of the folks saying Live 9 is cooking their USB HD's w/ terabyte-plus sample libraries taking entire days to catalog. This is different. These are test installs of the 9x trial on freshly formatted, empty hd's. I was just trying to put some 8.xx content back in to play with. So not sure what's up...
Re: Why Does This Bring a Quad Core CPU to it's Knees?
I have the same issue , more or less.
having win7 64 bit, live 9 and latest 9 beta, quadcore cpu, 4gb ram and, drive c: and d: are ssd. Dragging just one song into session view lets live9 stuttering, even the buffering. you can wath live drawing the curve in chunks. I see often the message in the menuebar `not responding` ..and the mouse pointer is presenting its circle for a while.
cmon ssd and quad core cpu. no paging happens.
i already know that live will stutter if at startup the msg appears creating new live set and it take ages till the windows pops up
that is totally strange behavior...
having win7 64 bit, live 9 and latest 9 beta, quadcore cpu, 4gb ram and, drive c: and d: are ssd. Dragging just one song into session view lets live9 stuttering, even the buffering. you can wath live drawing the curve in chunks. I see often the message in the menuebar `not responding` ..and the mouse pointer is presenting its circle for a while.
cmon ssd and quad core cpu. no paging happens.
i already know that live will stutter if at startup the msg appears creating new live set and it take ages till the windows pops up
that is totally strange behavior...