Multiple Metadata shown in Songhistory

[bluetwang]

Hi

I'm new in using Mixxx. I plan to send in a German Internet Radio Station. Most of the guys there are using SAM. I prefer Mixxx and I'm really happy with it. But there is a problem where I need your help.

The station is using shoutcast and a streambox generatet by http://www.ak-webdesign.net/service/sb_generator.htm . There is also a song history shown based on http://www.ak-webdesign.net/service/sh_generator.htm . Here I have the problem. There are always multiple entries of Artist and Songtitle in the list. Most of the time there are more than 10 entries of the same track. For me it looks like Mixxx is sending the information permanently out.
The guys using SAM do not have this problem. There it works fine.

Do you have an idea would I could do, to get this issue solved?

I'm using Windows7 and Mixxx 1.10.0 (build r3034)

Stefan

[Pegasus]

SOunds like a bug. Can you possibly collect more information and file a bug?

[bluetwang]

Thanks for the reply

What kind of information is needed? What is of help for you?

Stefan

[Pegasus]

Your OS, Mixxx version, streaming server type and version, and description of the problem. (You have most of that above already.) Just put it into a bug in our tracker ( https://bugs.launchpad.net/mixxx/ ) so we don't forget to take a look at it.

[Covenant]

Hi, same problem here.

I've installed Mixxx 1.10.1 installed from http://ppa.launchpad.net/mixxx/mixxx/ubuntu on a Ubuntu 12.04 64bit desktop system
SHOUTcast Server v2.0.0.29/posix(linux x86) runs on a Ubuntu 12.04 32bit server system in a VM on the above PC.
I'm listening to the stream with an IP radio.

I think this Bug #986981 is connected to Bug #1003403.

When trying to login to the transcoder with the credentials given in the sc_trans.conf, Mixxx isn't able to login. Error is wrong user or password.
When using the source login (like the transponder), Mixxx says "successfully logged in", but then in the song history every 5 seconds the songtitle of the song played in Mixxx appears over and over again. Though the song played in Mixxx is displayed as current song, listeners will still hear the playlist streamed by the transcoder, if it was running when starting Mixxx and logging in.

The problem seems to me that the login works in Shoutcast 1 mode. Don't know what may be the difference, but there seems to be one between Shoutcast 1 and 2, though there is no difference between Shoutcast 1 or 2 in the dropdown (as is for Icecast)

When starting the server and transcoder to play a playlist, the Shoutcast log says the following:

Code: Select all

2012-09-19 16:42:44   I   msg:[SRC 127.0.0.1:38438] SHOUTcast 2 source connection.
2012-09-19 16:42:44   I   msg:[SRC 127.0.0.1:38438] Password accepted. Stream id is 1
2012-09-19 16:42:45   I   msg:[SRC 127.0.0.1:38438 sid=1] stream configuration complete. [
type=SHOUTcast 2
mimeType=audio/mpeg
maxPayloadSize=16377
avgBitrate=128000
maxBitrate=128000
desiredBufferSize=320
minimumBufferSize=0
icyName=Covenant.FM
icyGenre=Metal
icyURL=http://www.lylesburg.de
icyPub=1
]
2012-09-19 16:42:45   I   msg:[SRC 127.0.0.1:38438 sid=1] Got complete metadata message type=3902 [566 bytes] id=1 span=1 content=
<?xml version="1.0" encoding="UTF-8" ?>
<metadata>
<COMM></COMM>
<TALB>Rock Songs CD 2</TALB>
<TCON v1="4294967295"></TCON>
<TENC>TRANSCast DNAS/posix(linux x86) v2.0.0.54</TENC>
<TIT2>Spinning Wheel</TIT2>
<TPE1>Blood, Sweat &amp; Tears</TPE1>
<TYER>1999</TYER>
<extension>
   <title seq="1">Blood, Sweat &amp; Tears - Spinning Wheel</title>
   <title seq="2">Europe - The Final Countdown</title>
   <title seq="3">Mott The Hoople - All The Young Dudes</title>
   <title seq="4">Heart - Barracuda</title>
   <soon>Europe - The Final Countdown</soon>
</extension>
</metadata>


When logging in from Mixxx and trying to stream, the log looks like this:

Code: Select all

2012-09-19 17:05:56   I   msg:[SRC 192.168.123.1:46636 sid=1] SHOUTcast 1 source connection.
2012-09-19 17:05:56   E   msg:[SRC 192.168.123.1:46636 sid=1] connection rejected. Bad icy header string [icy-name:]
2012-09-19 17:05:57   I   msg:[ADMINCGI] Title update [Abattoir - Screams From The Grave]
2012-09-19 17:06:01   I   msg:[SRC 192.168.123.1:46641 sid=1] SHOUTcast 1 source connection.
2012-09-19 17:06:01   E   msg:[SRC 192.168.123.1:46641 sid=1] connection rejected. Bad icy header string [icy-name:]
2012-09-19 17:06:02   I   msg:[ADMINCGI] Title update [Abattoir - Screams From The Grave]
2012-09-19 17:06:06   I   msg:[SRC 192.168.123.1:46646 sid=1] SHOUTcast 1 source connection.
2012-09-19 17:06:06   E   msg:[SRC 192.168.123.1:46646 sid=1] connection rejected. Bad icy header string [icy-name:]
2012-09-19 17:06:07   I   msg:[ADMINCGI] Title update [Abattoir - Screams From The Grave]
2012-09-19 17:06:10   I   msg:[SRC 192.168.123.1:46648 sid=1] SHOUTcast 1 source connection.
2012-09-19 17:06:10   E   msg:[SRC 192.168.123.1:46648 sid=1] connection rejected. Bad icy header string [icy-name:]
2012-09-19 17:06:11   I   msg:[ADMINCGI] Title update [Abattoir - Screams From The Grave]
2012-09-19 17:06:15   I   msg:[SRC 127.0.0.1:38438 sid=1] Got complete metadata message type=3902 [542 bytes] id=1 span=1 content=
<?xml version="1.0" encoding="UTF-8" ?>
<metadata>
<COMM></COMM>
<TALB>Rock Songs CD 1</TALB>
<TCON v1="4294967295"></TCON>
<TENC>TRANSCast DNAS/posix(linux x86) v2.0.0.54</TENC>
<TIT2>Black Betty</TIT2>
<TPE1>Ram Jam</TPE1>
<TYER>1999</TYER>
<extension>
   <title seq="1">Ram Jam - Black Betty</title>
   <title seq="2">Journey - Wheel In The Sky</title>
   <title seq="3">Firehouse - Don&apos;t Treat Me Bad</title>
   <title seq="4">Bob Dylan - Subterranean Homesick Blues</title>
   <soon>Journey - Wheel In The Sky</soon>
</extension>
</metadata>

So the connection isn't done right, the server still plays the playlist from the transcoder but updates the playlist every couple of seconds.
The Sam users log in into the transcoder, which is correctly logged in at the server.
So somehow to me it looks as if you have to implement two different methods for a login at shoutcast 1 and 2.

Greetings
(another) Stefan

[Covenant]

Did some more experiments with the login and watching the sc_trans.log

i have in my sc_trans.conf:

Code: Select all

djport=9002
djport2=9004
djlogin_1=mydjname
djpassword_1=mysecret


When I try to log into the transcoder as a V2 source, using 9004 as port, mydjname as loginname and mysecret as password, sc_trans.log shows no entry at all. No error or warning, just as if I did not try to connect.
When trying a V1 login using 9002 as port and putting mydjname and mypassword each into it's own inputbox, then the log shows an error "recieved password is in wrong format". This seems to be the correct behaviour.
Trying V1 again with port 9002, leaving the username empty and mydjname:mysecret in the password box, then the log shows a warning "login denied from mydjname:mysecret".

Any ideas?

Stefan