<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Derek Fowler</title>
    <description>The latest articles on DEV Community by Derek Fowler (@derek_fowler_tech).</description>
    <link>https://dev.to/derek_fowler_tech</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3497243%2F71849abe-92d8-4b8f-a4be-fe5191f77bac.png</url>
      <title>DEV Community: Derek Fowler</title>
      <link>https://dev.to/derek_fowler_tech</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/derek_fowler_tech"/>
    <language>en</language>
    <item>
      <title>Tips for When a STEP or IGES File Arrives and the Next Step Wants GLB</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Tue, 17 Nov 2026 08:18:38 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/tips-for-when-a-step-or-iges-file-arrives-and-the-next-step-wants-glb-5gle</link>
      <guid>https://dev.to/derek_fowler_tech/tips-for-when-a-step-or-iges-file-arrives-and-the-next-step-wants-glb-5gle</guid>
      <description>&lt;p&gt;A CAD interchange file can land in a project folder long before anyone has decided how the mesh will be shown on the web. The next tool in the chain often wants a GLB. Those two facts are easy to collapse into one “convert it somehow” step. These tips keep the formats, and the pages that handle them, in the right order. They are not a walkthrough of a single button click, and they are not a review score.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgozr14cmltz66rkl0njd.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgozr14cmltz66rkl0njd.png" alt="Official homepage gallery still of a sci-fi armored trooper in a visored helmet, silver-and-orange chest armor, and a dark blue suit, standing in a T-pose" width="308" height="348"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Read the file as interchange, not as a delivery mesh
&lt;/h2&gt;

&lt;p&gt;If the file is a STEP file, official format documentation treats it as an exchange structure. The Library of Congress page &lt;a href="https://www.loc.gov/preservation/digital/formats/fdd/fdd000448.shtml" rel="noopener noreferrer"&gt;STEP-file, ISO 10303-21&lt;/a&gt; describes ISO 10303-21 as an exchange format, often known as a STEP-file, that allows product data conforming to a schema in the EXPRESS data modeling language (ISO 10303-11) to be transferred among computer systems. The content of a STEP-file is called an “exchange structure.” The first characters in the first record are &lt;code&gt;ISO-10303-21;&lt;/code&gt;. The primary use, the same page says, is as exchange structures for content complying with other parts of the STEP standard, ISO 10303, particularly application protocols in parts 2xx, each of which defines a data exchange standard for a defined family of products at a defined stage in its life cycle. Recommended extensions quoted there include &lt;code&gt;.stp&lt;/code&gt; and &lt;code&gt;.step&lt;/code&gt; for files according to the ISO 10303 Application Protocols, and &lt;code&gt;.p21&lt;/code&gt; for general use.&lt;/p&gt;

&lt;p&gt;If the file is IGES, the older official description is similarly about communication between systems, not about packaging a mesh for a browser. The National Bureau of Standards report &lt;a href="https://www.nist.gov/publications/initial-graphics-exchange-specification-iges-version-30" rel="noopener noreferrer"&gt;Initial Graphics Exchange Specification (IGES), version 3.0&lt;/a&gt; (NBS IR 86-3359, 1986) says the document establishes information structures for the digital representation and communication of product definition data, so that product definition data used by various CAD/CAM systems can be exchanged in a compatible way. It defines a file structure format, a language format, and the representation of geometric, topological, and non-geometric product definition data. The product definition is treated as a file of entities in an application-independent format, mapped to and from a specific system’s native representation.&lt;/p&gt;

&lt;p&gt;The practical tip is small: look at the file as product data that was meant to move between CAD/CAM tools. Do not assume it is already the compact, display-oriented package that a web viewer wants.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Do not look for that handoff on the generator homepage
&lt;/h2&gt;

&lt;p&gt;The marketing homepage of &lt;a href="https://www.3dmaker.ai/" rel="noopener noreferrer"&gt;3DMaker&lt;/a&gt; is doing a different job. The heading is &lt;strong&gt;3DMaker: The AI 3D Model Maker for Any Idea&lt;/strong&gt;. The page introduces an AI 3D model generator that turns a prompt or a photo into a textured, game-ready mesh. You can start from words or from a photo; mesh density is described from &lt;strong&gt;Fast&lt;/strong&gt; to &lt;strong&gt;Ultra&lt;/strong&gt;; the image path can take a single photo or up to four angles. That is generation, not CAD import.&lt;/p&gt;

&lt;p&gt;The homepage is still useful in this pipeline, but only for its actual export contract. The visible handoff is &lt;strong&gt;GLB plus a rendered preview image&lt;/strong&gt;, with PBR textures included, ready for Blender, Unity, Unreal Engine, Three.js, Babylon.js, or model-viewer. The generator does not export OBJ or STL itself. Format conversion is a separate in-browser tool. If a STEP or IGES file is what you already have, staying on the homepage and looking for an upload slot in the prompt box will not solve the format problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Prefer a local conversion when the file should not leave the device
&lt;/h2&gt;

&lt;p&gt;When the next tool wants GLB and the source is already a STEP or IGES file, the relevant public page is a converter, not the generator. The &lt;a href="https://www.3dmaker.ai/tools/step-to-glb" rel="noopener noreferrer"&gt;STEP to GLB&lt;/a&gt; page states that contract in a few lines. The title is &lt;strong&gt;STEP / IGES to GLB Converter&lt;/strong&gt;. The heading is &lt;strong&gt;STEP / IGES → GLB&lt;/strong&gt;. The meta description says you convert STEP / IGES files to GLB in your browser, and that the file never leaves your device. The visible UI is &lt;strong&gt;Choose a STEP / IGES file to convert&lt;/strong&gt;, &lt;strong&gt;Processed locally in your browser&lt;/strong&gt;, and &lt;strong&gt;Convert&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The tip here is about the processing model, not about hidden features. The page says the conversion runs in the browser and the file stays on the device. If that is a requirement — a CAD file that should not be uploaded to a conversion service — the public copy is aligned with it. If you need a detailed report of which STEP application protocols or IGES entities survive the conversion, this page does not provide that report, and these tips will not invent one.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Believe only the converter’s own contract
&lt;/h2&gt;

&lt;p&gt;It is tempting to borrow claims from elsewhere on the site and attach them to this tool. That is a good way to misread it. The converter accepts STEP and IGES, and it outputs GLB. That is what the title, heading, and chooser all say. The page does not publish a file-size limit in the UI copy cited here, so do not assume one from another screen. Site-wide social-preview tags that mention other format names are homepage or generator marketing. They are not a fact about this converter, and they are not a fact about what the generator visibly exports.&lt;/p&gt;

&lt;p&gt;Keep the LoC and NBS descriptions in the same discipline. They explain why STEP-files and IGES files exist. They are not product scores, and they are not a claim that this converter implements ISO 10303 or the IGES specification.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Keep generation and conversion as two steps, even when both end in GLB
&lt;/h2&gt;

&lt;p&gt;A generated mesh from the homepage and a converted mesh from a STEP or IGES file may both be GLB files by the time you drop them into a viewer. That is not a reason to treat the two pages as one feature. One starts from a prompt or a photo and writes GLB plus a preview image. The other starts from a CAD interchange file you already have and writes a GLB locally in the browser.&lt;/p&gt;

&lt;p&gt;If you keep that split, the rest of the work gets easier. You can choose a viewer or a DCC tool that already accepts GLB, without asking the generator to become a CAD translator, and without asking the converter to become a model generator. The file that arrived from a CAD system can stay what the official literature says it is — an exchange structure or a product-definition communication file — until you deliberately turn it into a delivery mesh.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>FBX In, GLB as the Interchange, STL When a Later Step Needs It</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Mon, 16 Nov 2026 07:05:03 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/fbx-in-glb-as-the-interchange-stl-when-a-later-step-needs-it-24k2</link>
      <guid>https://dev.to/derek_fowler_tech/fbx-in-glb-as-the-interchange-stl-when-a-later-step-needs-it-24k2</guid>
      <description>&lt;p&gt;A mesh pipeline often changes format more than once, and those changes are not the same operation as generating the mesh. This note walks a simple handoff: an FBX file coming out of a content-creation tool, a GLB file used as the interchange, and an STL file requested by a later step. The public pages on &lt;a href="https://www.3dmaker.ai/" rel="noopener noreferrer"&gt;3DMaker&lt;/a&gt; happen to split those roles across a generator homepage and two in-browser converters. I am reading the format story first, and the product pages only as places where those steps appear.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3asiuast1hc83rqa58fm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3asiuast1hc83rqa58fm.png" alt="Official homepage gallery still of a wood-and-metal portable radio with a leather-textured front, a silver handle, and a circular tuner" width="512" height="512"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  FBX is a scene file you typically bring in, not a generator export
&lt;/h2&gt;

