Hi Andrew, I believe I have found a bug, or at least a gap in the logic.
If the Pro Tools session is moved from one location to another after the snapshot has been created, and you then try to bounce that snapshot, the bounce completes but afterwards, you get an error stating that the file could not be found.
I'm guessing here, but I think maybe Bounce Factory is looking in the original location (where the session was when the snapshot was created) for the bounce file before moving on. When it can't find it, it throws the error and reports the bounce failed.
However here's the thing ... I have the file destination for the bounces set to "Session folder Bounced Files/." Pro Tools recognizes the new location and puts the bounce file in the correct location. But for some reason Bounce Factory doesn't see the file has been created.
Might be worth looking into, and allowing Bounce Factory to follow the destination Pro Tools is reporting, even if the session has been moved.
Attaching the user data files here:
https://www.dropbox.com/scl/fi/4rpjhxh16iq1h2xw20u6j/Bounce-Factory-Data-bink-2024-04-10-12-46-09.643.zip?rlkey=vd0e7w5c97678ln678vglpdy6&dl=0
- SSoundFlow Bot @soundflowbot
Thanks for posting a question or an issue related to the 'Scheps Bounce Factory' package.
This package is made by @Andrew_Scheps. We're auto-tagging them here so that they will hopefully be able to help you.Please see support instructions here from @Andrew_Scheps:
Bounce Factory Support
The best and fastest way to get help with any Bounce Factory problem is to send the User Files and (if applicable) a screen recording of Bounce Factory failing. The easiest way to do this is to use the "Report a Problem" button in the app:
1. Go to the Bounce Factory settings using the cog in the bottom-right of the app:
2. Click the red "Report A Problem…" button at the bottom of the Settings screen
3. Follow the instructions on the screen.
Thanks!
Andrew 
In reply toBlake_Eiseman⬆:Andrew Scheps @Andrew_SchepsHi @Blake_Eiseman ,
BF definitely doesn't like it if the session is moved. The full path is used for a lot of things, and there's no way it can trust that session (even if it is the same name) is the same session and it's just asking for failure You've found the loophole of opening the session yourself, then bouncing just from that session, but I need to check for the existence of files and the session directory being the same as when the Snapshot was taken.
All that said I'm hoping to be able to leverage some of the additional session data I can access through the SDK, but so far there are enough missing pieces I really can't allow pointing Snapshots to different sessions, and I have to consider a moved session as a different session.
Maybe for version 2!
Andrew- BBlake Eiseman @Blake_Eiseman
Gotcha, thanks. And yeah that's what I did last night (I guess you can see that from the user files) ... I just opened each session manually as it threw the error.
This was sort of a "fringe" case I guess you could say. They were sessions that had already been backed up to my backup drive, and I then had to do some revised passes requested last minute. Rather than copying them back to my work drive, I figured I could just print them from the backup drive.
It would be great if something could be worked in for a new version, but it's not a workflow killer by any means.
Thanks for the quick reply!
Andrew Scheps @Andrew_SchepsYou're not the first person to request it, there are just so many screw cases that I don't feel comfortable saying it's going to work yet...