I'm going to need to buy an external hard drive as my internal is getting full. I have many songs on my Kjams music folder and then i have many songs in a folder i created for VCD's called "Imports". When i move my library, can i just drag the "imports" folder over to the new HD? I see the documentation on transferring my Kjams music folder.
Thanks in advance
Switching out HD's
:)
yes but you'll have to make a symbolic link from the old "imports" folder to the new one on the other drive. an alias will NOT work.
see the section on "expert unix freaks"
http://karaoke.kjams.com/wiki/Moving
see the section on "expert unix freaks"
http://karaoke.kjams.com/wiki/Moving
interesting
Interesting indeed. I *am* a unix/linux freak, so that explanation made good sense. I've moved everything from a backup stored on a removable disk to a more permanent location on the removable disk, and that worked out OK.
Here's the rub - after running the Push Meta Data on the roughly 6000 files I was moving, about 90 of them now come up as "Corrupted Zip File" - I noticed that kJams was apparently zipping them as part of the Push process. These files were all originally ripped from SCDG with kJams, and were not previously reporting errors - I can't confirm that the songs in question were ever accessed as part of a show.
It's not a huge deal, because I have the disks, and can re-rip the songs. That brings up another good question - what's the best way to update a song with a better version of the same file - either non-corrupted, or if I have a disk with a bad rip (I do), re-ripping it and re-adding it? All my CDG ripping is currently happening in Audiograbber, due to hardware limitations, so any bad rips are certainly not kJams fault.
I know it's been a couple months since I've been in contact, but over that time, kJams has revolutionized my show, and I've fought through some serious insanity to keep it that way - I lost a 250gb HD in my powerbook, got it mostly backed up, and am now running a 10gb HD in there until WD sends me my replacement. (I may need to play with some licensing hijinks when that happens, as it will technically be the third HD that kjpro will be on - we'll cross that bridge when we get to it.)
Here's the rub - after running the Push Meta Data on the roughly 6000 files I was moving, about 90 of them now come up as "Corrupted Zip File" - I noticed that kJams was apparently zipping them as part of the Push process. These files were all originally ripped from SCDG with kJams, and were not previously reporting errors - I can't confirm that the songs in question were ever accessed as part of a show.
It's not a huge deal, because I have the disks, and can re-rip the songs. That brings up another good question - what's the best way to update a song with a better version of the same file - either non-corrupted, or if I have a disk with a bad rip (I do), re-ripping it and re-adding it? All my CDG ripping is currently happening in Audiograbber, due to hardware limitations, so any bad rips are certainly not kJams fault.
I know it's been a couple months since I've been in contact, but over that time, kJams has revolutionized my show, and I've fought through some serious insanity to keep it that way - I lost a 250gb HD in my powerbook, got it mostly backed up, and am now running a 10gb HD in there until WD sends me my replacement. (I may need to play with some licensing hijinks when that happens, as it will technically be the third HD that kjpro will be on - we'll cross that bridge when we get to it.)
to clarify...
I'm not necessarily putting kJams at blame for the corrupted zips. If (and I assume they were) the zips were possibly already corrupted on the old drive, which went haywire - then they were transferred to the external drive, they may well have been corrupted prior to the meta push. Still, it is interesting that during that process, no warnings were given that the original zips were corrupt - perhaps this is the point of this, that there could be a warning during the meta push if it runs into a corrupt zip.
:)
kjams tells you the moment it notices a corrupt zip file, always.