#96

:tada: 20 characters of :point_up:

:grinning:

3 Likes
#97

This is so much fun! I have only scratched the surface.

Initial Experiment with composite output:
I edited my config. text with enable_tvout=1 which has enabled the composite out, but this also seems to make the HDMI out not work anymore and will only display EYESY on the Fates screen. Returning the config file to its prior state has restored order.

1 Like
#98

Can you test with enable_tvout=1 and then get the result from cat /proc/fb ?

Maybe with and without HDMI plugged in on reboot?

#99

With HDMI plugged in on boot: 0 fb_ssd1322
Without: 0 fb_ssd1322

What does it mean? :slight_smile: (thanks for the reply)

#100

So
 the HDMI and OLED use the system “framebuffers” to output video.

on my Pi4
1 fb_ssd1322 is the OLED (fb1)
0 DRM emulated is the HDMI (fb0)

So
 in the case of enable_tvout, it seems that this does not use the framebuffers? Will need to do more research on that and see what I can find.

FWIW:

enable_tvout (Pi 4B only)
On the Raspberry Pi 4, composite output is disabled by default, due to the way the internal clocks are interrelated and allocated. Because composite video requires a very specific clock, setting that clock to the required speed on the Pi 4 means that other clocks connected to it are detrimentally affected, which slightly slows down the entire system. Since composite video is a less commonly used function, we decided to disable it by default to prevent this system slowdown.

1 Like
#101

Uploading: IMG_20201118_101326.jpg

This thing can go really wild

#102

Thanks! Let me know if you need any testing! I’ll keep hacking at it from my end. Either way, this is so much fun!

I’m also gonna try out a cheap HDMI -> NTSC converter and see how it does.

#103

Made some progress yesterday!! :slight_smile:

Running Norns output into Eyesy on Fates:

output

10 Likes
#104

More progress in dev-land:

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

:tada:

(getting the service to launch reliably on attached HDMI was a huge pain)

8 Likes
#105

Cheap HDMI to composite adapter works. The menu is unreadable, but that’s nbd if you are prepared for it.

#106

I’m having a hard time figuring out midi mapping. I can plug in my SQ-1 and get notes from channel 2 but not channel one. The clock comes through too. I want to map the controls to a 16n and an really lost on that. I’m running amidiauto.service is there a configuration file somewhere where I say this controls that?

#107

aconnect is what you’d use. It’s a bit arcane though - google for examples.

Amidiauto will just connect EVERYTHING.

1 Like
#108

Did you program your controller to send out the CC messages on the right channel ? In the shift params menu of Eyesy you can set the input midi channel. Other than that my controllers have been plug n play for me, pd handles the midi FWIW

1 Like
#109

Ahh. I’ll do more looking in that direction. Thank you!

@lcchy I think I missed that too. I’ll double check it. Thank you!

1 Like
#110

:slight_smile: thank you everyone ! :pray:
4 Likes
#111

I’ve had some time this weekend to test the updates on a clean fates , so here it is :slight_smile:

Update (19/12/20):

Thanks again to everyone who helped (@okyeron and the others), here are the features:

  • Run Norns with Eyesy in parallel, Norns sound into Eyesy
  • Control via a Touchosc Template
  • Readme Update
  • Many bugfixes and small improvements

Please be sure to have the latest Fates firmware version installed (or you won’t be able to run Eyesy and Norns in parallel)

If you had already installed it via the github instructions, you can update by running in one line (do not forget to backup your presets first!):
cd ~/sidekick/patches/Eyesy; git fetch; git reset --hard origin/master; ./deploy.sh

14 Likes
#113

i’ve done this, wasn’t it a long update?
seems that i don’t see eyesy in my available script on norns, via sidekick is still working

#114

hi there, with the update there should now be two options in the sidekick menu, one being “Eyesy” that works like before and one called “Eyesy Norns” which should start Norns with Eyesy in the background (outputting the video via hdmi) when selected. Please let me know if I didn’t understand your question correctly :slight_smile:

#116

Update
Norns eyesy is showing up, seems fine for the norns part, but i can’t control eyesy via touch osc (all set as written in github
 Dunno)
The screen is detected as i can see the lighting bolt in the corner
 But nothing else.
I tried running the “standard” eyesy and is not working properly. As my fates boot up i see the eyesy booting up on the screen but controls dont work. And the fates screen is showing this

IMG_20210118_205124
IMG_20210118_2051242988×5312 1.34 MB

In both cases the screen is black. I know how eyesy work as the previous version worked for me.
I can access via a web browser the editor, seems ok i assume.
What can i do? I can’t use a midi controller right now so i cant test that
 Should i uninstall all and try again?

#117

you might try to update norns to the most recent version - which includes something for how the screens interact.

It’s possible you may need to edit the /boot/cmdline.txt file to change the framebuffer console to fbcon=map:2 (I have this on my pi4 install).