Jump to content

ShoreProductions

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ShoreProductions

  • Rank
    Just Startin'

Profile Information

  • Gender
    Not Telling
  • Registered Products
    2

Recent Profile Visitors

468 profile views
  1. Installing Gearbox for POD X3 on OS X 10.12.6 Sierra This process works with the POD X3, I cannot confirm that it will work with any other POD of any other operating system other than OS X 10.12.6, Sierra, although it may. Download: Gearbox 3.72 for OS X from Line 6 Downloads: Select: All Hardware | GearBox | All OS - 1. Run the Line Monkey 1.78 App and insure that your software is up to date, particularly “Flash Memory 2.00” 2. Perform a typical install of Gearbox 3.7.2 3. Navigate to /System/Library/Extensions and remove, rename or relocate the “Line6Audio.kext” file. 4. Replace it with the "Line6AudioSigned.kext" file (Linked Below), or extract the file yourself from the Drivers 7.6.8 download. Select: POD X3 | All Software | All OS - Line6AudioSigned.kext.zip Please share your results, so others might benefit from your experience.
  2. That's interesting AD, I'd watched that video previously prior to purchasing a PC+ and it didn't register with me that Line 6 had made an official statement regarding the future implementation of L6 Link control @ 6:09 The one advantage of MIDI is that it can be used with other external MIDI controllers including most DAWs provided the user has some form of a USB to MIDI converter.
  3. Did you install the Line 6 Helix Driver2, Version 1.0.5?
  4. Good point, if you're outputting mono, no need to expend additional processing.
  5. Close but no Cohiba, I would be willing to give you a tiparillo, as a consolation prize. Actually, I think that's the way I initially spelled it, but spell checker gave me a thumbs down. :rolleyes:
  6. You're right, the valve driver seems a little pink to me.........Maybe it's fuchsia.
  7. You're quite correct, my bad. My previous comment has been edited.
  8. To answer your question directly, I don't hear a difference, but then again my hearing is subpar due to way too many years of abuse. However, the dialog is digressing. My initial comment, was in regard to Phlim's statement regarding DSP consumption relating to "stock cabinets" and third party IRs. No mention was initially made regarding the usage of either 1024 or 2048 duration samples.
  9. I'm simply relaying what was said in his video:
  10. It's seems that Scott would take issue with the conversion issue as well. He seems to believe that there is a perceptible difference in using the 96K versions as opposed to the 48K versions, irrespective of transcoding: https://youtu.be/nAGCWFA380Q?t=209
  11. If that's the case, then Scott Minchk, intentionally mislead everyone in his video. I'm not quite sure how he would have accomplished that, considering that there don't seem to be any edits in his video. He clearly demonstrates that IRs consume less DSP, than stock cabinets. He also is known to use 96K wav samples for his IRs.
  12. I agree with you wholeheartedly, I wouldn't unscrupulously download Helix code or any other code, for that matter. From my limited research, it's my understanding that the DSP chips in the Helix are SHARC processors from Analog Devices and run on the .NET based IDE. That having been said, it's likely that SigmaStudio is the GUI development tool used my Line 6 for these processors. SigmaStudio is a freely available for download at: http://www.analog.com/en/design-center/processors-and-dsp/evaluation-and-development-software/ss_sigst_02.html#dsp-overview Although I'm not familiar with Enterprise Resource Planning or their software, I assume we could agree that no one or any small collaborative group, regardless of their level of expertise ( IE. the Helix development team), possess all the answers to every potential option available for this hardware. Some would argue, that once someone is mired in a particular paradigm, they inevitably have difficulty thinking outside the box. Even if one were understandably suspicious of another's code, the option for an individual to develop their own code, would ultimately prove to be of benefit to the Helix community. since concepts could still be exchanged.
  13. That's certainly your prerogative, however others may feel differently. We all fear, what we don't understand. I would agree with you. I wouldn't be inclined to install a effect from an individual that wasn't knowledgeable with the source code, but to my knowledge we don't even know what language was used to produce the code.
×
×
  • Create New...