|
|||||||
![]() |
|
|
Thread Tools |
|
|
#1 |
|
Tail Razer
Join Date: Jun 2005
Location: Bernyurass, AZ - USA
Posts: 4,027
Rep Power: 0 ![]() ![]() |
Output order of Crossover plugin...
I assume there is some logical reason for how the output pins on the various crossover plugins (including Max M.'s too):
L1 or Lo L H1 or Hi L L2 or Lo R H2 or Hi R I thought that they appear in the order presented in the Dane code, so I wonder why they are all set up this way - its kind of a PITA to connect them, for how I am using them anyway... but I have to think theres *some* logical reason for this order... I just can't see what that would be? Anyone? |
|
|
|
|
|
#2 |
|
h/h member-shmember
Join Date: Dec 2002
Location: Evil Empire
Posts: 2,639
Rep Power: 69 ![]() ![]() ![]() ![]() ![]() ![]() |
>but I have to think theres *some* logical reason for this order...
Well, probably it's just to "reflect" inputs (e.g. lefts first, then rights) I suspect this is just because people who wrote it, never used it themselves (in a way it is typically used) - hense they were not able to see how weird a connection is. Your point makes sense. |
|
|
|
|
|
#3 |
|
DriverHeaven Newbie
Join Date: Oct 2006
Posts: 4
Rep Power: 0 ![]() |
I would prefer for it to ordered the other way well
H1 H2 L1 L2 How hard is it to change the code? |
|
|
|
|
|
|
|
|
Tail Razer
Join Date: Jun 2005
Location: Bernyurass, AZ - USA
Posts: 4,027
Rep Power: 0 ![]() ![]() |
Quote:
but, I have to think theres an explanation - maybe it boils down to using least registers in dane... ?? thats the only thing I can come up with anyway.. |
|
|
|
|
|
|
#5 | |
|
HardwareHeaven Extreme Member
Join Date: Jan 2005
Posts: 5,563
Rep Power: 62 ![]() ![]() ![]() ![]() ![]() ![]() |
Quote:
i.e. Some plugins are made upon request, by people who may never actually need to use the plugin themselves... |
|
|
|
|
|
|
|
||
|
Tail Razer
Join Date: Jun 2005
Location: Bernyurass, AZ - USA
Posts: 4,027
Rep Power: 0 ![]() ![]() |
Quote:
Quote:
I just thought it was opportunity to learn something about their intended use or something... |
||
|
|
|
|
|
#7 |
|
HardwareHeaven Extreme Member
Join Date: Jan 2005
Posts: 5,563
Rep Power: 62 ![]() ![]() ![]() ![]() ![]() ![]() |
|
|
|
|
|
|
#8 |
|
DriverHeaven Newbie
Join Date: Oct 2006
Posts: 4
Rep Power: 0 ![]() |
Both orders do make sense. Just for my application (which is the most important) H1, H2, L1,L2 makes more sense.
Has anyone kindly asked the author to release another version? Or is there an alternative? |
|
|
|
|
|
#9 |
|
HardwareHeaven Extreme Member
Join Date: Jan 2005
Posts: 5,563
Rep Power: 62 ![]() ![]() ![]() ![]() ![]() ![]() |
|
|
|
|
|
|
#10 |
|
h/h member-shmember
Join Date: Dec 2002
Location: Evil Empire
Posts: 2,639
Rep Power: 69 ![]() ![]() ![]() ![]() ![]() ![]() |
lol
|
|
|
|
|
|
|
|
Tail Razer
Join Date: Jun 2005
Location: Bernyurass, AZ - USA
Posts: 4,027
Rep Power: 0 ![]() ![]() |
Doh!
I take it you connect the HIGHs to say REARS outputs (better codec) and LOWS to FRONT outputs on a SBLive then... And, I guess using a stereo pair to adjust Lows vs Highs volumes in DSP... I knew there had to be some logic behind it somewhere. |
|
|
|
|
|
#12 |
|
DriverHeaven Newbie
Join Date: Oct 2006
Posts: 4
Rep Power: 0 ![]() |
Actually... I have a Audigy 2 ZS that I use for my carputer. I use the DSP as an active crossover and use one output for the highs, one for the lows then one more for the rear. I did have a SBLive! at one point when I lost my DSP virginity so I did use that logic. It kinda just carried over to the Audigy.
I guess I could use the plug in the way it is, with out kriscrossing the outputs in the DSP, but I dunno. That just doesn't seem right to me.... and I run a dictatorship so what I say goes. Unless other people are involved. I just want to let it be known that I am more than grateful to all the folks that coded the kXproject drivers and the people who put out the plug in that make it amazing. Also that I am in no way complaining about the plug in as it stands... publicly... just showing and interest as others have to have the plug in outputs reordered to make our lives a little easier |
|
|
|
|
|
#13 |
|
HardwareHeaven Extreme Member
Join Date: Jan 2005
Posts: 5,563
Rep Power: 62 ![]() ![]() ![]() ![]() ![]() ![]() |
But how hard is it really, to do the cross-connections in the DSP... It is only 4 pins after all. Depending on how it is to be used, one person might want LHLH (i.e. current layout), another might prefer HLHL, another LLHH, and then there is HHLL (and there are some less likely orderings too).
|
|
|
|
|
|
#14 |
|
DriverHeaven Newbie
Join Date: Oct 2006
Posts: 4
Rep Power: 0 ![]() |
Well it is a little tricker than you're probably thinking because I don't have a mouse in my car and have to do it via touchscreen. I do use the large connector setting, but it's still a little tough. The other problem is that it auto connects the inputs below. So when I connect my my first Low pass output it connect the second hi and low pass outputs to the inputs below, knocking off whatever I have connected there. I'm not sure if that really makes sense, but yeah.
In summary, it's really not that big of a deal at all. I've been working with it for over a year now with no real issue. I hardly ever make changes to the actual DSP. Even if I do, it most likely won't be to the cross over portion near the end of the chain. Other people wanting different configurations makes me think that this should be configurable like the k2lt. That would be truly amazing. |
|
|
|
|
|
#15 |
|
HardwareHeaven Extreme Member
Join Date: Jan 2005
Posts: 5,563
Rep Power: 62 ![]() ![]() ![]() ![]() ![]() ![]() |
No wireless NIC to do it remotely, eh? j/k
![]() BTW: Holding down the ALT key when making the connections, keeps it from doing the auto-connecting thing (although I am not sure how easy that would be to do using a touch screen either). |
|
|
|
|
|
#16 |
|
HardwareHeaven Lover
Join Date: Dec 2007
Posts: 221
Rep Power: 40 ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
|
|
|
|
![]() |
| Thread Tools | |
|
|