Releases: t3duk/goxlr
v1.3.1
v1.3.0
GOXLR JS v1.3.0
New Features:
- Now you can use more then one GoXLR with the wrapper. Refer to the documentation for help with this.
- If you don't want the functions to initialise the connection by themselves, you can now manually open the connection with
connect()
. - Debug system, really only for my benefit or if there is an error with the wrapper you would like to report.
Bug Fixes:
- Event Queue system would include patches and incorrect IDs.
- Event Queue deletes data once used.
- Fixed functions opening connection if already closed.
Standard disclaimer applies found here
v1.2.2
v1.2.1
GOXLR JS v1.2.1
This update includes some new features which will make using the wrapper easier.
- We have added an
event queue system
. Now, all functions will return something, within 10 seconds. Read more about it here in the documentation.
Standard disclaimer applies found here
v1.2.0
GOXLR JS v1.2.0
This update includes some new features which will make using the wrapper easier.
- You can now change the bind address and port when creating the
GoXLR Instance
. Refer to the documentation to see more. - Merged 1goxlrCommands
,
daemonCommandsand
generalCommandsto
goxlr`. - When running a function, GOXLR JS will now not open a new connection (unless there is no existing one) and will not close the connection once finished. Developers will need to intergrade the
close()
function. This improves general things about the wrapper.
If you have any suggestions, feedback or and bugs to report please open an issue.
Standard disclaimer applies found here
v1.1.1 - ReadMe
README.md Update
Standard disclaimer applies found here
v1.1.0 - Inital Release
This is the initial release of GoXLR JS. This is a wrapper for the GoXLR Utility WebSocket API which is an open soured alternative to the official TC-Helicon app which runs on your computer locally.
Changelog
- Added Initialisation Stuff
- Added General Commands
- Added GoXLR Commands
- Added Daemon Commands
- Started Wiki
There are just under 150 separate commands, and I have not had time to test them all or document them all. They will all slowly be documented, if you notice anything wrong with them, open an issue and even better fix it with a PR.
Standard disclaimer applies found here