<?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/"
               xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
               xmlns:admin="http://webns.net/mvcb/"
               xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
               xmlns:content="http://purl.org/rss/1.0/modules/content/">
            <channel>
                <title>
					                		V5.0 Octopus Track Start/End - New features                                    </title>
                <link>https://forum.genoqs.net/community/new-features/v5-0-octopus-track-start-end</link>
                <description>genoQs Machines Forum Discussion Board</description>
                <language>en-US</language>
                <lastBuildDate>Mon, 11 May 2026 06:21:30 +0000</lastBuildDate>
                <generator>wpForo</generator>
                <ttl>60</ttl>
                					                    <item>
                        <title>RE: V5.0 Octopus Track Start/End</title>
                        <link>https://forum.genoqs.net/community/new-features/v5-0-octopus-track-start-end#post-249</link>
                        <pubDate>Sat, 23 Apr 2022 14:09:35 +0000</pubDate>
                        <description><![CDATA[@oehi@wilson
Hi Werner,
Thanks for your post. As a Berlin School enthusiast I did some experimental builds of the code along the lines of your suggestion a few years ago (after v5). It was...]]></description>
                        <content:encoded><![CDATA[<p>@oehi<br />@wilson</p>
<p>Hi Werner,</p>
<p>Thanks for your post. As a Berlin School enthusiast I did some experimental builds of the code along the lines of your suggestion a few years ago (after v5). It was limited to Preview Perform Mode for the simple reason that both sequencers have a great many features &amp; a limited amount of buttons - so the question we are continually wrestling with is trying to get the best usage (&amp; most features) out of the available real estate.</p>
<p>Currently, we have a fairly advanced build which will enable control of a track's mute status on a per step basis - which, whilst not changing the track length (as in your example) does give powerful 'Berlin' possibilities.</p>
<p>I can revisit the earlier 'step skip' experiments to see if there is a way we can adopt them to fit the current codebase. </p>
<p>Best,<br />Jean.</p>]]></content:encoded>
                        <category domain="https://forum.genoqs.net/community/new-features">New features</category>                        <dc:creator>Jean Blanc</dc:creator>
                        <guid isPermaLink="true">https://forum.genoqs.net/community/new-features/v5-0-octopus-track-start-end#post-249</guid>
                    </item>
                                        <item>
                        <title>V5.0 Octopus Track Start/End</title>
                        <link>https://forum.genoqs.net/community/new-features/v5-0-octopus-track-start-end#post-245</link>
                        <pubDate>Wed, 20 Apr 2022 19:14:32 +0000</pubDate>
                        <description><![CDATA[Hi all,
track start and stop can be defined by skip of steps. This somehow is a little bit cumbersome. Would nice to have an easy way how to select the start and end points of a track.
Che...]]></description>
                        <content:encoded><![CDATA[<p>Hi all,</p>
<p>track start and stop can be defined by skip of steps. This somehow is a little bit cumbersome. Would nice to have an easy way how to select the start and end points of a track.</p>
<p>Cheers, Werner</p>]]></content:encoded>
                        <category domain="https://forum.genoqs.net/community/new-features">New features</category>                        <dc:creator>Oehi</dc:creator>
                        <guid isPermaLink="true">https://forum.genoqs.net/community/new-features/v5-0-octopus-track-start-end#post-245</guid>
                    </item>
                                                </channel>
        </rss>
        