Merge branch 'v0.13.4'

Author: dromer

.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 0.13.3
+current_version = 0.13.4
 
 [bumpversion:file:pyproject.toml]
 search = {current_version}

.github/workflows/ci.yml

@@ -8,7 +8,7 @@ on:
 jobs:
 
   test:
-    runs-on: ubuntu-20.04
+    runs-on: ubuntu-22.04
     strategy:
       matrix:
         python-version: ['3.8', '3.9', '3.10', '3.11', '3.12']
@@ -32,7 +32,7 @@ jobs:
         run: tox
 
   build:
-    runs-on: ubuntu-20.04
+    runs-on: ubuntu-22.04
     steps:
       - uses: actions/checkout@v3
         with:

CHANGELOG.md

@@ -1,6 +1,18 @@
 CHANGELOG
 =====
 
+0.13.4
+-----
+
+Bugfixes:
+
+* sending `[stop(` to `[line~]` when it's not running no longer jumps the current value (#188)
+* JS: emsdk 4.0.7 EXPORTED_RUNTIME_METHODS
+* Typing: move obj_perf to defaultdict()
+* Documentation: corrections
+* CI: move to ubuntu-22.04
+* Dependency updates
+
 0.13.3
 -----
 

docs/02.getting_started.md

@@ -99,10 +99,11 @@ This list will be continuously epanded to document differences in object behavio
 * Heavy does not support numbers in `[unpack]`, e.g. `[unpack 0 0]` gives `Heavy only supports arguments 'f' and 's' to unpack.` Workaround is to use `f` instead, e.g. `[unpack f f]`, and if necessary prime the default values with a `[loadbang]` and `[0 0(`.
 * Sliders and number inputs are converted to `[f ]` and thus do not store send/receive/initialization/etc. settings.
 * Heavy does not accept arguments and control connections to: `[rzero~]`, `[rzero_rev~]`, `[czero~]`, `[czero_rev~]`. In Heavy, these objects accept only signal inputs. Arguments and control connections are ignored.
-* On the `[select]` object it is currently not possible to set the arguments via the right inlet (internally a hardcoded switch_case is used).
+* On the `[select]` and `[route]` objects it is currently not possible to set the arguments via the right inlet (internally a hardcoded switch_case is used).
 * Heavy supports remote/send messages, however empty messages are currently removed. So the typical `[; bla 1(` multiline message needs to contain at least something on the first line: `[_; bla 1(`.
-* Remote/send messages with `sinesum` or `const` arguments to initialize table values are not supported.
-* `[metro]` and `[timer]` objects do not accept tempo messages or unit arguments.
+* Remote/send messages with `sinesum`, `const` or `resize` arguments to initialize table values, or modify the table dimensions, are not supported.
+* `[delay]`, `[metro]` and `[timer]` objects do not accept tempo messages or unit arguments.
 * `[snapshot~]` does not respond within the same control flow as it executes in signal context. Its output happens on the next audio cycle, so additional care for this control flow needs to be taken into account if you depend on synchronous execution. It also doesn't accept `[set(` messages.
 * Certain filters are sensitive to ‘blowing up’ at very low or very high cutoff frequencies and/or resonances, due to the filter coefficients not being perfectly represented with a finite number of bits. While Pure data natively uses 64 bits, platforms like `OWL` and `Daisy`  that use 32 bit float are more sensitive to this. For example, the Pure data `[bp~]` filter is implemented with a biquad which is prone to fail or distort with cutoff frequencies less than around 200 Hz (at 48kHz sample rate).
+* Right inlet for table onset of `[tabread4~]` does not do anything.
 * Heavy does not support multichannel connections.

hvcc/generators/c2js/c2js.py

@@ -127,12 +127,13 @@ def run_emscripten(
             "-s", "RESERVED_FUNCTION_POINTERS=2",
             "-s", "DEFAULT_LIBRARY_FUNCS_TO_INCLUDE=$addFunction",
             "-s", f"EXPORTED_FUNCTIONS=[{hv_api_defs.format(patch_name)}]",
+            "-s", "EXPORTED_RUNTIME_METHODS=HEAPF32",
             "-s", f"MODULARIZE={should_modularize}",
-            '-s', 'ASSERTIONS=1',
-            '-s', f'ENVIRONMENT={environment}',
-            '-s', 'SINGLE_FILE=1',
-            '-s', 'ALLOW_TABLE_GROWTH=1',
-            '-s', f'BINARYEN_ASYNC_COMPILATION={binaryen_async}',  # Set this to 0 for the worklet so we don't
+            "-s", "ASSERTIONS=1",
+            "-s", f"ENVIRONMENT={environment}",
+            "-s", "SINGLE_FILE=1",
+            "-s", "ALLOW_TABLE_GROWTH=1",
+            "-s", f"BINARYEN_ASYNC_COMPILATION={binaryen_async}",  # Set this to 0 for the worklet so we don't
                                                                    # wait for promises when instantiating
             "--post-js", post_js_path
         ]

hvcc/generators/ir2c/ir2c_perf.py

@@ -33,24 +33,26 @@ def perf(
         blocksize: int = 512,
         mhz: int = 1000,
         verbose: bool = False
-    ) -> Dict[str, Counter]:
+    ) -> Dict[str, Dict[str, float]]:
         # read the hv.ir.json file
         with open(os.path.join(os.path.dirname(__file__), "../../core/json/heavy.ir.json"), "r") as f:
             HEAVY_IR_JSON = HeavyIRType(**json.load(f)).root
 
         objects: Counter = Counter()
-        perf: Counter = Counter()
-        per_object_perf: Dict[str, Counter] = defaultdict(Counter)
+        perf: Dict[str, float] = defaultdict(float)
+        per_object_perf: Dict[str, Dict[str, float]] = defaultdict(lambda: defaultdict(float))
+
         for o in ir.signal.processOrder:
             obj_id = o.id
             obj_type = ir.objects[obj_id].type
             if obj_type in HEAVY_IR_JSON.keys():
                 objects[obj_type] += 1
                 obj_perf = HEAVY_IR_JSON[obj_type].perf
                 assert obj_perf is not None
-                c = Counter(obj_perf.model_dump())
-                perf = perf + c
-                per_object_perf[obj_type] = per_object_perf[obj_type] + c
+                c = defaultdict(float, **obj_perf.model_dump())
+                for k, v in c.items():
+                    perf[k] = perf[k] + v
+                    per_object_perf[obj_type][k] = per_object_perf[obj_type][k] + v
             else:
                 print(f"ERROR: Unknown object type {obj_type}")
 
@@ -88,7 +90,8 @@ def perf(
             for k, v in items:
                 if perf["avx"] > 0:
                     print(
-                        "{2:>2.2g}%  {3:<5} {0:<16} {1}".format(k, v, int(100.0 * v["avx"] / perf["avx"]), objects[k])
+                        "{2:>2.2g}%  {3:<5} {0:<16} {1}".format(
+                            k, dict(v), int(100.0 * v["avx"] / perf["avx"]), objects[k])
                     )
 
         return per_object_perf

hvcc/generators/ir2c/static/HvLightPipe.c

@@ -25,7 +25,7 @@
     // https://msdn.microsoft.com/en-us/library/hh875058.aspx#BarrierRestrictions
     // http://doxygen.reactos.org/d8/d47/armintr_8h_a02be7ec76ca51842bc90d9b466b54752.html
     #define hv_sfence() __dmb(0xE) /* _ARM_BARRIER_ST */
-  #elif defined(__GNUC__)
+  #elif defined(__GNUC__) && (__ARM_ARCH >= 7)
     #define hv_sfence() __asm__ volatile ("dmb 0xE":::"memory")
   #else
     // http://stackoverflow.com/questions/19965076/gcc-memory-barrier-sync-synchronize-vs-asm-volatile-memory

hvcc/generators/ir2c/static/HvSignalLine.c

@@ -130,10 +130,11 @@ void sLine_onMessage(HeavyContextInterface *_c, SignalLine *o, int letIn,
     o->m = vdupq_n_f32(0.0f);
     o->t = vdupq_n_f32(x);
 #else // HV_SIMD_NONE
+    float x = (o->n > 0) ? (o->x + o->m) : o->t;
     o->n = 0;
-    o->x += o->m;
+    o->x = x;
     o->m = 0.0f;
-    o->t = o->x;
+    o->t = x;
 #endif
   }
 }

hvcc/types/compiler.py

@@ -35,7 +35,7 @@ class CompilerResp(BaseModel):
     out_file: str = ""
     compile_time: float = 0.0
     obj_counter: Counter = Counter()
-    obj_perf: Dict[str, Counter] = defaultdict(Counter)
+    obj_perf: Dict[str, Dict[str, float]] = defaultdict(lambda: defaultdict(float))
     ir: Optional[IRGraph] = None
 
 

hvcc/version.py

@@ -1 +1 @@
-VERSION = "0.13.3"
+VERSION = "0.13.4"