26 May '13 - 04:05 *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: 1 ... 51 52 [53] 54 55 ... 60
  Reply  |  Print  
Author Topic: BASS.NET API 2.4.10.1  (Read 369498 times)
bensam56
Posts: 65


« Reply #1040 on: 5 Jan '12 - 22:42 »
Reply with quoteQuote

Hi, Thank you for the update. Again the installer fails to install while integrating the help.
Logged
radio42
Posts: 4012


« Reply #1041 on: 6 Jan '12 - 00:09 »
Reply with quoteQuote

The installer will only fail, if you have specified a VS version which isn't installed on your system.
Logged
bensam56
Posts: 65


« Reply #1042 on: 6 Jan '12 - 01:30 »
Reply with quoteQuote

I have visual studio 2010 installed in my system. Your previous version installer works but not this one.
Logged
radio42
Posts: 4012


« Reply #1043 on: 6 Jan '12 - 08:54 »
Reply with quoteQuote

And what options did you select with the installer?
Did you enabld both:
- Integrate VS2005/2008 help?
- Integrate VS2010 help?
Logged
HarryHar
Posts: 135


« Reply #1044 on: 17 Jan '12 - 14:28 »
Reply with quoteQuote

I tried to use the waveform class using this code :

WaveForm _wf;

private void Initialize()
{
    _wf = new WaveForm;
}

private void LoadFile(string fileName)
{
    WaveForm.FileName = fileName;
    WaveForm.RenderStart(true, BASSFlag.BASS_DEFAULT);
    if (WaveForm.NotifyHandler == null)
        WaveForm.NotifyHandler = new WAVEFORMPROC(WaveFormUpdate);
}

The first time everything works fine, but I can't get it to work the second time. either with the same or a different filename. If I create a new WaveForm everytime it works.

Is this meant to work like this? Or am I missing something?
Logged
radio42
Posts: 4012


« Reply #1045 on: 17 Jan '12 - 15:11 »
Reply with quoteQuote

Actually it should work, when you assign a new/different "WaveForm.FileName" property value - as this will reset the the internal wave buffer.
However, if the 'rendering' is still in progress, this will fail.
You might check the following:
a) make sure, that assignment "WaveForm.FileName = fileName;" was successfull by checking the "WaveForm.FileName" property again after your assignment!
b) check the return value of "WaveForm.RenderStart" to see, if that returned FALSE.
Logged
ken
Posts: 630


« Reply #1046 on: 18 Jan '12 - 09:43 »
Reply with quoteQuote

Hi,

Can I use the "GetListeners" and "GetStats" in "Un4seen.Bass.Misc.BroadCast" without sending a stream to the IceCast server?

I want to build a simple statistics program for monitoring some streams on IceCast.

/Ken

Quote
Forget my question, I found an easier way. Just get the XML log direct from IceCast server ;-)
« Last Edit: 18 Jan '12 - 09:56 by ken » Logged
gyrosp
Posts: 31


« Reply #1047 on: 6 Feb '12 - 10:30 »
Reply with quoteQuote

I've downloaded Bass.Net 2.4.8.4 and BASS_DSHOW 2.4.1.

When I try to Init BASS_DShow I get following error:
EntryPointNotFoundException was unhandled
Der Einstiegspunkt "xVideo_Init" wurde nicht in der DLL "BASS_DSHOW.dll" gefunden.

Can you please tell me what I am doing wrong.
Logged
Ionut Cristea
Posts: 1377


« Reply #1048 on: 6 Feb '12 - 10:31 »
Reply with quoteQuote

Try with this

http://surodev.com/downloads/BASS_DSHOW.zip
Logged
gyrosp
Posts: 31


« Reply #1049 on: 6 Feb '12 - 10:34 »
Reply with quoteQuote


Thanks for the fast answer.

Now I get following error:
An incorrect version of BASS_DSHOW was loaded!
Version loaded: 0.1
Version expected: 2.4

File: XXX
FileVersion: 1, 2, 2, 0
Description: xVideo - Multimedia Library
Company: Copyright (C) 2011 Cristea Aurel Ionut
Language: Englisch (USA)
Logged
radio42
Posts: 4012


« Reply #1050 on: 6 Feb '12 - 11:44 »
Reply with quoteQuote

Seems, that the version number of BASS_DSHOW has changed unexpectedly - I don't know, looks like he has changed the internal version number from 2.4.x to something else - please ask Ionut what version number he is now reporting for .
I am sorry for that confusion, but it seems, that IOnut is constantly changing his API without taking care about backward compatibility!