&lt;p&gt;Autodesk’s developer help article &lt;a href="https://help.autodesk.com/cloudhelp/2020/ENU/FBX-Developer-Help/files/welcome_to_the_fbx_sdk/FBX_Developer_Help_welcome_to_the_fbx_sdk_what_is_autodesk_fbx_technology_html.html" rel="noopener noreferrer"&gt;What is Autodesk FBX Technology&lt;/a&gt; is a useful starting point for the inbound format. It describes Autodesk FBX as a family of tools that let 3D content developers import and export 3D data, contributing to the flexibility of organizations that mix and match 2D and 3D digital content creation applications. FBX files use the &lt;code&gt;.fbx&lt;/code&gt; extension whether they are saved in a binary, or native, format or in ASCII. They store data about cameras, lights, meshes, NURBS, and the other elements of a 3D scene. Applications such as Autodesk 3ds Max, Autodesk Maya, and Autodesk MotionBuilder can import all or part of that scene data from an FBX file, and can export their own scene data to one. The same page is explicit that the FBX file format itself is not documented, and that applications should use the FBX SDK to import and export scene data. I am citing that as industry context for what an FBX file is. I am not saying this product’s converter implements the SDK or unpacks every scene element the Autodesk page lists.&lt;/p&gt;

&lt;p&gt;When that inbound file needs to become a GLB, the site does not fold the work into the generator. The &lt;a href="https://www.3dmaker.ai/tools/fbx-to-glb" rel="noopener noreferrer"&gt;FBX to GLB&lt;/a&gt; page is a dedicated converter. Its title is &lt;strong&gt;FBX to GLB Converter&lt;/strong&gt;, the heading is &lt;strong&gt;FBX → GLB&lt;/strong&gt;, and the meta description says you convert FBX files to GLB in your browser, with the file never leaving your device. The visible UI is a chooser — &lt;strong&gt;Choose a FBX file to convert&lt;/strong&gt; — a &lt;strong&gt;Processed locally in your browser&lt;/strong&gt; line, and a &lt;strong&gt;Convert&lt;/strong&gt; button. A panel on the right repeats the local-processing claim. The shared component also exposes Converting…, Download GLB, Convert another file, and the error and validation strings: Conversion failed. Please check the file and try again.; This tool only accepts FBX files.; Choose a FBX file to convert first. There is an &lt;strong&gt;All tools&lt;/strong&gt; control on the page; it is a UI label, not a second landing I am linking here.&lt;/p&gt;

&lt;h2&gt;
  
  
  GLB is the interchange the generator actually hands off
&lt;/h2&gt;

&lt;p&gt;The marketing homepage is where the generator’s own delivery contract is written down. 3DMaker is described as an AI 3D model generator that turns a prompt or a photo into a textured, game-ready mesh. The heading is &lt;strong&gt;3DMaker: The AI 3D Model Maker for Any Idea&lt;/strong&gt;. You can start from words or from a photo; mesh density is offered from &lt;strong&gt;Fast&lt;/strong&gt; to &lt;strong&gt;Ultra&lt;/strong&gt;. The image path, on this homepage, can take a single photo or up to four angles. None of that is an FBX importer, and none of it is an STL exporter.&lt;/p&gt;

&lt;p&gt;What the page does state, in a feature block and in the FAQ, is the generator export: &lt;strong&gt;GLB plus a rendered preview image&lt;/strong&gt;, with PBR textures included, ready to drop into Blender, Unity, Unreal Engine, Three.js, Babylon.js, or model-viewer. The FAQ wording is the one I am treating as the contract: the 3D model maker exports GLB and a rendered preview image out of the box. Social-preview lines that mention other format names are not that contract. The generator does not export OBJ or STL itself.&lt;/p&gt;

&lt;p&gt;That choice of GLB lines up with how the format is documented as a delivery package. The Library of Congress page on &lt;a href="https://www.loc.gov/preservation/digital/formats/fdd/fdd000500.shtml" rel="noopener noreferrer"&gt;glTF (GL Transmission Format) 2.0&lt;/a&gt; describes glTF 2.0 as the most widely used chronological version of the glTF family, published by the Khronos Group in June 2017. glTF is intended as a vendor-neutral distribution format for 3D content, bridging the gap between 3D content creation tools and applications that display 3D graphics. Its originators described it as the “JPEG of 3D” or as a format for “the last mile.” glTF 2.0 added physically based rendering (PBR) for a portable, consistent description of materials. The core PBR model is the metallic-roughness material model, using parameters such as baseColorFactor, metallicFactor, and roughnessFactor. Binary glTF uses the &lt;code&gt;.glb&lt;/code&gt; filename extension and the media type &lt;code&gt;model/gltf-binary&lt;/code&gt;; the LoC page also calls glTF 2.0 a final-state format used for delivery to a web browser or other viewing software or device. That is why GLB is a reasonable interchange in this pipeline. It is not evidence that this generator implements the glTF 2.0 specification, and it is not a product score.&lt;/p&gt;

&lt;h2&gt;
  
  
  STL is a later conversion, not a second generator download
&lt;/h2&gt;

&lt;p&gt;If a later tool or workflow asks for STL, the handoff does not happen on the generator homepage. The &lt;a href="https://www.3dmaker.ai/tools/glb-to-stl" rel="noopener noreferrer"&gt;GLB to STL&lt;/a&gt; page is a second in-browser converter, built on the same local-processing UI. Its title is &lt;strong&gt;GLB to STL Converter&lt;/strong&gt;, the heading is &lt;strong&gt;GLB → STL&lt;/strong&gt;, and the meta description says you convert GLB files to STL in your browser, without the file leaving the device. The chooser asks you to &lt;strong&gt;Choose a GLB file to convert&lt;/strong&gt;. After a successful run, the shared component’s download label is Download STL. The failure and validation copy names GLB as the accepted source. This is a format step after interchange, not a hidden generator export.&lt;/p&gt;

&lt;p&gt;The important design point is the order. FBX can come in from a digital content creation tool. GLB is the file the generator actually writes, and the file a local FBX converter can also produce. STL appears only when you take that GLB to a separate converter. If you collapse those three roles into one “export” button, you will misread both the homepage and the two tool pages. Keep the inbound format, the interchange format, and the later-step format in separate steps, and the public UI matches the pipeline.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Three Surfaces, Three Jobs: Marketing Home, a Single-Use Board, and a Category Index</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Sat, 14 Nov 2026 07:39:33 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/three-surfaces-three-jobs-marketing-home-a-single-use-board-and-a-category-index-53kg</link>
      <guid>https://dev.to/derek_fowler_tech/three-surfaces-three-jobs-marketing-home-a-single-use-board-and-a-category-index-53kg</guid>
      <description>&lt;p&gt;A ranking tool often collapses, in conversation, into “the tier list site.” Looking at the public pages, that collapse hides three different objects. This note treats only what those pages themselves show: a marketing homepage, a blank board you fill with your own images, and a topic index for ready-made templates. It is not a source tour of the application’s internals, and it does not borrow marketing totals from the homepage as if they were measurements.&lt;/p&gt;

&lt;h2&gt;
  
  
  Object A: the homepage is a product introduction
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.tierlist.ai/" rel="noopener noreferrer"&gt;Tierlist&lt;/a&gt; titles the root page “Tier List Maker - Create &amp;amp; Share Tier Lists.” The lead is explicit: “Drag and rank anything. Pick a ready-made template or start from a blank board.” A “Start a blank tier list” control sits next to a “Browse by category” block whose top-level labels are Gaming, Anime &amp;amp; Manga, Music, TV &amp;amp; Movies, Sports, Food &amp;amp; Drink, Tabletop &amp;amp; TCG, Internet &amp;amp; Memes, Tech &amp;amp; Hardware, and Education &amp;amp; Career. A “Browse templates” section then shows featured ready-made boards.&lt;/p&gt;

&lt;p&gt;Lower on the same page, a three-step walkthrough describes the general product contract as the homepage wants it understood: choose a template or start from scratch and upload your own images; drag items from a pool into rows, with the option to rename rows and change their colors; then export a high-quality PNG with no watermark, or copy a shareable link. A separate feature list repeats drag-and-drop on desktop and mobile, custom row colors and labels, community templates that can be browsed, favorited, and remixed, and the same export and link options. The page also says you can start without creating an account.&lt;/p&gt;

&lt;p&gt;That is orientation. It tells you the product has two starting shapes. It is not itself either working surface.&lt;/p&gt;

