carblu iolanna glorya
Kansas Eiffel
Hi guys i have this noise problem with helix native. Is like crackling static noise when i palm mute. But it only happens with certain amps.it all happen when i downloaded ola englunds 5150 patch. Idk but this is wierd, if i use and od pedal and a noise gate and nothing else the noise is gone like 90% but if i use eq pedals racks and such like on the patch the noise is back!
All levels are fine. its wierd on my 6 string, if i turn the tone knob off the noise is gone. on the 7 is not that bad but its sound muddy. i tried a real amp to see if it was the pickups. and no noise, the 7 string sounded good like it was alive lol.
So I found what the issue is. Apparently this plugin is not multithreaded. I have a new i7 and this plugin maxes the processor when your patch has a lot of low end. I was using sonar and you can see the first core of the i7 processor max out and start crackling. This is very noticeable with the sandman patch on the 2nd play list. L6 please make this processor multi core supported and fix the low end maxing the processor. Something that helped me was cut the low end frequency in your patch. Other than this the plug in sounds great!
wow so that is the issue. thanks for the help! i hope u can help me with this other thing i know is not line 6 related. but i have bought their gear lol. anyways i have two guitars one ibanez and one jackson. both sound great on my peavey vypyr amp. but on amplitube is different. you know that metallic aggressive tone we get when we palm mute power chords ( ola englund type, metallica etc..) ? well with the ibanez it seems i cant achieve it on amplitube when theres allot of low end and its been equalized by others.( its a patch a downloaded from youtube) to much bass and noise that i have to make my own adjustments and problem solved. but its wierd that both can manage the tone pretty well on the vypyr and that the ibanez cant on amplitube with amps being equalized differently. could it be my pickups that cant manage well the low end or something, or the interface? thanks
I'm getting this same static issue on my rig --- and all the usual suspects have been checked and this is not related to my gear. Not sure what the issue is - I have an older i7 -- boatloads of RAM -- running Reaper ---- Can run GuitarRig and Amplitube and every plugin known to man simultaneously without any issues -- a single instance of NATIVE and I get load grade static and crackle on all the sounds.
I've got the crackling issue on my box, too. It seems to have lessened when I changed some clock settings in my BIOS (run at max clock all the time instead of throttling, although that still seems to not actually be happening). No individual core seems to be maxing out. I toggled between Helix and Pod Farm 2 to make sure it wasn't a newly occurring hardware issue or something but PF2 is OK.
Having the same issue here, popping and clicking noises, on every pre-set I have tried, crunch, clean, etc... I do not have this issue with any other pluggin I am using. I have Pro-tools 12. plenty of processor, ram, blah, blah, blah.
I have the same issue here with Reason 10. Moved audio interface from Asio4All to a native Asio driver but that didnt solve it. The only thing that seems to help is to increase the amount of samples in the buffer even up to a point where with a "smaller" buffer size the playback of a song slows down. This all happens as soon as i enable the helix native effect, switching off the effect in Reason brings it all back to a normal state.
On a related topic .... i recently started recording new projects (Logic Pro X) at 88.2 KHz, 24 bits bits (used to use 44.1 KHz). I started having problems with crackling and midi/audio synch. This is on a newer, potent computer with lotsa RAM. After reading some white papers showing experienced listeners often couldn't distinguish differences between 88.2 and 44.1, 24-bit classical recordings, I've gone back to 44.1 KHz, 24 bits and things have improved. Interestingly, many sample-based VI's work better at 44.1 anyway.
I don't want to start a debate about 44.1 v 88.2 v 96 KHz, but there are complex decisions to be made these days (sample rates, CPU, chip set, RAM, DAW, CPU-hungry plug-ins like Helix, audio interface, hard drive speeds, on and on). Trade-offs have to be weighed. The last thing I want to do is reset buffer sizes or freeze tracks when I'm heads down in a mixing session.
The 44.1khz has a freq range of 1hz to 22.05khz. That encompasses the entirety of human hearing including babies, and children. Anything more would only be noticeable in the studio with expensive high-quality equipment, and there is a large chance it won't be that noticeable even there.
Also 12bit was cassette. 16bit was CD. 16bit is plenty for consumer audio. The only real benefit to 24bit, 32bit float, (or higher) is more headroom in the mix (in the studio) when the mixing/mastering engineers are still working on the project. When they get finished it will be out at 16bit, 44.1khz on a disc.
Initially I had planned to use scenes to treat a single patch as a stereo rig... this has brought my system to its knees for the tones I'm going for. So I've gone back to use 4 seperate patches. It's good enough for now, but it does make me wonder whether more optimization needs to be done, or if there is some way to make the plug in multi-threaded... or if there's just something wrong with my config.
Also, my CPU has 4 physical cores and 8 logical ones. Cantabile and Reaper identified this as 8 cores, and defaulted to running multi-threaded with 8 cores. However, because real-time processing is critical for audio, this actually resulted in more clicks and pops. Manually setting this to the number of physical cores (in my case 4), solved the problem.
It seems to happen when I'm running Helix Native and also VLC running a video/audio track which I'm following. Would that cause this issue? I don't seem to have the problem if I run a single instance of Helix Native but if I introduce other work on the system we seem to run into this. Any advice?
And Using helix hardware is not why i bough native too. Clearly there is an issue somewhere. It kind of ruin the fun a bit. Even with no guitar plugged, high gain patches always have a lot of static noise.
Does your computer have plenty of horsepower? If its lacking, even increasing the buffers won't help with crackling if you're overloading your system. Try a fresh DAW project with just a single Helix Native track and nothing else running on your computer, with I/O buffer set to max. Does the crackling go away or diminish?
I kind off solved it, I still think it is more noisy than the hardware, but the main problem is that i was coming in way too hot. When direct in, i was using the old rule of play hard and use the input until it is not clipping. But when your record raw track from helix, you realise how quiet the levels are, so i matched that. there is still a lot of static but when i add a noise gate at the start it is all fine.
There are more ways for noise to get introduced into the signal using plug-ins/DAW than using Helix hardware. On top of that (as you have discovered) you have more places where you have to make sure you're not introducing digital clipping or overloads.
Just installed Native tonight. Using in Garageband. The noise on high gain amps is unbearable. Matchstick Jump isn't usable. I see the noise on the mains, not input, so I don't think it's anything before the computer. Computer is an iMac with an i7 and 32GB of memory. Plenty of horsepower and most cores not even working much.
Same issue here, no answers for any of us it seems like. Running 2 FireFace 800's through adapters, and independently, they both work fine. But the second you try to use them as an aggregate audio device, it just crackles and sounds demonic.
c01484d022