Thread: Pedal bored 2.0
View Single Post
Old 11-19-2019, 01:01 PM   #1
Human being with feelings
Join Date: Feb 2009
Posts: 35
Default Pedal bored 2.0

Hi fellow live Reaperites,

After much M and FA these last few months, I'm now at the stage where I'm happy with my working prototype platform for live usage. The attached pix give insight into the physical. Principally, the Behringer FCB1010 is the midi foot controller to drive the workflow. Internally, the three compartments consist of:

Processor bay: Intel NUC D54250 i5 with 16Gb RAM running W10. WiFi and BT module and 120Gb M2 SSD.

I/F bay: Tascam US800 8 in 6 out audio and midi in and out/through. Short audio cables route to the rear patch panel. Additionally, there's a 4 port USB2 hub.

BT bay: BT5 transceiver for IEM using buds.

Latest Reaper [v5.986] and Reapack scripts loaded. I use RealVNC to link into the NUC which currently allows me to develop the workflows and provide a graceful shutdown procedure [using my phone, for example].

Power is currently delivered by the NUC's wall wart via a socket on the patch panel and a switch. On order is a 19vDC power brick that claims to deliver 3.5A at 40000mA/H. I think I'm drawing around 500mA at present with everything up so hopefully, it's ample for gigging. This will be eventually mounted inside the BT bay. The external switch will then allow for internal or external feed should that need arise.

The FCB1010 is powered by a 5v/9v buck converter and modified following the instructions offered by Pipeline Audio. Again a switch allows for the mains to be used should the need arise.

The Tascam US800 is 5v powered via a USB port. The BT5 transceiver has a largish internal battery it seems but again is hooked up to a USB port for charging.

Initial monitoring of the heat inside the NUC is showing mid 60 deg C after running for well over an hour. Whilst there is a quiet fan in the NUC, I'll probably implement a blow and suck pair of small 40mm fans to provide an airflow within the plinth.

The base and the FCB are both attached using neodymium magnets and offer enough holding strength to allow for transport and kicking the unit in error [part of my testing!] and to ease the base off to enable startup [for now].

I can route my guitars in on 4 physical ports and have 2 more set up for mics [balanced cables so phantom power can be used if needed]. This isn't set in stone merely a starting point to see what works best.

I can now see the FCB spitting out midi PC info so I'm getting myself set up for live configs as well as other workflow models I'm looking to test out.

Today, I set myself up an FX chain to use my acoustic guitar to play bass. After a few iterations I've landed on a combo that appears to work reasonably latency free [to my ears at least?]. I've also loaded in the fantastic SM Drums collection though I'll go through the other popular drum VSTs to see which work the most favourable.

There's much more to get through such as:
* use the RasPi3B+ [mounted in the processor bay] as an Access Point to provide a controlled entry into the environment. The Pi will then hotspot to my phone should the t'interweb be needed. The NUC would then use the Ethernet port to communicate whilst the WiFi is temporarily disabled.
* the RasPi will also be used to capture performance data of the box using Node Red & MQTT borrowing techniques from the Home Automation world. Monitoring the health of the NUC and M2 SSD as well as Reaper info can be captured into a mySQL db or webbed into Go Ogle.
*with the CSI project now moving closer to beta then the FCB1010 needs looking into as a control surface if not done already? I also like the look of the micro controllers such as a Behringer X Touch Mini.
* performance tuning the W10 environment and
* using Kali linux on another RasPi to perform pen tests and harden the environment for use out in the real world.

I'm beginning a document to describe all the steps I've gone through and will share at some future point if anyone is interested. I'll also provide a materials list of the items used.

Should anyone have info to share on their best practises, workflows components etc. I'd be grateful to receive. Cheers

Yorky is offline   Reply With Quote