162 Batch Bounce job failed on bounce #83 and a couple other things
Hi Andrew.
I am on my last 2 days of demo of Bounce Factory, and I finally had an opportunity to use it in a real world setting of bouncing out a whole album of 12 tracks with stems---204 bounces. I started with an empty bounce list.
-I began by setting up 19 bounces in the first session, and bouncing it all out immediately. No problems (except what’s noted in the PS below). (Deleted these first 19 from the bounce list.)
-I setup 23 bounces in a 2nd session. Bounced it out immediately. No problems. (Kept all snapshots from this point forward.)
-I decided to setup ALL the remaining bounces from the next 10 sessions---162 bounces.
-I selected the 162 snapshots, started the bounce job and walked away. I monitored via text away from the studio. BF failed on bounce #83 out of 162. Not sure why.
-I returned to the computer and Collected the User Files. The link is below.
-I left everything as is, and I went through the list and re-selected what still needed to be bounced, and re-started the bounce job. (It was 5 remaining sessions, 80 bounces.)
-BF acted very weird and verified all 5 sessions---opened each one---but did not bounce any files. It would just open, verify, close and move to the next session for all 5 sessions. Then it told me it was done with Warnings. hmmmm
-I quit Pro Tools. Closed Bounce Factory. Relaunched both. Went through the list and re-selected the 80 snapshots. Started the bounce job, and BF bounced the remaining 80 files without incident.
-I went through all 204 total bounces from the 12 sessions (162 from the big batch and 42 from the two immediate session bounces) and all bounces were done correctly.
One other note: while reviewing all the bounces, I found something from my end that I wanted to change which required me to re-bounce 5 snapshots. While rebouncing, I realized something was still not how I wanted, and I tried to cancel by pressing the BF Cancel button. It simply ignored the dozens of clicks I did at various times, and just kept bouncing more files. I finally got it to stop by clicking the Pro Tools Cancel button while it was bouncing a file. Is the BF cancel button supposed to cancel mid-bounce, or while setting up the next bounce? Because if it is, I couldn't get it to stop doing what it was doing.
Here's the Collected Files:
http://www.epicscore.com/online/BounceFactoryData-gabriel-2025-05-05-20-43-02-625.zip
Here is the text from the Error logs: On the first failure, I just copied near where the failure occurred.
Monday, May 5, 2025 8:30:18 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Emperor Zero (Mus-A) - 1 tracks" in session "Emporer Zero Master-06"
Monday, May 5, 2025 8:30:51 PM: [Bounce Selected Snapshots] [INFO] Finished Bounce
Monday, May 5, 2025 8:30:55 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Emperor Zero (Perc) - 1 tracks" in session "Emporer Zero Master-06"
Monday, May 5, 2025 8:31:29 PM: [Bounce Selected Snapshots] [INFO] Finished Bounce
Monday, May 5, 2025 8:31:33 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Emperor Zero (ARPS) - 3 tracks" in session "Emporer Zero Master-06"
Monday, May 5, 2025 8:32:04 PM: [Bounce Selected Snapshots] [INFO] Finished Bounce
Monday, May 5, 2025 8:32:09 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Emperor Zero (SYNTHS1) - 3 tracks" in session "Emporer Zero Master-06"
Monday, May 5, 2025 8:32:41 PM: [Bounce Selected Snapshots] [INFO] Finished Bounce
Monday, May 5, 2025 8:32:45 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Emperor Zero" in session "Emporer Zero Master-06"
Monday, May 5, 2025 8:33:16 PM: [Bounce Selected Snapshots] [INFO] Finished Bounce
Monday, May 5, 2025 8:33:21 PM: [Bounce Selected Snapshots] [INFO] Starting to bounce 14 snapshots in session Final Eclipse Master-02
Monday, May 5, 2025 8:33:21 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Final Eclipse (Perc) - 1 tracks" in session "Final Eclipse Master-02"
Monday, May 5, 2025 8:34:04 PM: [Bounce Selected Snapshots] [WARN] batchBounce reported an error:
Failed Bounce
Monday, May 5, 2025 8:34:05 PM: [Bounce Selected Snapshots] [WARN] Bounce Failed!
This second error log is from when it just opened all 5 sessions but didn't actually bounce anything.
Monday, May 5, 2025 8:48:53 PM: [Bounce Selected Snapshots] [INFO] Bouncing 14 passes for the currently open session
Monday, May 5, 2025 8:48:53 PM: [Bounce Selected Snapshots] [INFO] Starting to bounce 14 snapshots in session Final Eclipse Master-02
Monday, May 5, 2025 8:48:53 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Final Eclipse (BRASS) - 2 tracks" in session "Final Eclipse Master-02"
Monday, May 5, 2025 8:49:12 PM: [Bounce Selected Snapshots] [WARN] batchBounce reported an error:
ReferenceError: bounceNames is not defined
Monday, May 5, 2025 8:49:12 PM: [Bounce Selected Snapshots] [INFO] Starting to bounce 17 snapshots in session Gladius Ultimus Master
Monday, May 5, 2025 8:49:12 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Gladius Ultimus (GUITARS) - 3 tracks" in session "Gladius Ultimus Master"
Monday, May 5, 2025 8:49:53 PM: [Bounce Selected Snapshots] [WARN] batchBounce reported an error:
ReferenceError: bounceNames is not defined
Monday, May 5, 2025 8:49:53 PM: [Bounce Selected Snapshots] [INFO] Starting to bounce 15 snapshots in session Hell Savior Master-04a
Monday, May 5, 2025 8:49:53 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Hell Savior (DRUMS) - 5 tracks" in session "Hell Savior Master-04a"
Monday, May 5, 2025 8:50:37 PM: [Bounce Selected Snapshots] [WARN] batchBounce reported an error:
ReferenceError: bounceNames is not defined
Monday, May 5, 2025 8:50:37 PM: [Bounce Selected Snapshots] [INFO] Starting to bounce 18 snapshots in session Inferno Rising Master
Monday, May 5, 2025 8:50:37 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Inferno Rising (SYNTHS1) - 3 tracks" in session "Inferno Rising Master"
Monday, May 5, 2025 8:51:18 PM: [Bounce Selected Snapshots] [WARN] batchBounce reported an error:
ReferenceError: bounceNames is not defined
Monday, May 5, 2025 8:51:18 PM: [Bounce Selected Snapshots] [INFO] Starting to bounce 16 snapshots in session Shadow Protocol Master
Monday, May 5, 2025 8:51:18 PM: [Bounce Selected Snapshots] [INFO] Setting up to bounce snapshot "Shadow Protocol (THUMPS) - 1 tracks" in session "Shadow Protocol Master"
Monday, May 5, 2025 8:52:01 PM: [Bounce Selected Snapshots] [WARN] batchBounce reported an error:
ReferenceError: bounceNames is not defined
Thanks.
-gabe
PS. Another weird thing happened near the beginning of the whole process of the first snapshots. I took 4 or 5 snapshots, and then, I'm sorry, I just don't know what happened---I think it was something funky with persistent windows that would not go away. There was more than one persistent window hanging around..Ultimately, I decided to quit Pro Tools and close Bounce Factory, and then when I re-opened Bounce Factory, the few snapshots that I had taken disappeared and the list was empty. That one caught me by surprise. I only lost a few snapshots, but that was a weird one.
I like Bounce Factory. I want to make it part of my workflow, but I feel like I'm still spending a fair amount of time chasing some things down with it. And my demo time is almost over….Please advise.
Andrew Scheps @Andrew_SchepsThanks for all the detailed info! I'll take things one at a time.
Cancel Button: There are a few times in the process where the Bounce Factory Cancel button can actually cancel, but unfortunately it's at the mercy of what's happening in Pro Tools and SoundFlow as to whether it can interrupt the main thread. Cancelling the bounce itself in PTs is definitely the best way to do it. If you're really stuck there is a "Stop All Running Commands" function in the SoundFlow menu (which has a default shortcut of shift-ctrl-escape). You should restart BF after using that one.
The bouncing itself: Every once in a while Pro Tools gets in a weird state where it functions correctly but to the outside world acts as if it's locked up. When BF tries to do things, it relies on PTs reporting back that those things have happened. When BF doesn't get the correct feedback it will attempt to skip what's not working but try the next task to see how much of the work it can get done. In your case it was failing trying to set up the first bounce for each session it opened, then optimistically hoped the next session would be responsive and cycled through the ones that were left. This does happen sometimes, but in my experience it's not that common. Restarting PTs seems to be the only way to wake it up.
Snapshots disappearing: I have absolutely no idea what that was. I don't see anything in the logs related to it. If Snapshots are successfully completed and show up in the list, that also means they are stored on the disk and should absolutely be there when you re-open the app. If you mean that you were in the midst of taking the Snapshot itself, then all of the setup and mix passes you have made will be there if you restart the Snapshot process without closing the app but won't be persistent when closing and re-launching. If you have any more info about the sequence of events on that one it would be great.
Thanks,
Andrew- GGabriel Shadid @Gabriel_Shadid
Hi.
Regarding the disappearing Snapshots---hehe I'm doing my best to recollect. Here we go:
-I started by Deleting everything out of the Snapshot list before setting up any bounces.
-I started with the first Snapshot.
-Almost immediately, I started getting persistent windows that would not go away.
-I tried to ignore them, but after a couple snapshots, there were actually a few dialog windows that were persistent on the screen. There enough windows that it was getting confusing as to which window was the new active ACTUAL window I should be clicking for Bounce Name. After 4 or 5 snapshots, and so many windows persisting and being confused on which window to click, I decided to quit Pro Tools and Bounce Factory and relaunch. It was quitting Pro Tools that made the persistent dialog windows finally go away.
-When I relaunched both Pro Tools and BF, the Snapshot list was empty.I’m starting to wonder if all the persistent dialog windows meant that BF wasn’t getting the OK command to actually save the snapshot? But there were a few snapshots in the list…….As I said, this one caught me off-guard. I was focusing on getting the bounces going, so I wasn’t as much in ”testing” mode, so when it got funky, I was like, wait….what just happened? Hahaha
-gabe
Andrew Scheps @Andrew_SchepsThat's very very strange. I've seen the one dialog hanging around in the background (the one that asks for a name for the Snapshot to save it in the app, and I only ever see it while I'm editing an existing Snapshot), but never more than one dialog and it's never done anything but be annoying. What other windows were there?
- GGabriel Shadid @Gabriel_Shadid
I just opened the session now that it occurred in to see what windows were there. Pro Tools Edit window is in the foreground. This particular session has the MIDI editor page behind it. I don't always have the MIDI editor page open, but it is in this session due to having to add some MIDI stuff to the session. The Mix window is always hanging out in the back. It's always open but I don't use it that often. I do most things off the Edit page. I always have a Waves Dorrough meter open (not in focus) in the top right of the computer screen. And of course, Bounce Factory was open.
-gabe
- Andrew Scheps @Andrew_Scheps
Sorry, I meant the extra BF windows. You said there was more than 1.
- GGabriel Shadid @Gabriel_Shadid
Oh, if I'm recalling correctly---and I'm sorry I didn't get a screenshot of it---I believe all of them were confirmation dialog windows of the Snapshot names. That's why I was getting confused on which one to click. And that's why I ultimately quit everything and started over because I was getting confused about which window was the current active one to dismiss.
Since I was only a few snapshots into the process of setting up the 19 bounces of that session, I'm trying to think of what else those windows could have been....yeah, I believe they were snapshot name confirmation windows.
- Andrew Scheps @Andrew_Scheps
Hmmmmm, like I said I've only ever seen 1. You seem to have all the luck.
- GGabriel Shadid @Gabriel_Shadid
Maybe I should go buy a lottery ticket!
- GGabriel Shadid @Gabriel_Shadid
You know, this exact process is how I got my first opportunity at beta-testing----back in the mid-90's. I was using Opcode Vision. And I kept running into problems. I didn't know anything about beta-testing back in those days---never even heard of it. One day, after several weeks of calling with problems, they asked me if I wanted to be a beta-tester. My response was, "what's that?" hahaha
I went on to beta test for Opcode, Waves, Spectrasonics and several others. (Ended up as the beta-moderator for Stylus RMX and writing RMX's 70,000 word user guide.) Anyway, those days are behind me (I met a lot of nice people being a beta tester), but I am having a bit of deja vu. :)
I do appreciate your support. You are very responsive.
btw, are you behind Waves' Scheps Omni Channel? Like did you have a big hand in its development? That plugin is quite powerful.
-gabe