Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Search the Community

Showing results for tags 'merge'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Support
    • Multi-Effects Units
    • Variax Instruments
    • Amplifiers
    • Computer Based Recording
    • Live Sound
    • Pedals/Controllers
    • Dream Rig - Line 6 Product Integration
  • General Discussion
    • Tone Discussion
    • Line 6 Lounge

Categories

  • General FAQ
    • Operating System-specific Information
  • Tutorial Videos
  • Effects/Controllers
    • HELIX/HX
    • DL4 MkII Stompbox Modeler
    • M5
    • FBV Controllers (MKII / 3)
  • Amplifiers
    • Catalyst
    • Powercab
    • Spider V
  • POD
    • POD Go
    • POD Express
    • Pocket POD
  • Guitars
    • JTV / Shuriken / Variax Standard / Workbench HD
  • Relay G10 Digital Wireless
  • Recording
    • Helix Native
    • Metallurgy
    • Echo Farm/Amp Farm
    • POD Farm 1/2.0/2.5
    • Computer Audio Set Up and Troubleshooting
  • Legacy Products
    • POD
    • Amps
    • 1st Gen Variax Guitars / Bass / Workbench
    • Effects and Controllers
    • AMPLIFi Series
    • Live Sound
    • Digital Wireless
    • Mobile Products
    • POD Studio / Tone Port / GuitarPort
    • Software
    • Dream Rig

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Registered Products

