I ran it and it all seemed good.. but on dbl clicking the run, it errors out…
Maybe a re-install?
Im on an M4 max but not that that should make a difference..
…andddd for whatever reason, a restart and attempting it again seems to have made it work..!
..Happy Monday.
Thanks again for sharing 
1 Like
This thing is INSANE. Thank you, @joelosis!!!
1 Like
Rocky 9.5?
It should be the only one. Stay current, stay clean.
Thanks gotta try this out …
1 Like
Strange I got boiling edges.. should you degrain first?
1 Like
I wouldn’t degrain, and you are using it like in the demo I did? I have had great results. One thing that can help is using ungraded as well
1 Like
Up and running on Mac Studio but can’t export. I run matting, let it process and when I export video it throws an error message “Not all frames have mattes. Please “Run Matting” from the Matting tab.” I can export a single image but not video. Anyone having similar problems?
2 Likes
Converted the color space to Rec709 from Log and that seems to have fixed it. Not sure why that would matter…
1 Like
The model would have been trained on rec 709, I sent it 2065-1 once by accident and it did not like it
1 Like
Makes sense. Thanks. And thanks for sharing this. It’s great.
1 Like
Update to my earlier issue. Looks like my problem wasn’t due to Rec709 vs Log (although that could cause issues I wasn’t experience per Joel). I found that Prores422HQ loads, tracks and runs matte properly but will not export. I tried again with Prores422 and it works perfectly. Not sure exactly why, but I’d imagine potentially data rate might be too high and using too much ram?
I’m running Sammie-Roto on a Mac M1 Ultra with 128gb of Ram.
1 Like
That’s really strange, I have successfully fed it prores444 on windows no problem
I had the same issue on mac with Version 1.3. No Export. I did send you a dm with the fix
1 Like
I had the same issue. If you look into your temp --> matting folder, you’ll see subfolders with .png files. These are the frames of your matte, you can copy & rename them to get a frame sequence. I wrote a short python script to handle it for me.
-Ted
Has anyone gotten this running on Macos 15.3.1?
I can see the issue is the system python version being 3.13 which isn’t supported. I created a conda environment with 3.12 and installed PyTorch w/o any issues. I then tried to run install_dependencies.sh and it’s seeing Python 3.12 but then errors out when it’s trying to check PyTorch. I’ve removed all references to 3.13 so unsure how it keeps appearing in the below log.
It also looks like I can only install PyTorch 2.5.1 so that is now looking more like the issue. Defining the version in pip doesn’t seem to do the trick.
✅ Detected compatible Python version: 3.12
Creating Python virtual environment...
Upgrading pip...
Requirement already satisfied: pip in ./venv/lib/python3.13/site-packages (25.1.1)
Installing wheel...
Requirement already satisfied: wheel in ./venv/lib/python3.13/site-packages (0.45.1)
Detected macOS. Installing PyTorch...
ERROR: Could not find a version that satisfies the requirement torch==2.7.0 (from versions: none)
ERROR: No matching distribution found for torch==2.7.0
This is my first attempt at using Anaconda so I’m sure I’m doing something wrong. Any guidance would be very much appreciated.
@kyleobley - you can try python virtual environments
I got it running on the Mac, but probably did it wrong and dangerously. I installed homebrew (https://brew.sh/), then did “brew install python” from a shell. After that, the install scripts and software worked!
Thanks @philm I’ll have a look. I thought that’s what conda was doing…but I’ll give it another go.