Jump to content

kdog

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

7 Neutral

About kdog

  • Rank
    Just Startin'

Profile Information

  • Registered Products
    2
  1. Actually, it's pretty simple: You have something that s*cks but is easy and something that doesn't but requires slightly more effort. You decide what type of artist you are. ;)
  2. I have an Amplifire and it is quite a bit more powerful in some regards. In others the Stomp is better. I would definitely say they are comparable products and if I could only keep one it would not be the Stomp. The Amplifire is not big at all very close in size to the stomp and some people are likely picking up the Stomp to experience Helix modeling for cheap rather than for the size. The Headrush Gigboard might be a great option for those kinds of folks who want top quality sounds without the full cost of some bigger units, too. The Stomp is extremely cool but not the only game in town.
  3. Thanks Phil, that is helpful. I used that info when experimenting with the Stomp as a laptop interface. Unfortunately the stomp always connects the input to the output, though, and not all of my Apps recognize anything but input 1. I tried it on the computer and it works using your info as long as I create a patch that mutes the input 1->output 1 path (i.e. a volume pedal set to 0). But if the DAW issues a command on the MIDI bus it will change the preset unless I specifically block program changes being sent to the stomp; so it is still kind of a pain and not as useful as say my Scarlett where I can just flick a switch to stop the direct monitoring. Summary: stomp is not a very good choice as an audio interface for me because its own DSP path is always wired on and cannot be disabled. (I understand this is not its primary function, and is in fact the behavior most users want most of the time, so I am not complaining; but I am a little bummed because this was a value added feature for me and has turned out to be not really worth the effort).
  4. This cannot be true, the Helix stock cabs do not sound anywhere near as good as the now dated Redwirez IRs. LOL.
  5. I appreciate the response but on an iPad I am not always using a DAW. There are a number of stand alone apps that process an audio signal directly and they vary in their capabilities, since most interfaces built for an iOS device have the opposite default behavior (not direct monitored by default) a true DAW is about the only thing the Stomp does work with if you want processing in the app. Also, given that other interfaces on both PC and iOS can invariably control their signal flow directly with regard to direct monitoring; it would be useful for the Stomp to be able to do this without relying on some feature, which may or may not be present, in the software being used.
  6. So, I got around to trying out my HX Stomp with my iPad(s) as an iOS audio interface. It works pretty nicely in terms of sound and latency. One big issue (for me) though, is it seems like any software on the iPad sees the audio input as 'post processed' so to use the Stomp as a dry input you must run it through a blank preset. This is all well and good but as near as I can tell it always direct monitors the output (was listening through headphones). This means you always hear the processed signal from any software coming to the output through the USB interface and the dry direct monitored input signal mixed together. Sometimes this is what you want but often, you don't. If you try to get around this by muting the stomp's output level or similar it also kills the input to the software on the iPad because it is sending the signal after any processing on the USB. Is there some way to defeat the Stomp's direct monitoring of it's input without killing the signal going to the connected device? This basic feature would really improve its utility as an audio interface and I am wondering if I may have overlooked it. If not, hopefully it could be added with a mixer app or setting on the device. The stomp is a cool little interface in addition to being a handy processor.
  7. kdog

    Helix Native

    The Native GUI is borderline unusable on a large monitor, IMHO. It looks okay on my laptop but on my big monitor I cannot read it even with my glasses on sometimes. The black background and general color scheme do not help at all, either. It seriously needs to be completely redone. I do not get why so many GUIs for VSTs seem to be stuck about ten years back in terms of their scalability. Big monitors have been around for years now. If you are using a heavy DAW you likely have not one but multiple really BIG monitors. The ability to resize up and down seems so fundamental that it absolutely stunning so few have any concept of it. Revalver is about the only one I can think of that supports it off hand. Anyway, I consider Helix Native particularly bad given its sticker price because the text is unreadable and on such a minimalist GUI a lot of settings are difficult to discern. It's pretty lacking in a number of areas as a stand alone product, TBH, it feels like the absolute minimum product they could do and still declare victory in implementing the concept for the Helix in VST. If it were a standalone product I am not sure it would actually be a success.
  8. Agreed. I am a 'Native-only' Helix user. I was considering picking up some of Glen D's or Fremen's paid preset packs so I could learn from them but without the snapshots they are really not viable. I have found a few good ones on custom tone but a lot of those use them too. I am glad they went ahead and released Native and it is a really good tool but I am very anxious for snapshots, will be psyched when they get here.
  9. Posters above are incorrect. Native supports parameter automation right out of the box today. It's trivial to setup a foot controller in a DAW/Host that supports MIDI automation. Helix Native supports 16 MIDI automation switches and if your host is setup correctly will work with program change commands also. Setup is DAW dependent because Native is not stand alone. See Page 29 of the Helix Native Manual for detailed info. I don't know how the hardware Helix behaves wrt MIDI (I don't use/own a Helix hardware unit I just have Native) but it works great with a generic MIDI floorboard connected to your audio interface.
  10. Darn, yes, you are correct, I misread the OP. Thanks for the correction.
  11. If you hover above the cab icon there is 'power' symbol that can toggle it off. It is also present on the settings screen where you select the mic and such to bypass the cab.
  12. What platform are you on? If it is a Mac, I would recommend Mainstage. It is an excellent and easy to use plugin host. Not too expensive at all.
  13. Sorry if you did not like the tone of my response, but nonetheless you clearly have it setup incorrectly. You can either take it (along with the more gentle input from others) as good advice and fix it, enjoying the product as it was designed to be used or you can ignore others advice, not learn anything, and move on, missing out on a great product. Your choice. Shrug.
  14. The way it is working on my Mac with Mainstage as a host: In the plugin it has a set of knob and switch controls defined but not assigned to anything (at least I don't think they are assigned by default). In the plugin you assign a control to a particular thing like say, the knob1 automation control to the gain knob on an amp. Then in mainstage (the host) I assign that knob1 parameter to one of the mainstage controls that has been assigned to some MIDI control and it all just works. It is almost exactly how Amplitube is setup in terms of mapping things. I do not directly assign MIDI control->Plugin Element in the plugin. Amplitube doesn't allow you to do that when it is invoked in a plugin either (if memory serves), the direct MIDI control in AT is only available in standalone which Native does not do. In a host it uses this automation parameter paradigm (AFAIK).
  15. Based on what you are describing, you still have your direct signal coming into your DAW. LOL. You probably should not be critical of VSTs in general if you can't get the most basic details of setting them up correct.
×
×
  • Create New...