Catalogues, mixes, and audio work a chat window cannot hear

A mix still opens as a session. Pro Tools, Ableton, Logic, or a cousin. Stems sit in a Dropbox or Drive folder named for the artist and the date. The engineer has a reference track and a list of notes from the artist that arrived at midnight. Cyriac Zeh and Nidrosoft start by watching how that folder is organized and who is allowed to bounce a master. We do not start with a prompt that claims it can finish the record. We start with the file that is actually on the drive.

Labels and publishers run a second stack. A catalogue spreadsheet holds title, ISRC, writers, splits, and whether the PRO registration went through. Someone copies those rows into DistroKid, TuneCore, a distributor portal, or a custom admin. Metadata errors show up as a missing writer on a statement. Nidrosoft sits with that sheet before we talk about models. If the sheet is the record, the first build drafts a row and a checklist. It does not invent a split.

Managers and artists live in the inbox. A sync request lands as a PDF. A playlist pitch is a paragraph someone rewrites from last month. A show needs an EPK, a stage plot, and a video the intern cannot find. Octana exists because that last request is often a message with a deadline. Clear Audio AI exists because the voice note from the venue is unusable. MixGuidera exists because the producer wants a second set of ears before they send the bounce. Those three products are public. Custom work starts when your catalogue or your rights pile needs a path they do not ship.

What people ask Nidrosoft for is time on the boring edges. Clean a field recording. Get a first pass of mix notes. Turn a release blurb into a video. File a registration packet. They do not ask us to replace the mixer they trust or to decide a split that counsel has not seen. We will draft. A person still prints the master, signs the split, and hits send on the pitch.

Clear Audio AI is a public Nidrosoft product for noise removal, voice clarity, and batch cleanup. A podcast host, a manager with a venue recording, or a content lead with a noisy interview drops a file and previews the result. Export formats cover the usual delivery. Processing is meant to be short enough to use between sessions. We built it because bad rooms still happen and a second recorder is not always in the bag.

Studios use it as a prep step, not as the mix. A location vocal gets cleaned, then it goes back into the session on its own track. A spoken intro for a reel gets cleaned, then it goes to the editor. Nidrosoft will not claim a model replaced a dialogue editor on a feature. We will claim you can hear a voice over HVAC and traffic well enough to decide whether to re-record. That decision stays human.

Batch work matters when a catalogue of interviews or live clips sits in one folder. Someone names files by date and guest. Someone does not. We look at the folder before we promise batch. A custom build can watch a Dropbox path, clean new files, and write the result next to the original with a suffix. The original stays untouched. Overwriting a master is not a default we will ship.

If your problem is a full mix, skip this product and look at MixGuidera or at an engineer. Clear Audio AI will make a bad arrangement louder and cleaner. That is not a favor. Cyriac Zeh will say that on a call if you send a stereo bounce and ask for magic. Cleanup and mix notes are different jobs. We keep the products named so you can buy the right one.

MixGuidera is a public mixing assistant. You give it a track and a reference. It returns notes on EQ, compression, and balance against genre habits and that reference. Producers who are learning, or who are too close to a session, use it before they send to an artist. Nidrosoft did not build it to replace a mixer with a client roster. We built it so the first revision is about music, not about a low end that hid under headphones.

The useful habit is to treat the notes as a checklist in the session. Solo the kick. Check the vocal against the reference. Move one band, bounce, listen on the cheap speaker. Teams that paste the notes into Slack and never open the session wasted the run. We would rather you ignore half the notes after you listen than accept all of them because a page said to. Ears still win.

Custom work around MixGuidera looks like a house template. A label that always wants vocals forward. A podcast network that always wants a limiter ceiling. A game audio lead who cares about a loudness target. We can lock those house rules into the checklist. We will not hide them inside a black box. The engineer should see the rule that fired. If they cannot, they will stop using the tool after one bad bounce.

Masters and delivery specs are a later conversation. Streaming loudness, a WAV for vinyl, a split for stems. MixGuidera is not a mastering chain we sell as a button. If you need a delivery checklist that reads the bounce and flags a missing ISRC chunk or a clipped file, that is a build we can scope. A person still uploads to the distributor. The checklist only stops the file that will bounce back next week.

Octana is live. You send a message. You get a finished video. Managers, labels, and artists use that path when a release needs a clip and the editor is on another job. Nidrosoft ships it as a product, not as a slide about generative video. The point is a file you can post or send, with a human still choosing the take. If the message is vague, the video will be vague. Write the song, the visual, and the length you need.

Rights still sit outside the render. A face, a sample, a logo, a room you do not own. We will not tell you Octana cleared those. Your manager or your counsel does. A custom pipeline can attach a checklist to each render: source footage, talent release, composition, and who approved the post. That checklist is the build. The render is the product. Mixing them without the list is how a clip comes down after it has already run.

Catalogue teams often need many short clips from one release. Same audio, different aspect, different caption. Octana covers the message-to-video job. A custom build can take a folder of stills and a WAV and spit the cutdowns you already storyboarded. We time that work on your folder, not on a demo reel. If your storyboard is a text in a group chat, we will write it down first. Models do poorly against a chat that changed twice since lunch.

Live shows and tours add another pile: recap cuts, merch spots, a thank-you from the bus. Those files arrive late and noisy. Clear Audio AI on the voice, Octana on the cut, a person on the caption that names the city correctly. Nidrosoft will not auto-post to the artist account. Tokens and passwords for social stay with the manager. We have seen enough stolen sessions to keep it that way.

Nidrosoft has not shipped a public rights or royalty product. There is no catalogue OS in the archive, and we will not pretend Clear Audio AI is one. The work we will take looks like the rest of our ops builds. A split sheet arrives as an email or a Doc. We draft a structured row: writers, publishers, shares that add to 100, and the missing signature. A person at the label or the publisher confirms the math. We will not invent a writer so the row looks complete.

PRO and distributor registrations are checklists. Title, ISRC, ISWC if you have it, performers, recordings, and the territory list someone always forgets. We can prefill from the catalogue sheet and flag blanks. The submit button stays with the person who has the login. A failed registration that a bot submitted under the wrong entity is a mess we refuse to own. Scope will say that in a sentence a lawyer can read.

Sync packets are a third pile. A supervisor asks for instrumentals, lyrics, and a quote. Someone hunts stems. Someone hunts the agreement. Someone writes a reply that forgets the hold. A useful system assembles the folder from known paths and drafts the reply with the quote the business affairs person already approved. NanoBrief is the public cousin for questionnaire-to-brief work in under two minutes. A sync reply is slower because money sits in the sentence.

Statements arrive as PDFs and CSVs from different societies and stores. Matching them to the catalogue sheet is a human job we can assist. We draft exceptions: a title we cannot match, a share that does not equal the sheet, a territory you did not license. Finance still books the number. If you want a full royalty engine, you want a vendor that already does that, not a San Diego studio inventing a ledger in a month. We will say so and leave.

Embed means we watch a mix day, a release week, or a catalogue update, whichever is the fire. We read the Slack channel where notes land. We open the Sheet. We listen to how people talk about a bounce they hate. Nidrosoft does this from San Diego on your Drive and your mail. We do not need a tour of every imprint. We need the folder that slips every Friday.

Diagnose means we cost the recurring work. Hours on cleanup. Hours on mix revisions that were preventable. Hours hunting stems for a sync. Hours rewriting the same pitch. Hours on video that could have been a message. We score feasibility against your storage and your DAW. A team on S3 and a label admin gets a different first build than an artist with one Dropbox and a manager on iPhone.

Scope means you buy a result. New files in a folder get a cleaned copy. A bounce gets a MixGuidera checklist in the thread. A release message gets an Octana draft. A split email gets a structured row. We write what the system may create and what it may not send. Posts, registrations, and money sentences stay queued. If an artist wants an agent that posts every render, we stop.