To work around this issue, you might set the "BassNet.OmitVersionCheck" property to FALSE - prior to using BASS_DSHOW.
Logged
Ionut Cristea
Posts: 1377


« Reply #1051 on: 6 Feb '12 - 11:46 »
Reply with quoteQuote

The internal version is 1.2.2 on the latest BASS_DSHOW
Logged
gyrosp
Posts: 31


« Reply #1052 on: 6 Feb '12 - 12:47 »
Reply with quoteQuote

Seems, that the version number of BASS_DSHOW has changed unexpectedly - I don't know, looks like he has changed the internal version number from 2.4.x to something else - please ask Ionut what version number he is now reporting for .
I am sorry for that confusion, but it seems, that IOnut is constantly changing his API without taking care about backward compatibility!

To work around this issue, you might set the "BassNet.OmitVersionCheck" property to FALSE - prior to using BASS_DSHOW.

I get the same error when I set OmitVersionCheck = false:
            Un4seen.Bass.BassNet.OmitCheckVersion = false;
            Un4seen.Bass.AddOn.DShow.BassDShow.BASS_DSHOW_Init(visualizer.GetVideoHandle(), BASSDSHOWInit.BASS_DSHOW_Default);

Logged
radio42
Posts: 4012


« Reply #1053 on: 6 Feb '12 - 13:08 »
Reply with quoteQuote

Sorry, you of course need to set BassNet.OmitCheckVersion to TRUE (omit = bypass).
Logged
gyrosp
Posts: 31


« Reply #1054 on: 6 Feb '12 - 13:19 »
Reply with quoteQuote

Sorry, you of course need to set BassNet.OmitCheckVersion to TRUE (omit = bypass).

Oh, this make sense Wink.

With OmitCheckVersion = True the error is gone but only to reveal the next error Sad:

Error
Unregistered version of BASS_DSHOW

Why does this have to be so complicated Wink? I thought Bass_DShow is free for none comercial use.
Logged
Ionut Cristea
Posts: 1377


« Reply #1055 on: 6 Feb '12 - 14:06 »
Reply with quoteQuote

 Just to keep track of those who use BASS_DSHOW Smiley
Logged
gyrosp
Posts: 31


« Reply #1056 on: 6 Feb '12 - 14:31 »
Reply with quoteQuote

Just to keep track of those who use BASS_DSHOW Smiley

Mhh, this sucks but I have to live with it Wink. Perhaps I'll spent the money for the shareware-license if I am happy with the results Wink.

Finally I got it to work but when I move my video-Form from my left monitor to the right monitor while playing a video the app crashes. Is this a known issue?
Logged
Ionut Cristea
Posts: 1377


« Reply #1057 on: 6 Feb '12 - 15:00 »
Reply with quoteQuote

   Yep. In the new version i will add a method to set the monitor so that will not crash Smiley
Logged
BulleTTime
Guest
« Reply #1058 on: 19 Feb '12 - 20:26 »
Reply with quoteQuote

I cant use any other classes than Bass for .Net 2.0. When i want to register using BassNet.Registration, i this error:

Internal compiler error. See the console log for more information. output was:warning CS1685: The predefined type `System.Runtime.CompilerServices.ExtensionAttribute' is ambiguous. Using definition from `System.Core, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e

This is logic as this tells me what its not .Net 2.0:


http://msdn.microsoft.com/en-us/library/system.runtime.compilerservices.extensionattribute.aspx

Any idea how i can register the .Net wrapper for 2.0?

Thanks
Logged
radio42
Posts: 4012


« Reply #1059 on: 20 Feb '12 - 09:14 »
Reply with quoteQuote

What target framework are you using for your application?
If your application is targeting the .Net framework v2.0, v3.0 or v3.5 make sure to reference the BASS.NET version for the v2.0 framework.
If your application is targeting the .Net framework v4.0 make sure to reference the BASS.NET version for the v4.0 framework.

However, this is just a compiler warning (not an error).
The predefined type (in this case the "System.Runtime.CompilerServices.ExtensionAttribute") is defined in multiple assemblies in the global alias.
This error occurs when a predefined system type is found in two assemblies.
One way this can happen is if you are referencing mscorlib from two different places, such as trying to run the .Net Framework versions 2.0 and e.g. 3.5 or 4.0 side-by-side, e.g. because multiple libraries or your main application are targeting/using different .Net framework versions.
The compiler will use the definition from only one of the assemblies.

As such the warning is just telling you from which one it is actually used.
Logged
Pages: 1 ... 51 52 [53] 54 55 ... 60
  Reply  |  Print  
 
Jump to:  

Powered by SMF 1.1.18 | SMF © 2013, Simple Machines