Licence - Solstice - Ravers Co

Ravers Co DAW

← Solstice

Licence

Applies to Solstice 0.1.1 and later. Effective 17 November 2026.

SOFTWARE LICENCE AGREEMENT

Solstice 0.1.3-beta
Copyright (c) 2026 Unicorn Mystic Group Limited Trading As Ravers Co New Zealand. All rights reserved.

Written by Gareth Erasmus and Justine Keating.

1. GRANT OF LICENCE

The Licensor is Unicorn Mystic Group Limited, a company registered in New Zealand and trading as Ravers Co New Zealand. The Licensor grants you a free, personal, non-exclusive, non-transferable licence to install and use this software ("the Software"). The licence is granted to one person: you, the holder of the Ravers Co account the Software was downloaded with, and it is recorded against that account. You may install and use the Software on any number of computers you own or control, for any purpose including commercial music production, but your licence is yours alone: anybody else who uses the Software needs a licence of their own, through an account of their own, which is also free. Music you make with the Software is yours. The Licensor claims no interest in it and no share of it.

2. WHAT YOU MAY NOT DO

You may not:

(a) redistribute, resell, rent or sublicense the Software, or host it for download elsewhere;

(b) reverse engineer, decompile or disassemble it, except to the extent that law expressly permits despite this term;

(c) remove or alter any notice of authorship, copyright or licence;

(d) represent the Software, or a modified copy of it, as your own.

3. IT IS FREE, AND IT STAYS FREE FOR THIS VERSION

The Software is supplied at no charge. Downloading it from ravers.co.nz requires a free Ravers Co account, which is how your licence key is delivered to you; no payment is due for the account, for the key or for the Software, and none becomes due later for the version you have. Later versions may offer paid features alongside a free edition. That does not reach backwards: the licence granted for the version you have received is perpetual, and no update or change of business model removes a feature you already have in a version already installed.

4. YOUR WORK, AND WHAT THE SOFTWARE SENDS

Projects, settings, recordings and logs are written to your own machine and belong to you. The Software does not send your work anywhere: your music is never uploaded. One request is made that carries nothing of yours and only brings something back: when you run the command Get Controller Tables, and at no other time, the Software fetches from ravers.co.nz a signed list of control surface tables and the tables that list names, and what it sends is the address asked for and a fixed client name and nothing else: no licence key, no installation number, nothing about your computer and nothing about your work.

Four other things do leave your machine, and this clause exists because an earlier version of it said they did not. First, an update check, which sends five fields and nothing else: the version, the channel, the platform, the processor type, and a random installation number made on your computer. You can switch it off. Second, when the Software runs under a licence key, that key, the same installation number, and the version, the platform and the processor type, so that the Licensor can tell your copy from a stranger's; a record of each computer a key is used on is kept against your account, it is not anonymous and is not aggregated, and it is used to match a fault report to the machine it came from and to block a computer or a key from the beta programme where that is necessary. Third, a fault report, and only when you send one: what you wrote, the version, the platform, the processor type, the installation number, your licence key if you have entered one, a description of your computer (its processor, memory, model, graphics processor, displays and the audio devices it has), a redacted tail of the Software's log, and, when the fault was recorded automatically, one picture of the Software's window showing whatever was on screen at the time and a call stack saying where in the Software's own code it stopped. The call stack names files inside the Software and offsets into them, never a folder on your computer, and it means nothing without a reference file the Licensor keeps and does not distribute. All of it is shown to you in full before anything leaves, the picture included, and nothing is sent unless you choose to send it. Fourth, if you switch the visuals output on, the tempo, the beat, the bar and the moments the music starts and stops go to an address you choose on your own network, so that a lighting or projection program can follow the music; it is off until you turn it on, and none of it goes to the Licensor.

The update check also runs while the Software is closed, from a task the installer puts on your computer and which does not show itself, on any setting that asks for a check the Software will not be open to make: with the weekly setting the task is what performs the weekly check, and with the default setting - a check when the Software starts - the task wakes, reads the setting, and does nothing at all. It sends what the check above sends and nothing more, the same setting switches it off, and removing the Software removes it. It also downloads the update itself when there is one, so that the next time you open the Software the file is already there: that is a download of the whole new version, and it happens in the background without asking you. The Software does the same while it is open: when its own check finds a newer version it downloads the whole of it in the background, without asking you first. Downloading installs nothing. A downloaded update is installed when you agree to restart for it, when you close the Software, or the next time you start the Software; if you have chosen the setting that installs updates straight away, the Software restarts to install one as soon as it has downloaded, without asking, though never while something is playing or recording. Switching the update check off stops the downloading as well as the checking. The task never installs anything by itself, it does not start while your computer is on battery, and it stops if your computer goes onto battery while it is running.

The Privacy section of the licence page at ravers.co.nz states exactly what is kept, for how long, and how to have it deleted; on request the Licensor will delete it. Write to [email protected] and the record of your computers will be deleted.

