Subject: infinity songs

From: ilm
Date: Wed Jun 14 12:14:45 2006

To: UADE-User-discussion
i'm in the process of converting songs to wave/mp3, but ran into some trouble with 'inifinity' subsongs (with uade123)

i could use
- (sub)song timeout: problem is i dont want 180 secs of a repeating sound effect
- silence timeout: if there isn't even 1 second silence i have a problem :)

so ideas i had:
- a flag so i know it it's infinite
- or extend -g to give info about the subsongs (length), so i can parse it with a bash script and see which songs are 'infinite' (&gt;512s)
- some other solution which i dont know ?

just some suggestions, i can even try to do it myself

---

From: ilm
Date: Fri Jun 16 16:03:13 2006

To: UADE-User-discussion
hmm, let me rephrase my question:

is there a way to see the length of a subsong,
(or -1 if length &gt; X seconds)

i tried the -g option but it doesn't give full detail on the subsongs

any ideas ?

(better ? :) )

---

From: shd
Date: Sat Jun 17 20:58:53 2006

To: UADE-User-discussion
[quote:9e073a84e1="ilm"]is there a way to see the length of a subsong,
(or -1 if length &gt; X seconds)
[/quote:9e073a84e1]

Only by playing the song fully or looking up the database.

[code:1:9e073a84e1]uade123 -f /dev/null song 2&gt;&amp;1 |grep magic |parse length
[/code:1:9e073a84e1]

Need more help? Database lookup is much faster, if the entry is available (~/.uade2/contentdb)

[quote:9e073a84e1]i tried the -g option but it doesn't give full detail on the subsongs
[/quote:9e073a84e1]

-g only gives the number of subsongs. The length can not be known in advance. One could get the length from the database, but it's the total length, not a per subsong length.

---

From: shd
Date: Sat Jun 17 21:00:27 2006

To: UADE-User-discussion
[quote:01d2572e49="shd"]Only by playing the song fully or looking up the database.
[/quote:01d2572e49]

But, for many formats the subsong length can not be known at all because the eagleplayer (usually custom) doesn't report song end at all.

---

From: ilm
Date: Sun Jun 18 13:28:14 2006

To: UADE-User-discussion
fist thanks for the reply, got some more questions though

[quote:d665cd075b]But, for many formats the subsong length can not be known at all because the eagleplayer (usually custom) doesn't report song end at all.[/quote:d665cd075b]

yes, i'm aware of that, i'm satisfied when i know it is longer than X seconds (ie 512 s)

so i could parse the stdout/stderr of uade123, not really a proper way cause uade123 prints the song position hundred of times :) (but that's k)

or get my information from contentdb, unfortunately it's empty ? when does a song get added to it ? tried playing some simple protracker mods, also with -g but to no avail. contentdb stays empty

[quote:d665cd075b]Need more help? Database lookup is much faster, if the entry is available (~/.uade2/contentdb)
[/quote:d665cd075b]

if i get this right, contentdb is the way to go (cleaner than my 1st option) but it isn't certain that every song gets recorded into it ? based on what ?

sorry if this information is available somewhere, didn't find it then

---

From: shd
Date: Sun Jun 18 13:34:07 2006

To: UADE-User-discussion
[quote:e3b761264b="ilm"]so i could parse the stdout/stderr of uade123, not really a proper way cause uade123 prints the song position hundred of times :)[/quote:e3b761264b]

Not a problem, just get the last one: uade123 ... |grep pattern |tail -n1 -&gt; you get one

[quote:e3b761264b]or get my information from contentdb, unfortunately it's empty ? when does a song get added to it ? tried playing some simple protracker mods, also with -g but to no avail. contentdb stays empty
[/quote:e3b761264b]

I just yesterday committed length saving feature into cvs version of uade123, it has been in the xmms plugin for a long time. The database is saved when uade123 quits if any chances were made.

[quote:e3b761264b]if i get this right, contentdb is the way to go (cleaner than my 1st option) but it isn't certain that every song gets recorded into it ? based on what ?[/quote:e3b761264b]

Basically the only general solution is to playback the whole song once so you have to invoke uade123. You might just as well parse the output text for song length rather than scanning contentdb afterwards.

[quote:e3b761264b]sorry if this information is available somewhere, didn't find it then[/quote:e3b761264b]

Not a problem, we have documented things scarcely. Feel free to contribute us documentation.

---

From: ilm
Date: Fri Jun 23 14:54:45 2006

To: UADE-User-discussion
like you said i might just go for the stdout parsing, as i have to play the song at least 1 time

or do both, check contentdb, if it ins't in it play song
it seems you identifies songs with md5sum (checked it), that's no problem in unix either.

thx for the answers

[quote:58c07af518]Not a problem, we have documented things scarcely. Feel free to contribute us documentation.[/quote:58c07af518]
i'm just do if i have time, except from contentdb i'd say most things are already in the manpages though