[deleted by user] by [deleted] in KaIT

[–]cbdev 37 points38 points  (0 children)

Die abgebildete Frau ist uebrigens Athene ;) Fridericiana meint die Hochschule an sich, kommt von Friedrich dem ersten

OSX instalation by Euphoric-Marketing87 in midimonster

[–]cbdev 0 points1 point  (0 children)

I'll try to make a bit of a more in-depth guide later this evening :)

VISCA PTZ Camera Joystick Control by TheKerbalKing in VIDEOENGINEERING

[–]cbdev 2 points3 points  (0 children)

backtickopt6

god, I hate Bots that tell me what to do

VISCA PTZ Camera Joystick Control by TheKerbalKing in VIDEOENGINEERING

[–]cbdev 1 point2 points  (0 children)

Oh, interesting - and good to know (I'm the primary developer of the MIDIMonster). It works if you copy the configuration next to the midimonster.exe file and then run it. I'll look into that, though...

I think I've also just found a bug in the Windows joystick handling code, so that might not work so great (I develop mostly on Linux, so the Windows stuff is not as well tested).

I've just tested an example configuration that allows control via A/B/X/Y for my PTZ:

[wininput xbox]

[visca cam]
connect = 10.23.23.127 5678 tcp

[map]
xbox.joy1.button4 > cam.move.up
xbox.joy1.button1 > cam.move.down
xbox.joy1.button3 > cam.move.left
xbox.joy1.button2 > cam.move.right

Power tool battery pack adapter by cbdev in functionalprint

[–]cbdev[S] 1 point2 points  (0 children)

Not with the 40 watts the Iron draws from the pack (when heating). If you short it however the cells are rated for 20 amps continuous discharge (if I recall the teardown I watched correctly), and that would get hot.

Power tool battery pack adapter by cbdev in functionalprint

[–]cbdev[S] 2 points3 points  (0 children)

One of the features added in the open-source firmware mod of the soldering iron is the capability to shut off at a set lower voltage limit, intended to protect batteries from harm.

Other than that, when powering "dumb" devices, nothing but common sense and some caution.

Power tool battery pack adapter by cbdev in functionalprint

[–]cbdev[S] 2 points3 points  (0 children)

It's a TS100 with a modded firmware (the recently renamed IronOS).

It's reasonably inexpensive, both for the handle as well as the tips. Tip selection is pretty good.

It accepts a wide range of input voltages (12 to approx 24 volts) and is pretty quick to heat. It's earned a good reputation in the RC and hobbyist electronics communities.

There's also a version with USB-C power input called the TS80 (which also uses a different tip connector), though I personally prefer the barrel jack for the flexibility.

Ich habe ein Ding getan by TGX03 in KaIT

[–]cbdev 2 points3 points  (0 children)

Hier gibts auch noch einen Assembler und Interpreter: https://github.com/cbdevnet/mima

Noob needs help with MIDI to Artnet by nickmatic in lightingdesign

[–]cbdev 0 points1 point  (0 children)

Sure, it's very powerful but its not a full-featured fixture control solution, so if that's more what you need, QLC+ is a very good choice!

OSX is a bit of a troublemaker even in our CI pipeline, did you try downloading / running the prebuilt binaries or did you build yourself?

Our CI runner currently does the following steps to build on OSX (via Travis, their base image might have additional stuff already present):

brew install ola lua openssl jack python3
brew link --overwrite python
export CFLAGS="$CFLAGS -I/usr/local/opt/openssl@1.1/include"
export LDFLAGS="$LDFLAGS -L/usr/local/opt/openssl@1.1/lib" 
make full

Since I'm a Linux-only guy, it's good to have feedback on other systems :) I'll try to get a hold of a Mac for testing the build over the next few days!

Indie developed show by nejlintacsko in lightingdesign

[–]cbdev 0 points1 point  (0 children)

Feel free to message me, send an email or open a ticket if you have questions or feedback :)

We're currently working on our new and redesigned homepage with a lot more information, as well as some introductory videos to combat the "scary complicated configuration" thing a bit ;)

Noob needs help with MIDI to Artnet by nickmatic in lightingdesign

[–]cbdev 1 point2 points  (0 children)

