dwood

Working very well so far for me! I noticed a pop/no audio thing when first hitting play w/the first project I loaded, but sure that's a problem with my ancient interface.

Logic X is recognizing maybe 10% of my 32-bit stuff I paid good money for. Dunno if this is an iLok thing. TBH, just about done with iLok. If you can't just make it work, man . . .

The latest. Purchased, d/l-ed a few hours ago.

Anyone else going through this in HS? 2 weeks in here, and it seems like failed promises.

Thanks for your work Timbertune! Gonna save me a lot of time from here on! -D Ignore my sig—OLD

Again, why should anyone have to go through that to correct an inherent problem? MIDI is 30 years old, for cryin' out loud.

I thought the problem went away a while back (from previous posts a couple years ago.) It's back again. Connecting another keyboard could help you troubleshoot I guess, but I have had problems connecting two at the same time, trying to get them to do different things, I'll just say. I do have an M-audio controller here I use occasionally when I need true waterfall action for organ/synth parts, but it doesn't have a joystick to test whether the CC7 problem is hardware or software related. So weird, as relatively simple as MIDI architecture is (compared to a DAW like Logic), there isn't some backward-engineered, simple interface for, say, plugging in a new, additional device, where it goes (hey, nice new controller—what would you like to call it, and what would you like it to do?) Let's not talk about the environment editor—I've only ever done more harm than good in there, and had to reset to defaults several times. Yes, I know it's powerful—maybe too powerful a hammer for a fly as simple as MIDI. This is one of the few instances where I wouldn't mind a "Clippy" type character dancing around, singing a song asking me what I want to do.

I am having the same problem using an old Roland A-80. Factory reset, but still didn't help problem Curiously, the pitch wheel does not cause this ever, only the joystick. Really infuriating for a few years now.

I, for one, have this near the top of my list of Logic pet peeves. Say you hit pause, and want to scrub in arrange, to find an off-grid event, at a certain zoom level. Well, it doesn't help to have the zoom flying all over the place when you're trying to be precise, and find where a sloppy film editor's cue begins. David, you're a Logic Master, but your advice of "just don't drag vertically" ignores the typical motion of mouse users, especially with mouse acceleration for larger screens. Just when you think you've found your point in the timeline, a quick up or downward movement sends the whole thing either to a ridiculously small, or ridiculously focused view. It just couldn't be hard to implement a tickbox to disable this (at least for me) unusable and productivity-sucking "feature," and i don't know why Apple hasn't addressed it. I sincerely hope I'm ignoring some small, obvious thing that will make me look like a complete idiot.

You can use a Gain plug-in on your Master channel strip and set it to mono to make sure what you hear at home is what you'll get on the PA. David, you've saved the day once again for me. Even though I'm using Logic for a show tonight in a mono-run theater, and not Mainstage. Thank you for getting to know these programs in such detail! PM me for a comp at Largo, if you want, and are bored—not going to spam a link here.

Well, good news then! To avoid having undesired volume changes in your channels strips, you should try to locate what's sending CC7. Logic's channel strip faders respond to that CC7, so if the controller doesn't send CC7 the faders will stay put. If you can't figure out how to make the controller stop sending CC7, you could set up a transformer object like this: http://www.logicprohelp.com/files/filter7_146.png J. Thanks again, jordito! I'll definitely refer back to this if need be! I only use 2 patches on the A-80, with differing velocity curves, so I think it's good for now, (set both patches to "100" for volume, and I don't change between them much) but I'm a total mess in "environment," so this is helpful!

Thanks, CCT! Think it's under control now

I think you were right before in thinking it's a hardware issue. I did some sort of "factory reset" on the A-80 from the manual, and the pitch bender problem went away. So weird it happened at the same time as I made the changes in Logic. Although now it changes volume on choosing different patches*, that is way less a problem. Thanks for your help, jordito! *A-80's patches, not Logic's.

Ok, I thought so. I'm thinking it very well may be a danged hardware issue, as the pitch wheel doesn't seem to affect the volume, while the joystick one does. That stinks, as I love the A-80's action, and don't have time to take it in (middle of scoring a movie here). Thanks for your quick response, and insight, though! Pretty odd, though, that this all happened right after having Logic "learn" a new midi assignment, and persisting after wiping the prefs clean...

Thanks for that, jordito—but is that fix temporary, or a recommended setting? In other words, will it affect my ability to use midi controllers' knobs/faders and such in future?