Skip to content

Releases

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 13 Nov 12:19

Camset Editor 0.2.1 runs on Windows too, and anyone can now look inside a settings file with nothing to install.

  • Windows: a zip for 64-bit Windows 10 and 11 (Intel or AMD). Unpack it anywhere and run camset_editor.exe in the folder it makes, keeping that folder's files together. The program is not signed, so Windows SmartScreen warns the first time you start it ("Windows protected your PC"): click More info, then Run anyway.
  • The definition viewer: choose a CAMSET*.DAT in your browser and see every setting by name, as the camera's menu has them. The file stays on your computer. It is on the docs site at https://camset-dev.github.io/camset/viewer/, and attached to this release as camset-viewer.html, which opens with no internet.
  • About in Settings: click the version at the right end of the status bar to see which editor this is, the cameras it knows, links to the docs and Report a problem, what changed in each release, and Copy details for a problem report (nothing of yours in it).
  • Fixes: on Windows the editor reads the computer's clock as local time (it took it as UTC) and no console window flashes up when it talks to a camera; the macOS disk image installs by dragging Camset Editor onto Applications; the web page's windows open on top of each other in the order you asked for them.
  • For people mapping a camera: a kit program started with the wrong Python (macOS's own, say) now says so and gives the command to run instead of ending in a traceback, and kit/setup.py walks Windows users through each step in plain words.

Read first: writing an edited settings file to a camera is at your own risk, so always keep a settings file the camera saved itself, on the card and on your computer. The packages do not include the camera helper that reading and writing a camera directly needs: the editor works on the files a camera saves to its card. Camset is an independent project, not affiliated with or endorsed by Sony.

The full list is in the changelog.

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 11:57

The editor for macOS and Linux, the mapping kit, the docs and the ILCE-1M2 (a1 II) firmware 4.00 definition, in the new lean form. It replaces 0.1.0, which is withdrawn.

Read first

  • 0.1.0 is withdrawn: use 0.2.0. Its packages are no longer offered. If you have the 0.1.0 editor, replace it with this one.
  • Camera definitions are in a new, lean form (definition format 2). This editor does not open a definition made for 0.1.0, and the 0.1.0 editor does not open the new ones; this editor comes with the new ILCE-1M2 definition. If you are mapping a camera with a clone of this repository, follow Updating your clone before going further, and write your definition afresh with the updated kit.
  • Writing an edited settings file to a camera is at your own risk. A file edited by hand once put a camera into a restart loop in Movie mode, which ended when Initialize was run on the camera; Initialize also clears the network setup and the memories. The editor and the camera may refuse or change values. Always keep the camera's own backup, a settings file it saved itself, to load back: on the card and on your computer.
  • This is an independent project, not affiliated with or endorsed by Sony. Sony and the camera names are used only to say what the files are.
  • The editor's packages (the macOS app and disk image, the Linux tarball) do not include the camera helper, which reading and writing a camera directly needs: the editor works on the files a camera saves to its card. The helper is built from Sony's Camera Remote SDK on your own computer under Sony's terms (the README, "The camera helper").
  • Windows: no package in this release; the editor builds from source there (the README, "Use the editor").

Everything in this release

The full list is in the changelog.