# Lathe Cloud

Lathe can share a song with the people you make music with, through Lathe Cloud. It works like git, not like a shared document:

- Everyone works offline on their own copy.
- **Push** sends a revision up. **Pull** brings collaborators' revisions down.

## Getting set up
- Release builds are already set up for Lathe Cloud.
- **Cloud > Sign In** with your Lathe Cloud account. The first time, Lathe asks you to choose your own password.

## Friends, projects and songs

- A **song** is one Lathe project file. A **project** is a group of songs: an album, a band, a client.
- You share with **friends** only. **Cloud > Friends** sends a request to someone's email; once they accept (in their Lathe), you can share with each other. Removing a friend doesn't unshare anything.
- **Cloud > Put This Song in the Cloud** uploads the open song (r1) into one of your projects, or a new one.
- **Cloud > Projects** lists your projects and their songs, and songs shared with you on their own. Select one to see who has it. **Open** downloads a song, audio included, into `Documents/Lathe/Projects/<name>`.
- Share a whole **project** (friends get every song in it, including ones added later) or a single **song**. Each person **can edit** (pull and push) or **can view** (pull only; they can still change their own copy, but can't push).
- **Share only some tracks.** In **Cloud > Projects**, Share > a friend > **Can push only some tracks...** (the song has to be open, and pushed at least once). Tick the tracks they may push. They clone the whole song and can change anything on their computer, but a push sends only those tracks, put on top of the newest revision; everything else they changed stays on their computer. Lathe Cloud refuses any other change, so it holds whatever version of Lathe they use. Change the tracks later from the person's menu in the song's people list (**Pushes Guitar**), or make them a full editor.
- What they see: a bar under the transport says "In “Song” you push Guitar. Everything else you change stays on this computer." Their tracks say **Yours** and are outlined in the arrangement and the mixer; the rest are dimmed (still playable and editable). **Cloud > Push Guitar...** pushes. Someone who can also edit the whole project isn't limited.
- Only the owner manages a project or song: share, change someone's access, **Stop Sharing** (with one person or everyone), **Rename** (shares stay), **Move to Project** (a song; people who had it only through its old project, or shared on its own, lose it), and **Delete from Cloud**. Anyone can **Leave**.
- When you lose access to something or become a viewer, Lathe tells you. Your copy on your computer is never touched: you just can't pull or push it anymore. **Cloud > Disconnect This Song** stops it asking.

![What a bandmate who may push only Guitar sees: the bar under the transport, Guitar outlined and marked Yours, the other tracks dimmed.](https://getlathe.app/img/cloud/push-guitar.jpg)

## Invite links
- **Cloud > Invite Someone by Link** makes a link (getlathe.app/join.html#...) to send however you like. Choose what it's for: just being friends, or the open song (if it's yours), to edit or view only. Song invites need a paid plan, like sharing.
- Whoever opens it types their email. Without an account, Lathe Cloud makes one and emails a temporary password. The invite waits under that email and is claimed when they next sign in: you become friends, they get the song, and Lathe offers to open it. If your plan has no room for another free editor, they join as a viewer and are told so.
- Someone already in Lathe can paste the link into **Cloud > Join with an Invite Link** instead.
- A link works for 14 days, for up to 10 people. You can have 20 open at once.

## Listening links
- **Cloud > Share a Listening Link** renders the song's mix as it sounds now (start to end, like File > Export Audio), uploads it (FLAC, lossless) and gives you a link (getlathe.app/listen.html#...). Anyone with it can play the mix in a browser, without Lathe or an account. Only the song's owner can share one (or stop it), on a paid plan; everyone on the song can see the link.
- Listeners can leave a comment at a moment in the song, with their name. It arrives as a song comment ("At 1:15: ..." from "Sam (listening link)"), and the owner gets a notice.
- A song has one link. **Share the Latest Mix** after changes updates what it plays; the link stays the same. **Stop Sharing** ends it, and deleting the song does too.

## Comments and conversations

![A comment on the vocal, open: the conversation, with Reply and Resolve.](https://getlathe.app/img/notes.jpg)

- Leave a comment on a track at a moment in the song: right-click the lane (or a clip) and choose **Add Comment Here**, or **Track > Add Comment at Start Marker** (Cmd/Ctrl+Alt+N). It shows as a speech bubble on the lane; the number is how many messages are in the thread.
- **Song comments** are about the whole song (the plan so far, what's left): **Track > Add Song Comment**, or **Add Song Comment** in the Comments window.
- Click a bubble to open the conversation: reply, **Resolve** (or Reopen), **Edit** your own comment, **Delete**. You can delete your own comments and replies; the song's owner can delete any. Everyone the song is shared with can write comments, viewers too.
- **Comments** in the top bar (Cmd/Ctrl+Shift+N) lists every comment, song comments first then in time order. Click one to jump there. It lights up when someone left something you haven't read, and the status bar tells you who. **On tracks** (also View > Comments on Tracks) shows every comment, hides resolved ones, or hides them all; that only changes your screen.
- A cloud song's comments live on the server: collaborators see them within a minute, with no Push needed and no conflicts. Comments are live but tracks are pushed and pulled, so a comment can be on a track that isn't in your copy. It still shows in the Comments window (not on a lane), with the track's name and why: **not pulled yet** (a newer revision is waiting; Pull and the comment appears on the track), **not pushed yet** (the track is still only on their computer) or **deleted**. You can read, reply to and resolve it either way.
- **Plug-ins a bandmate doesn't have.** The song still opens and nothing is lost: the plug-in shows in red ("Not installed. Settings are kept.") and keeps its settings, so it sounds as it did when the person who has it opens the song again. Until then a missing effect is skipped (the track plays dry) and a missing instrument is silent. You can still mix, move, bypass or remove it, and push.
- A comment stays on the track it was left on, even when two people add tracks at the same time or a track is deleted: each track has a permanent tag that comments point at, rather than its number, which Lathe can renumber when it merges. A song that isn't in the cloud keeps its comments in the project file, and they move to the server when you put it in the cloud.
- **Offline:** when Lathe can't reach the cloud, comments keep working. New comments and changes show at once (faded, "not sent yet") and are sent in order when the cloud is back; Lathe retries every 15 s. The Comments button reads **Comments offline** (its tooltip and the Comments window say why and how many changes are waiting). The last copy of the comments and the unsent changes are kept in the song's `.lathe/notes.json`, so they survive quitting.

## Push
- Uploads what you have open as a new revision, with your description and an automatic summary of what changed (faders, pans, mutes, sends, EQ bands, plug-in knobs, clips, new or removed tracks, tempo, monitor mixes).
- Audio files are stored once under their content hash, so a take is never uploaded twice.
- Takes are compressed before they go up, losslessly (FLAC): a recorded take is typically about half the size, and the file you pull back is identical, byte for byte, to the one that was recorded (every download is checked). Compressing runs several hundred times faster than real time, so it saves more upload time than it takes. Files FLAC can't hold (32-bit float) go up as they are.
- Up to 4 files (or 64 MB pieces of a big file) move at once, in both directions, and a dropped connection is retried. Change this under **Cloud > Transfers at Once**: 1 sends one file at a time, which is gentler on a slow connection.

## Pull
- Downloads new revisions and the latest one's audio.
- Doesn't change what you have open. Lathe offers to open the newest revision.

## History

Open History from the Cloud menu, or click the cloud label in the status bar.

![History: every revision of the song, with who pushed it and what it changed.](https://getlathe.app/img/history.jpg)

- Lists every revision: pushed, pulled, and **Local** ones (kept on this computer, not pushed).
- Select one to see what it changed and what opening it would change.
- **Open This Revision** first keeps what you have open as a Local revision, so switching never loses work.
- The cloud keeps each song's newest 5 revisions (20 on Pro). **Keep** a revision (a mix you sent, say) and it stays however many come after. Revisions the cloud let go stay in History on your computer ("only on this computer").

## Plans
- **Free**: join songs friends share with you, pull them, leave comments, and push if they made you an editor.
- **Starter**: your own songs and projects in the cloud, shared with friends. Each song up to 5 GB (its current version), 50 GB for all your songs together, 2 free accounts can edit your songs (any number can view).
- **Pro**: songs up to 25 GB, 250 GB in all, 20 revisions kept, any number of free editors.
- Your plan shows in the Cloud menu next to your email. When something doesn't fit, Lathe says what and why before anything uploads.

## If someone pushed first
- Lathe never puts your revision on top of theirs as it is (theirs would go missing from the newest revision). You get theirs first, then push yours on top of it:
  1. **Get the Newest**: Lathe sets your changes aside (kept in History as a Local revision, so nothing can be lost), pulls, and opens the newest revision. A bar under the transport says your changes are set aside. Listen, and change anything you like.
  2. **Put My Changes Back** (the bar, or the Cloud menu): Lathe puts what you'd changed on top of what's open. Changes are compared per song setting (tempo, time signature), per track setting (fader, pan, mute, plug-ins, EQ, sends, name, routing) and per clip, so if you worked on the vocal and they worked on the guitar, both stay. New tracks and clips from both sides stay.
  3. If you both changed the same thing (the same fader, the same clip, the tempo), Lathe lists each one in plain words ("Mine: fader -8.0 dB -> -6.0 dB" / "r2: fader -8.0 dB -> -1.0 dB") and you pick which to keep, or Keep All Mine / Keep All r2's. Cancel changes nothing.
  4. Push. The new revision has everything in theirs, plus your changes.
- Pulling while you have changes you haven't pushed offers the same thing: **Set Mine Aside and Open r2**.
- **Forget Them** (the bar, or Cloud > Forget My Set-Aside Changes) drops them; they stay in History.
- Your record arm and monitoring settings, and the loop region, are always yours: they never count as a conflict.

## Other things to know
- While a shared song is open, Lathe checks every two minutes for new revisions, friend requests and notices, and the status bar tells you when something is waiting.
- The history lives in a hidden `.lathe` folder inside the project folder, next to `Audio/`. Copying the folder copies the history.
