spikey

1 hour ago, prc232 said:

If any line 6 people are reading this I would love to see this support come to iPad pro. 

Be sure and also post this request over on "The Gear Page". 

13 minutes ago, shanecgriffo said:

oh i thought it has been open quite a while..? i bought something a few weeks back

It probably has been lol, but I just got the email, and I really wanted to thank Jason for those multiple long videos on Helix where he explained in detail how to make it sound better! I figured the best way to do that was to open my wallet and make it Win/Win!

Market Place  is now OPEN!

Just purchased a group of ("THANK YOU for ALL the YOUTUBE VIDEO's") patches of Jason Sadites for Helix!

On 7/17/2019 at 6:20 PM, rvroberts said:

What I don't know about the Code 100 is is it using essentially an FRFR speaker system or are they using typical guitar speakers?

With the head, I use the codes own cab simulations, or I can switch them off in the editor and use what I want. I would expect that the code combo has speakers in it that are "tuned" for the best sound from the code's amp. 

On 7/17/2019 at 10:28 AM, littlecharva said:

people out there in the forums talking about how bad it sounds, but to my unsophisticated ears, it sounds fine.

I have the code head and it sounds "better" than fine to me.

3 hours ago, littlecharva said:

You're absolutely right about the cab sims, the Helix sounds bad if I leave them turned on - which is bizarre considering the Marshall CODE has it's own cab sims.

If you run the cab sim from the code and also run Helix with its cab at the same time, yes it will not sound good as expected. 

On EQ- start watching this guy!  

Make a ticket with Line 6 and see what they say.

FYI here are my Apollo Quad specs... The newer models are even better. The difference in the A/D and D/A converters will sound differently if one is WAAAAAY better than the other design (and cost-wise), but I doubt the human ear could tell the difference if both were close (as in this case). I think the code/software in Helix is just "better" made for audio than Native was for a VST Plugin. But OTOH I'm not writing much code these days ; )

Features

Audio Interface

• Sample rates up to 192 kHz at 24-bit word length
• 18 x 24 simultaneous input/output channels:
  • Eight channels of analog-to-digital conversion via mic, line, or high-impedance inputs
• 14 channels of digital-to-analog conversion via:
  • Eight mono line outputs
  • Stereo monitor outputs
  • Two stereo headphone outputs
• 10 channels of digital I/O via:
  • Eight channels ADAT Optical I/O with S/MUX for high sample rates
  • Two channels coaxial S/PDIF I/O with sample rate conversion
  • Two FireWire 800 ports for daisy-chaining other FireWire devices
• 32-bit and 64-bit device drivers

Microphone Preamplifiers

• Four high-resolution, ultra-transparent, digitally-controlled analog mic preamps
• Front panel and software control of all preamp parameters
• Switchable low cut filter, 48V phantom power, 20 dB pad, polarity inversion, and stereo linking

Monitoring

• Stereo monitor outputs (independent of eight line outputs)
• Digitally-controlled analog monitor outputs maintains highest fidelity
• Front panel control of monitor levels and muting
• Two stereo headphone outputs with independent mix buses
• Independent front panel analog volume controls for headphone outputs
• Front panel pre-fader metering of monitor bus levels
• S/PDIF outputs can be set to mirror the monitor outputs

Onboard UAD-2 Processing

• DUO and QUAD models featuring two or four SHARC processors
• Realtime UAD Powered Plug-Ins processing on all of Apollos analog and digital inputs
• Same features and functionality as other UAD-2 products when used with DAW
• Can be combined with other UAD-2 devices for increased mixing DSP
• Includes UAD Powered Plug-Ins Analog Classics bundle
• Complete UAD-2 Powered Plug-Ins library is available online 24/7

Software

• Console application:
  • Enables Realtime UAD Powered Plug-Ins processing
  • DSP mixer for realtime monitoring and tracking
  • Remote control of all Apollo features and functionality
• Console Recall plug-in:
  • Saves Apollo configurations inside DAW sessions for easy recal
  • Enables control of all front panel parameters from within the DAW
  • VST, RTAS, and Audio Units plug-in formats
• UAD Meter & Control Panel application:
  • Configures global UAD-2 and Powered Plug-Ins settings and monitors system usage

Specifications

System

• I/O Complement
  • Microphone Inputs 4
  • High-Impedance Inputs 2
  • Analog Line Inputs 8
  • Analog Line Outputs 8
  • Analog Monitor Outputs 2 (1 stereo pair)
  • Headphone Outputs 2 stereo (independent mix buses)
  • ADAT Up to 8 channels via dual I/O ports with S/MUX
  • S/PDIF 1 stereo input, 1 stereo output
  • FireWire 800 (IEEE 1394b) Dual ports
  • Thunderbolt (via Option Card) Dual ports
  • Word Clock 1 input, 1 output
