Does anyone else have this problem? I think my OP-1 Field has stopped working since I updated my Macbook to Ventura, but I’m not sure whether that’s really the cause
UPDATE: Seems like it only works in Safe mode for now. Not ideal, but at least it works
I reported to them back in launch that the public beta of Ventura broke it. It’s worked for me more recently though. However there is an android MTP file transfer program for Mac, normally I’d never have such a thing installed, but this works also if you get stuck. You can hold Shift and push disk to get a legacy disk mode too, this mounts without app, but you can’t access the tracks. You can add Rephaser’s sample packs this way though 
Ah, thanks! I git it working though now booting my mac in Safe Mode. Bit of a hassle, but hopefully it’ll be resolved soon
Same happened to be recently. Was able to resolve just by restarting Mac & enabling MTP again on OP-1F. No safe mode needed for me.
Has anyone had luck lately with the MacOS on Ventura? The first time I tried mounting to disk I’ve had trouble but read through the manuals and worked it out, but seems like copying my Op-1 Field contents to iCloud is troublesome. I don’t own the included TE usb-c cable. I wonder if that’s an issue 
Not working on Sonoma… not even opening
Sorry, it does work… I just thought there would be some kind of different interface apart from the regular folders view
im still trying to get it work on Somoma… it says busy…
As I found in another thread, and was able to verify with Commander One Pro which supports mtp with a helpful level of verbosity, it is the ptpcamerad process blocking the mtp protocol.
On my mac, running Sonoma(14.6.1), ptpcamerad starts up every few seconds then keeps running in the background, blocking both TE Field Kit and Commander One. I have not traced down which application or process actually makes this happen.
As I understand it, this is not the fault of TE, but a “feature” of the operating systems built-in applications and/or the protocol implementation.
My solution, inspired by the thread where I found this but can’t now recall where, was to create a command line alias killing the process continuously. So in the file ~/.zshrc I have this line:
alias op1f_connect='while true; do sudo killall -kill -vz ptpcamerad; sleep 0.5; done'
After restarting the terminal application, I can now run:
op1f_connect
then connect the op-1 and access it through either the TE Field Kit or Commander One.
No trouble now, but understanding the problem certainly was. Especially since this came across as being no fault of TE’s, a little note about it in their Field Kit user guide would be supremely helpful.
I posted this also on a different forum, the thread that first came up when googling this.