-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auxiliary files not being moved when capture occurs on external drive #849
Comments
I was wrong about this. The files are being properly created and placed where they need to be. However, those |
I did a little digging, the error appears to be caused by the fact that the external hard drive's owner:group is set to VideoLabMini:staff instead of root:wheel. However, so far I've been unable to change the ownership to root:wheel, despite disabling SIP and whatnot. I'll see if there's any way to reliably change ownership on the later macOS, I'm currently on Sonoma. |
Thanks for double checking! That was the behavior I was able to reproduce on a mac on our end (files are moved, but errors get thrown). I'll poke at it a bit more if I have a chance, but let me know if you find some kind of work around to silence those errors. |
Thanks for looking into this! I did a bit of poking around it seems that ownership of any external drives will automatically be set to the user:group of the logged in user. I tried seeing if I could go into the folder options (cmd + i) and give |
The files are now moving, but the 501 error persists on the output. Not a huge deal. Let me know if the ticket should be closed at this point or if it should stay open until that error is suppressed. |
Thanks for the continued testing! I'd say let's leave this open for now as it is probably helpful for others to see that this is a known issue (and not a big problem). |
For some reason I'm getting errors when auxiliary files are being moved to their final location, but only when using external drives. These errors don't seem to be happening when capturing on the system drive. Here's the output from vrecord, you can see the
mv
errors at the end.The text was updated successfully, but these errors were encountered: