Expose SynthesisEngine instead of Synthesizer

processing · Sep 21, 2023 · 38b6e37 · 38b6e37
1 parent 868e056
commit 38b6e37
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 5 deletions.
diff --git a/examples/IO/LowLevelEngine/LowLevelEngine.pde b/examples/IO/LowLevelEngine/LowLevelEngine.pde
@@ -1,6 +1,6 @@
 import processing.sound.*;
 
-import com.jsyn.Synthesizer;
+import com.jsyn.engine.SynthesisEngine;
 
 void setup() {
 
@@ -27,7 +27,7 @@ void setup() {
 
   // to get programmatic access to the same information (and more), you can get 
   // and inspect the JSyn Synthesizer class yourself:
-  Synthesizer s = Sound.getSynthesizer();
+  SynthesisEngine s = Sound.getSynthesisEngine();
   println("Current CPU usage: " + s.getUsage());
 
 }

diff --git a/src/processing/sound/Sound.java b/src/processing/sound/Sound.java
@@ -262,9 +262,11 @@ public static void printConnections() {
 	}
 
 	/**
-	 * Direct access to the underlying JSyn Synthesizer object. Use at your own risk.
+	 * Direct access to the underlying JSyn SynthesisEngine object. Use at your 
+	 * own risk.
+	 * @see com.jsyn.engine.SynthesisEngine
 	 */
-	public static Synthesizer getSynthesizer() {
-		return Engine.getEngine().synth;
+	public static SynthesisEngine getSynthesisEngine() {
+		return (SynthesisEngine) Engine.getEngine().synth;
 	}
 }