Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Search the Community

Showing results for tags 'json'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Support
    • Multi-Effects Units
    • Variax Instruments
    • Amplifiers
    • Computer Based Recording
    • Live Sound
    • Pedals/Controllers
    • Dream Rig - Line 6 Product Integration
  • General Discussion
    • Tone Discussion
    • Line 6 Lounge

Categories

  • General FAQ
    • Operating System-specific Information
  • Tutorial Videos
  • Effects/Controllers
    • HELIX/HX
    • DL4 MkII Stompbox Modeler
    • FBV Controllers (MKII / 3)
    • M5
  • Amplifiers
    • Powercab
    • Catalyst
    • Spider V
  • POD
    • POD Go
    • Pocket POD
    • POD Express
  • Guitars
    • JTV / Shuriken / Variax Standard / Workbench HD
  • Relay/XD-V Digital Wireless
  • Recording
    • Helix Native
    • Metallurgy
    • Echo Farm/Amp Farm
    • POD Farm 1/2.0/2.5
    • Computer Audio Set Up and Troubleshooting
  • Legacy Products
    • POD
    • Amps
    • 1st Gen Variax Guitars / Bass / Workbench
    • Effects and Controllers
    • AMPLIFi Series
    • Live Sound
    • Digital Wireless
    • Mobile Products
    • POD Studio / Tone Port / GuitarPort
    • Software
    • Dream Rig

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Registered Products

Found 2 results

  1. Hello, I am working on a MIDI controller with LED displays and I would like to use a backup file (format .hls) to retrieve the name and footswitch default status (i.e. what FS is on/off for each snapshot when I go to the preset or change snapshot etc). Since I don't change my setlist that frequently I am not trying to read directly from the unit but instead hard code the names and behaviors based on the .hls. I use a JSON parser to decode the .hls file and see there is a section called footswitch Here is an example (see full file in attachment) 'footswitch': {'dsp0': {'block0': {'@fs_enabled': True, '@fs_index': 5, '@fs_label': 'Volume ' 'Pedal', '@fs_ledcolor': 65408, '@fs_momentary': False, '@fs_primary': True}, 'block1': = etc.. Based on that, I originally assumed that each @fs_index would refer to a footswitch with @fs_enable for the status. However, that doesn't seem to be the case because I have a few setups with @fs_index > 5. To make things more confusing, I also see some presets without the 'footswitch' blocks though there are setup in the unit. Has anyone be able to understand how the hsl file work for the foot-switches assignment ? Any guidance on how to interpret the structure of this file ? Thank you. Pat. Test.txt
  2. I am using the Helix to control a bank of external pedals using the VooDoo Hex. I control the VooDoo Hex loops using CC messages. Of course, I can use the command center to do this, but manually assigning multiple channel / CC messages to control each loop for each snapshot (or foot controller) is tedious. I doubt live programming the Helix directly using an external app (midi or FBV) is easy (please tell me if I am wrong). Is there documentation on the .hlx JSON format? I could write an GUI editor to facilitate editing the .hlx files then upload to Helix with the Line 6 editor. I can try and use samples to reverse engineer, but it would be better to get official docs. thanks, mark
×
×
  • Create New...