#beets

this is what i have for getting a year in my path.

you could probably just replace the initial if statement with if catalognum

does it matter if it is placed before or after

path:

default: etc

that's inside my path:

elGALLO: The order of config options shouldn't matter.

(IIRC.)

my defailt path default: $albumartist - %if{$release_year, ($release_year) $album} [$avgbitrate]/%if{$multidisc, Disc.$disc/}$track - $title

using 3 inline statements in there, release_year, avgbitrate, multidisk

The queries are tested in the order they appear in the configuration file, meaning that if an item matches multiple queries, beets will use the path format for the first matching query.

axion: But the position of the inline: config in relation to the path: config shouldn't matter, right?

That should not matter, no.

http://hastebin.com/rosacubero.bash cobra2

so if%[$string will only fill that spot IF theres a value?

what about only returning 24 FLAC for $bitdepth,

%if{$bitdepth = 16 return 0

elGALLO: https://beets.readthedocs.io/en/v1.4.1/referenc...

so %if{$bitdepth,24}

Will add "24" whenever $bitdepth is != 0.

One of my albums contain duplicates. filename.m4a and filename.1.m4a. They are the same size.

I'm trying to zap them with the duplicates plugin, but "beet duplicates" produces no output

are they the same track number?

darwin: yes

Hm, there should be a "beet diff file1 file2"... :)

one is probably not actually tracked by beets, etc.

How do I find out?

hm, I think they are, though

beet ls shows the duplicates

Fixed it with beet rm -f "path::.*\.1.m4a" for now

`beet diff` would be a neat plugin.

I guess it could be pretty simple in "just" getting the output of `beet list` or `beet info` and passing it through a diff Python module thing.

would it be a lot more useful than the log?

Mybe difflib?

ignore me, ofc it would be since it would include deletes and moves

polemic: How would the log be able to tell the difference between two (or more) files?

(Or are you replying to something different?)

oh... I thought you just meant diff between library

not files

my mistake

why does beet import -I /mnt/music/path/to/\[2006\]\ Some\ Album return: "error: no such file or directory: /mnt/music/path/to/[2006]"?

same thing happens if I put path in "s

but it works fine if I navigate to the album directory and do beet import -I .

take out the \s, put it in single quotes

single quotes? okay. Will try that. Thanks

double quotes tell the shell to be Clever, single quotes mean to take the enclosing text completely literally

gotcha

thank you :)

nope

still does it

I am probably showing myself to be a real noob, but when enclosed in 's beets still thinks that the path ends with the first space

so beet import '/path/to/2010 foo' returns "error: no such file or directory: /path/to/2010

are you typing the path or copy/pasting it

I suspect there might be a weird nonprintable character in there

typing it

this happens with any path with a space in it

as far as I can see

what platform are you on? mac, linux, windows?

linux

running beets in a debian-testing vm

and are you running a shell with tab-complete?

unless that is enabled by default, I do not think so.

h wait

oh wait, I understand your question, yes I am

and if you do ls /path/to etc and maniacally hit tab to complete it, does it work?

yes, but it uses \ to escape spaces etc

yes tab-complete does that

also works with ' and "

and ls

so if you get it to where you can ls the directory, and then hit up arrow for your shell history, and change ls to beet import, what happens?

errors mistaking the \ escaped space for the end of the input

you mind throwing the shell session into http://paste.debian.net/ ?

one sec, let me check how

copy and paste generally

I don't know what terminal you're using tho

what would you like me to paste?

the ls and the beet error

sure np

the key is I think there's something on the path that's important that's being overlooked

possibly the numbers?

yes, perhaps

I think it might be the -

wow!

that should be working!

when I try wrapping the \ escaped path but wrap it in 's beets errors with "error: no such option -\"

xarph is it possible that it's being on the client side of ssh?

*the problem is on

not if it's in the same session

did you try

'/mnt/music/2009\ -\ I\ Had\ the\ Blues\ But\ I\ Shook\ Them\ Loose/'

er

'/mnt/music/2009 - I Had the Blues But I Shook Them Loose/'

yup

single quoted, no \s?

yup, same error

same with "s too

I am running it in screen

if that matters?

that shouldn't matter

do beet import -v '/mnt/music/2009 - I Had the Blues But I Shook Them Loose/'

that does verbose output

so we can see if the path getting into beets is being mangled

standard stuff about loading plugins and library etc then: error: no such file or directory: /mnt/music/2009

I think for now you're gonna have to rename that directory to import it, unless one of the gurus here has an idea. The only thing left I can think of is if it's running in a weirdo shell or if it's in python3 and there's a python3 change that we haven't been aware of in terms of shell globbing

Python 2.7.12+

I just had an idea

nope, I thought it might be something to do with autocompletion, but turned it off and still remains

*beets autocompletion

the weird thing is

I just realized that my cron import scripts are working fine

so this must only happen in my shell

are you using bash, tcsh, zsh?

bash

may I pm you?

¯\_(ツ)_/¯

yeah, I suppose