Jump to content

Aramism

Member
  • Posts

    134
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Aramism's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

3

Reputation

  1. I got it to work, thanks again. additional question: how can I make it momentarily UNMUTE it? Meaning the default state is muted, and when I hold the button on the midi controlled, it is unmuted, then when I let it go it goes back to muted state. alternatively regarding the light, I have an arturia keystep 37. I just want to use one of the transport buttons to do the mute/unmute. Right now I have the button on it "clear Last" which has a light on it. But I don't know how to change the light state. I say alternatively because if the first option isn't possible the light option, as described in your post, would also work. By the way if it helps, the reason I'm trying to do figure this is out is because my intention is to use it as a talkback monitor button. I am recording a vocalist remotely using google desktop to control their local computer, so I need my screen to be full screen to see their screen, and I am using audiomovers to monitor the audio two ways. My input in my local daw needs the mute button so that my mic can be shutoff when I'm not talking (like any talkback button in a traditional setting) So either my first question about making it temporally be unmuted only when I press it, or having the light tell me, without looking at my own daw, what state its in, would help me tremendously. THANKS!!
  2. I'm trying to map a button on a midi keyboard to mute and unmute a specific track. I got it mapped but it only mutes when I hold and unmutes when I let go. How can I set it so that every time I press the button on the midi controller it just switches the mute on and off even if I take my finger off the button?
  3. I'm either doing this wrong or it's a bug. When selecting marquee as the secondary mouse click option and using it holding down command, by swiping a region then clicking on the swipe it automatically cuts the region at the marquee range. However, when selecting it either through keyboard shortcut for the tool menu (button T and T) or by setting it as the primary tool from the menu manually it does not cut the region by just clicking on the selection. It only cuts one slice by double clicking like the scissor. Shot a video if it helps https://youtu.be/QfAi0tgX3Y4
  4. OS12 LP 10.7.4 Mac Studio The volume fader in the inspector or mix window does not respond to scroll wheel of any tested 3rd party mouse except Apple's own magic mouse or magic trackpad. I had been using older Logic on older computer until lately and always used a logitech mouse going back 10 years or so and the mouse scrollwheel ALWAYS was able to control the volume fader with a very fine 0.1 db step increment. After updating to mac studio with brand new OS and latest logic this no longer works. Also tried logitech m510, kensington forever mouse and HP x3000 g2 mice. All have the same issue. Have tried installing software for the mice and they do not change anything. PS - As a temporary workaround you can still control it by just pressing down on a mouse button while scrolling the wheel. This is annoying but it's a workaround hopefully until it gets resolved
  5. Ok I got an HP mouse and a Kensington mouse, brand new, and both behaved the same. They work and scrolling in all areas is OK except on the volume fader. Same exact behavior as my original logitech mouse. So it seems to be an issue with logic and I will now report to the bugs center or whatever. Hopefully any others who have a similar issue will find this useful and if someone else has one please report as well so we can get it fixed!!!
  6. I got both apple mouse and magic pad just to test, I'm going to return them. I hate the mouse and how it feels, that's why. The trackpad is more doable but still not ideal. It's a matter of my hand preference and how it feels most comfortable as I do a lot of editing.
  7. I don't have an old logic. This is the latest version of logic and mac OS Anyway, the mouse is still made, it's not from 20 years ago. You can go buy it at staples. Update on MOUSEGATE: I got a brand new logitech an m510, which is a newer model, and has more buttons and software customizing. And... SAME RESULT. One new observation however. When I hold down either the left or right mouse button and scroll, it works. Of course this is cumbersome but it's a temporary solution. Though the resolution is 0.2 a time. Whereas with my other system on a slightly older logic 10.3 I think or 10.4 on OSX 10.11 it is 0.1 at a time. It's always been 0.1 going back as far as I can remember. But now even with the button click + scroll is only does 0.2. I should note that even with the magic trackpad, despite scrolling, it also does 0.2db increments. For comparison, I have a macbook pro with catalina and whatever latest logic is on catalina and both the logitech mouse works and the resolution on the macbook trackpad and the logitech and the external magic trackpad is 0.1 I'm wondering if it's just a logitech thing. So I ordered 3 other brands mice to test. They will come tomorrow and the day after, will update this with finding and report bugs once I isolate all possible issues. The 0.2 thing I guess is another logic bug so maybe others can test it on the latest version?
  8. I bought a new logitech mouse also with support for app specific programming. it's coming tonight just to test it and try to isolate the problem. Who would have thought there would be so much headache over such a seemingly simple problem such as a mouse!!! I've been using the same model forever and it's always worked perfectly! Also as stated before, my current (model m310) mouse works great in all other areas of the OS including all other scroll functions within logic except the volume faders.
  9. it's clear apple has some bugs to fix then! how/where can/do we report these things ?
  10. The mouse is maybe 3-4 years old. The software doesn't do much or change this, I tried it. However something interesting happened. I went and got an apple magic mouse and magic trackpad just to try them and with them it works, and my own mouse the faders work when the apple mouse is simultaneously connected even if I'm not using it (meaning two mice are connected at once) Then as soon as I turn off the apple either mouse or trackpad, my logitech scroller stops moving the fader. Crazy. Not sure what to make of this? Anyone? PS - I'm not keeping the apple mouse or pad, I can't use them they are not for me and I want to use my regular mouse my hand is used to. I just wanted to see if it would work or not.
  11. yes and yes. as i've said repeatedly, the scroll functions fine in all other areas of logic.
  12. But if it works in my current OS and in Logic on ALL other scrolling functions in my new mac/OS 12 and Logic except the fader (and pan pot though not as crucial for me) it doesn't seem like the software is the issue. In either case, I'll try to see if logitech has software for it. When I did a quick search yesterday whatever driver/software logitech had for my mouse wouldn't install as it's too old. Maybe their newest general software will work.
  13. there's no software. it's just a basic mouse. the scroll wheel works overall both throughout OS and within logic for all other scroll things, just no the fader. It works on my older mac forever with no mouse software.
  14. I've been on an older version of Logic Pro X and recently just got a mac studio and did a quantum leap forward to the latest version of Logic and it's great EXCEPT one major thing which is either some setting I have wrong or a bug or Apple just has a special team dedicating to doing things to piss people off and then laugh at them. The scroll wheel on the mouse as far as I can remember always was able to control the volume fader and pan knob. Now it no longer. I did a bunch of googling and it seems that this is some new thing but there wasn't too much info if it's been fixed or a workaround for it somehow? I have just a regular 2 button logitech mouse with a scroll wheel which I've been using for a long time. Any way around this or am I doing something wrong? Thanks!
×
×
  • Create New...