Mediabrowser playlist doesn't advance to next track

I have just purchased the pro license to enable the mediabrowser functionality.

I have just dragged 4 songs to the playlist 'bar' on the web page (two songs from two different albums, all flac files). Each plays find, but when a track ends the next does not start automatically.

However, if I do the same with mp3 files, the next track begins to play automatically.

This problem seems to occur with all flac files. A single folder of mp3 files will play each in turn, but a folder of flac files will not.

[zip]

Can you try a different browser?

ok.

I've tried with IE9, Firefox and Chrome.

Chrome works fine, but IE9 and Firefox don't. I also noticed that the track timer seems to indicate that the track stops about 2 to 3 seconds before it's end.

[zip]

Looks like a problem with the Flash / Flow Player in those browsers

Ok, even if we blame the flow/flash player for the playlist problems, then even in chrome when playing files in a folder (album) the next track does not automatically play as it does with a mp3 encoded track.

It now failed on chrome - so that's all three browsers.

Are there any logs that would show if these is a BUG in mediabrowser or maybe a problem with the flac encoding (done with linux abcde)?

[zip]

I'm planning to move to html5 with a different player in future, so not going to spend much effort fixing this, especially as it seems out of my control.

Ok.

So, when do you think you'll move to html 5? Will it be in version 1 or version 2? If not soon and version 1 can I have a refund as I paid the license to use media browser and it appears not to work correctly (no use blaming other peoples code if your product relies on 3rd party module for which there is no alternative)?

Maybe there should be a note on the media browser page warning that it does not work on flac files (even though they are listed as supported).

[zip]

It'll be in version 1 so your license will still work.

[Xmantium]

I'm planning to move to html5 with a different player in future, so not going to spend much effort fixing this, especially as it seems out of my control.

Great news for iOS and Android Chrome users!!