stripwax / saasound Goto Github PK

Hi Dave,

I wanted to put some SAM tunes into SidWiz 2 (https://appdb.winehq.org/objectManager.php?sClass=application&iId=18581).

The workflow with six channels is a bit boring. The same song needs to be started and recorded seven times (master + each channel separately).

It would be really cool if the audio recording option of SimCoupe could coax SAASound to output all seven versions at once! :-)

Cheers!

Since SimCoupe now defaults to an x64 install (on Windows), the 32-bit development-bleeding-edge dlls no longer work.
For SimCoupe this is not a problem since Si is compiling the SAASound sources as part of the build.

Any chance of an x64 development bleeding edge dll release?

When debug mode is enabled, files are named:

<base>0
<base>1
<base>2
<base>3
<base>4
<base>5

With <base> generally being saa.pcm, making this:

saa.pcm0
saa.pcm1
saa.pcm2
saa.pcm3
saa.pcm4
saa.pcm5

If <base> contains a file extension, could the channel number be inserted, leaving the file extension intact?

saa.0.pcm
saa.1.pcm
saa.2.pcm
saa.3.pcm
saa.4.pcm
saa.5.pcm

Seems I broke something in the latest huge batch of changes, and now the env generators are generating the wrong envelopes

Hey @stripwax this looks really great! The release binary seemed to be Windows only, so I wondered if it might be possible to make macOS release/instructions too?

Many thanks!

As you know I use SaaSound in my ASCD emulator. And ASCD is built with Visual Studio 2005 so it cleanly supports all operating systems from Windows 2000 to Windows 10. (Pre-2000 versions are not supported just because my timer code uses NT-kernel. This could be rewritten to support even older systems, but that's not really needed.)

In contrast to that, your SaaSound is compiled with Visual Studio 2017 which supports only Windows Vista and above and your DLL file also depends on VCRUNTIME140.DLL file which comes from Visual Studio 2017 and it is not present by default on each machine and people needs to search internet to get it (if they don't have it already from some other program).

I assume these restrictions are not needed and they are just caused by using that particular C++ compiler. So it would be nice if you could at least recompile it with static CRT library which would remove that VCRUNTIME140.DLL dependency. (I am not sure about those older Windows, how far it is compatible or not. We can test it.)

Your DLLs are binary-compatible with older versions, exactly as you stated in documentation, but only as far as people have that dependency DLL on their computer and use a new-enough operating system. :-) So I am thinking about recompilation in an older Visual Studio, but the project files are not backward compatible and cannot be opened directly in there.

(Issue report from simcoupe: simonowen/simcoupe#23 )

In his recently published book Beep to Boom: The Development of Advanced Runtime Sound Systems for Games and Extended Reality, Simon N Goodwin writes:

The volume controls of POKEY, TIA and SID supported 4-bit linear output in 15 even-sized steps. The AY, TI and SAA chips were superior in that respect because their volume controls used logarithmic 2 dB steps. Such non-linear volume controls are sensibly psychoacoustically weighted, so that each step up or down in volume sounded equivalent to the logarithmic human ear, but taking advantage of this requires that recordings made with a linear analogue-to-digital converter should be captured at much higher resolution and re-scaled as part of the conversion process.

I tried reading the source code - and failed - are SAASound's volumes logarithmic?