[{"data":1,"prerenderedAt":273},["ShallowReactive",2],{"docs":3,"doc:\u002Fdocs\u002Fguide\u002Fsafety":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":70,"body":90,"description":71,"extension":267,"meta":268,"navigation":269,"path":69,"seo":270,"stem":271,"__hash__":272},"docs\u002Fdocs\u002Fguide\u002Fsafety.md",{"type":91,"value":92,"toc":258},"minimark",[93,97,100,105,139,143,191,195,225,229,247,251],[94,95,70],"h1",{"id":96},"how-your-work-is-kept-safe",[98,99,71],"p",{},[101,102,104],"h2",{"id":103},"before-anything-is-written","Before anything is written",[106,107,108,121,127,133],"ul",{},[109,110,111,115,116,120],"li",{},[112,113,114],"strong",{},"Nothing is written without your yes."," On the command line every command only plans unless you pass ",[117,118,119],"code",{},"--apply",". In the app, every fix and every upgrade is reviewed first: what will change, and whether everything is ready.",[109,122,123,126],{},[112,124,125],{},"Never while Live runs."," A set that is open in Live must not be rewritten under it. livesaver checks, and refuses.",[109,128,129,132],{},[112,130,131],{},"One run at a time."," While one run writes, a second one is refused.",[109,134,135,138],{},[112,136,137],{},"Enough room."," The copies have to fit on the disk your projects lie on.",[101,140,142],{"id":141},"when-a-set-is-written","When a set is written",[106,144,145,151,157,167,173,179,185],{},[109,146,147,150],{},[112,148,149],{},"Only the bytes that must change do change."," livesaver never reads a set into a model and writes it out again. It replaces the bytes of a reference, and everything else stays exactly as Live saved it.",[109,152,153,156],{},[112,154,155],{},"The result is checked before it replaces the set."," It has to be well-formed, with as many references and devices as before, and every changed reference has to lead to its file.",[109,158,159,162,163,166],{},[112,160,161],{},"A backup beside every set."," The set as it was goes to the project's ",[117,164,165],{},"Backup"," folder, named with date and time, as Live names its own backups.",[109,168,169,172],{},[112,170,171],{},"The original is kept as well",", in livesaver's own folder. Live keeps only its newest backups; an undo works after Live has thinned them out.",[109,174,175,178],{},[112,176,177],{},"Written in one step."," The new set is written beside the old one and then takes its place, so there is never a half-written set. Finder tags and comments stay.",[109,180,181,184],{},[112,182,183],{},"Dated as what it is."," A set that was rewritten carries the date of the fix, as a set does that you save in Live. Its backup keeps the date the set had, and an undo gives the set that date back.",[109,186,187,190],{},[112,188,189],{},"A set that changed in the meantime is left alone."," Between planning and writing, the set must still be the one that was planned for.",[101,192,194],{"id":193},"afterwards","Afterwards",[106,196,197,203,214],{},[109,198,199,202],{},[112,200,201],{},"Every step is in a journal",", written before the step is taken. If a run is interrupted, the journal says how far it got, and an undo takes back what it did.",[109,204,205,208,209,213],{},[112,206,207],{},"Every run can be undone",": see ",[210,211,54],"a",{"href":212},"history",".",[109,215,216,219,220,224],{},[112,217,218],{},"Nothing is ever deleted."," What an undo removes is moved to the Trash (on Windows: to a ",[210,221,223],{"href":222},"windows#on-your-computer","trash folder of livesaver's own",").",[101,226,228],{"id":227},"your-data","Your data",[106,230,231,237],{},[109,232,233,236],{},[112,234,235],{},"Nothing leaves your computer."," livesaver has no account, no statistics, no network requests. The app asks nothing from any server but the livesaver on your own computer.",[109,238,239,242,243,246],{},[112,240,241],{},"Only its own page may ask."," ",[117,244,245],{},"livesaver web"," listens on your computer only, and answers only the page it served itself: another site open in your browser can neither read nor change anything.",[101,248,250],{"id":249},"how-this-is-tested","How this is tested",[98,252,253,254,213],{},"Against sets that Live itself saved, and read-only against a real library: 13,000 Live documents were read and written back without a change, byte for byte. See ",[210,255,257],{"href":256},"..\u002Fverification","How it is tested",{"title":259,"searchDepth":260,"depth":260,"links":261},"",2,[262,263,264,265,266],{"id":103,"depth":260,"text":104},{"id":141,"depth":260,"text":142},{"id":193,"depth":260,"text":194},{"id":227,"depth":260,"text":228},{"id":249,"depth":260,"text":250},"md",{},true,{"title":70,"description":71},"docs\u002Fguide\u002Fsafety","Uob0BnTWD25ZH2WGUspup7vT-lYb6FR57LxGXkiQjUg",1791245843400]