14.10.2023: Version 2.4.17.5 is out!

Note:
        - Full .Net core support also for BASS_BFX_MIX and BASS_BFX_ENV_NODE added

Full Install:
 www.un4seen.com/filez/4/Bass24.Net.zip

NuGet Package (.Net core only):
 www.nuget.org/packages/radio42.Bass.Net.core


-----
03.10.2023: Version 2.4.17.3 is out!

Note:
        - Support for the new BASS_TAG_HLS_EMSG added
        - BugFix in TAG_INFO when reading multi tag values (eg. for composers)
        - New overload for BASS_ChannelGetTagsID3V2

-----
24.10.2022: Version 2.4.17.2 is out!

Finally a full update after a long time...

Note:
        - Added support for .Net 6.0 (core)
        - Added support for .Net 4.8 (full)
        - Removed all other platform specific builds (no need anymore, so its time to update)
        - BASS: added support for v2.4.17.0
        - add-ons: all latest versions!

Other fundamental changes:
The used .Net Frameworks are now only the Full and the Core versions, which makes deployment and configuration much more easy.
The Encoder and Broadcasting Framework now supports all BASSenc_XXX add-ons.
iOS now uses dynamic linking (instead of static), just like any other platform, so make sure to always also update to all latest native BASS, plug-in and add-on versions!

core: .Net 6.0 fully supports platform independent development for Windows, Linux, macOS, Android or iOS - no other extra version/build is needed.
         The only limitation with this version is, that any Drawing or Image specific classes or functions have been excluded, like the Visual and WaveForm.

full: uses the .Net 4.8 full framework to target Windows development including any Drawing or Image specific classes or functions.


-----
24.09.2019: Version 2.4.14.1 is out!

Note:
        - Added support for .Net Core 2.1
        - Added support for .Net Standard 2.0

        - BASS: added support for v2.4.14.15
        - BASSWASAPI: added support for v2.4.2.3
        - BASS_FX: added support for v2.4.12.2
        - BASSenc: added support for v2.4.14.0
        - BASSASIO: added support for v1.4.0.0
        - BASSMIDI: added support for v2.4.12.4
        - BASSWEBM: added support for 2.4.0.0

-----
12.04.2019: Version 2.4.14.0 is out!

Note:
        - BASS: added support for v2.4.14.0
        - BASSMIDI: added support for v2.4.12.1

-----

15.10.2018: Version 2.4.13.3 is out!

Note:
   - BASS: added support for v2.4.13.25
   - BASSWASAPI: added support for v2.4.2.1
   - BASS_FX: added support for v2.4.12.1
   - BASSenc: added support for v2.4.14.0
   - BASSenc_MP3: added support for v2.4.0.0
   - BASSenc_FLAC: added support for v2.4.1.1
   - BASSenc_OGG: added support for v2.4.0.0
   - BASSenc_OPUS: added support for v2.4.0.2
   - BASSASIO: added support for v1.3.1.9
   - BASSMIDI: added support for v2.4.11.14
   - BASSHLS: added support for 2.4.1.2
   - BASSDSD: added support for 2.4.1.2

-----
11.01.2018: Version 2.4.13.0 is out!

Note:
    - BASS: added support for v2.4.13.2
    - BASSWASAPI: added support for v2.4.2.0
    - BASSHLS: added support for 2.4.0.0
    - Bass.Net.WinStore: all references to add-ons removed which can use the plug-in system

-----
31.08.2017: Version 2.4.12.7 is out!

Note:
   - Support for BASSmix v2.4.9.0 added
   - Support for BASSflac v2.4.4.0 added

-----
31.08.2017: Version 2.4.12.7 is out!

Note:
   - Support for BASSmix v2.4.9.0 added
   - Support for BASSflac v2.4.4.0 added

-----
31.08.2017: Version 2.4.12.7 is out!

Note:
   - Support for BASSmix v2.4.9.0 added
   - Support for BASSflac v2.4.4.0 added

-----

31.08.2017: Version 2.4.12.7 is out!

Note:
   - Support for BASSmix v2.4.9.0 added
   - Support for BASSflac v2.4.4.0 added

-----
31.08.2017: Version 2.4.12.7 is out!

Note:
   - Support for BASSmix v2.4.9.0 added
   - Support for BASSflac v2.4.4.0 added

-----

31.08.2017: Version 2.4.12.7 is out!

Note:
   - Support for BASSmix v2.4.9.0 added
   - Support for BASSflac v2.4.4.0 added

-----
16.05.2017: Version 2.4.12.6 is out!

Note:
   - Support for BASSmidi v2.4.11.0 added

IMPORTANT NOTE:
With this release I do NOT provide any setup.exe tool anymore!
This means, the full install is a plain zip file (just like for the native bass lib).
Just extract it to any new folder of your choice.
----------

16.12.2016: Version 2.4.12.5 is out!

Note:
   - Support for BASSmidi v2.4.10.0 added
   - Support for DSD and APE addon in Bass.Net.WinStore