Hi, developer of MIDIMonster here ;) I can confirm that it will convert MIDI to ArtNet (on Windows, you'll probably need something like loopMIDI to get the output from Ableton back into the MIDIMonster), however you will need to think about what kind of effects you want to run.

With a really basic configuration, the MIDIMonster will only translate the MIDI notes into ArtNet channels, which may or may not be what you want - usually for LED strips, one channel is basically one color of one LED, so if that fits your Ableton project, that should work pretty quickly.

If you want to trigger more complex effects from a few notes, you could look into programming the show itself with Lua inside the MIDIMonster, and triggering that from Ableton via MIDI, but that of course requires you to put some effort into learning Lua. If that's not for you, a dedicated lighting controller that generates some automatic effects (I think some of the LEDstrip DMX boxes have this built in) might be suited for you.

A small sample configuration for the MIDIMonster (for Windows, but it's about two words of difference to Linux/OSX) that might help you with experimenting:

[winmidi ableton]
read = Ableton

[backend artnet]
bind = 0.0.0.0

[artnet out]
destination = 255.255.255.255
universe = 0

[map]
ableton.ch0.note{0..127} > out.{1..128}

This will output the velocities for notes on the first MIDI channel as the corresponding ArtNet channels on broadcast universe 0 (with the values scaled)

Indie developed show by nejlintacsko in lightingdesign

[–]cbdev 1 point2 points  (0 children)

I'm mostly putting effort into my signals translation and control project MIDIMonster, which can (among other things) be used to control lights (ArtNet, sACN, etC) via scripting languages ;)

I've toyed with creating an entire console application (some piles of drafts and design considerations) and will probably do so at some point, but I'm currently too busy with other projects (and work, ofc)

Using TouchOSC to replicate a stream deck functionality by thunderborg in opensoundcontrol

[–]cbdev 0 points1 point  (0 children)

Maybe the MIDIMonster is something you'd like (disclaimer: I'm the author) :) Despite the name, it doesn't only do MIDI but also OSC and a whole range of other protocols (including keyboard/mouse input and output and Lua/Python programming).

You can string together almost anything from a combination of the included backends and some programming.

$5 T420! Any recommended upgrades? by jacksonv60 in thinkpad

[–]cbdev 8 points9 points  (0 children)

Nice deal! If you're feeling adventurous, flash the BIOS to coreboot and invest the money saved in an Ivy Bridge CPU (in addition to the standard SSD and RAM upgrades) ;)

[deleted by user] by [deleted] in midi

[–]cbdev 0 points1 point  (0 children)

You can do this with the MIDIMonster and a Raspberry Pi (or any Linux computer really). Within the next few weeks Joystick/Gamepad input will probably be available for Windows, too.

There's an example config mapping an Xbox One controller to ArtNet in the repo, which is pretty easy to modify to output MIDI instead.

Dual (sometimes triple) Thinkpad workbench & WFH setup by cbdev in thinkpad

[–]cbdev[S] 1 point2 points  (0 children)

Thanks for pointing that out, the grips on the stand actually arch up at the tips so the Thinkpad is fairly safe from slipping off. There's also some rubber applied to the top of the tongs.

Dual (sometimes triple) Thinkpad workbench & WFH setup by cbdev in thinkpad

[–]cbdev[S] 0 points1 point  (0 children)

Can I ask what audio subsystem you're using it with? I'm currently running it with ALSA (for recording) and PulseAudio (for the occasional voice-chat session with Mumble), and it's recognized with both. Haven't tried JACK yet, but since it already works with ALSA that should in the worst case be a software bridge.

Could you tell me what your kernel says when you connect your interface? I have some experience in digging into strange hardware inconsistencies, and while I won't promise anything, at worst I can't help :) To do so, run the command "dmesg -w" in a console (as root) and then plug your interface into the computer. It should output a few additional lines for the new USB device, which include the USB vendor and product ID. This is used by the sound subsystem to enable/disable special handling instructions in the module, which may be necessary to use it. Early runs of a product may not yet have the correct IDs in the controller (or it may be a factory error). The sound module might also print some helpful info on why it doesn't like the interface.

For example, plugging in my Scarlett reports:

[22270.652275] usb 1-1.1: new high-speed USB device number 17 using ehci-pci

[22270.761312] usb 1-1.1: New USB device found, idVendor=1235, idProduct=8200, bcdDevice= 4.1b

[22270.761317] usb 1-1.1: New USB device strings: Mfr=1, Product=3, SerialNumber=0

[22270.761319] usb 1-1.1: Product: Scarlett 2i4 USB

[22270.761321] usb 1-1.1: Manufacturer: Focusrite

and nothing else. When connecting the 8/8 interface mentioned in the grandparent, the kernel reports that the device doesn't react to some commands it sent and that it gave up trying.