RE: Midi problem

[Tom Hessels]

Hi Slau,

I posted this message in the KK list but because of the fact that it perhaps 
has something to do with a pt problem I weill also post it here:

Hi Slau,

 

The pedals are always connected.

So that’s not the problem.

There is also another strange problem that might be connected with my midi 
problem.

How can i explain it (I read a lot of english but i write it not very often)

And perhaps is what i write now is more in place in the ptaccess list.

Ok, when i start pro tools and choose a project from the recent table the 
project loads innediate and the faders of the fadeport 8 reacts.

But when i start to play the project I only hear ;my audio tracks. No 
instruments tracks are playing and also no effects are heard: no reverbs on 
audio tracks etc.

What i do then is loading the project using the .ptx file.

Often then I have that pedal issue.

I’Ll post this message also in ptaccess.

 

Tom.

Tom Herssels (the Netherlands.)

 

 

Van: komplete-kontrol-acc...@googlegroups.com 
 Namens Slau Halatyn
Verzonden: maandag 18 november 2019 00:00
Aan: komplete-kontrol-acc...@googlegroups.com
Onderwerp: Re: [komplete-kontrol-access] Midi problem

 

The first thing that occurs to me is that you need to make sure that your pedal 
is connected before powering up the NI keyboard. Once that is the case, only 
then you should boot-up your system. At least as a starting point, I'd make 
sure to follow those steps to eliminate variables.

slau

 





On Nov 17, 2019, at 1:28 PM, Tom Hessels mailto:tomhessel...@gmail.com> > wrote:

 

Hi,

 

I have to midi devices connected to my mac:

Native instruments s61 keyboard;

Faderport 8.

The last time (I think since I’m using teh Faderport) I have problems with the 
pedals connected to the s61.

Suddenly the sustain does’nt work annymore or the expression pedal acts strange.

I have to reset things or even restore a time machine backup.

I had alook at audio midie setup app and saw that both devices use port 1.

Could that be the problem or is is it possible to use mor devices on the same 
port?

I tried to change ports but the app seems not very accessible or am i doing 
things wrong?

 

Tom.

Tom Hessels (the Netherlands)

 

 

 

 

-- 
You received this message because you are subscribed to the Google Groups 
"Komplete Kontrol Access" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to   
komplete-kontrol-access+unsubscr...@googlegroups.com.
To view this discussion on the web, visit  

 
https://groups.google.com/d/msgid/komplete-kontrol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com.

 

-- 
You received this message because you are subscribed to the Google Groups 
"Komplete Kontrol Access" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to komplete-kontrol-access+unsubscr...@googlegroups.com 
 .
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/komplete-kontrol-access/CF8D1570-5B7C-4639-B1E4-54B303B37B63%40gmail.com
 

 .

 

 

Van: ptaccess@googlegroups.com  Namens Slau Halatyn
Verzonden: zondag 17 november 2019 16:08
Aan: PTAccess List 
Onderwerp: Re: Midi problem

 

Not sure as this is not Pro Tools specific but there is a Komplete Kontrol 
email list where somebody might have a better idea. I think you can find 
subscription info on www.kk-access.com  

HTH,

Slau

 





On Nov 17, 2019, at 9:59 AM, Tom Hessels mailto:tomhessel...@gmail.com> > wrote:

 

Hi,

 

I have to midi devices connected to my mac:

Native instruments s61 keyboard;

Faderport 8.

The last time (I think since I’m using teh Faderport) I have problems with the 
pedals connected to the s61.

Suddenly the sustain does’nt work annymore or the expression pedal acts strange.

I have to reset things or even restore a time machine backup.

I had alook at audio midie srtup app and saw that both devices use port 1.

Could that be the problem or is is it possible to use mor devices on the same 
port?

I tried to change ports but the app seems not very accessible or am i doing 
things wrong?

 

Tom.

Tom Hessels (the Netherlands)

 

 

 

-- 
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: Automation question.

[Martin (Punky) Sopart]

Hello Chuck!

