Jump to content

zolko60

Members
  • Content Count

    518
  • Joined

  • Last visited

  • Days Won

    2

zolko60 last won the day on July 20 2019

zolko60 had the most liked content!

Community Reputation

74 Neutral

About zolko60

  • Rank
    Gear Head

Profile Information

  • Registered Products
    1

Recent Profile Visitors

990 profile views
  1. There are plenty of knowledge on that topic online. Eg: You may also check the sample rate of your session. Maybe Logic allows you to record eg 44kHz with 48kHz Class Complaint driver?
  2. If you are direct monitoring the recording/playback path is exactly the same so it can't be any difference. However there is a chance you are doing something wrong eg. monitoring direct and software monitoring at the same time. In that case the latency makes comb filter with the direct signal which you may like better.
  3. The problem may be, the avialiable for download Windows driver is not the latest one. As far sa I remember the latest 2.8X Windows driver was only included with the whole update package.
  4. Nice chat on the topic in closed fb group https://www.facebook.com/groups/line6helixusergroup/permalink/1489385381245130/ Line6 employee claims nothing latency wise has changed with 2.9X firmware. Some people report RTL about 6-8ms on OSX at buffers sizes 64 and 32 samples. If anybody can confirm 32 (OSX) and 64 smpl buffers to be usefull (artifact free) please share your RTL reports or measurements and CPU model. Thank you for your cooperation!
  5. The Hx Edit "talks" to Helix hardware with simple json commands. Is it probably hard to implement heavy data trasmission required for such a visualisation with that method.
  6. Helix DSP allocation chart: https://benvesco.com/store/helix-dsp-allocations/ Helix MIDI guide: https://www.thegearpage.net/board/index.php?threads/the-unofficial-helix-midi-guide.1954544/
  7. New idea! Let's help Line6 2.0 - Helix wiki manual The Helix manuals (especially FL , LT) are very outdated. We are told writing a new manual is very substantial investment of time and resources. This is probably written by one author Eric Klein (aka DigitalIgloo) and need to be translated to many languages. This is why that work can be done at major releases firmware updates (X.00). Useful knowledge as specifications, new DSP blocks decription and their DSP usage, new funcionalities, MIDI manual, that should be in the owners manual, can be found in various places. Why not help Line6 and cooperate on the Helix wiki manual when all that content can be published, verified by Line6 employees and then edited and PDF published as neeeded?
  8. ...also, some users happen to be unaware of toe switch existence or can not switch it.
  9. Yes. You are playing for yourself and for your audience so there is no need to show any respect for the author's level intensions.
  10. The volume knob does not matter with leveling patches. Its purpose is setting global monitoring volume. The unity is also irrelevant to leveling patches. The guitar can be a factor. The brigde PAF style humbucker gives about -30LUFS unpadded. How the output loudness is dependent on the guitar is not researched yet. Still some measurements and setting some reference patches solves the problem.
  11. If you measure once or believe me that 01A, 01C, 03D are about -20LUFS no matter what you play then you can make a similar volume on any patch. ...and Helixes released so far have no leds to indicate the levels.
  12. I see the second topic of this thread is the idea of implementing metering in Helix hardware. I can imagine such a need but please consider: - we do not know what is the screen refresh or if a display GPU (if any) can handle such a task, - we do not know if and what DSP resources would be required, also Helix Floor has 7 analog and 12 digital inputs, 8 analog and 10 digital outputs - that is a plenty of meters! OK, but if you keep -20LUFS at output, your headroom is quite safe.
  13. No. Rationalizing things that make no sense makes no sense.
  14. There is no unity gain in case of amp modeling. After the amp peak level is likely reduced and rms level is rised. You put about -30LUFS (integrated) signal from a guitar and get -20LUFS at the output. Sometimes you need to be +/-5LUFS louder/quieter in the song context and loudness is heavy playing style dependent, so thinking of the absolute loudness equality hardly makes sense. Hx Native can mimic Helix hardware when input and output are set the same. Guitar Input +11dBu full scale (+17dBu with pad) and +11dBu full scale instrument level (+19dBu line level). -20LUFS output target is safe, it gives you a reasonable headroom. You can learn to target such a loudness level using any type of metering your DAW or mixer has or even your ears and compare it eg. to the factory patches of the same type. The volume knob is just a digital attenuator used to set the monitoring volume. The main reason of using it set clockwise at building patches is to prevent clipping, but if you keep -20LUFS output loudness level whatever method you develop or choose, it is unlikely to happen. There is a thread people present various methods of dealing with their loudness:
×
×
  • Create New...