----------
09.09.2016: Version 2.4.12.3 is out!

Note:
   - Support for BASSenc_OGG added
   - Support for BASSenc_OPUS added

-----
28.04.2016: Version 2.4.12.1 is out!

Note:
   - Bass.Net: .Net Framework v4.5 rebuild
   - Bass.Net.iOS: latest Xamarin.iOS target framework support
   - Bass.Net.Android: latest Mono/Xamarin.Android target framework support
   - Bass.Net.Linux: .Net Framework v4.5 rebuild
   - Bass.Net.OSX: .Net Framework v4.5 rebuild

------------------

OTHER STUFF:

BASS_WADSP: Winamp DSP plugin support
  www.un4seen.com/filez/4/bass_wadsp24.zip

ENC_AACPLUS: Winamp AacPlus command line encoder
  www.un4seen.com/filez/4/enc_aacPlus.zip

13.12.2005: Version 2.2.0.8 is out!

What has changed:

1) BASS .NET API is now available for .Net v1.1 (VS2003) and .Net v2.0 (VS2005) as seperate installers!!
This means you now have clean .Net 1.1 AND .Net 2.0 builds of the API available.
Please locate you download here:
NOTE:
Form now on there are two versions of the BASS .NET API maintained:
- BASS .NET API for .Net 2.0, VS2005   (Bass22.Net20.zip)
- BASS .NET API for .Net 1.1, VS2003   (Bass22.Net11.zip)

So pick your version accordingly to your VS environment!

2) The "WaveForm" class has been enhanced:
a) A new property "FrameResolution" was added to allow you to specify a rendering 'quality' between 1ms and 5000ms (which defines how many milliseconds should be kept in each rendered frame).
b) Now the class supports "Live Recording Rendering" (see the new RenderStartRecording, RenderStopRecording, RenderRecording methods) . The C# 'Encoder.cs' sample was enhanced to demo this feature.

3) The "BassTags" class was modified:
A bug was fixed when reading ID3v2.3.0 genre (TCON) tags.
Now the correct ID3v2.3.0 and ID3v2.4.0 genre strings are parsed - before this fix sometimes the genre-id only (e.g. "(21)" was returned.

4) The "Visuals" class was modified:
Now it needs to be instanciated (members are no longer static) !!!
This serves much more flexibility when using it on multiple controls or components (the C# 'Simple.cs' sample was adjusted accordingly).

5) The full source code of the BASS .NET API is from now on NOT included anymore in the downloads. BUT they can still be requested (upon valid reason from licensed users only!) - simply send a mail to "bn@ten53.de" or "bn@radio42.com".
This was simply done because of missuse and causing more trouble then help. And since from now on both .Net versions are fully maintained, I even guess the source is no longer needed by anyone - as all other stuff/add-ons also doesn't come with the source ;-)

Thanks! good work. But your download links point both to 1.1 version...

-> Fixed above ;-) THX!

How can I create a waveform "offline" (fast without playing audio in to speakers) and serialize the waveform to xml, so I can use it later with that audio file that the waveform belong to. Possible?

Offline rendering:
WF = new Un4seen.Bass.Misc.WaveForm(_fileName, null, this);
WF.FrameResolution = 0.01f; // 10ms are nice
if ( WF.RenderStart( false, BASSStream.BASS_SAMPLE_FLOAT | BASSStream.BASS_STREAM_PRESCAN ) )
    WF.WaveFormSaveToFile( "C:\\test.wf" ); // or use your filename and replace the ext.


All i want for xmas is:

- Beat Detection .
- Beat Sync. 2 streams, Master-Slave. With auto Pitch option on slave

;-)

Great ;-)

Live BPM Detection is rally hard to implement and i think it's more important to have a good beat sync between streams.  Also auto "pitch" on slaves so that they follow the BPM on the master stream and stay in sync would be great.

But don't limit the design to just one slave.  Any number of streams should be able to be a "slave"- stream.

Thoose features is is nice to have if you want to do live remixes etc.  The best software that have implemented this is  Ableton Live, then followed by Traktor 3.
I'm not looking to do a 100% automatic mixer, that would be really boring to use. 

But if you can make the beat detection version available then i will try to implement them myself .

I was going to start with the beat detection, but since you have one almost finished i think i will wait for yours.

The new BPMCounter class and how it works:

Just before we start:
a) Automated Mixing of multiple source and Pitch calculation is up to you!
b) Plotting of detected beats in a Waveform is also up to you!
-> However both should be possible ... and you also need to do some work ;-)

The new BPMCounter class provides general methods to detect beats live in an audio signal and to calculate the resulting Beats Per Minute (BPM).

The BPMCounter class is an internal implementation of the BASS .NET API and does not require any additional extension or add-on to the BASS audio library, meaning only bass.dll is required.

Internally the algo is based on human ear simulation - meaning an average energy history of 1 second is used, since this is what the human ear can keep - so the BPM results might change and vary more often as with systems scanning the whole file or bigger parts of it. The advantage is therefore that this system might be used with live data and has a fast reaction time of about 1 second only - like our human ear.

