[REAL Studio And PowerPC Support
Virginie Fayad
Call me a cynic though but I am also not surprised that Apple did it like this - accept the cash of PPCers for the upgrade and then making an update Intel only - easy way to sell more computers! And of course by saying support was never offered to non-intel machines for LP9 in the first place they have covered themselves legally.
No, it's not disgraceful, it's just progress. I bought my G5 new when I knew the Intel switch was coming. As a result, I got a mature machine that all apps supported and have had a happy and stable Mac life. Others waited and jumped on the new Intel batch and had to wait for many apps/plugs to catch up in order to work, then get debugged again. Some took quite a while.
I would say what is disgraceful is apple selling a machine based on the promise that it would perform great once the software/OS caught up...and then dumping support before actually supporting those features.
there are a lot of important features fixed in this update.. (esx24 sample edit for one) .So instead they throw in an ill prepared 64 bit option which there is 1 plug that works with it! ..it just makes no sense.. a bug fix and a working version of 9 might have been a better option.. I have a macbook 2.4ghz 64 bit just chugs on it ..rubbish.. great for the future perhaps but even then my tracks sounded great in 32bit.. pointless aggro..
I wouldn't call it ill prepared, and it makes perfect sense to me, users have been begging for it for a long time. There are just certain features that probably use external shared libraries that haven't been updated to 64 bit yet (some from third parties), and I'm extremely glad they didn't hold up the release for things that not everyone uses.
There weren't many plugins before release simply because there was no platform to run them on therefore no point in releasing them. Within a day, eastwest and Spectrasonics have announced 64 bit support with more on the way I'm sure. Not to mention that memory handling is already better even with 32 bit plugins. And there are a number of bugfixes in 9.1, 64 bit is far from the only improvement.
I don't know what to say about your macbook, on a low end machine it may not be useful, but it makes a radical difference on machines with more ram and more CPU power. And 32/64 isn't going to make any difference in sound quality, it's only for making better use of the hardware.
All you have to do is find the main program file in under Applications... right click on the program name and select "show Info" and look at where is says 'Kind: Application' at the top of the info window that opens.
You will see, if you try this with Logic 9.02 or another app like iMovie... the magic word 'Universal' next to 'Kind: Application....' which means it will work on both Intel and PPC processors... but if you try it with Logic 9.1 you will see 'Intel' which means Intel processors only.
I'm quite sure that for one or the other of those reasons, my stupid expensive (4k+) current machine (that I've had for 1 year, 3 months) WILL be replaced within the next 3 years for a variety of reasons.
Frankly, I'm shocked at how long the KEPT power pc support on the table... nearly 3 years. In computer time, that's amazing. Just ask all the people who went from XP to Vista or Win 7 (did that too)... took 3 years and a gob of money just to get things right.
i really don't believe they screwed anyone over....those with decent g5 machines still seem to be getting along fine but it is old technology that needed to be dropped at some point....logic 8 on tiger is still an extremely powerful prospect
BIP and freezing takes care of any musical hitches i might have but really , logic 9 on this laptop is still incredible.....i think i could easily get another 3 years out of this computer and then some......i reckon the suport will continue for intel for many more years it just remains to see if my beaten up machine will last more travels
Update, 3/11/2022: In the original version of this piece, we said that the stand on the Studio Display couldn't be changed. We've since learned that while the stand isn't user-serviceable, Apple service providers will be able to change it after-the-fact for a fee. We've updated the article accordingly.
Original story: Apple's announcements of the Mac Studio, the Studio Display, and the new top-end M1 Ultra chip earlier this week focused on those devices' headlining features, but there are always more details to explore as people dig through the spec sheets and Apple responds to questions from the press. Ahead of our full reviews, we've compiled some of the most interesting details about the new hardware.
The main risk with creating such a huge chip is that manufacturing yields will be low, as more surface area increases the likelihood that there will be a defect somewhere in the chip. But TSMC has been making M1-based chips on its 5 nm process for well over a year now, giving it plenty of time to optimize yields. And Apple is able to do some binning with the M1 Ultra (i.e., selling some chips with defects as lower-end models with the defective parts turned off), since there are versions with both 48 and 64 GPU cores.
The increased manufacturing complexity would explain why it costs so much to get a fully maxed-out M1 Ultra. Stepping up from the M1 Ultra with the 48-core GPU to the one with the 64-core GPU costs an extra $1,000. Compare that to the mere $200 it costs to upgrade the M1 Max from a 24-core GPU to a 32-core GPU.
Predictably, a genuine-looking results page for the Mac Studio and M1 Ultra appeared in the Geekbench online results database shortly after Apple's event ended. If the page is real, it helps to back up Apple's performance claims. Both its single and multi-core performance scores far exceed those of the 2019 Mac Pro's fastest 28-core Xeon W-3275M processor. A Mac Pro with that processor costs an eye-watering $13,000, compared to $4,000 for the M1 Ultra Studio model.
Geekbench gives us only a limited picture of a given device's performance, particularly for a pro-focused desktop like the Studio. The machine's ability to crunch on huge files for long periods of time will be just as important as its ability to run a benchmark app for two minutes. But that top-line number is impressive nevertheless.
Apple's new 5K Studio Display only lists Macs and iPads on its compatibility list, but nothing will prevent it from working with Windows PCs that can handle it. The fancy camera-panning Center Stage feature and True Tone support won't work, but the display itself, its speakers, and its webcam will all register to Windows PCs, and charging over USB-PD will presumably work for PCs as well. You will, however, need to connect the display to an Apple device to perform firmware updates.
We don't yet know the monitor's required PC specs. More modern computers with 11th- or 12th-generation Intel processors and Thunderbolt ports ought to be the safest bet. But whether the display will work with a regular USB-C port or a DisplayPort-to-USB-C connection remains to be seen. We'll do some testing of this in our review.
Embedded software debugging is the process of evaluating the behaviour of an application that is placed in its target environment and subjected to different boundary conditions. The debugger and its supporting hardware elements assist in providing tight control over the execution and complete visibility over the internal aspects of the target environment, so it allows to detect errors or modify behaviours of the application.
In the CCS environment, the debug is the next step after the project build which, after a successful assemble/compile/link process, allows the application executable file to be loaded to the target environment for debugging.
Debugging can also happen in a system that has code already loaded and running, typically on advanced stages of the product design or with a finished product. These two methods are fundamentally identical with only procedural differences that can be seen in the section Launching a debug session.
CCS can also debug an OS-hosted executable, which requires a high level operating system running on the target device/board (embedded Linux is the most common). However, the process of creating a project, building, and debugging is outside the scope of this document but references can be found in the section Linux Debug References
This setup, when used with CCS, allows the host PC to communicate with the target, load data and code, control the execution of the program loaded via breakpoints/watchpoints and step operations, as well as read data back to the host PC to be displayed in views such as Expressions/Memory/Disassembly.
To properly make CCS aware of the physical aspects of the debugging environment, a Target Configuration File must be created. This file is populated with the appropriate Debug Probe type (XDS, ICDI or MSP-FET) and host interface (USB or Ethernet). This file also contains the exact specification of the Device or Board being used.
The Target Configuration File is a plain text XML file, with a .ccxml extension, that contains all the necessary information for a debug session: the type of Debug Probe, the target board or device (or even multiple devices), and (optionally) a path to a GEL (General Extension Language) script, which is responsible for performing device and/or hardware initialization.
795a8134c1