Logic is in desperate need of an update. But the recent slew of updates along with the latest seeds of 10.5.2 means its just around the corner. Time Capsule's release depends on this update. I'm just patiently waiting. I would rather wait a few more weeks, if necessary, to get a working update. Leopard seems just fine to me. Haven't had any more crashes than I did with Tiger. I think people need to look at their system before totally blaming Apple. Maybe Leopard wasn't as completed as it could have been, but what OS can. OS's are developed to the best of their ability, and as a developer myself (of, ironically, Windows software), you never know how your system with work with the users hardware and software configurations.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Software Updates: iPhoto 7.1.2 & Prokit
- Thread starter petvas
- Start date
- Sort by reaction score
It is a joke, at almost all patches that causes you to reboot and sometimes not even that, someone yells that Safari is faster.
Just like people asking when the PowerBook G5 is going to come out.
Logic 8 you have to remember is a totally new app. It was totally re-written and does not have the old Emagic software attached to it, apart from the AU plugins.
Most of the bugs are OS bugs, take Protools HD as an example as well.
10.5.2 will fix a lot of them, and a major update to Logic Pro 8 is around the corner.
Most of the bugs are OS bugs, take Protools HD as an example as well.
10.5.2 will fix a lot of them, and a major update to Logic Pro 8 is around the corner.
After the update when trying to convert some video in QuickTime Pro, about 10 seconds into the conversion it stopped and gave me a "Prokit" error. I rebooted and it works fine now with no error.
Might want to reboot after the update just to be on the safe side.
Might want to reboot after the update just to be on the safe side.
You are right. I was immediately impressed with Logic 8 until I started using it. It uses more CPU, is slower, they removed (for me) important features, and basically I think they made it more into "GarageBand Pro". I am taking a look at Cubase 4 at the moment, maybe that's where I have to go. Logic 7's implementation of virtual instruments is bad, so Logic 8 is an improvement, but not enough for me to go that route yet, so I am still using Logic 7 and investigating my options. Sigh.
You'll find Cubase even more of a headache. It doesn't meet professional requirements, example, it does not have the ability to sidechain. VST is pretty much limited.
I know Cubase and I have tried switching to it before back when I used Logic 5 on PC. So I know I will have to take a very serious test drive to see if it can do what I need it to. But stuff like side chaining isn't any showstopper at all for me as most of my work lies in the MIDI world.
Here is some information about dynamic Braille displays
There have been some prototypes along that line, but nothing commercially available, and it would be fantastically expensive.
Not as useful as you might think. The resolution that is discernible by touch is maybe 20 dpi. For comparison, a computer Braille cell is approximately .5 inches high by .25 inches wide and is a 4 by 2 grid with each position raised (or not). Braille takes up a lot of space, but if you were trying to enlarged raised text to the point that different fonts became tactilely discernible, the problems would be much worse!
But the real problem with this your idea is that Braille is read by finger tip. In order to be as fast as possible, information must be linearized, and this is a key feature of the screen reading software. A two dimensional tactial display would be quite nice for some things, but as a general purpose output device, too much time would be wasted searching.
Here is an article. The piezoelectrical cells are so expensive that a display capable of showing 40 Braille characters at a time cost $2500 or more.
There have been some prototypes along that line, but nothing commercially available, and it would be fantastically expensive.
Not as useful as you might think. The resolution that is discernible by touch is maybe 20 dpi. For comparison, a computer Braille cell is approximately .5 inches high by .25 inches wide and is a 4 by 2 grid with each position raised (or not). Braille takes up a lot of space, but if you were trying to enlarged raised text to the point that different fonts became tactilely discernible, the problems would be much worse!
But the real problem with this your idea is that Braille is read by finger tip. In order to be as fast as possible, information must be linearized, and this is a key feature of the screen reading software. A two dimensional tactial display would be quite nice for some things, but as a general purpose output device, too much time would be wasted searching.
Here is an article. The piezoelectrical cells are so expensive that a display capable of showing 40 Braille characters at a time cost $2500 or more.
I think it was there before too, I just don't normally notice it. I realized after it's because I normally scroll with the mouse ball and I happened to use the scroll bar for the first time in a long while for some odd reason. I know it's existed for a while at least in general, I just couldn't remember if it was for Events in particular.
just great, i just installed FCS2 the other day, today i downloaded the updates only to return and fine their is more...does it ever end. NOrmally i'm happy for updates but at school i hate it b/c of my school close to dial-up connection
Wirelessly posted (Mozilla/5.0 (iPod; U; CPU like Mac OS X; en) AppleWebKit/420.1 (KHTML, like Gecko) Version/3.0 Mobile/4A93 Safari/419.3)
I guess you have to wait for your desired .2 update for a bit more...
petvas said:Well, it seems that I am one of the many that sit in front of their computer checking if Apple released 10.5.2
I guess you have to wait for your desired .2 update for a bit more...
iPhoto update has enabled Australian users to purchase Cards and Calendars etc through iPhoto.
http://www.apple.com/au/ilife/iphoto/printproducts.html
was released today
http://www.apple.com/au/ilife/iphoto/printproducts.html
was released today
Has anyone noticed if this Prokit update has fixed any issues with PhotoShop CS3? I know it reads like it only applies to Apple products but maybe they slid an update for CS3 in as well. I have been on the phone with Adobe everyday the past week and they assure me that an update is coming and it will come from Apple, not from Adobe. Can't wait to get home and download to see if it includes an update for CS3!
Do you say that as speculation or fact?
As far as I know, ProKit is not used by anyone outside of Apple. It's just used to give their "pro" apps their ugly and superfluous dark-grey interface.
What problems have you with Photoshop CS3? I've been using it on Leopard plenty, and it works fine.
I'm having all sorts of issues with CS3 on Leopard, and they're recognized by Adobe as well. Biggest issues are with numerics. For example, you want to change your font size to 15pt but only 18pt and 16pt are available on the slider. It won't let you manually type in the font size, you can only change the font size via the slider. Here's a link from Adobe on the issue:
http://www.adobe.com/support/pdfs/PhotoshopCS3_LeopardIssue.pdf
I was hoping maybe the Prokit would have extended to other pro products. Just wishful thinking I suppose. Overall the majority of CS3 works fine on Leopard, just some bugs that really make the small little things a pain in the butt! The frustrating thing for me was I waited to update to Leopard until I saw Adobe post that CS3 was compatible and for the most part it is I suppose, but not 100%.
My Logic and Leopard work just fine, thank heavens! It will be interesting to see the size of the Leopard update, over 400MB?! I wonder how the servers will handle that.
ManagedQ'ed iPhoto
I know this is somewhat unrelated but I just ManagedQ'ed iPhone update and found a whole bunch of copycat forums. Good to know MacRumors is still leading the pack.
I know this is somewhat unrelated but I just ManagedQ'ed iPhone update and found a whole bunch of copycat forums. Good to know MacRumors is still leading the pack.
Does the ProKit-update make Aperture work properly on Leopard? On my machine at least it usually refuses to start. It shows the splash-screen, and then nothing.
As it happens, I was actually able to fix this issue few days ago. But the thing is that I'm not sure that is it fixed for good, since Aperture does work occasionally. What happens is that I tried Dtracing Aperture with the "Instruments"-app Apple ships with Xcode. Needless to say I couldn't make heads or tails of it. But then I accidentally made it start Aperture over and over again. I think it went through that procedure maybe 20+ times before I managed to kill it. I then quit Instruments and tried starting Aperture... and it worked! Before running isntruments it did not work! Earlier the only way to get Aperture working again after it started acting up was to restart the machine.
Here's to hoping
As it happens, I was actually able to fix this issue few days ago. But the thing is that I'm not sure that is it fixed for good, since Aperture does work occasionally. What happens is that I tried Dtracing Aperture with the "Instruments"-app Apple ships with Xcode. Needless to say I couldn't make heads or tails of it. But then I accidentally made it start Aperture over and over again. I think it went through that procedure maybe 20+ times before I managed to kill it. I then quit Instruments and tried starting Aperture... and it worked! Before running isntruments it did not work! Earlier the only way to get Aperture working again after it started acting up was to restart the machine.
Here's to hoping