Source code modifications required?

[Edward Childs]

Hi Phil,

Hope you are well! I want to update a legacy sonification project which currently runs fine against jsyn-beta-16.5.1.jar. To run with your most up to date JSyn library, which I understand to be jsyn-20171016.jar, will I need to make modifications to the source code? Can you point me to a guide for doing the necessary upgrades?

Many thanks,

Ed

[Phil Burk]

Hello Ed,

> will I need to make modifications to the source code?

Maybe. I am generally loathe to make modifications to an API. But JSyn was started 25 years ago. The old API was a bit stale.
So I did create a modified API. This page describes how to migrate to the new API:

https://www.softsynth.com/jsyn/docs/migration.php

I also created a bridge so that the old API could run on top of the new API.

See https://www.softsynth.com/jsyn/developers/download.php

jsyn-complete-20160812.jar  is a jar with the OLD and new API and a bridge. Use that in place of jsyn-beta-16.5.1.jar.

If you want to use the old API on top of the latest JSyn build then use 

jsyn-old-api-20161206.jar
along with the newest JAR in your CLASSPATH. It should work.

Let me know what happens.

Phil Burk

[Edward Childs]

Hi Phil,

Thanks for the answer. If I substitute jsyn-complete-20160812.jar for jsyn-beta-16.5.1.jar, everything seems to resolve except for PanUnit and LineOut. I get "cannot be resolved to a type".

Edward

[Edward Childs]

Phil,

It does work fine though to use the second option, to use jsyn-old-api-20161206.jar together with the most recent .jar file (jsyn-20171016.jar).

Thanks,

Edward