[doc] No wildcards on Windows.
[doc] Document the WAV to D15/D8 conversion.
[setup] Shorten labels to available space.
[setup] Narrow the associations for AIMP.
[setup] "Open with".
[seek] Don't unmute on rewind.
[shellex] Fix installer error 1603.
[setup] Associate SAP with foobar2000.
[swift] Fix "Fatal error: Negative value is not representable".
[swift] Enable color diagnostics.
[doc] Update for win64 packages.
[shellex] sf feature #16 Handle all registry entries and propdesc registration from DLL (un)registration.
[opencl] Add progress messages.
I still don't understand your preference for regsvr32 over an installer, but here it is: https://asap.sourceforge.net/asap-8.0.0-ALPHA1-win64.zip The Explorer plugin is ASAPShellEx.dll + ASAPShellEx.propdesc which must live next to one another. regsvr32 error 80004005 means no admin priviledges, 80070002 means no propdesc file.
Have 64-bit Windows download as .zip
I still don't understand your preference for regsvr32 over an installer, but here it is: asap.sourceforge.net/asap-8.0.0-ALPHA1-win64.zip The Explorer plugin is ASAPShellEx.dll + ASAPShellEx.propdesc which must live next to one another. regsvr32 error 80004005 means no admin priviledges, 80070002 means no propdesc file.
[opencl] Free resources early.
Revert "[opencl] Refactor with CL_Buffer."
[opencl] Refactor with CL_Buffer.
[opencl] Refactor std::string -> std::vector<char>.
[opencl] Convert in parallel.
[opencl] Convert all subsongs.
C:\jac\system\Windows\Programming\Repositories\RASTER-Music-Tracker\src\asap.c(2813,24): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data system\Windows\Programming\Repositories\RASTER-Music-Tracker\src\asap.c(4448,22): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss o Fixed now.
[fu] sf bug #46 Avoid MSVC warnings.
[wasap] Fix WM_COPYDATA return value per doc.
[wasap] Handle media keys.
Strange. Are the .SAP files in C:\TEMP identical to the source files?
C:\jac\system\Windows\Programming\Repositories\RASTER-Music-Tracker\src\asap.c(2813,24): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data system\Windows\Programming\Repositories\RASTER-Music-Tracker\src\asap.c(4448,22): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss o I will handle these. For now, just don't pass filenames consisting of over two billion characters. ;) C:\jac\system\Windows\Programming\Repositories\RASTER-Music-Tracker\src\asap.c(3991,10):...
That's my preference from the 80s. Single user computer, so TEMP is not somewhere in the user profile, but there. Environment variables are set up like this: TEMP=C:\TEMP TMP=C:\TEMP When I trigger the diff, two .sap files are created there. But they are .SAP files, not text files,
I've added the _CRT_SECURE_NO_WARNINGS; define the project and the "unsafe" warnings are gone. But these two are still there and look valid to me: C:\jac\system\Windows\Programming\Repositories\RASTER-Music-Tracker\src\asap.c(2813,24): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data 1>C:\jac\system\Windows\Programming\Repositories\RASTER-Music-Tracker\src\asap.c(3991,10): warning C4996: 'strdup': The POSIX name for this item is deprecated. Instead, use the...
warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead.
Ok, I fixed some buffer overflows with malicious long filenames. MSVC may still complain about "unsafe" functions, but I don't care.
[wasap] sf bug #46 Fix buffer overflows with very long filenames.
[wasap] Remove UNICODE support.
[doc] Credit the STIMER bug report.
warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead.
This is not a bug. MSVC's warning says "may be unsafe". For many years, MSVC did not implement C99 - one had to stick to C89. Then they push for using these C11 functions which provide dubious safety - you need to pass the number of available characters. I switched from MSVC to MinGW many years ago. Since you have already MSYS2 (for perl), installing MinGW GCC is as easy as: pacman -S make mingw-w64-i686-gcc mingw-w64-x86_64-gcc Then: make win32/wasap.exe
warning C4996: 'strcpy': This function or variable may be unsafe. Consider using strcpy_s instead.
Windows Explorer extension doesn't work?
I believe this is fixed now.
[win64] Build WASAP, asapscan, asapscan, sap2txt for x64.
[setup] win64.msi contains everything needed for x64 Windows.
[release] "make dist" includes win64.zip.
[foobar2000] Simplify the build.
[win32] Merge 32-bit and 64-bit build rules.
[asapconv] Refactor converting WAV to D15/D8.
[asapconv] Convert WAV to D15/D8.
[asapconv] Start error messages with the filename.
[d15] Play D15/D8 samples.
Use dedicated "Date" attribute instead of"Year" in Explorer Plugin
Done and it's editable. The UI label is "SAP Date", because Windows provides a "Date" property (seems to be same as "Date modified") and you'd see two "Date"s when add a column.
[shellex] sf feature #17 Add the "SAP Date" property.
[release] sf feature #16 win64.zip package.
[setup] Install the foobar2000 plugin in home dir instead of Program Files.
[doc] Describe how to display subsong numbers in foobar2000.
Have 64-bit Windows download as .zip
[doc] Bump the copyright year.
Building XMMS2 plugin fails with
I could only add the FC format. The other formats start with FF FF bytes which makes them misdetected as MP3 by the "mad" plugin and after "mad" fails, ASAP is not given a chance. How to use XMMS2: xmms2 add NINJA.FC xmms2 play Starting xmms2d first is optional, but useful to see the logs. xmms2d -v gives more logs. For testing, use a *.FC file (from https://asap.sourceforge.net/examples.zip), as XMMS2's "gme" plugin provides a partial (inferior to ASAP) support for the SAP format.
[xmms2] Add the FC format.
[xmms2] sf bug #35 Fix "Failed to find plugin header".
Building XMMS2 plugin fails with
I got XMMS2 playing under Fedora 43. The sound is "choking", also on MP3s, but that might be because I'm running it in VirtualBox. I looked at ASAP's plugin source and realized it only supports *.SAP. :) I'll try to add the other formats.
I actually cannot start xmms2d either, it aborts for me. So I cannot test further, either. I actually just do this for "completeness" in packaging: Arch Linux AUR package "asap-chiptunes-player-git". Just for reference: My failure of starting xmms2d: INFO in core: ../src/xmms/log.c:50: Initialized logging system :) 13:39:47 INFO in core: ../src/xmms/ipc.c:981: IPC listening on 'unix:///tmp/xmms-ipc-[username]'. 13:39:47 ERROR in core: ../src/xmms/collsync.c:486: Could not restore collections from...
With this patch --- a/xmms2/libxmms_asap.c +++ b/xmms2/libxmms_asap.c @@ -108,6 +108,7 @@ static gboolean xmms_asap_setup(xmms_xform_plugin_t *xform_plugin) #ifdef XMMS_XFORM_PLUGIN_DEFINE // xmms2-devel 0.9.x +#define XMMS_PLUGIN_DESC_SYMBOL_NAME XMMS_PLUGIN_DESC XMMS_XFORM_PLUGIN_DEFINE("asap", "ASAP decoder", ASAPInfo_VERSION, "Another Slight Atari Player decoder", the error message of xmms2d goes away. But I still don't know how to play a file?
When I start xmms2d, I get an error about the plugin: 20:43:05 ERROR in core: ../src/xmms/plugin.c:394: Failed to find plugin header in /usr/lib/xmms2/libxmms_asap.so Full output of xmms2d: INFO in core: ../src/xmms/log.c:50: Initialized logging system :) 20:46:12 INFO in core: ../src/xmms/ipc.c:981: IPC listening on 'unix:///tmp/xmms-ipc-felics'. 20:46:12 ERROR in core: ../src/xmms/plugin.c:394: Failed to find plugin header in /usr/lib/xmms2/libxmms_asap.so 20:46:12 ERROR in core: ../src/xmms/collsync.c:486:...
Yes, the installer makes more registry entries that the DLL registration. This includes the entries for the Property page. Why unzip and run regsvr32 if you can just run the installer? What do you mean by a "portable" installation?
Also, is your issue just for malformed files or can't you diff any changes? I'm concerned that your error message says C:\TEMP. I don't have this directory on my disk.
I'm using the same TortoiseSVN version as you and ASAP 7.0.0 on Windows 11 24H2.
I removed fix-brk.bat from the ASMA repo. I don't reproduce any error message after copying the file you attached over asma/Unknown/Rock_1.sap. See the attached screenshot. What exactly did you do? MSYS2 perl (and other tools) can be run directly from the Windows command prompt. That's how I usually use it. I rarely use the bash and I never ever use the MSYS2 terminal.
Good solution, thanks.
fix-brk is a quick-and-dirty single-use tool for ASMA. No, I'm not going to maintain or document it. :) The I'd suggest to just remove it from the repo. Please attach the broken Rock_1.sap file for tests. See below. The root cause of your problems is that you installed a wrong perl on Windows, I've removed my previous Perl installation and use MYSYS2 now. What confuses me is that I now have a bash, but the scripts are ".bat" files?
fix-brk is a quick-and-dirty single-use tool for ASMA. No, I'm not going to maintain or document it. :) The I'd suggest to just remove it from the repo. Please attach the broken Rock_1.sap file for tests. See below. The root cause of your problems is that you installed a wrong perl on Windows, I've removed my previous Perl installation and use MYSYS2 now. What confuses me is that I now have a bash, but the scripts are ".bat" file?
I've removed my previous Perl installation and use MYSYS2 now. What confuses me is that I now have a bash, but the scripts are ".bat" file?
Tortoise Diff: The file C:\TEMP\Rock_1.sap-rev798.svn001.tmp.sap is not a valid text file!
Please attach the broken Rock_1.sap file for tests.
Tortoise Diff: The file C:\TEMP\Rock_1.sap-rev798.svn001.tmp.sap is not a valid text file!
fix-brk is a quick-and-dirty single-use tool for ASMA. No, I'm not going to maintain or document it. :) The root cause of your problems is that you installed a wrong perl on Windows, which uses CRLFs instead of LFs. My fix-brk wasn't prepared for that. Having LFs on all systems makes things easier. I use perl from https://www.msys2.org - after the installer is finished, run pacman -S perl. I use MSYS2 for tools like GCC, GNU Make, Python, Node.js. Now the only problem in ASAP is the poor reporting...
Have current version and "future" milestones
I configured the trackers to have N/A as the only "milestone", like I did before for Bugs.
Additional remark: my "checksap" reported the modified file as corrupted. If think the logic in the script incorrectly matches here.
Edit STIL information in WASAP Dialog
Tortoise Diff: The file C:\TEMP\Rock_1.sap-rev798.svn001.tmp.sap is not a valid text file!
Addition: I ran the win64.msi now also on the machine where the property pages didn't work and now they work.
Have current version and "future" milestones
Use dedicated "Date" attribute instead of"Year" in Explorer Plugin
Have 64-bit Windows download as .zip
ASAP 7.0.0 - Missing export form RMT format
Fixed in Git. Thanks!
[sap] sf bug #44 Fix no RMT extraction.
ASAP 7.0.0 - Missing export form RMT format
[xmplay] Fix all RMT instrument names to be number 000.
[md1] Enable in C#.
[d15] Allow garbage bytes in the file.
[release] 7.0.0.
ASAP 7.0.0 released