I contacted them via e/mail.

$75 would be perfect, but the lifetime download is $750.

Best! / Martin


On Nov 17, 2019, at 18:42, CHUCK REICHEL  
wrote:

Hi Martin,

Thats very interesting.
I haven't talked to them in a while though.
Did you call them?
I thought I saw on there site that you could still buy the tutorials but may be 
I miss read that.
BTW
That automation secrets is worth more Than #$75.00.
If it saves your "bacon" just once its paid for.
Talk soon
Chuck

On Nov 17, 2019, at 11:49 AM, Martin (Punky) Sopart wrote:

> Hello Chuch and all!
> 
> I contacted Groove3 and asked for the tutorial.
> They are only selling memberships or lifetime video downloads.
> No mp3.
> The tutorial video "Pro Tools Automation Secrets Pro Tools HD Automation 
> Secrets by Michael Costa” is about 750 $.
> 
> So things have changed I think.
> 
> Best! / Martin
> 
> 
> On Nov 15, 2019, at 19:03, Slau Halatyn  > wrote:
> 
> Glad to hear you've had some success. Keep in mind that the Write To start, 
> Write to All and Write To End commands are normally meant for when you do not 
> have a selection. There are specific times when you absolutely would use 
> those commands in conjunction with a selection. But, when automating 20 
> seconds or so, it doesn't necessarily make sense to use those features since 
> it's perfectly reasonable to have the transport play for 20 seconds.
> 
> An instance where you'd use the Write to All is if you're trying to establish 
> the overall level of a track for an entire timeline. You can get into Auto 
> write mode, engage the transport, set the level and, when you're happy with 
> it, press the write to All button. Then you will have the current automation 
> fader level set across your entire timeline. From there, you can make further 
> adjustments.
> 
> Let's say you wanted to then raise the volume at bar 30 and keep it raised 
> until the end of the timeline, you can once again go into Auto write, make 
> the adjustment and use Write to End to keep the fader level a bit higher 
> until the end.
> 
> Let's say you wanted to once again lower the level but only from bar 60 until 
> 4 bars before the end of the song. You can make a selection between bar 60 
> and 4 bars before the end of the song. Now with a longer selection that you 
> don't need to play in its entirety, you can set the new level and then press 
> Write to All. This will write the new level to the selected range.
> 
> Keep in mind that all of the Write to commands are meant to be executed while 
> the transport is engaged.
> 
> Slau
> 
> 
>> On Nov 15, 2019, at 12:31 PM, Juan Pablo Culasso Alonso > > wrote:
>> 
>> Slau, i had success!
>> I selected a portion of 20 seconds of a clip, automated pan from left to 
>> center by the first 3 seconds, and in the automation window y pressed the 
>> button 
>>  Write Automation to Selection End on Stop
>> So after the second 20 the sound as I expected, it returns to the left.
>> So now I need to check if in the Eucon app, there is already an option to 
>> atach to a key in my  avid transport to this three buttons.
>> 
>> Thanks,
>> JP.
>>> On Nov 15, 2019, at 1:03 PM, Slau Halatyn >> > wrote:
>>> 
>>> Juan,
>>> There could be any number of reasons your panning isn't sticking to the 
>>> right side. I'd suggest the following:
>>> 1. Set your track view to pan.
>>> 2. Select everything from beginning of the session to the end with Option 
>>> Shift Return and press Delete.
>>> 3. Confirm that your audio is still there.
>>> 4. Put your track into Auto Latch mode and, with your pan at center, engage 
>>> the transport and pan to the left.
>>> 
>>> When you stop the transport, your track should remain panned to the right.
>>> 
>>> Another approach you can take is to do this in Auto Write mode and, once 
>>> you've panned to the right, press the Write to End button in the Automation 
>>> window. You'll get a dialog informing you that automation has been written 
>>> to the end of the timeline.
>>> 
>>> Further, it appeared that you had Trim mode checked before engaging the 
>>> transport. Don't use Trim mode in this case. Make sure it's unchecked. Trim 
>>> mode is meant to make relative changes to already recorded automation data.
>>> 
>>> Let me know if this process works for you.
>>> 
>>> Slau
>>> 
>>> 
 On Nov 13, 2019, at 11:20 PM, Juan Pablo Culasso Alonso 
 mailto:jpcula...@gmail.com>> wrote:
 
 Slau, here is an example of panning automation I put in latch mode but the 
 parameter is not saved.
 
 https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1
  
 
 Is a 59 seconds recording. can you check that? and tell me what is wrong?
 
 Thanks,
 Juan.
> On Nov 13, 2019, at 10:01 PM, Slau Halatyn  

Re: Automation question.

[CHUCK REICHEL]

Hi Martin,

Thats very interesting.
I haven't talked to them in a while though.
Did you call them?
I thought I saw on there site that you could still buy the tutorials but may be 
I miss read that.
BTW
That automation secrets is worth more Than #$75.00.
If it saves your "bacon" just once its paid for.
Talk soon
Chuck

On Nov 17, 2019, at 11:49 AM, Martin (Punky) Sopart wrote:

> Hello Chuch and all!
> 
> I contacted Groove3 and asked for the tutorial.
> They are only selling memberships or lifetime video downloads.
> No mp3.
> The tutorial video "Pro Tools Automation Secrets Pro Tools HD Automation 
> Secrets by Michael Costa” is about 750 $.
> 
> So things have changed I think.
> 
> Best! / Martin
> 
> 
> On Nov 15, 2019, at 19:03, Slau Halatyn  wrote:
> 
> Glad to hear you've had some success. Keep in mind that the Write To start, 
> Write to All and Write To End commands are normally meant for when you do not 
> have a selection. There are specific times when you absolutely would use 
> those commands in conjunction with a selection. But, when automating 20 
> seconds or so, it doesn't necessarily make sense to use those features since 
> it's perfectly reasonable to have the transport play for 20 seconds.
> 
> An instance where you'd use the Write to All is if you're trying to establish 
> the overall level of a track for an entire timeline. You can get into Auto 
> write mode, engage the transport, set the level and, when you're happy with 
> it, press the write to All button. Then you will have the current automation 
> fader level set across your entire timeline. From there, you can make further 
> adjustments.
> 
> Let's say you wanted to then raise the volume at bar 30 and keep it raised 
> until the end of the timeline, you can once again go into Auto write, make 
> the adjustment and use Write to End to keep the fader level a bit higher 
> until the end.
> 
> Let's say you wanted to once again lower the level but only from bar 60 until 
> 4 bars before the end of the song. You can make a selection between bar 60 
> and 4 bars before the end of the song. Now with a longer selection that you 
> don't need to play in its entirety, you can set the new level and then press 
> Write to All. This will write the new level to the selected range.
> 
> Keep in mind that all of the Write to commands are meant to be executed while 
> the transport is engaged.
> 
> Slau
> 
> 
>> On Nov 15, 2019, at 12:31 PM, Juan Pablo Culasso Alonso 
>>  wrote:
>> 
>> Slau, i had success!
>> I selected a portion of 20 seconds of a clip, automated pan from left to 
>> center by the first 3 seconds, and in the automation window y pressed the 
>> button 
>>  Write Automation to Selection End on Stop
>> So after the second 20 the sound as I expected, it returns to the left.
>> So now I need to check if in the Eucon app, there is already an option to 
>> atach to a key in my  avid transport to this three buttons.
>> 
>> Thanks,
>> JP.
>>> On Nov 15, 2019, at 1:03 PM, Slau Halatyn  wrote:
>>> 
>>> Juan,
>>> There could be any number of reasons your panning isn't sticking to the 
>>> right side. I'd suggest the following:
>>> 1. Set your track view to pan.
>>> 2. Select everything from beginning of the session to the end with Option 
>>> Shift Return and press Delete.
>>> 3. Confirm that your audio is still there.
>>> 4. Put your track into Auto Latch mode and, with your pan at center, engage 
>>> the transport and pan to the left.
>>> 
>>> When you stop the transport, your track should remain panned to the right.
>>> 
>>> Another approach you can take is to do this in Auto Write mode and, once 
>>> you've panned to the right, press the Write to End button in the Automation 
>>> window. You'll get a dialog informing you that automation has been written 
>>> to the end of the timeline.
>>> 
>>> Further, it appeared that you had Trim mode checked before engaging the 
>>> transport. Don't use Trim mode in this case. Make sure it's unchecked. Trim 
>>> mode is meant to make relative changes to already recorded automation data.
>>> 
>>> Let me know if this process works for you.
>>> 
>>> Slau
>>> 
>>> 
 On Nov 13, 2019, at 11:20 PM, Juan Pablo Culasso Alonso 
  wrote:
 
 Slau, here is an example of panning automation I put in latch mode but the 
 parameter is not saved.
 
 https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1
 Is a 59 seconds recording. can you check that? and tell me what is wrong?
 
 Thanks,
 Juan.
