I’m going to bulk rename the files and adjust my script accordingly. That seems
be the easiest way to go. Thanks for the input.
Sent from my iPad
> On Jul 11, 2021, at 1:00 AM, Robert Jeffares
> wrote:
>
>
> The audio filename is going to be xx_001.wav
>
> Artist and Title are stored
The audio filename is going to be xx_001.wav
Artist and Title are stored in MySQL [or MariaDB ] where [] are allowed
in strings.
--set-string-artist=should work with []" <--tested and it does
--set-string-title="same"
I just checked this on a copy of the same OS. If the *source audio
Square brackets are glob characters in file names (they're a regex list
indicator). Maybe try disabling file globbing? That disables all of the
file expansion characters. "set -f" to turn off, "set +f" to turn back on.
Mike
On Sat, Jul 10, 2021 at 10:17 AM Dave wrote:
> rdimport will
rdimport will successfully import these files using the form rdimport
[options] [GROUP] *.flac
I can only think that the brackets are being interpreted by the script
in some way and sending bad information to rdimport.
On 7/9/2021 9:46 PM, Robert Jeffares wrote:
Hi Dave,
have you tried
I'm using the full file names because I'm also setting the talk and segue markers and scheduler codes, etc via the script. The files do contain metadata but for some reason rdimport doesn't always read the artist field. I'll try importing some files using wildcards in the filespec (*.flac) and
Hi Dave,
have you tried rdimport [options] [GROUP] *.flac ?
or is it falling down in the --metadata-pattern='%a - %t.flac'
Are you using CentOS or something else?
Do the flac files have metadata?
From memory [] brackets are not usually a problem
regards
Robert
On 10/07/21 7:03 am,
Hi all,
I'm about to use rdimport to import a couple of music libraries into
Rivendell via a shell script. In testing it works great except for the
fact rdimport does not like file names containing an open bracket ([).
For example, if I enter the file name using a double quote as "'N Sync -
