Jump to content

mdriftmeyer

Members
  • Posts

    45
  • Joined

  • Last visited

Contact Methods

  • Website URL
    http://www.reanimastudios.com

Profile Information

  • Gender
    Male

Recent Profile Visitors

2,132 profile views
  1. I think it has to do with the performance cores. The A17 bionic only has 2 performance cores. The M1 has 4 performance cores alongside 4 efficiency cores. The M2 offered 4, 6, 8, 16 performance core configurations. With the advent of the M4 line only the entry level iPad and iPad mini lacked an M processor. This way they can focus on M series only moving forward. Sooner or later even the iPad entry will have an M series processor.
  2. That doesn't square with the responsiveness of Logic Pro and FCP. What washes is that because they have too much cross-platform in their APIs [Windows bloat] it's a compromise they accepted for a larger user base. Well the user base is patient to a point. The Mac drove your success. Investing into two teams of developers now that you've been bought out is peanuts to the wealth generation potential. I speak having been in Engineering, Consulting, Professional Services at NeXT and later Apple. I guarantee the application base is a mish mash of hooks for C++ in Visual Studio and C++ in Xcode. I doubt they ever bothered learning ObjC/ObjC++ and when Swift came along with it's inherent bloat even Apple is still relying mainly on C/ObjC and C++/C in XNU kernel with ObjC++ hooks where necessary. I have an Acapella Licks track of over 40 tracks, roughly 12+ gigs of audio in Logic Pro 11.0.1. LP takes 5 seconds to launch w/ no session. It takes 5 seconds to launch that session where I mix in real-time with outboard Rupert Neve Designs gear and bounce my STEMS. I don't use a lot of F/x plugins. My main compressors are 5254s by RPN and soon the Master Buss Processor arrives outbound to the MBC for a limited near master mix. A clean session of Affinity Photo 2.5.x takes roughly 40 seconds to launch. It's not nearly as encompassing as Logic Pro. The issue is with Windows and it's APIs and how you've not abstracted between platforms and reduced labor costs for a less than stellar result. Adobe had to hire us at Apple for consulting on their Mac projects for a solid decade because they figured we do a better job being Apple on teaching and improving their code bases. And people wonder and complain that Apple has a 30% tax when they built everything and you still cannot manage to become proficient in the frameworks.
  3. Can someone answer how it takes 20-30 seconds to load Designer 2.5.1 and all the 2.x series apps for the first time. On the M2 Mini maxed out CPU/GPU/RAM, etc., this loads like a turd the first time. Close the app and About panel snaps forward and front and the app loads within a few seconds. Still slower than Logic Pro 11.0 that was just released but I expect that to be the case. However, each new version of Logic loads ever faster, unlike the 2.x series that clearly must need to load a lot behind the scenes before it can be presented in the most basic standard view.
  4. Auto capitalization should default to the OS system paradigm.
  5. Per Blender 4.0 Developer Release Notes Bcon 1 https://wiki.blender.org/wiki/Reference/Release_Notes/4.0/Rendering Below link to the new default folding into Blender 4.0. https://projects.blender.org/blender/blender/commit/a9053f7efbe8b25429b11bccd679dbe81ea60e3f
  6. An app attempts to connect to a server mount point should time out with a notification which mount point fails and then default to user desktop path in Finder. Affinity should contact Apple Dev for clarification on this and what methods need to be called to produce such behavior within the apps so this doesn’t hang the application. They should test the length of timeout optimal from user feedback. UNIX command line timeouts on NeXTSTEP we had preset to 900 ms before pipe closed. Personally, I wished they never split OS X in two and then gutted the server side services. You should launch the app executable from Terminal.app to record the output and find out if it is specific to the application or an issue with macOS/OS X.
  7. For those injecting this is a useless feature you don't do much technical publications. For you, just deselect that option. For the rest of us that find it useful and don't want to load a CAD program, but want to integrate these features into complex Designer creations we'll leave it on.
  8. https://gs.statcounter.com/os-market-share/desktop/worldwide
  9. Then there should be a choice in a configuration setting to enable or disable the behavior.
  10. It's a big upgrade, but one that will be universally adopted and should have already been on their radar for the past twelve months or so. I'm looking forward to it as it is required to build the likes of Blender 2.93 and newer.
  11. The spinning beach ball is a non-modal state to allow the system to manage processes dealing with cache, swapping, writing and more and thus whenever one hits a wall with physical memory and core activities it will surface. This goes back to our NeXTSTEP operating system us NeXT folks developed and brought to Apple. And first rule of thumb in any large image processing, video scrubbing, audio mixing, etc., you max out your system RAM and get the fastest drives you can.
  12. Blender has this feature. To have this feature for CAD/CAM, isometric top, front, side and 3D projection (really 2.5d) and leveraging brushes for shading would give the Suite blueprint scale production and Publisher a huge lift in technical publishing
  13. My Account shows the following view w/o anything loading inside it, just to echo what others are saying and to second Jeremy Bohn and it not loading the first time.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.