Recent Changes - Search:

edit SideBar

Audio Notes

Modifying Clip Player to use getResource()

The goal is to modify ClipPlayer to use getResource() instead of accepting a URL as the name of the clip to be played.

The reason we are using a URL is because the javafx Media constructor expects a String that represents a URI.

If we used getResource() here, then we would need to get the resource, create a URI with a server and serve the contents to the Media constructor, which would then read the URI again.

This seems silly, if we want to use getResource(), then we should probably not use javafx Media and instead use getResource() and what we use in AudioHelper

Details about ClipPlayer

$PTII/org/terraswarm/accessor/accessors/web/audio/ClipPlayer.js uses the audio module, which is defined in $PTII/ptolemy/actor/lib/jjs/modules/audio/audio.js, which uses a ClipPlayerHelper, which is defined in ptolemy/actor/lib/jjs/modules/audio/

ClipPlayerHelper uses, which takes a ( as an argument:

  _player = new MediaPlayer(new Media(url));

The constructor for Media takes a String:

public Media(java.lang.String source)
Constructs a Media instance. This is the only way to specify the media source. The source must represent a valid URI and is immutable. Only HTTP, FILE, and JAR URLs are supported. If the provided URL is invalid then an exception will be thrown. If an asynchronous error occurs, the error property will be set. Listen to this property to be notified of any such errors.
If the source uses a non-blocking protocol such as FILE, then any problems which can be detected immediately will cause a MediaException to be thrown. Such problems include the media being inaccessible or in an unsupported format. If however a potentially blocking protocol such as HTTP is used, then the connection will be initialized asynchronously so that these sorts of errors will be signaled by setting the error property.
The supplied URI must conform to RFC-2396 as required by
Only HTTP, FILE, and JAR URIs are supported.
See for more information about URI formatting in general. JAR URL syntax is specified in


Edward wrote:

"I think the key reason for using getResource() is simply to have a uniform convention for how to access files from within a swarmlet. An alternative would be to abstract the part of getResource() that translates a string, e.g. "strum.wav", into something to read. I.e.,

what is the search path?"

"So an alternative would be just to make the original ClipPlayer smarter so it matches the searches that getResource() does."

In CapeCode, getResource() has no search path, we throw an error if the resource refers to a disallowed path (Starts with /, .., anything other than http, https, $CLASSPATH, $KEYSTORE etc.)

One idea would be to modify getResource() so that it takes a returnURI option which would return the approved URI of the resource.


Edit - History - Print - Recent Changes - Search
Page last modified on October 27, 2017, at 03:44 PM