Hi,
I'll preface this by saying I know that it is a beta, that there will be bugs and possibly a need to restart the system etc, however, I need the new text editing capabilities that Ventura provides and am therefore considering putting my machine on the beta.
Have people, using the public beta, found any show stopping problems yet? Any bugs that make the system unusable? More specifically, any issues using Ulysses, as that is my editor of choice?
Thanks for any input you can provide.
O
Comments
I'm not running it, but it…
I'm not running it, but it always differs with beta releases from machine to machine in my experience. If I were you I'd install the beta on a secondary disk partition and test it out - that way it's easy to remove it if it proves to not work well for you.
I'd see if beta support is even possible
By beta support, I was wondering if you can get access to a pre-release beta of the program. My idea behind this is, if you install ventura, use the version you know already. If you don't get results you're after, test out the beta. That way you can report to both Apple and whoever the company is. But I'm adventurous. Having said that, I'm waiting for the second beta I think. well, maybe I'll just go all in. Good luck.
Using it and works quite well
I can't speak to the particular app you mentioned, but I've been using it a while now, and find it to be very stable. Eloquence is nice, and that alone made it worth the upgrade. I have had some issues in Safari filling out forms and logging in to sites where I didn't already have my user and password saved, as things have been going out of focus, and things I could normally tab to were somehow not showing up when tabbing, but then I restart VO, and it's fine. That's the only problem I've had.
its stable, however
While the beta is very stable, you should install it in a separate apfs volume to keep your primary mac os from any miss hap, I.e, apps still needing updates to work propperly. I always beta test by making a new apfs volume and performing a clean install of mac and then the beta. If I want to test apps, I launch them from my other macos primary system to avoid having to redownload everything since apfs share content accross the same container. For instance, I have my macos main volume, with macos monterey and a new apfs volume with macos ventura. If I want to test apps, I can just go to my macintosh hd volume with macos monterey, from macos ventura, go to the applications folder, and launch whichever app I need.
This is a great idea, thank…
This is a great idea, thank you. Yeah, lots of stuff to log back into and so on. I'll do a fresh install on the volume now and use your tip there.
So far I've not encountered safari not responding, which is most exciting. Voiceover also seems generally more responsive. Not sure if that's just because of it being a new install, but it's at least hopeful.
Just a note for any who do have the OS on a separate volume, I was finding the volume selection on my M1, holding down the power during boot, to be unreliable. To choose your startup disk on Ventura you have to go to system settings and into the general tab, and it's in there. the system settings app is new and therefore the startup options have moved a little. For us, drilling through a bunch of new menus can be frustrating rather than for sighted peers who can scan far faster.
they should
they should remove the power key boot picker. they should make that when you hold power, it boots into recovery.
I'm running the developer beta, and it is working well
I'm running the developer beta, and it is working well. Eloquence is very responsive on Ventura, just like on windows with NVDA and Jaws. however, VoiceOver sometimes loses focus on webpages, such as 9to5mac. I already submitted this feedback to apple and hopefully the next beta fixes it.
Why the developer beta when
@jc, just curious, but why are you still running the developer beta when the public beta is out? I mean are there any upsides running the developer beta instead of the public beta?
webpage find not working
Just to be aware. Currently vo+f to find text in a webpage is neither working in chrome or safari in the beta. It announces the feature but no window or text input box appears.
Screen dimming or turned off
I am using 22A5321d, and it works pretty well for me. However, though the keyboard wakes up my M1 iMac, it doesn't always turn the screen on, and I sometimes need several attempts. I have Touch ID, which always unlocks the Mac, but the screen might stay off.
Also, while watching full screen YouTube videos the screen might dim or turn off.
I know I started this thread…
I know I started this thread and did make the jump. As I've said elsewhere, VoiceOver performance in safari is pretty bad on certain pages such as reddit. I think it is something to do with busy live regions. Voiceover restarts and moves focus.
There is also an issue with focus getting stuck on headings which, at best, can be fixed with VO shift up, to move up a level of focus, at worst, restarting VoiceOver.
If rapid data collection is part of your job or school work, I'd not suggest trying the beta. It's not an upgrade.
this may change later this week with the next public beta coming out and I'll report back then.
continue to report these bugs. It's great we can talk about them and share commonalities on here now, but every time we raise a concern here, or experience the same issue, we all need to report it with the feedback app... Though, I know you're all aware of this.
In hindsight, I should not have upgraded as there are no discernible benefits to the OS and only bugs, though happy to report them as my work is my own and not in a position of high responsibility or time pressures.
I mean uprading to betas
Upgrading to betas is always a risk, and there will of course be a bunch of bugs. Its a beta, after all.
I'm hoping elequence goes back to normall in the next beta of mac like in ios.