CutE by 42NET – Audacity-based Multi-Platform Audio Editor with Database-Backed Workflow | C++ -- 2
Budget: $250 – $750 USD
CutE by 42NET – Project Concept (US / International Version)
1. Project Goal
CutE by 42NET is a professional, multi-platform audio editing application built on top of the Audacity open-source codebase.
The goal of the project is to:
Edit real audio files while managing their metadata and business-related information through a database-backed workflow.
The objective is not to create a new audio engine, but to extend an existing, stable foundation to meet professional and business-oriented requirements.
2. Platform and Technology
CutE is designed as a multi-platform application:
- Windows
- macOS
- Linux
Core technologies:
- C++
- wxWidgets
- Audacity codebase
- CMake
- ODBC
- Microsoft SQL Server
3. Audio Asset Model
In CutE, audio assets exist as actual files, typically in the following formats:
- WAV
- MP3
- MP2
Audio editing always operates on real audio files.
The database does not store audio data.
Instead, it stores:
- Meta data (title, description, duration, modification time)
- categories
- status information
- permission data
- business-related attributes
There is a logical relationship between audio files and database records, not a physical one.
4. Role of the Database
The database is responsible for:
- managing metadata associated with audio files
- categorization
- searching and listing
- enforcing permissions
- supporting business logic
When an audio file is opened or saved, the application performs database operations to read or update metadata related to that file.
5. Project Foundations
The following foundations are already in place:
- Audacity-based application structure
- working build system
- database connectivity
- authentication architecture scaffolding
The current project phase focuses on:
Implementing the described behavior on top of the existing, functional foundation.
6. Authentication and Permissions
CutE includes a database-backed permission model that:
- is user-based
- controls access to audio assets
- defines available operations per user
Permissions determine:
- which audio assets are visible
- which categories are accessible
- which actions are allowed
The permission system is part of the core business logic, independent of UI implementation.
7. Voice-Centric Workflow
The primary working unit in CutE is a Voice, which:
- represents a specific audio file
- has associated database metadata
- belongs to a category
- is permission-controlled
Open Voice
- selection happens through a database-backed list
- the selected item opens its corresponding audio file for editing
Save
- audio changes are written back to the file
- metadata updates are persisted in the database
8. User Interface and Usage
The CutE user interface is designed for:
- professional use
- fast operation
- keyboard-oriented workflows
- high-resolution displays
The visual design aims to be:
- clean
- readable
- suitable for long working sessions
9. Editing Philosophy
The editing model is:
- selection
- optimized for speed
- inspired by Sound Forge workflows
- built on top of the Audacity audio engine
10. Project Direction
In this project:
- the application foundation already exists
- the infrastructure is operational
- development focuses on implementing functional requirements incrementally
CutE is not a greenfield project, but a targeted extension of a proven codebase, with a clearly defined direction and scope.
11. One-Sentence Summary
CutE by 42NET is a multi-platform, Audacity-based audio editing application that operates on real audio files while managing their metadata and permissions through a Microsoft SQL Server–backed workflow.
1. Project Goal
CutE by 42NET is a professional, multi-platform audio editing application built on top of the Audacity open-source codebase.
The goal of the project is to:
Edit real audio files while managing their metadata and business-related information through a database-backed workflow.
The objective is not to create a new audio engine, but to extend an existing, stable foundation to meet professional and business-oriented requirements.
2. Platform and Technology
CutE is designed as a multi-platform application:
- Windows
- macOS
- Linux
Core technologies:
- C++
- wxWidgets
- Audacity codebase
- CMake
- ODBC
- Microsoft SQL Server
3. Audio Asset Model
In CutE, audio assets exist as actual files, typically in the following formats:
- WAV
- MP3
- MP2
Audio editing always operates on real audio files.
The database does not store audio data.
Instead, it stores:
- Meta data (title, description, duration, modification time)
- categories
- status information
- permission data
- business-related attributes
There is a logical relationship between audio files and database records, not a physical one.
4. Role of the Database
The database is responsible for:
- managing metadata associated with audio files
- categorization
- searching and listing
- enforcing permissions
- supporting business logic
When an audio file is opened or saved, the application performs database operations to read or update metadata related to that file.
5. Project Foundations
The following foundations are already in place:
- Audacity-based application structure
- working build system
- database connectivity
- authentication architecture scaffolding
The current project phase focuses on:
Implementing the described behavior on top of the existing, functional foundation.
6. Authentication and Permissions
CutE includes a database-backed permission model that:
- is user-based
- controls access to audio assets
- defines available operations per user
Permissions determine:
- which audio assets are visible
- which categories are accessible
- which actions are allowed
The permission system is part of the core business logic, independent of UI implementation.
7. Voice-Centric Workflow
The primary working unit in CutE is a Voice, which:
- represents a specific audio file
- has associated database metadata
- belongs to a category
- is permission-controlled
Open Voice
- selection happens through a database-backed list
- the selected item opens its corresponding audio file for editing
Save
- audio changes are written back to the file
- metadata updates are persisted in the database
8. User Interface and Usage
The CutE user interface is designed for:
- professional use
- fast operation
- keyboard-oriented workflows
- high-resolution displays
The visual design aims to be:
- clean
- readable
- suitable for long working sessions
9. Editing Philosophy
The editing model is:
- selection
- optimized for speed
- inspired by Sound Forge workflows
- built on top of the Audacity audio engine
10. Project Direction
In this project:
- the application foundation already exists
- the infrastructure is operational
- development focuses on implementing functional requirements incrementally
CutE is not a greenfield project, but a targeted extension of a proven codebase, with a clearly defined direction and scope.
11. One-Sentence Summary
CutE by 42NET is a multi-platform, Audacity-based audio editing application that operates on real audio files while managing their metadata and permissions through a Microsoft SQL Server–backed workflow.