BASS and MASM user

[LordAdef]

Hi everyone,

I've been around for a while but only now I am really learning this incredible library!

I've updated the .inc file and it's already working.

I will need a lot of help from you guys, so please excuse me if I ask too many questions.

I am currently studying one of the masm examples (Spectrum). I will be adding some extra functionalities to the this example. In the future, if the developer so wants, I will be happy to be included in the distribution (some masm examples don't work, I'll fix them)


Alex

[Ian @ un4seen]

It has been a while since the MASM stuff was last updated, so I have now put an updated BASS.INC file for BASS 2.4.17 in the MASM package. Please re-download to get that (and let me know if you see any problems). Any updated/fixed examples would be much appreciated. If possible, please have them do the same thing as the C examples of the same name for consistency.

[LordAdef]

It has been a while since the MASM stuff was last updated, so I have now put an updated BASS.INC file for BASS 2.4.17 in the MASM package. Please re-download to get that (and let me know if you see any problems).

Hi Ian,
I had already manually updated the .inc based on the 2.4.17 bass.h. Up to now, no issues, but I will re-download and check yours.
For your information, there are two structure members with name conflict, I changed the 'name' members to 'aname'(just for now):

BASS_DEVICEINFO struct
        aname    DWORD   ?       ; description  <--
        driver   DWORD   ?       ; driver
        flags    DWORD   ?
BASS_DEVICEINFO ends

BASS_PLUGINFORM struct
        ctype    DWORD   ?      ; channel type
        aname    DWORD   ?      ; format description   <--
        exts     DWORD   ?      ; file extension filter (*.ext1;*.ext2;etc...)
BASS_PLUGINFORM ends

Any updated/fixed examples would be much appreciated. If possible, please have them do the same thing as the C examples of the same name for consistency.

Sure, I am going to check all the current ones and keep consistency. I'll keep you posted.

[Ian @ un4seen]

For your information, there are two structure members with name conflict, I changed the 'name' members to 'aname'(just for now):

BASS_DEVICEINFO struct
        aname    DWORD  ?      ; description  <--
        driver  DWORD  ?      ; driver
        flags    DWORD  ?
BASS_DEVICEINFO ends

BASS_PLUGINFORM struct
        ctype    DWORD  ?      ; channel type
        aname    DWORD  ?      ; format description  <--
        exts    DWORD  ?      ; file extension filter (*.ext1;*.ext2;etc...)
BASS_PLUGINFORM ends

Thanks. I've changed them to "name_" now (update on the BASS page), to keep them easily recognisable in the documentation. Let me know if that's problematic.