Can not change any tags in audio (ALAC) .m4a file

Bug #511768 reported by jimav
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
atomicparsley (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: atomicparsley

None of the tag-setting options, such as --title, seem to work on MP4 files containing only audio.
Using package atomicparsley version 0.9.0-0ubuntu3

AtomicParsley outputs several screen-fulls of "Progress:" lines and then says "Finished writing to temp file.",
and then exits. The file specified on the command line is not modified.

The files I'm trying to add tags to were created using ffmpeg -acoded alac
I will attach a test script.

Following is the output from the test script; note that after running AtomicParsley test.m4a --title NewTitle
there are no new tags added and the file's modification time did not change:

+ : Create an MP4 file containing an alac-encoded audio track (reads "test.wav")
+ ffmpeg -i test.wav -acodec alac -track 1 test.m4a

+ : Set the modification time to be very old, to help detect if it changes
+ touch -t 7101010000 test.m4a
+ ls -l test.m4a test.wav
-rw-r--r-- 1 jima jima 1149084 1971-01-01 00:00 test.m4a
-rw-r--r-- 1 jima jima 2305592 2010-01-23 18:17 test.wav

+ : Show existing tags
+ AtomicParsley test.m4a -t
Atom "©too" contains: Lavf52.31.0
Atom "trkn" contains: 1

+ : Try to add a tag using AtomicParsley
+ AtomicParsley test.m4a --title MyNewTitle

 Started writing to temp file.
 Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: >0%------------------------------------------------------------------ Progress: ==================================>45%------------------------------- Progress: ===================================================================>8 Progress: ===========================================================================>100%|
 Finished writing to temp file.

+ : See if anything changed (it didn't; note time stamp did not change either)
+ AtomicParsley test.m4a -t
Atom "©too" contains: Lavf52.31.0
Atom "trkn" contains: 1
+ ls -l test.m4a
-rw-r--r-- 1 jima jima 1149084 1971-01-01 00:00 test.m4a
+ date
Sat Jan 23 18:22:08 PST 2010

ProblemType: Bug
Architecture: amd64
Date: Sat Jan 23 17:46:57 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: atomicparsley 0.9.0-0ubuntu3
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: atomicparsley
Uname: Linux 2.6.31-17-generic x86_64

Revision history for this message
jimav (james-avera) wrote :
Revision history for this message
jimav (james-avera) wrote :
Revision history for this message
jimav (james-avera) wrote :
Revision history for this message
jimav (james-avera) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.