Build and Own happen in your Dropbox or Drive and your distributor login. Someone on the team, usually a coordinator or an assistant engineer, learns the watch folder, the checklist, and the review queue. Training uses last week's release folder, not a stock song from a demo reel. When we step back, that person should run the path without calling San Diego. Cyriac Zeh will stay for the work you name. The masters never leave your drive as the only copy we hold.

An AI audit for a music company is two weeks in the work. We open the catalogue sheet, the stem folders, the mix notes channel, and the inbox that holds sync and registration. We talk to the engineer, the catalogue manager, and the person who posts. Nidrosoft will decline an audit that is only a listening session about the future of music. Taste is your job. Filing and delivery are ours to map.

Each opportunity sits next to a tool you already pay for. Dropbox or Drive. Pro Tools, Ableton, or Logic. DistroKid, TuneCore, or the label admin. Gmail. Octana. Clear Audio AI. MixGuidera. That list keeps the roadmap from becoming a studio redesign. If the first win is cleanup on a live interview folder, we say so. If the first win is a video path you can already buy as Octana, we say buy the product and skip a custom render farm we would have to host.

Risks go on the map next to the folder they would hit. Overwriting a WAV master. Posting a face you cannot use. Registering a song under the wrong publisher entity at a PRO. Generating a split sheet that does not add to 100. We mark those as human gates before anyone asks for a batch run. Labels that want speed without gates should buy consumer tools and accept takedowns. Labels that want Nidrosoft want the gates written in the scope a lawyer can skim.

Email cyriac@nidrosoft.com with the org type and the fire. Artist team, label, publisher, mix studio, or content network. Name the DAW or distributor if you know it. Attach a redacted folder tree if you can share one. Book the public calendar if a decision maker can grant Drive or Dropbox access the same week. Two weeks later you have a ranked list of hours. You do not have a new imprint or a new catalogue brand.

A first build we take is a watch folder for cleanup. New interviews or live clips dropped into a named path get a cleaned sibling file with a suffix the editor already understands. The original WAV stays untouched. Someone reviews a sample reel before the batch runs on a whole tour folder. Clear Audio AI can be the engine, or we can wire a pipeline you already like. The habit is the sibling file, the original, and the log of which model version ran.

A second build we take is mix notes in the thread you already use. A bounce lands. MixGuidera or a house checklist replies with the five things to hear. The engineer still opens the session. We will not auto-apply EQ on a master bus you cannot undo. If your house wants a recall sheet next to the notes, we add that. Recall without a person who was at the session is how you chase a ghost setting.

A third build we take is release video and catalogue drafts. Octana for the clip from a Slack or iMessage. A row draft for the catalogue Sheet with title, ISRC, and writers left blank when missing. A registration checklist. A sync folder assembled from known stem paths. Each of those ends in a queue. The manager posts. Business affairs sends the quote. Catalogue submits at the PRO or distributor. Nidrosoft measures success as hours back and errors caught. We do not sell playlist adds or streams.

Transformation is the audit plus two or three builds plus training for the coordinator who will run the watch folder after we leave. We need a named owner and access to storage before we estimate weeks. Rent-an-engineer exists if you want a monthly embedded person instead of a fixed scope. Both paths end with your team on the send to Instagram, the distributor, or the supervisor. We will not keep the only login to DistroKid, TuneCore, or your label admin.

Once a label or a studio pays more than one model vendor, the invoice needs a name. TokenTra is the public product for that. Connect providers, see spend by project, set alerts. Public results on this site say teams cut 10 to 30 percent of wasted AI spend after they can see it. A music company that only uses one consumer seat can skip this. A company that renders video all month cannot.

