Recent changes to support-requests

#4 Add install targets for `asap2wav` executables.

2023-05-08T12:27:43.081000Z

status: open --> wont-fix
assigned_to: Piotr Fusik

#4 Add install targets for `asap2wav` executables.

2023-05-08T12:01:45.381000Z

In my Arch Linux package asap-chiptunes-player-git

It can be used to get ideas how to achieve this.

Add install targets for `asap2wav` executables.

2023-05-08T11:57:32.770000Z

I hereby express my wish to add make install-python, make install-python-bin and make install-swift targets, to easily install python module system wide and to easily install asap2wav executable systemwide.

make install-python should install the python/asap.py library to the systemwide python modules directory,
make install-python-bin should prepend a shabeng-line (#!/usr/bin/env python) to python/asap2wav.py and install it with executable permissions as bin/asap2wav,
make install-swift should install swift/asap2wav with executable permissions as bin/asap2wav,
all honouring DESTDIR and --prefix.

In my Arch Linux package asap-chiptunes-player-git I refrain from the swift-based executable because swift compiler is a big beast which is not easily available and I use the python executable.

Add install targets for `asap2wav` executables.

2023-05-08T11:57:32.770000Z

Ticket 4 has been modified: Add install targets for asap2wav executables.
Edited By: Piotr Fusik (pfusik)
Status updated: 'open' => 'wont-fix'
Owner updated: None => 'pfusik'

#3 CMC/CMS file structure

2020-05-05T10:08:00.078000Z

status: open --> closed

#3 CMC/CMS file structure

2020-05-05T09:19:09.462000Z

found it finally: http://atariki.krap.pl/index.php/CMC_(format_pliku)

you can close the ticket.

BR,
M.

CMC/CMS file structure

2020-05-05T09:03:29.888000Z

Hi,

do we have CMC / CMS music file structure definition available?

CMC/CMS file structure

2020-05-05T09:03:29.888000Z

Ticket 3 has been modified: CMC/CMS file structure
Edited By: Piotr Fusik (pfusik)
Status updated: u'open' => u'closed'

Play Method

2011-05-14T17:19:09Z

Now after resolving ERROR LOADING - filename error with your help (by adding the MIME type to my server), I ran into a new snag. This time it's the START method of the applet i can not get to work.

Here's my situation: I have a page that uses ASAP applet to play SAP music. When the page is first displayed, the applet plays a predetermined song and also displays a drop-down list with more songs to choose. When the user chooses a new song from the drop-down list, an ONCHANGE event is generated, which in turn issues a javascript call to the applet's START method to play the selected song. (onchange=javascript:pokey_start("pokey/"+document.songs.song.value,-1)

According to my java logs, the applet requests the new file from the server but nothing happens (the applet just keeps playing the predetermined song)
I have no problem with STOP or PAUSE, just START.

This is how my code looks like:

function pokey_stop() {
var s = document.PokeyP.stop();
return null;
}
function pokey_start(songName,songNo) {
var s = document.PokeyP.Play(songName,songNo);
return null;
}
function pokey_pause() {
var s = document.PokeyP.togglePause();
return null;

<form method="post" name="songs" style="width: 258px; height: 24px">
<select name="song" style="width: 263px; font-family: Verdana; font-size: x-small; background-color: #000000; color: #FFFFFF;" onchange=javascript:pokey_start("pokey/"+document.songs.song.value,-1)>
<option value="Deadline.sap">Deadline</option>
.
.
.
<option value="Ballblazer.sap">Ballblazer</option>
</select>
</form>

ERROR LOADING - file

2011-05-10T23:07:06Z

Using the Java Applet and running locally I can play SAP files with no problem, however when I try to play from the webserver (remotely) the applet throws an ERROR LOADING + filename exception.

I am using IE 9.0 (32 bit) and Firefox 3.6 (32 bit) on Windows 7 (64 bit) and this happens with both browsers.
My web server is IIS running on a 64 bit Windows 7 computer.

This does not seem to be a JAVA security issue as i set "permission java.security.AllPermission; " in the java.policy file.