> On Nov 13, 2019, at 10:01 PM, Slau Halatyn  wrote:
> 
> Well, good for you! OK, now when you go to the Automation window, you'll 
> see buttons for writing to the start, end or entire length of the session 
> from beginning to end. With an Avid control surface, there are dedicated 
> buttons for these functions. Anyway, you'll have a much easier time with 
> Ultimate.
> Slau
> 
> 
> 
>> On Nov 13, 

Re: Automation question.

[Martin (Punky) Sopart]

Hello Chuch and all!

I contacted Groove3 and asked for the tutorial.
They are only selling memberships or lifetime video downloads.
No mp3.
The tutorial video "Pro Tools Automation Secrets Pro Tools HD Automation 
Secrets by Michael Costa” is about 750 $.

So things have changed I think.

Best! / Martin


On Nov 15, 2019, at 19:03, Slau Halatyn  wrote:

Glad to hear you've had some success. Keep in mind that the Write To start, 
Write to All and Write To End commands are normally meant for when you do not 
have a selection. There are specific times when you absolutely would use those 
commands in conjunction with a selection. But, when automating 20 seconds or 
so, it doesn't necessarily make sense to use those features since it's 
perfectly reasonable to have the transport play for 20 seconds.

An instance where you'd use the Write to All is if you're trying to establish 
the overall level of a track for an entire timeline. You can get into Auto 
write mode, engage the transport, set the level and, when you're happy with it, 
press the write to All button. Then you will have the current automation fader 
level set across your entire timeline. From there, you can make further 
adjustments.

Let's say you wanted to then raise the volume at bar 30 and keep it raised 
until the end of the timeline, you can once again go into Auto write, make the 
adjustment and use Write to End to keep the fader level a bit higher until the 
end.

Let's say you wanted to once again lower the level but only from bar 60 until 4 
bars before the end of the song. You can make a selection between bar 60 and 4 
bars before the end of the song. Now with a longer selection that you don't 
need to play in its entirety, you can set the new level and then press Write to 
All. This will write the new level to the selected range.

Keep in mind that all of the Write to commands are meant to be executed while 
the transport is engaged.

Slau