Found 5 results

  1. hi guys first of all I'd like to let you know that I read all the threads I found about this same subject and didn't find the complete answers, so I decided to run some tests myself (like I did on the POD HD years ago) and to create a new thread with my results (I'm on FW 2.60 by the way) ok, I'll start from the end results, so that those who just need to have a quick answer can read it immediatly, then I'll give some deeper explanations the main point of this post is: the moment you create a split/merge routing configuration by dragging down a block you get a level change: after the merge block, with all bypassed fx: with split A/B and Y you get +3dB at the output sum with split crossover you get -3dB at the output sum BUT each path by itself gets attenuated by -3dB so if you use the split A/B to switch between sounds, each of those sounds is -3dB qiueter than the same fx/amp with the same settings in a non-splitted path the good news are that the level changes do not actually occur at the split, so the two paths are both an exact copy of the signal before the split, instead the change occurs at the merge block so the right solution is to act on the merge mixer faders --- why? and why those values? • well to answer, I need to clarify two things that I've read someone get wrong and mixed up in other threads 1) when you sum two identical signals in a circuit either analog or digital you get +6dB boost (voltage sum) 2) when you send a signal to a physical speaker and then send the same identical signal also to another identical speaker you get +3dB (acoustic power sum) this is math and physics, not an opinion now, this second point is one of the reasons why something called "pan law" exists: as we said, when you have a mono signal going to two speakers (so the pan knob on a mixer is at the center position) you get +3dB of sound pressure so mixer designers in some cases decided to pad the center position of the pan knob by -3dB, gradually returning to unity gain at the extremes (in some other cases they may use -2.5, -4.5 or -6dB: the actual effect of the pan law depends on the coherence/incoherence of the signals, on speaker placement, on listening conditions, and also on mixing taste I would say, so the designers have to make an assumption and take a plunge, I don't have time to enter into this now, sorry). • now back to the Helix: you have an empty "new preset" patch you have a signal going through path 1 (I used various sine waves and pink noise) you add a gain block at 0dB (if you want you can even bypass it) => nothing changes you drag the block down creating a double path => you get +3dB at the output sum so, what's going on? - the A/B or Y split duplicates the signal to two paths, so each of them carries the same identical signal which goes to a merge block mixer channel, then the two get summed together... so you should get +6dB, but... ... since the pans in the mixer have a -3dB pan law you only get +3dB - the crossover does not duplicate the signal but splits it in two frequency bands, if you sum those two filtered signals you get the exact same signal you had before, so no +6dB boost here, but there is still the pan law, so you get the -3dB - but, as I wrote before, each path by itself gets attenuated by -3dB because of the pan law, so if you use the split A/B to switch between sounds, each of those sounds is -3dB qiueter than the same fx/amp with the same settings in a non-splitted path • please note that these are not theories or speculations, I've tested and measured thoroughly every configuration and I'm sure the Helix routing works like that • all this behaviours occur identically to mono or stereo signals, remember that all the lines representing signal flow in the Helix display are always "double conductor cables" so either stereo or dual-mono (stereo = they carry two different signals; dual-mono = they carry two identical signals) this point could be deepened a lot but I don't have time for this now --- some other considerations: • if for example you open the pan pots of the merge mixer to the extreme L and R, the pan law attenuation does not apply and the level goes back to unity BUT this is not a solution, because if you run in stereo you only get the left from path 1A and the right from path 1B • I'd like to warn you of potential problems I found with the parameters inside the split blocks I) the split A/B "route to" parameter is a balance control, not a crossfader, so moving it to the left attenuates the signal going into B while not touching the signal going into A and viceversa; so it is appropriate to use that parameter to switch from A to B but not too much to find a mix of A with B for 3 reasons: 1- as I said you only have control over the attenuation of one of the two signals you are mixing 2- at center (even position) you have more level than any other position because the two signals are at full level, so the judgement on which is the best mix is compromised for psychoacoustic reasons 3- worst of all: if the blocks in the paths are amps or distortion boxes or compressors, as long as you are not in A100, "even" or B100 positions, you are sending an attenuated signal to one of them, changing its sound and not only its level II) the split Y "Balance A" and "Balance B" parameters (added in fw 2.10 so not covered in the manual) work like this: the stereo or dual mono signal goes into the split, it is duplicated to path A and B and on each of those you can control the balance between left and right, those balance control also have a pan law but different from the merge mixer block pans ! in this case it's unity at center and +3dB at sides ! (I think the reason for this is to avoid an attenuation to the splitted signals at default settings) so if for example you use 2 amps in the paths do not use these parameters or the two amps will receive a different level than if the balance is at center. --- • to finish I'll add two other Helix Routing measurements I found during my tests: - the pan block is actually a balance control with a pan law equal to that applied in the split Y block: at center it's at unity gain, going to the left attenuates the right up to minus infinite and adds +3dB to the left (and viceversa) - unlike the POD HD500 the fx sends / returns on the Helix are all at unity gain levels (+/-0.3dB), thanks Line 6 ! --- thanks for reading, I hope to have been helpful bye Lorenzo
  2. Hello, I am in need of help. I am a new Helix owner. I need to be able to merge path B (mic) after effects up to path A (guitar) just before the looper. I have been deeply covering the online manual for this (page 17) and it says how to MOVE a split or merge block, but not how to Create one... Once I learn how to do this, I also want to find out if I can change this with a snapshot so, I can choose when I'm looping to record guitar and vocals or just guitar. Any suggestions? ~Rob
  3. I know the "right" answer for this is snapshots, but I don't want to use snapshots for this preset. I'm setting up a distortion block but want to add a clean blend to it, so I'm moving it to path B and using the Split and Mixer blocks that result on path A to blend in my clean sound. The thing is I don't really want it evenly blended, but rather slightly less of the clean sound compared to 0dB as defaults in the merge block. So I thought I could control the parameter for the A level in the merge block to be controlled by the same switch that engages the distortion block. I would think to accomplish this I set the control to the switch and then on the dirt block engage set the lower level and on the dirt block disengage the 0dB level. But assigning the merge block to the footswitch sets the levels to -60dB and +12dB when I click the switch back and forth. Definitely not what I would ever want. Can I set a min/max level on the merge mixer parameter I'm trying to control, since clearly it doesn't remember the levels I had it set at for the on/off states of the switch? This is the first time I've run into a parameter control issue on the Helix, and I know I could solve it with snapshots, but I want this to be a simple pedal on/off scenario. This whole issue could/should be fixed by adding a blend parameter to every effect on the unit (purity to the original effects controls be dammed).
  4. I've asked in the Facebook group and read some threads over here about the topic but some things about it still confuses me, so here we go again. Is there any panning law by default in the Helix while using Y splits or AB splits followed by a merge block? At what dB? Is the signal lowered att the split or at the merge block? I'm using a patch for my bass that has a y split in the beginning with some distortion blocks on path 1b, and no blocks on path 1a, followed by a merge block, some comp, mod and lastly a single amp block and a cab. I use this setup to "blend" the distortions with my clean bass tone before hiting the amp block. But something sounds "off" while doing this compared to just putting all the blocks on a single path. I do understand how panning does work and that merging two mono signals results in a boost of 3db, two stereo signals in a 6 db boost, etc. Allthough i compensate by cutting the output block of the merge block I still end up by a signal that sounds either slightly boosted or with to little gain hitting the amp block. The settup that seem to be working the best is to use a Y split with L+R hard panned to either side and then both panned center at the merge block + a -3db compensation at the merge blocks output gain. Even by doing this you can clearly hear a difference when moving fxs like a comp block before or after the split+merge. Am I missing something? I do not have the dist blocks in path 1b on all the time and I want my blocks to get the same amount of signal after the split/merge as if I wasn't usinging parallel paths. Is this even possible?
  5. Hey. I have a simple question i'd like to: connect for example a piano/keyboard with midi cable to pod hd500x midi IN then connect Pod's midi out/thru to pc with midi/usb interface then use pod hd switches to control ableton functions via midi, and at the same time control my vst virtual instrument with keyboard. so: is it possible to use pod as midi controller and send midi notes from piano to pc at the same time (with one usb/midi interface)? Sorry for my english (polish native) Thanks in advance Kacper
×
×
  • Create New...