While everyone recovers from turkeys and Black Friday left overs, we've been excessively busy wrecking our brains over a weird bug. It seems to happen only to very few people and it's very unfortunate that no-one at u-he is among those. For that reason it is tough to debug. Tough times often require unconventional methods. Thus we have decided to take the challenge to you guys out there:
Step 1: Download & Install
UPDATE: Final build, a very last chance! Less CPU hungry, focussed on the bug
Satin rev 2107 Win
Satin rev 2107 Mac
(this is a special beta version - not meant for production, but good for bug hunts!)
Step 2: Set up a project
- in your host of choice
- regardless if Mac/Win/VST/AU/AAX/VST3/32/64bit
- add 1-20 audio/master tracks
- add 1-20 Satins
- we recommend not to use existing projects!
Step 3: Playback
- if any Satin doesn't pass audio or is "muted", go straight to Step 5
Note: This version of Satin drains some serious CPU for debugging - if playback stutters, don't worry, it's only this build of Satin! CPU overloads are to be expected.
Step 4: Save Project, Close host, start host, open project, play back again
- is any Satin silent/muted now?
- if not, repeat Step 4 a few times
Step 5: Satin.log
- on your desktop you'll find a file called "Satin.log"
- open in Wordpad/Textedit
- does it contain the phrase "BUG FRIDAY!"?
- if no, go back to Step 4
Step 6: If you have a Satin.log that contains "BUG FRIDAY!"
- please send that Satin.log to support at u-he dot com
The first sender of a Satin.log that contains "BUG FRIDAY!" wins a u-he plug-in of choice
Another u-he plug-in of choice goes to a randomly picked sender of any such Satin.log that reaches us till Monday Dec. 2nd around noon in Berlin.
... but if none come in till Monday then we will assume that whatever we did, it fixed the bug
Anyone can take part, you don't need to be a u-he customer. Needless to say, it doesn't help to just write the phrase into any random Satin.log file - we'll notice whether or not it's genuine
Good luck,
- Urs
