From 10133a262cbc86af1b719b83ce102e28a8e855cb Mon Sep 17 00:00:00 2001
From: Flex Council <65683126+FlexCouncil@users.noreply.github.com>
Date: Tue, 16 Jul 2024 17:36:52 -0700
Subject: [PATCH] Update README.md

---
 README.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/README.md b/README.md
index 2d272bf..2f5fc55 100644
--- a/README.md
+++ b/README.md
@@ -15,5 +15,3 @@ At the bottom-right is a pitch filter. All notes are selected by default. If you
 At the far right are octave range sliders, with “Lo Oct” representing the octave floor and “Hi Oct” representing the octave ceiling, rooted in the note C. They will constrain the algorithms' output to the desired pitch range (inclusive for "Lo Oct" and exclusive for "Hi Oct.") For example, if you have “Lo Oct” set to “2” and and “Hi Oct” set to “5,” all notes between and including C2 and B4 will be let through as is. All notes outside that range will be converted to the nearest in-range octave. If “Lo Oct” is greater than or equal to “Hi Oct,” no notes will be returned.
 
 This version (1.0) is viable in the studio, but use caution if performing live. Sometimes the algorithms don’t make any notes at all or get stuck on the same notes, but they usually recover after a cycle or two. If this happens for a long period, try adding some notes manually or increasing the temperature. If all else fails, click the “Restart” button at the bottom-right.
-
-Note: The device will work only when frozen. If you unfreeze the device, the reference to the Node script will break. However, you can edit this ([**unfrozen device**](https://github.com/FlexCouncil/Clip-Evolver/blob/main/Clip-Evolver-Unfrozen.zip)) and re-freeze it when you are ready to use it.