u-he

bmrzycki · Post by **bmrzycki** » Sat Nov 30, 2013 11:00 pm

3ee wrote:
Satin log wrote:[...]
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQUNEXPECTED SILENCE at processReproEQ

UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
UNEXPECTED SILENCE at processReproEQ
[...]

...and it goes on like that for many pages.

Added: oh yeah, Satin works without a problem!

I get the same thing and it's still working fine on all channels. No sign of BUG FRIDAY! anywhere in the log.

Tp3 · Post by **Tp3** » Sat Nov 30, 2013 11:02 pm

Are others experiencing unproportional CPU jumps from instance to instance ?

First instance of SATIN consumes 8% on my machine. upon loading the second instance, CPU meter jumps to 25-30% (!)...

Lujxio · Post by **Lujxio** » Sat Nov 30, 2013 11:30 pm

Urs wrote:
Breeze wrote: However, here's a suspicion: It may happen when a project is reopened and not all tracks start processing at once. That is, maybe some tracks are not processed right away (track isn't selected, audio starts a few bars in). Maybe the UI of such s track is open.

*sigh* if it's a threading problem and the amount of logging interferes with it... it'll be hard to find. Anyone with an 8GHz i9 machine?

That would happen to me with an Older version of Diva, when I opened some projects with Diva no sound

crazyfiltertweaker · Post by **crazyfiltertweaker** » Sat Nov 30, 2013 11:56 pm

nice idea!

U-He is the best!

SJ_Digriz · Post by **SJ_Digriz** » Sun Dec 01, 2013 12:08 am

Satin working fine, but the VST3 version won't save the loaded preset in Cubase 7 or Sonar X3, but the VST2 version does. LOL ... no bug friday so far though.

timbesamusca · Post by **timbesamusca** » Sun Dec 01, 2013 1:07 pm

I've tested it again with Build 2086 still no "bug Friday"!

kingmobmaskreplica · Post by **kingmobmaskreplica** » Sun Dec 01, 2013 1:36 pm

Tested with both debug versions. No Bug Friday on ProTools 10 or 11 on Mac. Boo and indeed hoo!

Ameyah Audio · Post by **Ameyah Audio** » Sun Dec 01, 2013 2:47 pm

Tp3 wrote:Are others experiencing unproportional CPU jumps from instance to instance ?

First instance of SATIN consumes 8% on my machine. upon loading the second instance, CPU meter jumps to 25-30% (!)...

same here, 8% cpu usage with one instance and added the 2nd boom 25% CPU usage and after 5 instances 100$ cpu and thats an AMD 8 core.

i gave up - need the 2nd screen for the notebook and studies.
good luck everybody.

Tp3 · Post by **Tp3** » Sun Dec 01, 2013 3:00 pm

Trancestorm wrote:
Tp3 wrote:Are others experiencing unproportional CPU jumps from instance to instance ?

First instance of SATIN consumes 8% on my machine. upon loading the second instance, CPU meter jumps to 25-30% (!)...
same here, 8% cpu usage with one instance and added the 2nd boom 25% CPU usage and after 5 instances 100$ cpu and thats an AMD 8 core.

i gave up - need the 2nd screen for the notebook and studies.
good luck everybody.

Well, I'm not "giving up".

I have faith in the guys

HiEnergy · Post by **HiEnergy** » Sun Dec 01, 2013 5:15 pm

I even tested with Maschine 1.7 inside of Bitwig Beta. No traces of Friday bugs here...

Urs: Willst Du die Maschine-Bitwig-Logfiles haben?

Urs · Post by **Urs** » Sun Dec 01, 2013 5:43 pm

HiEnergy wrote:I even tested with Maschine 1.7 inside of Bitwig Beta. No traces of Friday bugs here...

Hmmm...

Urs: Willst Du die Maschine-Bitwig-Logfiles haben?

ja, bitte.

#----

I think we're looking at it from the wrong angle... we have 200+ testers here, and while some experience the symthoms, they're not related to the things we thought they would.

I'll put my head together with Sascha and Clemens tomorrow. Maybe we can come up with a new strategy.

HiEnergy · Post by **HiEnergy** » Sun Dec 01, 2013 6:03 pm

Urs wrote:ja, bitte.

Urs: You may have mail.

clangorous · Post by **clangorous** » Mon Dec 02, 2013 2:35 am

Urs,

Had it happen, but no "Bug Friday" in the log that I can find. First time one of my Satin tracks had no sound. Second time all but one of my Satin tracks had no sound, which happened to be a track where the VSTi had crashed.

Two logs sent to support@u-he.com in case they are useful.

indy138 · Post by **indy138** » Tue Dec 03, 2013 3:42 am

So I guess with Monday gone, it's over now?

I've tested it in the Live 9 Suite with different arrangements, put a big strain on my 2009 MacBook Pro. But no 'Bug Friday', I also searched for 'Freitag', just to be sure!

Urs · Post by **Urs** » Tue Dec 03, 2013 8:07 am

Well, it seems to me that whatever we hoped to find, isn't there.

We're going to do a few things now:

- write test programs for certain areas that seemed problematic in the past
- write code to see whether muted Satin's process at all
- take all the current debug stuff out
- generalise that debug stuff for quick injection in future cases
- figure out new stress test
- evaluate freakingly expensive bug hunting software

While we do this we'll try to release Diva 1.3 and Zebra 2.7 this week. Otherwise we won't have enough time to respond to feedback before we go on vacations. If we can't get Satin to work flawless before then, we simply have to keep it at 1.1 until January.

Anyhow, there's still a good chance for an timely fix

u-he

KVR Audio

Bug Friday - win & suffer with u-he!