5. INTELLECTUAL PROPERTY

All rights in the Software remain with the Licensor. This licence gives you the right to use the Software and conveys no ownership of it or of its source code. Third party components are used under their own terms, which are set out in NOTICES.txt, distributed with the Software and shown by it. Two of them are copyleft. One, the LAME MP3 encoder in libmp3lame.dll, is licensed under the GNU Library General Public License version 2, and it ships as its own library beside the Software, so you may replace that library with your own build of it. The other is two codebooks of numbers taken from FFmpeg, licensed under the GNU Lesser General Public License version 2.1 or later and compiled into the Software itself, so there is no separate library there for you to replace; section 14 of NOTICES.txt names those two tables, says which release of FFmpeg they were taken from and how to obtain that source. For both of them, clause 2 does not stop you modifying the Software for your own use or reverse engineering it to debug such a change, as those licences require.

6. NO WARRANTY

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. THE LICENSOR IS NOT LIABLE FOR ANY LOSS OR DAMAGE ARISING FROM ITS USE, INCLUDING LOST WORK. KEEP BACKUPS OF ANYTHING YOU CARE ABOUT.

7. CONSUMER RIGHTS

Nothing in this licence limits any right you have under consumer law that cannot lawfully be limited. In New Zealand, the Consumer Guarantees Act does not apply where software is supplied free of charge for business use, and where it does apply, this licence yields to it.

8. TERMINATION

This licence ends if you breach it. On termination you must stop using the Software and remove it. Your own work is unaffected.

9. GOVERNING LAW

New Zealand law governs this agreement.

Enquiries: [email protected]
https://ravers.co.nz

Earlier versions

The licence you received with a version stays the licence for that version. A change only ever applies to versions released after it.

From version 0.1.0

SOFTWARE LICENCE AGREEMENT

Solstice 0.1.0-beta
Copyright (c) 2026 Unicorn Mystic Group Limited Trading As Ravers Co New Zealand. All rights reserved.

Written by Gareth Erasmus and Justine Keating.

1. GRANT OF LICENCE

The Licensor is Unicorn Mystic Group Limited, a company registered in New Zealand and trading as Ravers Co New Zealand. The Licensor grants you a free, non-exclusive, non-transferable licence to install and use this software ("the Software") on any number of computers you own or control, for any purpose including commercial music production. Music you make with the Software is yours. The Licensor claims no interest in it and no share of it.

2. WHAT YOU MAY NOT DO

You may not:

(a) redistribute, resell, rent or sublicense the Software, or host it for download elsewhere;

(b) reverse engineer, decompile or disassemble it, except to the extent that law expressly permits despite this term;

(c) remove or alter any notice of authorship, copyright or licence;

(d) represent the Software, or a modified copy of it, as your own.

3. IT IS FREE, AND IT STAYS FREE FOR THIS VERSION

The Software is supplied at no charge. Downloading it from ravers.co.nz requires a free Ravers Co account, which is how your licence key is delivered to you; no payment is due for the account, for the key or for the Software, and none becomes due later for the version you have. Later versions may offer paid features alongside a free edition. That does not reach backwards: the licence granted for the version you have received is perpetual, and no update or change of business model removes a feature you already have in a version already installed.

4. YOUR WORK, AND WHAT THE SOFTWARE SENDS

Projects, settings, recordings and logs are written to your own machine and belong to you. The Software does not send your work anywhere: your music is never uploaded. One request is made that carries nothing of yours and only brings something back: when you run the command Get Controller Tables, and at no other time, the Software fetches from ravers.co.nz a signed list of control surface tables and the tables that list names, and what it sends is the address asked for and a fixed client name and nothing else: no licence key, no installation number, nothing about your computer and nothing about your work.

Four other things do leave your machine, and this clause exists because an earlier version of it said they did not. First, an update check, which sends five fields and nothing else: the version, the channel, the platform, the processor type, and a random installation number made on your computer. You can switch it off. Second, when the Software runs under a licence key, that key, the same installation number, and the version, the platform and the processor type, so that the Licensor can tell your copy from a stranger's; a record of each computer a key is used on is kept against your account, it is not anonymous and is not aggregated, and it is used to match a fault report to the machine it came from and to block a computer or a key from the beta programme where that is necessary. Third, a fault report, and only when you send one: what you wrote, the version, the platform, the processor type, the installation number, your licence key if you have entered one, a redacted tail of the Software's log, and, when the fault was recorded automatically, one picture of the Software's window showing whatever was on screen at the time and a call stack saying where in the Software's own code it stopped. The call stack names files inside the Software and offsets into them, never a folder on your computer, and it means nothing without a reference file the Licensor keeps and does not distribute. All of it is shown to you in full before anything leaves, the picture included, and nothing is sent unless you choose to send it. Fourth, if you switch the visuals output on, the tempo, the beat, the bar and the moments the music starts and stops go to an address you choose on your own network, so that a lighting or projection program can follow the music; it is off until you turn it on, and none of it goes to the Licensor.

