[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#656884: picard: Can't use directories on 'File naming' Options



I think this issue should be closed. This was reported for a very old release and is definitely working in the 2.x releases.

If this should be still an issue for anyone this should be brought upstream.

Philipp

On Sun, 22 Jan 2012 16:48:36 +0000 =?utf-8?q?Lu=C3=ADs_Picciochi_Oliveira?= <Pitxyoki@Gmail.com> wrote:
> Package: picard
> Version: 0.16-1
> Severity: normal
>
> Hi,
>
> According to the picard documentation [1,2], it should be possible to define
> directories on the "File Naming" Options panel. Music files would then be moved
> to those directories according to the defined rules. However, when I define
> something like:
>
> %artist$/%tracknumber% - %title%
>
> The tracks get named only according to '%tracknumber% - %title%' and anything
> before the last slash is ignored.
> I used this feature in previous versions and it worked well. I only noticed
> this problem on this latest update (from 0.11-2.1 to 0.16-1).
>
> Best regards,
> Luís Picciochi Oliveira
>
>
> 1 - http://musicbrainz.org/doc/MusicBrainz_Picard/Documentation/Options
> 2 - http://musicbrainz.org/doc/MusicBrainz_Picard/Documentation/Scripting
>
>
>
> -- System Information:
> Debian Release: wheezy/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages picard depends on:
> ii  libavcodec53    4:0.7.3-2
> ii  libavformat53   4:0.7.3-2
> ii  libc6           2.13-24
> ii  libdiscid0      0.2.2-2
> ii  libfftw3-3      3.3-1
> ii  libgcc1         1:4.6.2-11
> ii  libofa0         0.9.3-4
> ii  libstdc++6      4.6.2-11
> ii  python          2.7.2-9
> ii  python-mutagen  1.20-1
> ii  python-qt4      4.9-2
> ii  python2.7       2.7.2-8
>
> picard recommends no packages.
>
> picard suggests no packages.
>
> -- no debconf information
>
>
>

Reply to: