Please ensure Javascript is enabled for purposes of website accessibility Jump to content

PierM

Members
  • Posts

    1,689
  • Joined

  • Last visited

  • Days Won

    83

Everything posted by PierM

  1. This is a bug, not sure if in the Helix or in the PCabs. I have the same setup, and I get this when Helix power up BEFORE the two PCs completed their own boot, or when the last Powercab in the daisy chain, turns ON before the rest of the rig. Anyway, try a different boot sequence like (starting with everything OFF); 1) Powerup the Powercab A (the one receiving link from Helix) - Wait the boot to complete 2) Powerup the Powercab B (the one receiving link from Powercab A) - Wait the boot to complete 3) Powerup the Helix If doesnt work, try 2), 1), 3). If doesnt work try 3) 1), 2).... Point is, test different sequences, 'til you find the one which works for you. (sounds silly, but Ive read people solving with a different sequence than mine, but that wouldnt work for me....) Important thing is to just wait for every device to complete its own boot, before powering up the others....
  2. Never had a Pageflip or OnSong on my iPad, so not sure how this is working. From the sound of it, I'm assuming it's a macro available in the Pageflip firmware/software. You can't do these kind of macros with the Helix, you can just either send a momentary or a toggle CC, but the action to scroll through songs while pressing, sounds like a macro to me, something that waits a second or two, then start sending continuous commands to the OnSong application, until you lift. Again, just assuming here... no idea how these things are communicating, neither I know what kind of MIDI messages OnSong can manage. As soon as you have all the toys at home, you can start experimenting on your own. ;)
  3. Ok nevermind. I've found that disabling the hardware compatibility option, does allow me to assign same CCs as the hardware. Which is IMHO a nonsense, as they were already assigned and stored in the preset, exactly to respect the Hardware compatibility mode. Bah?! Anyway, at least this way seems working, even if I have to reassign CCs to blocks, to be exactly the same as they were in the preset, LOL. :) See in this pic. The original assignment are those with dimmed colors, and referring to hardware footswitches. Those can't be used... But then, disabling compatibility mode, does allow me to reassign those same CCs as the hardware, as in the pic. Looks like a bug to me, or a bad design.
  4. Hi guys, as the title says; is there a way to just use the same MIDI mapping as the Helix Control and Helix Stomp/Footswitch CCs? I mean, I do have my Rack in the studio, and Native at home. Is there a way to have my Native just using the hardware CCs, so that I don't have to use extra mapping? I have this option in other devices. For example, my Obehreim Echoplex hardware and its plugin counterpart (from the same engineer), they both use exactly the same stock reserved MIDI mapping, so the virtual version can just reuse same controller presets as the hardware, without have to remap MIDI controllers. I tried to do that, but seems only working for snapshots (they do act correctly, just using same CCs and values, as the hardware), while I can't find a way to do the same with Stomps/FS. They just seems ignoring those CCs that I've programmed in my controllers, and that are those used by the Helix hardware. What's the pros of this? Well, that I can create a virtual setup on my DAW (Ableton Live), that does (almost) perfectly mirror the hardware counterpart, without have to create dedicated mapping on my controllers, for the plugins. Any solution, thoughts?
  5. If you are sending from Helix to the iPad, through the H9, that's a THRU not an OUT. The THRU mode is often filtered (especially on devices with a single THRU/OUT), so you can only hope that H9 has a clean and reliable THRU, otherwise it could be glitchy. Said that, if you are just sending couple of CC messages here and there, it should be fine.
  6. Depends on the iPod. The iPod touch are indeed HOSTs, running iOS, and they can use a Camera Kit. They are like iPhones without Phone...:) If it's an old iPod classic, then no.
  7. Voted. I think the core point here is if the Global EQ which is already available, with its own reserved DSP power and logic, could be hijacked to AES/EBU at the same cost, or if would need extra logic to be asked to the DSP...in which case would break presets. If the first, we have a chance to see it implemented in the future....if the second, I wouldnt hold my breath. Said that; without that option, I cant really see the advantage to use the Link with Powercabs (that are boomy by default, even with the low cut). Not advantageous enough to justify the absence of Global EQ (which is fundamental for gigging people).
  8. Buddy, you are killing me! That was my first suggestion in this thread....:D.
  9. Man, just chill, you risk a stroke lol! They could do it, just not a priority.
  10. HOST needs power and there are not other way to feed it without a DC IN. ...and No, MIDI cant feed VA to an HOST, neither the Helix. And btw, you have already an HOST that can run "without" DC IN....that iPad with its battery. :P
  11. Power is going nowhere, even if you had 100 MIDI devices in a daisy chain. It's current draw that matters, and those BT trasmitters are usually requiring small currents. Should be fine, but dont ask me 100% warranty, as I never tested this specific solution. On paper, it should work.
  12. If there is something, is under the Legacy section of FILTERS.
  13. Clipping? Depends; if there is a pad activated, or a low track volume, or negative gain (attenuation) etc... It could clip, and probably will sound awfully noisy....but that's not gonna explode anything. Nothing bad happen. Just a very low level, since a MIC signal is expecting a preamp which won't be found in a device INput set at line level.
  14. Rack doesnt have Test Mode.
  15. Well, Helix has already a full MIDI DIN loop available (IN/OUT-THRU), so in theory a internal Host would have been a bit overkill for the average market of the Helix. Then, if as the OP you run out of MIDI ports, and you want to go wireless through Helix USB, you could buy a little MIDI USB HOST (a little computer that does the job of managing MIDI IN/OUT data flow), and plug your BT Wireless MIDI there. Like that one in the pic i posted. Helix USB cable goes into that box USB A Host, and there you go....you have 1 extra MIDI Loop available to go wireless. That's pretty much my setup, as my Helix MIDI DIN ports are connected to a set of loopers, and USB goes into iPad (my host), to control the Helix with hands, and propagate the Helix midi to other wireless controllers (like an old BCR2000 with a quicco, that I use to changes on the fly few Helix blocks params)... OP has an iPad, like me, so he didnt really need another HOST (hence my original suggestion)...
  16. I dont use the Link with my two PC+ for that same reason (I could use a EQ block but DSP are full for my preset), other than because the daisy chain has few bugs that make the entire thing pretty erratic. Indeed, let's hope for a patch that cover both the problems. :)
  17. mine does 100% the same as your, still works fine.
  18. There is no contradiction, if you understand what have been said.... :) Just watch that video. Hope this finally make things clear.....lol
  19. No worries. Once you get the concept, it's easy to follow the logic; USB A = HOST USB B, USB B micro = USB Peripheral USB MIDI Comunication = USB Peripheral <---------------------------> HOST = USB B <-----------------CABLE--------------------> USB A NO USB Comunication (WRONG CONNECTION) = USB Peripheral <--------------------------->USB Peripheral = USB B <---------------CABLE-------------->USB B Helix = USB Peripheral = USB B H9 = USB Peripheral = USB B Micro CME WIDI USB = USB Peripheral = USB A direct (Since doesn't need a cable and goes directly connected to HOST) iPad = HOST (USB A, through the Camera Kit adapter) Laptop = HOST (USB A) PC = HOST (USB A)
  20. CME WIDI USB is a USB device, and needs an HOST (You plug the WIDI to a laptop [HOST], you connecto to a BT keyboard [USB Device]...and stuff like that). Helix is NOT an host, is another device. So, as well as with the H9, connecting helix usb to CME WIDI USB, is like connecting a Printer to a Mouse....You keep thinking an USB port design, as just a matter of design. It is NOT. The design changes, as the purpose is different. Just read the info I linked, it's all explained. ;) ....At some point, since you seems lacking MIDI and USB basics, you have either to believe users here who knows that stuff, or experiment yourself your own route, at your own risk. At this point, you've been suggested with many options available, but I see you keep searching for something different, so yeah, feel free to experiment buying random stuff and connecting random adapters to random ports. ;)
  21. It's not gonna work. USB Midi (as any other USB protocol), needs a device to Host communication. Helix and H9 are devices, Host is a computer, or a tablet, an ipad, etc. This is why you have different USB ports there. When you inter-connect two USB peripherals (helix and H9) via USB (forcing the connection through adapters), you have two peripherals with nothing to say each other, since it's the HOST that manages and translates data traffic between USB peripherals. Connecting Helix with H9 is more or less like connecting a Printer to a Mouse. https://www.midi.org/midi-articles/basic-of-usb EDIT: Also, in general, never force a direct link between USB devices, unless you don't know what you are doing. Not the case here, as USB B doesn't transport voltage, but USB A does, as well as many other protocols and ports. So, my advice, if you don't know how things are working, never try to force a connection between two devices with different ports, as happens that those ports are different for a good reason, and you may fry something just messing around... ;)
  22. MIDI Out is mandatory yes, as it's giving the power to the transmitter. So, if you dont need to send anything back to Helix, you can just plug the Helix out. For the H9, if you need to control it through the Helix MIDI commands, down to H9 MIDI IN , you need both IN and OUT connected (on the H9). Now I need to go. :)
  23. Loop I mean the BT Wireless adapter going into MIDI IN and OUT in the back of the Helix and H9... :)
  24. No, you dont need any Box. If you use two BT MIDI set, and an ipad; Helix has MIDI loop closed with one Yamaha BT-01 iPad will receive and send (if needed) BT MIDI From Helix, via BT-01 (you can use AUM to create the MIDI Route) iPad will advertise MIDI Over BT wireless and will become a Central. H9 has MIDI loop closed with a second BT-01 and will communicate with iPad Central AUM will put in communication iPad (and apps using MIDI) with Helix, and Helix with H9. Remember these BT devices, are using the serial power (also called Power Over MIDI), which can be 3.3V or 5V. These splitters, merger, etc, are typically asking 5V, and Im not sure Helix is producing that power for them. This means you are not sure those boxes will transport the voltage needed to powerup the BT Wireless.
×
×
  • Create New...