- Last Active
When you show bar charts and point out quarters, it would be nice if you could label the chart better in a graphic program after the chart source exports the chart.I did it on my iPad in Vectornator, using it for the first time. Amazing features and amazingly useless search in the help/ support area. I could have knocked this out in InDesign in 15 minutes or less, which I’ve used since 2003. And I’d have had the time to do a nicer job.
I hope you can improve on this and do something like this so we can find all the 2nd quarters for the comparisons. Maybe highlighting the 2nd quarters with shaded rectangles (in multiply mode to make ‘see-through’) would work better. Labeling and dividing the years with vertical rules helps too.
Thanks in advance for considering this.
The screen captures were done in dark mode and are visually confusing. Can you redo the screen captures without dark mode?
The left side of the screen does not look like what Apple showed during their announcement. In their presentation, the apps look like trapezoidal perspective views of icons stacked vertically. Perhaps that’s what you are showing, but the dark icons against the dark mode background are disappearing—black on black.
Is it possible to repost this article with a few screenshots where we can see them without dark mode so they are visible against the background?
hucom2000 said:It still boggles my mind that we can have lossless on a HomePod mini, but not AirPods Max…From Apple website: https://support.apple.com/en-gb/HT212183
Can I listen to lossless audio using Apple’s Lightning to 3.5 mm Headphone Jack Adapter?
Yes. The Lightning to 3.5 mm Headphone Jack Adapter is designed to transmit audio from the iPhone’s Lightning connector. It contains a digital-to-analogue converter that supports up to 24-bit/48 kHz lossless audio.
—> So, yes on headphones with analog 3.5 mm jack.
Can I listen to lossless audio using the AirPods Max Lightning to 3.5 mm Audio Cable?
The Lightning to 3.5 mm Audio Cable was designed to allow AirPods Max to connect to analogue sources for listening to films and music. AirPods Max can be connected to devices playing Lossless and Hi-Res Lossless recordings with exceptional audio quality. However, given the analogue-to-digital conversion in the cable, the playback will not be completely lossless.
So the work-around I heard discussed is the digital to analog DAC in the Lightning to 3.5 mm Headphone Jack Adapter into the Lightning port, then the Lightning to 3.5mm Audio Cable (it should be called Audio to Lightning cable) to AirPods Max.
It sounds like a double conversion could lose something in each step, but the discussion was that it sure beat the hell out of Bluetooth. I’m wanting to find a Lightning to Lightning cable and try it.
What I remember in the discussion by some audiophiles is that you don’t get all the way to the “pure” lossless, but you get pretty darn close. And since there are many who can’t discern the difference between a high quality lossy codec (AAC?) and lossless, I’d say I’d be pretty happy with “pretty darn close” to lossless.
But my hope is based on one discussion. I hope a high end sound engineer writes an article on this. Is anyone on Anandtech reading this? Or at Audiophile Magazine?
Could AppleInsider interview a sound engineer and do some double blind testing?
The follow on to the iMac’s ‘just-in-time’ success was the iPod scale up. It greatly expanded the Apple brand beyond computers into a Apple becoming a cultural icon.Without scaling up so fast to meet the accelerating adoption demand via supply chain genius of Tim Cook, the iPod would not have met the demand and subsequently would not have funded the miniaturization engineering advancements needed in the iPhone, nor funded the R&D for development of the iPhone.
At the time of iPod success and meeting the leaps in production/supply needs, the bond was set between Tim Cook and Steve Jobs. They were learning from each other at that point.
The next two critical individuals beyond Steve Jobs and Tim Cook were Avie Tevanian (OSX platform) and Jony Ives (design).
Who else were so highly critical after these four?
dantheman827 said:dysamoria said:
It’s not an executable. That’s the issue.larryjw said:
No, a PDF is a program. Just because a PDF can be labeled a document doesn’t mean it’s not a program. You need to take abstraction up a level.Rayz2016 said:
No, PDF is a document format. It doesn’t run, it’s rendered, same with music files. But that’s not the real problem.larryjw said:I think Apple's guideline rejecting executing code is needs to be eliminated -- an emulator is an emulator.
In reality, executing code in an emulator is what programs do. For example, PDF files are themselves computer programs which instruct and iPad how to render a PDF visually.
Isn't programs as data and data as programs the basic principle of computing?The emulator allows apps to run code that can’t be seen or examined by Apple, and that has always been against the rules. PDFs, the other hand, are pretty benign. It would be quite hard to piggyback an App Store in a PDF document.So the real problem is the lack of consistency in applying the rules. This should never have been allowed in the App Store in the first place, so they’re going to look like real dicks for removing it now.A previous commenter also suggested that a program must be executed on the CPU. That’s also not correct.
In designing systems, one is always trading off between the “executable” and the “data”. Different languages tend to encourage marking the boundaries differently, but it remains that these boundaries between data and executable are quite arbitrary.In a micro programmed CPU, your “executable” is just data. To the hardware guys, the micro program is just data which drives NAND gates and voltage changes.
PDF Files can definitely contain executable codeAny PDF graphics (all graphics for that matter) contained are handled by existing OS layer close to the kernel. It’s safe and mature. Non-PDF graphics are translated and handled as display PDF and display PDF shouldn’t be the issue. PDF documents have features like links, authentication and more that are likely at an execution of function in a sandboxed area.The graphic display computing is now baked into silicon for speed in Metal.I’d imagine DOS has many vulnerabilities. Whether the sandbox can be penetrated (or escaped) is something Apple engineers can determine in a non-disclosed manner.There seems to be a lot of conjecture as to why the App was rejected beyond the stated reasons.