boynigel

disregard question. for some reason I thought there wasn't a 44.1 kHz setting on the helix, and that it started at 48 kHz. gotta stop w/the edibles when I do this stuff ;)

Using an LT as my pro tools interface. when I try to open older sessions that were recorded at 44.1 kHz, I get a message saying, "The current playback engine does not support a sample rate of 44.1 kHz." Anyone know any "tricks" to make it happen?

it should, and it did work! plug and play. went usb route after all because the Arturia didn't come w/its own power supply (!!!) so I dug out an old USB hub and plugged it into my Mac keyboard to gain an extra port. I'm superstitious and didn't want to tempt fate by plugging the old hub directly into the Mac. I thought maybe there'd be a chance of it performing poorly since I was putting it through the keyboard, but it doesn't...so that's good too. at the end of the day it's just midi data so why would it?...but stranger things have happened, and thankfully they didn't. thanks again. learned a lot.

haters gonna hate LOL...seriously though, I get it. I came REALLY close to walking away from PT myself. specifically looked into Reaper and Logic. When I saw just as many issues/problems in their respective user groups as PT, I decided to (again) stick w/the evil I know. I'm old, so I've been w/PT since the 001 days. I know they go back further but I couldn't afford TDM back then. 001 was my gateway. I'm aware PT got complacent, allowing others to eclipse them but when I found that what the others offered wasn't necessarily anything I needed/wanted. Didn't want to have to learn a new ecosystem. and yes, I'm paying more w/PT but not having to pay them $10/mo wouldn't change my financial future if I chose another platform.

Well I think that's the route I'm gonna go then. It'll be money well spent, and I won't have to have the Yamaha taking up all that space in my small home studio anymore. Big thanks to you and @rd2rk for your time and expertise. If I weren't already considering downsizing, I'd probably fight it out w/the Yamaha some more, via the MIDI to USB adapter route suggested, but this situation gave me that extra push to go small, sooner. thanks again.

Okay, regarding the KB reset, the 2nd time was the charm. This time I was greeted by the message, Clr. However, the problem persists. I don't have the cabling needed to take the Helix out of the equation as I've never needed a MIDI to USB until now. That said, now that we know that the Yamaha is the culprit, is there any good reason why this wouldn't work for me? https://www.guitarcenter.com/Arturia/KeyStep-Limited-Black-Edition-1500000048425.gc I am NOT a piano/keys player. I bought the Yamaha back when I had a bandmate who could actually play keys. I just need a small controller for my plugin synths for when I want to add some atmosphere or texture (versus an actual keys "performance") to a recording, and was contemplating purchase of a small controller that I could keep on my desktop long before the Yamaha wigged out. the nice thing about the KB in the link is that it has actual MIDI DIN ports, so no adapters necessary.

