For the record I have fixed the center window problem for p96_pip and made the code general by moving it to cgx_common.c
Thank you
Quote:
Some of your enchantment request should maybe be added to bug tracker, I think my focus has to be on the real bugs.
Yep, however all of them are problems, smaller of bigger aren't too mutch different as we presume to have all of them fixed (soon or later)
Would be logic to reimplement atleast all the old features from the afxgroup (minimum) rathen then continue our spare test with 1000 different versions, that's why i start from the small different things first
Aniway from now on i will report all the issues (bug or request) in the official bugtracker, it will be better for you ..
Yep, however all of them are problems, smaller of bigger aren't too much different as we presume to have all of them fixed (soon or later)
Core mplayer (codecs) crashes is low priority as this will maybe be fixed whit Mplayer core upgrade.
DSI/ISI Crashes in Amiga components AREXX/Video output/Audio output is high priority, that also includes all options that video output driver supports.
DSI/ISI Crashes in start-up or shutdown code is also high priority.
Nice to have should be medium priority.
Things that act strange, depending how easy it is to reproduce the issue fixed or not, medium to low priority.
DSI is high priority because it can result in system instability, ISI can be a sign of bad function pointer or memory corruption, so there for its also high priority.
Quote:
Would be logic to re-implement at least all the old features from the afxgroup (minimum) rather then continue our spare test with 1000 different versions, that's why i start from the small different things first
Well I like to make shore every thing works before moving on, it just makes it easier to know what failed, and I also think its easy to focus.
Quote:
Anyway from now on i will report all the issues (bug or request) in the official bugtracker, it will be better for you ..
Thank you, its easier to work when I have a TODO list instead of trying to remember what page in comments where posted in this forum.
Well the bug tracker can't handle it, but if I make the bug rapport my e-mail address in the bug tracker, so the person who reported the issue does not get a e-mail when its fixed, or when the developer (mostly me it seams) make a comment.
The only thing I hate about code.google.com is that I can't edit my comments, anyway all the bug trackers I have tried does not support that, well its free so I cant complain really.
Anyway there is a RSS feed at code.google.com.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Sorry for saying something probably already known, however I installed liveforit mplayer with the reaction gui (all default settings) and if I switch from full screen to window mode, because I have the transparent windows, the movie windows would remain semi transparent. By clicking on it, it become not transparent, but after few seconds the focus goes automatically to the gui window and obviously the movie window return semi transparent.
This is quite annoying. I don't know if it is a problem of player or the gui.
You might try to merge with your code now rathen then still waiting forever for Varthall, even because he seems in sleep mode again..
Quote:
DSI is high priority because it can result in system instability, ISI can be a sign of bad function pointer or memory corruption, so there for its also high priority.
Of course, luckly stability seems relative good already .. for what i know still a crash with the SDL driver (at exit) but this one was already know, i'll report it aniway:
Well I like to make shore every thing works before moving on, it just makes it easier to know what failed, and I also think its easy to focus.
Problem is that for certain (already reported) issue we need a reimplementation of all the old features first, for example: the "mute" option doesn't work when selected from menu (in afxgroup version), but right now you didn't reimplement any menu in your current fork, so the "mute" option can't be tested because your version doesn't have any menu ..
That's why i suggest you to re-implement ALL the feature first (from the original afxgroup) with an HIGH priority for all the future test
Quote:
Thank you, its easier to work when I have a TODO list instead of trying to remember what page in comments where posted in this forum.
Well the bug tracker can't handle it, but if I make the bug rapport my e-mail address in the bug tracker, so the person who reported the issue does not get a e-mail when its fixed, or when the developer (mostly me it seams) make a comment.
The only thing I hate about code.google.com is that I can't edit my comments, anyway all the bug trackers I have tried does not support that, well its free so I cant complain really.
Anyway there is a RSS feed at code.google.com.
Yes that's true .. however i'm still following the SVN pratically everyday so i can track easily if a problem is fixed or not .. i think there will be no problem for any eventual betatester
Quote:
By the way the PUBSCREEN issue is also now fixed.
Do you mean the buggy "white stripes" reintroduced in p96_pip since the latest 4.2 release ?
Do you mean the buggy "white stripes" reintroduced in p96_pip since the latest 4.2 release ?
No I have not worked on that one as I mostly do development on X1000, its a bit hazel to work p96_pip as I need to copy files to AmigaONE-XE, to check what it looks like etc.
Anyway I need to check if the center screen fix works.
No I have not worked on that one as I mostly do development on X1000, its a bit hazel to work p96_pip as I need to copy files to AmigaONE-XE, to check what it looks like etc.
Probably it's caused by your latest modifications of the the aspect ratio, since 4.2 (with p96_pip) i have that strange stripes in fullscreen, while with cgx_wpa now the window will be autoresized for no apparent reason
Yes, window resize feature seams to do that, the problem is not that it try's to resize it, the problem is that it does it incorrect, anyway I think I have fixed that one.
changed some calculation from LONG to ULONG, I hope that solves it, I have not seen the issue after I changed it anyway.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
I get anywhere between half and 4 seconds of a very bright washed out image that turns to a pure white display unless it's a still image (youtube style) then it only gets brighter if the image changes for a slideshow type file.
I guess its like that because you made inactive windows transparent in workbench GUI prefs, mplayer can't take make it self active window, because other programs might need to be active window, anyway I think there is window tag I can set to turn transparency off on the mplayer window.
Edited by LiveForIt on 2014/5/20 21:58:58
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
I tried a couple of videos .vob and .xvid with your port on my sam460 with radeonHD 4670 and it seems to work, i don't know if the aspect ratio is correct because i compared it with dvplayer and liveforit port and they show the aspect different
Sam 460EX, 2Gb Ram, Radeon R7 250, AmigaOS4.1 FE A4000 PPC604@233, Mediator A1200 PPC603@160, Mediator uA1 G3@800, 512 Mb [sold]
Do you have the gui option to open control panel set? If you do, it defaults to allowing the control panel to take the focus off the video window. This results in transparent video window, which as you say is annoying. This behaviour can be turned off from an mplayer gui setting. Sorry not home right now to direct you exactly, but it is not hard to find.
I tried a couple of videos .vob and .xvid with your port on my sam460 with radeonHD 4670 and it seems to work,
Some benchmarks compared to LiveForIt's -vo comp would be nice now that it's working on RadeonHD cards. It's probably much slower on a X-1000 (if someone want's to compare them on a X-1000 please use the non-altivec version of the LiveForIt MPlayer), but on a Sam460ex my video output may be faster, and it should be possible to make it even faster by adding support for onchipmem.resource, but that only makes sense if the current version is already faster than -vo comp on a Sam460ex with RadeonHD gfx card.
Quote:
i don't know if the aspect ratio is correct because i compared it with dvplayer and liveforit port and they show the aspect different
No idea about DvPlayer, LiveForIt's MPlayer doesn't have monitor aspect support, but what I'm doing may be wrong as well.
@TiredOfLife Quote:
With the beta 11, I have been able to watch youtube clips at 360p (MP4) using SMTube and the M9 on a Sam440EP.
Are you downloading the videos with SMTube, or are you using streaming?
No idea about DvPlayer, LiveForIt's MPlayer doesn't have monitor aspect support, but what I'm doing may be wrong as well.
Aspect ratio in liveforit mplayer, is base its calculation on the screen mode selected, if the user has selected a screen mode whit a 4:3 aspect ratio it assumes the monitor is 4:3, if the user has selected a screen mode that is 16:9 then, the program thinks you have 16:9 monitor.
In full screen it can go wrong as try's to find screen mode that fits the video aspect width and height, whit out knowing what the monitor aspect ratio is, I don't really like the code it looks inefficient and over complicated, and it does not have idea what monitor the user wants to open the screen on.
I assume most screen modes are correct as the monitor provides this modes trow DDC, so in most cases the aspect ratio should be correct.
Edited by LiveForIt on 2014/5/21 7:39:51 Edited by LiveForIt on 2014/5/21 7:40:21
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
About benchmarking, or using the new version in upload queue on OS4Depot.net
When using mplayer on Sam440/AmigaONE-XE/AmigaONE-SE with old Radeon 9250 card. (I assume on-board graphics on Sam460 also its better whit RGB then ARGB.)
As the bitmap format will be wrong, and I guess its going to run slower on this computers with old graphic cards.
cgx_wpa does not yet have support for option rgb, and will use argb by default in my build.
Edited by LiveForIt on 2014/5/21 7:48:16 Edited by LiveForIt on 2014/5/21 8:20:21 Edited by LiveForIt on 2014/5/21 11:24:12 Edited by LiveForIt on 2014/5/21 11:25:07
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
