http://www.elderscrolls.com/skyrim/

Soon the wait will be over!

What? No MorphOS version?

Umm.. what? Why are we waiting for it? That beer looks good though...

[ Edited by jPV 01.11.2011 - 16:48 ]

This past weekend I took my son to a GameStop store (US chain) to pick out a Nintendo DS game...

I came upon a conversation that one of their store clerks was having with a teenage kid and his mother about the midnight release of this game. They are planning on having tents, food, and an outdoor game space for people to hang out in through the night until its available for sale after midnight. I was amazed.

@Debaser

Well, *it is* a big happening!

Similar events took place all over the world at the midnight release of Starcraft 2, with compos, live performances etc. I was there, and won some Starcraft 2 T-shirts and other memorabilia.

And speaking of that game, how about *this* kind of promotion for a computer game?

starcraft-2-airplane.jpg

BTW The website is perfectly rendered with current OWB release,
incl. embedded video player.

http://www.exception-dev.de/mos/OWB_video.png

But on my Peg2/G4 playing the video causes 100% cpu load
and the video is at low speed.

What about the mac mini g4? Is video playback better than on
my peg2? Can someone test it?

Freak wannabes need to tent down out of the shop to show their freakness...

Real-blood freaks don't need that gibberish...

[ Edited by amiades 01.11.2011 - 17:11 ]

@eliot

The surface is quite big and the video is quite high quality too, so it's normal. That said, if you click the fullscreen button, it will be substancially faster.

> if you click the fullscreen button, it will be substancially faster.

Here that doesn't make it faster at all. However, copying the video URL from the context menu, pasting the URL in the address bar and playing the video in overlay mode does.

eliot,
Quote:

Fullscreen with G4 mini (1.25) was not very taxing on CPU and played very well but not quite fluid at some moments.

Quote:

It would be surprising if it didn't, because it doesn't make a difference if it's in a separate tab or not, once you're in overlay mode.
I just checked the actual the attributes of the media: 920x518 2558kbps (mp4/h264). Even in MPlayer, that would be slightly too much for a Pegasos2. On a mac mini it should be no issue, though (OWB Media Player and MPlayer basically have the same performance, since they use the same library and blitting routines).

> It would be surprising if it didn't, because it doesn't make a difference
> if it's in a separate tab or not, once you're in overlay mode.

Exactly, the site's own video player doesn't seem to use overlay in full mode here. I'm puzzled as to why it seems to work for you and Debaser but doesn't for me.

Oh, ok. That's weird then. Probably useragent related. Try spoofing as safari and see if it changes anything.

(and sorry for the offtopic, takemehomegrandma :) )

> Probably useragent related. Try spoofing as safari and see if it changes anything.

Spot-on, Fab! Spoofing as Safari makes overlay mode work. Thanks :-)

eliot,
Quote:

Just tried the trailer on mini 1500 - runs smooth at about 90% load in full screen mode.

Quote:

Funny, I never thought of this thread to become about browser/multimedia benchmarking, but cool that it turned out that way (which of course is a little more on-topic given this site's context! )

As a reference - anybody knows how the site performs on various browsers on various hardware on OS4...?

Zylesea,
Quote:

Interesting - I did not get that high of a load when I ran it in fullscreen on my 1.25 mini. Then again maybe you had some other tools running at the same time?

>> Just tried the trailer on mini 1500 - runs smooth at about 90% load in full screen mode.

> Interesting - I did not get that high of a load when I ran it in fullscreen on my 1.25 mini.

I have the same hardware like Zylesea and except for the beginning and the end with mostly black background my CPU runs between 95 and 100%. What's your loopfilter setting in OWB prefs?

Andreas_Wolf,
Quote:
No particular setting, just the default "all frames" (alle Einzelbilder). Spoofing is default, too.

> the default "all frames" (alle Einzelbilder).

Okay, that's what I have here as well. So I don't know why you have less load than me, but the difference is almost marginal. I'm more interested in Debaser's loopfilter setting as he says he has even less load than you with a slower machine which I think could be due to reduced quality via loopfilter setting.

> Spoofing is default, too.

And what's this "default" you have selected in that particular OWB setting ("Browser-ID")?

default default i.e. odyssey web browser

> default default ;-) i.e. odyssey web browser

Then it's even more of a mystery to me. I just tried it again and here it's still as I said, i.e. no spoofing -> no overlay, spoofing as Safari -> working overlay. Strange.

Andreas_Wolf,
Quote:

Yes sir that is probably it. It is set to "Skip All But Reference Frames" however - it is rather fluid, at least I am fine with it and I am getting 79-83% usage. I must say that I played around a bit and look a little more care at looking at cpu usage - it does go way up around ~2:00 mark to as far as 99% and then drops back down towards the end. I guess I was paying too much attention to how pretty the game looks :)

Using Fullscreen and spoofed as Safari browser. When swithed to Process All Frames it goes to hell, comparitively speaking, to be perfecly honest and 100% usage.

> Yes sir that is probably it. It is set to "Skip All But Reference Frames"

Alright, then we have one mystery less to solve ;-) Thanks for reporting.

> cpu usage - it does go way up around ~2:00 mark to as far as 99%
> and then drops back down towards the end.

Yes, same here. Around this mark it even stutters here with "process all frames" setting.

> Using Fullscreen and spoofed as Safari browser.

Interesting. So it take it that spoofing is necessary for you (as it is for me but not for Zylesea) in order to make overlay mode work?

> When swithed to Process All Frames it goes to hell, comparitively speaking,
> to be perfecly honest and 100% usage.

Yeah, that's to be expected with 1.25 GHz.

Andreas_Wolf,
Quote:

'Simply out of habit - but it works in "default" as well actually.