Skip to content

Processing-NDI #174

Open
Open

Description

@ndev-itservices

Properties File URL

https://github.com/ndev-itservices/processing-ndi-win-mac/releases/latest/download/ProcessingNDI.txt

Home Page URL

https://github.com/ndev-itservices/processing-ndi-win-mac

Guidelines Confirmation

  • I confirm that my library follows the guidelines.

Additional Remarks

Send and receive NDI® video (sketch window, PGraphics, PImage; one or many sources) on macOS 13+ (Apple Silicon and Intel) and Windows 10/11 x64. The NDI 6 runtime is bundled under the NDI SDK licence. NDI® is a registered trademark of Vizrt NDI AB

Activity

  1. github-actions commented on Nov 12, 2026

    @github-actions
    Contributor

    Your properties file was successfully parsed.
    An error was encountered when adding your contribution.

    We will look into this issue as soon as possible. Please check the details of your submission and try again if necessary.

  2. ndev-itservices commented on Nov 13, 2026

    @ndev-itservices
    Author

    The properties file parsed fine; the failure is in scripts/add_new_contribution_to_yaml.py (line 47):

    max_index = max([int(contribution["id"]) for contribution in contributions_list])
    ValueError: invalid literal for int() with base 10: 'org.rednoise.rita'
    

    Cause: the daily update on 2026-11-10 (aa67c88) copied the id=org.rednoise.rita field from RiTa's library.properties over its numeric database id:

    -- id: 314
    +- id: org.rednoise.rita

    Since then every new submission fails at this step. Suggested fix: restore id: 314 for RiTa, and keep the database id from being overwritten by a properties field named id in fetch_updates.py (or skip non-integer ids when computing max_index).

    Once it is fixed, I can edit this issue to re-run the workflow. Thanks!

  3. mingness commented on Nov 13, 2026

    @mingness
    Collaborator

    thanks for that @ndev-itservices , that is exactly the bug that I detected in our script when I reviewed rita, that it writes the id from the properties file. and it didn't occur to me that not fixing it would cause a problem each time now the scheduled update happens. I'll get on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions