Re: New Waves Central a leap forward

[CHUCK REICHEL]

Hi Jesse,
Nice to "see" some VoiceOver accessibility being implemented. ;)
Give this guy Rani a report on whats working & what needs fixed. :)
Rani Merom 
Rani has the authority to get er done!

Talk soon
Chuck
"God does not play dice with the universe"
"Albert Einstein’

On Oct 29, 2019, at 12:19 PM, Jesse Kragiel wrote:

> As the subject says, the new Waves Central manager is a leap forward in 
> accessibility when compared to any prior version. I launched it, and 
> immediately was frustrated because the EULA screen would not allow any 
> navigation. I figured, business as usual, but my niece was in the room, so 
> she clicked the button, and I was surprised to be greeted with a typical web 
> view which allowed me to navigate and press elements on the screen using 
> typical VO commands. I bought and successfully authorized some plugins, went 
> into the settings screen and performed cleanup and uninstall operations with 
> no problems whatsoever. There are two glaring problems. The first is that the 
> state of checkboxes isn't reported, almost a deal breaker until you figure 
> out that by default, nothing is checked, and the first checkbox in the list 
> always selects everything. Let's remember that up till yesterday, there was 
> nothing we could do in Central without a working pair of eyes close by.
> This isn't perfect, but it's a giant forward step. If only Waves could figure 
> out how to make its toolbars accessible all across the board! I have used 
> VOCR to successfully use the toolbar in some of the plugins, but not all.  
> Finally though Waves Central works, and it's far easier than iLok or Avid 
> Link! This is huge!
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/9c7a0cd0-c566-4f36-8f9c-61467aeef677%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/568353EA-E392-4937-AB5B-DD4B0ABACC50%40gmail.com.

Re: Kontakt6 plug-in

[Slau Halatyn]

I haven't noticed any significant difference but it stands to reason that 
Komplete Kontrol would presumably take a bit longer since the plug-in itself 
needs to load Kontakt within itself. frankly, it wouldn't matter to me which 
one to use except for the fact that Komplete Kontrol offers the possibility of 
NKS support in many cases. With Kontakt itself, there's the extra layer of 
having to load instruments by browsing, etc. whereas KK has a more immediate 
method of loading NKIs. It's almost 6 of one and half a dozen of the other.
Slau


> On Oct 29, 2019, at 11:24 AM, John André Lium-Netland 
>  wrote:
> 
> Hi,
> 
> I have special interest in this thread, since I try to do the same thing. I 
> have tried to load Kontakt instruments both from Kontakt and from Komplete 
> Kontrol. In both cases from the PT plugin. I have a feeling that the Komplete 
> Kontrol plugin loads the instruments faster than the Kontakt plugin. Is this 
> true or false? For a specific task, I’ll create TFX files in PT for a set of 
> Kontakt instruments, but I’ve not decided if it’s best to do that from 
> Kontakt or from Komplete Kontrol.
> 
> Any suggestions or reasons to choose the one over the other solution?
> 
> Best,
> John André
> 
>  
> On 29 Oct 2019, at 14:38, Slau Halatyn  > wrote:
> 
> Hi Martin,
> Use Control+f to open the file menu and you'll get a number of options, among 
> them, the Load Instrument option. Let me know if that works for you.
> HTH,
> Slau
> 
> 
>> On Oct 29, 2019, at 6:18 AM, Martin (Punky) Sopart > > wrote:
>> 
>> Hello Slau and others!
>> 
>> Here is the long story...
>> 
>> I have an instrument for the full version of Kontakt.
>> Copying the folder structure into the user content of NI and running KK 
>> standalone makes it possible to browse and open that instrument in KK 
>> standalone and KK plug-in in Pro Tools.
>> 
>> Unfortunately the instruments interface must be treated with VOCR and the 
>> mouse macros.
>> Due to that fact I thought that it might be better to get rid of 
>> non-relevant screen informations by opening the Kontakt plug-in in Pro Tools 
>> without KK over it.
>> But how do I open my instrument here?
>> Is there a way to test the macros for Kontakt plug-in anyhow.
>> Control+1 and Control+B do nothing...
>> 
>> Thanks and best! / Martin
>>> -Original Message-
>>> From: ptaccess@googlegroups.com  
>>> [mailto:ptaccess@googlegroups.com ]
>>> On Behalf Of Slau Halatyn
>>> Sent: Sunday, October 27, 2019 11:47 PM
>>> To: PTAccess List >> >
>>> Subject: Re: Kontakt6 plug-in
>>> 
>>> Hi Martin,
>>> I think a couple of things have changed from version 5 to version 6 
>>> including
>>> the ability to "add" a Kontakt library so the whole browser question might 
>>> be
>>> irrelevant, I'm not sure. I do know that, when Kontakt 6 came out, I 
>>> verified
>>> that the macros for loading NKIs and batch resaving, etc. did work and the
>>> interface was largely unchanged. I'll have to revisit the whole question of
>>> how the browsing might have changed.
>>> HTH,
>>> Slau
>>> 
>>> 
>>> 
>>> On Oct 27, 2019, at 12:54 PM, Martin (Punky) Sopart
>>> mailto:m...@cakewalker.de> >> > > wrote:
>>> 
>>> Hello Slau and others!
>>> 
>>> I just imported and activated the Keyboard Maestro macro groups
>>> for Kontakt plug-in.
>>> Could I use them with the current version of Kontakt:
>>> 
>>> When e.g. pressing Control+B to get the browser status, nothing
>>> happens.
>>> Same for Control+1.
>>> 
>>> Thanks for helping.
>>> 
>>> Best! / Martin
>>> 
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to ptaccess+unsubscr...@googlegroups.com 
>>> 
>>> >> > .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/ptaccess/ACF037AD-5372-437C-985D- 
>>> 
>>> 72065A52EAE7%40cakewalker.de .
>>> 
>>> 
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to ptaccess+unsubscr...@googlegroups.com 
>>> 
>>> >> > .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/ptaccess/0FDC24D4-4733-4701-8FC1- 
>>> 

New Waves Central a leap forward

[Jesse Kragiel]

As the subject says, the new Waves Central manager is a leap forward in 
accessibility when compared to any prior version. I launched it, and 
immediately was frustrated because the EULA screen would not allow any 
navigation. I figured, business as usual, but my niece was in the room, so 
she clicked the button, and I was surprised to be greeted with a typical 
web view which allowed me to navigate and press elements on the screen 
using typical VO commands. I bought and successfully authorized some 
plugins, went into the settings screen and performed cleanup and uninstall 
operations with no problems whatsoever. There are two glaring problems. The 
first is that the state of checkboxes isn't reported, almost a deal breaker 
until you figure out that by default, nothing is checked, and the first 
checkbox in the list always selects everything. Let's remember that up till 
yesterday, there was nothing we could do in Central without a working pair 
of eyes close by.
This isn't perfect, but it's a giant forward step. If only Waves could 
figure out how to make its toolbars accessible all across the board! I have 
used VOCR to successfully use the toolbar in some of the plugins, but not 
all.  Finally though Waves Central works, and it's far easier than iLok or 
Avid Link! This is huge!

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/9c7a0cd0-c566-4f36-8f9c-61467aeef677%40googlegroups.com.

Re: Kontakt6 plug-in

[John André Lium-Netland]

Hi,

I have special interest in this thread, since I try to do the same thing. I 
have tried to load Kontakt instruments both from Kontakt and from Komplete 
Kontrol. In both cases from the PT plugin. I have a feeling that the Komplete 
Kontrol plugin loads the instruments faster than the Kontakt plugin. Is this 
true or false? For a specific task, I’ll create TFX files in PT for a set of 
Kontakt instruments, but I’ve not decided if it’s best to do that from Kontakt 
or from Komplete Kontrol.

Any suggestions or reasons to choose the one over the other solution?

Best,
John André

 
On 29 Oct 2019, at 14:38, Slau Halatyn  wrote:

Hi Martin,
Use Control+f to open the file menu and you'll get a number of options, among 
them, the Load Instrument option. Let me know if that works for you.
HTH,
Slau


> On Oct 29, 2019, at 6:18 AM, Martin (Punky) Sopart  > wrote:
> 
> Hello Slau and others!
> 
> Here is the long story...
> 
> I have an instrument for the full version of Kontakt.
> Copying the folder structure into the user content of NI and running KK 
> standalone makes it possible to browse and open that instrument in KK 
> standalone and KK plug-in in Pro Tools.
> 
> Unfortunately the instruments interface must be treated with VOCR and the 
> mouse macros.
> Due to that fact I thought that it might be better to get rid of non-relevant 
> screen informations by opening the Kontakt plug-in in Pro Tools without KK 
> over it.
> But how do I open my instrument here?
> Is there a way to test the macros for Kontakt plug-in anyhow.
> Control+1 and Control+B do nothing...
> 
> Thanks and best! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com  
>> [mailto:ptaccess@googlegroups.com ]
>> On Behalf Of Slau Halatyn
>> Sent: Sunday, October 27, 2019 11:47 PM
>> To: PTAccess List > >
>> Subject: Re: Kontakt6 plug-in
>> 
>> Hi Martin,
>> I think a couple of things have changed from version 5 to version 6 including
>> the ability to "add" a Kontakt library so the whole browser question might be
>> irrelevant, I'm not sure. I do know that, when Kontakt 6 came out, I verified
>> that the macros for loading NKIs and batch resaving, etc. did work and the
>> interface was largely unchanged. I'll have to revisit the whole question of
>> how the browsing might have changed.
>> HTH,
>> Slau
>> 
>> 
>> 
>>  On Oct 27, 2019, at 12:54 PM, Martin (Punky) Sopart
>> mailto:m...@cakewalker.de> > > > wrote:
>> 
>>  Hello Slau and others!
>> 
>>  I just imported and activated the Keyboard Maestro macro groups
>> for Kontakt plug-in.
>>  Could I use them with the current version of Kontakt:
>> 
>>  When e.g. pressing Control+B to get the browser status, nothing
>> happens.
>>  Same for Control+1.
>> 
>>  Thanks for helping.
>> 
>>  Best! / Martin
>> 
>>  --
>>  You received this message because you are subscribed to the Google
>> Groups "Pro Tools Accessibility" group.
>>  To unsubscribe from this group and stop receiving emails from it,
>> send an email to ptaccess+unsubscr...@googlegroups.com 
>> 
>> > > .
>>  To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ptaccess/ACF037AD-5372-437C-985D- 
>> 
>> 72065A52EAE7%40cakewalker.de .
>> 
>> 
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com 
>> 
>> > > .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ptaccess/0FDC24D4-4733-4701-8FC1- 
>> 
>> 348CC3C9908A%40gmail.com 
>> > 
>> 348CC3C9908A%40gmail.com 
>> ?utm_medium=email_source=footer> .
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> 

Re: Kontakt6 plug-in

[Slau Halatyn]

Hi Martin,
Use Control+f to open the file menu and you'll get a number of options, among 
them, the Load Instrument option. Let me know if that works for you.
HTH,
Slau


> On Oct 29, 2019, at 6:18 AM, Martin (Punky) Sopart  wrote:
> 
> Hello Slau and others!
> 
> Here is the long story...
> 
> I have an instrument for the full version of Kontakt.
> Copying the folder structure into the user content of NI and running KK 
> standalone makes it possible to browse and open that instrument in KK 
> standalone and KK plug-in in Pro Tools.
> 
> Unfortunately the instruments interface must be treated with VOCR and the 
> mouse macros.
> Due to that fact I thought that it might be better to get rid of non-relevant 
> screen informations by opening the Kontakt plug-in in Pro Tools without KK 
> over it.
> But how do I open my instrument here?
> Is there a way to test the macros for Kontakt plug-in anyhow.
> Control+1 and Control+B do nothing...
> 
> Thanks and best! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com  
>> [mailto:ptaccess@googlegroups.com ]
>> On Behalf Of Slau Halatyn
>> Sent: Sunday, October 27, 2019 11:47 PM
>> To: PTAccess List > >
>> Subject: Re: Kontakt6 plug-in
>> 
>> Hi Martin,
>> I think a couple of things have changed from version 5 to version 6 including
>> the ability to "add" a Kontakt library so the whole browser question might be
>> irrelevant, I'm not sure. I do know that, when Kontakt 6 came out, I verified
>> that the macros for loading NKIs and batch resaving, etc. did work and the
>> interface was largely unchanged. I'll have to revisit the whole question of
>> how the browsing might have changed.
>> HTH,
>> Slau
>> 
>> 
>> 
>>  On Oct 27, 2019, at 12:54 PM, Martin (Punky) Sopart
>> mailto:m...@cakewalker.de> > > > wrote:
>> 
>>  Hello Slau and others!
>> 
>>  I just imported and activated the Keyboard Maestro macro groups
>> for Kontakt plug-in.
>>  Could I use them with the current version of Kontakt:
>> 
>>  When e.g. pressing Control+B to get the browser status, nothing
>> happens.
>>  Same for Control+1.
>> 
>>  Thanks for helping.
>> 
>>  Best! / Martin
>> 
>>  --
>>  You received this message because you are subscribed to the Google
>> Groups "Pro Tools Accessibility" group.
>>  To unsubscribe from this group and stop receiving emails from it,
>> send an email to ptaccess+unsubscr...@googlegroups.com 
>> 
>> > > .
>>  To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ptaccess/ACF037AD-5372-437C-985D- 
>> 
>> 72065A52EAE7%40cakewalker.de .
>> 
>> 
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com 
>> 
>> > > .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ptaccess/0FDC24D4-4733-4701-8FC1- 
>> 
>> 348CC3C9908A%40gmail.com 
>> > 
>> 348CC3C9908A%40gmail.com 
>> ?utm_medium=email_source=footer> .
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/00b101d58e42%2442b854e0%24c828fea0%24%40cakewalker.de
>  
> .

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/F6357ADB-0061-424C-8A18-CF0DC4C5445E%40gmail.com.

Re: Kontakt6 plug-in

[Slau Halatyn]

Hi Phil,
Actually, that was my point. The UI is the same between both versions. The only 
difference is that they eliminated the process of adding Kontakt libraries.
HTH


> On Oct 28, 2019, at 8:01 PM, Phil Muir  
> wrote:
> 
> Not dissagreeing with you on this. Was just attempting to explain the 
> diference between the Kontakt 5 and 6 interfaces.
> 
> On 28 October 2019 23:40:13 Slau Halatyn  > wrote:
> 
>> Well, the instruments themselves all have their own specific interface but 
>> what I'm talking about is the part of the UI that doesn't change and remains 
>> the same. That's where the toolbar appears and one would normally click on 
>> various controls to achieve various results. That part of the UI has not 
>> changed.
>> 
>> 
>>> On Oct 28, 2019, at 6:53 PM, Phil Muir >> > wrote:
>>> 
>>> I seem to remember that the interface looks the same until you try to load 
>>> a Kontakt 6 instrument.
>>> 
>>> On 27 October 2019 22:47:25 Slau Halatyn >> > wrote:
>>> 
 Hi Martin,
 I think a couple of things have changed from version 5 to version 6 
 including the ability to "add" a Kontakt library so the whole browser 
 question might be irrelevant, I'm not sure. I do know that, when Kontakt 6 
 came out, I verified that the macros for loading NKIs and batch resaving, 
 etc. did work and the interface was largely unchanged. I'll have to 
 revisit the whole question of how the browsing might have changed.
 HTH,
 Slau
 
 
