bobthedog

Great news :)

In the EU you get two years by law anyway, in the UK up to 6: https://www.theguardian.com/money/2011/feb/05/how-long-electrical-goods-guaranteed

The only way you could possibly hear the unprocessed sound of your strings alongside the processed sound is that you are using the helix plugin as a send rather than an insert. Or you have the audio interface direct monitoring turned on outside of the DAW.

My bet is any problem will go away with the Scarlett, Focusrite know what they are doing.

I'm guessing they want you to prioritise the audio device driver rather than the front end app. In my opinion I would leave it on foreground. Nowadays there isn't much needed to get modern computers to handle audio correctly, users should make sure the processors are not being throttled back and also on windows use DPC checker to make sure that you haven't got any hardware drivers that are causing problems. http://www.thesycon.de/eng/latency_check.shtml The main thing is that some cheaper audio interfaces increase latency by using extra buffers, so you may think you are setting your buffer to 128 samples which would give you around 5ms in out latency (with a little extra for DAC/ADC times) while really the interface driver is adding another set of buffers that may be sticking it up to a noticeable 15ms, so the user drops the buffer size and then the driver or computer then cannot manage or the driver still uses the larger buffers and you still get latency. Also some interfaces then lie about their extra latency by hiding it, this can cause problems for the DAW where it is getting buffer under-runs on input and over-runs on output. Have you tried doing a test to see what the real latency is by connecting a loop cable to your interface Out to In and sending some audio out of the DAW and re-recording it, then measure the difference in time between the two tracks. Does this match up with the figure that the DAW is reporting for latency? Make sure that any delay/latency compensation in the DAW is turned off when you do this.

Well there is a big difference between flight simulators and audio software. A flight simulator is working to a different time slice than audio software. So lets say you flight simulator is trying to hit 60 frames per second it needs to create a new frame of data around every 16.66 miliseconds in order for you to get a smooth experience. No dropped frames, no frame rate changes etc. The physics stuff may be running at a much faster rate but it still feeds into the visual feedback time slice. With audio software lets say you are running at 48K with a 128 sample buffer, you have around 1.33 milliseconds to give the user a smooth experience. No crackles, no overloads etc. Also with audio unlike a flight simulator you have a complex changing directed graph of jobs that need processing as users use sends, returns, buses etc. So certain jobs need processing before other jobs as those jobs rely on their output data and possibly on the output data of other jobs and of course other jobs rely on them. Now I'm not saying that the advise on the sweet water site is correct, I'm just saying that flight sims/audiosoftware stress the processing/cache system on the CPU in very different ways.

Logic pro x 12 core mac pro with a Apollo Duo interface. 44.1K Note for pc owners: cpu readings on macs are % of a logical core, so this machine has 24 logical cores and a max cpu reading of 2400% So 50% cpu on a 4 core mac would read as 6.25% on a pc and on a 12 core mac would read 2% on a pc. Logic Pro 1 audio track record enabled 5.4% Add helix with default patch Factory 1/01A 32 buffer = 54.9% 64 buffer = 35.8% 128 buffer = 35.5% 256 buffer = 35.2% 512 buffer = 35.7% 1024 buffer = 34.4% 8 tracks with default 01A patch, record enabled on all tracks 32 buffer = 248,5% 64 buffer = 219.4% 128 buffer = 198.3% 256 buffer = 188.2% 512 buffer = 181.8% 1024 buffer = 179.7% At 32 buffer (4 ms in to out) I get no crackles at all. For playback test I set the buffer to 128 (8.8 ms in to out) and duplicated the tracks until I heard crackles, here it managed 37 tracks with cpu of 900% The maximum tracks I could get at 1024 buffer was 45 tracks with 1017% cpu. So I don’t think the cpu is that bad, I am sure they could improve it a bit but it isn’t causing this machine any problems with that patch. Does anyone have a problem patch from the factory bank I could test?

I agree totally, the UI is a nightmare on my 30 inch monitor. You should not have to scroll a windows to get to all the parameters. The block type/subtype should be a pull down, maybe on right click on the block then we get all that space back. Preset choosing should be separate, who do we need that taking up space. Maybe the developers should look at some other plugins to see how they do things! The one thing the editor and the plugin make me realise is just how good the UI on the helix itself is!

The sound is absolutely fine, it sounds exactly the same as my helix. The interface is another matter, tiny on my monitor and I have to scroll a little window to get at all the parameters of the modules, and the scroll wheel also changes the value of parameters as well as scrolling depending on where the mouse is. Absolute madness! I thought the Helix editor UI was pretty bad but at least you could size it, having an un-sizeable version is really painful.

Hi Guys, Can anyone resize the plugin window? It's really small on my system. Cheers Andy

I can't just go looking anywhere else when I have been looking at this thread every day for months :)

The update procedure, I have got to the point where I won't even update unless there is a major version change, that to me shows there is something seriously wrong. The pitch and synth stuff is pretty bad. The tuner could use some improvement. Undo would be good for when the joystick destroys your careful work.

Reading the original post all the bass player is saying though is that the monitoring is not good for the band/him as the PA speakers are in front of him pointing away. There is some validity in this but does your synth line and vocals just go through the PA as well, can he hear them or is he just bothered about the guitar? I would think a simple solution would be to have a monitoring setup firing back towards the band, it's sort of basic.

It's all to do with the guitar fretboard being imperfect and not being able to accurately do equal temperament. You can get necks that help: http://www.guyguitars.com/truetemperament/eng/tt_whichtemp.html Or an autotune system: http://www.autotuneforguitar.com

Well as a software developer I have to argue this point. If I was to gain access to your bank and take all your money from your account should you still be so happy that it was only numbers and not physical notes I was stealing? The cost of developing a piece of software is planned against a projected number of sales, if those sales are reduced by people stealing a copy you as a developer are loosing an actual item, this item was a projected sale which was used to fund the development cost. It isn't just manufacturing costs that count towards real product cost.

Mmm, you should see mine! Mostly one or two amp blocks, one or two cabs/IRs and some fx loops.

In the UK I think you get a basic 2 year warranty anyway from EU Law, also the Sales of goods act can nudge date this further depending on the fault. Edit, just looked sales of goods act is 6 years as long as you can prove it isn't fair wear and tear.

As Line 6 have been mad enough to use VST3 instead of VST2 I guess there is a very small chance bordering on the very improbable.

"Lazy" - People that can't be bothered to read long posts.

For me the interface on the unit is very good, at the moment there is no way I would use the clunky software editor. I am hoping the Native editor works a bit better though then the Helix could go on the floor where it belongs rather than on the desk!

I must admit I would rather pay $100 than $199!

Day off today then ;)

how come no one posted anything here yesterday?

Everything is a circle, or a sine wave over time. Nothing lasts and everything lasts. I wouldn't worry.

Thats because the code in Guitar Rig and Amplitude isn't as good as the helix code, it has nothing to do with the processor it is running on.