![]() It's the same with the Late 2005 PowerBook G4s because by this time Apple had already announced they were switching to Intel and people were waiting for newer and faster machines like the Mac Pro and MacBook Pro. Quad G5s are quite rare and are hard to find. If it was me, I'd install Tiger and keep it as a Mac running OS X in my collection. You can install Linux on it to get better App support and could allow you to run more modern stuff. I would say install Tiger because that will perform great on one of these 2005 G5s and will work much better than Leopard. I have a 1.67GHz PowerBook G4 17" and an iMac G4 1GHz and they still work fine and can handle basic tasks as long as you don't want to do too much web browsing. You can still do some basic stuff on it without too much trouble at all. I wouldn't use a G5 as my main computer for anything in 2020 but if you manage to find an upgraded Quad Model with 16GB Ram, put an SSD in and a decent Graphics Card. You can install old stuff like TenFourFox, Adobe CS3 and Microsoft Office 2008 and they will run fine. That machine supports up to 16GB of Ram.Īll G5s support up to Mac OS X 10.5.8 Leopard which is very old and doesn't support any modern software. That makes the Dual 2.5GHz a Quad Core and that was the first Mac with a Quad-Core CPU. That machine supports up to 4GB of Ram on the 2GHz or up to 8GB of Ram on the 2.3GHz and 2.7GHz The Late 2005 came with a 2GHz, 2.3GHz or Dual 2.5GHz but each CPU has 2 Cores. The Early 2005 came with a Dual 2GHz, 2.3GHz or 2.7GHz G5. There's a long grey sticker on the inside right at the bottom that will tell you the full specs. I have also not been able to reproduce it on the iPad - neither the physical device nor the simulator - it has played just fine.First, I would check to see if it's an Early 2005 or Late 2005 as they didn't release a 2.7GHz in Late 2005. Sometimes, trying to seek within one of these "hung" sounds (assigning a different value to currentTime at least twice?) will get it playing.Īdditionally, this behaviour has *not* been seen in Safari 4.0.5 (531.22.7) on Windows XP, and a friend with OS X 10.5 reported that he could not reproduce the issue on his version of Safari either. However, copying + pasting the MP3 link (or dragging it from the page) into the address bar often (but not always) results in playback failure, similar to how the JS Audio() case behaves. Turning off JavaScript means the link falls through and loads in the "built-in" browser audio player, where it seems to work without issue. My test scenario involves JS intercepting a link to an MP3 file, and trying to play it via new Audio('foo.mp3') followed immediately by a call to play(). Observed: HTML 5 Audio() "play" event fires, followed by "waiting", then "loadstart", but no audio is heard. (Examples can be provided, if helpful.)Įxpected: MP3 should start buffering, load a certain amount and then begin playback. The MP3 files in question were encoded with LAME, and are 10 seconds and ~4 minutes in length. ![]() I am seeing this (or a similar) issue intermittently on Safari 4.0.5 (6531.22.7) on Snow Leopard, 10.6.3. Declare the variable in the global scope:Īudio = new Audio("Tromboon-sample.ogg") So it gets collected once it finishes playing. Var audio = new Audio("Tromboon-sample.ogg") It won't play again because the audio element is defined in a variable local to the function: > startTime on the Audio object this has no effect either. ![]() > again, which works in Firefox, but nothing happens. > Also of note, I cannot get audio to replay in Webkit. > Both of these tests work in Firefox 3.6.īoth of these tests also work in Safari on OSX if the Xiph QuickTime components are installed > On Chrome the bug shows up for both ogg and mp3 audio files. > I found the same problem in Chrome 5.0.342.1 developer version on OSX 10.5.7. The problem only occurs in the context of a HTML 5 "Audio" object.īoth production Safari 4.0.4 (6531.21.10) and the webkit nightly ( r51580) were tested. If you click on the MP3 filenames, you'll see that QuickTime X can play them all just fine in their own window. You'll notice that the sounds in the 0.03 to 0.05 second range do not load at all, and generate a MEDIA_ERR_SRC_NOT_SUPPORTED error. This bug only occurs in Snow Leopard with QuickTime X and Safari 4.0.4.Īll these MP3 files were created in exactly the same way (created as AIFF files in SoundTrack Pro v2.0.2, then converted to 64kbit mono MP3s in iTunes v9.0.2). Sounds that are shorter than 0.03, or longer than 0.10 seconds load and play just fine.Īll sounds load and play properly in Leopard 10.5 with QuickTime 7 and Safari 4.0.4. The HTML 5 Audio implementation in Snow Leopard Safari / QuickTime X has problems loading short MP3 files, specifically those between 0.03 and 0.10 seconds in length.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |