Yay! Big clean up on IDV3 Tag Decoding for MP3, and at last Album images are working (grabbed straight from the Audio file)

No public release just yet though..

@abalaban

The actual problem I was having with pthreads on OS4 was when using the pthread_attr_setinhertisched() function, it would always fail when I used the attribute, PTHREAD_EXPLICIT_SCHED. (This then meant I coudn't use the pthread_attr_setschedparam() function.)

I think Thomas Frieden then confirmed that this wasn't fully implemented. So instead of mixing pthreads and AmigaOS process related API calls I wrote my own class to ease the handling, which was built up from the standard AmigaOS API calls. (I now use this class all over TuneNet).

Cheers,
Bean.

@abalaban

I switched from PThreads to my own process management system due to a number of non working schedualing functions. Apart from that the implementation was pretty sound.

Cheers,
Bean.

@TiredOfLife

Thanks for the heads up on that one, I'll take a look.

Cheers,
Bean.

@jalih

I don't know much about this, but had a look at the link. Do I understand this correctly, is it like a "virtual" tasks library? All running on a single task, but with the actual application in control of the scheduling?

Cheers,
Bean.

@ChrisH

Yeah, bug fixes are being dealt with at the moment.

I'm quite excited at the new methods for plugins to dynamically update the song information. Not only does this fix a few issues with passing information around processes, it also allows a great deal of flexibility in what a plugin can update. You could for example even have a tune periodically updating an Album cover, like a frame to frame anim (if you so desired), or more practically updating a song title from a radio stream (like the shoutcast plugin does now).

Cheers,
Bean.

@ChrisH

It is true that the interface leaves a lot to be desired and has many inconsistencies in usage and features.

No real thought was ever put into the standard interface. I initially wanted just a simple tool to stream music whilst I worked on other projects and then that became my main project on the Amiga!

Also, going back a few years I just wanted TuneNet's interface to be compact, which is why I opted for those awful arrow selectors to keep things on screen down to a minimum. It doesn't work too well.

With the Skin System, Player, Mixer, Docky, Plugin, Visuals and standard Reaction GUI TuneNet has never excelled in 1 area, more it's been a jack of all (most) trades (but master of none!). I'm trying to solve this by making the inner workings more managable so it is easier and quicker to develop up in the future. This will ultimately result in a better standard GUI.

In my day job the applications we developed were always let down by our interfaces. These days they are much better and aimed at the average user, hopefully I can get that into TuneNet eventually. I'll put a few of your suggestions into the app.

Cheers,
Bean.

P.S. CUPS can still be a nightmare, but is generally a lot better these days!

P.P.S. I hope people at least found addding and playing a Tune a simple task (though I fear people are going to mention the complexities of installing plugins and libraries here!)

@ChrisH

Hiya,

It seems there is a lot in TuneNet that is a little non standard and difficult to use. I actually hate the way I did the arrow button to select the popup menu for the editing functions (it really sucks), so I plan to bring things a little more in line with standards!

A couple of points:

* Clicking on the title headers of the list should sort the list, and then selecting the drop down menu option "re-order as shown" should reorder the list for you.

* If you select Prefs -> GUI Level -> Graphical, you'll get AISS icons next time you start up TuneNet (as long as AISS is installed), with as AJS rightly says, a pause button! I'll bring this into line in a future release so that the text buttons get the same treatment!

* A Full Skin must be downloaded and dearchived, and selecting that directory in the Full Skin selector within Prefs will then set that Skin. Then select the SkinFX Display from the Menu. The full archive on OS4 Depot should include a default skin that you simply have to select "SkinFX Window".

Please make sure the expat library is installed - latest one from OS4 depot!

* I'll look into supporting other versions of the ID tags soon.

* I'll look to put an FAQ on the website.

I've a lot on my plate right now, but if you could hold the MODS till the next ANT meeting I'll look into them then (sorry couldn't make the last one).

Cheers,
Bean.

(Right - Must get on with some code! )

@TSK

Quote:

Sorry, I must have misread / understood. I think it was
the comment about the datatypes that threw me.

At least that's my excuse anyway.

You would still need to parse the files ID3 tags though.
ID3v2 can support multiple images (and it might not be at
the beginning of the file).

Cheers,
Bean.

@Chris

Hi Chris,

Do you mean a varying file format type, for things like the XMP plugin whereby the format playing can be of type "MED", "Protracker".. etc etc...

If so, then no problem - I'll add it in. The new method basically uses a series of TAGS which can be created and passed through to TuneNet for processing. This will happen at the Open() stage and can be dynamically/periodically updated whilst playing at the DoNotify() stage.

Cheers,
Bean.

@kas1e

What Window do you mean exactly?

The skinnable window system is definable via the Skin, and it's possible to make the whole window draggable if you want the skin to react in that way (it's down to the skin XML construct at the moment).

However, for the Reaction GUI it follows the standard system rules and behaviour. I don't know if there is a setting in the GUI WB prefs for this - I can't recall.

As broadblues mentions there is a keyboard control to move the whole window.

Cheers,
Bean.

@TSK

The embeded pictures can be different formats, see the debug output below from my tag reader, so the resulting data will need to be passed through datatypes.

Anyway, I've now started to tackle the handling of more Tune Information including pictures. It is now very easy to provide a multitude of information from a plugin back to TuneNet.

Cheers,
Bean.

****

idv32 "mp3:Mr BriteSide/01 Mr. Brightside (Club Edit).mp3"
** idv32: ? 2005/2009 by Paul Heams **

Compiled with examine mode on

Clearing pointers
Reading File
IDV3 tag found
version 2

... SNIP ...

ID : PIC - (Size of block is 103216 bytes)
comparing images..Mime Type = JPG (4) Read in Picture Number = 0,

Attached Picture

************************************
** Found 6 bits of requested info **
************************************
[Title ] : Mr. Brightside (Club Edit)
[Artist ] : Jealous Guys
[Band ] :
[Album ] : Mr. Brightside - EP
[Genre ] : Fusion
[BPM ] :
[Copyright] :
[Comment ] : iTunSMPB
[Image 0 ] : 0x67e24000
[Image 1 ] : 0x000000
[Image 2 ] : 0x000000
[Image 3 ] : 0x000000
[Image 4 ] : 0x000000
Free Image (object 10)

@MichaelMerkel

TuneNet natively supports ID3v2 tags, but that's about it.

Looking back at where I left my tag reader I'd already written the code to pull out images but this has never been integrated into TuneNet.

Some malformed ID3v2 tags are supported (like a certain version of Apple's iTunes), but TuneNet has a very simple and strict (and as such not very flexible) tag reader that I wrote, to this spec: http://www.id3.org/id3v2.3.0

@SpotUp,

I'll see what I can do.

@All,

I've noticed some serious bugs with the Internet Radio Scan and Search, I'll be looking at this next.

Thanks,
Bean.

OK, you'll find a version here with the bug mentioned above fixed:-

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

As usual I'll be interested to know how people get on, hopefully no more straight off freezes.

V86.66

* Fixed the number of sound allocations for the AHI User Mode
* Message System - Internal Changes
* Updated 1st time start message.
* AHI Audio 0 is now the default mode for new users.

Cheers,
Bean.

@redfox

The bug should only affect AHI User Mode audio, and not a straight AHI Audio 0 selection, so the problem you mention may still remain even after this next release. Can you let me know what version of AWeb you are using? I'll download it to try and reproduce once the next version has been made public ( the fix for the fix for the fix version ).

@sundown

Oh #@?!, I think I've found the bug that people who use the AHI User Mode have been getting.

Damn, it looks like whilst trying to find the issue with the Audio being at half volume I've mis-overtyped a number within the Audio Output source file.

A source comparison between V86.52 and the current one confirms it.

Damn, sorry guys. I'll get a fix out tonight, in the meantime just switch to Audio 0 / 1 / 2 or 3 in the Audio Mode prefs, save, reboot (to be sure) and play.

In the next release I think I'll make Audio 0 the default mode, rather than the User Mode (Music Unit).

Cheers,
Bean.

@kas1e

It looks like the issue may be down to the AHI User Mode as Kas1e mentioned, but I'm not sure if it is that in general, or a particular driver, namely the "device Unit 0 audio mode" driver.

If people are using the above they shouldn't have to anymore as you can select AHI Audio 0 from the TuneNet Preferences (General Tab->Audio Mode).

If people are expriencing solid freezes and really bad stability then please could they list what Audio Mode they are using, and if it is a User Mode what driver "AHI Mode" is selected, IE: VIA-AC97:HiFi 16 bit stereo++".

I want to get to the bottom of the issue.

Thanks,
Bean.

@sundown

Kas1e is kindly doing some testing for me. Hopefully we'll get to the bottom of the issue.

Cheers,
Bean.

@all,

Well it seems like I've right gone and stuffed something up! lol!!

I suggest everybody goes back a few versions till I work out where the issues are and why my machine is impervious to bad buggy code!!

Sorry guys.

Cheers,
Bean.

@Thematic

Hi, vast as in it doesn't work anymore?