setting up nsv

[uberphreak99]

can anyone tell me how to actually set up NSV? I'm suprised that it did not come with a readme or anything

Have you read the stickies on top of the forums? It is still beta and under development not really for the weak of computer illiterate.

[nitrons*girl]

dittos here, i'm so incredibly lost, i've read the stickies and all the links and everything else, i can't get the stuff to open in dos correctly, i've encoded 1 vid that was 1.5gb (originally 64mb) and it won't play... i like to think that i'm fairly computer literate, as i have a computer repair business, and i pick things up pretty quickly, but this thing just has me totally baffled! just a simple "readme" would be good. *sigh*

[Vchat20]

GUI plz

[Jeeper One]

Hi everyone:

I've been doin' a little experimenting with NSV (though not live) since I've had to keep my cam offline because this new keyboard takes up the USB connection which my cam ordinarily and otherwise would (Grrrr ) and I have to say that while I'm not an expert by any means, I like to think I'm catching on.

Having said that, I think the NSV format is too dependent on UNCOMPRESSED MPEG rather than taking what's available. Add to this the fact that there isn't a way in which one can use their favorite conversion program unless FLASK *IS* your favorite program (It's certainly NOT one of mine) PLUS the fact that the current NSV Tools don't work with AVI unless you use the Batch Encoder (which BTW seems to have a problem finding an audio codec on my machine for some strange reason even with my radio station OFF THE AIR as it gives an audio codec not found error message), I'd have to say that I think it'll most likely be quite some time before the new NSV video format EVER takes off like SHOUTcast has UNLESS you have a webcam and (if you run a radio station like *I* do ) open an additional port within the SHOUTcast server to allow room for a LIVE video stream complete with audio (I suppose I could always have the radio station use the NULL Output plugin within Winamp if needed).

As much as I hate to admit it (because I'd really like to see this thing become a reality), I don't see myself dumping iVista 4.1 with audio module anytime soon (if ever).

Oh well....Maybe good things shouldn't be rushed... But we can at least PREPARE for it though

Cheers for now

Jeeper One

Ok
NSV is still in the beta development process so there isn't much for it yet.

Hopefully when it reacesh 1.0 there will be specs released in order for other programs to implement NSV.

The only thing the batch encoder (nsvate) does well is crash. Try using the command line NSVenc.

I have no problems encoding from AVI. Just make sure you cna play the file on your system. It uses Direct Show filters.

Likewise I have no problem encoding from any type of MPEG.

Hopefully when SHOUTcast 3.0 or NSV 1.0 comes out there will be more GUI. Maybe even a Winamp plug-in like SHOUTcast.

When trying to playback make sure you sue the right url:
http://ip:8000/;stream.nsv

If you don't add the .nsv part Winamp will try to play it as a MP3, which is wrong.

if you encoded a 64MB video and it jumps to 1.5Gig you did something wrong. What were your settings? Audio? Video? Bit rates, frame rates, and resolutions?

[Jeeper One]

Hi everyone:

I'm trying the FLASK for NSV program now, but about the only thing IT knows how to do well is parse the audio from the video (yes, I do use Direct Stream Copy too).

And this is EVEN IF you make the audio and video THE SAME FILE.

THIS is why I'm saying you guys should be working on a codec which can be used by the numerous companies which produce the numerous converters out there to provide NSV support. Without that, NO converter program is going to know how to handle NSV unless Nullsoft builds the program themselves.

This should be a NO-BRAINER even for the NullSoft Techies, but I guess not.

Simply because AOL may have put you guys at Nullsoft on a shoestring budget DOES NOT mean YOUR BRAINS have to THINK like that.

Note, the above isn't meant to be a cheap shot, but rather some constructive (and hopefully useful) criticizm (sp?).

Just my $.02 worth

Jeeper One

[nitrons*girl]

*scratches head* changed settings, i've used the flask and NSVate, both are throwing out 1.5+gb vids, neither playable, with NSVate when i change the sound to "mp3 audio" i at least get sound, but winamp says [Buffering 99%] and all i get is super crappy audio and no video....??????? EEP!! *pulling out hair*

NSV is still in development. Therefore there is no stream specification out yet. NSV is still BETA SOFTWARE. Therefore it is not done and very new. Therefore other software does not support it yet.

The tools are still being developed and can be buggy. As Beta software usually is.

Try not using Flask and NSVate, but using the command line encoder tool nsvenc. This is the most developed tool. You can configure the output with the "/configre" switch.

The general concept that you all seem to be missing is that NSV is still in development. It's not done. It's beta. It's not meant for professional use right now. It's buggy. It's poorly documented. It's a format in development. Therefore no other companies use it.

Using NSVenc I have no encoding problems. I don't even bother with Flask or NSVate. The command line tool just works easier and always works.

If you aren't happy with its current status in development come back when it is done and there are more user-friendly tools for encoding.

[Jeeper One]

Hi everyone:

Originally posted by Sawg
NSV is still in development. Therefore there is no stream specification out yet. NSV is still BETA SOFTWARE. Therefore it is not done and very new. Therefore other software does not support it yet.

Even a Beta codec would be better than NOTHING.

Try not using Flask and NSVate, but using the command line encoder tool nsvenc. This is the most developed tool. You can configure the output with the "/configre" switch.

This would be easy to do IF you're NOT using WinXP. You have to remember that Win XP has almost ZERO support for DOS and DOS-based tools. Win XP (even the Home Edition) also happens to be on the vast majority of PCs these days too.

As such, you have to do a lot better (even in Beta form) than just simply telling people to use "command line" tools which are UNUSABLE in XP _BEFORE_ you unleash the software on the rest of the world.

I have to wonder if releasing NSV in its present state was the right thing for Nullsoft to do.

The general concept that you all seem to be missing is that NSV is still in development. It's not done. It's beta. It's not meant for professional use right now. It's buggy. It's poorly documented. It's a format in development. Therefore no other companies use it.

Then either STOP DOWNLOADS ALTOGETHER or CLEARLY state that Win XP simply bcan't be supported at this time. How painful of a job is that??

Using NSVenc I have no encoding problems. I don't even bother with Flask or NSVate. The command line tool just works easier and always works.

That's probably because you're using an operating system that supports DOS or you are using it on a machine which ONLY DOS on it. This is probably why you're saying it always works for you.

If you aren't happy with its current status in development come back when it is done and there are more user-friendly tools for encoding.

It's like what I've said before. I'm not going to drop my current webcam software for NSV as it's not done yet, but I'm also going to continue tinkering with it and will gladly post some of my results as I go along.

In the meantime, my radio station will continue to get all of the SHOUTcast resources and SHOULD I master the art of encoding in NSV (and once I have enough stuff to make a video playlist), only THEN will I configure my SHOUTcast server to open another Base Port (or post a message on the appropriate board as to how to do this) and adjust the max. number of listeners to accomondate my new NSV-based TV station AS WELL AS my current radio station.

Cheers for now

Jeeper One

Command line tools work perfectly fine in Windows XP

Start > run > cmd

XP is supported fine. I have no problems with NSVtools in XP. Hell, they are Win32 applications, just work on the command line. If you don't know how to use command line tools you should wait until it is done and there are more GUI tools. But because you cannot figure out don't assume it doesn't work.

It honestly looks like you have no CLUE what you are doing. I recommend you wait until SHOUTcast3 and NSV is meant for end user usage. Until then it is a development codec and only recommended for people who know what they are doing. It is not currently meant for every day usage yet. But the download won't be removed because you don't understand how to use it. By the looks of the Internet TV listing in Winamp 2.91 enough people can figure it out. Stick with audio for now. Let the format develop.

[Rocker]

/me walks into wall repeatedly without thinking

[Jeeper One]

Hi everyone:


I got the following message when trying to use the nsvscsrc command line tool...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Patrick Cook>nsvscsrc.exe
'nsvscsrc.exe' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Patrick Cook>

Which is why I use the programs themselves.

During my offline time (Due to a problem in the main line between me and my cable provider, I spent the last TWO DAYS offline), I finally figured out how to set up the Batch Encoder, however no matter how I set it up, the audio kept going WAY WAY WAY faster than the video did. The video seemed to be going at normal speed, but the audio was going at like SUPER TURBO speed and the length was shown as being shorter than the actual length or was (usually) LONGER than the actual length. NEVER right on target and NEVER in sync.

And you're right, I *don't* know how to use command line tools BUT if I don't experiment with the tools that are available by plugging away over and over again until I get it right, HOW will I learn?? Perhaps my suggesting that they be removed was a little thick, but it seems to me that WE are supposed to be Nullsoft's QA Team and that's NOT right at all. Being Beta testers is one thing. Being the comapany's QA Team is another.

With that said, I will go put Jeeper One Radio back online now that I'm back.

Cheers for now

Jeeper One

You cannot run the tool from any directory . Go to the folder where it is installed and ran there.

There is nothing wrong with the tools. The batch encoder i a little crash, but all other tools work fine. Not being able to figure out the tools is a USER error. They are not responsible for that.

Like I said, stick with SHOUTcast and let the people who know what they are doing play with NSV.

[Jay]

Originally posted by Jeeper One

Which is why I use the programs themselves.

During my offline time (Due to a problem in the main line between me and my cable provider, I spent the last TWO DAYS offline), I finally figured out how to set up the Batch Encoder, however no matter how I set it up, the audio kept going WAY WAY WAY faster than the video did. The video seemed to be going at normal speed, but the audio was going at like SUPER TURBO speed and the length was shown as being shorter than the actual length or was (usually) LONGER than the actual length. NEVER right on target and NEVER in sync.

And you're right, I *don't* know how to use command line tools BUT if I don't experiment with the tools that are available by plugging away over and over again until I get it right, HOW will I learn?? Perhaps my suggesting that they be removed was a little thick, but it seems to me that WE are supposed to be Nullsoft's QA Team and that's NOT right at all. Being Beta testers is one thing. Being the comapany's QA Team is another.

If you do not know how to use command line tools then you souldn't be beta testing software or complaining when it doesn't work. I am not sure what you mean above but you definately got it wrong, beta testers are part of the quality assurance process. I am glad that beta testing is open to the public personally, and if you know basic windows commands and how video works on the computer you will have no problem setting up nsv. Just ask the 15 people online with NSV SHOUTcast stations.

[Jeeper One]

Hi everyone:

Well....I'll just keep plugging away locally till I get it right (Ain't nuttin' wrong with that ). If and when I do, I'll JOIN those 15 people with MY TV station.

The point I was trying to make is that there should be a pre-release testing system that goes on only within the company. Maybe there was with NSV, but perhaps Nullsoft was probably under pressure from higher-ups within AOL to release NSV now even though it's obviously not ready??? I dunno...

But I *do* know this much, I'll keep plugging away and do less complaining because it's not really productive.

Cheers for now

Jeeper One

NSV was limited to Nullsoft for quite a while. It is to a point where it is stable enough to be released to the public. Plenty of people understand it perfectly fine. If you do not understand command line tools that is NOT Nullsoft's fault. If you are unhappy with the current status of NSV then stop using it. But just because you are not pleased doesn't mean that everyone else in not either.

[akrall]

Swag

What are the best settings to use for nsvenc? for example, how does the interlace works and all the other settings? Ive been trying to find more info on that but lo luck yet.

Thx!

Originally posted by Sawg
NSV is still in development. Therefore there is no stream specification out yet. NSV is still BETA SOFTWARE. Therefore it is not done and very new. Therefore other software does not support it yet.

The tools are still being developed and can be buggy. As Beta software usually is.

Try not using Flask and NSVate, but using the command line encoder tool nsvenc. This is the most developed tool. You can configure the output with the "/configre" switch.

The general concept that you all seem to be missing is that NSV is still in development. It's not done. It's beta. It's not meant for professional use right now. It's buggy. It's poorly documented. It's a format in development. Therefore no other companies use it.

Using NSVenc I have no encoding problems. I don't even bother with Flask or NSVate. The command line tool just works easier and always works.

If you aren't happy with its current status in development come back when it is done and there are more user-friendly tools for encoding.

[sankt]

I dont think they currently are,

Might be a good idea to get some one to do that now.