Jump to content

Klaim

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Klaim

  • Rank
    Just Startin'

Profile Information

  • Registered Products
    1
  1. Klaim

    rate my tones

    Looks nice with my (not-flat) output! I was wondering: id you use any IR? Or is this only with the Helix stuffs? Is this a recent Helix version?
  2. @jshimkoski On 2 laptops: - both Windows 10 - both with Chrome, apparently up to date I don't get these squares with Firefox.
  3. Thanks for this website, it's helping me a lot (a noob at all this). I noticed that there might be unicode issues for example on amp settings explainations: https://helixhelp.com/manuals/helix/the-blocks.html#common-amp-settings I see squares (was there supposed to be symbols?)
  4. @Digital_Igloo I see, I was expecting that you already considered that (which is why I asked here first). I wonder if a way to visualize this as a separate "view" would work. Currently it's confusing because you have to know which pedal does what (I'm a noob in pedals so I don't know much of the ones available). In a physical pedalboard, at least part of the information is immediately visible: you can see the cables that are doubled on the pedals. But it's partial info as you say.
  5. How wow I can't manage to submit an idea in ideascale, it's super buggy O__O
  6. Indeed, maybe some other representation would work too. I think in some cases it might be hard to pull of because of the different ways signals can be split, but nothing impossible. I'll try to put this in ideascale then (I believe the devs do rely on it to see interest?)
  7. I was watching this: After watching this, I'm starting to think that the existence or collapsing of stereo or mono signal would be made FAR MORE CLEAR the lines were doubled when the signal is stereo. That way you immediately see between which block or input/output the signal becomes mono or stereo. Here is how it would look like: BEFORE (as in now) AFTER (display double lines on stereo signal paths) That way it's obvious what's happening, which block makes or keep the signal stereo, which block keeps or makes the signal mono and that this preset is meant to be stereo or not. I can see how that would make the drawings of the signal path with branches a bit more difficult though... depending on if it's a split signal left and right or not for example. What do you think?
  8. Klaim

    Buffer pedals + Helix ?

    Thanks for clarifying! Also thanks @emagli for the clarifications and @rd2rk, @SmackedActor and @silverhead for these info! I copied the list to refer to it later. I feel much more enlighted now XD
  9. Klaim

    Buffer pedals + Helix ?

    Thank you very much @rd2rk and @emagli for these answers, very helpful. I got a complementary explanation from a friend guitarist+electrician because I had trouble understanding what is actually impedance (in particular why I need a bigger number on the receiving side than on the source side). He then proceed to clarify your statements and I found the setting in the input block, we checked the specs of the pickups my main guitar have (Ibanez TAM10) and relied on your information to think about these setup. If I understand correctly then (please correct me if I'm wrong): - If I set the Guitar-Z setting to 1M OMhs, whatever I have plugged before the Helix should work. If in Auto, the first block gives the actual impedance at input at least, so that's best if I have no pedal before. - for pedals in send/returns loops, I should never have to change anything; - I will probably not need buffer pedals in these setup except if long cables are involved or if I have a lot of pedals before the input plug of the helix (or if none of these pedals have any buffer). Turns out almost all of my current physical pedals are true-bypass (I have no Boss pedal...yet) which basically means that having them all off is like having a longer cable (if they were all before the input or in the same send/return loop). My friend told me if the length is under 3 meters (12foot) it should be ok. I think that will always be the case but it's good to know (if you can confirm). The most complex situation I can think of for my projects is if I use the 4 send/returns + pedals in front, all on the same pedalboard, next to the helix (like an extension to the helix) in which case the cables shouldn't big longer than 1.5meters. Also if the polytune3 buffer is in the front of that complex setup, that should help keeping the signal right (if my understanding is correct). I was wondering: why isn't the default in presets to have 1M Omhs in the input block? Is it to be more true to the actual sound you would get with the pedals being simulated? Also @emagli could you clarify what you mean by "wah" and "fuzz"? Are you talking about physical pedals (in send/return loops?) or blocks (simulations)? Are you talking about specific models or do you mean "any wah" and "any fuzz"?
  10. Context: I'm still learning about music, only started a few years ago (though I compose a lot, for bands, games, movies). I have a Helix floor since the end of last year that I use as my main pedalboard+amp like many. Most of my time using it is for production, I had plans to use it live but you know the situation. I watched a lot of videos explaining stuffs about pedalboards and one thing that I still have a hard time to understand is: Is there a situation where I would need a buffer pedal when I use the Helix? (this question is rised also because I intend to get a Polytune3 - I don't like the Helix tuner :/ - and they act like buffers apparently, so I need to know what'I'm getting into...) I can see different categories of situations: 1. I use the Helix alone. In this case I think it's not useful, but I don't understand enough to be absolutely sure. Would adding a buffer in front of the Helix (for example the Polytune3) actually impact the sounds? 2. I use the Helix + a few pedals in front: mostly effects that I can't find in the helix. Assuming I will not have too many pedals (maybe 3 to 5 big max) in front of the helix, would a buffer help somewehre? Does it depends on the pedal? 3. I use the Helix + pedals in front + pedals in send-returns: mostly effects that are unusual + a (non-trivial) looper. Not sure if I will actually get there but it's one of the situations I was considering trying for a project. Same question about any need for a buffer? So far I assumed that I'll never need a bufffer as long as signals go through the helix, but as said, it's not completely clear to me.
  11. I wonder if a major iteration of that protocol (or maybe another protocol) could allow multiple interfaces and routing different interface input and output however we want. I mean, I don't see the hardware limitation. Or maybe it's for "forcing" the soft-realtime guarantee at the protocol level, but it looks like it's an arbitrary barrier today. I'll check if there are discussions in audio devs circles about this kind of thing.
  12. Oh that explains a lot! I was wondering why all DAWs were doing that "oversimplification" of forcing input and output from the same interface... (didn't make sens for me, coding-wise, but it make sens if it's a protocol requirement, even if it looks old-school)
  13. Beware, ASIO4All is seriously buggy. In particular, I used it with Windows10 + Focusrite audio interface and got regular bluescreens (due to ASIO4ALL trying to write where it shouldn't). An alternative for windows is VoiceMeeter Banana, it's designed specificatlly to be an aggregate of multiple interfaces (including ASIO ones). However it's not really trivial to configure for specific cases, I mean I use it and it works well but not with Ableton Live for some reason (probably my fault for not setting something properly). It's the closest non-crashing tool for that though. I wish DAWs would have an internal way to handle multiple ASIO interfaces. I don't know what is exactly the limitation here, I just know it's an OS one, but programming-wise (I'm a programmer) I saw code acquiring several ASIO drivers without a problem, so I don't know, it's maybe just that it was not common until recently?
  14. Windows 10 here, Ableton Live 10, I confirm I can see the combobox and change the value. I was wondering if in your case the value isn't just the one set on the device?
  15. That can be challenged: I've worked on console games and it is indeed difficult to make a software that doesn't crash after 48h (it's even harder when it's not on console and not games). But it is possible as it is a hard requirement on consoles. However, the requirements are not the same than for a musician's tool which is not running on a laptop. For things that are basically live performance hardware, one would expect to be able to spend a full day with the thing on, or at least a big bunch of hours. (I have a looper pedal that have some random issues like that too, I can't use it for live because of that) And in my specific case, both issues happened after a few hours (less than 5), not after days.
×
×
  • Create New...