> On Oct 27, 2019, at 12:54 PM, Martin (Punky) Sopart  > wrote:
> 
> Hello Slau and others!
> 
> I just imported and activated the Keyboard Maestro macro groups  for 
> Kontakt plug-in.
> Could I use them with the current version of Kontakt:
> 
> When e.g. pressing Control+B to get the browser status, nothing happens.
> Same for Control+1.
> 
> Thanks for helping.
> 
> Best! / Martin
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/ACF037AD-5372-437C-985D-72065A52EAE7%40cakewalker.de
>  
> .
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/0FDC24D4-4733-4701-8FC1-348CC3C9908A%40gmail.com
>  
> .
 
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 "Pro Tools Accessibility" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to ptaccess+unsubscr...@googlegroups.com 
 .
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/ptaccess/16e14934878.279c.db423894e9b0bc6221d01044e43225ea%40accessibilitytraining.co.uk
  
 .
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com 
>>> .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ptaccess/273E883A-BB26-49F4-9A79-4F189FEBA45F%40gmail.com
>>>  
>>> .
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> 

RE: Kontakt6 plug-in

[Martin (Punky) Sopart]

Hello Slau and others!

Here is the long story...

I have an instrument for the full version of Kontakt.
Copying the folder structure into the user content of NI and running KK 
standalone makes it possible to browse and open that instrument in KK 
standalone and KK plug-in in Pro Tools.

Unfortunately the instruments interface must be treated with VOCR and the mouse 
macros.
Due to that fact I thought that it might be better to get rid of non-relevant 
screen informations by opening the Kontakt plug-in in Pro Tools without KK over 
it.
But how do I open my instrument here?
Is there a way to test the macros for Kontakt plug-in anyhow.
Control+1 and Control+B do nothing...

Thanks and best! / Martin
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
> On Behalf Of Slau Halatyn
> Sent: Sunday, October 27, 2019 11:47 PM
> To: PTAccess List 
> Subject: Re: Kontakt6 plug-in
> 
> Hi Martin,
> I think a couple of things have changed from version 5 to version 6 including
> the ability to "add" a Kontakt library so the whole browser question might be
> irrelevant, I'm not sure. I do know that, when Kontakt 6 came out, I verified
> that the macros for loading NKIs and batch resaving, etc. did work and the
> interface was largely unchanged. I'll have to revisit the whole question of
> how the browsing might have changed.
> HTH,
> Slau
> 
> 
> 
>   On Oct 27, 2019, at 12:54 PM, Martin (Punky) Sopart
> mailto:m...@cakewalker.de> > wrote:
> 
>   Hello Slau and others!
> 
>   I just imported and activated the Keyboard Maestro macro groups
> for Kontakt plug-in.
>   Could I use them with the current version of Kontakt:
> 
>   When e.g. pressing Control+B to get the browser status, nothing
> happens.
>   Same for Control+1.
> 
>   Thanks for helping.
> 
>   Best! / Martin
> 
>   --
>   You received this message because you are subscribed to the Google
> Groups "Pro Tools Accessibility" group.
>   To unsubscribe from this group and stop receiving emails from it,
> send an email to ptaccess+unsubscr...@googlegroups.com
>  .
>   To view this discussion on the web visit
> https://groups.google.com/d/msgid/ptaccess/ACF037AD-5372-437C-985D-
> 72065A52EAE7%40cakewalker.de.
> 
> 
> 
> --
> You received this message because you are subscribed to the Google Groups
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com
>  .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ptaccess/0FDC24D4-4733-4701-8FC1-
> 348CC3C9908A%40gmail.com
>  348CC3C9908A%40gmail.com?utm_medium=email_source=footer> .


-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/00b101d58e42%2442b854e0%24c828fea0%24%40cakewalker.de.