▲

[radio42]

Would this be the case also if my application were to be released under GPL?

I guess so, yes. But to be sure you'll need to ask Thomson!

Do you know of the differences between these two with respect to sound quality and performance?

Sound quality should be almost the same, since decoding is decoding - there couldn't be something added which is not present. The sound quality is mainly effected be the encoding process!
In terms of performance: BASS is slightly faster and uses less resources.

I think I'm gonna run a test both ways and see what I can learn from this...

In your case this is really recommended. I would do the same!

[ken]

Intresting...

Well wich flag to use for internat decoding or "windows" decoding?

[radio42]

In BASS v2.3.0.1 and below there is still the "BASS_CONFIG_MP3_CODEC" flag (used with BASS_SetConfig)

Form BASS v2.3.0.2 and above there will be no flag anymore. Instead two seperate BASS dll's will be shiped.

[Ian @ un4seen]

Do you know of the differences between these two with respect to sound quality and performance?

Besides what Bernd already said above, the only other real difference to note is that the Windows decoder can't produce floating-point output, so BASS has to convert it to floating-point for floating-point channels (BASS_SAMPLE_FLOAT). That means floating-point channels will take slightly more CPU compared to 16-bit when using the Windows decoder, which is opposite to the BASS decoder (it decodes in floating-point and then converts to 16-bit if necessary). This doesn't apply to OSX users, as the OSX decoder can produce floating-point output.

Regarding your earlier question of choosing which MP3 decoder to use (if you have multiple decoders installed), you can set the order in the Audio Codecs Properties control panel. Note the Windows default decoder is produced by Fraunhofer.

[radio42]

The current BASS.NET API v2.3.1.0 is already fully BASS v2.3.0.2 enabled - so no update will be needed.

However, note, that there is already an update out, which supports the new BASS_VIS v.2.3.0.3.
Here you can find the latest update (which is already a pre-BASS.NET v2.3.1.1 version):

.Net 1.1. build : http://www.un4seen.com/filez/4/Bass23.Net11_update.zip
.Net 2.0 build : http://www.un4seen.com/filez/4/Bass23.Net20_update.zip

Make sure to copy the included files to your install directory!

Have fun...

[mitchjs]

the .net stuff is great!!

i am using strong named assemblies...
so to use your's as a sub assembly it must be strong named...

could you strong name your .net api for us

thanks so much

mitch

[radio42]

The BASS.NET API is already strong-named!
:-)

[mitchjs]

sorry, you are right

my eyes must have seen "false" somewhere...

great work on this thing!

oh one thing.. might not be .net related but

when i

Code SelectExpand

_visPlugin = BassVis.BASS_WINAMPVIS_CreateVis(@"visPlugins\vis_avs.dll", 0, (int)BASSVISCreate.BASS_VIS_NOINIT, this.Handle, true);

i get

Code SelectExpand

PInvokeStackImbalance was detected
Message: A call to PInvoke function 'Bass.Net!Un4seen.Bass.AddOn.Vis.BassVis::BASS_WINAMPVIS_CreateVis' has unbalanced the stack. This is likely because the managed PInvoke signature does not match the unmanaged target signature. Check that the calling convention and parameters of the PInvoke signature match the target unmanaged signature.

any idea?

thanks
mitch

[mitchjs]

here is a note...
i get same error on BASS_WINAMPVIS_Free

i looked at the help file for the bass_vis.dll it actually takes 2 params

so i imported that function my self, created

Code SelectExpand

[DllImport("bass_vis.dll")]
  private static extern bool BASS_WINAMPVIS_Free(int handle, int VisCounter);

and used that... and no stack error

mitch

[mitchjs]

yes!

all fixed when i do my own inports of bass_vis.dll

did bas_vis.dll change on you?

mitch

[radio42]

Yes, just scroll up a bit on this thread and you'll find the following:

----
The current BASS.NET API v2.3.1.0 is already fully BASS v2.3.0.2 enabled - so no update will be needed.