So there is a valid reason, that this BPMCounter lives next to the great work JOBnik has done in it's BASS_FX add-on.
So this is not intended to replace it!!!

The typical use of this class is as followed:

a) create an instance of this class (e.g. at the beginning of your application)

b) use a timer callback (e.g. every 20ms or every 25ms) to process the audio signal (the timer frequency must be specified when creating the class instance).

c) in the timer callback call ProcessAudio to detect a beat.

d) retrieve the BPM propertiy to get the calculated Beats Per Minute value.

You should call the Reset method whenever you play another stream or if the returned BPM looks completely wrong.

There are also methods to calculate the BPM manually using a TAP click button. E.g. call TapBeat on a mouse click event to tap (set) a beat manually and call TappedBPM to retrieve the manually tapped BPM value.

Beat detection is a very very complex task and it is almost impossible to implement it matching for any kind of audio signal. So please note, that it might NOT work with all tracks in the same way - with some tracks it might return really bad results. This implementation is a 'simple' one (not needing too much CPU power). It is based on instant energy calculation on 128 frequency bands and comparing them with it's average engery for that band. The variation of the energy of each frequency band is used as a dynamic sensitivity factor. The peak detector uses an attack time of 0ms and there is a dynamic release envelop for the release time - plus we have a Schmitt triggers and a rising edge detectors implemented for each frequency band. The low pass frequency has a fixed value of 350Hz (for detecting bass drums) and the mid range frequency is set to be between 1500Hz and 4000Hz (to detect e.g. snare drums). This to calculate an overall trigger value for all frequency bands. Finally there is a Schmitt trigger again to detect the final beat for each call to the audio signal processing.

You might notice, that often more beats are detected as you would recognize them with your ear (when doing manual tapping). These are intermediate beats or simply lound noise in the signal (which the algo did not filter good enough). So the BPM calculation uses a time spotting approximation to determine when a beat is a good beat to count. 'No-good' beats are simply not counted. So it sometimes might take some time until the live BPM value reaches a good value!

The default BPM value range is between 60 and 180 BPM. But this might be changed using the MinBPM or MaxBPM properties.

Note: 1 BPM is worth about 5ms (at 120BMP) - or in other words: if your timer intervall differs in 5ms the resulting BPM might have a difference of about 1 BPM. Therefor we use a BPM history buffer which we interleave and calculate the average to equalize this effect.

The BPM results are not equally good for all music tracks and genres. However, beat detection and BPM calculation is mostly needed for DJ applications with music having mostly clear and distinct beats and for this kind of music the class produces very good results. Also keep in mind, that when working with highly compressed or equalized tracks (e.g. badly encoded MP3 tracks) the quality might also suffer - so for best results use good audio material.

Have FUN - and let me know if it is useful...

There's a bug in version 2.2.0.10 (.net 1.1 and maybe 2.0).

Here's my code:

                If Un4seen.Bass.AddOn.Tags.BassTags.BASS_TAG_GetFromFile(StreamChan, TI) Then
                    Artist = TI.artist.ToString
                    Title = TI.title.ToString
                    Genre = TI.genre.ToString
                    Comment = TI.comment.ToString
                    TrkYear = TI.year.ToString
                    Album = TI.album.ToString

The genre is supposed to be "Big Band" but it ends up as "BigBand". Same for "Top 40" ends up being "Top40". The code you are using must be removing the spaces in the genres.

Thanks,

Rick

To ALL,

BASS .NET API v2.2.0.10 works fine with BASS 2.2.0.3 !!!

The BASS .NET doc still states 2.2.0.2, but there was no API change in 2.2.0.3, so I did want to build a new version just for updating the doc ;-)

When you have installed BASS .NET...go to your installation folder...and take a look at the "Samples" sub-directory.

Encoder examples are included in the following samples:
CS:
- Encoder
VB:
- AudioJoiner

Hi Nick,

normally a "System.BadImageFormatException" is indicating that the file image of an executable program is invalid or the application is not a managed assembly.

So, there could be various reasons:
a) some files got corrupted (eg. during download or install)
a) the file image gets corrupted during runtime due to a memory failure
c) you are running a .Net 1.1 lib against a .Net 2.0 environment (the VS2005 beta had some bugs here!)
d) You've tried to load an assembly built against a newer version of the CLR than was running.

So I assume either c) or d) is your problem!

So make sure (when using the samples):
1. that the referenced BASS .NET API version is matching your CLR (eg. .Net 2.0)
    -> maybe due to your conversion you need to replace the BASS .NET API library reference
2. when starting an application (runtime) that really the .Net 2.0 CLR is loaded and not the old .Net 1.1

Here is nice article about it:
http://blogs.msdn.com/suzcook/

So I bet you have some mixed projects, e.g. referencing a BASS .NET API 1.0 lib in a VS2005 project...

Do you recommend uninstalling .10 first? Or just installing .11 over it?

yes, it is already there - Ian just needs to change the web.

and Yes, you can installing over any other version without problems.