I am currently looking into getting a keyboard to use in jamming sessions. I have so far been partial to Roland GO:KEYS 5 (this over the 3 due to the additional inputs and an acceptable imo price difference). This (around 500 EUR) is around the max I want to give for it.

But, as far as I can tell, it does not have a proper loop function. It has a layered recording-function, but this would require me to play through the full song.

So I have two questions:

  1. Are there any keyboards anyone of you would recommend in roughly the same price range that has a looper?

  2. Could I use my Boss RC-5 for this, plug the keyboard into input A and plug it back into the keyboard from output A? I would like to avoid buying a new speaker for this, and tge loop pedal would also be connected to my guitar and to the amp.

  • cyberwolfie@lemmy.mlOP
    link
    fedilink
    arrow-up
    2
    ·
    6 days ago

    I want to go FOSS, so I’ve tried LMMS and Ardour, both only briefly. Found out that Ardour is probably more what I am going for as I want to connect a guitar directly and record as well, and as far as I could tell, I would have to make guitar recordings outside of LMMS and bring them in after.

    I spent a little time trying to get my piano, guitar and MIDI-controller set up with Ardour, which I almost got working (just the control buttons on the MIDI controller (Nektar Impact LX25+) that I couldn’t get any response from). I struggled with plugins though, tried yabridge, couldn’t get it to work, and figured it was because I was running the flatpak version of Ardour. So I am planning on buying the precompiled binaries from Ardour to also support development, but I want to wait until I have some time to get properly going. My mistake might also have been to bite off a bit more than I could chew from the get-go, and that I should start by following some tutorials to get to know the software better before I start interfacing everything.

    • trashcan@sh.itjust.worksM
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      6 days ago

      My mistake might also have been to bite off a bit more than I could chew from the get-go, and that I should start by following some tutorials to get to know the software better before I start interfacing everything.

      That could be it. Don’t forget limitations lead to creativity.

      I went with Bitwig because it’s natively Linux compatible, supports 32-bit and 64-bit VST2, VST3, and CLAP plugins with multiple sandboxing options making a plugin crash a nonissue.

      A DAW may be the one thing I am willing to go for proprietary. It’s the most expensive software I have purchased for hobbyist use and it’s rewarding every time I open it. I went with the simplicity of having things “just work” for once.

      But that said with all the options I do get lost in rabbit holes and would probably finish more tracks with fewer choices.