Jump to content

zolko60

Members
  • Posts

    594
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by zolko60

  1. I have Friedmann BE-OD clone. IMO this is the best "brown sound" I've heard. It does the trick whatever amp you will stick to it. There is a yt EVH fan who confirms my claim.
  2. Clarett probably has Toslink input switchable between SPDIF and ADAT protocols. There are some SPDIF RCA to SPDIF optical converters on the market. In case of LT you would need AES/EBU to SPDIF optical. Multi Output or whatever is assigned to Digital Out. AES/EBU and SPDIF are two channell only protocols. I don't think Clarett could level the incoming digital signal. You can set Hx digital output level either in output block volume or global settings. As far as I remember Hx Volume knob affects what you set in Global Settings, likely only analog outputs. (2.71 firmware state). Yes. usual input representation. ;) Should work but I would check the manual or Focusrite forums.
  3. And if this does not work replace with a compatible tactile switch eg. C&K PTS645SL43-2 LFS
  4. You mean OSX? I have never seen independently set buffers for ASIO drivers on Windows. All my interfaces have common buffer setting for all ASIO clients. Is this specific for Apollo Core Audio OSX driver?
  5. Are you sure? There indeed were some changes how Steinberg implemented PC# in VST3. https://www.steinberg.net/forums/viewtopic.php?t=74526
  6. Why? The pilot's guide says it is also VST2 and it appears as VST and VST3 in Reaper plugin list (Windows). And the answer would be simple: Program Changes are either implemented or not. It does not matter what plug-in type it is.
  7. In Reaper you can automate and make PC# control "FX presets" changes. This somehow changes the whole plugin state including the Helix preset. So the PC#s can be used at "higher" DAW instance. I guess it shoud work in other DAWs which have their own "FX presets".
  8. Really? I have not notice any benefit latency wise by using standalone "plugins" vs DAW/Host hosted. Pro Tools may be the exception with its CPU heavy engine. Third party hosting is also beneficial. You can workaround all HxN limitations and integrate it with the best in their class plugins. So for me there are two possible reasons of making stand alone plugins. The first is a convienience for unexperienced users not using DAWs. The second is full controll meant by two way MIDI or whatever other communication protocol. It is easy to control HxN by the controller but it is not easy to control the controller. When you change preset or snapshot you may eg. expect the software to send at least CCs that illuminate controller switches. As far as I know there are no plans to make Native compete the hardware Hx versions in live usage.
  9. The actual difference is 9ms only by changing the driver. Resampling in case of OSX multi sample rate Core Audio does not change much unless the right way is to compare 2 times bigger buffer at two times sampling rate. If so the difference is 3ms (12ms to CC). Class Complaint OSX 48KHz 128 buffer - In 5.917 Out 4.688 = 10.605ms Multi sample rate Core Audio 48kHz 128 buffer - In 8.667 Out 10.667 = 19.334ms Multi sample rate Core Audio 96kHz 128 buffer - In 10.333 Out 9.333 = 19.666ms Multi sample rate Core Audio 96kHz 256 buffer - In 11.667 Out 10.667 = 22.334ms Source:
  10. That would require USB transfer of signals other than 48kHz. Is this the case? IDK We are told "Guitar In" is 123dB dynamic range. Is this true? IDK Is "Guitar in" set to 1Mohm something different from "Return In" set to instrument level? IDK Are there Hx Stomp inputs/outputs any different from Hx FL inputs/outputs? IDK You mean in some documents published by Line6? I have never seen any but if the device is claimed to be Class Complaint and works as Class Complaint under OSX and the only sampling rate it reports is 48kHz you can conclude it is 48kHz.
  11. I have almost sorted out what is going on with Helix input and output levels by my and my friends research. The professional standard for line level audio signals is +4dBu. If we assume 15dB headroom to full scale digital level (0dBFS) is the standard Line 6 has adopted then Helix has three level settings: Line level: +19dBu full scale (+4dBu reference with 15dB of headroom) Instrument level: +11dBu full scale (-4dBu reference) Mic level: +8dBu (-7dBu reference) The pad on instrument input labeled "Guitar In" is 5dB so padded input is +16dBu full scale. Hx FL/RA "Aux In" is just another line level input. The Volume Kob is a digital attenuator assigned before chosen DA converter(s). Now let's see what is happening when we interface Helix with Yamaha MG06 mixer by XLR cable: Let's input -4dBu sinus signal to Guitar Input. It will appear at Hx XLR outputs set to mic level as -7dBu. MG06 mic preamp gain range is 20-64dB. At minimal gain position we get +13dBu. Getting unity gain is not possible without engaging mixer 26dB pad. Using DI box is better because they usually attenuate an amplitude by 18-20dB (plus some padding). -4dBu input signal appears at Helix XLR or TRS outputs set to line at +4dBu. After DI box -14dBu. At min mic pre gain we are near the unity. What I don't know is if Hx FL/RA mic input is set to the same mic level standard (0dB gain=-7dBu reference with 15dB of headroom=+8dB full scale). I would appeciate if somebody could confirm that. Thank you for your attention and research cooperation. :) Yamaha MG06 manual http://shopwl.com/content/MG06 Mixing Console - Manual.pdf
  12. In what sense they are 192kHz while Hx has 48kHz clock? Do they make some on chip oversampling?
  13. Well, this is not an "issue". You record 48kHz audio but you process and store it at 96kHz. What you monitor is 48kHz because your interface works with 48kHz sampling rate. On the fly resampling induces some additional latency and this is why 48kHz Class Complaint usage on OSX gives the smalest latency. The only reason to use other than 48kHz sampling rate with Helix as USB interface is compatibility with 96kHz sessions on some DAWs.
  14. You have four phisical inputs hardwired to four USB inputs (5-8). 1-4 are processed signals connected to those phisical inputs (or taken from USB output). Helix works at 24/48. 96khz is done by driver resampling. You can expect problems with monitoring when Hx is used as your monitoring center. Round Trip latency is quite high so monitoring thru DAW is problematic. Conclusion: Using Stomp ar even Floor/Rack as an main audio interface may not be a good idea.
  15. "(...) I have posted I can't remember on whose page recently that we are working our asses off (...) We gonna alter the calendar (...) move spring out, shorten the summer (...) I would say within the next two weeks (...) If I am wrong and I am wrong all the time (...) we will update my mistake to the team...) I think we are very close, you know measure twice cut once kind of thing (...)" 1:09:00
  16. I would prefer to help you with "no but" solution but I can't. :(
  17. I suppose there may be more solutions of your puzzle (not easy one without snapshots). 1. If we define the task as "how to construct A/B, Y, Bp switch on parallel paths with constant dry level", we can use: - delays mix parameter automation as bypass (mix=0 bypass on, mix=100 dry kill) - single delay dry path as a dry path for both - multiple FS assigments Expected issues: - not intuitive FS illumination - trails mutes 2. So maybe A,B, Bp would have nicer solution? 3. Or maybe it's better to automate some multitap delay? While I am away of may hardware Hx LT and Native has no multiple assigments I leave it to somebody else ;)
  18. Now I have realized my way is maybe the same as setting delay time to different division by FS, so maybe you could skip one delay. :) There is no volume compensation in splits. When you route signal by both paths you double it.
  19. You set multiple assigment. Set both delays bypasses to the same FS.
  20. Skip the individual bypasses (unless you really need to use both delays simultaneously) Delays parallel on A and B paths Split A/B routing (A or B) - first footswitch Common bypass - second footswitch Merge.
  21. XLR or TRS 1/4" jack. Shielded, high quality, flexible.
  22. The manual is irrelevant, but I stll believe keeping the obsolete manual written in 2016 after 2.80 firmware update which is changing Helix quite seriously would be strange. BTW almost all of published documents are obsolete, the Knowledge Base is hardly updated. If you want to capture some L6 leaks the L6 website is the last place to search. TGP and facebook are the media. Is it driving me nuts? I don't think so. It is just the kind of practice I don't expect from the company treating their customers seriously. To criticize the communication politics is nothing wrong. L6 has just a chance to listen and fanboys have chance to improve their justification and defence methods. :D A. OK. So keeping that info sticked to the first page of this forum is justified when their good faith failed? BTW the 2.80 release candidate compilation was successfull and in time. After having RC complied and sent to testers, estimations could be made more responsibly. What about "Avialiable 2019"? B. If L6 is dissapointed so maybe by using empathy it is reasonable to conclude some of the customers could be dissapionted too? And then undertake some PR action? C I can appreciate that. I can not appreciate the lack of proper communication. No drama involved. If I meet some L6 guy I can still shake his/her hand. :) I haven't seen anyone pissing on L6. All I see is questions of either missinformed or disappointed customers and the fanboys dog piling on them. OK. i buy it! Please (smbdy in charge) consider editing "Helix Firmware 2.80 (Available SPRING 2019)" topic to "Helix Firmware 2.80 (Avialable when it's ready)" or just to "Helix Firmware 2.80"
×
×
  • Create New...