@clement

Thanks Clément

This is a bug that it doesn't work the same way when triggering it with MSC vs using the Spacebar. I will add this to our tracker.

For now, here's the easiest workaround I could come up with: This file (Fade Demo.izz) will make it behave the way you want it to (and also led me to discover a different bug involving trying to deactivate an activated Scene you're transitioning into mid-transition). If you're clicking around to deactivate Scenes mid-transition that you've already activated you may get an assertion dialog about failing to deactivate the Scene, but it you press "Continue" everything is fine.

The trick is to put a MIDI Show Control Watcher paired with a Text Comparator looking for the cue number of the next Scene (the one you want to "bump" in). When you hit that cue, it'll trigger the Activate Scene actor and bump the next Scene in.

Best wishes,

Woland

@fubbi great !! No more driver nightmare for DMX !!! Thank you a thousand times. Also because with Sonoma arriving I was worried that would cause DMX nightmare. 

Got it all working

Thanks a lot

Andy

@andy-delmaine

You can have a look at creating custom actions for google home (https://developers.google.com/... )

Most likely you can get it to send something to NodeRed (with nodeJS). this way you can avoid a lot of actual coding but it will still be some finicky work. I did not watch it but this seems to be about how to get it going.

Node red has an optional OSC Node https://www.npmjs.com/package/...

@jtsteph said:

I will do. Always happy to share. I just put a gallery up from the show we did at Sound Symposium. I will tag you on it now.

 Can't wait to see!

Hey Isadora community,

I'm new with using Isadora & currently working on my first project: I want to control parameters in Isadora with Control Voltages coming from a Eurorack Modular Synthesizer System via a DC-Coupled Audio-Interface.

I habe already got some results, but figured out crashes, that led me to a general question:

Is it normal that everytime I pull off the usb cable (to the soundcard), Isadora simply closes without any warnings, questions or report on the next startup?
(I'm guessing a major problem in my system, that is also responsible for the "smaller" crashes...)

Working on:
- MBP, mid 2014, high sierra 10.13.6

- Motu Ultralite AVB, Firmware 1.3.4+617 (newest), USB

Some ideas?
Thx in advance!

Lukas

you can use the Korg Nano Kontrol Editor software to assign different control numbers to each unit if you want to keep them both on the same port/channel. or assign different channels or ports. free download here

i know what midi messages the Kaoss DJ sends (it's in the manual, mostly control and note-on). other midi controllers I use (arturia mini lab) work out of the box.

it must be related to Korg using a different MIDI implementation.

@Salimelo 

I've had huge success sending MIDI Show Control (MSC) from QLab and ETC Ion/Nomad lighting consoles to trigger Isadora (via MIDI Show Control Watcher actors paired with comparators), in conjunction with using @dbengali (Mac) and @djinoui 's (Windows) JumpByName custom Isadora plugins and then prefacing Scene names with MSC cue #'s.

JumpByName.izzyplug.zip (Mac)

Best wishes,

Woland

Yeah, I've been using jumpbyname for years. It's been awesome. I usually disable the midi while editing.