Skip to main content

Everybody needs a DAW

The new year is out and basically DAWs are here to stay. I've been looking for an upgrade from my US-428 which has been serving me faithfully for the last few of years from the time I remembered getting it when it first came out. Frontier designs have done a great job in thinking up really niffy products. Most recently, the wireless tranzport.

So which new DAW will I be spending my hard earned money. Magazines like future music and computer music used to have issues for buying studios under a budget and home studio makeovers with limited cash. We probably wouldn't see that much of those articles anymore as home studios are more popular and the choices of products are ridulous. Any studio makeover is bound to be sponsored by the product's company.

So where do we start? I normally try to look at products that not going to be discontinued or I'm sure will have a long running support (for my intended use lifespan). Even if there may be a product that has kick ass specs, if no one uses it, I wouldn't. Companies that have stood the test of time like tascam, yamaha, m-audio, alesis and mackie would be the first places to look for a DAW.

For most of the products out now, I will put them into 2 categories.

* Mixers pretending to be audio interfaces: e.g. Yamaha, alesis and mackie
* Audio interfaces failing to be mixers: e.g. Tascam, m-audio

I actually like the mixer/daw products, because these things work even if you rip them from your computers. However in this instance, if I'm looking at a US-428 replacement and an upgrade as well to deal with the ordeals of modern home productions.

Requirement 1: Compatibility with all/most software sequencers. This comes in useful when you realise you need to do a project which came in a different format. Pro tools is really being "elite" on only working with its own hardware. M-audio has m-powered pro tools and tascam only allows control over pro tools, but not use the actual interface.

Requirement 2: Enough Ins/outs that also include phantom power. Great when you realise that phantom powers your DI box.

Requirement 3: Motorised faders. Got to have them for automation, its a great incentive to watch sliders move on their own. I wouldn't bother otherwise.


Options:

1) Tascam FW-1884 with the digi 002 rack, hmmm. yes, but how much is that going to cost?

2) M-audio projectmix I/O. Its new and I dont know much about it yet, but can you really have your cake and eat it too?

Comments

Popular posts from this blog

Multiple Broadlink RM mini 3 integration using MQTT

Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this. https://lprhodes.github.io/slate/

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone https://github.com/eschava/broadlink-mqtt

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'
4. Start the python script and check that it started and detected all the RM devices.
Check the log file to see what the IP / MAC addresses are. DEBUG Connected to RM2 Broadlink device at …

Fibaro HCL Virtual Device Slider

How to setup Fibaro home center lite (HCL) slider for virtual devices.

As the Fibaro HCL does not support LUA. The question was how to update the number value of the slider to send to the HTTP string. Thanks to this site which is a really good reference https://www.vesternet.com/resources/application-notes/apnt-88/

The 2 use cases here are;

Sonos HTTP API Volume

To allow for volume control for all Sonos devices, add a virtual device with the IP address for SONOS HTTP API and specify the default port to 5005. Create Slider and put the following text into the string.

GET /volume/_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A


Domotiz Virtual Devices

GET /json.htm?type=command&param=switchlight&idx=XX&switchcmd=Set%20Level&level=_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Replace XX with the device ID.

Restart Fibaro HCL when it stops working automatically

It seems that the Fibaro HCL seems to hang every now and then. Instead of trying to restart it regularly, which doesn't really work, as it's almost impossible to predict when this will happen.

This method checks that the HCL is actually running and in the event it stops working, trigger a script that will restart it.


1. Get a non Fibaro controlled power plug and scripts to control it.

I used a wifi smart plug, TP-link HS100 and downloaded the scripts from

https://blog.georgovassilis.com/2016/05/07/controlling-the-tp-link-hs100-wi-fi-smart-plug/

2. Create a bash script to restart the Fibaro, e.g. restart_fibaro.sh

#!/bin/bash

ip_addr=
scripts=

$scripts/tplink-smartplug.py -t $ip_addr -c off
sleep 10
$scripts/tplink-smartplug.py -t $ip_addr -c on


3. Create a test global variable in the Fibaro HCL

Go to the variables panel and create a test variable, e.g. Test


4. Add a cron entry to test that the Fibaro API is still working and restart if it's not.

The cron script is scheduled ev…