• A/D D/A Conversion
  • Supported Sample Rates (kHz) 44.1, 48, 88.2, 96, 176.4, 192
  • A/D Bits Per Sample 24
  • Simultaneous A/D conversion 8 channels
  • Simultaneous D/A conversion 14 channels
  • Analog Round-Trip Latency 1.1 milliseconds @ 96 kHz sample rate
  • Analog Round-Trip Latency with four serial UAD-2 plug-ins via Console application 1.1 milliseconds @ 96 kHz sample rate

Analog I/O

• Microphone Inputs 1 4
  • Jack Type XLR Female
  • Phantom Power +48V, Switchable
  • Dynamic Range 118 dB (Aweighting)
  • Signal-to-Noise Ratio 118 dB (Aweighting)
  • Total Harmonic Distortion + Noise 110 dB
• HiZ Inputs
  • Jack Type ¼ Male (Mono TS plug required)
  • Dynamic Range 117 dB (Aweighting)
  • Signal-to-Noise Ratio 117 dB (Aweighting)
  • Total Harmonic Distortion + Noise 103 dB
• Line Inputs 1 4
  • Jack Type ¼Male TRS Balanced
  • Dynamic Range 117 dB (Aweighting)
  • Signal-to-Noise Ratio 117 dB (Aweighting)
  • Total Harmonic Distortion + Noise 107 dB
• Line Inputs 5 8
  • Jack Type ¼ Male TRS Balanced
  • Dynamic Range 117 dB (Aweighting)
  • Signal-to-Noise Ratio 117 dB (Aweighting)
  • Total Harmonic Distortion + Noise 107 d
• Line Outputs 1 8
  • Jack Type ¼ Male TRS Balanced
  • Dynamic Range 118 dB (Aweighting)
  • Frequency Response 20 Hz 20 kHz, ±0.1 dB
  • Signal-to-Noise Ratio 118 dB (Aweighting)
  • Total Harmonic Distortion + Noise 106 dB
• Monitor Outputs 1 2
  • Jack Type ¼ Male TRS Balanced
  • Frequency Response 20 Hz 20 kHz, ±0.1 dB
  • Dynamic Range 115 dB (Aweighting)
  • Signal-to-Noise Ratio 114 dB (Aweighting)
  • Total Harmonic Distortion + Noise 103 dB
• Stereo Headphone Outputs 1 & 2
  • Jack Type ¼ Male TRS Stereo/Unbalanced
  • Frequency Response 20 Hz 20 kHz, ±0.1 dB
  • Dynamic Range 113 dB (Aweighting)
  • Signal-to-Noise Ratio 113 dB (Aweighting)
  • Total Harmonic Distortion + Noise 101 dB

Digital I/O

• S/PDIF
  • Jack Type Phono (RCA)
  • Format IEC958
• ADAT
  • Jack Type Optical TOSLINK JIS F05
  • Format ADAT Digital Lightpipe with S/MUX
  • Channel Assignments @ 44.1 kHz, 48 kHz Port 1 = Channels 1 8, Port 2 = 1 8 (mirrored)
  • Channel Assignments @ 88.2 kHz, 96 kHz Port 1 = Channels 1 4, Port 2 = Channels 5 8
  • Channel Assignments @ 176.4 kHz, 192 kHz Port 1 = Channels 1 2, Port 2 = Channels 3 4
• Word Clock
  • Jack Type BNC
  • Lock Range ±0.5% of any supported sample rate
  • Word Clock Input Termination 75 Ohms, switchable
• Synchronization Sources
  • Internal, Word Clock, S/PDIF, ADAT

Electrical

• Power Supplies External AC to DC Power Supply Brick, Internal DC to DC Power Supply
• AC Connector Type IEC Male
• AC Requirements 100V 240V AC, 50 60 Hz
• DC Connector Type XLR 4-Pin Locking Male (Neutrik P/N NC4MDM3-H)
• DC Requirements 12 VDC, ±5%
• Maximum Power Consumption 6.5 amperes

Mechanical

• Dimensions
  • Width 19
  • Height 1.75 (1U rack space)
  • Depth, Chassis Only 12.125
  • Depth, Including Knob & Jack Protrusions 13.5
  • Shipping Box (Width x Depth x Height) 24 x 17 x 8
• Weight
  • Shipping Weight (with box & accessories) 18 pounds
  • Weight (bare unit) 9.1 pounds

Why would dragging them to the desktop 1st make "any" difference?