&lt;h2&gt;
  
  
  Object B: the single-use page is a disposable ranking canvas
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://www.tierlist.ai/single-use-tier-list" rel="noopener noreferrer"&gt;single-use tier list&lt;/a&gt; document title is “Single Use Tier List Maker.” The meta description does not talk about templates. It says: build a tier list, drag images into ranked tiers, and download the result as an image. The canvas is labeled “My Tier List,” with a “Rows &amp;amp; labels” control. Default rows are S, A, B, C, and D. The instructions on the board are operational, not promotional: drag items to rank them, use the arrows to reorder rows, right-click an item to remove it. Image presentation is adjustable — Pin, Images, Square, Landscape, Portrait, Circle, No crop — and the intake control is “Upload images.”&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fme3jk24qyrwcovqro4ea.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fme3jk24qyrwcovqro4ea.png" alt="The single-use editor, with empty S through D rows and an upload control" width="800" height="447"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This object has no preloaded roster in the document that the page itself renders as its starting state. It also does not present a topic tree. I am not folding the homepage’s share-link sentence into this URL; the page’s own description ends at downloading an image.&lt;/p&gt;

&lt;h2&gt;
  
  
  Object C: the category page is a template index
&lt;/h2&gt;

&lt;p&gt;The third object is a finding aid. &lt;a href="https://www.tierlist.ai/category" rel="noopener noreferrer"&gt;Tier list categories&lt;/a&gt; is titled “Tier List Categories.” The heading is “Categories,” and the lead is “Browse tier list templates by topic.” Gaming is expanded into Gacha &amp;amp; RPG, MOBA, Roblox, Strategy &amp;amp; Card, Anime Games, Pokémon, Other Games, Fighting, MMORPG, FPS &amp;amp; Shooter, and Sports Games. Other top-level groups — Anime &amp;amp; Manga, Music, TV &amp;amp; Movies, Sports, Food &amp;amp; Drink, Tabletop &amp;amp; TCG, Internet &amp;amp; Memes, Tech &amp;amp; Hardware, Education &amp;amp; Career — each show sub-groups and a “View all” link. The page description lists gaming, anime, music, movies, sports, food, tabletop, and internet culture. There is no ranking grid on this page. The job is to get you to a prepared template, not to accept an upload.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two research references, kept in their lane
&lt;/h2&gt;

&lt;p&gt;Why split “find a prepared set” from “rank the pictures I already have”? Information-architecture research treats grouping for findability as its own problem. In &lt;a href="https://www.nngroup.com/articles/card-sorting-definition/" rel="noopener noreferrer"&gt;“Card Sorting: Uncover Users’ Mental Models for Better Information Architecture”&lt;/a&gt; (Nielsen Norman Group, February 2, 2024), Samhita Tankala and Katie Sherwin define card sorting as “a research method in which study participants place individually labeled cards into groups according to criteria that make the most sense to them.” They argue that the method helps a team build an information architecture that matches users’ mental models, which improves findability and discoverability. That is a method for designing grouping, not a claim that this product ran a card sort, and not a method for ranking items from S to D.&lt;/p&gt;

&lt;p&gt;Page Laubheimer’s &lt;a href="https://www.nngroup.com/articles/taxonomy-101/" rel="noopener noreferrer"&gt;“Taxonomy 101”&lt;/a&gt; (Nielsen Norman Group, July 3, 2022) defines a taxonomy as “a closed list of acceptable terms that are arranged hierarchically and are used to describe and classify content.” He distinguishes that backstage vocabulary from visible navigation, where “we are concerned with grouping things in a way that adheres to users’ mental models.” I am not asserting that the site’s category tree is a formal metadata taxonomy. I am using the distinction to keep Object C honest: it is a visible grouping of templates, and that is a different contract from Object B’s blank board.&lt;/p&gt;

&lt;h2&gt;
  
  
  A small interface rule
&lt;/h2&gt;

&lt;p&gt;If a page introduces both paths, keep it as an introduction. If a page accepts uploads onto an empty S–D grid and offers a download, treat it as a single-use canvas. If a page only browses templates by topic, treat it as an index. Sharing a brand name does not make the three objects the same type, and collapsing them in the URL structure would hide the contract the user actually needs.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ux</category>
      <category>design</category>
    </item>
    <item>
      <title>From Prompt or Photo Through Mesh Density to a PBR GLB</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Fri, 13 Nov 2026 02:10:29 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/from-prompt-or-photo-through-mesh-density-to-a-pbr-glb-mim</link>
      <guid>https://dev.to/derek_fowler_tech/from-prompt-or-photo-through-mesh-density-to-a-pbr-glb-mim</guid>
      <description>&lt;p&gt;A usable 3D generation session is a short pipeline, not a single button. You choose an input, you choose how dense the mesh should be, and you leave with a textured asset in a format an engine can load. This note walks that path as it appears on the live pages of &lt;a href="https://www.3dmaker.ai/" rel="noopener noreferrer"&gt;3DMaker&lt;/a&gt;, without treating marketing numbers as measurements.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6woacwpt1ncpv4lgi3ta.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6woacwpt1ncpv4lgi3ta.png" alt="Official still of a glazed vase and a woven basket, showing built-in PBR materials on a finished mesh" width="800" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Input stage: a prompt or a photo, not both contracts on one screen
&lt;/h2&gt;

&lt;p&gt;The marketing homepage is only the briefing. Its heading calls the product an AI 3D model maker for any idea, and a section titled &lt;strong&gt;One AI 3D Model Generator, Two Ways to Start&lt;/strong&gt; says a written description and a single photo are both supposed to produce the same textured, game-ready mesh. The homepage gallery even invites you to &lt;strong&gt;drag to rotate&lt;/strong&gt; sample meshes. The actual input contracts, though, live on two tool pages.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://www.3dmaker.ai/text-to-3d" rel="noopener noreferrer"&gt;Text to 3D&lt;/a&gt; page is the prompt stage. You get up to 1,024 characters for materials, proportions, and style. No sketch or reference photo is required. A &lt;strong&gt;Surprise me&lt;/strong&gt; control can supply a starting prompt when you do not yet have one. The page’s guidance is to be specific: a weathered or dented object description gives the generator more to use than a bare noun.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://www.3dmaker.ai/image-to-3d" rel="noopener noreferrer"&gt;Image to 3D&lt;/a&gt; page is the photo stage. It leads with a single reference image and accepts &lt;strong&gt;PNG, JPG, or WEBP&lt;/strong&gt;. The page says PBR materials are pulled from that source photo, and that a plain, well-lit background helps the subject separate from its surroundings. The homepage mentions that an image path can use up to four angles; this dedicated landing still frames the job as one photo, so I am not treating multi-angle capture as the default step in this pipeline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Density stage: Fast, Standard, Pro, or Ultra
&lt;/h2&gt;

&lt;p&gt;Both tool pages expose the same four mesh density names: &lt;strong&gt;Fast, Standard, Pro, and Ultra&lt;/strong&gt;. They are UI options for how much detail the mesh should carry, not a timing table. The text page says you can switch density without changing the prompt. The image page says you can switch density without re-uploading the photo. In a pipeline, that matters more than the labels themselves: input and density are independent knobs. I am not citing the product’s own totals block, or any stated generation time, as independent data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Output stage: PBR on the mesh, GLB plus a preview
&lt;/h2&gt;

&lt;p&gt;The visible export contract is consistent across the homepage FAQ and both tool pages: the generator textures the mesh automatically and exports &lt;strong&gt;GLB and a rendered preview image&lt;/strong&gt;. PBR textures are included; the pages do not describe a separate texturing pass. The destination list is Blender, Unity, Unreal Engine, Three.js, Babylon.js, or model-viewer. I am not treating other format names that appear only in social-preview text as an on-page export promise.&lt;/p&gt;

&lt;p&gt;That output choice matches how the industry talks about runtime delivery. The Khronos Group describes &lt;a href="https://www.khronos.org/gltf/" rel="noopener noreferrer"&gt;glTF&lt;/a&gt; as a royalty-free specification for the efficient transmission and loading of 3D scenes and models by engines and applications. It minimizes asset size and the runtime work needed to unpack the file. The core description is JSON; a scene can also be stored as a single binary &lt;code&gt;.glb&lt;/code&gt;. glTF 2.0 is published as ISO/IEC 12113:2022, and Khronos PBR is the material model used inside glTF to approximate real-world lighting and surface response. If you are handing a generated mesh to an engine, GLB with PBR is a standard hand-off, not a product-specific slogan.&lt;/p&gt;

&lt;p&gt;The first stage — especially the prompt stage — also has a research backdrop that is easy to over-read. In &lt;a href="https://dreamfusion3d.github.io/" rel="noopener noreferrer"&gt;DreamFusion: Text-to-3D using 2D Diffusion&lt;/a&gt;, Ben Poole, Ajay Jain, Jonathan T. Barron, and Ben Mildenhall used a pretrained 2D text-to-image diffusion model as a prior for text-to-3D synthesis, without 3D training data and without changing the image model. They optimize a 3D representation so that 2D renderings from random angles score well under that prior; the result can be viewed from any angle, relit, or composited into a 3D environment, and the project page notes that the representation can be exported to a mesh for ordinary 3D software. I am citing that as the research problem behind “text in, a viewable 3D asset out.” I am not saying this product implements DreamFusion, a NeRF, or their distillation loss.&lt;/p&gt;

