#63

Pretty basic on both the sound and visuals front, but, Digitakt is sequencing both sounds and Eyesy parameter changes here.

https://www.instagram.com/p/CHhAcR6BKem/?igshid=1ofzlh5yuds3s

3 Likes
#64

Eyesy web editor kinda working (though probably still buggy as heck):

https://www.instagram.com/p/CHhRmUDB60P/

7 Likes
#65

Having it on shield would be sick! Is it possible to unblock HDMI output?

2 Likes
#66

Man you work so fast, amazing.

#67

installed, I get blank screen in both fates and monitorā€¦

#68

Do you have this as a branch or PR? Iā€™d be happy to also work on it. Iā€™m a web engineer by trade, in theory.

#69

Not yet. Gonna try to wrangle that together later today. Iā€™ll zap you a msg when I get it together.

2 Likes
#70

Working at first try! Even audio input going
Did Someone try HDMI to VGA adapters? On my HDMI screen is working, not on my old VGA one via an adapter

#71

another thing: how can i lower the treshold of the audio input?

#72

OpenFrameworks/lua engine* compiled and demo patches working!
https://www.instagram.com/p/CHmek0XhbVm/

(* super bleeding edge stuff there and not many example patches to look at yet)

ā€¦

button 1 is a shift, so click once (or 2-click maybe) to switch from the main info menu to a set of controls for input gain, trigger source and midi channel

7 Likes
#73

Hey yā€™all! Iā€™ve been working with @okyeron to get the webapp working, and itā€™s now merged in. Please follow the instructions in the README: https://github.com/Lcchy/Eyesy_for_fates

If you do try this, let me know if it works or if you run into issues. I only have my one Fates, so I havenā€™t been able to test it on other hardware.

PR if youā€™re curious: https://github.com/Lcchy/Eyesy_for_fates/pull/2

PXL_20201116_064512944
PXL_20201116_0645129444032Ɨ3024 4.29 MB

13 Likes
#74

Thanks for this, Iā€™ve installed Eyesy as per top of the page instructions but I get blank screen.

#75

Iā€™m sorry to hear! Letā€™s see if we can figure it out. Some questions to help troubleshoot:

  1. When you say top of page instructions, which instructions are you following?
  2. Are you plugging in the HDMI cable while Fates is powered down and then powering up? You canā€™t plug in the HDMI cable after power; Fates doesnā€™t seem to recognize it.
  3. Which HDMI port are you plugging into? The documentation says ā€˜firstā€™, which is hard to say which one is first :slight_smile: I have a Pi4 and it is the HDMI port closest to the front of the unit.
  4. If you do all of the above, and you runs Norns, do you get anything on screen? For me, itā€™s very small, but I get some activity at the very top of the screen. See photo:
    PXL_20201116_214443389
    PXL_20201116_2144433894032Ɨ3024 3.86 MB
  5. If you power up without any HDMI cable, and run Eyesy, do you get any activity on your Fates screen, or just a blank screen?
  6. When you power up Fates with an HDMI cable plugged in, do you get a screen with a square color gradation? It may be specific to my Pi4, but mine looks like this. Itā€™s only on screen for a couple of seconds.
    PXL_20201116_214410919
    PXL_20201116_2144109194032Ɨ3024 2.42 MB

Some of this information should help us narrow down what might be going on.

1 Like
#76

Update: Web editor !

Thanks a lot to @xenus_dad and @okyeron for making the web editor work! This is very cool!

(I also added the possibility to use the two fates inputs independently with etc.audio_left and etc.audio_right in the Mode scripts, etc.audio_in remains L+R, thanks @TheTechnobear for his code on OTC)

In order to update, you can run : cd ~/sidekick/patches/Eyesy; git pull; ./deploy.sh

6 Likes
#77

This is amazing! Very cool work.

Does anyone else experience quite bit of latency between audio and video? Visuals seem to be around ~300ā€“500ms behind audio input for me. Midi triggers are tighter to visuals

My fates is a pi3.

#78

For me audio is reflected pretty much real time. Iā€™m on a Pi4. Are you viewing the Eyesy hdmi output directly or through some sort of capture device possibly?

#79

Itā€™s definitely directā€”though I am running it into a 4K tv screen; which might be a struggle for the pi3?

#80

Thank you, I made some progress with the cabIe plugged in before powering up. I get the gradient square and then a list of run services until it gets to norns login:
Them I am stuckā€¦
Installed as per Github instructions

image
image3264Ɨ2448 2.6 MB

#81

Looks like it has succesfully installed, I got it working (at least by looking at the onboard screen, I need to find where that damn micro-HDMI adapetr isā€¦)
However, if I relaunch Norns again (from sidekick), most of Norns commands are stuck (canā€™t select any app, encoders stop working, ā€œscanningā€ for apps hangsā€¦)ā€¦everything is up-to-dateā€¦

#82

Ok, that is useful. This is not a solution, but, try this:

  1. Without an HDMI cable plugged, launch Fates.
  2. Using Sidekick, launch Eyesy.
  3. Using Sidekick, power down and then unplug power.
  4. Plug in the HDMI cable, then plug in power.

Iā€™m curious what you get if you do things in that order. Again itā€™s not a real solution, but it helps with diagnostics and it also might get it working for you.