[{"data":1,"prerenderedAt":293},["ShallowReactive",2],{"docs":3,"doc:\u002Fdocs\u002Fguide\u002Fquestions":88},[4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84],{"path":5,"title":6,"description":7},"\u002Fdocs\u002Fcodemods","Codemods","A codemod is a small program that changes Live Sets. livesaver runs it over folders of sets, shows\nwhat would change, and with --apply writes the changes the same way every livesaver command\ndoes: the result must be well-formed XML, Live's backup scheme is followed\n(Backup\u002F\u003Cset> [date time].als), the run is journaled, and livesaver undo \u003Crun> puts every set\nback.",{"path":9,"title":10,"description":11},"\u002Fdocs\u002Fformat","Ableton Live file formats — what livesaver relies on","Facts collected from Live's own files (verified against real sets) and public research\n(Steinberg VST3 SDK, JUCE, Ableton's maxdevtools). Each page names its sources.",{"path":13,"title":14,"description":15},"\u002Fdocs\u002Fformat\u002Fcontainers","Containers and id spaces","How Live's files are packed: which are gzip-compressed XML and which are binary, what lies beside them, and how the ids inside a document are numbered.",{"path":17,"title":18,"description":19},"\u002Fdocs\u002Fformat\u002Ffileref","FileRef","A \u003CFileRef> locates one file. It appears in many containers, but only some are real dependencies.",{"path":21,"title":22,"description":23},"\u002Fdocs\u002Fformat\u002Ffinder","Finder tags, comments and plug-in bundles (macOS)","What status, reorg and the plug-in inventory read and write outside Live's own files.",{"path":25,"title":26,"description":27},"\u002Fdocs\u002Fformat\u002Ffingerprints","Fingerprints","How Live recognises a file again: the size and the checksum it stores with every reference, where vendors and pack updates break that, and what livesaver compares instead.",{"path":29,"title":30,"description":31},"\u002Fdocs\u002Fformat\u002Flive-setup","Live installation and library locations","Where Live keeps its app resources, its library folders and its own databases, and how livesaver finds them without being told. Everything below was read on a Mac; Windows is at the end, from Ableton's documentation.",{"path":33,"title":34,"description":35},"\u002Fdocs\u002Fformat\u002Fplugins","Plug-ins in Live Sets","How a Live Set stores a plug-in in each format, how the same plug-in is recognised across formats, and what an upgrade from VST2 to VST3 has to carry over.",{"path":37,"title":38,"description":39},"\u002Fdocs\u002Fformat\u002Fversions","\u003CAbleton> root attributes per Live version","The root is \u003CAbleton MajorVersion MinorVersion SchemaChangeCount Creator Revision>. Creator is \"Ableton Live x.y.z\".",{"path":41,"title":42,"description":43},"\u002Fdocs\u002Fguide\u002Fbrowser","In the browser","The app also runs on its own, as a page in your browser. It reads the folders you give it and changes nothing: good for a first look, or on a computer where you cannot install anything. In Chrome and Edge it can also fix samples and upgrade plug-ins, if you switch that on: see Fixing in the page.",{"path":45,"title":46,"description":47},"\u002Fdocs\u002Fguide\u002Fcommand-line","The command line","Everything the app does, the livesaver command does too, and more: project status in Finder, a catalog of your sets to search, and codemods. Every command only plans unless you pass --apply.",{"path":49,"title":50,"description":51},"\u002Fdocs\u002Fguide\u002Fgetting-started","Getting started","livesaver finds the samples your Ableton Live sets have lost, collects them into their projects, and shows which plug-ins are missing. This page takes you from nothing to your first scan.",{"path":53,"title":54,"description":55},"\u002Fdocs\u002Fguide\u002Fhistory","History and undo","Everything livesaver changes is written down as a run: what it was asked, every step it took, and the original of every set it rewrote. That is what makes an undo possible, also weeks later.",{"path":57,"title":58,"description":59},"\u002Fdocs\u002Fguide\u002Fmissing","When samples stay missing","A fix can only find what is in the folders it searches. What stays missing is listed by where it came from, because what helps differs: a pack is installed again, an old drive is plugged in, a folder is added.",{"path":61,"title":62,"description":63},"\u002Fdocs\u002Fguide\u002Fplugins","Plug-ins","Live finds a plug-in by its format and its id, never by its name. livesaver reads which plug-ins your sets use and compares them with what is installed, the way Live does, so you know before you open a set what will be missing in it.",{"path":65,"title":66,"description":67},"\u002Fdocs\u002Fguide\u002Fquestions","Questions and answers","Short answers to what comes up first. If yours is not here, ask on GitHub.",{"path":69,"title":70,"description":71},"\u002Fdocs\u002Fguide\u002Fsafety","How your work is kept safe","livesaver edits the files your music lives in. These are the rules it keeps, so that nothing is lost.",{"path":73,"title":74,"description":75},"\u002Fdocs\u002Fguide\u002Fsamples","Fix missing samples","A set that has lost its samples opens in Live with “Media files are missing”. livesaver finds the files again by what they are, puts them into the project, and points the set at them, for every project at once.",{"path":77,"title":78,"description":79},"\u002Fdocs\u002Fguide\u002Fwindows","livesaver on Windows","livesaver is made and tested on a Mac. Windows is new: it is built from what Ableton documents about Live on Windows and from the way sets that were saved on Windows store their files. No one has tried it on a Windows computer with Live yet. This page says what is there, what differs from a Mac, and what is not known.",{"path":81,"title":82,"description":83},"\u002Fdocs\u002Fverification","Verification","What is checked, and how to repeat it. Checks on a real library are read-only; everything that\nwrites runs on temporary copies.",{"path":85,"title":86,"description":87},"\u002Fdocs\u002Fweb","The web app","apps\u002Fweb is one app (Vite, Vue, Nuxt UI) that runs in two situations:",{"id":89,"title":66,"body":90,"description":67,"extension":287,"meta":288,"navigation":289,"path":65,"seo":290,"stem":291,"__hash__":292},"docs\u002Fdocs\u002Fguide\u002Fquestions.md",{"type":91,"value":92,"toc":279},"minimark",[93,97,109,114,121,145,155,161,165,171,181,187,193,204,208,218,227,237,248,254,258],[94,95,66],"h1",{"id":96},"questions-and-answers",[98,99,100,101,108],"p",{},"Short answers to what comes up first. If yours is not here, ",[102,103,107],"a",{"href":104,"rel":105},"https:\u002F\u002Fgithub.com\u002FPolobase\u002Flivesaver\u002Fissues",[106],"nofollow","ask on GitHub",".",[110,111,113],"h2",{"id":112},"about-livesaver","About livesaver",[98,115,116,120],{},[117,118,119],"strong",{},"Does livesaver need Ableton Live?","\nNo. It reads and writes Live's files itself. Live has to be closed while livesaver fixes, so that no open set is overwritten.",[98,122,123,126,127,131,132,131,135,131,138,131,141,144],{},[117,124,125],{},"Which versions of Live does it understand?","\nSets, racks, presets and clips (",[128,129,130],"code",{},".als",", ",[128,133,134],{},".adg",[128,136,137],{},".adv",[128,139,140],{},".alc",[128,142,143],{},".agr",") from Live 8.2 to Live 12.",[98,146,147,150,151,154],{},[117,148,149],{},"Does it run on Windows?","\nIt is built to, and that is new: livesaver is made and tested on macOS, and no one has tried it on a Windows computer with Live yet. It handles Windows paths and knows where Ableton keeps its folders there. Try a fix on a copy first; ",[102,152,78],{"href":153},"windows"," says what differs and what is not known. On a Mac it has always read sets that were saved on Windows.",[98,156,157,160],{},[117,158,159],{},"What does it cost?","\nNothing. It is open source under the MIT license, and not affiliated with Ableton.",[110,162,164],{"id":163},"samples","Samples",[98,166,167,170],{},[117,168,169],{},"Live says “Media files are missing”, but the files are on my disk. Why?","\nA set remembers where each sample was. If the file was moved, a drive was renamed, or the project came from another computer, Live looks in the old place. livesaver finds the file by its fingerprint wherever it is now, and puts it into the project, where Live always finds it.",[98,172,173,176,177,108],{},[117,174,175],{},"What is an uncertain match?","\nA file that fits by its name and place, but whose fingerprint does not confirm it. livesaver marks such matches, and you can leave them out of a fix. See ",[102,178,180],{"href":179},"samples#uncertain-matches","Uncertain matches",[98,182,183,186],{},[117,184,185],{},"Why is a sample “Different content”?","\nA file of that name was found, but its audio is not what the set used. Taking it would change your music without telling you, so it stays missing.",[98,188,189,192],{},[117,190,191],{},"Does a fix change how my set sounds?","\nNo. A fix changes where the set looks for its samples, not the samples and not the set's content.",[98,194,195,198,199,203],{},[117,196,197],{},"Why does my project get bigger?","\nA fix copies samples from outside into the project, as ",[200,201,202],"em",{},"Collect All and Save"," does. On the same disk, macOS can make such a copy without using more room, and livesaver copies that way where it can.",[110,205,207],{"id":206},"the-app","The app",[98,209,210,213,214,108],{},[117,211,212],{},"Is anything sent anywhere?","\nNo. See ",[102,215,217],{"href":216},"safety#your-data","Your data",[98,219,220,223,224,108],{},[117,221,222],{},"My browser asks whether to upload my folder.","\nThat is the browser's word for letting a page read a folder. Nothing is uploaded. See ",[102,225,42],{"href":226},"browser#giving-it-folders",[98,228,229,232,233,236],{},[117,230,231],{},"The app says “livesaver on this computer does not answer”.","\nThe ",[128,234,235],{},"livesaver web"," in your terminal was stopped. Start it again; it opens the app anew.",[98,238,239,242,243,247],{},[117,240,241],{},"Can I undo a fix after I closed the app?","\nYes. The overview offers to undo the last fix, and the ",[102,244,246],{"href":245},"history","History"," lists every run.",[98,249,250,253],{},[117,251,252],{},"macOS asks whether livesaver may access a folder.","\nAllow it for the folders your projects and samples are in. A folder livesaver may not read is reported, and what is in it is not found.",[110,255,257],{"id":256},"removing-it","Removing it",[98,259,260,263,264,267,268,271,272,275,276,108],{},[117,261,262],{},"How do I remove everything livesaver wrote?","\nIts own files are in ",[128,265,266],{},"~\u002FLibrary\u002FApplication Support\u002Flivesaver"," (runs, with the originals for undo) and ",[128,269,270],{},"~\u002F.config\u002Flivesaver"," (your settings). In your projects it leaves what Live would leave as well: the collected samples in ",[128,273,274],{},"Samples\u002FImported",", and backups in ",[128,277,278],{},"Backup",{"title":280,"searchDepth":281,"depth":281,"links":282},"",2,[283,284,285,286],{"id":112,"depth":281,"text":113},{"id":163,"depth":281,"text":164},{"id":206,"depth":281,"text":207},{"id":256,"depth":281,"text":257},"md",{},true,{"title":66,"description":67},"docs\u002Fguide\u002Fquestions","-HTpdlBvG_N4iDn95Qk9Usl1CSDx724GOU9jOM2OOjk",1791245843820]