git-moss / DrivenByMoss-Documentation

The documenation for DrivenByMoss for Bitwig and Cockos Reaper
GNU Lesser General Public License v3.0
146 stars 24 forks source link

BUG - X-Touch - NOT WORKING IN REAL BIG PRODUCTION SYSTEMS #35

Closed mduque123 closed 1 year ago

mduque123 commented 1 year ago

When selecting anoter track in the MCP and returning back click to anoter the fader does not change the volume in the selected track but in anoter track. This is very confusing.

I have had to change te configuration to: Select Channel on Fader Touch: On , Activate Volume mode on Fader Touch: On.

It is a Pitty that this does not work in a real system with 4 or 5 midi controllers and a bounch of tracks (more than 100).

git-moss commented 1 year ago

Can you send me a test project which shows the issue? And some steps how to reproduce it.

When you say "it changes it the volume of another track" -> which one? The previous track? Did the selection got set to the new one?

Furthermore, what is your OS?

mduque123 commented 1 year ago

Play with Tracks3.zip

Just have TCP and MCP docked. Select track number 24, move XT fader, then select 16 and move the corresponding father in the XTouch and the one moving te volume is the 24 instead (even this is not selected)

I work with W10 and Reaper 6.79

git-moss commented 1 year ago

I cannot replicate this. I am not running SWS. Have you tried if this makes a difference? It could also help if you can make a little video.

Might also be worth checking if there is any Reaper setting related to track selection.

mduque123 commented 1 year ago

I will create another clean without SWS

El mié, 3 may 2023 21:09, Jürgen Moßgraber @.***> escribió:

I cannot replicate this. I am not running SWS. Have you tried if this makes a difference? It could also help if you can make a little video.

— Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss-Documentation/issues/35#issuecomment-1533560378, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJQXXQVBRWNHGNMH3542X4LXEKUOFANCNFSM6AAAAAAXSBSHKA . You are receiving this because you authored the thread.Message ID: @.***>

mduque123 commented 1 year ago

However I hope this is not the issue. I need SWS for a lot of things

El mié, 3 may 2023 21:43, Duque LR @.***> escribió:

I will create another clean without SWS

El mié, 3 may 2023 21:09, Jürgen Moßgraber @.***> escribió:

I cannot replicate this. I am not running SWS. Have you tried if this makes a difference? It could also help if you can make a little video.

— Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss-Documentation/issues/35#issuecomment-1533560378, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJQXXQVBRWNHGNMH3542X4LXEKUOFANCNFSM6AAAAAAXSBSHKA . You are receiving this because you authored the thread.Message ID: @.***>

mduque123 commented 1 year ago

Hi. I just uninstalled SWS and still have the same problem. It does not happen with CSI or Kinkle protocols.

Later today or tomorrow I will film a video with the phone.

Thanks a lot.

On Wed, 3 May 2023 at 22:00, Duque LR @.***> wrote:

However I hope this is not the issue. I need SWS for a lot of things

El mié, 3 may 2023 21:43, Duque LR @.***> escribió:

I will create another clean without SWS

El mié, 3 may 2023 21:09, Jürgen Moßgraber @.***> escribió:

I cannot replicate this. I am not running SWS. Have you tried if this makes a difference? It could also help if you can make a little video.

— Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss-Documentation/issues/35#issuecomment-1533560378, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJQXXQVBRWNHGNMH3542X4LXEKUOFANCNFSM6AAAAAAXSBSHKA . You are receiving this because you authored the thread.Message ID: @.***>

-- Manuel Duque

mduque123 commented 1 year ago

https://drive.google.com/file/d/12om0VzmmMYIvaLk4igEJBcSHpwP6j101/view?usp=sharing

This is the video demonstration of the error

git-moss commented 1 year ago

Thanks! The helpful hint was finally that it does only happen if you disable the Volume mode on touch. Will be fixed in the next update!

mduque123 commented 1 year ago

What great news Jurgen :) Then your extension is the best in the world.

On Sun, 7 May 2023 at 19:19, Jürgen Moßgraber @.***> wrote:

Closed #35 https://github.com/git-moss/DrivenByMoss-Documentation/issues/35 as completed.

— Reply to this email directly, view it on GitHub https://github.com/git-moss/DrivenByMoss-Documentation/issues/35#event-9184650438, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJQXXQX2AGOMY66S2T7ZZH3XE7KQPANCNFSM6AAAAAAXSBSHKA . You are receiving this because you authored the thread.Message ID: <git-moss/DrivenByMoss-Documentation/issue/35/issue_event/9184650438@ github.com>

-- Manuel Duque