Intentropy Creative Studios in Newcastle, New South Wales | Arts and entertainment

Intentropy Creative Studios

Locality: Newcastle, New South Wales

Phone: +61 473 888 922

Add/Update information

Reviews

Tags

• Arts and entertainment
• Record label

25.01.2022 I have begun work on coding some MIDI to Open Sound Control conversion tools for osctoolkit. Open source code for osctoolkit can be found here. https://github.com/ShaneHutter/osctoolkit

21.01.2022 The Reaper DAW supports Open Sound Control. https://www.reaper.fm/sdk/osc/osc.php

18.01.2022 I was able to confirm that osctoolkit will run on a Mac, providing that all the dependencies are installed properly, and the scripts are run with Python3. To do: Simplify the installation, Build a user friendly GUI, ... Ensure it will also run on Windows. See more

16.01.2022 I've just added path aliasing to my software "OSC Whispers" Essentially this will allow musicians/producers to control a massive amount of equipment, instruments, lighting gear, live visuals, and even recording software (DAWs) from a single tablet or phone (running Lemur or TouchOSC) While the technicality of this may seem daunting to most musicians/producers, the implication of it is quite phenomenal. When things move along a bit further I will create videos that will make ...this easier for many people to understand. In the meantime I will try to explain how this works here. OSC (Open Sound Control) is a means of sending controller changes, or MIDI like information over a computer network (and allot more). It is thousands of times faster and more capable than MIDI, and can operate wireless over WiFi. OSC Whispers is a program that I am actively developing that acts as an OSC forwarding agent. Imagine you are using TouchOSC as a control pad, on your phone, and you have many pieces of equipment or software that can be controlled with OSC. Unfortunately TouchOSC can only send messages to one IP address and one port number. This means that you can only control one thing with your phone. With OSC Whispers you can assign the IP and port in TouchOSC to the IP and port of a server (say a Raspberry Pi) running the software. Whispers will use a rule set to forward the OSC messages that it receives on to any number of different devices, essentially making the capabilities of TouchOSC virtually limitless. An OSC message has two fundamental parts to it, a path and some arguments. The path indicates what is being changed, and the arguments indicate how it will be changed. For example in order to play back a recording using Ardour (recording software) you can send an OSC message with the path "/ardour/transport_play" and the argument 1. Now imagine you have Ardour running on five different computers and you want them to all start playing at the exact same time. With OSC whispers you can have this message forwarded on to each computer. This latest update adds a feature I call OSC Path Aliasing. What this means is that before Whispers forwards the message, it can be told to replace the path with a new path. Effectively this means that one touch of a button on your phone not only plays all the computers running Ardour, but also some computer running REAPER DAW as well. This doesn't just apply to playing the audio back, but can also be used to arm tracks, start recordings, etc... Imagine a group of musicians getting together, all running there own PCs with there own audio interfaces, having the ability to use it all in tandem for one massive recording session. It's still the early days of development, but it is functional, and improving. Eventually I will have tutorial videos, and example that will hopefully be much easier to understand than this wordy rant is. https://github.com/ShaneHutter/osctoolkit

12.01.2022 Catalystic Enlightenment

11.01.2022 Ive just added path aliasing to my software "OSC Whispers" Essentially this will allow musicians/producers to control a massive amount of equipment, instruments, lighting gear, live visuals, and even recording software (DAWs) from a single tablet or phone (running Lemur or TouchOSC) While the technicality of this may seem daunting to most musicians/producers, the implication of it is quite phenomenal. When things move along a bit further I will create videos that will make ...this easier for many people to understand. In the meantime I will try to explain how this works here. OSC (Open Sound Control) is a means of sending controller changes, or MIDI like information over a computer network (and allot more). It is thousands of times faster and more capable than MIDI, and can operate wireless over WiFi. OSC Whispers is a program that I am actively developing that acts as an OSC forwarding agent. Imagine you are using TouchOSC as a control pad, on your phone, and you have many pieces of equipment or software that can be controlled with OSC. Unfortunately TouchOSC can only send messages to one IP address and one port number. This means that you can only control one thing with your phone. With OSC Whispers you can assign the IP and port in TouchOSC to the IP and port of a server (say a Raspberry Pi) running the software. Whispers will use a rule set to forward the OSC messages that it receives on to any number of different devices, essentially making the capabilities of TouchOSC virtually limitless. An OSC message has two fundamental parts to it, a path and some arguments. The path indicates what is being changed, and the arguments indicate how it will be changed. For example in order to play back a recording using Ardour (recording software) you can send an OSC message with the path "/ardour/transport_play" and the argument 1. Now imagine you have Ardour running on five different computers and you want them to all start playing at the exact same time. With OSC whispers you can have this message forwarded on to each computer. This latest update adds a feature I call OSC Path Aliasing. What this means is that before Whispers forwards the message, it can be told to replace the path with a new path. Effectively this means that one touch of a button on your phone not only plays all the computers running Ardour, but also some computer running REAPER DAW as well. This doesnt just apply to playing the audio back, but can also be used to arm tracks, start recordings, etc... Imagine a group of musicians getting together, all running there own PCs with there own audio interfaces, having the ability to use it all in tandem for one massive recording session. Its still the early days of development, but it is functional, and improving. Eventually I will have tutorial videos, and example that will hopefully be much easier to understand than this wordy rant is. https://github.com/ShaneHutter/osctoolkit

10.01.2022 circa 2007 - 2014

01.01.2022 In order to create increasingly complex animations, using unconventional means, and within a reasonable timeframe, I have been working on a Python module for automating mouse and keyboard actions on Linux/Unix systems. The module is coming along nicely. Https://www.github.com/ShaneHutter/pyxdotool