&lt;h2&gt;
  
  
  A compact pipeline checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Briefing, or a reminder that both inputs exist → the marketing homepage, including the drag-to-rotate gallery.&lt;/li&gt;
&lt;li&gt;Input is a description → the text-to-3D page, up to 1,024 characters, optional Surprise me.&lt;/li&gt;
&lt;li&gt;Input is a photo → the image-to-3D page, PNG/JPG/WEBP, prefer a plain background.&lt;/li&gt;
&lt;li&gt;Detail level → Fast, Standard, Pro, or Ultra, switched independently of the input.&lt;/li&gt;
&lt;li&gt;Hand-off → GLB plus a preview image, PBR included, into the engine or DCC tool you already use.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep the brochure at the root. Run the session as input, then density, then a GLB. The mesh is a starting point for a modeler’s judgment, not a replacement for it.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>gamedev</category>
    </item>
    <item>
      <title>After You Generate: Why the Marketing Root Is Not Your Asset Library</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Thu, 12 Nov 2026 06:38:57 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/after-you-generate-why-the-marketing-root-is-not-your-asset-library-1ph4</link>
      <guid>https://dev.to/derek_fowler_tech/after-you-generate-why-the-marketing-root-is-not-your-asset-library-1ph4</guid>
      <description>&lt;p&gt;Most AI music sites teach the wrong first habit: they train you to return to the marketing root when you want last week’s track. The root is a sales document. The place that is built to hold generated songs, covers, and videos is a different route. This is a short information-architecture note on that split, based on a live fetch of &lt;a href="https://www.wav.ai/" rel="noopener noreferrer"&gt;WAV AI&lt;/a&gt; and its media library page.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzrpdysxu26pz9hecop1r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzrpdysxu26pz9hecop1r.png" alt="Official AI Stem Splitter hero still, showing separated audio parts" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Route &lt;code&gt;/&lt;/code&gt; is a brochure with a clear contract
&lt;/h2&gt;

&lt;p&gt;The document title on the root is &lt;strong&gt;Free AI Music Generator &amp;amp; Music Tools&lt;/strong&gt;. The visible &lt;code&gt;h1&lt;/code&gt; is &lt;strong&gt;Free AI Music Generator&lt;/strong&gt;. The supporting line is the pitch: turn ideas into music instantly; create songs, beats, and tracks with Text to Music AI; no music skills needed. The primary call to action is &lt;strong&gt;Start free&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Below that, the page is still a brochure. Sample styles (Lo-Fi, EDM, Hip-Hop, Cinematic) live under &lt;strong&gt;Hear the Magic&lt;/strong&gt;. Four feature blocks under &lt;strong&gt;Everything You Need to Make Perfect Audio&lt;/strong&gt; describe a generator, an extender, a remixer, and an editor, each with a try-it prompt. Audience sections, testimonials, and a FAQ follow. If you are routing first-time visitors, this is the right surface. If you are routing someone who already generated a track and wants it back, this page has no collection to offer them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Route &lt;code&gt;/media&lt;/code&gt; is an Assets surface
&lt;/h2&gt;

&lt;p&gt;In the site navigation, &lt;strong&gt;Media&lt;/strong&gt; does not sit under Create (Music, Lyrics, Editor) or under Tools. It sits under &lt;strong&gt;Assets&lt;/strong&gt;. That grouping is the IA clue. The &lt;a href="https://www.wav.ai/media" rel="noopener noreferrer"&gt;Media Library&lt;/a&gt; page uses a different document title from the marketing root: &lt;strong&gt;Media Library | WAV AI&lt;/strong&gt;. The meta description says to manage your generated songs, covers, and videos in the WAV AI media library.&lt;/p&gt;

&lt;p&gt;The visible chrome on that page is collection chrome: &lt;strong&gt;All Creations&lt;/strong&gt;, &lt;strong&gt;Upload&lt;/strong&gt;, and &lt;strong&gt;Folders&lt;/strong&gt;. A public fetch without a signed-in library still returns HTTP 200 and renders the page. It is not a login wall. The body shows an empty state, &lt;strong&gt;No assets found matching your criteria.&lt;/strong&gt; That copy only makes sense on a filtered collection. It would be a strange sentence to put on a marketing homepage.&lt;/p&gt;

&lt;p&gt;One thing to watch if you log titles for analytics: the Open Graph title on &lt;code&gt;/media&lt;/code&gt; still reused the generic marketing title in this fetch, while the HTML &lt;code&gt;&amp;lt;title&amp;gt;&lt;/code&gt; correctly said Media Library. If events or social cards key off &lt;code&gt;og:title&lt;/code&gt;, the two surfaces can look identical in a report even though the routes and on-page contracts are different. Prefer the document title and the visible controls, not the social title, when you decide what the page is.&lt;/p&gt;

&lt;h2&gt;
  
  
  Recognition is the library’s job; recall is what the homepage leaves you with
&lt;/h2&gt;

&lt;p&gt;Raluca Budiu’s &lt;a href="https://www.nngroup.com/articles/recognition-and-recall/" rel="noopener noreferrer"&gt;Memory Recognition and Recall in User Interfaces&lt;/a&gt; (Nielsen Norman Group, 15 January 2024) is useful here as interface guidance, not as a score. The article distinguishes recall (retrieving a name or detail from scratch) from recognition (seeing a familiar item in a list). Recognition is easier because the extra cues raise the chance of retrieval. Histories, recently viewed items, and saved lists are the examples it gives of interfaces that let people resume work they have already seen.&lt;/p&gt;

&lt;p&gt;A marketing root asks you to recall that a track exists and then start over from a prompt. A media library, if it shows the work, turns the same task into recognition: you scan songs, covers, and videos until the familiar one appears. That is the routing reason to keep &lt;code&gt;/&lt;/code&gt; and &lt;code&gt;/media&lt;/code&gt; apart.&lt;/p&gt;

&lt;p&gt;The Library of Congress page &lt;a href="https://digitalpreservation.gov/personalarchiving/audio.html" rel="noopener noreferrer"&gt;Keeping Personal Digital Audio&lt;/a&gt; adds a practical, non-UX angle. Its Personal Digital Archiving tips are to identify audio files, decide which recordings have long-term value, organize them with descriptive names, tags, and folders, and keep metadata such as an export date. I am not treating the product library as a preservation archive, and I am not claiming it performs those backups. The transferable idea is smaller: generated audio is a collection, and collections need a place with folders and a way to find a file again.&lt;/p&gt;

&lt;h2&gt;
  
  
  A compact routing checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;First visit, or a visitor who still needs the pitch → &lt;code&gt;/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Someone asking “where did that track / cover / video go?” → &lt;code&gt;/media&lt;/code&gt;, under Assets, with All Creations, Upload, and Folders on the page.&lt;/li&gt;
&lt;li&gt;Do not collapse the two routes because their Open Graph titles look alike.&lt;/li&gt;
&lt;li&gt;Do not describe &lt;code&gt;/media&lt;/code&gt; as login-only; the public page loads, and an empty state is not the same thing as an auth wall.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Keep the brochure at the root. Put the library on its own path. The people who come back for work they already made should not have to recall a prompt from a sales page.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>music</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Routing First Clicks: Marketing Root Versus the /home Task Chooser</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Wed, 11 Nov 2026 02:46:46 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/routing-first-clicks-marketing-root-versus-the-home-task-chooser-559e</link>
      <guid>https://dev.to/derek_fowler_tech/routing-first-clicks-marketing-root-versus-the-home-task-chooser-559e</guid>
      <description>&lt;p&gt;A marketing document and a task chooser can share a brand and still have different preconditions. If you route a first-time visitor into a worklist before they understand the product, they have to invent a job. If you keep a returning maker on the brochure, they have to hunt for a starting task inside testimonials and FAQ. This technical note is a routing walkthrough for those two public entry contracts in a product such as &lt;a href="https://www.wav.ai/" rel="noopener noreferrer"&gt;WAV AI&lt;/a&gt;. I am describing the live pages, not an inferred backend.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp36t0rle34h22ic5n5kh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp36t0rle34h22ic5n5kh.png" alt="Recommended Text to Music card on the creation hub" width="600" height="300"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Contract A: &lt;code&gt;/&lt;/code&gt; is a marketing document
&lt;/h2&gt;