The update check also runs while the Software is closed, from a task the installer puts on your computer and which does not show itself, on any setting that asks for a check the Software will not be open to make: with the weekly setting the task is what performs the weekly check, and with the default setting - a check when the Software starts - the task wakes, reads the setting, and does nothing at all. It sends what the check above sends and nothing more, the same setting switches it off, and removing the Software removes it. It also downloads the update itself when there is one, so that the next time you open the Software the file is already there: that is a download of the whole new version, and it happens in the background without asking you. The Software does the same while it is open: when its own check finds a newer version it downloads the whole of it in the background, without asking you first. Downloading installs nothing. A downloaded update is installed when you agree to restart for it, when you close the Software, or the next time you start the Software; if you have chosen the setting that installs updates straight away, the Software restarts to install one as soon as it has downloaded, without asking, though never while something is playing or recording. Switching the update check off stops the downloading as well as the checking. The task never installs anything by itself, it does not start while your computer is on battery, and it stops if your computer goes onto battery while it is running.

The Privacy section of the licence page at ravers.co.nz states exactly what is kept, for how long, and how to have it deleted; on request the Licensor will delete it. Write to [email protected] and the record of your computers will be deleted.

5. INTELLECTUAL PROPERTY

All rights in the Software remain with the Licensor. This licence gives you the right to use the Software and conveys no ownership of it or of its source code. Third party components are used under their own terms, which are set out in NOTICES.txt, distributed with the Software and shown by it. Two of them are copyleft. One, the LAME MP3 encoder in libmp3lame.dll, is licensed under the GNU Library General Public License version 2, and it ships as its own library beside the Software, so you may replace that library with your own build of it. The other is two codebooks of numbers taken from FFmpeg, licensed under the GNU Lesser General Public License version 2.1 or later and compiled into the Software itself, so there is no separate library there for you to replace; section 14 of NOTICES.txt names those two tables, says which release of FFmpeg they were taken from and how to obtain that source. For both of them, clause 2 does not stop you modifying the Software for your own use or reverse engineering it to debug such a change, as those licences require.

6. NO WARRANTY

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. THE LICENSOR IS NOT LIABLE FOR ANY LOSS OR DAMAGE ARISING FROM ITS USE, INCLUDING LOST WORK. KEEP BACKUPS OF ANYTHING YOU CARE ABOUT.

7. CONSUMER RIGHTS

Nothing in this licence limits any right you have under consumer law that cannot lawfully be limited. In New Zealand, the Consumer Guarantees Act does not apply where software is supplied free of charge for business use, and where it does apply, this licence yields to it.

8. TERMINATION

This licence ends if you breach it. On termination you must stop using the Software and remove it. Your own work is unaffected.

9. GOVERNING LAW

New Zealand law governs this agreement.

Enquiries: [email protected]
https://ravers.co.nz

Source code offer

The LAME MP3 encoder the app ships beside it (libmp3lame.dll) is licensed under the GNU Library General Public License, version 2 or later. The two FFmpeg DTS codebooks are licensed under the GNU Lesser General Public License, version 2.1 or later. The complete source code of both is yours free on request: write to [email protected]. For LAME the offer stands for three years from the last time we offered the version you have; for the codebooks, three years from the release that contains them. You may replace the LAME library with your own build, and the licence allows changing the app for your own use and reverse engineering it to debug such a change.

Privacy

YOUR WORK STAYS WITH YOU. Projects, settings, recordings and logs are written to your own computer. The app does not upload any of them, and nothing here is about your music.

WHAT AN UPDATE CHECK SENDS. The app asks this site at most once a day and sends five things: its version, its channel (stable or beta), the platform, the processor type, and a random installation number made on your computer, not from anything about you or your machine. You can switch it off in Settings. This site turns those checks into daily totals and nothing else: for that counting the installation number is never stored as itself, only as a scrambled form; the scrambling key is replaced every day, and every scrambled form older than today is deleted when the day turns, so nothing links one day to the next; and your network address is never recorded next to any of it.

WHAT WE KEEP AGAINST YOUR ACCOUNT, AND THIS PART IS NOT ANONYMOUS. When the app runs under your licence key it sends the key and that same installation number. We keep a row for that computer: the installation number as it was sent, which key it belongs to, when the computer was first and last seen, how many times it has been seen, and the version, platform and processor type. It is not scrambled and it is not a daily total. It sits next to the Ravers Co account the key was issued to, and it stays for as long as that account holds a key. We keep it for two reasons and no others: so that a crash report can be matched to the machine it came from, and so that one computer, or one whole key, can be blocked from the beta if it has to be. A blocked computer is told it has been blocked and given an address to write to.

