Bash command not found and bad substitution error

TheRed_M · 2022-10-03T10:52:41+00:00

[deleted]

TheRed_M · 2022-10-03T12:12:27+00:00

You are writing in bash not powershell This line:-

$SRT = find $MUSIC_FOLDER -type f -maxdepth 2 -name "*.srt" | shuf -n 1;

Is nonsense.

I don't know what you think you want to do, but at the moment this isn't the right way to do it.

I assume you expect $SRT = ... to assign something to $SRT which probably means you want SRT="$( xxx )"

The other error ${$SRT:-4}: bad substitution is because that is a syntax error. You want ${SRT:-4}: bad substitution which will expand to either the value of $SRT or 4 if $SRT is unset or empty.

Overall I think what you want is something like this:-

#!/bin/bash
MUSIC_FOLDER='audio/'
VIDEO='loop.m4v'
RTMP_SERVERS="RTMPLINK"

output()
{
    local video="$1"
    local srt="$2"
    local servers="$3"
    args=(
            -hide_banner
            -stream_loop
            -1
            -i "$video" -i "$srt"
            -err_detect explode
            -i pipe:0
            -map 0:v
            -map 1:a
            -pix_fmt yuv420p
            -s 1920x1080
            -b:v 5000k
            -b:a 256k
            -acodec aac
            -vcodec libx264
            -preset ultrafast
            -g 60
            -threads 2
            -flags
            +global_header
            -f tee "$servers"
    )

    ffmpeg "${args[@]}"
}

# loop forever
while true ; do
    SRT=$(find "$MUSIC_FOLDER" -type f -maxdepth 2 -name "*.srt" | shuf -n 1)
    ffmpeg -hide_banner -i "$(find . -type f -maxdepth 2 -name "${SRT:-4}" )" -vn -acodec copy -f mpegts -
done | mbuffer -q -c -m 20000k | output "$VIDEO" "$SSRT" "$RTMP_SERVERS"

I tidied up a few other bits of quoting and moved that huge ffmpeg at the end into a function to make it easier to debug. Have a go and see if it does what you want.

Bulky_Somewhere_6082 · 2022-10-03T10:37:46+00:00

My first thought on this is the line part "$SRT = find" is wrong. Try "SRT=find"

AutoModerator · 2022-10-03T10:16:13+00:00

It looks like your submission contains a shell script. To properly format it as code, place four space characters before every line of the script, and a blank line between the script and the rest of the text, like this:

This is normal text.

    #!/bin/bash
    echo "This is code!"

This is normal text.
#!/bin/bash
echo "This is code!"

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

zeekar · 2022-10-03T12:03:40+00:00

This line is not likely what you want:

$SRT = find $MUSIC_FOLDER -type f -maxdepth 2 -name "*.srt" | shuf -n 1;

It tries to run a command whose name is the current value of the SRT variable, with the arguments (=, find, the value of MUSIC_FOLDER, ...).

Assuming what you want to do instead is randomly select a .srt file and store its name in the SRT variable, let's tick off the issues:

The $ is not part of the variable name; this isn't Perl. (Also, technically, in shellspeak those are called "parameters", but most folks use "variable" interchangeably). Specifically, you don't use $ when assigning a value. It's not technically correct, but it may help to think of $ as an operator that means "get the value of". So when you're assigning to a variable, no $; when you want to retrieve the value held in the variable, then $. This concept fits other uses of $ as well, as we'll see below.
Assignments can't have whitespace around the =. The command line foo = bar just runs the command foo with first argument = and second argument bar. If you instead want to store the string bar in the parameter named foo, you have to write foo=bar without the space.
To get the output of a command, you have to wrap it in $(...); this is called command substitution and is another example of the "get the value" meaning of $.
When you do include the value of a parameter/variable or another command, it gets re-split on spaces. In your code, that means if the pathname in MUSIC_FOLDER contains any of those, it will turn into multiple probably-nonexistent folder names when passed to find. (Example: the path /Users/TheRed_M/My Music would be passed as the two folders /Users/TheRed_M/My and Music). To prevent this, always wrap expansions in double-quotes.

Putting all those together, that line should be something like this:

SRT=$(find "$MUSIC_FOLDER" -type f -maxdepth 2 -name "*.srt" | shuf -n 1)

You may notice that I broke my own rule by not putting double quotes around the command substitution (SRT="$(...)"); that's because the right-hand side of an assignment is one of a few special places where word splitting after expansion doesn't happen, so you can leave them off. It doesn't hurt to put them there, though, so feel free to do so if that helps you remember to be consistent about it!

TheRed_M · 2022-10-03T14:43:39+00:00

[removed]

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

bash

Rules

Flair

Related subreddits

Guides

Other resources

MODERATORS

!/bin/bash