Rogue wrote:
@samo79

Well the reason is that once Timberwolf comes out, we would want the latest version of it. Updating the source code now to 3.6 and later to 4.0 is a waste of time, so we opted to go for 4.0 directly as the better alternative.

I see no reason for USB 3 development as there is no Amiga hardware with USB 3 ports and unless someone knows any different, I don't believe the X1000 or SAM460 are going to have them.

USB3 is like Blu-Ray... pointless.

DVD sales are now down, I don't know about Blu-Ray sales, but like Music the future for video now lies in online/downloaded content as the hard drive has exceeded people's dreams and storage requirements and most importantly is dirty cheap.

ChrisH wrote:
Quote:

however I'm left with a CLI output window to close, what do I add to stop this appearing?

Add WINDOW=NIL: to the icon's tooltypes.

Quote:

Take it this should do the trick with regards to giving other things priority like MPlayer?

Once you fix "Run", it should do - unless your Ripper starts a separate task to do the encoding.

ChrisH wrote:
I use LAME in a Shell script, so I just put ChangeTaskPri -1 before it. If you're using some Workbench program, then you either manually change it's task priority each time you run it (boring!) using Scout, or you create a script to run your program using WbRun & you put ChangeTaskPri -1 before it.

afxgroup wrote:
@Daniel

Quote:

Could GUI parts be taken from AWeb, which is open source and has a Reaction GUI?

Maybe you don't understand that he doesn't want to add useless GUI to OWB

joerg wrote:
- Neither the AROS OWB nor the MorphOS OWB use an AmigaOS GUI but Zune or MUI4 instead, i.e. you can't use anything in GUI related parts from the other 2 in the AmigaOS 4.x OWB and most of the platform specific parts depend on the GUI.

Or you'd have to downgrade the GUI of the AmigaOS 4.x OWB to MUI, but it's impossible to collect a bounty large enough for me to consider touching extreme crap like MUI ever again.

However, MPlayer won't play a video on the Workbench screen if I have the screen in 32 bit mode. And MilkyTracker has audio playback problems if run too big and Workbench is set to 32 bit, regardless of whether MilkyTacker is set to run in a window on WB or fullscreen. If Workbench is in 16 bit mode, MilkyTracker is fine all the way to the full 1920 x 1080.

I again booted the Sam from the installation DVD, and it's the same level of performance. The one thing I've done that has made an improvement was set interrupts to "YES" via the monitor ToolTypes.

Interesting that Daniel reports similar performance with a 733mhz "complete system" from AmigaKit. So maybe it's the LiteOn DVD drive, assuming we have the same drive and others with better playback have a different model drive??? Of course, as mentioned, I've already ordered another copy of this drive so I'll have the drawer cover.

I'm not sure that it is.

I have read that this system will not achieve 100 percent smooth DVD playback but that it should be "close." Mine is not even close. It stutters and skips to the point of being unwatchable. I'm using the latest registered version of DvPlayer. I really don't intend to use this computer for DVD playback as a routine, but I'm more concerned that various other video files do not play smoothly with DvPlayer or with MPlayer. No, I'm not attempting to play HD video files and don't expect that level of performance from the Sam.

My system is a 733MHZ "complete system" from AmigaKit. I am running OS4.1u2 and driving a 1920x1080 LCD screen at native resolution.

djrikki wrote:

I am fairly sure the author of OWB must be thinking 'is it really worth me developing OWB any further with the world's most popular browser arriving shortly on the Amiga platform?'

koft wrote:
@Daniel

What do y'all mean by a "Download Manager"? I'm using OWB on MorphOS and it's fantastic. When one downloads stuff a window appears showing the status of the download and everything. OWB shows more information about stuff than other browsers like Safari, IE, Firefox, etc. If OWB was on windows, It would probably be my main browser. I love that one second startup on my crappy eMac. OWB is one snappy little browser.

Implementing a download manger is trivial and only takes a few minutes, plugins are supported already (there are just none). If they'd port for example libgnashplugin.so to AmigaOS 4.x it would work in both Timberwolf and OWB - for displaying some annoying flash ads you could only block again in Timberwolf with Add-Ons like NoScript and Adblock plus but not in OWB
(For most other things gnash isn't good enough.)

That doesn't make any sense since they would have less time for other projects. Implementing a complete web browser, which would be comparable to browsers like Firefox or Opera, around OWB from scratch would be much more work than porting an existing web browser like Firefox is.