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

Petes63Strat

Members
  • Posts

    66
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Petes63Strat

  1. Good point. Thanks. I really don't have a strong need for the hardware version other than the convenience of pedals, snapshots, etc. I was just unclear about whether the hardware version and its editing software might somehow replace the need for Native. I am new to this so I'm still trying to understand how this works . Did Line 6 design these products to work together? For example will Native recognize the floor version and possibly allow it to change tones or snapshots within the plugin while recording, or is this asking too much?
  2. I have been enjoying my Helix Native and the convenience of just dropping a plugin into my various guitar tracks in Logic Pro DAW. I will often have a dozen guitar tracks, sometimes bits and pieces, and love the idea that I can just go in and tweak the tone with the plugin of each track but this brings me to my question: I have a chance to pickup a Helix LT which made me wonder how different it would be to use this hardware version of Helix when it comes to laying down tracks IF I was to no longer use Native. It would seem that I'd have to create each track with the hardware as the input and would not be able to adjust the tone after the fact, like with Native. It has my head spinning a little. I like the idea of the floor unit for the pedal and switching control, etc. that Native lacks but I can't get my head around how to use it as effectively with my DAW as Native, or would I need to use both? Any suggestions sure would be appreciated.
  3. "The toe switch isn't the reason the defective pedals are breaking. That doesn't have anything to do with it...". Really? I understand that there is a flaw in the design of the metal stamped panel or perhaps the way in which the pedal's pivoting assembly is attached to this panel. However, if the toe switch is also defective, in that it requires more force to trigger this switch than was originally intended (designed for) one could reasonably conclude that this additional DOWNWARD FORCE would translate to additional stress on the pedal's pivot point which might contribute to an early failure of this assembly. But that's just me.
  4. One thing that might help is if the toe switch did not require so much pressure to trigger between the 2 modes. My friend has a brand new Helix LT and says that he has to practically stand on it to activate the switch. This only contributes to the likelihood of the hardware cracking as described above. Can anyone explain how this "switch" is designed or where it's located? Any ideas on addressing this to trigger with less pressure? Is it a mechanical switch or is it some kind of sensor, pressure plate, beam, any idea?
  5. Soundog: I think I'm getting closer to the source of my problems with Helix Native and my tinny headphones tone. I was reading though that thread that I linked you too and realized that you had actually commented there toward the end. I saw where a couple of guys commented on their Sennheiser HD 600 (300 ohm) headphones (Beyer-dynamic DT 880s & 990s at 250 Ohm) and how much they loved them while pointing out that the lower OHM units all seemed to sound terrible. It was then that I realized that the headphones I use are also lower impedance and wondered if this is what is contributing to the tinny, crappy tone that I get. One is 38 ohms and other is 55 Ohms. Like Rich (rsvete12), I am using the Rig Kontrol 3 as an audio interface (on his recommendation) which has a headphone out but I am not sure what the impedance is so I am apprehensive to spend $300 on a new set of the Sennheisers until I can get to the bottom of this. I also have a Focusrite Scarlett 2i interface if need be. Focusrite says to "look for headphones with a maximum impedance of 200 ohms", which is already above that of the Sennheisers. At the moment I am running the L&R line outs from the Rig Kontrol 3 unit to my Samson Q5 headphone amp. So, I am not even sure if the headphone amp requires its own consideration where OHMs & headphones are concerned or do I just base the OHMs upon what the Rig Kontrol 3 is sending to it from the line outs? It's all a bit of a question mark for me. I am determined to get good tone in headphones (like you do) so if I can confirm that the Sennheisers will help I will certainly order a set. Sorry this got so long winded. I hope to report back with some great news if I can get this sorted out!
  6. Thanks soundog. I appreciate your help. It seems that a lot of players have this same issue so I know I'm not alone. I read through this entire thread below but did find much help: I will try one of the EQ plugins you mentioned and see if I can improve upon this. Thanks again!
  7. Hey Soundog: I was hoping you might have a suggestion to improve my Helix Native tone through headphones using your EQ plugin idea. I have been searching all over for a solution when I came across this thread. I have no shortage of otherwise great quality headphones (and have tested with even more from friends and colleagues). Here is my situation: Pretty much everything (including Helix Native) sounds good through my power amp and Yamaha NS10 monitors. However, when I try to monitor through my headphones Helix sounds terribly thin, trebley and lifeless BUT all of my other tracks still sound perfectly fine. I have not been able to find a work-around and have even tested with multiple Audio Interfaces. But then it occurred to me that I might try an EQ plugin (I use Apple Studio X) where I could adjust the EQ to try and achieve a good sound on the track that I'm running helix through and then simply switch the EQ on or off depending upon whether I'm monitoring through my amp & speakers or my headphones. Has anyone tried this? Do you think there is a way of improving the Helix tone in this way? I am actually at a point where I have otherwise stopped using my headphones with Helix. I have only basic experience with EQ so I am not sure where to start with any attempt to correct this tinny sound (other than just screw around 'til it sounds better). I tried Rich's idea of a headphone tube amp and while it warmed everything up a little it still left me short on Helix.
  8. Sound info from Soundog. I will start digging into those Logic Pro tricks as needed. Many thanks!
  9. soundog: This may be off topic so if you can, please point me to a proper discussion about this as I can't find one: I understand that Helix Native has a given amount of processing power as a plugin. This is evident when I start to see some features greyed-out as I try to add one too many blocks. My question is this: If I have several guitar tracks in their raw form (not mixed down), and I have the Helix plugin FX on each track, does Helix see this as 'one big plugin' straining Helix, or is it only a strain on my Mac's ability to process multiples of the plugin? I have a Mac Pro with 2x 2.66 Ghz 6-core Xeon, 48 Gb 1333 Mhz DDR3 Ecc Ram with all SSD drives so if it is the computer that suffered the load I would hope that my setup can handle it. I might know the answer to this but I want to confirm it with someone who is experienced in these matters. I am loving my Hxn so thanks again for your early assistance with setting me up!
  10. *Update: This works but can be finicky in Log Pro since the DAW will often forget these controller settings from project to project. Still not 100% happy here. soundog: I finally got my HxN Snapshots to properly change via the Native Instruments Guitar Rig 3 floor controller with Logic Pro DAW. It working! In the end it was a simple but counter intuitive step that made it work. I first had to experiment for hours with the midi settings within the Rig 3 unit. Then I added one step to the way I was using the learn feature in Logic Pro. I have a feeling that it was this step in Logic that made it work as many of the midi settings in the Rig 3 should have actually worked sooner: While in the Learn mode of Logic Pro, I would choose the Snapshot drop-down from within Helix Native. This would then be reflected in the Logic Learn window and was waiting confirmation with some action on the controller. The next step should be to simply hit one of the switches on the controller, look for it to confirm in the Learn window and then disable Learn but, this never worked. So, out of frustration, I tried it this way: While in the Learn mode of Logic Pro, I chose the Snapshot drop-down from within Helix Native. This was then reflected in the Logic Learn window. Now, instead of hitting just one switch on the controller, I hit all 6 switched (those that I wanted to use to control 6 snapshots, one right after the other) and THEN closed out of the Lean mode. It worked. It shouldn't but it did. To be sure, I cleared all the settings, went through it 3 more times and it worked each and every time. I then saved my Rig 3 midi file and sent it to rsvette12 to load into his unit and it worked for him. He even found improvements over his original settings. I know this is an odd combination of parts that might not apply to many other players out there but I must say that I love this setup, just as rsvette12 suggested that I would. Its built in audio interface, expression pedal and 8 lighted switches in a rock solid case for the price is a deal. Here is a screen-shot of my Rig 3 controller settings. For those interested: Just replicate these settings for as many switches as you will be using for your HxN snapshots but with one change. The value fields (both) must be set like this for the individual switches: 4 for switch #1 20 for switch #2 36 for switch #3 52 for switch #4 68 for switch #5 86 for switch #6 etc. Thanks again for your help along the way. Happy New Year.
  11. soundog: I think you're correct here. I have tried both ways but ultimately felt that I needed to place the greatest emphasis toward the Controller Assignment window as you could see in my attached image. I still get virtually the same poor results each time I try a different combination of settings. I will either get the situation where only one button cycles through the Snapshots with each click, and none of the other buttons do anything, or I may happen to use a setting that yields zero results. I just can't find a way to get an action out of each button for each Snapshot, and I'm still here working on it. I did notice (as I'm sure you did) that when I program it through Smart Controls (as you do) it very neatly divides a knob into 8 sectors. I really thought I was onto something when I noticed this but there is just no apparent way to translate that to the foot controller switches. It's just not fair that rsvette12's setup is working while mine is not! After all I am a much better person than he is! I'm kidding. He has been a real trooper and has gone above and beyond in trying to help me get to the bottom of this. We need more guys like him (and you of course) who are willing to take an active interest in helping others and sharing their knowledge. Thanks again for your continued help! Happy New Year.
  12. soundog. I would be so grateful if you could keep me in mind with any kind of solution or work-around. I have never been so stumped by something that should otherwise be relatively straight forward. Thanks again!
  13. Hi soundog. Thanks for weighing in. I have tried the Smart Controls feature and also tried using separate CC#'s for each Snapshot. I still get the same results whether I use Smart Control or go directly through Learn, outside of Smart Control. The problem (from what I have read and experienced thus far) is that the Snapshots are recognized as a group only (or index) and cannot be programmed separately as taracatac outlines above. Logic identifies them as "Snapshot Index" when I use the learn feature. If I use the learn feature with each of the 8 Snapshots (one at a time) they are ALL still identified simply as "Snapshot Index", not "Snapshot #1" or 2 or 3, etc. I hope that makes sense. At the very least I would have expected Line-6 to make the Snapshots easily programmable so that a player could work through them while laying down a track. I know there is a good argument for doing this in other ways, after all we are using sophisticated DAWs that allow us to piece things together. The part that is frustrating is that others are able to use this Kontrol Rig 3 floor unit (and others units) with their DAW on a PC to change Snapshots but I can't find a way to make it work on my Mac Pro with Logic. That's a first for me. Thanks again for your info!
  14. soundog: You inspired me to buy Helix Native to begin with and I'm glad I did! Since you and I are both on Mac (I am using Logic Pro and I THINK you are too) perhaps you can help me with this: I have spent a great many hours trying to change the Helix Native Snapshots with my external controller but can't make it work. Here is my setup and what I have tried: Logic Pro X with newest Helix Native Plugin Native Instruments Kontrol Rig 3 Controller (with their Controller Editor Software) Mac Pro, El Capitan 10.11.6 I have done this as mentioned above: footswitch1 CC#69 value:4 - this calls up snapshot 1 footswitch2 CC#69 value:20 - this calls up snapshot 2 footswitch3 CC#69 value:36 - this calls up snapshot 3 footswitch4 CC#69 value:52- this calls up snapshot 4 Etc. I then performed the "Learn" function for button #1 on my controller and the Helix Snapshot Index which seems to yield the correct on-screen response (and I then disable LEARN). Pretty straight forward. However, when I then test the controller buttons only Button #1 does anything at all and all it does is sequences through all of the Snapshots to the next higher number each time I press the button, the other buttons provide no reaction. When I study the "learn" window in Logic I can confirm that it is in fact receiving the 'CC#69 value:4' as it should (since I have used button #1 with Learn). I have tried what seems to be everything but clearly something is missing. I know that revette12 (who has been enormously helpful) has had success with his Kontrol Rig 3 controller and changing Helix Native Snapshots but he is using a PC and his Studio One DAW, not a MAC and Logic Pro, so he too is stumped at this moment where my setup is concerned. There are an awful lot of choices via several drop-downs within Logic's Learn window that I do not understand. I have tested many of them but of course there are an endless amount of combinations so the problem might lay there. Can you suggest anything that might help us move this along because I am out of tricks. * I have also tried 0-7 as an alternative to the numbers above (4,20,36,52,etc.) and other CC numbers as well. No luck. In the end Helix sees only the single button that I used with the Learn feature, and no others.
  15. No, I have been searching all over the place to see if there is some software that will allow me to communicate with this controller but there does not appear to be any. I think I will pass on trying to make it work with this unit and wait until I get a suitable controller like the Rig 3, as you suggested to begin with. Don't you just hate it when people don't take your advice the first time! :) Actually I'm just waiting to find the right unit. Thanks for hanging in there with me.
  16. That makes sense. Yes, I am convinced that I must effect the right settings in my controller first but I do not know what those settings are supposed to be for each button in order to communicate the right info to Helix. I read the part about sending a CC of between 0-15 for Snapshot #1, etc. but is it really that simple? Sending a midi CC of 7 (for example) will really do what I am looking for or is there more to this? I might just have to wait until I can get the Rig Kontrol 3 as you suggested as it may be a lot more straight forward. I just haven't found one yet.
  17. Hello again. I am using Logic Pro X and it has a very easy 'Learn' feature which I am able to use with no problem. If possible, my goal would be to learn how to assign a different Snapshot (1-8) to each of the 8 drum pads (or possibly other assignable buttons on this keyboard). As someone seemed to clarify already these Snapshots don't really want to 'Learn' in the same way that the other features are willing to 'Learn'. ex: If I go through the proper 'Learn' procedure with the individual Snapshots one at a time in the Helix Native editor window, and try to make it 'Learn' the button on my controller, that button will successfully trigger a Snapshot but not necessarily the right one. If I then press one of the other buttons that I just programmed it will not trigger the Snapshot that I programmed it to but will instead just make the Snapshot go to the next higher number (like from Snapshot 3 to Snapshot 4). Therefore there must be something I am missing in my keyboard programming of general understanding of how this works. In order to dig into it deeper I'd just like to understand what the Helix Native Snapshots are looking for in order to successfully change to the correct Snapshot number. That said, I may never figure this out on this Axiom keyboard because the documentation is terrible and complex midi channel programming is not my strong suit. Also, I am not aware of any 'controller software' for this unit. I have typically made changes only from within the controller unit itself. Remember that I am using MAC so sometimes there is no driver or software settings to work with like there might be on PC.
  18. I am able to setup most of what is needed but I'm still having issues with changing Snapshots via my USB controller. I will eventually buy a more suitable controller (as rsvette12 and others have suggested) but I'd like to figure this out on my Axiom 61 keyboard controller if for no other reason than to get better acquainted with all of these elements and how they communicate with one another. The Axiom has 8 little drum pads that might work for choosing 8 different Snapshots but I don't fully understand the mechanics of how this is supposed to happen. I read the part about using a 'Control Change' (CC) of 0-15 for Snapshot 1 and 16-29 for Snapshot #2, and the mention of using midi channel 24, etc. but how does the Helix plugin know what midi channel to respond to when there does not appear to be any way to set it from within the Helix plugin? Or does it just read and respond to all channels by default? Very confusing for a very old rocker who dropped acid in the 60's. I'm kidding ;) Can anyone expand a little on the comments below from cruzfolmli? This is all I want for Christmas! Happy New Year to all. On 4/1/2018 at 3:38 AM, cruzfolmli said: You map it to a midi channel not a switch. So say you map it to channel 24. Have switch 1 send CC #24 value: 1 then have switch 2 send CC #24 value:127 etc...
  19. Yes! I have been wanting to find a way to address the tinny sound of my otherwise great headphones when monitoring my DAW. It all sounds pretty good through my trusty NS10 monitors and power amp but thin and lifeless through the headphone jack on my Scarlett audio unit. I will start looking for an app solution. Is the headphone output from the RK3 pretty good? Your Corvette is spectacular! That's the perfect color combo in my opinion. I still have my all black C6 Z51 3LT from '08. 30K miles so its still like new and I don't drive it enough to justify the bump. I meant to mention earlier that Soundog also helped me out a lot. Your right. There are some great people here that are willing to pitch in and help out. Thanks again. I'll keep you posted.
  20. Wow, this is great stuff and sounds like a perfect solution. I can't tell you how much I appreciate your help. I will get my my grubby little mitts on one of these units and will get back with you. I promise not to allow this to fall under the heading of "No good deed goes unpunished" but I may have a general question or two. While we're on the subject, do you have these buttons replicate exactly what the buttons on a Helix floor unit do or do you have your own personal setup? I just ask because there are so many patches made for the Helix floor unit but they don't really translate straight across to Native due to its lack of hardware buttons. Just curious and I am VERY new to this. I didn't understand you last short post: "Mac stuff here - i would load some up and see if it helps - should " On a personal note: Do you wear tights and a cape? 'Cause I feel like you just swooped down to help me out of a jam :) Hey, do you have a Vette?
  21. Ya, with the Mac I am pretty much stuck with whatever driver they are providing. With the RK3 do you program it to the DAW and the DAW to the Helix plugin? Or does it program directly to the plugin? Not sure how this works since I've never had to deal with this. My only experience with this sort of thing is this: I have a USB Alesis keyboard controller that Logic Pro located automatically and I then found that most of its controls were allocated to the DAW which seemed pretty clever and was a real time save. I made a few personal changes here and there and it works great. But, it sounds like the RK3 would have to be addressed manually (?) Glad to hear that it also works well for an audio interface. This might be a real bonus! I really appreciate your help, by the way. I am always ready to tackle anything as that's how we learn so I will keep an eye on that one in the Ebay auction and elsewhere! Thanks again.
×
×
  • Create New...