Domains, storefronts, and forgotten microsites sit with Nerlude. A campaign site from last year's album still bills a host. The DNS for the merch shop sits on an ex-intern Gmail. The storefront SSL renews on a card nobody watches. We point at Nerlude for 30, 14, and 7 day alerts and encrypted credentials. We do not point at it as a catalogue or a royalty ledger. Different job. Same class of forgotten login that takes down a pre-order page.

Omnira UI is there if you need an operator console for reviews. A queue of mixes waiting on notes. A queue of Octana clips waiting on a caption. A queue of split rows waiting on a signature. Software teams already use that thinking on tickets. A label can use it on assets. We will not drop Omnira Dental onto a catalogue Sheet. That product is a clinic system. The review-queue habit is what transfers, including the visible who-must-click field.

Training is a half-day on your folder and your last release. Engineers and coordinators bring live bounces, the catalogue Sheet, and the Slack channel where notes land. We refuse a tools tour with stock songs and a public playlist. If the room cannot open Dropbox or Drive, buy a course and skip the studio invoice. Come back when someone who owns the catalogue login is in the chair and can share a folder.

Hire a strategy shop if you want a keynote on the future of listening and no one will open the catalogue Sheet or the stem folder. Nidrosoft is a poor fit. Cyriac Zeh will say that on the first call. We are also a poor fit if you only want ChatGPT seats for writing artist bios and press one-sheets. Buy the seats from the vendor. Come back when a watch folder, a mix queue, or a registration checklist is the work you want ranked.

Do not book us without a decision maker. An intern with curiosity and no Drive admin will get a decline. A plugin vendor who wants a logo without folder access will get the same. We work with teams that can name an owner, grant Dropbox or Drive access, and pick a repeating job such as cleanup or registration drafts. Solo artists fit when one path pays for itself, usually Clear Audio AI or Octana. Larger labels start on one imprint, not every series at once.

We will not take a scope that posts to the artist account, registers at a PRO, or signs splits without a person. We will not overwrite masters in the session folder. We will not claim a model cleared a sample or a face. If you need a generative artist that ships songs under your name with no editor, another vendor will sell that story on a stage. You will own the takedown and the split fight. Nidrosoft will not bid that.

If the real need is a health, dating, or travel app, look at Helia, Rizzer, and Guidera in the public archive and go to those industry pages. Those products are live and named. We will not stretch a music page over them to look broader. Adjacent studio work is fine to mention in a first call. Pretending a dating coach is a catalogue tool is how a buyer wastes a week. Say the object you want filed.

Write cyriac@nidrosoft.com with the org, the DAW or distributor you use, and the fire. Cleanup, mix notes, Octana video, or catalogue filing. Cyriac Zeh reads that inbox. Attach a redacted folder tree or a screenshot of the Sheet if you can. Book the public calendar if a manager or label owner can join the same week. A pitch for Nidrosoft to become a label or a distributor will get a no in one reply.

The first live process should land in a folder or a Slack thread you already open on release week. A cleaned sibling file next to the original. A MixGuidera checklist on a bounce. An Octana draft from a message with a length and a visual. Nidrosoft has 125 products shipped and 16 public systems. Clear Audio AI, MixGuidera, and Octana are the music-facing three. The rest of the archive is context so you can see we ship, not a bundle you must buy.

You own the files on day one. Hosting stays on the Dropbox, Drive, or S3 you already use, or on Azure, AWS, or Google Cloud if we add a small piece. EU residency is available when a contract or a collector needs it. After we leave, a coordinator should run the watch folder and the queue without a San Diego call. If they cannot add a suffix rule or a checklist item, we did not finish the Own step.

Software and healthcare pages cover TokenTra, Nerlude, Omnira Dental, and the rest of the public stack those teams already click. Read how we work for Embed, Diagnose, Scope, Build, Own. Read about for Cyriac Zeh and the San Diego studio. Use contact for the public calendar or write cyriac@nidrosoft.com with the folder and the fire. The work starts when someone who can approve storage access and name who hits send is on the thread.