CRASH REPORTS, WHICH ONLY GO WHEN YOU SEND ONE. A report carries what you typed, the version, the platform and processor type, that installation number, your licence key if you have entered one, a description of the computer it comes from (its processor, memory, model, graphics processor, displays and the audio devices it has), and a tail of the app's own log which the app redacts before it sends it. When the app recorded the fault itself, rather than you writing it up, it also carries one screenshot of the app window showing whatever was on screen at the time; a report you write yourself carries no screenshot, and no picture is taken at all while reporting is switched off in Settings. A report you write yourself, from the Help menu or with its key, can be sent even while that automatic reporting is switched off, because you are shown the whole report first and nothing goes unless you choose to send it. Before anything leaves, the app lists every one of those on screen, the screenshot among them - it tells you the picture is there and how large it is rather than showing you the image. Nothing is sent without you asking for it to be, and a report you choose not to send is kept on your own computer, where you can attach it to an email yourself if you change your mind. The report becomes a support ticket in your name so that somebody can reply to you. A screenshot is deleted ninety days after it arrives, automatically; the written report is kept while the bug is open and afterwards as the record of what was fixed.

BUG REPORTS FROM THIS SITE. The bug report form on the download page and in the getting started guide keeps what you write in it, the computer and the version you choose, and the email address we reply to, which is your account's address when you are signed in, with your account beside it. It takes no files and carries nothing about your computer that you did not type yourself. It is kept on this site where only our administrators can read it, emailed to [email protected] so that a person reads it, and kept for 180 days from the day it arrives, then deleted automatically. Cloudflare Turnstile checks that a person filled the form in, and your network address is not stored with the report.

WHAT WE DO NOT DO. We do not store your network address next to any of this. We do not sell it, share it or send it to anybody else. There is no advertising or tracking code in the app, and there never will be.

HAVING IT DELETED. Write to [email protected] and we will delete the rows for your computers, your crash reports and their screenshots. Closing your Ravers Co account takes all of it with it.

Third-party notices

Show the notices
THIRD PARTY NOTICES
===================

Solstice 0.1.0-beta
Copyright (c) 2026 Unicorn Mystic Group Limited Trading As Ravers Co New Zealand. All rights reserved.


WHAT THIS FILE IS
-----------------
Solstice is closed source and is licensed under the terms in LICENSE.txt.
That covers the parts written here. It does not, and cannot, cover work by
other people that the product is built on, and clause 5 of that licence points
the reader at this file.

WHERE THE AUTHORITATIVE COPY IS
-------------------------------
ThirdPartyAttributions in src\app\Ravers.App.Identity.pas, which is what the
application shows in its credits. This file is the copy that travels with the
repository and the download.

They are kept in step by tools\check-notices.ps1, which fails the build when a
component named in one is missing from the other, and also when a third party
unit is used anywhere under src\ or tests\ and appears in neither. That is the
same arrangement the licence text already has, and for the same reason: two
copies of a legal statement that nothing compares will differ, and the one
people read will be the wrong one.

WHY THERE IS SO LITTLE IN IT
----------------------------
Almost nothing here is somebody else's. That is not an accident: the obvious
dependencies for a product like this are the audio libraries, and the good ones
are GPL or LGPL. GPL cannot go into a closed source product at all, and LGPL
wants the user to be able to relink, which a statically linked Delphi binary
does not offer. So the time stretcher, the resampler, the file readers, the
analysis and the synthesis were all written here, which removes the question
instead of answering it.

There are two exceptions, and the difference between them is the point. LAME,
the MP3 encoder (section 8), proves the reasoning: it ships as its own DLL
beside the product, not inside it, so a user can put their own build of it in
its place. The two DTS codebooks taken from FFmpeg (section 14) do not and
cannot: they are LGPL 2.1 data compiled into the binary, where there is nothing
to relink. ETSI TS 102 114 does not print those two tables and says as much, so
reading DTS at all meant taking them from somewhere, and section 14 records the
decision to take them from FFmpeg rather than leave DTS to FFmpeg itself, with
the holder, the licence version, where the numbers came from and the offer of
their source.

Until 29 October 2026 this summary said LAME was the one exception, which
contradicted section 14 of this same file and understated what the product
carries. Clause 5 of LICENSE.txt named only LAME for the same reason and now
names both.

A dependency added later gets an entry BEFORE it is merged, not after the first
release. A font, an image or a sound is exactly as much of an obligation as a
library and gets an entry too.

HOW TO READ AN ENTRY
--------------------
"In the shipped product" means the code is compiled into the binary a user
downloads, and the notice travels with it.

"Build and test only" means it is used to develop or verify the product and is
NOT in the binary a user downloads. It is listed anyway, because the way a file
like this goes wrong is somebody adding a dependency and nobody noticing, and a
complete list is the only kind that can be checked.

UNRESOLVED means a fact is missing that has to be read from the source that
owns it, and it is written down as missing rather than guessed. A guessed line
in a legal notice is a false statement about somebody else's work in the one
document whose whole purpose is accuracy about it. The release build refuses to
run while any UNRESOLVED remains; the ordinary build reports them and carries
on, so an incomplete notice stops nobody working and stops anybody shipping.