> On Nov 15, 2019, at 12:31 PM, Juan Pablo Culasso Alonso  > wrote:
> 
> Slau, i had success!
> I selected a portion of 20 seconds of a clip, automated pan from left to 
> center by the first 3 seconds, and in the automation window y pressed the 
> button 
>  Write Automation to Selection End on Stop
> So after the second 20 the sound as I expected, it returns to the left.
> So now I need to check if in the Eucon app, there is already an option to 
> atach to a key in my  avid transport to this three buttons.
> 
> Thanks,
> JP.
>> On Nov 15, 2019, at 1:03 PM, Slau Halatyn > > wrote:
>> 
>> Juan,
>> There could be any number of reasons your panning isn't sticking to the 
>> right side. I'd suggest the following:
>> 1. Set your track view to pan.
>> 2. Select everything from beginning of the session to the end with Option 
>> Shift Return and press Delete.
>> 3. Confirm that your audio is still there.
>> 4. Put your track into Auto Latch mode and, with your pan at center, engage 
>> the transport and pan to the left.
>> 
>> When you stop the transport, your track should remain panned to the right.
>> 
>> Another approach you can take is to do this in Auto Write mode and, once 
>> you've panned to the right, press the Write to End button in the Automation 
>> window. You'll get a dialog informing you that automation has been written 
>> to the end of the timeline.
>> 
>> Further, it appeared that you had Trim mode checked before engaging the 
>> transport. Don't use Trim mode in this case. Make sure it's unchecked. Trim 
>> mode is meant to make relative changes to already recorded automation data.
>> 
>> Let me know if this process works for you.
>> 
>> Slau
>> 
>> 
>>> On Nov 13, 2019, at 11:20 PM, Juan Pablo Culasso Alonso 
>>> mailto:jpcula...@gmail.com>> wrote:
>>> 
>>> Slau, here is an example of panning automation I put in latch mode but the 
>>> parameter is not saved.
>>> 
>>> https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1
>>>  
>>> 
>>> Is a 59 seconds recording. can you check that? and tell me what is wrong?
>>> 
>>> Thanks,
>>> Juan.
 On Nov 13, 2019, at 10:01 PM, Slau Halatyn >>> > wrote:
 
 Well, good for you! OK, now when you go to the Automation window, you'll 
 see buttons for writing to the start, end or entire length of the session 
 from beginning to end. With an Avid control surface, there are dedicated 
 buttons for these functions. Anyway, you'll have a much easier time with 
 Ultimate.
 Slau
 
 
 
> On Nov 13, 2019, at 4:11 PM, Juan Pablo Culasso Alonso 
> mailto:jpcula...@gmail.com>> wrote:
> 
> Thanks, slau, I just installed it.
> 
> 
>> On Nov 13, 2019, at 6:10 PM, Slau Halatyn > > wrote:
>> 
>> For controls like panning, where you want the value to remain 

Re: Midi problem

[Slau Halatyn]

Not sure as this is not Pro Tools specific but there is a Komplete Kontrol 
email list where somebody might have a better idea. I think you can find 
subscription info on www.kk-access.com 
HTH,
Slau


> On Nov 17, 2019, at 9:59 AM, Tom Hessels  wrote:
> 
> Hi,
>  
> I have to midi devices connected to my mac:
> Native instruments s61 keyboard;
> Faderport 8.
> The last time (I think since I’m using teh Faderport) I have problems with 
> the pedals connected to the s61.
> Suddenly the sustain does’nt work annymore or the expression pedal acts 
> strange.
> I have to reset things or even restore a time machine backup.
> I had alook at audio midie srtup app and saw that both devices use port 1.
> Could that be the problem or is is it possible to use mor devices on the same 
> port?
> I tried to change ports but the app seems not very accessible or am i doing 
> things wrong?
>  
> Tom.
> Tom Hessels (the Netherlands)
>  
>  
> 
> -- 
> 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/000801d59d57%24942647f0%24bc72d7d0%24%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/2E29C104-395A-45EE-9CDF-41DFF409932B%40gmail.com.

Midi problem

[Tom Hessels]

Hi,

 

I have to midi devices connected to my mac:

Native instruments s61 keyboard;

Faderport 8.

The last time (I think since I'm using teh Faderport) I have problems with
the pedals connected to the s61.

Suddenly the sustain does'nt work annymore or the expression pedal acts
strange.

I have to reset things or even restore a time machine backup.

I had alook at audio midie srtup app and saw that both devices use port 1.

Could that be the problem or is is it possible to use mor devices on the
same port?

I tried to change ports but the app seems not very accessible or am i doing
things wrong?

 

Tom.

Tom Hessels (the Netherlands)

 

 

-- 
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/000801d59d57%24942647f0%24bc72d7d0%24%40gmail.com.