shellrhythm / shellrhythm-cli Goto Github PK

I get the following error when attempting to install on my Mac (2020 Pro M1):

OSError: dlopen(./libbass.so, 0x000A): tried: '/opt/homebrew/Caskroom/miniforge/base/lib/./libbass.so' (no such file), '/opt/homebrew/Caskroom/miniforge/base/lib/./libbass.so' (no such file), '/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/lib-dynload/../.././libbass.so' (no such file), '/opt/homebrew/Caskroom/miniforge/base/lib/./libbass.so' (no such file), '/opt/homebrew/Caskroom/miniforge/base/bin/../lib/./libbass.so' (no such file), './libbass.so' (no such file), '/Users/sysadmin/shellrhythm/libbass.so' (no such file)

Any idea how to fix it?

now, i could make these all into their own separate little threads, but

1. many of these are quite small by themselves
2. are all related to the editor and (mostly) its ease of use
3. this isn't that professional (yet) anyways

that being said,

Thego124's list of nitpicks and problems:

bugs/problems (in order of perceived difficulty):

1. metronome seems to use clap.wav
2. editor doesn't have a lower resolution bound afaik
3. white notes don't get inverted on the timeline when selected, like how other colors do
4. song continues playing after exiting from song's offset calibration menu, plays alongside menu music / editor preview
5. ctrl+space (needs a different keybind) (playback from start) doesn't work for me

nitpicks and wants (in order of importance):

1. auto-select on creating new note
2. in-editor way to change song difficulty and approach rate
3. softer hit sound (being worked on)
4. given the visual constraints, multiple tracks/timelines seems like a bad idea, but there should be at least some marcation for when there are multiple notes on the same beat (# instead of a letter?)
5. either:
   * ability to select and edit multiple notes at once
   * or commands for selecting and editing notes, which might be more reasonable
   (repeatedly pressing [down]; e; x; [esc] to change the color of a bunch of notes gets tiring quickly, especially when wanting one of the later colors) (new commands done)
6. actually, x and c don't do anything by themselves afaik, why do you need to press e before them anyways?
7. on-screen cheat sheet (maybe even a changing one if you do program the previous one in, so it shows different notes depending on what's selected)
8. duplicate note: press a button, copies the selected note onto the same pos. and time, and selects it ( as per 1) )
9. better made chart data files: sometimes, you need to edit them manually, which means it's annoying when it's all one line

Doing pip install -r requirements.txt fails the moment it wants to install anything in particular related to either blessed or term-image.

Workaround:

• Go into the folder where python is located.
  • In this case i'm using MSYS to host Python in my computer as a whole, so my solution was to go into ".../lib/python3.10" in the Terminal and do pip install term-image and pip install blessed.
  • This solution works perfectly and once it opens up it runs 100%

Recommendation:

• Make a python installer script that sets the main path to ".../lib/python3.10" via "cd" or something similar and run pip from there.

While loading, before the main menu shows up, if you resize it to a small size can cause the entire terminal to crash on you.

Screenshot taken a second after it crashes:

When accessing the Metadata, the list doesn't round up and tries to access unknown options if you continue going down.

Pressing Enter in this stage causes an index out of range error, resulting a crash:

Basically, beatsound plays for hit object 1, well it can decide to not play for hit object 2 if the delay between these two hit objects is too short

I am working on a fix, I'm just putting this here so people know i am already aware of that issue

sincerely apologising for this issue in the meantime 😅

Adding the "Space" Key as a Note causes this error:

Resizing the terminal can cause these kinds of issues.

This gets fixed when it goes from one entire window to another.

The installer echoes that the installation was successful without even checking if anything went wrong. For example, pip had trouble installing stuff on my Arch system, but the installer still echoed that the installation was successful. Also, I don't think using shellrhythm in terminal seems to work.

This is optional but using a requirements.txt file for installation of deps will be easier for the end user and will save time, offering the control of the version you wanna use.
So instead of doing pip install . . . . ., you can just do pip install requirements.txt and everything is ready.
It would be a nice addition.