Getting experimental FeedForward editor to work

Hello @yaxu, that was the problem… I use Fedora/Gnome desktop and the terminal preferences (accessible from the menu at the top left of the screen) have “Enable the menu accelerator key (F10 by default)” ticked. Deselecting this makes the application work as expected (F10 to Quit).

1 Like

There is a hack that can be used in certain terminal programs to emulate ctrl-enter and shift-enter. I use this to emulate Atom's behavior with tidal-vim.

See vim - How to map Shift-Enter - Stack Overflow for more details.

1 Like

Hi :wink: i'm trying to follow the installation procedure stated in the GitHub page but i'm not able to find the ~/.cabal/bin folder.
Sorry but i'm a bit inexpertise doing this kind of stuff, but i think that the feedforward functionalities are awesome and instructive for the beginners !!
I'm on Ubuntu 20.04 with Tidal 1.5.4

Thanks a lot :wink:

That's strange. Can you share the output of the cabal install command?

Of course :wink: here the output. Thanks Alex

You'll need to be inside the feedforward folder before running cabal install

Ohhh sorry :wink: here the output from the feedforward folder, after running the cabal install .

Hm, howabout cabal install c2hs first?

unfortunately,

it gives me the same error. I also try to do a cabal update and then the other command but nothing change. The same result with the sudo privilege :slight_smile:

Ok, try cabal install happy alex before that, (believe it or not)

Is someone who's installed on mac os x able to contribute step-by-step install instructions?

1 Like

working on it now.

I may already have ncurses installed, but will suggest how to install it in macos assuming I can get everything running.

EDIT: it installed easily on macOS Mojave 10.14.6. The only quirk is my Backspace key isn't recognized. Otherwise I can type stuff in the buffer and it seems to work.

EDIT: PR submitted with install instructions

1 Like

I guess a no-delete live coding performance is the opposite of a no-input mixer performance

4 Likes

Any idea what this build issue could be caused by?

1 Like

Ah looks like that's my fault, feedforward needs updating for the latest tidal, will have a look over the weekend..

I've just pushed a change, so that it should run at least..

2 Likes

When I run both cabal install happy alex and cabal install c2hs I get this error:

Warning: could not create a symlink in /home/hellocatfood/.cabal/bin for c2hs
because the file exists there already but is not managed by cabal. You can
create a symlink for this executable manually if you wish. The executable file
has been installed at /home/hellocatfood/.cabal/bin/c2hs

I don't know if this is a showstopper or not.

When I eventually run ~/.cabal/bin/feedforward 2> err.txt Supercollider says too many users. The full error is:

full error details
SuperDirt: listening to Tidal on port 57120
NODE TREE Group 0
   1 group
      13 group
      1059 dirt_delay2
      1058 dirt_reverb2
      1057 dirt_leslie2
      1056 dirt_rms2
      1055 dirt_monitor2
      12 group
      1054 dirt_delay2
      1053 dirt_reverb2
      1052 dirt_leslie2
      1051 dirt_rms2
      1050 dirt_monitor2
      11 group
      1049 dirt_delay2
      1048 dirt_reverb2
      1047 dirt_leslie2
      1046 dirt_rms2
      1045 dirt_monitor2
      10 group
      1044 dirt_delay2
      1043 dirt_reverb2
      1042 dirt_leslie2
      1041 dirt_rms2
      1040 dirt_monitor2
      9 group
      1039 dirt_delay2
      1038 dirt_reverb2
      1037 dirt_leslie2
      1036 dirt_rms2
      1035 dirt_monitor2
      8 group
      1034 dirt_delay2
      1033 dirt_reverb2
      1032 dirt_leslie2
      1031 dirt_rms2
      1030 dirt_monitor2
      7 group
      1029 dirt_delay2
      1028 dirt_reverb2
      1027 dirt_leslie2
      1026 dirt_rms2
      1025 dirt_monitor2
      6 group
      1024 dirt_delay2
      1023 dirt_reverb2
      1022 dirt_leslie2
      1021 dirt_rms2
      1020 dirt_monitor2
      5 group
      1019 dirt_delay2
      1018 dirt_reverb2
      1017 dirt_leslie2
      1016 dirt_rms2
      1015 dirt_monitor2
      4 group
      1014 dirt_delay2
      1013 dirt_reverb2
      1012 dirt_leslie2
      1011 dirt_rms2
      1010 dirt_monitor2
      3 group
      1009 dirt_delay2
      1008 dirt_reverb2
      1007 dirt_leslie2
      1006 dirt_rms2
      1005 dirt_monitor2
      2 group
      1004 dirt_delay2
      1003 dirt_reverb2
      1002 dirt_leslie2
      1001 dirt_rms2
      1000 dirt_monitor2
too many users

This text will be hidden

I get that 'error' too, it doesn't seem to cause any problems at all. I think it's just put there to confuse us.

It looks like you're nearly there! To fix the too many users error, run something like this before starting superdirt:

s.options.maxLogins = 8;

I'm running ffw in an ubuntu linux terminal. Everything is working great except that on every execute it dumps a lot of information in to the screen. I can clear it with ctrl-l but have to do that every time I evaluate tidal pattern. Still managing to have fun anyway so :slight_smile:

@squim There's a note about that in the README:

Usage

At the moment it sends a lot of info to stderr, which you'll need to direct somewhere, e.g. by running like this:

feedforward 2> err.txt

1 Like