I just downloaded a different midi monitor, pic attached. As a best guess, I switched the "display midi notes as" box from hex to decimal. the other display choices were, note (mid C = C3, or, note (mid C = C4). let me know if any of those are preferred.

nothing connected to the host port, nothing connected to midi in port. the switch was always in the MIDI position, I even slid it back and forth a few times in case the connection got wonky. Optimistically tried the sustain pedal (yes, it's Yamaha's own) to no avail. I CAN see the pedal being actuated via the midi monitor I have (see pic). You're right about MAC MIDI monitors. going to the App Store to see if I can find one that offers more info than the one in the pic. I support your evil witch theory because all of this changeover to new gear was going wayyyy too smoothly up until this incident.

this was the first thing I tried as it was potentially the quickest/easiest fix, but no, it wasn't the fix. I was a little concerned that when I did the procedure, nothing special happened w/the KB's display indicating that a reset had occurred. maybe this is by design, but literally every piece of gear I've ever done this on, no matter how old, would at the very least blink the display (in the absence of any actual confirmation message).

Yep, Yamaha. it's sixteen year old P-90 Electric Piano. I did follow your link and will use if necessary. Regarding my Yamaha, I checked the manual and it really didn't offer too much in terms of troubleshooting midi. not the best written manual either. https://www.wwbw.com/Yamaha-P90-Professional-Portable-Stage-Piano-707440.wwbw

it seems the problem might be with my keyboard. when I did the test via Command Center and FS to send a midi note, it worked. I could see the info being recorded on the midi monitor app. But when I turned on my KB, the window started rapidly filling up with F8 messages from my KB as if someone was hammering out 64th notes on whatever key sends an F8 message. while that was happening, if I hit any of the KB keys I could see those notes register on the screen in between the million F8's per-second that were filling the window non-stop. it's like something is jammed on my KB that keeps sending rapid fire F8 messages. Btw- regarding my adapter comment that you didn't understand, regarding frying usb c ports, I was talking about one of these: https://www.amazon.com/Syntech-Adapter-Thunderbolt-Compatible-MacBook/dp/B07CVX3516/ref=sr_1_3?keywords=usb%2Bto%2Busb%2Bc%2Badapter&qid=1655954803&sr=8-3&th=1

two different midi cables. This would be the first time I've used helix w/PT. I had a 2012 MBP that gave up the ghost about 2 years ago and I've been on recording hiatus ever since. I was running a very old version of PT. early 10 if I had to guess. New machine (Mac M1 Max Studio), newest PT version (12), and new interface (Helix). Without getting winded as to my reasons, I had to start from scratch. my keyboard WAS communicating fine with my old version of PT via my box 2 pro firewire interface. Maybe I should bite the bullet and get a small KB controller and go the usb route. My current controller is an 88-key monstrosity anyway.

Before I updated to the latest version of PT, I contemplated going w/another DAW but after 22 years I figured I'd stick w/the evil I know. there's enough outside distractions that can squash creative flow, I don't need it from my DAW too. this is my first hiccup w/the new version.

yep, did all that w/the same result. thanks for trying.

I matched all those settings. still nothing. thanks for your time though

any chance you could share more than the two aforementioned midi settings? I have no idea what MIDI PC Receive, MIDI PC Send, and others should be set to. I've been trying all different kinds of settings but nothing works. As far as protools goes, everything looks good there. I'm definitely not going the usb interface route.

I did that but PT still isn't receiving midi data. I'm reluctant to go the usb route as I've heard stories of usb to usb C adapters frying the usb C ports on my computer (M1 Mac Studio). If I can do it w/the OG midi cables, that's preferred.

I'm using my LT as an audio interface with protools. I have a keyboard hooked up to the midi in of the LT with the hopes of being able to use it to control a mellotron plugin within a protools session. If this can be done, what should my midi settings be? I've been messing around with them in the Global menu but I can't get the keyboard to trigger the soft synth in PT.

How well does it perform in terms of tracking latency whereas it's via the "old" usb, versus usb c or thunderbolt?

Yes but I didn’t see anything specific to running Monterey with the LT as an audio interface on an M1 machine. Unless someone with firsthand experience chimes in, I suppose I can just try it once I get the computer

I’m contemplating a Mac Studio to update my DAW (protools). This computer runs the new M1 chips and I know there’s some compatibility issues with some companies’ products so I’m wondering if any one is running their Helix successfully on any of the M1 machines. I was originally planning on buying a stand-alone audio interface until I learned that my LT could function as one.

Okay I found the bug. I was pulling the eq block from my Favorites list. Perhaps that particular one was corrupted because if I start from scratch and dial in my eq curve there are none of the aforementioned issues. Still though- DOWN with 3.15!

Didn’t work. I backed up, restored, same result. Still can’t unassigned the eq block from foot switch 9. The only workaround is to assign the eq block to another foot switch. But that’s flawed too in the event that all the other switches are already assigned to blocks. In this case it sets it up so that the foot switch toggles between the already assigned block, and the eq block. More frustrating is that I don’t even want it assigned to ANY foot switch. i don’t know about others but I can’t wait for 3.15 to be a fuzzy memory. It’s the first truly buggy version I’ve experienced. I had another issue that Line6 couldn’t even solve.

Every time, on any patch, when I assign a graphic eq block, my LT keeps automatically assigning it to foot switch 9. When I go to the menu to unassigned it, it’s already set to “none”. So annoying. Firmware glitch?

Perfect, thank you!