Ableton 6 0 7 for Intel Mac OS X v10 5 Leopard zip

Ableton 6.0.7 for Intel Mac OS X v10.5 Leopard Found it on another tracker. Posting it here, it works!

udp://tracker.openbittorrent.com:80
udp://open.demonii.com:1337
udp://tracker.coppersurfer.tk:6969
udp://exodus.desync.com:6969

plprado (2008-03-25)

I´m seeding it but here it show zero seeders... What should I do?

plprado (2008-03-25)

well, nevermind.

skitzo79 (2008-03-25)

does anyone have a key??

Anguilles (2008-03-25)

yep, i send it.

plprado (2008-03-25)

There's a "unlock.cfg" file included in the ZIP. And Instructions to use it as well...

Shunnabunich (2008-03-25)

So, by "for Intel", I assume it means PPC Macs are out of the question for this one? Damn.

Anguilles (2008-03-26)

If it's the same Live that mine (with the unlock.cfg) it will work for ever

hardstyledopey (2008-03-29)

Works on hack 10.4.10

tektuk (2008-04-15)

Copyright violation detected....
Like 5.2

kristoffer1989 (2008-04-17)

i can't get i to work. i don1t have that folder to put the unlock in. and it doesn't work to just create it either...
can someone please help?
serial for 6 or 7 please?
i really need live and i can't afford it at the moment.. please

piratedmoney (2008-04-20)

Does this work on Windows? HAHA

siocman (2008-04-21)

same problem as kristoffer1989..... please help

mathforlyfe (2008-05-05)

I had the same problem but I resized that you have to go to user's>(you're account)>library>Application Support then it should be there. You HAVE to go through you're account to get there. Hope this helps.

pocketaf (2008-05-13)

have anyone tried to instal 7th windows version of ableton with crossover on mac?
and maybe it succeed to someone?

kuakeli (2008-05-27)

Does anyone have the unlock key or keygen or something?? can't save or bounce before unlocking.. thanks

GreyMatters (2008-05-28)