-------------------------------------------------------------------------------
1. CLAP (CLever Audio Plug-in API), version 1.2.x
-------------------------------------------------------------------------------
Status:    In the shipped product.
Holder:    Alexandre Bique and the CLAP contributors.
Licence:   MIT.
Where:     https://github.com/free-audio/clap
Used for:  The plug-in format this application hosts.

No CLAP source is included. The application binary interface was translated to
Delphi from the published headers, in src\host\Ravers.Host.Clap.Types.pas and
its neighbours, and that translation is our own work.

The credit is here because it is owed, not because a licence compels it. MIT
requires the copyright and permission notices to travel with copies of the
software, and no copy of that software is being distributed. Naming the
standard the product implements and the people who wrote it costs nothing and
is true, so it is said whichever way the legal question falls. Whether more
than this is required is a question for the local legal opinion already on the
plan, and not one to settle by reading around the subject.


-------------------------------------------------------------------------------
2. Embarcadero RTL and FireMonkey, Delphi 11 Alexandria
-------------------------------------------------------------------------------
Status:    In the shipped product.
Holder:    Embarcadero Technologies.
Licence:   Embarcadero licence, under our own developer licence.
Where:     https://www.embarcadero.com
Used for:  The runtime library and the interface framework the application is
           built on. Every unit whose name begins System., FMX., Winapi., Vcl.,
           Macapi. or Posix. is theirs, and they are linked into the binary.

RESOLVED (a), 31 October 2026. This entry used to say that two things had to
    be read out of the developer licence agreement rather than remembered:
    whether the runtime may be redistributed at all in a product given away
    free, and whether an attribution line is owed. The agreement has now been
    read. The answers are yes it may, and no line is owed.

    WHICH AGREEMENT. The Software License and Support Agreement that applies to
    RAD Studio 11, Delphi 11 and C++Builder 11, published by Embarcadero and
    dated 13 September 2021. That is the edition this product is built with:
    tools\build.ps1 compiles against Studio\22.0, which is Alexandria. The
    installation is NOT Community Edition, whose terms are materially different
    and would have to be read separately. Community Edition ships neither
    C++Builder nor the macOS ARM64 compiler, and this one carries bcc64.exe and
    dccosxarm64.exe, both dated with the 11.0 release.

    MAY IT BE REDISTRIBUTED IN A PRODUCT GIVEN AWAY FREE. Yes. Clause 2.2.2(a)
    grants the licence to "make exact copies of the Redistributables and
    distribute those copies solely as components of Licensee's Works and solely
    as required for permitting end users of the Works to install and execute the
    Works". Nothing in 2.2.1, 2.2.2, 2.2.3 or anywhere else in the agreement
    conditions that grant on the Work being sold, on a price being charged or on
    a royalty being paid. The only condition it places on the Work itself is
    2.2.3(d): the Work must "add primary and substantial functionality to the
    Redistributables" and not be "merely a set or subset" of them. A digital
    audio workstation is not a thin wrapper around a runtime library, so that
    condition is met and it is not a close question. Clause 2.2.8 reserves
    royalties for "all other uses or distribution of the Redistributables",
    which means uses outside the 2.2.2 grant, not free Works inside it.

    IS AN ATTRIBUTION LINE REQUIRED. No. There is a notice obligation and it is
    not the same thing. Clause 2.2.3(c) requires that "all copies of the Works
    Licensee create must bear a valid copyright notice, either Licensee's own or
    the Licensor copyright notice that appears on the Product". Licensee's own
    satisfies it, and this product carries one. No clause anywhere in the
    agreement requires Embarcadero to be named, credited or acknowledged in the
    product or its documentation, so there is no prescribed wording to copy
    because there is no requirement to meet. The second half of 2.2.3(c), not to
    remove or alter a Licensor notice carried inside a Redistributable, is
    satisfied by not doing anything to it.

    SO WHY IS SECTION 2 STILL HERE. Because this file lists what the product is
    built on whether or not a licence compels the entry. That is the rule stated
    under HOW TO READ AN ENTRY and it is the same reason section 1 credits CLAP.
    Clause 2.2.3(b) permits this section explicitly: Licensor's names and
    trademarks may not be used to market the Work "except to state descriptively
    that Licensee's Work was written using the Product", which is what this
    section does and all it does.

    WHAT REMAINS, AND IT IS SMALL. The agreement read is the standard published
    one. An ordering document could in principle carry different terms, although
    clause 1 says this agreement governs and controls where the two conflict.
    The 2.2.2 grant is also limited to Works "created by Licensee using a duly
    licensed, properly registered copy of the Product", so what this entry
    leaves behind is an obligation to keep the licence current, not to add a
    line to anything.

    WHAT THIS CHANGED IN THE PRODUCT. Clause 2.2.3(c) is a condition on every
    copy, so it was checked rather than assumed, and the check failed. The
    binary's VERSIONINFO carried "Copyright (c) 2026 Ravers Co", built from
    APP_COMPANY, while the licence agreement, the credits screen and this file
    all name Unicorn Mystic Group Limited. A brand is not a legal person, and
    the signing certificate this is about to be signed with will name the
    company, so the one notice travelling inside the binary would have been the
    only one disagreeing. The build script now builds that line from
    APP_LEGAL_ENTITY, and tools\check-identity.ps1 fails the build if it is ever
    built from anything else.


