nsv and shoutcast over v2

Smelter · 28th June 2013, 06:22

Word.

Just as confirmed before, and reconfirmed today. Using VP8 .

DrO · 28th June 2013, 11:17

I assume that means it's working ok through a v2 DNAS ? as cannot work out the source code on the phone, which leads me to say it'd be better to attach code examples than to post inline (will edit that when I'm not on mobile).

[edit]
changed the code block to a txt attachment of the java code

Smelter · 28th June 2013, 12:04

yup. v2 nsv kicking ass

DrO · 28th June 2013, 12:15

rightio, had thought that was the case, i think the only things i know that the v2 DNAS doesn't currently do right with NSV is in some of the playlist reponses available from the DNAS, otherwise it should just be seen as a normal data stream type going through the system (unlike what OGG bases streams are going to need when i can get that finished off).

Smelter · 28th June 2013, 17:38

PLaying /server/1 makes a aac type 0x8003 , adding the /1.nsv makes a video stream.

Smelter · 28th June 2013, 20:39

content type :misc/ultravox :O

Smelter · 28th June 2013, 20:41

btw, playing '1.nsv' while publishing aacp type 0x8001, in winamp made it hang.

DrO · 28th June 2013, 23:02

you need to give me some sort of working example or how to replicate the hang (and also ensure you're testing against the current Winamp release).

not quite following the other 2 posts, though i know there were some quirks with how the content type was reported for streams other than MP3 and AAC at times with the current build (as i did a bit of work with one of the stations trying to use the v2 DNAS for NSV). though other than possible crash fixes, there isn't much i can do time wise (or inclined in all honesty) to much else than i've done so far towards NSV handling in the v2 DNAS - as long as the streams can be sourced through it without issue to clients then that's the main thing so it's like a v1 DNAS in that respect.

Smelter · 29th June 2013, 01:17

yyea, its probably not the latest version of winamp, and it was my fault for trying to play localhost:8000/1.nsv when broadcasting aac ADTS stream.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

28th June 2013, 11:17	#2
DrO Join Date: Sep 2003 Posts: 27,876	I assume that means it's working ok through a v2 DNAS ? as cannot work out the source code on the phone, which leads me to say it'd be better to attach code examples than to post inline (will edit that when I'm not on mobile). [edit] changed the code block to a txt attachment of the java code

28th June 2013, 12:04	#3
Smelter Major Dude Join Date: Jan 2004 Posts: 1,141	yup. v2 nsv kicking ass

28th June 2013, 12:15	#4
DrO Join Date: Sep 2003 Posts: 27,876	rightio, had thought that was the case, i think the only things i know that the v2 DNAS doesn't currently do right with NSV is in some of the playlist reponses available from the DNAS, otherwise it should just be seen as a normal data stream type going through the system (unlike what OGG bases streams are going to need when i can get that finished off).

28th June 2013, 17:38	#5
Smelter Major Dude Join Date: Jan 2004 Posts: 1,141	PLaying /server/1 makes a aac type 0x8003 , adding the /1.nsv makes a video stream.

28th June 2013, 20:39	#6
Smelter Major Dude Join Date: Jan 2004 Posts: 1,141	content type :misc/ultravox :O

28th June 2013, 20:41	#7
Smelter Major Dude Join Date: Jan 2004 Posts: 1,141	btw, playing '1.nsv' while publishing aacp type 0x8001, in winamp made it hang.

28th June 2013, 23:02	#8
DrO Join Date: Sep 2003 Posts: 27,876	you need to give me some sort of working example or how to replicate the hang (and also ensure you're testing against the current Winamp release). not quite following the other 2 posts, though i know there were some quirks with how the content type was reported for streams other than MP3 and AAC at times with the current build (as i did a bit of work with one of the stations trying to use the v2 DNAS for NSV). though other than possible crash fixes, there isn't much i can do time wise (or inclined in all honesty) to much else than i've done so far towards NSV handling in the v2 DNAS - as long as the streams can be sourced through it without issue to clients then that's the main thing so it's like a v1 DNAS in that respect.

29th June 2013, 01:17	#9
Smelter Major Dude Join Date: Jan 2004 Posts: 1,141	yyea, its probably not the latest version of winamp, and it was my fault for trying to play localhost:8000/1.nsv when broadcasting aac ADTS stream.