@kas1e

Nice Video!

@kas1e

Did V86.52 work (current one on OS4Depot)? Because the difference between these two was ridiculously slight! Literally the order of some function calls on exit.

@nexus

The station search was patched up recently, but if you are still having problems please let me know.

@kas1e

Hmm, looks like it's going to need further investigation. I'm wondering now if it's some kind of timing issue.

What previous version ran without issue?

Thanks,
Bean

New test version available. I'd be interested to see if the Opener bugs have gone for those who had them.

http://www.tunenet.co.uk/download/TN8664.lha

* Fix for non thread safe players (Curty's Sid Player should work again now)
* Players are registered and de-registered safely now.
* DSI memory hit error in player removed.

Many Thanks,
Bean.

@AJS

New as in the version I've been working on for the last week or two. It has some changes in the way TuneNet deals with the opening and closing tracks, and and few player bugs fixed up.

Cheers,
Bean.

..> I've OWB, Cubic, Sashimi and TuneNet running. Seems all good here, and that's whilst coding and testing changes.

@AJS

Just testing the new TuneNet with it. Mikey you haven't made it crash yet

Cheers,
Bean.

@broadblues

I'm hoping the next release will make things more stable. I've come accross a few issues, and have re-implemented the way in which tunes are terminated. There was also an issue with the Opener which could end up writting to a random bit of memory under certain conditions..

Cheers,
Bean.

@Tuxedo

I can't really see the point of testing for this until the standard crashes have been dealt with first. Once everyone is able to use TN without all these Grim crashes happening then we'll see if that has made a difference to your hard locks and go from there.

Cheers,
Bean.

@spotUP

Quote:

It's hard to tell! I seem to be one of the few that doesn't suffer from them! :)

I'm about 50% through the changes for it, so we'll know soon enough.

@redfox,

The disable on the "Scan Now" button was just to prevent the user from scanning too often. It is fine to double click stations whilst it is disabled, scanning, or in find mode - at least it should be.

@RacerX,

It's on the list for implementation.

Cheers,
Bean.

@kas1e

Thanks for the info. The odd thing is the player/opener code has hardly changed from V0.86.50 to V86.60. I've identified several problems (as I mentioned previously) I hope they are the cause.

Cheers,
Bean.

@Mikey_C

Indeed :)

Na, it's all good. I want to know why TuneNet works well on some machines, but crashes on others - I'll get there.

Cheers.
Bean.

P.S. Got myself a great 1080P monitor, so I'm viewing my Workbench in fabulous 1920x1080 res, makes a hell of a difference when programming! :)

@Snuffy and @kas1e,

I'm currently re-implementing the Opener() process as I've identified several potential issues with it.... This may take a little time..

Cheers,
Bean.

@kas1e

Hmm, this is going to take a bit of tracking down. Would you be interested in trying out a test version to try and locate the issue? If so could you PM me your email address?

In any case please could you answer the following:

1/ What is the full path and filename to the file you were trying to load?
2/ Does the same problem occur if you open an AIFF or PT module?
3/ Have you tried a variety of MP3 files (or the same one each time)?
4/ Has TN ever worked for you?
5/ Are you in GUI , SkinFX or Docky mode? (Please list docky / skin in use).
6/ Are you playing with an AHI device number, or Music Unit (User Mode)?

Many Thanks,
Paul.

@kas1e

Please can you remove the XMP plugin, reboot and retry your test.

I'm not saying that is the issue, but you should really test with the standard plugins only so I can be sure TuneNet is the culprit!

Thanks,
Bean

@spotUP

I'm concentrating on stability at the moment. It's getting better (V0.86.60), but I'm not there yet. After that comes additional functionality for organising the music, and then I'll restart the post processing plugin fuctions.

Cheers,
Bean.

@redfox

Please can you try this new exe and let me know if it is any better.

http://www.tunenet.co.uk/downloads/tn8660.lha

V0.86.60 - 1st July 09
* Fixed issues with sequence of message replies.
* Fixed textual crash bug with the SkinFX ListBrowser gadget.
* Radio scanning was broken and could cause Reaction crashes.

Cheers,
Bean.

@Tuxedo

No. At the moment I just want to get it fully stable and cleaned up. Then I'll think about expanding it, however, that said you can play CD tracks using the AIFF player, but of course there is no CDDB support.

Cheers,
Bean.

@kas1e

I've found 3 bugs, one with the station list (whose methods changed in 0.86.54), one to do with messages collection (which might be the cause of the freezes), and another to do with the SkinFX playlist. I'll put another test release up later in the week.

Cheers
Bean.

Update

I've fixed all 3 issues and am currently testing it. I hope to have a new release for tomorrow.

@redfox,

Regarding the solid freezes I really don't know what to suggest. I'll need some kind of Crash log to understand what is going on. Certainly it's something I can't reproduce.

After it next crashes soft reboot and type C:dumpdebugbuffer > ram:debug.log and PM me the debug.log file (it creates in ram).

Also please make sure you only have the standard plugins installed (remove all old ones whilst testing). Test after a hard reboot only.

Thanks
Bean.

@pjs

There are no ARexx ports yet, what you are seeing are Tasks running. (The AmigaAmp one allows the AmigaAmp scopes to work with TuneNet).

In the mean time you can control TuneNet in the following way:

1/ Launch TuneNet (from Workbench, or in daemon mode from CLI (tunenet -daemon).

2/ Then launch the TuneNet execuable again from CLI with one of the following parameters.

-stoptune Stop the current tune
-restarttune restart the current tune
-pausetune Pause toggle
-addtune Add tune without playing
-nexttune Next tune in playlist
-prevtune Previous tune in playlist
-nexttrack Next track (sub-song)
-prevtrack Previous track (sub-song)
-quit Kill TuneNet Processes

... you'll see that instead of launching Two TuneNet's the second one will control the 1st.

Anyway, type TuneNet ? from the command line to see a full list of options. You should be able to program your multimedia keys like this, for basic functions, until I get an ARexx port in place.

Cheers,
Bean.