Stack working in MACOS, not in Windows.

stephen barncard stephenREVOLUTION2 at
Mon Feb 22 10:46:47 EST 2010

I wasn't depending on any player except what was in Rev. In this case it was
non-Quicktime installation imbedding Eric's music player code, using the
video player object. I am assuming WMP would be the code that would play the
file in that situation. What am I to assume, otherwise? The project was
non-operational in Win until I used the .mp3 suffix.

Anyway, using a suffix is usally the right thing to do when working with
files, as far as I can see.

And yes, QT also only works from files in the player. But on mac it plays
the MP3s without the suffix.

This cost a whole bunch of time and I though others should know.
Stephen Barncard
San Francisco

On 22 February 2010 04:21, Jim Bufalini <jim at> wrote:

> stephen barncard wrote:
> > SUCCESS. Found it. *Thank you Jacque, Jim, Mark, **Björnke, Peter* for
> > all
> > your suggestions and I tried them all.
> >
> > here's the "fix"
> >
> > put the tempname & ".mp3" into tPath
> >
> >
> > It wasn't really my code, exactly.... er...  it was more of a Win-Mac
> > assumption about MP3 files.
> >
> > My client wanted major obfuscation of the funny business we're doing
> > with
> > the decryption and playing - and wanted to not only have a temp type
> > file
> > name, but no suffix. It worked in mac.
> >
> > But Windows media player really wants to see that suffix.
> What you are saying here is not exactly so. Windows Media Player
> (wmplayer.exe) would "like" to see the file extension but does not require
> it. This is so of many, if not most PC programs (like Rev on PC does not
> require the .rev extension to know that a file is a stack and to open the
> stack. A stack can have any extension or no extension.). What "needs" to see
> the extension is the OS.
> The OS uses the extension of a file to know what to open the file with
> (which program the file extension is associated with). In the case of no
> extension, or an "unknown" extension, the user "could" be prompted to
> indicate what program to use, or in the case of say a shell, nothing could
> happen and the file is simply not opened (in your case played).
> What you can do, is instead of just trying to call the file, call the
> player and pass the music file as a command line parameter as in: *wmplayer
> c:\theDirectoryTheMusicIsIn\theMusicFile* (with or without the extension).
> Now at this point, wmplayer, depending on how it is configured, could open
> a dialog saying it doesn't recognize the extension, does the user want to
> attempt to play the file anyway? Or it could just play it. Again, this
> depends on the configuration of the wmplayer on that machine.
> Also, you need to be aware that extensions can be "switched" which means
> that the OS can be configured to open .mp3 files with a player other than
> wmplayer. This is another reason, if you are depending on a specific player
> to launch, to launch the player with a command line parameter rather than
> just launching the file.
> As to playing from memory, I believe wmplayer only works with files.
> Aloha,
> Jim Bufalini
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list