Jump to content

soundog

Members
  • Content Count

    1,567
  • Joined

  • Last visited

  • Days Won

    32

soundog last won the day on August 13

soundog had the most liked content!

Community Reputation

482 Good

3 Followers

About soundog

  • Rank
    Power User

Contact Methods

  • Website URL
    johnplainsong.com

Profile Information

  • Gender
    Male
  • Location
    Pacific Northwest
  • Interests
    music, time travel, teleportation, levitation
  • Registered Products
    3

Recent Profile Visitors

1,782 profile views
  1. Not sure how PMs work on this forum. ?!#% Trying this...

  2. @dawiodjoopkk12 — what sayest thou? Are you bona fide? A bot? A devil? Enlighten us!
  3. Wow, datacommando — I see what you mean! Very weird. I just read his other posts. I wonder if those little links at the bottoms of his posts (different in each post, and hidden by using small, light-colored fonts) give him some kind of cash flow? Like 0.00001 cent per post. So now he's some rich kid living in a mansion at the edge of the sea somewhere ... laughing at us and drinking Mai Tai's. If so, I feel used.
  4. soundog

    tim

    You gotta admit it made you want to click on it.
  5. Right on! Everyone having this problem should open a ticket and provide info to tech support. Doing so will help prioritize the alarm, and maybe lead to a solution. Squeaky wheel gets the grease. As someone who enjoys using Helix Native (with Mojave and Logic Pro 10.4.7), I sure wish Line 6 would find a fix for y'all.
  6. soundog

    Reverb Models

    A Klon is to a reverb as an amoeba is to a sperm whale. Where can I get this on a T-shirt in a men's medium?
  7. If it shows up in the plug=in manager as Enabled, than you should be able to use it: Create an audio track. In the track channel strip (main window or mixer window), click the Audio FX button, and use the pull down menu to find Audio Units > Line 6 > Helix Native. Select Helix Native and it should appear as a plug in in your audio track channel.
  8. Excellent info, @goldballoon ..... thanks for adding it!
  9. Sure its subjective. But you gotta trust your ears! Also, see this thread:
  10. Hmmmm. That's not normal behavior, and certainly annoying! The trial version does "phone home" (requiring a log-in to your Line 6 account) but an authorized/purchased copy of Helix Native should not do this, and you should be able to use it unhindered. Try a reinstall, or contact Line 6 and open a support ticket. The other possibility is .... did you recently upgrade Logic to version 10.5? It has had some problems with various plug-ins, especially when running under Catalina.
  11. Then you've got a seriously big problem.
  12. This is a weird thread, but I'll chime anyway. I play on a lot of sunlit stages. I find direct sun is the worst, and if you are in a shadow you can see the LEDs good enough. So ... if you build a thin plywood (even cardboard or art board will work) three sided box fitted to surround the sides and back of the Helix (leaving a slot for cords in the back, you can then fit the top with shade cloth that will cover just enough so you can still access the pedals, etc. The box should be high enough to need cast shadows cast on the LEDs. If the sun is behind you, you can fashion a high shade block behind you and the Helix. You have to think in terms of a sun block between the sun and your pedals. High noon is the biggest challenge, but that's where shade cloth can help.
  13. For what its worth, Helix preset files (.hlx files) follow the open standard JSON "JavaScript Object Notation." There's plenty of documentation re JASON online, and free or paid JSON editors available. I used to use one on the Mac called JSON Wizard to bulk edit Helix files. You can decipher the parameters in a preset jason file, but its not for the weak-hearted, and you may need to sign some sort of deal with the devil to get adept at deciphering things. Some Helix users have attempted writing parsers for .hlx files; look around on the forum and you might find something. Just to show you what you could be getting into with reading .hlx files, here is the front part of a preset, as read into a free online JSON Editor (there are lots of them, but I used jsoneditoronline.org): {"data":{"device_version":43122688,"tone":{"variax":{"@variax_str3tuning":0,"@variax_str2level":1,"@variax_str4tuning":0,"@variax_str2tuning":0,"@variax_str1level":1,"@variax_str5level":1,"@variax_model":0,"@model":"@variax","@variax_str3level":1,"@variax_volumeknob":-0.1,"@variax_str4level":1,"@variax_str6level":1,"@variax_str5tuning":0,"@variax_customtuning":true,"@variax_lockctrls":0,"@variax_toneknob":-0.1,"@variax_str1tuning":0,"@variax_magmode":true,"@variax_str6tuning":0},"dsp1":{"split":{"bypass":false,"@position":3,"BalanceB":0.5,"@enabled":true,"BalanceA":0.5,"@model":"HD2_AppDSPFlowSplitY","@no_snapshot_bypass":false},"block2":{"@path":0,"@type":0,"@stereo":false,"@position":2,"@no_snapshot_bypass":false,"Gain":2,"@enabled":false,"@model":"HD2_VolPanGain"},"outputA":{"@output":5,"@model":"HD2_AppDSPFlowOutput","gain":0,"pan":0.5},"block4":{"@no_snapshot_bypass":false,"Speed":0.02199996,"SyncSelect1":6,"Feedback":0.28,"@position":4,"@stereo":true,"TempoSync1":true,"@type":7,"Mix":0.22,"@model":"HD2_DelayModChorusEcho","HighCut":9540,"Level":0,"ModulationMode":1,"Depth":0.49,"@path":0,"@trails":false,"Scale":0.75,"Time":0.538,"@enabled":false,"LowCut":155,"Spread":1},"inputA":{"decay":0.5,"noiseGate":false,"@model":"HD2_AppDSPFlow1Input","@input":0,"threshold":-48},"block8":{"@model":"HD2_Chorus","Mix":0.5,"Tone":0.5,"Predelay":0.3199999,"Level":0,"WaveShape":2,"@no_snapshot_bypass":false,"SyncSelect1":6,"Speed":0.3199999,"@type":0,"@stereo":tru etc...... If you read through this gibberish, you’ll be able to find the block # used, and what it is. So for the above, Block 4 is category: Delay, and the effect is the Mod/Chorus Echo. The parameters used for Mod/Chorus echo are: Time, Feedback, Low Cut, High Cut, Mix, Level, Speed, Depth, Modulation Mode, and Trails. Reading through the gibberish, you can figure out what the parameters are. I didn’t take the time to do a direct compare of the JSON file and the preset parameter settings to figure everything out exactly, but most of the parameters are obvious. It wouldn’t take long to decipher the rest and get good at it. For this example: Time: 0.538 (not sure how this translates to ms in the block, but do some math; the parameter range is 0—8s. Double check to determine.) Feedback: 28% Low Cut: 155 Hz High Cut: 9.54 KHz Mix: 22% Level: 0.0 dB Speed: 0.02199 (again, double check to see how this parameter relates actual preset; range of actual parameter is 0—10. I’m guessing this is 2.2) Depth: 49% Mod Mode: check to see if 1 = off, chorus, or vibrato Trails: Off Like I say, its devil’s work. Somebody should write a good interpreter or parser and give it away to the world. I can’t because I’ve got to go clean my deck.
  14. Necrophilia is a treatable condition.
×
×
  • Create New...