KVR Audio

aMUSEd · Post by **aMUSEd** » Sat May 16, 2009 5:17 pm

PaulSC wrote:
aMUSEd wrote:Why does the screen go black when I open the gui the first time? Not a deal killer but weird behaviour for a plugin - like it's taking over the graphics subsystem on its own
known issue, being investigated

Thanks - it says:

4) GUI drawing issue: (i.e. black screen on first load--confined to the GUI window--not the entire computer screen).

but that isn't quite accurate (for me). Initially when the plugin loads the whole screen does go black for about a second and I get that sound you get when you change screen resolution sometimes (like when you play a game that's a different resolution than you are running) - then it reverts to the black plugin screen and I have to close it and repoen to fix it. That's why it seems like it's trying to take over the screen resolution or something.

aMUSEd · Post by **aMUSEd** » Sat May 16, 2009 5:24 pm

Yes my hypothesis appears to be confirmed - it is trying to tap into the graphics hardware. If you reduce the graphics hardware acceleration setting (even just by one notch) in display settings/advanced/troubleshooting the bug does not occur.

Andrew Souter · Post by **Andrew Souter** » Sun May 17, 2009 8:24 am

The Black GUI issue is known.

We are updating a bunch of of low level (SDK) code now. We used VST-GUI for 0.9.x and 1.0.00 and we were intending to completely replace it with our own custom code later in the summer. Denis had some inspirations though a few weeks ago so we are doing this now together with the other low-level stuff like 64-bit support etc.

VST-GUI SDK is sort of old and can give some issues and complications, and we believe the Black-GUI issue/annoyance is a result of this. Thus when we replace this code completely with our own custom code, this issue should disappear. It will also allow us to do other cool things we had in mind for the GUI but were unable to do previously b/c of the limitations imposed by the VST-GUI SDK.

Summary: known issue, and it will be resolved shortly...

Andrew Souter · Post by **Andrew Souter** » Sun May 17, 2009 8:27 am

also for anyone reading who has not used Aether but is reading the thread and considering it... it should be made clear that the Black GUI bug/issue/annoyance has a very simple workaround: simply close/minimize the GUI and then reopen it, and everything is fine. It only occurs on some systems and only on loading the first instance in the project.

Thanks.

I return to the office on May 24.

Out for the rest of the day now...

jensa · Post by **jensa** » Sun May 24, 2009 11:59 pm

Welcome back Andrew! How was the vacation?

Andrew Souter · Post by **Andrew Souter** » Mon May 25, 2009 12:28 pm

It was great.

Denis actually took a short one too, and we are both now back, and fully refreshed and energized and ready to take things to the next level!

If there are still any outstanding questions which may have gotten lost in the rush at the end of the group buy and our subsequent travels, please ask again.

wheever · Post by **wheever** » Mon May 25, 2009 2:57 pm

I asked this upthread:

I bought Aether via the group buy knowing it wasn't yet compatible with OSX 10.4.x yet, but with the hope that you'd fix that in the next rev. So, my question is when is the next rev due? I'm dying to use Aether, but with the Tiger problem I can't even enter my serial in DP!

Thanks!

Blackinfinity · Post by **Blackinfinity** » Tue May 26, 2009 3:28 pm

I have to take back what I said regarding Aether in Windows 7. I got the same problems actually...it did for some reason work good the first day...after fresh windows installed...the day after it was back to normal...I have no idea why...the only difference between the first day and the second is that I had installed more applications in windows.

Andrew Souter · Post by **Andrew Souter** » Tue May 26, 2009 8:40 pm

We are still restructuring some of our low level code base for the 1.1 and future products. This should last at least until the end of the month. We expect that this work will automatically solve most of the outstanding issues, but if any remain we will thoroughly test and debug them at that point.

I would guesstimate we may have something to test/show within two weeks. This is an unofficial guesstimate. Thanks for the patience.

Regarding X.4.11, we have varying reports and we do not officially support X.4.x at this point. Some people are successfully using Logic and Live on X.4.11. The issue you mention may be specific to DP 5.x on X.4.11. We can not reproduce this issue with DP 6 under X.5.x. Do you happen to have any other hosts that you may try to authorize the product?

elxsound · Post by **elxsound** » Tue May 26, 2009 8:46 pm

Hey, welcome back Andrew!

Love the sound of that "future products"

wheever · Post by **wheever** » Thu May 28, 2009 11:26 pm

Galbanum wrote:Regarding X.4.11, we have varying reports and we do not officially support X.4.x at this point. Some people are successfully using Logic and Live on X.4.11. The issue you mention may be specific to DP 5.x on X.4.11. We can not reproduce this issue with DP 6 under X.5.x. Do you happen to have any other hosts that you may try to authorize the product?

I'm using DP 6.02 in 10.4.11. I tried authorizing Aether in both Audiofinder and in Peak 5. In both instances the UI is unresponsive--meaning it doesn't allow me to authorize or respond to any inputs at all. Just sits there. I'm assuming this means the problem is between Aether and OSX 10.4.x.

I know you don't officially support 10.4.x at this point, but as it said on your website that you were working on it, I was hopeful that this fix would be included in the next revision. (Actually, I was counting on it, which is why I did the group buy.)

Andrew Souter · Post by **Andrew Souter** » Fri May 29, 2009 9:31 pm

Can you try something for us: can you try to authorize using the VST version in Peak? Does that work or no?

We do not officially support X.4 at this point, but hopefully we may find a workaround for you.

wheever · Post by **wheever** » Sat May 30, 2009 3:58 pm

Galbanum wrote:Can you try something for us: can you try to authorize using the VST version in Peak? Does that work or no?

I tried this and Peak throws an error that says something like "empty result. Peak is unable to use this plug-in" Other VSTs load fine. Drag, man!

Is there any way to trick Aether into using the generic AU UI?

Thanks for your help!

misterg · Post by **misterg** » Sat May 30, 2009 8:00 pm

wheever wrote: I'm using DP 6.02 in 10.4.11. I tried authorizing Aether in both Audiofinder and in Peak 5. In both instances the UI is unresponsive--meaning it doesn't allow me to authorize or respond to any inputs at all. Just sits there. I'm assuming this means the problem is between Aether and OSX 10.4.x.

I had problems authorizing Aether AU in Live 7 on 10.4.11 (I jumped at the group buy also, hoping Tiger support was forthcoming)

At first I could not enter the codes for the serial, the GUI was unresponsive for me also.
I gave it a couple tries, and eventually clicked a sweet spot in the authorizing panel that let me enter the code.

I don't remember the exact spot I clicked, but it may be worth clicking around to see if this works for you.

I was ready to give up, and just stumbled on this... hope it helps.

wheever · Post by **wheever** » Wed Jun 10, 2009 3:02 pm

misterg wrote: At first I could not enter the codes for the serial, the GUI was unresponsive for me also.
I gave it a couple tries, and eventually clicked a sweet spot in the authorizing panel that let me enter the code.

I don't remember the exact spot I clicked, but it may be worth clicking around to see if this works for you.

I was ready to give up, and just stumbled on this... hope it helps.

No, I can't get this to work in anything. After you entered the serial# did Aether work? I noticed that 2Caudio has changed the language on its home page about supporting Tiger. It looks like they're not going to work on compatibility after all, and I wasted $125. I'm very disappointed. I'm thinking about trying to get my money back.

2C-Aether Reverb