-------------------------------------------------------------------------------
3. DUnitX, bundled with Delphi
-------------------------------------------------------------------------------
Status:    Build and test only. NOT in the shipped product.
Holder:    Vincent Parrett and contributors.
Licence:   Apache 2.0.
Where:     https://github.com/VSoftTechnologies/DUnitX
Used for:  The test framework. Every assertion in the suite runs through it and
           the console runner is the only binary the build script executes. The
           application does not reference it and does not link it.

The Apache 2.0 text is not reproduced here because nothing that carries this
notice carries DUnitX. Should any part of it ever reach the shipped product,
the full licence text has to come with it, along with the NOTICE requirements
of clause 4 of that licence.


-------------------------------------------------------------------------------
4. Fonts, images and sounds
-------------------------------------------------------------------------------
Status:    None at present.

Every image in the product is drawn here: brand\ holds the marks as SVG and
they are ours. There is no third party font in the tree. The typography work
still open on the plan will bring one, at which point it gets an entry with its
licence and its embedding permission. A font licence that permits desktop use
does not automatically permit embedding in an application, and that distinction
is where a file like this usually first becomes wrong.


-------------------------------------------------------------------------------
5. VST3, the plug-in interfaces
-------------------------------------------------------------------------------
Status:    In the shipped product.
Holder:    Steinberg Media Technologies GmbH.
Licence:   MIT, since VST3 SDK 3.8. Translated from SDK 3.8.1.
Where:     https://github.com/steinbergmedia/vst3sdk
Used for:  Hosting VST3 plug-ins.

No SDK file is in the product or in this repository. The interfaces were
translated to Delphi from Steinberg's published headers, in
src\host\Ravers.Host.Vst3.Types.pas, and the host that uses them is our own
work. Because a translation of the interface definitions may be a substantial
portion of them, Steinberg's notice travels with the product in full:

    MIT License

    Copyright (c) 2026, Steinberg Media Technologies GmbH

    Permission is hereby granted, free of charge, to any person obtaining a
    copy of this software and associated documentation files (the "Software"),
    to deal in the Software without restriction, including without limitation
    the rights to use, copy, modify, merge, publish, distribute, sublicense,
    and/or sell copies of the Software, and to permit persons to whom the
    Software is furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included in
    all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
    IN THE SOFTWARE.

The product does not use the VST name or logo. Should it ever do so,
Steinberg's usage guidelines apply, including the line "VST is a registered
trademark of Steinberg Media Technologies GmbH".

The test suite also compiles a small VST3 plug-in of our own against
Steinberg's generated C interface, which is BSD licensed. That header is never
in this repository and nothing built from it is shipped.


-------------------------------------------------------------------------------
6. ASIO, the low latency Windows driver interface
-------------------------------------------------------------------------------
Status:    Host written by Ravers Co. No part of Steinberg's ASIO SDK is in
           this repository or in the product.

The product talks to low latency audio drivers of the kind Steinberg calls
ASIO, through our own implementation of the driver interface
(src\platform\win\Ravers.Platform.Win.Asio.pas). It was written without
Steinberg's SDK and without accepting Steinberg's SDK licence, neither of
which is used, bundled or distributed. The drivers themselves are supplied
by the makers of the user's audio interface and are not part of this product.

The product carries no ASIO logo and makes no claim of ASIO compatibility or
certification.

ASIO is a trademark of Steinberg Media Technologies GmbH. The name appears in
this notice and in the source only to identify the kind of driver the product
can talk to. It does not indicate any endorsement by or affiliation with
Steinberg.


-------------------------------------------------------------------------------
7. minimp3, the MP3 standard's tables
-------------------------------------------------------------------------------
Status:    Tables in the shipped product.
Holder:    the minimp3 authors.
Licence:   CC0 1.0 (public domain).
Where:     https://github.com/lieff/minimp3
Used for:  The fixed tables of the MP3 standard inside the product's own MP3
           reader.

The product reads MP3 with its own code (src\media\Ravers.Media.Mp3.pas),
written for this product. The standard's fixed tables, and the arrangement of
the Huffman tables, the inverse transforms and the synthesis filter, follow
minimp3, whose authors dedicated it to the public domain under CC0 1.0. The
tables were generated from its header by tools\make-mp3-tables.pl into
src\media\Ravers.Media.Mp3Tables.inc rather than retyped. No minimp3 source
file is in this repository or in the product. CC0 asks nothing in return; the
credit is given because it is owed.

