requietus666

on command center - right click "instant" item and you have your copy paste options

you're doing it right, on helix: instant msg - set program number, save preset on triple play: set "midi foot input" to helix it works

for example, I sorted out my volume drop problems with visual metering, like american audio dbm, just connect one of the sends to dbm, and put send block wherever in the chain and you have visual cue approx what volume you're at

not really a solution to the problem, but a workaround

no, you can't. there's only 16 knobs (variable), 16 switches (on off) and master input, master output, master bypass

this should probably be under native threads, anyway I too find Poulin amps the best amp sims out there, and initially I have to confess I couldn't quite match them with Helix, but after some months of tweaking I managed to get somewhat better tones, not to mention the convenience of having my sound wherever I bring my helix I have found that helix input has far more better dynamic range which is more suitable for guitar sound and this makes a HUGE difference. Since getting Helix I don't run my amp sims on focusrite saffire using its input, only spdif

for practicing at home I use phones or jacks out to homemade frfr at rehearsals and live - xlr out for recording - spdif to saffire (yes, the same aforementioned latency thing)

maybe angry shaman - angry chair by alice in chains ?

observation: Interestingly, predominantly in fractal forums folks praise how much better axfx sounds compared to helix, but on helix forums folks say they're both great :-)

This is indeed very nice idea to bring all FS related info into one screen Yes, you can edit scribble strip names in editor in bypass assign, command assign and (if you use FSs for MIDI) command center

WAV files have meta tags, and this is what comes into play, because, from what I have found, Helix floor (and Native, too) reads meta tags first and filenames afterwards. For example, if You import your regular IR "abcd.wav" from redwirez or whatever, you place it on 76 position. Then you export this IR to hard drive, and suddenly Helix inserts meta tags into filename (abcd into title tag), thus, if you rename your exported IR to "76abcd.wav", the meta tags will still show IR name "abcd" as it was on Helix device when exporting. It's not a major inconvenience but at first I was surprised because IR bundles come without meta tags. For many years now I use http://www.mp3tag.de/en, so I simply remove tags from IR which have been exported from Helix to keep consistency. One little wasted step.

at first, I kept Digitech Drop but eventually sold; it did way too much coloring and latency too perceptible

affirmative. you can output to 3/4 other option is to use native on tripleplay insert to get a blend with mags

oh, geez, totally missed that ! Thanks

not really bugs but little annoyances with helix: 1) program change message is sent on patch change. There's instant messages for that, I suppose, anyway, it should be up to user whether to send pc or not; 2) mouse scrollwheel behavior inconsistent in helix editor. On fx block parameters page mouse scrollwheel as vertical scroll, but on global EQ page it changes values of parameters underneath. 3) When you enter tuner mode, the foot tap is actually recorded and remembered, but last press should be dismissed. I've many times accidentally changed tempo just by entering and exiting tuner mode. Design-wise, I think it would be nice to have an option to swap TAP and MODE buttons, because now MODE button is a little more difficult to reach in a live situation, but we tune mostly while idle, don't we ? Similar thing applies to preset/bank/snapshot up/down buttons, I'd like to see an option to remove them completely in live situation, it's too easy to accidentally press down footswitch. What do the priests say about this ? Is it doable at all in helix architecture ?

PC here. TriplePlay comes in 32 and 64 bit versions. Make sure you run x64 version because Native is only x64. oh wait, mac... I am sorry.

I too own TriplePlay and I can say while it is compatible (if compatible means vst plugin reads and loads), it is veeeery unstable. I could easily make TriplePlay crash with busier Native patches (imported from Helix Floor or even made from scratch). And yes, since 1.4 TP is somewhat on new level, very improved

Thomann ships to Oz, but it's eur50

you can convert to spdif, but only an as output from helix lt eg, https://www.thomann.de/gb/pro_snake_aes_ebu_spdif_cable_3.htm

It's doable. If You're unhappy with Helix cab sim - In Helix set path 1 output to usb3/4, path 2 input to usb5/6. In Amplitube set input to usb3/4 and output to usb 5/6. This way you have Helix path 1 before amplitube and path 2 after it. First, there will be some latency, but second, Helix impulse loader gives you just as much freedom. Go to Ownhammer website, they have free demos, and it's a marvelous thing to start with.

Likewise many might find Native unattractive (or not "ages ahead" of competition) with, say, scarlett pres

I (probably) solved my incovenience with routing spdif from helix to saffire, this way I can use helix preamp and saffire latency advantage.

hi all, I've been using focusrite saffire pro 14 for years now, it's a brilliant piece of equipment, stable drivers, pristine sound etc. I've done all kinds of stuff with it, daw recording, apmsims. When I got Helix and used it with my usual amp sims for the first time, I was blown away. The sound was SO MUCH clearer with Helix !! And now I am guessing if I was living in a bubble. Yes, ampsims with Saffire had some minor hiss but it was somewhat tolerable (yet I wouldn't gone live with that sound), but with Helix I can definitely bypass all the gates and denoizers whatsoever. What do You think, is it really that big of a difference between these two, or might be something been wrong with my Saffire all along ? Yes, it's firewire, I am using fw to pci card, a cheap one, not the texasinstruments. Could it do much difference if changed ? What else can You suggest ? I am more than happy with Helix, it becomes really a centerpiece of my workflow, but I don't want to get rid of my Saffire, too, because it performs in DAW better than Helix and daw latency is much lower without artifacts. It's WIndows 8.1 machine x64, i5.

thx for the hints, very helpful. these two problems are solved. with boxiness, - I was using native64 thru savihost, which has only stereo input pairs. lame. as with dry signal being carried thru - it is some sort of bug with jBridge. I jbridged it and ran it in Cubase32, whose gui is the most pleasant for me from all. In reaper64, of course, there are no routing problems.

well, for some reason it doesn't, native sounds very boxy, can't match. global eqs disabled, etc etc... Also, this is another thing, I record a dry track - with native being on insert fx I get a dry sound along with native processed. when native output is turned to zero, still the dry track is present. and this is using different interface, too. I really want to like Native, but it doesn't come to me easy, first the crashes, now the eq things (still, triple play every 2nd or 3rd run says native64 is not plugin, occasionally on rescan adds, sometimes not)