feat: complete openDAW -> openDIAW.be rename (48 occurrences across 21 files)
Header menu, MissingFeature, Privacy, Imprint, Errors, dialogs, auth-callback, all manuals (index, cloud-backup, permissions, recording, file-system, browser-support, tech-stack, creating-a-device, shadertoy, apparat, spielwerk, werkstatt). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
kxkm
@@ -3,7 +3,7 @@
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Authentication - openDAW</title>
|
||||
<title>Authentication - openDIAW.be</title>
|
||||
<style>
|
||||
body {
|
||||
font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, sans-serif;
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Browser Support Manuals
|
||||
|
||||
openDAW is tested on the latest version of all modern browsers, such as Chrome, Firefox, and Safari.
|
||||
openDIAW.be is tested on the latest version of all modern browsers, such as Chrome, Firefox, and Safari.
|
||||
|
||||
However, there are differences in which web APIs are supported by each browser.
|
||||
|
||||
|
||||
@@ -1,26 +1,26 @@
|
||||
# Cloud Backup
|
||||
|
||||
openDAW supports privately synchronizing your projects in [Google Drive](action://backup-google-drive) and [Dropbox](action://backup-dropbox).
|
||||
openDIAW.be supports privately synchronizing your projects in [Google Drive](action://backup-google-drive) and [Dropbox](action://backup-dropbox).
|
||||
Both services require a one-time **OAuth login**. OAuth is the official login method provided by many cloud services.
|
||||
|
||||
## Flow
|
||||
|
||||
- You log in directly on the provider’s website
|
||||
- openDAW receives a secure access token from them
|
||||
- openDAW never sees your password or personal data
|
||||
- No personal data or assets are stored on openDAW servers
|
||||
- openDIAW.be receives a secure access token from them
|
||||
- openDIAW.be never sees your password or personal data
|
||||
- No personal data or assets are stored on openDIAW.be servers
|
||||
- Everything stays in your own cloud account
|
||||
|
||||
---
|
||||
|
||||
## How to run a backup
|
||||
|
||||
Every time you click openDAW menu > Cloud Backup > (Select service), openDAW synchronizes all projects and samples with
|
||||
Every time you click openDIAW.be menu > Cloud Backup > (Select service), openDIAW.be synchronizes all projects and samples with
|
||||
your connected cloud service, uploading new and changed files and removing those that were deleted locally.
|
||||
|
||||
## How it works
|
||||
|
||||
During backup, openDAW uploads new and modified files and updates its index.json catalog for each domain (projects and
|
||||
During backup, openDIAW.be uploads new and modified files and updates its index.json catalog for each domain (projects and
|
||||
samples). If a backup is aborted, some files may remain in the cloud without being referenced in the catalog. It is also
|
||||
not recommended to modify or move the files directly in the cloud, as remote changes can confuse the backup system and
|
||||
cause it to stop working as expected.
|
||||
@@ -33,17 +33,17 @@ cause it to stop working as expected.
|
||||
|
||||
1. Go to [Google Drive settings](https://drive.google.com/drive/settings)
|
||||
2. Click **Manage apps**
|
||||
3. Find **openDAW** in the list
|
||||
3. Find **openDIAW.be** in the list
|
||||
4. Choose one of the following:
|
||||
- **Disconnect from Drive** → removes openDAW’s access to your Drive
|
||||
- **Delete hidden app data** (if shown) → permanently deletes all files openDAW stored in your hidden appData space
|
||||
- **Disconnect from Drive** → removes openDIAW.be’s access to your Drive
|
||||
- **Delete hidden app data** (if shown) → permanently deletes all files openDIAW.be stored in your hidden appData space
|
||||
|
||||
### Dropbox (recommended, faster)
|
||||
|
||||
1. Go to [Dropbox connected apps](https://www.dropbox.com/account/connected_apps?utm_source=opendaw.studio)
|
||||
2. Find **openDAW** in the list
|
||||
2. Find **openDIAW.be** in the list
|
||||
3. Click **Disconnect**
|
||||
4. When prompted, choose to also **delete all app folder data** if you want to remove files created by openDAW
|
||||
4. When prompted, choose to also **delete all app folder data** if you want to remove files created by openDIAW.be
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
# Creating an Audio Effect Device for openDAW
|
||||
# Creating an Audio Effect Device for openDIAW.be
|
||||
|
||||
### Disclaimer
|
||||
|
||||
Adding a device to openDAW itself requires a PR. There is not yet an open device API hence adding a new device involves
|
||||
significant manual work. This guide documents how to create a complete audio effect device in openDAW.
|
||||
Adding a device to openDIAW.be itself requires a PR. There is not yet an open device API hence adding a new device involves
|
||||
significant manual work. This guide documents how to create a complete audio effect device in openDIAW.be.
|
||||
|
||||
## Overview
|
||||
|
||||
|
||||
@@ -165,7 +165,7 @@ Select **Examples** in the code editor toolbar to load ready-made processors (Ha
|
||||
Copy the following prompt into an AI assistant to get help writing Werkstatt processors:
|
||||
|
||||
```
|
||||
You are helping the user write a DSP processor for the openDAW Werkstatt audio effect.
|
||||
You are helping the user write a DSP processor for the openDIAW.be Werkstatt audio effect.
|
||||
The user writes plain JavaScript (no imports, no modules). The code runs inside an AudioWorklet.
|
||||
|
||||
The code MUST define a class called `Processor` with the following interface:
|
||||
|
||||
@@ -226,7 +226,7 @@ Select **Examples** in the code editor toolbar to load ready-made instruments (S
|
||||
Copy the following prompt into an AI assistant to get help writing Apparat instruments:
|
||||
|
||||
```
|
||||
You are helping the user write an instrument processor for the openDAW Apparat device.
|
||||
You are helping the user write an instrument processor for the openDIAW.be Apparat device.
|
||||
The user writes plain JavaScript (no imports, no modules). The code runs inside an AudioWorklet.
|
||||
|
||||
The code MUST define a class called `Processor` with the following interface:
|
||||
|
||||
@@ -221,7 +221,7 @@ Select **Examples** in the code editor toolbar to load ready-made processors (Ch
|
||||
Copy the following prompt into an AI assistant to get help writing Spielwerk processors:
|
||||
|
||||
```
|
||||
You are helping the user write a MIDI effect processor for the openDAW Spielwerk device.
|
||||
You are helping the user write a MIDI effect processor for the openDIAW.be Spielwerk device.
|
||||
The user writes plain JavaScript (no imports, no modules). The code runs inside an AudioWorklet.
|
||||
|
||||
The code MUST define a class called `Processor` with the following interface:
|
||||
|
||||
@@ -41,7 +41,7 @@ While frozen:
|
||||
## Automatic Unfreezing
|
||||
|
||||
Frozen audio is rendered at a specific tempo. When the tempo changes, the cached audio would no longer be in sync with
|
||||
the timeline. openDAW automatically unfreezes all frozen audio units when:
|
||||
the timeline. openDIAW.be automatically unfreezes all frozen audio units when:
|
||||
|
||||
- The **project tempo (BPM)** is changed manually
|
||||
- **Tempo automation** is added, removed, or modified
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
# openDAW Manuals
|
||||
# openDIAW.be Manuals
|
||||
|
||||
Please join our [discord community](https://discord.opendaw.studio) for updates and news!
|
||||
|
||||
## Known Issues
|
||||
|
||||
**openDAW is in an early prototype stage and NOT ready for production use!**
|
||||
**openDIAW.be is in an early prototype stage and NOT ready for production use!**
|
||||
|
||||
### General
|
||||
|
||||
* Some features in openDAW may be unpolished or not functional yet.
|
||||
* Some features in openDIAW.be may be unpolished or not functional yet.
|
||||
* No backward compatibility is guaranteed. New studio versions may invalidate old project files.
|
||||
|
||||
### Audio Engine
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
|
||||
## TLDR
|
||||
|
||||
Browsers only reveal the full list of audio devices once microphone access has been granted. That’s why openDAW needs to
|
||||
Browsers only reveal the full list of audio devices once microphone access has been granted. That’s why openDIAW.be needs to
|
||||
request microphone permission before you can select inputs. We recommend allowing this access permanently when prompted,
|
||||
as it makes working with openDAW much smoother.
|
||||
as it makes working with openDIAW.be much smoother.
|
||||
|
||||
## More Info
|
||||
|
||||
@@ -12,7 +12,7 @@ In all modern browsers, `navigator.mediaDevices.enumerateDevices()` will only li
|
||||
user
|
||||
grants permission—typically via a getUserMedia() call. Chrome, Safari, and Firefox have all adopted this behavior to
|
||||
protect user privacy and reduce fingerprinting risks. Without permission, device names, IDs, or availability remain
|
||||
hidden. This is how browsers are designed. Granting microphone access ensures openDAW can list
|
||||
hidden. This is how browsers are designed. Granting microphone access ensures openDIAW.be can list
|
||||
all connected audio devices properly.
|
||||
|
||||
[Lookup 'enumerateDevices'](https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/enumerateDevices)
|
||||
@@ -1,26 +1,26 @@
|
||||
# openDAW File System
|
||||
# openDIAW.be File System
|
||||
|
||||
openDAW stores your projects and samples in the
|
||||
openDIAW.be stores your projects and samples in the
|
||||
[Origin private file system](https://developer.mozilla.org/en-US/docs/Web/API/File_System_API/Origin_private_file_system) (
|
||||
OPFS).
|
||||
|
||||
## Why Samples?
|
||||
|
||||
openDAW uses the OPFS to store user-imported samples because modern browsers do not retain
|
||||
openDIAW.be uses the OPFS to store user-imported samples because modern browsers do not retain
|
||||
information about the file origins of imported local files due to security restrictions. This means that once a user
|
||||
imports a file, the browser has no way to automatically reload it the next time openDAW starts. To ensure persistent
|
||||
access to user samples, openDAW copies every imported sample into OPFS, allowing the application to manage and retrieve
|
||||
imports a file, the browser has no way to automatically reload it the next time openDIAW.be starts. To ensure persistent
|
||||
access to user samples, openDIAW.be copies every imported sample into OPFS, allowing the application to manage and retrieve
|
||||
these files securely without relying on external file paths.
|
||||
|
||||
## Granting OPFS Storage Permission in Firefox
|
||||
|
||||
In Firefox, storing data in OPFS requires explicit user approval due to its privacy settings. Without permission,
|
||||
openDAW may not be able to retain imported samples across sessions. To allow persistent storage for openDAW in Firefox,
|
||||
openDIAW.be may not be able to retain imported samples across sessions. To allow persistent storage for openDIAW.be in Firefox,
|
||||
follow these steps:
|
||||
|
||||
* Open Firefox Settings
|
||||
* Navigate to Privacy & Security
|
||||
* Scroll down to Permissions and find Storage Permissions
|
||||
* Click Exceptions and enter the openDAW studio URL `https://opendaw.studio`
|
||||
* Click Exceptions and enter the openDIAW.be studio URL `https://opendaw.studio`
|
||||
* Select Allow and confirm the changes
|
||||
* Restart Firefox for the settings to take effect
|
||||
@@ -77,6 +77,6 @@ note input.
|
||||
|
||||
## Latency Compensation
|
||||
|
||||
openDAW automatically compensates for system latency when recording. The recorded audio and MIDI data is aligned to the
|
||||
openDIAW.be automatically compensates for system latency when recording. The recorded audio and MIDI data is aligned to the
|
||||
correct timeline position regardless of your output device latency. However, lower latency still provides a better
|
||||
real-time playing experience.
|
||||
|
||||
@@ -89,7 +89,7 @@ The following Shadertoy features are **not available**:
|
||||
|
||||
## 6. Video Export
|
||||
|
||||
Export your shader visualization as an MP4 video file via **openDAW Menu** > Export > Video...
|
||||
Export your shader visualization as an MP4 video file via **openDIAW.be Menu** > Export > Video...
|
||||
|
||||
### Export Settings
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ The repository is a multi-package workspace managed with npm workspaces, Turbo,
|
||||
|
||||
## Libraries
|
||||
|
||||
openDAW uses minimal external dependencies, avoiding hidden behaviors from bulky UI frameworks.
|
||||
openDIAW.be uses minimal external dependencies, avoiding hidden behaviors from bulky UI frameworks.
|
||||
|
||||
Each in-house library has a clear, focused purpose.
|
||||
|
||||
|
||||
@@ -10,10 +10,10 @@ type Construct = { error: unknown }
|
||||
export const MissingFeature = ({error}: Construct) => {
|
||||
return (
|
||||
<div className={className}>
|
||||
<h1>Get openDAW Working</h1>
|
||||
<h1>Get openDIAW.be Working</h1>
|
||||
<h2>An important feature <span style={{color: Colors.purple.toString()}}>"{error}"</span> is missing.</h2>
|
||||
<p>Please update your browser or switch to the latest Chrome (recommended).</p>
|
||||
<p>openDAW should run on all modern browsers like Chrome, Edge, Firefox, and Safari.</p>
|
||||
<p>openDIAW.be should run on all modern browsers like Chrome, Edge, Firefox, and Safari.</p>
|
||||
<p>If you are already using one of these, please report your problem to <a
|
||||
href="mailto:support@opendaw.org">support@opendaw.org</a></p>
|
||||
</div>
|
||||
|
||||
@@ -312,7 +312,7 @@ export namespace Dialogs {
|
||||
<p>{message}</p>
|
||||
{foreignHostname !== null ? (
|
||||
<p style={{color: Colors.red.toString()}}>
|
||||
This error originated from external code ({foreignHostname}), not openDAW.
|
||||
This error originated from external code ({foreignHostname}), not openDIAW.be.
|
||||
If you are using a proxy or have browser extensions installed, please disable them.
|
||||
</p>
|
||||
) : probablyHasExtension && (
|
||||
|
||||
@@ -79,7 +79,7 @@ export const Header = ({lifecycle, service}: Construct) => {
|
||||
<header className={className}>
|
||||
<MenuButton root={service.menu}
|
||||
appearance={{color: Colors.gray, activeColor: Colors.bright, tinyTriangle: true}}>
|
||||
<h5>openDAW</h5>
|
||||
<h5>openDIAW.be</h5>
|
||||
</MenuButton>
|
||||
<hr/>
|
||||
<Group onInit={element => StudioPreferences.catchupAndSubscribe(enabled =>
|
||||
|
||||
@@ -20,7 +20,7 @@ export const ErrorsPage: PageFactory<StudioService> = ({lifecycle}: PageContext<
|
||||
return (
|
||||
<div className={className}>
|
||||
<h1>Errors</h1>
|
||||
<p>This page shows all errors reported from users running openDAW in production, helping us identify and fix
|
||||
<p>This page shows all errors reported from users running openDIAW.be in production, helping us identify and fix
|
||||
issues.</p>
|
||||
<h5>Report any issues <a href="https://github.com/andremichelle/opendaw/issues/"
|
||||
target="github"
|
||||
|
||||
@@ -24,7 +24,7 @@ export const ImprintPage: PageFactory<StudioService> = ({}: PageContext<StudioSe
|
||||
This imprint is provided to comply with German law.<br/>
|
||||
</p>
|
||||
<p>
|
||||
For inquiries regarding openDAW, please use the contact above or visit <a style={{color: Colors.blue}}
|
||||
For inquiries regarding openDIAW.be, please use the contact above or visit <a style={{color: Colors.blue}}
|
||||
href="https://opendaw.org">opendaw.org</a>
|
||||
</p>
|
||||
</div>
|
||||
|
||||
@@ -9,16 +9,16 @@ const className = Html.adoptStyleSheet(css, "PrivacyPage")
|
||||
export const PrivacyPage: PageFactory<StudioService> = ({}: PageContext<StudioService>) => (
|
||||
<div className={className}>
|
||||
<h1>Privacy Policy</h1>
|
||||
<p style={{color: Colors.blue.toString()}}>openDAW respects your privacy. This application does not collect
|
||||
<p style={{color: Colors.blue.toString()}}>openDIAW.be respects your privacy. This application does not collect
|
||||
personal data, create user accounts, or track visitors.</p>
|
||||
<h3>Local storage</h3>
|
||||
<p>Your projects and samples are stored on your own device (local file system or browser storage). No
|
||||
personal information is sent to our servers.</p>
|
||||
<h3>Cloud connections</h3>
|
||||
<p>If you choose to connect a cloud service (e.g. Google Drive or Dropbox), openDAW uses the official OAuth
|
||||
<p>If you choose to connect a cloud service (e.g. Google Drive or Dropbox), openDIAW.be uses the official OAuth
|
||||
process. The access tokens are stored only in your browser or desktop app and are never shared with us.</p>
|
||||
<h3>Data usage</h3>
|
||||
<p>openDAW does not process, analyze, or share any personal data. Files remain under your control in your chosen
|
||||
<p>openDIAW.be does not process, analyze, or share any personal data. Files remain under your control in your chosen
|
||||
storage location.</p>
|
||||
<h3>Contact</h3>
|
||||
<p>For questions about this policy, contact: <a style={{color: Colors.blue}}
|
||||
|
||||
@@ -80,7 +80,7 @@ export const ErrorEntry = ({entry}: Construct) => {
|
||||
script_tags: entry.script_tags,
|
||||
logs: entry.logs
|
||||
}
|
||||
const prompt = `Please help me fix this error in the openDAW codebase.
|
||||
const prompt = `Please help me fix this error in the openDIAW.be codebase.
|
||||
|
||||
Error Information:
|
||||
\`\`\`json
|
||||
|
||||
Reference in New Issue
Block a user