The test suite compares the reader with the ISO/IEC 11172-4 compliance
streams and their reference decodes kept alongside minimp3. Those files are
fetched once to a folder outside the repository and are never shipped.

-------------------------------------------------------------------------------
8. LAME, the MP3 encoder
-------------------------------------------------------------------------------
Status:    In the shipped product, as the separate library libmp3lame.dll.
Holder:    The LAME Project and the authors named in its source.
Licence:   GNU Library General Public License version 2, or any later version.
Where:     https://www.mp3dev.org and https://lame.sourceforge.io
Used for:  Writing MP3 files, as the first choice of encoder.

LAME 3.100 is built by tools\build.ps1 from its release source, unmodified,
with the configuration LAME ships for Windows compilers (configMS.h) and its
own export list (include\lame.def). Nothing in it is changed, added or taken
away. It is not compiled into the product: it is its own DLL beside the
product, loaded only from the product's folder, and the product works with
any build of LAME that keeps the same interface. You are free to put your own
build of it in its place, and clause 5 of the licence says so.

The source travels with it. The release tarball it was built from is in the
download as libmp3lame-source-3.100.tar.gz, SHA-256
ddfe36cab873794038ae2c1210557ad34857a4b6bdc515785d1da9e175b1da1e, which is
the hash of the published 3.100 release; the build refuses any other file. The
licence text is beside it as libmp3lame-LICENSE.txt. If either is ever missing
from a copy you received, write to [email protected] and they will be sent
at no charge, and that offer stands for three years from the last time this
version was offered for download.

LAME's decoder, MPGLIB, is licensed under the GPL and is not compiled in: the
build leaves HAVE_MPGLIB undefined, and MP3 is read by the product's own
reader (section 7).

The copyright lines in the LAME source files that are built are these,
copied from the files themselves: Mark Taylor; Takehiro Tominaga; Robert
Hegemann; Gabriel Bouvigne; Alexander Leidinger; Albert L. Faber; Naoki
Shibata; Jonathan Dee; John Dahlstrom; Don Melton; Olcios; David Robinson
and Glen Sawyer; Ron Mayer; and The LAME Project.

LAME's README suggests seeking advice about software patents before
redistributing it. The patents on MPEG audio layer three have expired, and
the licensing programme for them ended in 2017.


-------------------------------------------------------------------------------
9. Indy (Internet Direct), bundled with Delphi
-------------------------------------------------------------------------------
Status:    Build and test only. NOT in the shipped product.
Holder:    Chad Z. Hower and the Indy Pit Crew.
Licence:   Indy Modified BSD License, or at your choice the Indy MPL License.
Where:     https://github.com/IndySockets/Indy
Used for:  An HTTP server inside the test process, listening on the loopback
           address only, that the product's download transport is tested
           against. The units used are IdHTTPServer, IdCustomHTTPServer and
           IdContext. The application does not reference Indy and does not
           link it: its downloads go through the runtime library's HTTP client.

The licence text is not reproduced here because nothing that carries this
notice carries Indy. Should any part of it ever reach the shipped product, its
licence text has to come with it.

-------------------------------------------------------------------------------
10. libogg and libvorbis, the Ogg container and the Vorbis encoder
-------------------------------------------------------------------------------
Status:    In the shipped product, as the separate library libvorbis.dll,
           which holds both.
Holder:    Xiph.org Foundation.
Licence:   BSD three clause.
Where:     https://xiph.org/vorbis and https://xiph.org/ogg
Used for:  Writing Ogg Vorbis files. Reading them is the product's own work
           and uses neither library.

libogg 1.3.6 and libvorbis 1.3.7 are built by tools\build.ps1 from their
release source, unmodified, with the export lists the two projects ship for
Windows. The one file that is not theirs is include\ogg\config_types.h, which
their own configure or cmake writes and neither tarball carries; the build
writes it for a compiler with stdint.h. The licence text is beside the library
as libogg-LICENSE.txt and libvorbis-LICENSE.txt.

The copyright line in both, copied from the files themselves, is: Copyright
(c) 2002, Xiph.org Foundation for libogg, and Copyright (c) 2002-2020
Xiph.org Foundation for libvorbis.


-------------------------------------------------------------------------------
11. libopus, the Opus codec
-------------------------------------------------------------------------------
Status:    In the shipped product, as the separate library libopus.dll.
Holder:    Xiph.Org and the authors named in its source, which are Xiph.Org,
           Skype Limited, Octasic, Jean-Marc Valin, Timothy B. Terriberry,
           CSIRO, Gregory Maxwell, Mark Borgerding, Erik de Castro Lopo,
           Mozilla and Amazon.
Licence:   BSD three clause.
Where:     https://opus-codec.org
Used for:  Reading and writing Opus. The container work around it, the pages,
           the head packets, the pre-skip and the channel order, is the
           product's own.