&lt;p&gt;The root page’s visible heading is &lt;strong&gt;Free AI Music Generator&lt;/strong&gt;. The supporting line is a product statement: turn ideas into music instantly; create songs, beats, and tracks with Text to Music AI; no music skills needed. The primary call to action is &lt;strong&gt;Start free&lt;/strong&gt;. Later on the same document you still get brochure-style prompts (Start creating your music, Try Free AI Music Generator Now), not a structured job menu.&lt;/p&gt;

&lt;p&gt;The rest of the page is evidence and orientation, in marketing order:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Sample audio under &lt;strong&gt;Hear the Magic&lt;/strong&gt; (Lo-Fi, EDM, Hip-Hop, Cinematic)&lt;/li&gt;
&lt;li&gt;Four feature blocks under &lt;strong&gt;Everything You Need to Make Perfect Audio&lt;/strong&gt;: AI Music Generator, AI Music Extender, AI Remixer, AI Music Editor&lt;/li&gt;
&lt;li&gt;An audience section, &lt;strong&gt;Built for Creators, Brands, and Everyone&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Testimonials under &lt;strong&gt;Loved by Creators Worldwide&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Frequently Asked Questions&lt;/strong&gt;, including free start, style control, uploading audio, commercial use, rights, distribution, and export formats&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That is a valid first surface when the visitor still needs to learn what the product is. It is a weak first surface when the visitor already has a job in mind and only needs to choose a tool family.&lt;/p&gt;

&lt;p&gt;Huei-Hsin Wang’s &lt;a href="https://www.nngroup.com/articles/homepage-design-principles/" rel="noopener noreferrer"&gt;Homepage Design: 5 Fundamental Principles&lt;/a&gt; (Nielsen Norman Group, 15 March 2024) calls the homepage a site’s “front door,” and says it should stand apart visually from other pages, communicate purpose, and prompt the next action. I am citing that as routing context for keeping a distinct marketing root. It is not a usability audit of this site.&lt;/p&gt;

&lt;h2&gt;
  
  
  Contract B: &lt;code&gt;/home&lt;/code&gt; is a task chooser
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://www.wav.ai/home" rel="noopener noreferrer"&gt;AI Music Generator &amp;amp; Tools&lt;/a&gt; page uses the document title Free AI Music Generator &amp;amp; Music Tools, but the heading on the page is the actual contract: &lt;strong&gt;What would you like to create today?&lt;/strong&gt; The Create grouping is already split into &lt;strong&gt;Music&lt;/strong&gt;, &lt;strong&gt;Lyrics&lt;/strong&gt;, and &lt;strong&gt;Editor&lt;/strong&gt;. That is a chooser, not another elevator pitch.&lt;/p&gt;

&lt;p&gt;A &lt;strong&gt;Recommended tools&lt;/strong&gt; row then materializes three likely first jobs, each with a one-line description:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Text to Music — Generate studio-quality tracks from text prompts&lt;/li&gt;
&lt;li&gt;Remix — Remix your audio into completely new styles&lt;/li&gt;
&lt;li&gt;Stem Splitter — Extract vocals, drums, and instruments from audio&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The same page also carries a full inventory under &lt;strong&gt;AI Creative Suite&lt;/strong&gt;. Music Tools lists Text to Music and Photo to Music. Lyrics Tools lists Lyric Studio. Editor Tools lists Music Remix, Music Mashup, Music Extend, Music Replace, Stem Splitter, and Music Mastering. The descriptions on those cards are job-shaped (for example, Photo to Music as turning images into musical compositions, Lyric Studio as generating and editing lyrics, Music Mashup as blending multiple tracks).&lt;/p&gt;

&lt;p&gt;This hub loaded without a login in a public fetch. Do not model it as a private dashboard or as a synonym for the marketing root. The two pages share a brand and, in the HTML title, even a similar document name. The visible heading and the component tree are what differ.&lt;/p&gt;

&lt;p&gt;The GOV.UK Design System’s &lt;a href="https://design-system.service.gov.uk/patterns/start-using-a-service/" rel="noopener noreferrer"&gt;Start using a service&lt;/a&gt; pattern is useful here as a routing analogy, not as a claim that this product is a government service. It says a start point should give just enough information to understand what the service does and whether it will meet the need, and should include a button that links &lt;em&gt;into&lt;/em&gt; the service (Start now, Sign in, and similar action labels). The marketing root looks like that start point. The /home page looks like the first screen after you have already decided to go in.&lt;/p&gt;

