Your using "-lavdopts skiploopfilter=none", this setting is slower, but produce better picture quality. Try "-lavdopts skiploopfilter=all" it should run faster.
Rapport have not been frequent from the AmigaOS4 Sam460 Beta testers, I don't know if you can or not play 720p on Sam460, but lets say a strongly doubt it. I have not gotten the feed back I need to say it does or does not yet.
Your version of mplayer is old, there are meany things different between the new mplayer and the mplayer your using. There have also been additional changes in AmigaOS4.1 Final.
So for now lets just wait for AmigaOS4.1 final, and we will know then.
Edited by LiveForIt on 2014/11/28 3:14:19
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Your benchmark results, shows the X1000 in action, it does not say anything about the speed of mplayer on sam460.
PA6T chip runs a 1.8Ghz, the AMCC460ex Soc runs at 1.1Ghz. (Diff 700Mhz) PA6T has AltiVec, the AMCC460ex Soc has no AltiVec. In other words the PA6T is many times faster then AMCC460ex SoC.
I don't know if "-lavdopts skiploopfilter=none" is ignored when in the command line argument or not, when you have it in the config file.
Edited by LiveForIt on 2014/11/28 3:32:43
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
That seems awfully slow, try skipping all filters as liveforit suggested and after a reboot with nothing else running eg. browsers etc.
In theory according to acube your CPU is 1.1ghz, so your VC seconds should be under double mine not over 5 times longer. I didn't think the Altivec makes that much difference.
Amiga user since 1985 AOS4, A-EON, IBrowse & Alinea Betatester
75.052/189.858 * 100 = 39.58% less time to decode the video.
Mplayer AltiVec playback is 1.65 x faster then none AltiVec.
1.800 Ghz * 1.65 = 2.970 Ghz
A none Altivec computer will need to be 2.970 Ghz to have same computer power to decode a 1080p video with out AltiVec, as The X1000 with AltiVec.
Edited by LiveForIt on 2014/11/28 4:45:07 Edited by LiveForIt on 2014/11/28 4:46:04 Edited by LiveForIt on 2014/11/28 4:47:42 Edited by LiveForIt on 2014/12/3 0:30:44 Edited by LiveForIt on 2014/12/3 12:19:43 Edited by LiveForIt on 2014/12/3 12:21:24
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
----- the requestor ------ AmigaDOS Please insert volume http: in any drive Process: 960 "mplayer-altivec" -----------------------------
If I Cancel the requestor, it reappears. Upon the 2nd Cancel, another appears. But when the 3rd one appears, then a Cancel allows the program to play as I had hoped.
My 5 questions: 1) Should I put this at the bugs list? 2) Is there a "how to use LiveForIt-MPlayer" that covers an error on my part? 3) Did I not get all of the documentation? The 2 README files mention documention that is not in this directory. 4) Where should I be reading/asking about liveForIt-MPlayer? and 5) I am used to typing Control+c to stop MPlayer, but now that hangs the program and window. Though I have discovered that opening a separate window and typing STATUS to find the <#>, then BREAK <#> ALL does cause a graceful exit, I have no way of knowing if this the accepted way or not? So. Is Control+c a feature request? Defect? or "Other"?
Thank you, George Wyche
=========== The computer setup =============== I am using X1000, most recent updates, downloaded liveforit-mplayer from OS4Depot last night. There is no installation so I put it directly into my Work2: an SFS-2 partition. My principle use of any mplayer is for internet audio streams.
No, just wait for AmigaOS4.1 final, and next mplayer, I think the bug was fixed a long time ago, do you have the last version of mplayer I uploaded to OS4Depot.net, or did you get it from some where else?
The AmigaOS requestor should be totally disabled, from mplayer.
2) Is there a "how to use LiveForIt-MPlayer" that covers an error on my part?
mplayer -vo comp:help (or at least in the one the beta testers have)
you can also send "help" as AREXX command to get the commands you can use in AREXX. (They are mostly the same the ones you pipe to mplayer in Linux)
3) Did I not get all of the documentation? The 2 README files mention documentation that is not in this directory.
Maybe, I only copy docs, I think is useful to the users, to distribution directory and compress it using LHA. Anyway there are lots tips on the nest on Linux forums.
4) Where should I be reading/asking about liveForIt-MPlayer?
Here is just fine (preferably under a new topic), my blog is also ok, because we are taking about a different topic in this one.
Don't expect answer in the comments on OS4Depot.net, I get no alert if anyone post there, and I don't check that often.
Edited by LiveForIt on 2014/12/1 13:23:27
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
I am not at all clear about HTTP Handler. Besides, I don't want my setup to differ from "stock", i.e. no workarounds that I am quite likely to forget are in place.
My "work around" is to use the command line and suffer the 3 [Cancel] clicks AND starting another window just to do BREAK for a graceful exit.
About documentation: I am not too good at automatically substituting "Amiga (and supposed obvious translations)" for Linux specific info.
I was looking for a "what is different for the Amiga MPlayer vs Linux" or where ever this code is derived. Maybe just a compile switch listing? then I can at least see what to NOT to follow along in the Linux documentation. I have followed along with (for the most part) the discussion about the various flavors of mplayer that are currently being worked on for OS4.
I'm never, ever sure how much to continue to soak up before asking specific questions. MPlayer is a good example of that, because of what I did read about the mplayer linux documentation was/is voluminus with many options. I'll mention again that my principal interest is in the audio for internet radio.
Thanks for your suggestion, anyway. I did go do some reading about the http-handler, but the questions mounted up faster than the answers, affirming my decision to stick closer to "stock".
George Wyche PS. I do make non-trivial donations for the software I use, so this conversation might be more than just to an enthusiast. Thanks.
I am not at all clear about HTTP Handler. Besides, I don't want my setup to differ from "stock", i.e. no workarounds that I am quite likely to forget are in place.
My "work around" is to use the command line and suffer the 3 [Cancel] clicks AND starting another window just to do BREAK for a graceful exit.
I think its part of AmigaOS4.1 as standard, its just not enabled by default, copy the http device from devs:storage to devs:dosdrivers this will enable it.
What this does is that you open text documents from http: device, with application support internet or network as its all handled in the http: device.
Quote:
About documentation: I am not too good at automatically substituting "Amiga (and supposed obvious translations)" for Linux specific info.
?
Quote:
I was looking for a "what is different for the Amiga MPlayer vs Linux" or where ever this code is derived. Maybe just a compile switch listing?
No, AmigaOS is not Linux OS, so there is lot of things that goes into making it work on AmigaOS as it does, the change log you can see at code.google.com.
The latest changes for comp_yuv / comp_yuv2, and newest mplayer has not been uploaded as the work involved in supporting hardware accelerated video in AmigaOS4.1 was a secret up until AmiWest.
The code it self is useless unless you have a updated AmigaOS4.1 SDK, and AmigaOS4.1 Final, the latest changes will be released when a new SDK is out, and the AmigaOS4.1 final is out.
Quote:
then I can at least see what to NOT to follow along in the Linux documentation. I have followed along with (for the most part) the discussion about the various flavors of mplayer that are currently being worked on for OS4.
Well you have 2 mplayers, MUIMplayer that is based directly on work by Fabian (FAB) a MorphOS developer, as he does not wont hes work in repository.
I have decided to work on different branch of mplayer a port done by afxgroup (Andrea Palmate), of course there has been other developers as well who has worked on this one, this version of mplayer is closer to the Linux version, as it has no native GUI integrated.
How ever there is external GUI made by Daniel Westerberg for people who don't like to type things in shell.
Quote:
I'm never, ever sure how much to continue to soak up before asking specific questions. MPlayer is a good example of that, because of what I did read about the mplayer linux documentation was/is voluminus with many options.
Yes indeed it has many options.
Quote:
I'll mention again that my principal interest is in the audio for internet radio.
Have you considered that mplayer might not be the best music player? Have you tried TuneNet and AmigaAMP?
Quote:
Thanks for your suggestion, anyway. I did go do some reading about the http-handler, but the questions mounted up faster than the answers, affirming my decision to stick closer to "stock".
well if you don't wont to use http-handler, I suggest just assign http: to RAM: this will mute any request for inserting http: into any drive.
The issue is that mplayer first try's to open it as file, if this fails, it move on to trying to connect over TCP/IP, on Linux this not a issue because there are no volume and devices. But on AmigaOS we have so, AmigaOS think http: is volume or a device, so it ask for you insert that floppy disk with that name so to speak.
Quote:
George Wyche PS. I do make non-trivial donations for the software I use, so this conversation might be more than just to an enthusiast. Thanks.
Well lets put this way, I work on mplayer because I like to play good quality movies, and if get payed for it in the process its bonus.
I don't normally do things for free unless its some I wont, of course I'm willing to do things for money, I'm a capitalist, I take donations for the work I do not the product, the product MPlayer is under GPL and can't be sold. I'm not interested in a MOAP.
There are lots of developers who has contributed to mplayer over the years, I don't think they like it if the product was sold.
I don't have lot time this days having a day job, that is not paying, right now. So if its some thing that you wont me to do it better be worth my while.
Edited by LiveForIt on 2014/12/3 3:06:32
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Comment 1: The first benchmark show the 720p movie being played in 616.826 sec with skiploopfilters=none, so its 21 seconds slower then normal playback speed.
Comment 9: The 2en benchmark show the 720p movie being played in 585.452 sec, with skiploopfilters=all, so it plays the movie 11 sec faster, then the normal playback speed.
So the 2en benchmarks show that 720p video can be decoded on Sam460, but here is the catch this is with out displaying a picture and with out playing any sound.
If the Sam460 can play a 720p video it will be just barely, with hardware acceleration we have now. As pointed out by djrikki you need AmigaOS4.1 Final, for DMA support, you need the latest HD 2.4 drivers to enable composition video.
Its anyone's guess, there is limit to what the hardware can do, on the software side there is lot that can be done like UVD and VDPAU, but this things is not present in 2.4 drivers.
Edited by LiveForIt on 2014/12/3 2:52:39 Edited by LiveForIt on 2014/12/3 3:11:28
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
I think its part of AmigaOS4.1 as standard, its just not enabled by default, copy the http device from devs:storage to devs:dosdrivers this will enable it.
That's the URL DosDriver, That won't really solve the problem, it just detects a url in a filepath and asks you what program you want to handle it with.
Nothing is stopping anyone adding mplayer to url preferences though.
@ggw
I've checked out the smtube play video rexx script and found this:
/* optimisations from K-L (compatible with MUI-MPlayer Overlay and SDL-MPlayer) */
/*MPLAYER_OPTIONS = "-cache 8192 -cache-min 20 -autoq 100 -autosync 30" */
/* optimisations from K-L (compatible with MUI-MPlayer NON-Overlay) */
/*MPLAYER_OPTIONS = "-vo cgx_wpa -cache-min 20 -autoq 100 -autosync 30" */
/* for SDL-MPlayer 4.2.4 complaining about a HTTP: assign at startup */
ADDRESS COMMAND "ASSIGN http: RAM:"
Possibly assigning http: to ram: may fix your problem.
Although if you're just streaming audio I'd use AmigaAMP3.
Amiga user since 1985 AOS4, A-EON, IBrowse & Alinea Betatester