Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by rd2rk

  1. Not using CommandCenter. You would need a MIDI controller that was capable of sending more than one MIDI Command at a time. For instance: CC#0 Value 7 + PC#33 + CC#69 Value 3 Would call Bank #6 Preset #33 Snapshot 4. You would then need to set up another FS on the controller to go wherever you wanted to go next. This is not a very simple thing to configure, as it requires a lot of strategery on your part. Then changing it all to accommodate the setlist and songs. And then being able to recall in the heat of battle which FS sends you where THIS week. Hitting the "ambient" FS for a blues solo would be embarrassing at best!
  2. Just verify that the keystep does MIDI over USB, not just using the DIN ports. After looking at your screenshots I'm more convinced than ever that the problem has to do with running the P90 through Helix. IDK why that should be. I use my KB same as you (NOT a keys player), and my Seiko DS-250 dates from the 1980s! As I said above, I had a similar problem at one time. I just spent a few minutes swapping all of my various MIDI connections around, IN/OUT/THRU/AROUND/OVER and DOWN trying to replicate the problem and couldn't! Whatever I did to fix the problem so long ago fixed it good! Could also be that MS improved it's MIDI handling in some update or other, it's not like the Gods of Redmond would deign to tell us mortals something like that... Now, why PT doesn't connect is another story. When I had the problem, whatever softsynth I was using would just lock up with the note playing. But that was Reaper. Did I mention how much I hate PT? Though, while I hate to defend it, when I reinstalled PTF it automatically recognized all 7 of my MIDI controllers and set them up to work with it. That's something that neither Reaper nor Ableton will do!
  3. Nobody's computer has had a serial port since the dark ages, so I assume there's nothing connected to the HOST Port. I'm also assuming there's nothing connected to the MIDI IN Port. Set the switch by the MIDI Port to MIDI. If you have a sustain pedal, connect it. The troubleshooting section of the P90 manual mentions possible problems in this area. If you don't have a sustain pedal a dummy 1/4" plug might work, worth a try. Or any momentary FS. BOSS FS pedals have a polarity switch you could try. IIRC, a sustain pedal works by delaying the MIDI NOTE OFF message (NOTE# + Value <64). I could be wrong about that. Can you see that message occurring in the MIDI Monitor? If possible, take a screenshot of your MIDI Monitor screen and attach it to your reply so I can (hopefully) see what the P90 is actually sending. Unfortunately, like many things MAC, the MIDI Monitors I've seen simplify the readout to the point of near uselessness. If there are any display options in your MIDI Monitor, make sure they're all on. If there's a HEX option turn it OFF. I don't speak HEX. I can translate it but it's a PITA. Hopefully this will give me some more info. It's possible that the P90 is transmitting so much data at such a high rate that it's overwhelming the MIDI THRU capability of the Helix. It's also possible that you've been cursed by an evil witch, but we'll cross that stream when we get there :-). It's late now, I'll look into it more tomorrow when I have the screenshot.
  4. That's the "stuck note" thing I referred to. IDK why this happens, it may be a setting in your KB. What is the exact model of your KB? The adapter you linked to is not what you need. Did you follow my Amazon link? That's what you need. Tell me about your KB first though, maybe we can get it working with Helix.
  5. If you want a smaller KB, well, far be it from me to discourage GAS! But FIRST establish that the KB that sent MIDI in the past STILL sends MIDI! That starts with a MIDI Monitor. Once you have the MIDI Monitor installed, go into CommandCenter and configure a FS to send a MIDI NOTE. That won't eliminate the THRU function as the culprit, but if there's no MIDI at the computer sending a NOTE from Helix I'd suspect a rotten Apple! If there's still no MIDI from the KB at the computer using Helix as the interface, then if you still have the MIDI Interface that you used before Helix try with that. If there's still no MIDI you've eliminated everything but the KB. Borrow something that sends MIDI and start over with the process of elimination. @datacommando - is there a special MAC MIDI Driver for Helix that he needs? I don't understand this - the cable I'm talking about is something like this: AmazonSmile: iConnectivity The First C (and USB A) Type Mac, PC, iOS, and Android Compatible MIDI Interface (mioXC) : Everything Else There's cheaper ones, but this is the brand I use (USB A version) and it's dependable for all purposes.
  6. Try installing a MIDI MONITOR on your computer to make sure that MIDI is getting from your KB thru Helix to the computer itself.
  7. That's all you need to make it happen. I hate ProTools and haven't had it on my computer for a while. I reinstalled PTFirst just to see if you'd have problems. It automatically configured itself to receive MIDI, and the default project (Electronica) with a synth bass track plays. This is using Helix as MIDI Interface set as I described. My MIDI BASE CHANNEL is set to the default of 1. RECEIVE MIDI CLOCK = MIDI SEND MIDI CLOCK = OFF Have you got your sample rates matched? Helix default is 48 but PTF set it at 44.1 so I had to change that. MIDI PC SEND controls whether or not the default MIDI PC# is sent when a preset loads. MIDI PC Receive controls whether or not Helix RECEIVES MIDI PC#s or just CC#s. Those are unrelated to the issue.
  8. Turn on MIDI THRU and MIDI over USB. Be aware that sometimes using it this way with a MIDI KB causes a - what's it called? - when the NOTE ON gets stuck? I get around this by connecting my KB via USB. You'll need a DIN to USB interface cable if your KB (like mine) is too old to have USB. Fortunately, even the Chinese cheapies work for this purpose. EDIT: I hadn't tried this in a while so I just did and it worked fine. Try it first before going the USB interface route.
  9. You can use a Return pair as a Path input, no need for a Block in the preset.
  10. Keep in mind what I said about MIDI Interfaces. While the UNO_ControlCenter editor works fine with the stock FCB chip, it may or may not work with your MIDI interface, which you still haven't specified so I can't say either way. Also and FYI, FCB/UNO usually refers to an FCB with the UNO chip. If you haven't already, you should probably sign up here: main@fcb1010.groups.io | Home There's also an UNO group there should you decide to upgrade your chip.
  11. The SEND/RETURNs are 1/4".
  12. There's no equivalent "AUX" Inputs (the aux input is mono for a second instrument). I'm not familiar with the Motu AVB, but a quick look at the manual shows SPDIF Out, and the Rack has SPDIF IN, so that can be used as a Path Input. For other purposes you'd need to use a Stereo Return Block and a pair of returns (2 of the 4 available) which can be placed anywhere in the signal path or used as a Path Input.
  13. No. Distortion?? Attach the actual preset.
  14. rd2rk

    wireless headphones

    16ms. Not bad at all!
  15. You didn't specify which editor or MIDI Interface you're using.
  16. Catalyst Edit merely loads what's on the Catalyst and allows you to configure it in a GUI. What you're controlling with MIDI is the Catalyst itself. You've listed a whole lot of stuff you might want to control. You'll need to decide exactly how you want to use your FCB. With the stock chip you can send 5 PC messages, 1 or 2 CC messages (depending upon exactly what type - only 1 if toggling) and 1 Note. They can all be sent on different MIDI Channels, to control different HW/SW. Complex and detailed strategy is required when using more than one HW/SW. To control Catalyst you'll need at least 2 FCB Banks. Here's what a very basic configuration might look like. FCB Bank 00 FS5-10 select: FS5 - Cat Bank1 ChA FS6 - Cat Bank1 ChB FS7 - Cat Bank2 ChA FS8 - Cat Bank2 ChB FS9 - Cat Bank3 ChA FS10 - Cat Bank3 ChB FCB Bank 01 selects Catalyst Banks 4-6 A/B In both FCB Banks: FS1 Toggles GATE FS2 Toggles BOOST FS3 Toggles EFFECT FS4 Toggles REVERB Exp A = Volume Exp B = Expression Again, this is a very basic configuration, there's lots more you can do with MIDI and Catalyst but, as mentioned, you have some strategerizing to do!
  17. More likely an error in the documentation. It happens.
  18. rd2rk

    Digital noise

    I missed that. OTOH, it's a really nice sounding preset, if he tells us where he got it I might try some myself, or recommend the actual creator to the next newbie who asks "What are the best commercial presets?". Help him atone for his sin... :-)
  19. I've been using the FCB1010 for over 10 years to control all sorts of things. I control my Catalyst with MIDI from my Helix but could easily configure the FCB to do it. I can help you with this, but first a few questions: Does your FCB have the stock chip or something else? If something else then what? How much experience do you have with MIDI? IOW - do you know the types and functions of the various (basic) MIDI messages (PC and CC)? What editor are you using? I won't even try to help you if you're not using an editor. Not like it can't be done, I've just seen that movie too many times to want to see it again. The best editor is the UNO_ControlCenter which costs <>$25 here: FCB/UnO Control Center for the Behringer FCB1010 You can try using one of the free editors, but unless you value your time VERY cheaply, get the UNO_ControlCenter. Yes, it will work with the stock chip. However, not all MIDI Interfaces will work with an editor. What MIDI Interface are you using? Awaiting your reply...
  20. I took a minute to look into this, as I've never tried to use my Powercab like that. I have the PC212+ which, AFAIK, in your situation works the same way as having two PC112+. You can have different IRs on each speaker in FRFR MODE or USER IR MODE. You can have different emulations on each speaker in SPEAKER MODE. But the MODE itself applies to both speakers.
  21. Why would you want to run a PREamp into a SIMULATED speaker without a power amp? How would you then AMPLIFY that into a REAL WORLD speaker so you could hear it? Or would you be doing this to send to a DAW for recording, which still leaves the question of WHY would you not want at least a simulated power amp in the signal chain? The purpose of a reactive load box is to allow you to capture a REAL WORLD power amp into a line level signal for recording and/or attenuate the REAL WORLD power amp for low level playing. Color me VERY confused...
  22. Are your speakers PC112+ or PC212+? IIRC, your problem is a known issue on the PC212+, but not on the PC112+. In any case, there's problems with L6 Link that L6 has so far refused to deal with. Or even acknowledge. Contact support and see for yourself. Good Luck! As far as many of us who have been active about this on the forums can tell, the Powercab series is abandonware.
  • Create New...