Ok, i just got the Copy Violation Error about the illegal key. Seems to be an inherent problem, as I was surprised at first that my 5.2 UB was getting busted when 7 has been out for ages it seems. Although this is how I got my 5.2 back up and running, it might/should work (except for the different serial #'s) for newer and older versions. This is for Mac, no idea about PC except that you need to clean the registry.
Ableton runs a checksum when you're computer is connected to the internet (must be fairly random b/c I've been running Live for 6 months and I'm always connected via wireless). Ableton has sneaky Advanced TCP/IP.plist files hidden in the Preferences folder, and they are zero length too. This is how i got it working again using info from various forums on the web. Thanks to the genius of Voidet, Entomologist and PUNK-ska I got Live back fully running (and for good!) and hopefully you can too.
It should be noted that Ableton, when connected to the web, will catch the invalid key if the script is not correctly written. To be sure you can always disconnect from the web before using Live, but that;s a hassle so the script is a perfect solution. Following the other steps correctly will get Live up and running again, but it will only be a matter of time before Ableton runs a checksum and finds that its using an invalid key, yet again giving the Copy Violation Error, crashing Live, and ruining the track you were currently working on. Locking the "unlock.cfg" doesn't work, as it reports an error if you try to save a file. But if the script is working, then the script will then stay open and every five minutes will call the Unix copy command 'cp' to overwrite 'Unlock.cfg' with the working cracked one, thus for that file defeating any counting/flagging mechanism. I have it permanently running to re-copy the working cracked 'Unlock.cfg' file every 5 minutes - extremely low CPU usage too. Make sure you are not connected to the internet. After its working again, If you load files that have been saved with a (detected) cracked version, it will report back a Copy Violation Error and crash Live. New files should work fine.
1. First open up Terminal, found in your applications folder/utilities. Type (or copy/paste:
defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder
*that is two commands*
(this shows all files, including the hidden files, in each folder)
2. Go to your home directory, then click on library, then Preferences.
~/Library/Preferences/
3. Look for a file that looks like "Advanced TCP:IP 0000blahblahblah.plist" and delete it.
4. Delete the folder Ableton in the Preferences folder.
5. Go back into Terminal and type (or copy/paste) these two commands:
defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder
(this hides all the hidden files in each folder again)
******Alternatively to #1-5:
Run Terminal and type:
cd Library
cd Preferences
ls -al

GreyMatters (2008-05-28)

rm "Advanced TCP/IP.plist"
(or whatever the files name is, to delete these, for as many files there are of that type as necessary, but it should be a maximum of two. Make sure you have the double quotes for the file name as Unix takes names with spaces as parameters if unquoted).
6. Go to ~/Library/Application Support/Ableton/Live 5.2/Unlock/Unlock.cfg
and delete the file and the Unlock folder.
7. Open Live. The procedure above should have reset your Ableton. It should ask if you want to proceed in demo mode or enter a valid key. Choose to enter key.
-enter this serial:
4008-7527-B461-5C69-8A88-C075
8. Choose "Enter unlock code" and enter the following code (yes, there are strange characters in there):
%SPECLK -

GreyMatters (2008-05-28)

%SPECLK -

GreyMatters (2008-05-28)

%SPECLK /

GreyMatters (2008-05-28)

(%SPECLK /

GreyMatters (2008-05-28)

9. To unlock Operator, enter this serial:
A407-7107-A71D-5764-5106-A196
10. Again, select "Enter unlock code" and enter the following code:
11. There, so Live should now open fine. A new "unlock.cfg" has been input and the dreaded Advanced TCP/IP.plist file(s) has/have been removed. However, when connected to the net, Live is still susceptible to the Ableton checksum in the future.
***The only problem at this point will be that any Live files that are infected with the copyright file will not open correctly.
12. Somehow the Copy Violation Error checksum also modifies the 'Unlock.cfg' when it saves files, possibly a counter. I found an Applescript which copies over the 'cracked' Unlock.cfg back in every five minutes, thus resetting it. The script will stay open and every five minutes will overwrite 'Unlock.cfg' with the cracked working version, thus defeating any counting/flagging mechanism.
13. First of all, make a copy of the original cracked 'Unlock.cfg' file that is working fine to open Live, and paste it to any location other than Ableton's directory (I used my documents folder for simplicity).
14. Open script Editor and enter this:
on idle
tell application "Finder"
do shell script "cp '/{PATH TO THE COPY OF UNLOCK.CFG}/Unlock.cfg' '/Users/{YOUR USERNAME}/Library/Application Support/Ableton/Live 5.2/Unlock/Unlock.cfg'"
end tell
return 300 'Application' and set the checkboxes for 'Run Only', 'Stay Open' and if desired 'Startup Screen' (or choose to run script automatically on login, up to you, but I recommend for extra insurance).
15. Run the script to ensure it works. Double-click the file where it was saved. Select "run," and if it doesn't report back any errors but remains open, it should be working properly.

GreyMatters (2008-05-28)

OK so something the Pirate Bay website doesn't like something about the unlock code, so here's the link to where I found it:

GreyMatters (2008-05-29)

From the Ableton Website Forums
Topic: Copyright Protection Can't Use Live 7 but I Paid!
Tue Mar 25, 2008
User1: " Since 2 months now I a have a problem with Ableton 7 that I purchased
from the Ableton Website. Everytime I start the Program I get Message from Live saying ''A Copyprotection Violation has been identified. Please
contact...'' and I cant use the program! I tried reinstalling and installing Live 7.2 with a new Unlock Key and it worked for about 2 weeks. Now again the Message comes and I cant use Live. I tried the same again but it still doesnt work. Thats really bad since I use Live for producing, djing and many more...
and I paid for the Software! Ableton support doesnt even know what to do and leaves me with the problem.Thats not fair!!!"
User2: "So what did Ableton support say, specifically?"
User3: "A couple of weeks ago I started live after a crash I think and it came up in demo mode!!!! I had to authorize it again which worked but WTF?
User1: "To User2: The support asked me for the serial number, what they can check on my acount all the time if they want Confused
and then they said that I should use the beta version.
But it didnt fix the problem!!! To User3: Same here, it happend after a crash and since then its fucked! I think everyone should know that with Ableton there are many problems like that!"
User4: "Im having the same problem. Support gave me a new serial to use after telling me to trash the unlock file and reinstall, which fixed it for a few days. It started happening soon after i started using a plugin called Lucifer by Devine machine. Are you using the same plugin by any chance?"
User5: "The same thing happened to me with Live 7.0.3 and 7.0.2 during a basic session. A window poped up à la "a copy protection violation has been detected". After some email correspondence with the support I deleted all the preferences and unlocked Live 7 again. Since then it worked without a problem, although i am still feeling very uncomfortable about this whole thing.
The biggest problem is the way the copy protection worked (at least in my case): With the copy protection message coming up the audiostream IMMEDIATELY stopped and there was no way to save the current set. Imagine this to happen during a gig, what a horror. You have to fiddle for over half an hour to get things running again -> a night/business ruined.
This never happend with Live 6 which i am still using to play live. No way i am using Live 7 for live action if Ableton can not guarantee that the copy protection works as it should."
User4: "This also happens on Live 6 im afraid. I was advised by support to do the same "delete preferences and unlock file, delete and reinstall Live". The problem returned within an hour. The latest thing i've been told is to reinstall Leopard doing an "archive and install" as it might be related to a corrupt user profile. I gig every week so im screwed if this doesn't solve it.
the people its happen to are you all on Mac's? What version OS are you using? I was on 10.5.2 when this was happening. i've since heard there's issues with 10.5.2. Back to 10.5 at the minute. fingers crossed."
User5: "happened with winxp sp2 and live 7.0.3 & 7.0.2
i did swap the cpu 2 months before it happend but neither did i have to reauthorize nor did the the challenge code change so it can't be the cause of the copy protection error."

pocketaf (2008-06-03)

GreyMatters
Thank you very much and Punk-SKA
i did everything step by step with this version it works ok but i have some problems with scripting.
i entered this:
on idle
tell application "Finder"
do shell script "cp '/{PATH TO THE COPY OF UNLOCK.CFG}/Unlock.cfg' '/Users/{YOUR USERNAME}/Library/Application Support/Ableton/Live 5.2/Unlock/Unlock.cfg'"
end tell
((return 300) i tried to write in many variations)
changed everything like it should be on my computer but when i press compile or run it show me: Syntax Error Expected end of line but found end of script....
help one more time plz. coz i heard that Live crashing even when you fixed it with serials

m3m3148 (2008-08-11)

pocketaf... look a little bit more closely...
on idle
tell application "Finder"
do shell script "cp '/{PATH TO THE COPY OF UNLOCK.CFG}/Unlock.cfg' '/Users/{YOUR USERNAME}/Library/Application Support/Ableton/Live 5.2/Unlock/Unlock.cfg'"
end tell
inside the {} brackets, you should edit the content to say /Users/pocketaf (or whatever your User Name on your computer is)/Documents (or wherever you copied the unlock.cfg file to)/Unlock.cfg.... don't copy this verbatim!!!
Also, if you have a different version of Ableton, don't write Live 5.2 (etc..)
also, you have to write 'end' at the end of your script...

m3m3148 (2008-08-11)

that being said... Grey Matters, I am having a few syntax errors with the script myself.. the variable Users not being defined.... thoughts?

Evil_Laserlord (2008-10-16)

Having some problems with syslogd hogging CPU, but it downloaded quickly and registered fine. Any ideas on where to find an update/solution to the syslogd problem?

decliki (2008-11-01)

Trying to get the above procedure to work on this version (6.0.7), I can't seem to find a working serial though, so I can't get past step 7.
Both KCN:s and I-serialreader:s serial numbers, and the serial which is given while using cracked mode are considered invalid by the app. A working serial for version 6.0.7 ?

caynick (2008-11-23)

hey thanks for this great release
anyone know where we get the banks for the instruments? i cant do anything with mine at all...
cheers
minxparties@gmail.com

badfox88 (2008-11-25)

for people stuck without serials... I have just gotten the copy violation & the serial codes were listed in the URL it sent me to! haha
I just followed GreyMatter's steps & used these serials instead (works fine with the unlock code too)
Here are the ones i used anyway:
ABLETON LIVE 6.0.7- 3006-3604-3417-2FC4-C38C-88FD
OPERATOR- 3404-B10E-E829-A12C-698C-CCAE
SAMPLER- 3415-910A-78B3-B7B4-A319-DB2A
ESSENTIAL INSTRUMENT COLLECTION- 3802-1600-7A3A-66F3-4EE5-B9CC
thanks to grey matter for helping me out & i hope this helps everyone else

katzabuki (2009-01-17)

@ GreyMatters: First of all thanks for all your info and explanations!!
Some thoughts:
I've downloaded ableton 6.0.7 some time ago.
Only yesterday I got the copy violation.
Now about your instructions:
1. I'm not familiar with Applescripts and Script Editor, but just like m3ect. I get syntax errors, and I also don't get this "run 300 'Application'" instruction.
So: I take it that the applescript starts with "on idle" and ends with "tell end" When I copy/paste it into Script Editor, I get syntax errors.
2. Since you explained so clearly how the copy violation thing works (big up!!!), we can think with you on a/your solution. And this is my thought/question: are steps 7 to 11 not obsolete? Step 13 made me think this.
I mean: with the download of Ableton comes a 'original cracked 'Unlock.cfg' file that is working fine to open Live', and instructions:
1.Drag and drop Live.app (111,4 Mb) into your programs folder.
2.Store Unlock.cfg in ~/Library/Application Support/Ableton/Live 6.0.7/Unlock/Unlock.cfg
3.Start the application and have fun!
So there you go, and have fun, untill the dreaded copy violation pops up.
At that point, we can follow your instructions step 1 -6 to get ridd of this Advanced TCP/IP.plist file(s) and the corrupted Unlock.cfg.
But now we need to unlock Live again.
You come up with step 7-11.
But why not simply use the original, uncorrupted unlock.cfg that came with the download?? Unzip the download again, and it's there. Repeat 'Store Unlock.cfg in ~/Library/Application Support/Ableton/Live 6.0.7/Unlock/Unlock.cfg', just as you did the first time, and your unlocked again in one simple go. Now this works for me. But... like you stated: 'when connected to the net, Live is still susceptible to the Ableton checksum in the future.' So I did get unlocked without steps 7 - 11 in no time, using the original cracked unlock.cfg - but... got a copy violation in no time as well. Now - so I thought -if you are right, I only needed to get ridd of the newly corrupted Unlock.cfg, and replace it with the original one that came with the download. Which indeed got Live running again. In other words: I only needed to do manually what your script would do automatially. So that is why getting that applescript working is so important. I hope you can come back on that!! (and on my 'theory')!!
To resume:

katzabuki (2009-01-17)

To resume:
- Download Ableton.
- Follow the install instructions in the readme file:
1. Drag and drop Live.app (111,4 Mb) into your programs folder.
2. Store Unlock.cfg in ~/Library/Application Support/Ableton/Live 6.0.7/Unlock/Unlock.cfg
3. Start the application and have fun!
4. Read the following note
*******NOTE**********
IT IS POSSIBLE THAT LIVE WILL LOCK UP AFTER A CERTAIN PERIOD OF TIME, DUE TO THE COMMON COPY VIOLATION SECURITY "PROBLEM"
CONSIDER BUYING THE SOFTWARE AT: WWW.ABLETON.COM
- When this 'copy violation problem' occurs: follow GreyMatters steps 1- 6 to get ridd of this nasty Advanced TCP/IP.plist file(s) and the corrupted Unlock.cfg. These steps "should have reset your Ableton."
- Since Ableton is reset, you need to unlock again. Use the original cracked Unlock.cfg that came with the download (unzip again). Store this uncorrupted Unlock.cfg in ~/Library/Application Support/Ableton/Live 6.0.7/Unlock/Unlock.cfg.
- You can run Ableton without any problem, UNTIL......... you have to do all this again, and again, and again
- So what we need, is to get that Applescript running to do that for us, am I right (PLEASE CORRECT ME WHEN I'm NOT)!!
- HELP US GREY MATTERS - you got us so far already...!! What about the syntax errors?? How to write this applescript??

katzabuki (2009-01-17)

So I found the missing link - I guess GreyMatters got sloppy.
This is what he wrote on another site:
Open script Editor and enter this:
on idle tell application "Finder" do shell script "cp '/{PATH TO THE COPY OF UNLOCK.CFG}/Unlock.cfg' '/Users/{YOUR USERNAME}/Library/Application Support/Ableton/Live 5.2/Unlock/Unlock.cfg'" end tell
return 300 ( 'Application' and set the checkboxes for 'Run Only', 'Stay Open' and if desired 'Startup Screen' (or choose to run script automatically on login, up to you, but I recommend for extra insurance)
Now I've got the script running!
Wonder if this will beat the "copy violation problem"

katzabuki (2009-01-17)

No GreyMatters didn't get sloppy: it's a HTML-thing or whatever you call it. He used signs which makes a part of the text get lost, so I see.
THE CORRECT APPLESCRIPT IS THIS:
Open script Editor and enter this:
on idle
tell application "Finder" do shell script "cp '/{PATH TO THE COPY OF UNLOCK.CFG}/Unlock.cfg' '/Users/{YOUR USERNAME}/Library/Application Support/Ableton/Live 5.2/Unlock/Unlock.cfg'" end tell
return 300 (......this is 5 minutes in seconds until next loop)
end idle
Replace the items enclosed in the curly braces {...} with appropriate path/names. Then in script Editor 'Save As' - 'Application' and set the checkboxes for 'Run Only', 'Stay Open' and if desired 'Startup Screen' (or choose to run script automatically on login, up to you, but I recommend for extra insurance)

katzabuki (2009-01-17)

I don't know why this is getting srewed up all the time. I'll try again.
THE CORRECT APPLESCRIPT IS:
Open script Editor and enter this:
on idle
tell application "Finder"
do shell script "cp '/{PATH TO THE COPY OF UNLOCK.CFG}/Unlock.cfg' '/Users/{YOUR USERNAME}/Library/Application Support/Ableton/Live 5.2/Unlock/Unlock.cfg'"
end tell
return 300 (......this is 5 minutes in seconds until next loop)
end idle
Replace the items enclosed in the curly braces {...} with appropriate path/names. Then in script Editor 'Save As' - 'Application' and set the checkboxes for 'Run Only', 'Stay Open' and if desired 'Startup Screen' (or choose to run script automatically on login, up to you, but I recommend for extra insurance)

katzabuki (2009-01-17)

PFFFFFFFF: so that last one is the correct script.
Good Luck!!!

nocircle (2009-01-19)

My scripts are correct but I am having issues with the serial number.
I get the same ones as were listed by badfox, but they still get challenged. I upped the repeat cycle to 79 seconds just in case.
Here's part of the Ableton log.txt found in /users/(me)/library/preferences/Ableton
1183661 ms. LSongAgent: Begin Destructing
1183662 ms. LSongAgent: Begin SetSongUnit
1183665 ms. LSongAgent: End SetSongUnit
1183692 ms. Audio time allocations: Midi Delay: Capacity/Used/Failures: 74898/0/0
1183692 ms. Audio time allocations: InterDomainEvents: Capacity/Used/Failures: 47662/0/0
1183693 ms. ALAudioInOut: Stop started
1183694 ms. ALAudioInOut: Begin of UpdateAudioStateStatic
1183694 ms. ALAudioInOut: --Audio state--
1183694 ms. ALAudioInOut: In: 0 Out: 0
1183694 ms. ALAudioInOut: Sample Rate 44100.000000
1183694 ms. ALAudioInOut: End of UpdateAudioStateStatic
1183695 ms. ALAudioInOut: Stop finished
1183695 ms. LSongAgent: End Destructing
1183697 ms. AMidiIO: Start CloseAllActivatedDevices
1183698 ms. AMidiIO: End CloseAllActivatedDevices
1183698 ms. ALAudioInOut: Destructor started
1183698 ms. ALAudioInOut: Destructor finished
1183736 ms. Default App: End OnQuit
The Destructor action doesn't happen when Live is closed normally... only when the application crashes due to the alleged copy violation.
Any advice?

nocircle (2009-01-19)

Ok, much thanks to everyone on here.
First, I am still getting the copy violation issue.
I follow steps 1-5, BUT, even though I am showing all files and folders, the Advanced TCP:IP blaaajdsfasd file is not present.
Step 7 is where I encounter my second issue. I have tried both the serial number encountered in the URL when directed to the ableton site as well as the serial number that the original unlock.cfg file has (which badfox posted). Neither work so I am unable to proceed fully.
So far, I seem to be okay with new files, but older files that were used prior to the initial copy protection crash will crash ableton with the copy protection violation notice within 2.5 minutes of opening.
I have adjusted by script to 79 s from the recommended 300. Its cpu usage is still minimal.
My next step will be to tinker with older saved files to see what can be removed from the project that allows the .als projects to run without causing the crash.

nocircle (2009-01-19)

I deleted all the Ableton Project Info folders as well as .asd files.
I am now only encountering crashes with old files when I enable recorded midi instruments in older files.

katzabuki (2009-01-21)

@ Nocircle: I'm thinking and trying with you (and earlier suggestions).
This is what I came up with so far.
- about the Advanced TCP:IP blaaajdsfasd file: apparently you only have to delete that once. I mean after you crash, and get Live running again, that file isn't getting installed again.
- about the serials: I just don't understand why you need them...?? Using the (1) serial and the unlock.cfg that I used during the first installation, works fine for me to unlock after crashing now too.
- about the script: I don't know if we need it.
At this point, after experimenting, this is how it went and what seems (keep fingers crossed) to work for me.
1. Downloaded Live about a year ago. Installed with serial from serialbox and unlock.cfg that came with download. Everything fine, until....
2. I - only recently! - got copy violated.
3. Followed GreyMatters' step 1-6 to get rid of the Advanced TCP:IP blaaajdsfasd file and the unlock.cfg.
4. Used the original unlock.cfg (unpacked the downloaad again) and the serial from serialbox to get Live running again in one simple go.
5. Again Live works fine, but: I got COPY VIOLATED when using old files. New files seems OK.
6. To get the old files running again:
- Start a new project
- Go to Live's Browser and find the old, corrupted project file you want to use again - it's a ABCXYZ.als file.
- Click the triangle that exposes all midi an audio files of the project.
- Drag and drop those files in Track Title Bar of the Session View Selector. This way you reconstruct your old set (song/track) as a new set (song/track).
- Save this set.
- Presto!!
7. Live is working again, old sets are working again. Until.... That is were the script comes in. Is that necessary? And what is the logic about copying every 5 minutes, if Ableton makes random checks?? I don't think that it works that way. There is probably a count, and I think as far as time's concerned, this is more a thing about weeks or even month, than minutes. So I got rid of the script, and will replace the unlock.cfg with a copy manualy every 2 weeks or so manualy.
Good luck - and the ultimate solution stays very welcome!!!

katzabuki (2009-01-21)

This is my overall thought.
Live cracks work, until you get a copy violation.
Getting Live running again is very simple: reset (get rid of the unlock.cfg) and reinstall. Because you reset, you can use the initial serial and unlock file.
Now Live works, since you made a new clean install, but the files you saved with the old copy violated Live are corrupt - you have to 'reset' them too. I explained above how yoy can do that.
So...
In short: if you get a copy violation, you're fucked, and need to reset both Live AND all your saved sets.
So it matters to prevent to get copy violated.
I hope replacing the unlock.cgf with a copy every 2 (or 1,3,4,???) weeks can do that.
Good luck.

neon_electro (2009-01-22)

I know that in Mac OS X Leopard, there is a feature called "sandboxing" where you can block an individual application's access to writing/reading files, or more pertinent to this thread, INTERNET ACCESS.
all it involves is two main steps:
1) creating a sandbox file- very easy: simply copy this text into a new text file (including parentheses):
(version 1)
(debug deny)
(allow default)
(deny network*)
now save that under whatever name you choose, but make sure you have a ".sb" extension for the file. for example, you could name it "ableton.sb". Additionally, make sure the icon for the file changes to a blank document. if it still shows "txt" on the document, then it still has the .txt extension on it (it would be ableton.sb.txt and would not work). Note that the you might look at the name and it would say "ableton.sb", but the .txt extension can be hidden. It will not work if the .txt extension is there.
now that you have your sandbox file, place it anywhere you want to keep it.
2) running Ableton within the sandbox- using the sandbox-exec command, we can tell OS X to run an application within our sandbox file. Specifically though, you need to use the UNIX executable file that is inside every Mac app.
to find Live's executable file, go to the Live application you use to open the app. Right-click (or control-click) the app, and choose "Show Package Contents". Go to the Contents, then MacOS folder. Inside is Live's UNIX executable. it should have a gray icon with a green "exec" in the top left corner.
Now, you can simply open Terminal, type in "sandbox-exec -f" then a space, then drag the actual sandbox file from the Finder to the Terminal window. This will put the location of the file into text so you don't have to. Another space, and then drag the Live UNIX executable file into the terminal window. Run the command, and Live should start up. You won't notice anything different because Live doesn't normally tell you when it's trying to access the internet. If you try this with an app like Safari, it will not allow you to go to any sites because it will be restricted.
You can additionally make an AppleScript to run the command, save the AppleScript as an app, and place it on your dock in Live's place, allowing you to sandbox Live whenever you run it.
Hope this helps! I'll check back here if there are any questions.

neon_electro (2009-01-22)

p.s. I started looking into this stuff after my own copy of Live got the copy protection bug. To fix Live after the copy protection bug hits, you still need to follow GreyMatters' advice on removing the AdvancedTCPIP file and replacing the unlock.cfg file with a new one.
My advice is for when you have a working, unlocked version of Live, and you want to restrict it from accessing the Internet. As far as I know, this shouldn't crash it because it would be equivalent to running Live with AirPort turned off, or your Ethernet cable unplugged. Only in this case, you can run your internet apps at the same time :)

neon_electro (2009-01-22)

one more comment, this time though, I'm having a problem with AppleScript:
If I want AppleScript to perform a shell script, and a file path contains a space in one of the folders, how do I tell AppleScript there's a space in the folder?
If I just typed the command into the Terminal, I would use a \ character after the word before the space, a space, and then the next word (example. .../Ableton\ Live/...). AppleScript does not like this one bit, and when I try to compile a script with this syntax in it, it tells me "Expected ?"? but found unknown token." and highlights the first instance of me using that \ character.
Any AppleScript pros out there?

katzabuki (2009-01-23)

@ Neon Electro: interesting advice, this sandboxing!
@ Eveybody: when copyviolated you have to do 3 things.
Follow GreyMatters' advice on removing the Advanced TCPIP file and replacing the unlock.cfg file, and copy your old Live sets in new ones. I'm still up and running!
After GreyMatters' steps 1-6, you have reset Live and can use the original unlock.cfg and serial - no problem!

zambranofan (2009-01-24)

Hey Neon Electro--sandboxing really must be the way to go here, and this would be useful for lots of other applications as well. However, I'm having problems. I followed your instructions exactly, and here's what I'm getting out of the terminal:
mycomputer:~ me$ sandbox-exec -f /Live\ 6.0.7/ableton.sb /Live\ 6.0.7/Live.app/Contents/MacOS/Live
sandbox_init: Cannot find a supported language version, try '(version 1)'.
The .sb file I created was copy-and-pasted exactly as you directed...with the (version 1) and all. There doesn't seem to be very much useful documentation on the web on sandboxing in Leopard, so I'm pretty much stuck. Any ideas?

ridersofdepression (2009-01-29)

Ok... used most of the afternoon to get this working... wasn't hard at all. I made a short resumé of the grey matter+serials wich works and unlock codes
Cleanup:
Clean up the unlock.cfg in -library/application support/ableton/live6.0.7/unlock
1. First open up Terminal, found in your applications folder/utilities. Type (or copy/paste:
defaults write com.apple.finder AppleShowAllFiles TRUE
killall Finder
*that is two commands*
(this shows all files, including the hidden files, in each folder)
2. Go to your home directory, then click on library, then Preferences.
~/Library/Preferences/
3. Look for a file that looks like "Advanced TCP:IP 0000blahblahblah.plist" and delete it.
4. Delete the folder Ableton in the Preferences folder.
5. Go back into Terminal and type (or copy/paste) these two commands:
defaults write com.apple.finder AppleShowAllFiles FALSE
killall Finder
Serials:
ABLETON LIVE 6.0.7- 3006-3604-3417-2FC4-C38C-88FD
OPERATOR- 3404-B10E-E829-A12C-698C-CCAE
SAMPLER- 3415-910A-78B3-B7B4-A319-DB2A
ESSENTIAL INSTRUMENT COLLECTION- 3802-1600-7A3A-66F3-4EE5-B9CC
Unlock codes (same for all)
%SPECLK -

ridersofdepression (2009-01-29)

Unlock codes (same for all)
%SPECLK -

ridersofdepression (2009-01-29)

Unlock codes (same for all)
%SPECLK -

ridersofdepression (2009-01-29)

neon_electro (2009-02-05)

Back again, I'm not sure how scientifically I've tested the sandboxing technique, I got an error again but I'm pretty sure I happened to open one of the "corrupted" projects.
I think the best way to test it would be to use a fresh install of Mac OS X, fresh install of Live w/ sandboxing put in place. Currently, I have another machine, so I'm using that one without internet on.
@zambranofan: Hmm. :( I've since deleted my sandbox file, so I tried following my own directions. I copied the text, made a new .sb file, and tried running the command again, and it works for me. What version of Leopard are you running? I'm on 10.5.5 at the moment, been meaning to get 10.5.6... hehe.

katzabuki (2009-03-01)

Okay: got violated again.
The good thing is: I know now how to get back on track within 5 minutes:
- Get rid of the hidden TCP:IP etc file
- Replace the unlock file with the one that comes with this download.
- Open a new project, go to the file browers, find the copy violated project, drag all the audio en midi tracks back in the project, and save.
How to prevent from getting copy violated again: no idea.
One thing: if the project has more version of a track, they are all corrupt.
NOTICE: the copy violated files all contain in the folder "Ableton Project Info" a file called "IndexMac.db". Anybody any idea if deleting that file clears the project after cleaning up??

neonzebra (2009-03-16)

Just curious: after following the multitude of great advice on here, has anybody tried using the app Little Snitch to block ableton from connecting to the internet? Little Snitch's ability to do that seems dubious, considering the great length some people on here have gone to, what with creating sandbox files, scripts etc. I will give it a try myself, but I can't guarantee that my results will be accurate either way. Thank you everyone for seeding and for collectively working on this problem.

gangreneghost (2009-09-25)

@neon_electro Any word on the success of the sandboxing? You asked how to pull it off in an applescript before... it was a while ago but, incase you still want to know:
1)open the script editor
2)type the following:
do shell script "sandbox-exec -f
3)save it as an application
4)Use this to open Live from now on.
This could be useful... provided sandboxing works.

gangreneghost (2009-09-27)

Uh... guess it doesn't. Damn.