However, note, that there is already an update out, which supports the new BASS_VIS v.2.3.0.3.
Here you can find the latest update (which is already a pre-BASS.NET v2.3.1.1 version):

.Net 1.1. build : http://www.un4seen.com/filez/4/Bass23.Net11_update.zip
.Net 2.0 build : http://www.un4seen.com/filez/4/Bass23.Net20_update.zip

Make sure to copy the included files to your install directory!

Have fun...

[BassFan]

Yes, just scroll up a bit on this thread and you'll find the following:

----
The current BASS.NET API v2.3.1.0 is already fully BASS v2.3.0.2 enabled - so no update will be needed.

However, note, that there is already an update out, which supports the new BASS_VIS v.2.3.0.3.
Here you can find the latest update (which is already a pre-BASS.NET v2.3.1.1 version):

.Net 1.1. build : http://www.un4seen.com/filez/4/Bass23.Net11_update.zip
.Net 2.0 build : http://www.un4seen.com/filez/4/Bass23.Net20_update.zip

Make sure to copy the included files to your install directory!

Have fun...

i working on a C# Sample for BassVis from mitchjs... it's work now
And will it insert in the BassVis Archive when mitchjs say ok!

Sorry for my english .. hihihiihihhi

Ich arbeite gerade an den C# Sample von mitchjs.
Es funktioniert ganz gut
Wenn mitchjs sein OK gibt dann addiere ich es im Archiv für BassVis


greets

[radio42]

Super!  sounds great!!!

If you want - pass me the sample to add it to BASS.NET

[BassFan]

Super!  sounds great!!!

If you want - pass me the sample to add it to BASS.NET

jo keine problem
Habe aber die XML und NET.dll aus dem Archiv rausgeschmissen
Wird ja neu erstellt wenn compiliert wird.

Warte noch auf mitch das er mir sein OK dafür gibt.
Ist ja auch ein teil von ihm im Source

gruss

[mitchjs]

that code isnt ready for public!

its to messy and needs more work

since i couldnt get beat data into vis...
i think it was cause of my .net api was the 2.3.1.0 not the 2.3.1.1

ill clean up and make a nicer demo

thanks
mitch

[BassFan]

that code isnt ready for public!

its to messy and needs more work

since i couldnt get beat data into vis...
i think it was cause of my .net api was the 2.3.1.0 not the 2.3.1.1

ill clean up and make a nicer demo

thanks
mitch

i have say you can not run BassVis 2.3.0.3 with .net api 2.3.1.0 use .net api 2.3.1.1 for this Version
The sample work great with no problem by me

greets

[ken]

I need to record a audiosource and convert it "on the fly" to several audioformat at the same time (let's say wma, mp3 low bitrate , mp3 high bitrate)  I need create a new file every hour (or different duration) but with out and gap in the recording. I assume that I run Bass recorder all the time and I just create new file every hour.

Plase point me in the right direction on how to do this, "connecting" the encoder correct for this.

Thanks!

*** I think I solved it :-)

[radio42]

Oki - perfect ;-)

[ken]

Well it works as I like encoding several formats at the same time from a live source. But...

How do I set the "EncoderWMA" to encode realy low quality, like 5 kbit/s and 8kHz mono.

I have my recorder at 44.1Khz stereo

Code SelectExpand

_recHandle2 = Bass.BASS_RecordStart(44100, 2, BASSRecord.BASS_RECORD_PAUSE, _recProc, 0); and I need it that way cause I encode other formats in good quality.

Code SelectExpand

_wma = new EncoderWMA(_recHandle2);
_wma.InputFile = null;
_wma.OutputFile = filename;
_wma.WMA_Bitrate = bitRate;
_wma.WMA_UseVBR = false;
_wma.WMA_UseNetwork = false;
_wma.WMA_UsePublish = false;
_wma.Start(null, 0);

Thanks!

[radio42]

The WMA codec does not support all ranges of samplerates and bitrates.

You might use the "BASS_WMA_EncodeGetRates" method to query the available bitrates for a given samplerate.