opus metadata

[s***@posteo.se]

Hi there!

I'm currently taking a look at this new fancy audio codec and I'm wondering how I have to set the tags so cmus reads them properly. For this I looked into the manpage of opusenc and found the link to http://www.xiph.org/vorbis/doc/v-comment.html. So I set it up accordingly, but cmus doesn't show the track number, no matter what I name it.

My script flac2opus is attached. Note: I chose to name all comments with lowercase letters, because that's what --artist and --title do as well, as you can see with opusinfo. But cmus also shows these tags if they are e.g. uppercase.

Can someone give me a hint?

Best
sekret

[mhca12]

Post by s***@posteo.se
Hi there!
I'm currently taking a look at this new fancy audio codec and I'm
wondering how I have to set the tags so cmus reads them properly. For this
I looked into the manpage of opusenc and found the link to
http://www.xiph.org/vorbis/doc/v-comment.html. So I set it up
accordingly, but cmus doesn't show the track number, no matter what I name
it.
My script flac2opus is attached. Note: I chose to name all comments with
lowercase letters, because that's what --artist and --title do as well, as
you can see with opusinfo. But cmus also shows these tags if they are e.g.
uppercase.
Can someone give me a hint?

I may be wrong but I remember that right now you have only two choices.
Either you set the tags when running opusenc or use oggz-comment built
from git https://www.xiph.org/oggz/
https://git.xiph.org/?p=liboggz.git;a=summary

[sekret]

Post by s***@posteo.se
Hi there!
I'm currently taking a look at this new fancy audio codec and I'm wondering how I have to set the tags so cmus reads them properly. For this I looked into the manpage of opusenc and found the link to http://www.xiph.org/vorbis/doc/v-comment.html. So I set it up accordingly, but cmus doesn't show the track number, no matter what I name it.
My script flac2opus is attached. Note: I chose to name all comments with lowercase letters, because that's what --artist and --title do as well, as you can see with opusinfo. But cmus also shows these tags if they are e.g. uppercase.
Can someone give me a hint?
Best
sekret

I just realized, that I forgot to attach the script. Sorry!

[sekret]

Ok, it kinda looks like I was wrong, today I wanted to look into it again and now it works perfectly. I'm not entirely sure what has changed..

Post by sekret

Post by s***@posteo.se
Hi there!
I'm currently taking a look at this new fancy audio codec and I'm wondering how I have to set the tags so cmus reads them properly. For this I looked into the manpage of opusenc and found the link to http://www.xiph.org/vorbis/doc/v-comment.html. So I set it up accordingly, but cmus doesn't show the track number, no matter what I name it.
My script flac2opus is attached. Note: I chose to name all comments with lowercase letters, because that's what --artist and --title do as well, as you can see with opusinfo. But cmus also shows these tags if they are e.g. uppercase.
Can someone give me a hint?
Best
sekret

I just realized, that I forgot to attach the script. Sorry!
#!/bin/bash
encopts="--bitrate 128.0"
for a in *.flac
do
ARTIST="$(metaflac "$a" --show-tag=ARTIST | sed s/.*=//g)"
ALBUM="$(metaflac "$a" --show-tag=ALBUM | sed s/.*=//g)"
TITLE="$(metaflac "$a" --show-tag=TITLE | sed s/.*=//g)"
TRACKNUMBER="$(metaflac "$a" --show-tag=TRACKNUMBER | sed s/.*=//g)"
GENRE="$(metaflac "$a" --show-tag=GENRE | sed s/.*=//g)"
DATE="$(metaflac "$a" --show-tag=DATE | sed s/.*=//g)"
flac -c -d "$a" | opusenc --artist "$ARTIST" --comment "album=$ALBUM" --title "$TITLE" --comment "tracknumber=$TRACKNUMBER" --comment "genre=$GENRE" --comment "date=$DATE" $encopts - "$TRACKNUMBER $TITLE".opus
done
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk

[mhca12]

Cool.


Relatedly does anyone know of a small player supporting opus efficiently
with hardware support like vorbis?

Post by sekret
Ok, it kinda looks like I was wrong, today I wanted to look into it again
and now it works perfectly. I'm not entirely sure what has changed..

Post by sekret

Post by s***@posteo.se
Hi there!
I'm currently taking a look at this new fancy audio codec and I'm

wondering how I have to set the tags so cmus reads them properly. For this
I looked into the manpage of opusenc and found the link to
http://www.xiph.org/vorbis/doc/v-comment.html. So I set it up
accordingly, but cmus doesn't show the track number, no matter what I name
it.

Post by sekret

Post by s***@posteo.se
My script flac2opus is attached. Note: I chose to name all comments

with lowercase letters, because that's what --artist and --title do as
well, as you can see with opusinfo. But cmus also shows these tags if they
are e.g. uppercase.

Post by sekret

Post by s***@posteo.se
Can someone give me a hint?
Best
sekret

I just realized, that I forgot to attach the script. Sorry!
#!/bin/bash
encopts="--bitrate 128.0"
for a in *.flac
do
ARTIST="$(metaflac "$a" --show-tag=ARTIST | sed s/.*=//g)"
ALBUM="$(metaflac "$a" --show-tag=ALBUM | sed s/.*=//g)"
TITLE="$(metaflac "$a" --show-tag=TITLE | sed s/.*=//g)"
TRACKNUMBER="$(metaflac "$a" --show-tag=TRACKNUMBER | sed s/.*=//g)"
GENRE="$(metaflac "$a" --show-tag=GENRE | sed s/.*=//g)"
DATE="$(metaflac "$a" --show-tag=DATE | sed s/.*=//g)"
flac -c -d "$a" | opusenc --artist "$ARTIST" --comment

"album=$ALBUM" --title "$TITLE" --comment "tracknumber=$TRACKNUMBER"
--comment "genre=$GENRE" --comment "date=$DATE" $encopts - "$TRACKNUMBER
$TITLE".opus

Post by sekret
done

------------------------------------------------------------------------------

Post by sekret
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!

http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk