You need to upload it to an image service like imageShack or imgur and then link to it from your post, most of these services automatically provide links to the pics for use in forums like KVR.legreg6 wrote:How do I add a screenshot to a post ?
AAX Podolski & Satin (beta)
-
- KVRian
- 573 posts since 20 Aug, 2013
-
- KVRer
- 20 posts since 10 Sep, 2013
Thanks. I've just done it...thought it would show the screenshot upfront but it does not.#rob wrote:You need to upload it to an image service like imageShack or imgur and then link to it from your post, most of these services automatically provide links to the pics for use in forums like KVR.legreg6 wrote:How do I add a screenshot to a post ?
Anyway, Podolski does not load in PT 10.3.5 for me.
It get this message instead :
"This plugin could not be made active because a DAE error was encountered.
DAE error -7054 was encountered.."
-
- KVRian
- 573 posts since 20 Aug, 2013
I don't know if this has been discussed elsewhere already, but it seems that Satin's AAX version has a buggy activation/unlocking routine.
So when you enter your correct user name and serial number in Satin AAX, it will still reject your information and suggest you entered it incorrectly.
Please use any other non-AAX host, even free or demo versions (Logic, GarageBand, Reaper, ...) to load the VST2 or AU version of Satin and unlock/activate it like that. Once it has been unlocked from within another host, it will load fine and show up as registered in Pro Tools as well.
Cheers
So when you enter your correct user name and serial number in Satin AAX, it will still reject your information and suggest you entered it incorrectly.
Please use any other non-AAX host, even free or demo versions (Logic, GarageBand, Reaper, ...) to load the VST2 or AU version of Satin and unlock/activate it like that. Once it has been unlocked from within another host, it will load fine and show up as registered in Pro Tools as well.
Cheers
-
kingmobmaskreplica kingmobmaskreplica https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=313724
- KVRer
- 6 posts since 3 Oct, 2013 from UK
Hi there,
I'm getting the cpu spiking mentioned earlier with Satin on Protools 10.3.6. For a random test I chucked Satin on every track in a large session to see what would happen..... Computer and Protools not happy and refused to add anymore Satins after around twenty or so instances
CPU was jumping from 95 down to 60 or 30 and after reducing down to 8 Satins and a reasonably steady CPU of 30-31 I got repeated messages that more RAM was needed. When trying to add more instances I got 'DAE error: std::bad_alloc'. After closing the session, it would not re-open and crashed on the attempt. A force quit of ProTools allowed the session to be opened afterwards. Hope this helps. Oh and its on MAC
I'm getting the cpu spiking mentioned earlier with Satin on Protools 10.3.6. For a random test I chucked Satin on every track in a large session to see what would happen..... Computer and Protools not happy and refused to add anymore Satins after around twenty or so instances
CPU was jumping from 95 down to 60 or 30 and after reducing down to 8 Satins and a reasonably steady CPU of 30-31 I got repeated messages that more RAM was needed. When trying to add more instances I got 'DAE error: std::bad_alloc'. After closing the session, it would not re-open and crashed on the attempt. A force quit of ProTools allowed the session to be opened afterwards. Hope this helps. Oh and its on MAC
-
- u-he
- Topic Starter
- 28065 posts since 8 Aug, 2002 from Berlin
AAX testing for Satin is now here:
http://www.kvraudio.com/forum/viewtopic ... 16#5532416
We're going to have a dedicated thread with all our AAX stuff shortly, once Satin is good to go.
http://www.kvraudio.com/forum/viewtopic ... 16#5532416
We're going to have a dedicated thread with all our AAX stuff shortly, once Satin is good to go.
