Hello,

Does anyone know if there is a some form of SDK available to take advantage of new OS4.1 features? I'm particularly interested in using the GFX compositing engine for enhancing the skin capabilities within TuneNet.

Cheers,
Bean.

@PEB

That looks pretty neat! Though there is no technical documentation or source in the archive unfortunately.

Cheers,
Bean.

@abalaban

That's now fixed, thanks for the report.

Still working my way through some issues, next release will be soonish I hope.

..Oh and OS4.1 is really good. Is there any news on a newer SDK? Specifically I want to experiment with the new compositing engine for skins. I've been out of the loop for a while, so I've no idea what is what these days.

Cheers,
Bean.

OS4.1 is waiting for me at home! :)

@spotUP

Lol! just answered that question on the AmigaWorld forum! Have a look over there.

Cheers,
Bean.

@spotUP

Cheers Spot, I'll update the plugin list over the weekend. ..and also try some of them out!

@Mikey_C

Quote:

Thanks! I'll put the kettle on!

Hello!

I've put an update together that should solve the current station listing problem.

I've only included the binary (and icon), so simply replace the current executable.

Also included are a few changes to the player code which might help to solve a few problems reported previously.

The update can be found here:

http://tunenet.co.uk/download.html

..at the top.

For the record I'm still developing TuneNet, though it's true I've not really been using my Amiga lately. I've been lifted by news that OS4.1 is out and am interested in the new graphics engine for obvious reasons (skins). So I've put in an order for it for my A1 and hopefully this'll get me back into things.

I'll be back soon, hopefully to give my impressions on OS4.1!

Cheers, and thanks to all that use TuneNet.
Bean.

Hi Jack,

I'll take a look at the weekend and see what I can find (sorry no time these days). I'll also try out AMuse, it looks good from what I can see of the screenshots.

Cheers,
Bean.

@Chris

Wow, I've been away to long, all these suggestions. Come to the next Ant and we'll discuss.

Cheers,
Bean.

@Raziel

The crashog supplied suggests that a the save playlist is failing, specifically a file write. I'm wondering if a plugin is the cause of it (memory / file system errors). It's possible that a clean up on one of the plugins is not cleaning itself up properly.. Maybe, it cleans something up from TestPlayer() that is never used when you don't open a song??

Can you:

a/ check all plugins are up to date and reboot.

b/ Clear down to 0 plugins and launch / quit.

c/ Add a plugin, and keep doing step c until the problem occurs then note which 2 plugins were last added.

Thanks,
Bean

@salass00

The system now correctly truncates to the max number of players (64). I will make this dynamic on the future, the playlist, radio list and other things all use lists (actually a mini DB class I wrote). I was just a bit lazy in the plugin department! :) I will follow up your suggestion.

Cheers Bean

@Raziel

Typing on a mobile device so this will be short!
Skins : Have you installed the expat library? See TuneNet site downloads for details. If so try one of the example skins ( lights ) that definately works.

Aweb : Can you describe fully?

Plugins : I'll check the crashlog when I can get to an Amiga?

Cheers,
Bean

@bean

OK, Service release in OS4 Depot queue, which fixes the bugs mentioned above.

The next full version will have newer features.

Cheers,
Bean.

@bean

Whoops. Only 24 plugins are allowed, and the check code is messed up. Sorry all! Anything over 24 players will start to corrupt memory, please remove some players for the time being.

I'll get a service release out as soon as possible.

Bean.

@salass00

I didn't realise there were so many plugin's available. I'll check the code as I thought I'd put a limitation in there. Looks like that limit code isn't working and it's trashing the place.

The plugin pointers are held within a static array and not a linked list, and there should be a limit. I'll make sure that limit goes up (64 be enough?) and that the limiter check works.

Cheers,
Bean.

@salass00

Good to hear you've found it!

Cheers,
Bean.

@salass00

Can you try the following.

1/ Empty out all plugins except the defaults, and try to recreate the problem. If not then...>

2/ Add a single plugin in one at a time and try to recreate.

You'll have to restart TuneNet each time.

I think it's probably a bug in one of the plugin detections (Test) functions. Where by it's doing an extensive test on the file (not just filename or first few bytes) and that is making it fall over.

Also try all the above from RAM DISK: as well.

Let me know how you get on, I've got some time this weekend in between GT5 to look further into the problem

Cheers,
Bean.

@salass00

Hi,

I can't recreate that bug. Are you sure it's not a problem with a particular plugin? Does it occur on mp3 files for example?

Cheers,
Bean.

@All,

Lol, these are very cool.

Have a good Christmas (holiday, break, whatever!) everyone.

Cheers,
Bean.