Nearfield / Known problems
Known problems in the beta
These are problems in the beta that we already know about. Read this list before you send a report. Each item says what you may see and what to do.
Your problem is not on this list? Report a problem
This list is for version 0.1.0-beta.9. It lists only problems that you can meet in the app today. We update it when a version changes one of them. The update notice in Nearfield links here when a new build has notes. What changed in each version is on the changes page.
The list
A button that saves a file may not save it
Some buttons give you a file: the recovery code (“Nearfield recovery code.txt”), “Save to a file” in Diagnostics, and the account export. We turned on file saving in the installed window. We have not yet seen it work on every Mac and Windows computer.
What to do: after you press one of these buttons, look in your Downloads folder. If the file is not there, tell us which button you pressed. Do not rely on a recovery code until you have seen its file.
Screens can answer slowly while a share lands
While a shared project arrives on a Mac, some screens (the Inbox, the Dashboard and the sync line on the Dashboard) can take many seconds to answer. We measured this on one Mac. We made a change, and we have not yet timed it again during a real share.
What to do: wait. Report it only if a screen is still empty after a few minutes.
A share arrives only while both computers are on
In this build, a share goes directly from one computer to the other. It moves only while both computers are on and online at the same time. Cloud sharing, which brings a share while the other computer is off, comes in an update.
What to do: leave both computers on until the share has arrived. If a share has not arrived after both computers were on for a while, tell us.
A collaborator on an older version can bring back an older master
A shared project keeps one record of its newest master. Beta.7, beta.8 and beta.9 replace that record only when they have a newer export. Beta.5 replaces the record each time its own folder has a different master. So a collaborator on beta.5 can put an older master back over your new one, again and again.
What to do: update every computer in the shared project to beta.9. Tell your collaborators to update too.
The first open of the Mac build may show a warning
The beta is not signed with an Apple Developer ID yet. On a Mac, the first open can show a warning. We changed how the Mac build is sealed. We have not yet tested the new build on a clean Mac.
What to do: follow the “Open Anyway” steps on the download page. If your Mac says that Nearfield is damaged, tell us.
What this page means for your work
- None of these problems changes your Ableton Sets.
- Nearfield never edits a Set. A fix is always a new copy beside yours.