Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About shemeshg

  • Rank
    Just Startin'

Profile Information

  • Registered Products

Recent Profile Visitors

184 profile views
  1. attached Open Stage Control, implementing the - The “Unofficial” Helix MIDI Guide v3.0 I still don't understand why Line6 developers made for example midi of FS1 is for stamp mode only, (unlike using the footswitch on the unit itself where it can be used to select preset etc...) it is better the nothing though remember to install dependencies for python midi and to run with correct parameters like: ./open-stage-control.app/Contents/MacOS/open-stage-control -m list "HELIX:2,2" I wish helix developer would 1. sending midi foot switch would be like as pressing the footswitch on the unit (select stamp, switch preset...) and not just select stamp. 2. consider implementing OSC(Open sound control) for the Helix Editor Software (The helix software would act as a OSC server that can be controlled from a tablet) HELIX.json
  2. confirmed usb id: USB_ID(0x0E41, 0x424a): /* Line6 Helix LT - firmware >= 2.8 */ that maximum kernel available for me is AMD 64, for now......
  3. Twin harmony is cool effect, however I’d like to use it is pitch correction for my Theremin The Helix seems to do great in identifying and correcting pitch, in the “Twin harmony”. However 1, No chromatic Scale exists. 2. I wish we had parameter for how fast should auto tune engage (for Theremin vibrato at beginning of note, for Fretless base to make transition from one note to another more smooth). If at Line6 you think, “we like it that way we dont want to change it. Maybe you could add auto tune effect. Personally, I think there is no need for another effect called "autotune", 1. and 2. would do the same functionality and in much more powerfull way….
  4. Helix can send CC, turning CC to note is simple using 1. your daw (Logic pro transformation object) 2. VCV rack, just connect CC trigger, to note trigger module. 3. Using 3 lines of code in Midi Javascript 4. You dont want to "play with your foot switches", you do want to trigger event/sequences/patches with it... Lets try simple home assignment . VCV rack will control Helix Gain volume where amplitude of change will decrease over time. 1. Free 40min of your time. 2. In VCV rack add LFO, and ADSR 3. Connect LFO to ADSR to control amplitude over time. 4. Add CC trigger (You can also have VCV identify a trigger as any sounde larger then 3V) 5. connect cc trigger to adsr 6. Helix configure footswitch A1 to trigger CC channel X 7. Helix configure Gain affect to receve changes on CC channel Y 8. test that VCV accepted your trigger successfully. 9.Verify that the ptach actually works. This is a simple task with no keyboard. - In the synth world we dont need to trigger specific notes, we trigger sequence events. ** This is a Virtual Analog task, their might be as well FM synthesis home assignment, Live looping home assignment or AbeltonLive10 Loops assignment. however analog monophonic synth is the best way to start, a. You can simplify this task even more by jest sending LFO from VCV Rack to Helix, this is 7Min assignment but it would be less challenging . b. It is always best to have Helix or External Synth produce the sound and Midi just play changes with it.
  5. Helix got 8ins 8 out, in terms of logical usb ports, so it is might benefit for example to get your software synth in to Usb3/4 for effects while guitar goes in to guitar in for example. This is also good for recording, for some reason sending sound from two different programs to same output cause glitches. Artistically, , I like for myself recording classical string quartet on monophonic analog synth, or guitar. For live shows probably you are looking for building a simple VCV Rack patch, and maybe the patch would control external analog synth. and all trigged by guitar VCV RACK 1.0 is free and can also control pitch wheel, so maybe LFO can also control the external synth pitch wheel. also a loop playback VCV rack module can be used to trigger recording/playing every N bars All of this would be triggered by any note sent from the guitar to VCV. or Helix internal clock thew these things are really nice, I find it more interesting investing my time on piano classical music , and playing Piano pieces on guitar (Bach for example). then gong experimental.
  6. To wrap-up the discussion. now that we both on the same page managed to recreate the issue: 1. This bug does not occurs on any other interface (Synths, or soundcards I have, or generic midi interface). only Helix has this bug 2. It is easy to solve by code (Just do not re-echo requests sent to all-ins through Helix,), easy to reproduce, easy to debug. it is just a matter of programmer forgot to Own the all-inst event before resending it, so it will not re-re-re-sent 3. Logic Pro Unlike Live 10, do not have independent midi engine per track. Logic has one "Midi environment" window for all project and tracks. => By default Helix Out Din will not work on Logic Pro, (unless creating something like /dev/null object from the Helix input). 3.1 This is definitely not standard request from a user to mess with "Midi Environment" because Helix Re-eco request sent to "all-ins" I do however agree that in live10 it is almost not issue at all. Anyway Thanks for response
  7. Hi Your test WAS OK, you were just one click away from the bug. just set to "ALL INS" I've repeated your last experiment and in did it was ok, However to trigger the loopback bug you would have to switch from USB2-0-MIdi to "all ins" Here I've repeated your experiment where Focustrite ss my simple Midi using external Roland old usb keyboard . (No more Casio, no more USB directly connected) Here where it is ok: Here you should see it loopback: Notice that after loopback occurs, no notes will be sent to external DIN and the Helix needs to be reboot It he picture you see as constant lights but these lights in the Live10 gone wild and Helix would require restart to play any midi note. Your test WAS OK, you were just one click away from the bug. just set to "ALL INS" BTW - Really deeply thank you
  8. Hi Sorry, for the mis understanding, 1. indeed it is required USB keyboard I've tried using webMidi test page and it was not reproducible (https://jazz-soft.net/download/web-midi/web-midi-test.html) 2. no need to connect anything to the Helix MIDI IN DIN, only MIDI OUT DIN when set TRACK MONITOR to "OFF" nothing is actually sent when I play on the keyboard so I have to set it is AUTO I guess, It is good though to set it to OFF when using module/keyboard that don't have "ECHO OFF" mode, to avoid playing back the same note. (like a casio digital piano, or when connecting the external sound module back to the Helix midi in) But here the problem is infinit looping and not just the same note itself Here compared tested with Focusrite Soundcard and all ok
  9. Hi Here instruction for reproducing the issue in Live 10. 1. Start new project, press tab to switch "Project view" from "loop view" 2. in the "1 Midi" set the record on [red] 3. in the "1 Midi" set dropbox from up to down as follows: - "CASIO USB" or any other external keyboard you have - Keep default of "All Channels" [it is the input channel, of the keyboard so it is not matter' - "auto" button on [yellow] - HELIX [This is the output port] - Ch 1 [this the the channel of you hardware synth 4. Press any key like "Do" *** Here everything should work correctly 5. Change the first dropdown to - "All Ins" 6. Press any key like "Do" You will see that - Helix is keep re-sending the Do(C4) over end over again - lights on the Live10 always on. indicating loop. - lights in the hardware synth indicate loop. 7 test that with Focusrite soundcard or any other usb midi device and see it is only occurs with Helix. The Loopback you've mentioned 'track monitor' is wave partial cancellation, and not actually recursive midi data loopback that overload the Helix
  10. Actually, I see that the MIDI OUT DIN is ok. The problem was that the loopback, bug caused Helix system overload. So the *** OUT DIN is ok. my mistake*** The loopback bug, will not impact Reaper, since you specify your input keyboard as the midi input port. However in Logic Pro, we have "ALL" (all devices) as input by default, and since then The loopback bug: - note sent out of MIDI DIN -> Sent also USB MIDI IN it caused loopback, it is possible to walk-around by ignoring midi in from Helix. at the logic midi environment
  11. 1. in logic pro or any other DAW, open Midi Channel 2. in the midi channel select 'HELIX' as port 3. connect external sound module to the MIDI OUT DIN 4. Send some notes using keyboard or create a region with some notes Expected: Sound is produced on external module However: No MIDI data sent from the Helix. [ there is another issue with MIDI IN DIN, of keyboard connected to MIDI IN DIN, and playing any note would produce Loopback by the USB-MIDI-IN, however according to Line6 support, this fix is more of a feature request, so lets leave that aside.. ]
  12. Hi I have Helix, with sound module [Roland D-100] and some times Neutron, connected to the Midi out. I'd like to be able to play the Roland using the MIDI DIN out, without causing loopback. rd2rk - I thought that too, but surprisingly, the MIDI THRU also Re-Play whatever comes into Helix through USB, hence the bug I've tested that on other 2 sound cards I have (Focusrite), and they do not have this bug. It is not problem in logic, I've written simple plugin in Midi-js and found it does this eco-ing thing too.
  13. and with through: on causes Loopback. 1. set general settings to Midi over usb: on Midi throu: on These two actions are essential to send midi through the midi out jack(MIDI DIN) open Logic pro. 1. Right click display and set to custom 2. create external midi track, set output to Helix and send any note like C4(DO in the do re mi...) 3. No need to connect anything to the midi in DIN to produce the error. Expected Error: This will cause infinite loop where the C4 is sent through the DIN, AND through the USB. this cause feed back from the usb again... Expected Test Comparison: Connect any other sound card like Focusrite, and see it has no problem. Note: It is possible to walk-around and remove the incoming midi connection through the usb, using the "Environment Window" but it does not make any sense.
  14. found that it has in the preset file "join" : { "@model" : "HD2_AppDSPFlowJoin", "B Pan" : 0.85000002384185791, "B Level" : 0, "A Level" : 0, "A Pan" : 0.14999997615814209, "@position" : 8, "Level" : 0, "@enabled" : true, "B Polarity" : false }, Since it was a preset for me, i never looked closely into the join, setting the panning at the join solved it
  15. Do for example this simple test, 1. set preset to "factory 2 - 01A Boutique", -> this is a Dry/Wet most simple straight forward example 2. on your DAW, set your monitoring to Pre-Fader to see level indication Unexpected Result ->. when Volume pedal on Wet Position (100%) Left right are balanced when Volume pedal on Dry Position (0%) [no sound routed through the Delay] Left is 5db more then the right.
  • Create New...