codamedia
Members-
Posts
3,327 -
Joined
-
Last visited
-
Days Won
114
Everything posted by codamedia
-
yep... that was my point :)
-
I'm curious what you feel these are? Not arguing... actually curious : ) I know you have mentioned things like global blocks which... after a little thinking... actually has me excited about that type of feature. But I don't see that in this unit? Touchscreen? As we have discussed, not enough for me, but I understand if others want it. One thing I did like in one of the demo's I saw was a "search" feature. But - since I only roll my own presets, I would never use that :) Small footprint, not so important to me (just IMO).... but the capturing does interest me. ONLY if it is on part with Kemper! Otherwise if I had the extra cash I would just buy a Kemper Stage to go with my Helix... a combo some of my colleagues have. well... I don't own a Firehawk but I do own a Helix. There is nothing in that video that sets the Cortex apart "yet"..... just sayin'....
-
Current potential of what?
-
The other way to look at this is that only the flagship products have had VDI connectors... never the lower cost alternatives. Inflation taken into account, all things are still equal.
-
Line 6 does not monitor these forums for suggestions... Take your idea over the ideascale and post it there. https://line6.ideascale.com/
-
The answer to this is directly above by "lungho".... but I have to add a saying that I live by... on BOTH sides of the statement. "failure to plan on your part does not constitute an emergency on my part" or in reverse "my failure to plan is nobody else's problem" Seriously.... you knew you had work to do and didn't think you could do it all within Native.... why didn't you just take the Stomp home instead of demanding Line 6 change something for you?
-
Last I checked... you can still plug any Variax into any device... you just can't "control it" from any device. In the HX (Helix) line they offer three products with VDI connections and three products without. Choose the product that is right for you, and let others do the same. You can't expect everything at the cheapest cost....
-
This forum needs an icon for "trolls".
-
The Fishman Fluence for #3 makes sense as to why that image looks so unnatural... thanks for that. That first one does look the most natural to me... and since it's the downloaded sample I can see why you seem to like it. The extended lows of the other three would EAT any headroom and processing power in frequencies that you can't really hear, but would impact the overall tone, probably negatively. The extended highs on #3 I will blame on the fishman's.... I do not know the pickups or the reason they are that way so I'll reserve further judgement :) Most people do not have a problem with the dry signal of the Helix, so I think something else is going on. Are you sure you didn't process that signal (boosted lows/highs, compression, etc...) in the DAW after you captured them? Or... did you capture some noise such as ground loop hum, buzz, and/or hiss? Keep us posted on your next tests after you did your reset.
-
Please tell us what EACH picture is that we are looking at. From top to bottom... what exactly is "image 1", "image 2", etc... etc... From what I see... Image 1 looks normal (maybe a bridge humbucker?) and image 3 looks very unnatural for a pickup. Image 2 is an overlay so I don't know what it is suppose to be, and 4 looks better, but with an extended low range that isn't normal. If the sample guitar is not the same as your guitar... it is going to sound different. It's not "how they were recorded" as much as "what was being recorded". Do you have any idea what they used for a guitar on any samples you were trying? IMO, Never assume anything. Set it to 1M then you know for sure. Yes sorry, you are correct. A Helix and LT do not have "instrument/line" for the guitar input.
-
According to DI on TGP... "All models from Helix (with very few caveats); $449.99. April." So it's a sub $500 Helix with the limitations TBA... other than the obvious hardware differences. Line 6 always had a strong foothold in the sub $500 market so I guess they wanted back in. It's the largest market in the industry, I can understand that reasoning. TBH.... Based on my needs it looks like a more practical back up rig for me than the Stomp does. The limitations and size will dictate :)
-
I could be wrong, but I think snapshots have 2 limits.... You cannot swap amp/effect blocks You cannot re-assign footswitches or EXP's. #2 would be your problem. You can't have it control one thing in snap 2 then something totally different in snap 3.
-
I question anything I am buying from Amazon unless it comes from a reputable seller. I find Amazon itself (eg: when fulfilled by Amazon) to be generally safe, but those little bargain shops can be very unscrupulous. That was why my first question was "is it a genuine Apple Adapter?" Glad to hear it's all working for you now.
-
What is the exact chain you are using to record the "2nd" dry signal that you are comparing the Helix dry input to? Make sure the input on the Helix is set to Instrument, not Line Check the impedance setting on the input block... IMO, set it to 1M rather than auto if recording a dry track. This will assure the system is not changing it without your knowledge. Anything lower than 1M will begin to "dull" the signal.
-
Certainly not the end of the world... For those people that struggle with touch screens they are getting used to using a stylus :( When Line 6 decides to go the route of touch screen (which I know is inevitable) I do hope they keep the less fortunate in mind and retain the joystick.. or an equivalent.
-
Nobody in this thread has suggested that. Just because i said I "prefer" a pointer does not mean I don't want YOU to have a touchscreen :) Actually... here is a quote of mine from this very thread.... IMO the best option is to provide both a touchscreen and a pointer (job wheel, joystick, etc... etc..) so everyone wins. For me it's preference... for others, touchscreens just won't work! I know they provide knobs for adjusting values, but do they provide a pointer.... a way to actually get around the screen?
-
That is a very risky business move... and puts you in a terrible place if the plan halts and you promised to refund everyone's money. If you've spent it all, there is nothing to give back. The pre-sales would be a way to convince/secure investors. If they see 1000 pre-orders, they will feel much more comfortable investing their $$$. It is important to understand that YES, some people do have problems with their smartphones. Touchscreens work for the majority, but that doesn't mean they work for everyone.
-
There is no crystal ball to work with... you can only build using the technology available at the time. More power require a new piece of hardware... and I'm sure at some point, that will come. But it's important to realize that even that "new device" will be constrained to the technology limitations of it's date of production and within a year or so this entire "not enough power" discussion comes right back into focus. That is part of this game that will never, ever end! It is best not to let your mind get preoccupied with it. Don't worry about how many sounds you need in a night.... worry about how many sounds you need in a song. Try to solve the song with snapshots, not the entire night.
-
Just to confirm.... Sending a CC 69 command via HEX is not working... but you CAN send a Program Change in HEX? Can you provide a sample of the Program Change HEX you are using?
-
Actually... in a later post I did add this... I believe it is much more complicated that just saying HX Edit is guilty... partially for reason you described.
-
That has always been my approach to things as well. I always try an editor out of curiosity... but prefer editing the devices directly. When I ran into problems with HX Edit early in the game it was easy for me to just shrug it off as nothing I really needed anyway. I bought a Helix, not an editor... and the Helix is rock solid (IMO). To be fair... I don't even know if it's HX Edit that is a problem, or simply configuration conflicts within a computer. Some people have no problems, others do. I'm sure both are telling the truth :)
-
There are two things to consider with snapshots. Review these and evaluate the best way to set them up for your use. The various combinations of these could drive you crazy if not setup the way you want. 1: Global > Preferences > Snapshot Edits Recall (default): When you make changes in the snapshot (eg: turn an effect on or off) then leave that snapshot... that change is "remembered" when you return to the original snapshot. IE: It loads the last state of the snapshot when you return. Discard: When you make changes in the snapshot (eg: turn an effect on or off) then leave that snapshot... that change is "forgotten" when you return to the original snapshot. IE: It loads the original (programmed) state of the snapshot when you return. In both circumstances, reloading the preset returns everything to it's original saved state. 2: Since firmware 2.8... when adding a block you now have 2 methods to control it's bypass state. Snapshot Bypass ON (default). The snapshot will control the effects on/off status Snapshot Bypass OFF: The snapshot has no control over the on/off status... it is completely manual. The on/off status of each block is saved with the preset... so reloading the preset will reset the on/off state. Global > EXP Pedals > EXP1 Pedal Position: Determines whether the position of EXP1 is set "per preset, per snapshot, or globally". EXP2 Pedal Position: Determines whether the position of EXP2 is set "per preset, per snapshot, or globally". EXP3 Pedal Position (on Helix Floor only): Determines whether the position of EXP3 is set "per preset, per snapshot, or globally".
-
Two warnings with this... ALWAYS backup the file before altering it or you might find yourself needing to re-install the software. Do not change the "symbolicID" values on these pages.
-
@themetallikid ... Do you do all your work in HX Edit? If so, have you tried just working on the Helix itself? Reason I ask is that I have encountered silly issues when working in HX Edit, but never from the machine itself. I made the decision long ago to use HX Edit strictly for backup/restore and IR management and I have never had a single problem since. Right, wrong, or indifferent. That's just my experience. EDIT to Add...You posted a response while I was prepping my post.... I think you are on the right track with this....
-
You can always count on these forums for the following... Stomp users want more blocks HX Effects users want amp modeling LT users want more inputs Floor users want a smaller footprint