libopus 1.6.1 is built by tools\build.ps1 from its release source, unmodified,
from the file lists Opus ships in its own make fragments. It is built without
optimisation because the C compiler in Delphi 11 is a Clang 5 that miscompiles
Opus at every level above none; the library is correct as built and decodes
around 175 times faster than the sound it reads.

The copyright line, copied from its COPYING file, is: Copyright 2001-2023
Xiph.Org, Skype Limited, Octasic, Jean-Marc Valin, Timothy B. Terriberry,
CSIRO, Gregory Maxwell, Mark Borgerding, Erik de Castro Lopo, Mozilla, Amazon.

Opus is subject to royalty free patent licences, which its COPYING file lists
in full and which is beside the library as libopus-LICENSE.txt.

-------------------------------------------------------------------------------
12. ATSC A/52, the AC-3 standard's tables
-------------------------------------------------------------------------------
Status:    Tables in the shipped product.
Holder:    Advanced Television Systems Committee, Inc.
Licence:   None needed: the numbers a published standard prints
Where:     https://www.atsc.org
Used for:  The fixed tables of the AC-3 standard inside the product's own AC-3
           reader.

The product reads AC-3 with its own code (src\media\Ravers.Media.Ac3.pas),
written for this product from the text of ATSC A/52:2018, Digital Audio
Compression (AC-3, E-AC-3), which the ATSC publishes for free download. The
fixed tables the standard prints, the frame sizes, the band structure, the
quantiser levels, the hearing thresholds and the transform window, were read
out of that document by tools\make-ac3-tables.pl into
src\media\Ravers.Media.Ac3Tables.inc rather than retyped. That script verifies
the shape and the length of every table it writes and refuses to write one it
cannot verify. No third party AC-3 source is in this repository or in the
product, and the standard document itself is not in either.

The reader is held to FFmpeg's decoder in the test suite. FFmpeg is not
shipped, is not linked, and none of its code is in this product; it is used as
a reference the way a tuning fork is.

No Dolby trade mark is used and none is claimed. "AC-3" is used as the name of
the format the standard defines, which is what the standard calls it.

-------------------------------------------------------------------------------
13. ETSI TS 102 114, the DTS standard's tables
-------------------------------------------------------------------------------
Status:    Tables in the shipped product.
Holder:    European Telecommunications Standards Institute
Licence:   None needed: the numbers a published standard prints
Where:     https://www.etsi.org
Used for:  The fixed tables of the DTS Coherent Acoustics standard inside the
           product's own DTS reader.

The product reads the DTS core with its own code (src\media\Ravers.Media.Dts.pas),
written for this product from ETSI TS 102 114 V1.6.1, DTS Coherent Acoustics;
Core and Extensions with Additional Profiles, which ETSI publishes free. The
tables that standard prints were read out of it by tools\make-dts-tables.pl into
src\media\Ravers.Media.DtsTables.inc, and that script checks every one of them.
Four codes of one Huffman book (D65) are not printed anywhere in the text, one
minus sign in another (D129) is lost, and one figure in a block code book is
misprinted; the script names each of those and says how it settles it. The
standard document itself is not in the repository or the product.

No DTS trade mark or logo is used and no DTS certification is claimed. "DTS" is
used as the name of the format the standard describes.

-------------------------------------------------------------------------------
14. FFmpeg, two DTS codebooks
-------------------------------------------------------------------------------
Status:    Tables in the shipped product.
Holder:    the FFmpeg developers, including Gildas Bazin and Benjamin Larsson
Licence:   GNU Lesser General Public License version 2.1 or later
Where:     https://ffmpeg.org
Used for:  The two codebooks the DTS standard does not print, inside the
           product's own DTS reader.

ETSI TS 102 114 needs two tables it does not print: D.10.1, the ADPCM prediction
codebook of 4 096 vectors, and D.10.2, the high frequency VQ codebook of 1 024.
Of both it says "Due to its extensive size, this table is not included here",
and no release of the standard carries them as an attachment. They are taken,
unmodified and as numbers only, from libavcodec/dcadata.c in FFmpeg at release
tag n8.0, which is licensed under the GNU Lesser General Public License version
2.1 or later, by tools\make-dts-tables.pl into
src\media\Ravers.Media.DtsCodebooks.inc. That file holds those two tables and
nothing else. No FFmpeg code is in the product.

The file they came from, with its copyright notice, is at
https://github.com/FFmpeg/FFmpeg/blob/n8.0/libavcodec/dcadata.c, and a copy of
it, and of the two tables as this product holds them, is available on request
from [email protected] for three years from the release that contains them.
The GNU Lesser General Public License version 2.1 is at
https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.

The decision to take these two tables from FFmpeg rather than leave DTS to FFmpeg
itself was Gareth Erasmus's, on 16 September 2026, knowing they are LGPL data
inside a closed product.

Trademarks

VST is a registered trademark of Steinberg Media Technologies GmbH.

Questions about the licence: [email protected]

Checkout