Here's a listing of known issues in the current SynthEyes 2304 build 1056. Generally these will be fixed in the next build. Just because something is listed here doesn't mean that it's new, just that it hasn't previously been reported. Let us know if there's something, especially a crash, that we should fix!
- If your SynthEyes Help/About shows a 'Compiled' date of April 12th, uninstall, redownload, and reinstall. The April 12th build can crash reopening files when a moving object is the Active Tracker Host and a radial-4, radial+squash, or fisheye lens panel was open when the file was saved. That original build has been replaced! The current build shows April 18th and will reopen those files without issue.
- Time-shifting scenes due to adding or removing frames causes a crash. Keys must be moved manually using the Graph Editor until the next SynthEyes release.
- Radial-4th order models result in mismatches after the Lens Workflow script is run, notably when much padding is present. (Use the 'Maximum rounding error' control to reduce undesired padding of irregularly-sized source images.) An updated script is available in the Customer Only area.
- Nuke and Fusion scripts updated again June 19th to add more new features; the current exporters generate better pipelines than the original release. Download from the Updated Scripts page in the Customer-Only area.
- After Effects script updated May 12th to fix crash passing workarea information to the FBX exporter for Cinema 4D integration. See Updated Scripts also.
- When exporting to Nuke or Fusion without running the Lens Workflow (ie with a zero-pass workflow), exports to other rendering applications (such as Maya) must include the lens center and required overscan. At present, only the newly released Maya ASCII Updated exporter can do this. Otherwise, 3-D renders will not match. You can eliminate the lens center as an issue by not calculating it, but you may still need to set an appropriate overscan manually. We may update additional exporters to include lens center and overscan, where technology and interest permit. Instead, we always recommend running the Lens Workflow—Lens Workflow was designed exactly to avoid such issues!
- The updated scripts area has a bugfix for a USDA exporter error when the scene being exported has meshes with rolling front projection texture coordinates.
- ProRes on M1 Minis under macOS Ventura, SynthEyes 2204 and later: The ProRes movie decoder in Ventura produces an all-black image on M1 Minis. M1 Pro and M1 Max Macbook Pros read ProRes fine in Ventura. No reports of problems on other M1/M2 machines or Intel. Workaround: SynthEyes 2304 on macOS contains a preference named “Force 8bit ProRes,” in the ProRes section for use only on affected Mac Minis. It produces images by forcing 8-bit reads even if you request 16- or 32-bit reads. See the Ventura blog post for more information.
General — Not SynthEyes-Specific
- SynthEyes plugins for After Effects are Intel-only at this time. To use them, you'll need to turn on “Open using Rosetta” on Adobe After Effects 202x.app's Get Info panel.
- SynthEyes to Blender via Python: Blender 3.2–3.5 contain a bad version of python, python 3.10, that crashes when large python scripts are compiled. If you export sufficiently large meshes from SynthEyes to Blender via the blender (python) export, when you import them to blender, python will crash, causing blender to crash. Make sure you're using SynthEyes 2210 or later and turn on the “Hex data workaround” in the blender exporter. This has been fixed in python, but it's unclear when that fixed python will appear in blender.
- SynthEyes to Blender via USD: blender does not read the camera aperture (sensor size) information from the USDA file, so the camera field of view will be wrong. We got this fixed in the source code, but it's unclear which version of blender the fix will appear in. If the sizes are wrong in your version, you'll have to set the sensor sizes manually.
- Autodesk Flame on Apple Silicon macOS using Python. SynthEyes can't be started from Flame's python using SyPy3 due to Rosetta. See the Flame python blog post for Rosetta details and an entertaining workaround.
- SynthEyes to anything via Filmbox FBX: SynthEyes writes FBX files using a recent version of FBX by default; older versions of other applications cannot read those files and camera path animation may appear to be missing. Instead, tell the exporter to write one of the older versions of FBX.
- Windows will fail to write H.264/265 movies from Save Sequence or Preview Movie if you've set the bit rate too low; increase the value as needed. See also HEVC/H.265 on Windows 10 in the user manual.
- In the macOS color picker, if you attempt to drag the color to the swatches at the picker's bottom-right, it will crash SynthEyes ... and applications such as Apple's own TextEdit. This is a generic macOS issue; the workaround is don't do that until Apple fixes it (don't hold your breath).
For feature suggestions, see the Sug button in SynthEyes.