New EYESY OS v3

EYESY
83

There is a new scenes converter tool in the docs:

It will convert a v2 Scenes.csv to a collection of v3 scene folders. It is possible for the old scene to reference a mode that isn’t present, in which case it wont get loaded.

1 Like
84

Can you paste your palette.json file that you are using? For example, this is what the file should look like:

[
{"name":"My Palette","a":[0.5,0.5,0.5],"b":[1,1,1],"c":[1,1,1],"d":[0,0.33,0.67]},
{"name":"Palette 2","a":[0.55,0.09,0.09],"b":[-0.75,-1.12,-1.46],"c":[5,4.03,2.71],"d":[0,0.33,0.67]}
]
1 Like
85

I’m a goof! I forgot the main brackets before the curly braces. I am successful. While I have you though, I noted in the manual that theres supposed to be a default palettes file in the documentation. Can we have access to it? Did I miss it as well?

86

We need to update the manual. In the meantime, you can check out the default palettes here:

https://raw.githubusercontent.com/critterandguitari/EYESY_OS/refs/heads/master/engines/python/color_palettes.py

1 Like
87

Awesome, thank you so much!

88

Thank you! Not sure how I missed this in the docs.

89

I recently flashed a card on a Mac and got OS v3.0 up and running. I’ve had problems where it seems to just shut off whenever it wants, and about 50% of the time, when i connect to wi-fi, the unit turns off.

Also, is there any plans to bring back eyesy.local for the browser interface? that’s so much easier to remember than an IP that could change. That’s how the Ableton Move interface works (move.local).

If I flashed a new card, and kept the old card, can I simply use the older OS without issues?

+1 for bringing back Ableton Link. I have a Move and a Push 3 and would definitely use that feature if it were resurrected.

90

Hi - this sounds like it could be related to how the SD card is inserted in the EYESY. With the power off, can you eject it and re-insert it. No need to fully remove it from the EYESY - just let it spring out ~1/8" and then push it back in. You should feel/hear a click when it is correctly captured by the SD card holder inside the EYESY.

It could also be related to an inadequate power supply - are you using a supply with output specs of 9VDC, 1000mA minimum, and a 2.1mm center positive tip?

If the problem continues, please contact us directly.

91

I wonder if it’s the power supply? I’m using a USB hub with a myVolts Ripcord USB to 9v 2.1mm center positive cable so I can power a small field monitor along with it. I’ve succesfully used this to do visuals at shows for hours without issue on the old OS. The old OS worked reliably, so I think it may be the way the card is inserted. I’ll start there.

This is what I’m using for power:

while also powering this:

92

Thanks for the additional information about your power set up. In my experience, the myVolts Ripcord supplies are great, but they’ll just stop producing any output voltage if the draw from the device it is powering is too much for it.

If you tried the EYESY’s stock power supply and the behavior went away, it would suggest that the issue is with the Ripcord not being able to meet the demand from the EYESY.

93

There is a minor update to the EYESY OS. The latest v3.1 fixes a few problems:

  • Allows more special characters in WiFi password.
  • MIDI note off messages are recognized. This was leading to stuck notes for certain gear.
  • Changes to composite videos settings are saved.

Follow the steps in the manual to update: