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

d0stenning

Members
  • Posts

    364
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by d0stenning

  1. exactly - which ... is why i proposed this: "Have a special block - linked to a foot-switch which - when turned on - makes all 8 ( or more ) foot-switches temporarily become MIDI controllers. In this mode each switch would have dedicated scribble-strip names i could customise.: http://line6.ideasca...al/802355-23508 This would be much in the similar fashion to how we currently enter or exit the LOOPER mode in the Helix This might be used for example to control external loopers like Loopy HD on the iPad, or launch Loops or scenes in Ableton over MIDI via mapping - or some kind of sequencer control during live mode. A single pedal would have to be dedicated to EXIT - to exit back to normal mode." Another thought I just had is that instead of limiting this special block to **just** assigning MIDI control functions to all 8 pedals in this mode. instead it could be left open. So if we want to use 7 pedals in this mode for pure MIDI control - but have the 8th pedal assigned to a BOOST or some other effect then we still can. This way we could in fact have several blocks programmed - inside a single preset - which we can switch into and out of - as we wish. So maybe one block has pedals mainly for LOOPY HD, but another gets used to control Ableton scenes, loops etc - whatever. Or a block could be set up so that all we have are 7 or 8 "scenes" - one per pedal. !!!
  2. Soundog above mentioned the need for a USB host in order to connect a Nanokontrol to the HELIX ** without** needing a computer in the chain. I've just discovered theres this thing called USB On The GO - and there are devices for it. In order to plug the NanoKontrol into HELIX without a USB host computer This Lindy OTG hub has a socket for external powering so maybe this is it - and might avoid the need to buy one of those expensive iConnectMIDI boxes ? http://www.lindy.co.uk/usb-firewire-c4/4-port-usb-2-0-otg-hub-p8430 from the blurb: 4 Port USB 2.0 OTG hub (4 x USB Type A female) with USB Micro-B connector Integrated 13cm cable for connecting Smartphones/Tablets USB 2.0 high speed (480Mbit/sec), backwards compatible with full speed (12Mbit/sec) and low speed (1.5Mbit/sec) Bus powered with socket for optional 5V DC 2.6A power supply 2 year warranty "The LINDY 4 Port USB OTG Hub allows you to connect four peripheral devices to your tablet or smartphone without the need for a PC. It can connect external Flash Drives, Card Readers, Keyboards & Mice directly to your handset. Supporting data transfer speeds up to 480Mbit/sec, it is fully compatible with USB 1.1, USB 2.0 and USB On-The-Go (OTG). Small and light it is ideal for use in BYOD (Bring Your Own Device) offices, mobile workers or simply adding extra functionality to your OTG device. ******An optional power supply also means you can power more demanding devices such as Webcams and bus powered external drives**** "
  3. And in fact i'd rather see a feature added that allows me to **hide** those amp and effect models I'm unlikely to ever use in creating new patches. I really find these days that limiting one's choices not only helps avoid the sheer hassle of navigating thru huge lists but also helps creativity.
  4. Yes - for those willing to use a laptop on stage Ableton offers ***SO*** much more. I've done a fair bit of investigating of some of the Max4Live Looping devices which extend the functionality of the built in Live Looper - specially when wanting to loop on several tracks and switch between track easily. I'll maybe do more and try mapping HELIX pedals to it. Last time i tried it there were those HELIX USB audio issues - but we're past that now so need to reinvestigate this all. The other route of course other than pedals or Ableton - is Loopy HD
  5. I cannot conceive of a being greater than PeterHamm. Therefore PeterHamm is Eric Clapton. ( the OwnHammer-ological argument )
  6. Yup - well lets settle for 120 seconds more ;)
  7. fair point - neither did I - but as they put in a looper - at the minimum I just wish it had more looping time. For me the built-in looper just doesn't have enough time for me to really use it in the manner i'd like. Merely raising it to 3 minutes would have been so cool - since thats the total time of a typical complete track- so ups the looping form being just a phrase or few - to a complete song. for the price of a little more memory - or a HDXC slot.
  8. Also - given the popularity of the iOS looping app Loopy HD - just some enhancements to allow more MIDI control flexibility to control devices like Loopy HD would be greatly welcome methinks http://line6.ideascale.com/a/dtd/MIDI-CONTROLLER-Block-where-all-footswitches-become-MIDI-pedal/802355-23508 "Have a special block - linked to a foot-switch which - when turned on - makes all 8 ( or more ) foot-switches temporarily become MIDI controllers. In this mode each switch would have dedicated scribble-strip names i could customise. I realise there is some existing MIDI controller functionality for foot-switches already. But I need the scribble strips AND the foots-switches to ONLY act as MIDI controllers in this mode - while being able to return to normal control of effects etc by exiting this. This would be much in the similar fashion to how we currently enter or exit the LOOPER mode in the Helix This might be used for example to control external loopers like Loopy HD on the iPad, or launch Loops or scenes in Ableton over MIDI via mapping - or some kind of sequencer control during live mode. A single pedal would have to be dedicated to EXIT - to exit back to normal mode." Another thought I just had is that instead of limiting this special block to **just** assigning MIDI control functions to all 8 pedals in this mode. instead it could be left open. So if we want to use 7 pedals in this mode for pure MIDI control - but have the 8th pedal assigned to a BOOST or some other effect then we still can. This way we could in fact have several blocks programmed - inside a single preset - which we can switch into and out of - as we wish. So maybe one block has pedals mainly for LOOPY HD, but another gets used to control Ableton scenes, loops etc - whatever. Or a block could be set up so that all we have are 7 or 8 "scenes" - one per pedal. !!!
  9. I think people would play more for a "DeLuxe" version of HELIX that had a XDHC Card slot and more memory and features for proper multi-track looping. In the meantime I submitted this proposal some while back: http://line6.ideascale.com/a/dtd/Extend-Looper-capability-with-add-on-unit-w-SDHC-memory-card/802351-23508 "Manufacture an add-on device - say a second Swell pedal - or a foot-controller-extension WITH a built-in slot for an SDHC card on the side and a USB socket to be connected to the main Helix ( via USB of course ). If necessary some kind of USB-Splitter thing could be built-in so that while this SDHC extender pedal is connected to the main Helix the Helix can still connect over USB to any other device - say a computer or iPad etc.. for audio etc. This "extender" box could ALSO finally incorporate WI-FI built-in in order to finally allow the Helix to be controlled. programmed and managed over Wi-Fi - by for example an iPad. The Helix Looper software could then be modified significantly to support very advanced types of Looper functionality - making use of the storage of the SDHC card - accessed over the USB connection."
  10. Well in my case - i literally don't have **any** other guitar gear apart from my JTV and my HELIX and my PA..... so ....... ain't I lucky ! :) But I don't plan to buy any outboards either. I'm a "keep it minimal" and "Total Recall" kind of guy - so a HELIX and Ableton suits me perfectly :) But while I have your kind ear - two very simple changes to the HELIX FW that would make a LOT of difference methinks is this: A ) add *CUT block* option in the HELIX so we can easily move any helix block from Path A to Path B. This need crops up often when I have run out of space or DSP in path A and want to stick move one or more blocks to path B. B ) a **CLEAR PRESET** option. Its a drag to have to copy and paste an empty block just when we don't want an existing preset in a current slot. Two obvious and simple to implement changes - that i'm sure are already in IdeaScale :) Often its the most simple feature changes that don't actually require much developer effort that are the most appreciated and useful by/for the end-user. I say this as a developer ( C++/JUCE ) myself :)
  11. There are so many cool and useful improvements that can be made to how we use the HELIX overall - regardless of amp model - that are in the IdeaScale suggestions database which would improve things for every user - so i'd rather they not just spend their resources on endless exotic amp models. Except maybe a pure acoustic guitar amp, and an amp for jazz arch top guitar (Polytone?) since those are in a unique category. So i'd rather see them work on and bring out new FW for things that improve workflow and enhance usefulness ( MIDI controller effect block ) - something that expands on the ways in which this box can be used - and usability in a live gig situation (scenes) as well as make the process of patch creation easier (eg. when wanting to borrow bits from several existing patches into a new patch). Also something that makes it easier to find the right patch once one has hundreds of them. Personally - all those "ooh if only they supported [place exotic boutique amp name here] i'd be in seventh heaven" suggestions can wait. How many models do we really need anyway ? Arguably a better solution for these amp model requests would be for L6 to bring out a graphic interface based "amp designer-editor" to allow users to come up with their own circuits would allow 3rd parties and enthusiasts to do this instead of L6. Or for user-created effects blocks, something like Native Instruments does with their Reaktor DAW plugin ( which allows you to design a DSP circuit/algorithm graphically and then literally spits out DSP code in C or what is known as "p-code" and compiles it into high performance CPU efficient native DSP code ) - if they have access to the circuits - thus saving L6 the effort of all this. Just sayin' OTOH I *do* see the argument for including a bigger range of - and more high quality - effects in there. After all - this beast is ideally something that could replace all one's beloved pedals and the wiring mess and unreliability that goes with them.
  12. very nice indeed. And more so for having little in the way of reverb- Can you possibly share the presets on CustomTone ?
  13. Auto volume normalisation via global reference patch & scenes Auto volume normalisation via global reference patch using (upcoming feature?) scenes: In principle it ought to be possible for some sort of volume normalisation feature be built into the HELIX firmware so that for example - give us via firmware the means to set up a global REFERENCE patch - with three or four "Scenes". one scene the user specifies as "clean", another for boost, one for "lead" or OD - maybe more. The user then ensures that the volume levels for each of these "reference scenes" within this "reference patch" are the volume levels they desire for their typical needs ( in a mix, gigging etc ) Then whenever we create a new patch - we also set up scenes for the new patch - and the HELX provides a means for us to tell the HELIX that scene 1 is our "clean" , scene 2 is our "boost" scene 3 our "lead", scene 4 our "rhythm etc . And then with a single button click the HELIX normalises the levels and output for this new patch to match my initial "reference". So that for the new patch I am now ensured that for the common usages - clean, OD, boost rhythm etc - my new patch can be interchanged with any other without any need to tweak final output levels etc. http://line6.ideasca...es/823342-23508
  14. Thinking about this made me come up with ( big groan from everyone... ) yet another feature request: http://line6.ideascale.com/a/dtd/Auto-volume-normalisation-via-global-reference-patch-scenes/823342-23508 Auto volume normalisation via global reference patch & scenes Auto volume normalisation via global reference patch using (upcoming feature?) scenes: In principle it ought to be possible for some sort of volume normalisation feature be built into the HELIX firmware so that for example - give us via firmware the means to set up a global REFERENCE patch - with three or four "Scenes". one scene the user specifies as "clean", another for boost, one for "lead" or OD - maybe more. The user then ensures that the volume levels for each of these "reference scenes" within this "reference patch" are the volume levels they desire for their typical needs ( in a mix, gigging etc ) Then whenever we create a new patch - we also set up scenes for the new patch - and the HELX provides a means for us to tell the HELIX that scene 1 is our "clean" , scene 2 is our "boost" scene 3 our "lead", scene 4 our "rhythm etc . And then with a single button click the HELIX normalises the levels and output for this new patch to match my initial "reference". So that for the new patch I am now ensured that for the common usages - clean, OD, boost rhythm etc - my new patch can be interchanged with any other without any need to tweak final output levels etc. http://line6.ideascale.com/a/dtd/Auto-volume-normalisation-via-global-reference-patch-scenes/823342-23508
  15. A thought regarding CustomTone patches: Last night I enjoyed just trying out and playing with my latest batch of CustomTone downloads. ( jamming to Soon and Waters Of March if you must know ) But one problem seems common - they all come in at different volume output levels - so i find myself reaching for Channel Volume a lot. So ... is it time to have maybe a "reference" patch in there - to which anyone considering posting their new HELIX patch can compare how their patch sounds volume level wise ? Maybe this "REFERENCE" patch can have three "Reference" volumes - for "Clean" when boost and "OD" are off, just "OD" is on and just "boost" is on... So that we can audition and use patches easily - and know that the basic typical options will produce the same levels of output ? Just an idea - maybe L6 could come up with this patch and make it a "sticky" on the forum ? I principle it ought to be possible for some sort of normalisation feature be built into the HELIX too. So that for example - we set up a global reference patch - with three "Scenes" * L6 **will** eventually implement this of course methinks ) one scene for "clean" one for boost, one for "lead" or OD - maybe more. And then whenever we set up scenes for a new patch - the HELX FW provides a means of telling the HELIX that scene 1 is our "clean" , scene 2 is our "boost" scene 3 our "lead", scene 4 our "rhythm. And then with a single button click the HELIX normalises the levels and output for this new patch to match my initial "reference".
  16. yes i've been using the /13 as a clean thing with wet reverbs. nice.
  17. HELIX Editor crash in v 1.12 I was - i think - making changes in one patch - then double clicked on a different patch in the same setlist and the app crashed. It **is** possible that i might have saved the patch being edited before double clicking on another but i forget. In any case here is the OSX Crash log in an enclosed file HELIX Editor crashlog.rtf
  18. HELIX Editor 1.12 - using delete key to delete a block A small thing: I don't know where to submit bug-reports or enhancement requests ( this none os somewhere between ) but among the new set of keyboard shortcuts I noticed that the programmer has assigned the DELETE key on Macs, NOT the BACKSPACE key to delete blocks. On MacBooks like mine - there is no DELETE key -and yes i know that **often** in an app the BACKSPACE key performs the same function as the DELETE key- but in HELIX Editor 1.12 this is not the case. For the time being though - for any macbook users out there who don't have a DELETE key, simply press "fn" and BACKSPACE and you will able to delete the block you have highlighted. ( there is also a right-click contextual menu you can use ) To thee HELIX Editor programmers though- please amend the editor so that we can use BACKSPACE **or** DELETE key to delete blocks
  19. As a seasoned ( jaded ) programmer ... I fully concur. Undo/Redo is what we call in the trade ... "non-trivial" to implement.
  20. In the editor I could live with just the ability to copy several highlighted blocks and paste into another patch I suppose. Or maybe just select an entire single "chain-line"and copy-paste that. <fwiw, I bet that copying blocks from one patch to another will be way easier on the unit than the editor... but then there's that "oh my aching back" issue...> YUP.... . a damn shame here - as its mostly so easy and instant to do stuff on the HELIX itself... apart from that lower back pain........ :(
  21. http://line6.ideascale.com/a/dtd/HELIX-Editor-View-TWO-presets-at-same-time/820657-23508?submitted=1 Christian Arnolds excellent "Loopy HD Control" CustomTone and videos is a great idea. But it now begs for a new feature in the HELIX Editor: today I wanted to use this for another preset I made. So a new ideaScale is called for: Currently I would have to make a copy of the preset "Loopy HD Control" and go in manually and just set it up from scratch block-by-block to match the parts in my own original patch I want. It would be better if in the HELIX Editor I could see AT ONCE BOTH my preferred preset - with the tones how i want it- AND the new "TARGET" preset - and then simply highlight the blocks I want then COPY AND PASTE this to the new preset containing the MIDI control pedal assignments. For this I need to be able to view the details for TWO presets AT ONCE - one being the "SOURCE" preset (read-only) and the other being the TARGET - with only the TARGET being editable, paste-able etc so one can copy anything from the SOURCE into the TARGET patch. This would save a lot of time. It would also be very useful in any situation where one wants to combine parts from two different patches into a new one.
  22. http://line6.ideascale.com/a/dtd/HELIX-Editor-View-TWO-presets-at-same-time/820657-23508?submitted=1 Christian Arnolds excellent "Loopy HD Control" CustomTone and videos is a great idea. But it now begs for a new feature in the HELIX Editor: today I wanted to use this for another preset I made. So a new ideaScale is called for: Currently I would have to make a copy of the preset "Loopy HD Control" and go in manually and just set it up from scratch block-by-block to match the parts in my own original patch I want. It would be better if in the HELIX Editor I could see AT ONCE BOTH my preferred preset - with the tones how i want it- AND the new "TARGET" preset - and then simply highlight the blocks I want then COPY AND PASTE this to the new preset containing the MIDI control pedal assignments. For this I need to be able to view the details for TWO presets AT ONCE - one being the "SOURCE" preset (read-only) and the other being the TARGET - with only the TARGET being editable, paste-able etc so one can copy anything from the SOURCE into the TARGET patch. This would save a lot of time. It would also be very useful in any situation where one wants to combine parts from two different patches into a new one.
  23. Good point about the MIDI DIN - and have removed that new feature from the FR for an "extender" - but the EXP's those can go in my view since we would still have 2 EXP's on the main HELIX unit. Now this does in fact beg the question of whether there is an argument for another - more expensive than HELIX Control type product - one useable by non-HELIX users as well as HELIX users that includes MIDI DIN and 4 EXPs etc... and there is a case for that too - since when I surveyed the other MIDI floor controllers out there which have scribble strips - ( FAMC, RJM for example ) those currently go for around $1000 at least and more ! so if L6 were to enter that market too and sell for say $500 then L6 would be making a product far cheaper than the competition and would gain a new market much bigger than just HELIX owners. And having some kind of more intelligent link to Ableton etc for example would be amazing ( triggering loops, scenes etc ) where the scribble strips automatically change according to track names, clip names in Ableton etc - would be uber cool.
  24. Latest IDEASCALE suggestion: A cheaper, basic "HELIX Control" type floor controller to extend the HELIX. This would - in contrast to the HELIX Controller for the Rack - NOT include the following: * LCD panel at the top ( not needed since we have what we need in the HELIX itself ) * the 4 expression pedal and toe switch sockets * the HOST socket BUT would also include the following: * an extra USB type A socket - to connect to the main HELIX, as well as the existing type B ( to allow iPads or other devices to be connected and routed to to the HELIX * DIN MIDI out and in sockets to control other MIDI based devices So up-vote this.... if you're pedal-greedy. Finally - you may say ( about this ) i'm a dreamer ....... .......... but i'm not the only one ... (ok ok ok i'll get my coat ) http://line6.ideascale.com/a/dtd/A-cheaper-basic-HELIX-Control-type-floor-controller-extender/820103-23508
  25. Shouldn't have to do this "have you tried turning it off and on again" business though ..... sounds like that upcoming "active sense" USB firmware upgrade might be a good idea
×
×
  • Create New...