<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Visiyn — Follow the build</title>
    <link>https://visiyn.com/updates</link>
    <description>Dev diary for Visiyn Studios. The product is in development.</description>
    <language>en</language>
    <lastBuildDate>Thu, 24 Sep 2026 21:56:20 GMT</lastBuildDate>
    <item>
      <title>[Draft] The assistant is learning to explain a transition</title>
      <link>https://visiyn.com/updates#explain-a-transition</link>
      <guid isPermaLink="true">https://visiyn.com/updates#explain-a-transition</guid>
      <pubDate>Thu, 24 Sep 2026 12:00:00 GMT</pubDate>
      <description><![CDATA[<p>Work in progress. When a handoff feels early or crowded, the assistant is being taught to answer from the phrase, the overlap, and whether a technique can work there.</p><p>Draft — written for review, not as a release note.</p><p>A DJ already knows the question: why did that transition feel early, crowded, or right? Recent work in the studio is about letting the assistant answer with something it can point at.</p><p>It is being taught to use what it heard and measured. That includes where the phrase and the structure sit, whether vocals and the spectrum are stacked on each other, and whether a technique is viable in that spot.</p><p>This is still in progress. It does not play the set for you. You still run the mix.</p>]]></description>
    </item>
  </channel>
</rss>
