Menu ▾ ▴

#84 Source proposal: native ConcertAmi plan import with persistent library songs (Xojo validation pending)

Next release
open
nobody
None
1
2026-11-07
2026-11-07
Anonymous
No

This is a source-level proposal to add ConcertAmi plan import directly to OpenSong, based on official source/trunk SVN revision 1844. Please review it for possible inclusion; it is not a compiled or released integration.

Important validation limitation: the Xojo changes have NOT been compiled or run. Xojo 2026r3 was obtained from the official vendor, but its required account sign-in was unavailable. Development continued without native compilation. The patch was prepared with AI assistance and needs human review and native validation before acceptance. I am not requesting a binary build or claiming that the patch is ready to merge.

Proposed workflow

  • File → Import → Download ConcertAmi plan… opens the user's normal browser at https://concertami.com/integrations.
  • The user signs in to ConcertAmi normally and exports one authorised plan, including lyrics/chords and attribution. Passwords, browser cookies and access tokens never pass through OpenSong.
  • File → Import → ConcertAmi plan… selects the downloaded .concertami.xml file, previews the program and asks for confirmation.
  • Confirmed songs become ordinary, permanently saved OpenSong library files under Songs/ConcertAmi. The imported set under Sets references these songs. They remain available after restarting OpenSong or deleting the set.
  • Identical exports reuse existing files. Local edits and unrelated songs/sets are never overwritten. Changed source content/key/metadata creates separate song versions; changed programs create separate sets. This is explicit file import, not live synchronization or automatic title matching.

Scope and safeguards

The patch adds a native importer module, two menu actions, project registration, nine translated language packs, documentation and a wholly synthetic sample. It does not modify the existing REST API or start/control a presentation. No new runtime, subprocess, listener, credentials or server configuration are needed.

The XML format is versioned and bounded to 16 MiB, 1000 songs and 1000 program items. The importer reconstructs whitelisted text fields and rejects DTD/entity constructs, NUL bytes, invalid or duplicate identities, missing song references and unknown item types. Exported filenames/paths/styles are not accepted. New files are staged; songs are published before the set; ordinary write failures roll back only files created by that import. Existing files are not overwritten or deleted. A crash can leave valid new library songs without a set; this limitation is documented.

The companion exporter supports lyrics, chords, sections, notes, program order, author/copyright/CCLI metadata and Polish UTF-8 text. Media/PDF attachments and OCR are outside this patch; missing song text blocks export instead of silently omitting the song.

Evidence and remaining gates

  • Patch dry-run succeeds against a clean copy of the r1844 source snapshot.
  • All upstream language XML files still parse.
  • Companion exporter conversion tests pass; its synthetic output also round-trips through an existing OpenSong XML reader.
  • 11 targeted browser tests passed for exporter behaviour and existing settings/Playback navigation. The ConcertAmi JS suite passes 88 tests.
  • These checks do NOT execute Xojo code. Native compilation, actual file persistence/restart, cancellation, local-edit preservation, failure rollback, projection isolation and Windows/macOS/Linux testing remain required. Detailed steps are in documentation/concertami.md inside the patch.

The attached .patch is directly reviewable and applies with patch -p1 from source/trunk. The ZIP includes the same patch, format/validation notes, synthetic example and the newly written standalone exporter/conversion tests. No customer records, real songs, credentials or production exports are included. The native patch is GPL-2.0-only to match OpenSong.

If a neutral song/set bundle importer or different menu placement would fit the project better, I am happy to adjust the proposal to the maintainers' preferred architecture.

2 Attachments

Discussion

Anonymous
Anonymous

Add attachments
Cancel