Is that so. Well, In that case, Line-6 should have used a "better" audio Interface when making Native then. ; )

All jokes aside If that were the case, I would have expected Native to sound "better" to my ears than it does.

Why? Because the A/D and D/A converters in the Apollo are superb. I just think its "my" ears which would make

sense because they are old and have listened to my playing over the decades. ; )

34 minutes ago, silverhead said:

 

And you're using Helix as the audio interface for your DAW on Mac? 

Nope, I'm using Helix as a guitar processor. My audio Interface is an Apollo Quad. My Helix and Kemper, my Fender SuperSonic and Marshall Code and DSL all sound good thru the Apollo. 

2 hours ago, silverhead said:

Are you monitoring the tones the same way in Helix and Helix Native?

Yes, Silver, I am. Both going thru the same pair of HR824 monitors. I don't think the oversampling chips made for audio are the same in my Mac versus those designed for audio in Helix. I remember D.I. talking about this way back as well. In any case, Native just sounds and feels "harder" tone-wise to me. Altho Helix is just another box of software- Maybe it's just a "software versus hardware" thing eh? 

I could not get the same tones out of Native I do from Helix. Ive been told from others the same thing, and then there are a few that say it sounds the same to them. Maybe it's just me but food for thought. Id get Helix and then buy Native later when on sale.

9 hours ago, leebee said:

I am still convinced that 2.81 deals with setlists/presets differently. I have now updated to 2.71. No problems. All setlists/presets perfect.

Interesting. Annoying as hell but still interesting. I would have bet a steak dinner Line 6 would have tested this, if not on 2.80 at least on 2.81. Like you said, if it won't import set lists why save/back them up?

Hope you get 2.82 very soon and it fixes this.

Thanks, I should have looked there 1st. 

Mine says "Edited" along with the old cab name. If you press the "Select" knob you will see what the cab is now changed to. Be careful and don't save the preset while in "edited" mode because it will be saying its one cab while sounding like (and being) another.

8 hours ago, Andy1175 said:

Maybe they misread the update instructions.  :)

Could be. I'm guessing almost a 3rd of those (and I'm being conservative) updating did.

21 minutes ago, Hillman1312 said:

For what its worth and to keep this thread active on the topic, I'm on 2.81 but the issue with the LA studio comp is still there. 

So Line-6 knows its a bug and just didn't get to it yet, or they did not know about it?

Yes, they are busy but a 5 second "we'll get er done" goes a long way here. I'd check TGP on this but obviously, my IP is banned there. 

2 hours ago, cruisinon2 said:

 

"What are you doing to my firmware, Dave?" ;)

 

 

"This mission is too important for me to allow you to jeopardize it."

What an amazing thing! I am "really having some fUN with this now! I have Helix hooked to the PC+ pair via L6-Link. I have the XLR L&R outputs of my Kemper hooked to the PC+ pair (XLR inputs). I then ran the XLR outputs from both PC+'s to my Mixer channel inputs. Now I can set up HX-Edit to pick any Cabinet from both PC+'s and save this as a Cabinet name (in HX-Edit) for my Kemper, and ALSO

use Helix as needed (in the normal L6-Link way) and swap cabinets in the PC+ pair for each Patch! ALL FROM My Chair in front of my DAW- BEST OF BOTH WORLDS!!! 

Hummmm, did I mess up by asking this or is this so easy to figure out a caveman could do it? 

Just wondering if I am overlooking something in HX Edit to allow me to store IR's in the PC+? 

Or do I always have to use PowerCab Edit for this task and nothing else?

Advanced Thanks for any info. ; )

I'm a bit confused..., a-gain. ; ) 

Is the only way to add IR's into a Power Cab + with PowerCab Edit only? 

Can I not add IR's into a PC+ IR slot using HX Edit? I mean if Helix sees the PC+ via HX-Edit and can control the speaker simulations inside the PC+ shouldn't I be able to add or remove IR's in the PC+ via HX-Edit too?

On 8/13/2019 at 11:07 AM, hideout said:

As a Mac user, I am very curious to see if other Mac users have had issues with the update.

I had no issues with the update after reading and then installing 2.80 and then 2.81, on my late 2009 iMac 27".

9 minutes ago, DunedinDragon said:

If you download weird little shareware programs or use advanced hardware configurations for gaming you should probably expect trouble. 

There goes the neighborhood... ; )

4 hours ago, mrkphpps said:

I was joking - this is not a tuner thread - sorry - my bad

 

It's all good. This is a useless wasted bandwidth thread about what would be nice but its never gonna happen anyway. Not that I'm complaining about not complaining. ; )