&lt;h2&gt;
  
  
  Routing table
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Incoming state&lt;/th&gt;
&lt;th&gt;Surface&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Visitor still needs the pitch, samples, feature story, or FAQ&lt;/td&gt;
&lt;td&gt;Marketing root (&lt;code&gt;/&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;The page is a document: heading, proof, and a Start free action&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Visitor already intends to make something and must pick a family&lt;/td&gt;
&lt;td&gt;Creation hub (&lt;code&gt;/home&lt;/code&gt;)&lt;/td&gt;
&lt;td&gt;The heading asks what to create; Create is already Music / Lyrics / Editor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Visitor wants a suggested first job&lt;/td&gt;
&lt;td&gt;Creation hub, Recommended tools&lt;/td&gt;
&lt;td&gt;Three named starting cards, not a feature essay&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Visitor wants the full tool inventory after choosing a family&lt;/td&gt;
&lt;td&gt;Creation hub, AI Creative Suite&lt;/td&gt;
&lt;td&gt;Grouped list with one-line job descriptions&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;You are about to treat &lt;code&gt;/&lt;/code&gt; and &lt;code&gt;/home&lt;/code&gt; as aliases&lt;/td&gt;
&lt;td&gt;Don’t&lt;/td&gt;
&lt;td&gt;Same brand, different contract; the HTML title is not the heading&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A compact build rule: keep the marketing document responsible for “what is this?” and keep the /home chooser responsible for “which job today?” Collapsing them into one page forces either a brochure to act like a router, or a router to act like an ad. The live split already exists; the only implementation detail that matters for a first click is to honor the precondition instead of the tab label.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>music</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Catalog Index vs Editor Family: Preconditions When the Input Is Already a Mix</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Tue, 10 Nov 2026 07:28:21 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/catalog-index-vs-editor-family-preconditions-when-the-input-is-already-a-mix-51ki</link>
      <guid>https://dev.to/derek_fowler_tech/catalog-index-vs-editor-family-preconditions-when-the-input-is-already-a-mix-51ki</guid>
      <description>&lt;p&gt;A generation surface and an editing surface fail in different ways. The first fails when you do not have audio yet and still try to pick a specialized transform. The second fails when you already have a mix and you still wander an undifferentiated index. This technical note is about the two entry contracts in a product such as &lt;a href="https://www.wav.ai/" rel="noopener noreferrer"&gt;WAV AI&lt;/a&gt;, and the precondition each one assumes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcskjn8bvjn8dhatwbtg9.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcskjn8bvjn8dhatwbtg9.webp" alt="Diagram of one waveform branching into six editor jobs" width="800" height="600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The catalog is an index with three groups
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.wav.ai/tools" rel="noopener noreferrer"&gt;All Music Tools&lt;/a&gt; is titled All Music Tools. Its description is a single sentence: create original music, write lyrics, and reshape existing audio from one focused set of tools. That is an index contract, not an “open this file” contract.&lt;/p&gt;

&lt;p&gt;The page materializes the contract as three groups:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Music Tools: Text to Music, Photo to Music&lt;/li&gt;
&lt;li&gt;Lyrics Tools: Lyric Studio&lt;/li&gt;
&lt;li&gt;Editor Tools: Music Remix, Music Mashup, Music Extend, Music Replace, Stem Splitter, Music Mastering&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Featured sections under those headings expand the same families. If the next action is still “which family?”, this is the right surface. If the next action is already “this file, this transform,” the index is a detour.&lt;/p&gt;

&lt;p&gt;Jakob Nielsen’s &lt;a href="https://www.nngroup.com/articles/top-10-ia-mistakes/" rel="noopener noreferrer"&gt;Top 10 Information Architecture (IA) Mistakes&lt;/a&gt; (Nielsen Norman Group, 10 May 2009) includes “Missing Category Landing Pages”: a section overview helps people understand scope; linking only to leaf pages can hide what the section contains. I am citing that as information-architecture context for keeping a tools index, not as a usability score for this site.&lt;/p&gt;

&lt;h2&gt;
  
  
  The editor family assumes you already have audio
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://www.wav.ai/editor" rel="noopener noreferrer"&gt;AI Music Editor&lt;/a&gt; page states the precondition in the FAQ: yes, you need a song before you start; these tools work with music you already have. Inputs vary by tool: one song, two songs, an eligible generated song from the Music Library, or a finished song plus a different reference song.&lt;/p&gt;

&lt;p&gt;The workspace is a family of six job-specific tools, not a single multi-purpose canvas: Music Remix, Music Mashup, Music Extend, Song Section Editor, Stem Splitter, and AI Music Mastering. The catalog card for the section-edit job is labeled Music Replace; the editor page calls it Song Section Editor. The page’s own rationale for separate tools is “make one clear change at a time.” You may chain tools on the same song (remix, then stem-split, then master with a reference), but each step is still one job.&lt;/p&gt;

&lt;p&gt;That precondition is the important interface detail. An editor tool that wants an existing mix is a different function signature from a generator that wants a prompt or an image. Mixing the two signatures is how pipelines get noisy: you open Remix because it is nearby, when the actual problem is that you still need a first draft from Text to Music or Lyric Studio.&lt;/p&gt;

&lt;p&gt;Yuancheng Wang and colleagues, in &lt;a href="https://arxiv.org/abs/2304.00830" rel="noopener noreferrer"&gt;AUDIT: Audio Editing by Following Instructions with Latent Diffusion Models&lt;/a&gt; (2023), frame instruction-guided audio editing as a task that takes existing input audio plus an instruction, rather than a full target description from scratch. I am using that only as research context for the “input already exists” contract. It is not a claim that this product uses that model, and I am not quoting the paper’s scores as product quality.&lt;/p&gt;

&lt;h2&gt;
  
  
  A compact routing table
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Precondition&lt;/th&gt;
&lt;th&gt;Surface&lt;/th&gt;
&lt;th&gt;First action&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;No audio, or only a family (generate / lyrics / later edit)&lt;/td&gt;
&lt;td&gt;Tools catalog&lt;/td&gt;
&lt;td&gt;Pick the group, then the leaf tool&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;One existing track, new arrangement&lt;/td&gt;
&lt;td&gt;Editor&lt;/td&gt;
&lt;td&gt;Music Remix&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Two existing tracks, one blend&lt;/td&gt;
&lt;td&gt;Editor&lt;/td&gt;
&lt;td&gt;Music Mashup&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Track is right but too short&lt;/td&gt;
&lt;td&gt;Editor&lt;/td&gt;
&lt;td&gt;Music Extend&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;One eligible section needs new lyrics or style&lt;/td&gt;
&lt;td&gt;Editor&lt;/td&gt;
&lt;td&gt;Song Section Editor&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Need isolated parts&lt;/td&gt;
&lt;td&gt;Editor&lt;/td&gt;
&lt;td&gt;Stem Splitter&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mix is finished; need a reference master&lt;/td&gt;
&lt;td&gt;Editor&lt;/td&gt;
&lt;td&gt;AI Music Mastering&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Stop when the note next to the file records the surface (&lt;code&gt;catalog&lt;/code&gt; or &lt;code&gt;editor&lt;/code&gt;) and the single job you ran. If you cannot fill the “input audio” column, you are still on the catalog side of the contract.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>music</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How to Separate Lyric Fields from Style, Then Decide Whether a Video Still Is a Better Control Signal</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Mon, 09 Nov 2026 07:48:59 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/how-to-separate-lyric-fields-from-style-then-decide-whether-a-video-still-is-a-better-control-1ce5</link>
      <guid>https://dev.to/derek_fowler_tech/how-to-separate-lyric-fields-from-style-then-decide-whether-a-video-still-is-a-better-control-1ce5</guid>
      <description>&lt;p&gt;Short-song pipelines often collapse “write a prompt” into one box, even when the inputs are not the same type of signal. Lyrics are a verbal deliverable. Style is a set of musical constraints. A video still is a visual constraint that may not need a paragraph at all. This how-to keeps those lanes named. A workspace like &lt;a href="https://www.wav.ai/" rel="noopener noreferrer"&gt;WAV AI&lt;/a&gt; helps when you pick the control surface before you generate.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1wj2debiw57fm9jp2mck.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1wj2debiw57fm9jp2mck.webp" alt="Photo to music starting modes" width="800" height="600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Map the deliverable to a control surface
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What you already have&lt;/th&gt;
&lt;th&gt;Control surface&lt;/th&gt;
&lt;th&gt;Do not start with&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Locked lyrics plus a style you can name&lt;/td&gt;
&lt;td&gt;Separate lyric and style fields&lt;/td&gt;
&lt;td&gt;One sentence that restates the verses and the genre together&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A scene-level description, no locked words&lt;/td&gt;
&lt;td&gt;A single whole-song prompt&lt;/td&gt;
&lt;td&gt;Empty lyric fields you feel obliged to invent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A video still, cover, illustration, or photo that already sets the mood&lt;/td&gt;
&lt;td&gt;The image first, optional written note second&lt;/td&gt;
&lt;td&gt;A long prompt that only describes the picture&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Andrea Agostinelli et al., &lt;a href="https://arxiv.org/abs/2301.11325" rel="noopener noreferrer"&gt;MusicLM: Generating Music From Text&lt;/a&gt; (Google Research, 2023), treat language as a control signal over generated music. That is industry context for why a text brief can steer generation. It does not describe this product’s internals.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pipeline A — split lyrics from style
&lt;/h2&gt;

&lt;p&gt;Open &lt;a href="https://www.wav.ai/music/text-to-music" rel="noopener noreferrer"&gt;Text to Music&lt;/a&gt; when the brief is verbal.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Custom&lt;/strong&gt; is the mode for locked lyrics: put the words in the lyrics field and the musical direction in the style field. In style, name genre, mood, instruments, pace, or the role the music will play in a video or song. You can create a song that uses those lyrics, or an instrumental if you want the style without sung words. This is also the path for making music from lyrics you already wrote.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Inspiration&lt;/strong&gt; is the mode for a single whole-song prompt. Use it for background music for a video when the brief is one descriptive sentence, or for instrumental music without lyrics when you would rather not invent a lyric field.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pipeline B — start from a still when the picture is the brief
&lt;/h2&gt;

&lt;p&gt;Open &lt;a href="https://www.wav.ai/music/photo-to-music" rel="noopener noreferrer"&gt;Photo to Music&lt;/a&gt; when a visual is already doing the briefing work:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Choose an image — a photo, an illustration, a cover image, or a video still.&lt;/li&gt;
&lt;li&gt;Add an optional written music note (genre, pace, instruments, or story) only when the image leaves something unsaid.&lt;/li&gt;
&lt;li&gt;Create a song or an instrumental.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The written note is optional. Typical jobs: original music for a video scene taken from a still; turning artwork or cover art into a song idea; music for a photo post.&lt;/p&gt;

&lt;p&gt;Jade Copet et al., &lt;a href="https://arxiv.org/abs/2306.05284" rel="noopener noreferrer"&gt;Simple and Controllable Music Generation&lt;/a&gt; (MusicGen / Meta AI, NeurIPS 2023), discuss generation conditioned on a textual description and, separately, on other controls. That paper is useful context for why splitting lyrics from style, or pairing an image with an optional note, is a control-design choice. It is not a claim that this product uses that model, and its scores are not product metrics.&lt;/p&gt;

&lt;h2&gt;
  
  
  Anti-patterns
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Pasting finished lyrics into a single Inspiration prompt so style language and verses fight for the same sentence.&lt;/li&gt;
&lt;li&gt;Inventing lyrics because a Custom form has a lyrics field, when you actually wanted an instrumental.&lt;/li&gt;
&lt;li&gt;Writing a long note that only restates what the still already shows.&lt;/li&gt;
&lt;li&gt;Treating a research paper’s numbers as if they belonged to the button you clicked.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ship when the filename records the control (&lt;code&gt;custom-lyrics&lt;/code&gt;, &lt;code&gt;inspiration&lt;/code&gt;, or &lt;code&gt;photo+note&lt;/code&gt; / &lt;code&gt;photo-only&lt;/code&gt;) and you have not mixed three briefs in one pass.&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>ai</category>
      <category>music</category>
    </item>
    <item>
      <title>How to Finish a Short Song: Master the Stereo Mix or Split It Into Parts First</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Sun, 08 Nov 2026 07:32:11 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/how-to-finish-a-short-song-master-the-stereo-mix-or-split-it-into-parts-first-4h5l</link>
      <guid>https://dev.to/derek_fowler_tech/how-to-finish-a-short-song-master-the-stereo-mix-or-split-it-into-parts-first-4h5l</guid>
      <description>&lt;p&gt;Short-song pipelines often collapse “finish the track” into one afternoon: raise the loudness of a file that is not mixed yet, or split a mix that only needed to sit next to a playlist. This how-to keeps two lanes named. A workspace like &lt;a href="https://www.wav.ai/" rel="noopener noreferrer"&gt;WAV AI&lt;/a&gt; helps when you pick the lane before you click.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzrpdysxu26pz9hecop1r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzrpdysxu26pz9hecop1r.png" alt="Stem splitter hero" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Decide the lane from the deliverable
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Deliverable&lt;/th&gt;
&lt;th&gt;Lane&lt;/th&gt;
&lt;th&gt;Do not open yet&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Stereo file that should sit next to a release, video, or playlist&lt;/td&gt;
&lt;td&gt;Master the finished mix against a different reference&lt;/td&gt;
&lt;td&gt;A stem split “to see the parts”&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Instrumental, isolated vocal, or one instrument to study&lt;/td&gt;
&lt;td&gt;Split the mix&lt;/td&gt;
&lt;td&gt;A mastering pass on a file whose parts are still the real ask&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Arrangement or balance still changing&lt;/td&gt;
&lt;td&gt;Neither — finish the mix first&lt;/td&gt;
&lt;td&gt;Both in the same undifferentiated click&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href="https://www.izotope.com/community/blog/what-is-mastering" rel="noopener noreferrer"&gt;iZotope’s explainer “What is mastering?”&lt;/a&gt; is the shortest third-party reminder of the order: mastering comes after the mix. Mixing balances separate tracks; mastering listens to the whole mixdown and polishes that stereo file for consistent playback and distribution.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pipeline A — reference-guided mastering
&lt;/h2&gt;

&lt;p&gt;Use &lt;a href="https://www.wav.ai/editor/music-mastering" rel="noopener noreferrer"&gt;AI Mastering&lt;/a&gt; only when arrangement and mix are already ready:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Choose the finished song (upload it or pick it from the Music Library).&lt;/li&gt;
&lt;li&gt;Choose a different reference track that already has the loudness and overall sound you want to move closer to. The same song cannot be both the target and the reference.&lt;/li&gt;
&lt;li&gt;Create the mastered version, then compare original vs mastered.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The reference guides loudness and overall balance. Typical jobs: prepare a song for release; match music that sounds quieter or less even than surrounding tracks in a video or playlist; compare two final directions by running the same song against two different references. Export with a date and keep the unmastered mix for rollback.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pipeline B — split when the parts are the product
&lt;/h2&gt;

&lt;p&gt;Open &lt;a href="https://www.wav.ai/editor/stem-splitter" rel="noopener noreferrer"&gt;Stem Splitter&lt;/a&gt; when the stereo master is not the deliverable:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Choose a song (upload or Music Library).&lt;/li&gt;
&lt;li&gt;Choose the split.&lt;/li&gt;
&lt;li&gt;Listen to each part before you commit it to a rehearsal, karaoke bed, or edit.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Vocal remover produces an instrumental version. A 4-stem split gives vocals, drums, bass, and other elements. A 6-stem split also separates guitar and piano. Those part names overlap the four-family convention (vocals / drums / bass / other) used in source-separation research such as Alexandre Défossez’s &lt;a href="https://arxiv.org/abs/2111.03600" rel="noopener noreferrer"&gt;Hybrid Spectrogram and Waveform Source Separation&lt;/a&gt; (Demucs / MDX 2021). That paper is industry context for why splitting a mix is a different job from finishing a stereo master. It is not a description of this product’s internals, and its quality scores are not product metrics.&lt;/p&gt;

&lt;h2&gt;
  
  
  Anti-patterns
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Mastering a draft whose arrangement will change tomorrow.&lt;/li&gt;
&lt;li&gt;Using the song as its own reference.&lt;/li&gt;
&lt;li&gt;Splitting a finished mix only because it sounded small beside other tracks—try a reference-guided master first.&lt;/li&gt;
&lt;li&gt;Treating a research paper’s numbers as if they belonged to the tool you clicked.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ship when the filename encodes the lane (&lt;code&gt;master-ref-A&lt;/code&gt; or &lt;code&gt;stems-4&lt;/code&gt;) and the unprocessed mix is still one hop away.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Technical Note: Single-Track Remix vs Two-Idea Mashup in a Short BGM Pipeline</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Sat, 07 Nov 2026 07:35:40 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/technical-note-single-track-remix-vs-two-idea-mashup-in-a-short-bgm-pipeline-3j5d</link>
      <guid>https://dev.to/derek_fowler_tech/technical-note-single-track-remix-vs-two-idea-mashup-in-a-short-bgm-pipeline-3j5d</guid>
      <description>&lt;h1&gt;
  
  
  Technical Note: Single-Track Remix vs Two-Idea Mashup in a Short BGM Pipeline
&lt;/h1&gt;

&lt;p&gt;Builders often collapse “fix the bed for the cut” into one afternoon: open every blend and transform control, then wonder why the file is un-diffable. This technical note defines a two-lane pipeline for already-approved material: &lt;strong&gt;remix&lt;/strong&gt; when one keeper needs structural energy changes; &lt;strong&gt;mashup&lt;/strong&gt; when two keepers must share one timeline. A suite like &lt;a href="https://www.wav.ai/" rel="noopener noreferrer"&gt;WAV AI&lt;/a&gt; helps when those lanes stay named.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcdkgwf5ttk5ogugusg2p.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcdkgwf5ttk5ogugusg2p.png" alt="Music mashup hero" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Pipeline contract
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Lane&lt;/th&gt;
&lt;th&gt;Input you trust&lt;/th&gt;
&lt;th&gt;Output artifact&lt;/th&gt;
&lt;th&gt;Failure mode&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;REMIX&lt;/td&gt;
&lt;td&gt;One named keeper; picture timing stable&lt;/td&gt;
&lt;td&gt;Dated remix WAV/MP3 + archived pre-remix&lt;/td&gt;
&lt;td&gt;Remixing a scratch as if it were final&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;MASHUP&lt;/td&gt;
&lt;td&gt;Two keepers that each survive dialogue&lt;/td&gt;
&lt;td&gt;Dated mashup + intact A/B sources&lt;/td&gt;
&lt;td&gt;Blending two hypotheses “to hide gaps”&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;BOTH (forbidden same hour)&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;Un-diffable “we tried everything”&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Write the lane name in the ticket title before you click anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lane A — remix as structured transform
&lt;/h2&gt;

&lt;p&gt;Treat &lt;a href="https://www.wav.ai/editor/remix" rel="noopener noreferrer"&gt;Music Remix&lt;/a&gt; like a single-op compiler on one identity:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;assert(source.is_keeper)
change = one_line_contract()   # e.g. "soften bars 8–16 under VO"
candidate = remix(source, change)
keeper_out = pick_under_dialogue([source, candidate])
save(keeper_out, f"remix-{date}-v1")
archive(source)                # rollback path stays one hop
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Text-to-music systems such as &lt;a href="https://research.google/pubs/musiclm-generating-music-from-text/" rel="noopener noreferrer"&gt;MusicLM&lt;/a&gt; (Google Research) show language can steer hierarchical generation. That supports short, revisable change briefs—not endless remix loops on a non-keeper.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lane B — mashup as relationship edit
&lt;/h2&gt;

&lt;p&gt;Open &lt;a href="https://www.wav.ai/editor/mashup" rel="noopener noreferrer"&gt;AI Mashup&lt;/a&gt; only when &lt;code&gt;keeper-A&lt;/code&gt; and &lt;code&gt;keeper-B&lt;/code&gt; both survive critique:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Assign roles (&lt;code&gt;groove&lt;/code&gt;, &lt;code&gt;lift&lt;/code&gt;, &lt;code&gt;texture&lt;/code&gt;) so the blend has a job description.&lt;/li&gt;
&lt;li&gt;Rehydrate shared hard negatives and duration budget.&lt;/li&gt;
&lt;li&gt;Apply &lt;strong&gt;one&lt;/strong&gt; mashup pass; reject versions where neither source remains recognizable under picture.&lt;/li&gt;
&lt;li&gt;Emit &lt;code&gt;mashup-{date}&lt;/code&gt;; never overwrite A or B in place.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Interactive creative ML work around &lt;a href="https://magenta.withgoogle.com/" rel="noopener noreferrer"&gt;Magenta&lt;/a&gt; emphasizes control surfaces over one-shot magic. Remix is a control surface on one track; mashup is a control surface on a pair. Mixing those jobs into one click deletes the audit trail.&lt;/p&gt;

&lt;h2&gt;
  
  
  Anti-patterns
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Mashupping two generator scratches “just in case.”&lt;/li&gt;
&lt;li&gt;Running five remixes on A when the real ask was “borrow B’s lift.”&lt;/li&gt;
&lt;li&gt;Citing product marketing stats as pipeline “data”—use primary research links instead.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ship when speech still reads and the filename encodes the lane. Pretty can wait for the next ticket.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Technical Note: Generator Scratch vs Music-Maker Workspace in a Short BGM Pipeline</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Thu, 05 Nov 2026 10:19:52 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/technical-note-generator-scratch-vs-music-maker-workspace-in-a-short-bgm-pipeline-4ild</link>
      <guid>https://dev.to/derek_fowler_tech/technical-note-generator-scratch-vs-music-maker-workspace-in-a-short-bgm-pipeline-4ild</guid>
      <description>&lt;p&gt;Builders often collapse “AI music for the cut” into one afternoon: one prompt, one export, one upload. Then the picture changes and the file is trash—or worse, they open every advanced control before they know if the mood even works. This technical note defines a two-lane pipeline: disposable generator scratch first, structured music-maker workspace second. A suite like &lt;a href="https://www.wav.ai/" rel="noopener noreferrer"&gt;WAV AI&lt;/a&gt; helps when those lanes stay named.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F61ad03n9lg5u4yugxuc2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F61ad03n9lg5u4yugxuc2.png" alt="Text to music feature"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Pipeline contract
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Lane&lt;/th&gt;
&lt;th&gt;Input you trust&lt;/th&gt;
&lt;th&gt;Output artifact&lt;/th&gt;
&lt;th&gt;Failure mode&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GENERATOR&lt;/td&gt;
&lt;td&gt;Picture timing still soft; mood hypothesis only&lt;/td&gt;
&lt;td&gt;Dated scratch WAV/MP3&lt;/td&gt;
&lt;td&gt;Treating scratch as final&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;WORKSPACE&lt;/td&gt;
&lt;td&gt;Mood + timing approved under dialogue&lt;/td&gt;
&lt;td&gt;Section-edited keeper + named export&lt;/td&gt;
&lt;td&gt;Editing before approval&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;BOTH (forbidden same hour)&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;Un-diffable “we tried everything”&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Write the lane name in the ticket title before you click anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lane A — free generator as scratch compiler
&lt;/h2&gt;

&lt;p&gt;Treat a &lt;a href="https://www.wav.ai/tools/ai-music-generator" rel="noopener noreferrer"&gt;Free AI Music Generator&lt;/a&gt; like a fast compiler for hypotheses:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;prompt&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;genre&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;bpm_hint&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;mood&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;hard_negatives&lt;/span&gt;
&lt;span class="n"&gt;candidates&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;generate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;keeper_scratch&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;pick_under_dialogue&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;candidates&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="nf"&gt;save&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;keeper_scratch&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;scratch-&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;date&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;-v1&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="c1"&gt;# stop — no extend/remix yet
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Text-to-music systems such as &lt;a href="https://research.google/pubs/musiclm-generating-music-from-text/" rel="noopener noreferrer"&gt;MusicLM&lt;/a&gt; (Google Research) show language can steer hierarchical generation. That is a reason to keep prompts short and revisable—not a reason to skip a later structured pass.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lane B — music-maker workspace as structured edit
&lt;/h2&gt;

&lt;p&gt;Open an &lt;a href="https://www.wav.ai/music" rel="noopener noreferrer"&gt;AI Music Maker&lt;/a&gt; only when &lt;code&gt;scratch-vN&lt;/code&gt; survives critique:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Rehydrate the brief (same negatives, same duration budget).&lt;/li&gt;
&lt;li&gt;Apply &lt;strong&gt;one&lt;/strong&gt; structural op: extend a soft middle, remix energy, or replace a noisy intro window.&lt;/li&gt;
&lt;li&gt;Diff by ear under dialogue; reject “louder but less intelligible.”&lt;/li&gt;
&lt;li&gt;Emit &lt;code&gt;keeper-{date}&lt;/code&gt;; archive scratch separately so rollback is one path.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Interactive creative ML work around &lt;a href="https://magenta.withgoogle.com/" rel="noopener noreferrer"&gt;Magenta&lt;/a&gt; emphasizes control surfaces over one-shot magic. Workspace ops are control surfaces; generator prompts are exploration.&lt;/p&gt;

&lt;h2&gt;
  
  
  Anti-patterns
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Running extend/remix on every generator candidate “just in case.”&lt;/li&gt;
&lt;li&gt;Renaming &lt;code&gt;scratch-v1&lt;/code&gt; to &lt;code&gt;final&lt;/code&gt; without a workspace pass when the cut will rerun.&lt;/li&gt;
&lt;li&gt;Citing product marketing stats as pipeline “data”—use primary research links instead.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ship when speech still reads and the filename encodes the lane. Pretty can wait for the next ticket.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Technical Note: Generator Scratch vs Music-Maker Workspace in a Short BGM Pipeline</title>
      <dc:creator>Derek Fowler</dc:creator>
      <pubDate>Thu, 05 Nov 2026 08:00:29 +0000</pubDate>
      <link>https://dev.to/derek_fowler_tech/technical-note-generator-scratch-vs-music-maker-workspace-in-a-short-bgm-pipeline-4kdd</link>
      <guid>https://dev.to/derek_fowler_tech/technical-note-generator-scratch-vs-music-maker-workspace-in-a-short-bgm-pipeline-4kdd</guid>
      <description>&lt;p&gt;Builders often collapse “AI music for the cut” into one afternoon: one prompt, one export, one upload. Then the picture changes and the file is trash—or worse, they open every advanced control before they know if the mood even works. This technical note defines a two-lane pipeline: disposable generator scratch first, structured music-maker workspace second. A suite like &lt;a href="https://www.wav.ai/" rel="noopener noreferrer"&gt;WAV AI&lt;/a&gt; helps when those lanes stay named.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F61ad03n9lg5u4yugxuc2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F61ad03n9lg5u4yugxuc2.png" alt="Text to music feature" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Pipeline contract
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Lane&lt;/th&gt;
&lt;th&gt;Input you trust&lt;/th&gt;
&lt;th&gt;Output artifact&lt;/th&gt;
&lt;th&gt;Failure mode&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;GENERATOR&lt;/td&gt;
&lt;td&gt;Picture timing still soft; mood hypothesis only&lt;/td&gt;
&lt;td&gt;Dated scratch WAV/MP3&lt;/td&gt;
&lt;td&gt;Treating scratch as final&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;WORKSPACE&lt;/td&gt;
&lt;td&gt;Mood + timing approved under dialogue&lt;/td&gt;
&lt;td&gt;Section-edited keeper + named export&lt;/td&gt;
&lt;td&gt;Editing before approval&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;BOTH (forbidden same hour)&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;—&lt;/td&gt;
&lt;td&gt;Un-diffable “we tried everything”&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Write the lane name in the ticket title before you click anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lane A — free generator as scratch compiler
&lt;/h2&gt;

&lt;p&gt;Treat a &lt;a href="https://www.wav.ai/tools/ai-music-generator" rel="noopener noreferrer"&gt;Free AI Music Generator&lt;/a&gt; like a fast compiler for hypotheses:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;prompt = genre + bpm_hint + mood + hard_negatives
candidates = generate(n=2)
keeper_scratch = pick_under_dialogue(candidates)
save(keeper_scratch, f"scratch-{date}-v1")
# stop — no extend/remix yet
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Text-to-music systems such as &lt;a href="https://research.google/pubs/musiclm-generating-music-from-text/" rel="noopener noreferrer"&gt;MusicLM&lt;/a&gt; (Google Research) show language can steer hierarchical generation. That is a reason to keep prompts short and revisable—not a reason to skip a later structured pass.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lane B — music-maker workspace as structured edit
&lt;/h2&gt;

&lt;p&gt;Open an &lt;a href="https://www.wav.ai/music" rel="noopener noreferrer"&gt;AI Music Maker&lt;/a&gt; only when &lt;code&gt;scratch-vN&lt;/code&gt; survives critique:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Rehydrate the brief (same negatives, same duration budget).&lt;/li&gt;
&lt;li&gt;Apply &lt;strong&gt;one&lt;/strong&gt; structural op: extend a soft middle, remix energy, or replace a noisy intro window.&lt;/li&gt;
&lt;li&gt;Diff by ear under dialogue; reject “louder but less intelligible.”&lt;/li&gt;
&lt;li&gt;Emit &lt;code&gt;keeper-{date}&lt;/code&gt;; archive scratch separately so rollback is one path.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Interactive creative ML work around &lt;a href="https://magenta.withgoogle.com/" rel="noopener noreferrer"&gt;Magenta&lt;/a&gt; emphasizes control surfaces over one-shot magic. Workspace ops are control surfaces; generator prompts are exploration.&lt;/p&gt;

&lt;h2&gt;
  
  
  Anti-patterns
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Running extend/remix on every generator candidate “just in case.”&lt;/li&gt;
&lt;li&gt;Renaming &lt;code&gt;scratch-v1&lt;/code&gt; to &lt;code&gt;final&lt;/code&gt; without a workspace pass when the cut will rerun.&lt;/li&gt;
&lt;li&gt;Citing product marketing stats as pipeline “data”—use primary research links instead.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ship when speech still reads and the filename encodes the lane. Pretty can wait for the next ticket.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>music</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
