Just upated to latest release and for some reason every MP3 file is played twice before moving onto the next? Can't see anything in the pulldown menu's saying to repeat a song etc. or maybe I'm just missing somehting right in front of my face ...wouldn't be the first time eh

Last edited by klx300r on 27-Dec-2022 at 04:05 AM.

_________________
____________________________
c64-2sids, A1000, A1200T-060@50(finally working!),A4000-CSMKIII
! My Master Miggies- Amiga 1000 & AmigaOne X1000 !
mancave-ramblings
X1000 I BELIEVE

@klx300r

when was it updated last? any hope for OS4 fixed version.

Last edited by NutsAboutAmiga on 27-Dec-2022 at 04:10 PM.
Last edited by NutsAboutAmiga on 27-Dec-2022 at 04:09 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@NutsAboutAmiga

Some months ago I offered myself to the author as a beta tester to point out the problems with the program under os4 , but he refused saying he wasn't interested... but the source is available so someone else could do it if he wanted to

http://bax.comlab.uni-rostock.de/~bj/software/eagleplayer/

Last edited by samo79 on 27-Dec-2022 at 06:08 PM.

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@klx300r

Hey!

Maybe something about "Songend" and "No New Module"?

Take care!

_________________
Tygre
Scientific Progress Goes Boing!

@samo79

I can understand if it's intended for real Amigas and OS4 isn't considered real Amiga enough. But, if the problems reveal an actual bug in the original source code then that's a bad attitude. I think we are all a bit too old for making excuses about things still working by accident on AmigaOS even after finding out if they trash memory.

@Hypex

That depends, if was in general, or if was because the bug report came from the wrong people.

many Amiga developers don’t have the time they used to, they don’t have the same motivation, and don’t have the hardware to verify or see the bugs reported, working in the dark, trying to find bugs they don’t find.

A bug report has to be relevant, its supposed to not work, wrong target hardware, or not working because of an actual bug. To be honest, most bugs report are useless.

This thing has to be debugged without JIT compiler enabled, to see 68K registers, and we need to put a lot debug text to see where things go bad, I believe totally freezes my computer.

I think a good milestone should be getting it at least NallePuh friendly, getting complete system friendly can be too much work.

Last edited by NutsAboutAmiga on 28-Dec-2022 at 10:19 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@tygre

thanks that worked for not playing the same song twice ..now to play with stuff to randomly start the next song in the folder

_________________
____________________________
c64-2sids, A1000, A1200T-060@50(finally working!),A4000-CSMKIII
! My Master Miggies- Amiga 1000 & AmigaOne X1000 !
mancave-ramblings
X1000 I BELIEVE

@klx300r

Enjoy

_________________
Tygre
Scientific Progress Goes Boing!

@NutsAboutAmiga

The problem is most Amiga programs were coded without an MMU. So they could be trashing memory and no one would be the wiser. In fact, I found a few did trash memory, but because it didn't crash they still worked. Even when MMUs were available the developer need to have one installed and actively using it for testing. I don't know if many commercial Amiga companies did that.

On top of that is the hacker culture. Where people liked to hack into the OS or peek and poke at internal structures. All those combined is a recipe for disaster.

So one thing OS4 was good for was testing 68K software. I found with basic MMU protection bad apps tripped up straight away. Then after some update it became more strict. Some stuff I had written in 68K days started crashing. I found I had passed a string to DOS function, but missed the note that it needed to be parsed first, so it crashed. It wasn't intentional, but I had ignored the instructions, and was now paying for it with crashing software. Lol. A more common but perhaps less known example would be OpenFromLock(). I've missed it before but it closes the lock! In the 68K olden days this would simply be missed. But, it is filesystem dependant how it reacts, and on OS4 it will freeze or crash the system! The function examples really should have thrown a yellow alert where misuse was found and they did in some cases. But memory trashing is harder to find and so here we are today.