Workflow Standard Mix pass question
Following up from my request Release Notes for Bounce Factory 1.8 (newest on top) #post-5
This question is perhaps a little redundant now that the BF 1.8 update has introduced the ability to update a Snapshot with a new/different session file.
But I'm still interested on how/why you'd use Standard Mix Passes. This question makes a few assumptions about mixing workflow. I'm basing it off how I think most mixers work - by recording mixes to a 'print' track within the session, which can be used for future reference and subsequent mix revisions are saved with some form of incremental mix session name iteration. Perhaps your workflow is different?
Were you taking new Snapshots every mix revision, assuming the mix session name changes? So even if say a mix had a minor volume adjustment you'd still go through the Snapshot process and getting BF to run the Standard Mix pass? Or was there a more efficient process of updating Snapshots to the current mix?
With revisions, I'd normally just punch-in the section that has been changed, or print entire song manually. I have always found this process optimal rather than taking a Snapshot and then getting BF to print it, as often the mix needs to be sent promptly, rather than waiting for appropriate downtime to allow BF to print when I'm not active at the computer. I only ever saw time-value in BF for doing multitudes of stems, which I mostly use BF for.
Interested to hear anyone else's perspective on this too.
Cheers
Forrester
- 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 toForrester_Savell⬆:Andrew Scheps @Andrew_SchepsHi @Forrester_Savell ,
I have my mixes in the session the same way you do, on playlists on a print track. But to print them I use Bounce Factory. I don't ever print manually or punch into existing mixes. When I used to use analog gear and had to print real-time I would sometimes punch in, but not for many years.
I have a custom script that uses BF code to print my revisions which auto updates the revision number, but would be exactly the same as using a Main Mix Pass if I edited it to change the mix name, pointed it to the new session and switched my print track back to whatever playlist it was on when taking the Snapshot. This not only prints it, but puts it on a playlist on the track and exports my reference I send to the artist. I realise this is new behaviour for BF users, so I'm not pretending this was as easy before 1.8.
When the mix is approved and I need to print mix variants I have saved mix passes that I load into a Snapshot to do instrumentals etc, but the Standard Mix Pass is my Main Mix. The only time I don't use the Standard Mix Pass is if I am making Snapshots exclusively to print stems. Printing the Main Mix manually is something I don't want to do ever.
I can understand printing mix revisions manually since the only change would be to the bounce filename, but even having to make the playlist and export manually is abhorrent to me now.
So, I think the assumption that everybody prints Main Mixes manually might be where we differ. Especially now that you can point a Snapshot to a new session.
Anyway, curious what other users think.
- FForrester Savell @Forrester_Savell
Thanks for your insight. Definitely will be changing workflow now with the 1.8 update.