As a quick side note, I (flug_m) am a moderator of the saveourtunes forums, but am not an administrator. Recently the forums have been taken over by spam bots and I don’t have the time to delete the 800+ messages left on there over the past two days; therefore I am removing the link to the forums.

Links the latest version of ourTunes are still available on the front page - read the previous entries. The version posted should be sufficient for Windows; little progress has been made on an OSX compatible version.

Alright, I was asked to repost the code for ourTunes with some of the fixes, so here it is:
ourTunes1-7g.jar

It fixes the file renaming error, and catches an Exception in the JmDNSImpl.java that prevents ourTunes from seeing networked clients - you still may see minor problems with this issue.

However, there is still a problem with ourTunes under OS X. There is a header field in the passing data specifying an
x-audiocast-port: < port number>,
and when I can get back to work on this project, I want to see what data passes on that port. I do believe it’s UDP, but I’d need to double check.

Otherwise, my apologies for the late repost. This weekend was fantastic on campus with the win over UT.

News is rather slow, but so is testing and development.  After looking through a few posts today, I felt that I might be able to post a few code changes and see if it improved certain aspects of the program; however, certain issues are bound to remain in the program.

Note - this updated version is experimental and not really developer tested.  I would greatly appreciate others input…
(1) Often reported by people is the fact that they can’t see the list of shares in ourTunes.

+If you have a firewall enabled, then allow inbound/outbound to the programs java and javaw!  ourTunes is useless without its networking components!
+However, some users were still having problems.  I lengthened the time it takes for an share to report to the GUI; this is to prevent thread interference.

(2) This was a feature request from nearly 3 months ago, but wav and midi files are now supported.  (As a note, ourTunes doesn’t recognize the extension “mid” - it must be “midi”)

(3) ourTunes switched JmDNS libraries to version 2.0 - The behavior changed somewhat from the previous verison of the library causing the word “Tunnel” to appear in iTunes instead of the library name.  This makes it easier to find the mirror, but it’s accidental.

(4) ourTunes no longer shares port 3689 with iTunes; this was done in the hopes that ourTunes and iTunes would play nicer on OS X, but I don’t have access to a mac for quite some time.  I’m hoping OS X users would be able to test this proposition…

—-

Lastly, I’ve read news here and there about Wine on Linux.  With Wine, a linux user is now capable of using iTunes on his machine.  The good news is that ourTunes can run on the Wine platform; the bad news:  A Linux user needs to write an appropriate class that implements ourtunes.os.OS (source code and documentation are inside the file), and then pass me the result of the call System.getProperty(”os.name”).

In future update, I intend to linkify the hyperlinks in the about panel, so please include in the implementation the following method (appropriately, it should launch the web browser and go to the page specified by the URL):

public void launchHyperlink(URL address); //don’t assume firefox is the default web browser on the OS!
Link here:  http://www.webpages.ttu.edu/mroth/tunes/ourTunes1-7f.jar