Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #93369
    Profile photo of jay.mostacho
    jay.mostacho
    Participant

    Unless I’m mistaken, non of you who have commented on this thread so far are an exec, a PM, in R&D, or eng for A&H. IMO the comments about what a corporation might do/should do/wont do or what is too expensive or not really shouldn’t be up for discussion- because we really don’t know and all is pure speculation.

    The point of these open forums is to relay info from end users and see if any steam builds in the discussions- A&H will research the finances, marketing & what not and therefore aren’t relevant to the discussion. The first comments on every one of these suggestions seems to be to try to shoot the idea down first, explain there’s already an arduous path available for the suggestion, or use corporate speculation when those arguments are exhausted. Maybe it would be more helpful if each participant tried seeing if it’s something that would actually be a value add or helpful to them first. Comment to “yes and” the idea or click like if it’s a flat out “yes”. Move on if it’s not. Again, A&H will seek out the threads with most likes/discussion and would help the better ideas float to the top.

    So back to the actual topic, no one can see a use for an 8 or 12 input only 1RU device? It will only make your lives miserable in the field or in your facilities? Buying a 16×8 i/o box suits you just well for an extra 6 inputs in a remote location? Something that is roughly $1300 US and 4RU vs something around $1100 US and 1RU?

    Maybe this idea is a bad one and I’m fine with that but not one participant yet has argued against it’s merits.

    #93364
    Profile photo of jay.mostacho
    jay.mostacho
    Participant

    Wow- clearly this picture needs to be on the main page of this suggestions tab to warn anyone with potential ideas. Just because it doesn’t make sense in your unique situation doesn’t make it a waste of development time or causal to shoot it down. The form factor exists, the pre-amps exist- it’s code and fitting it all in 1RU. Seriously, it’s like taking the AR804 and upgrading it to 96k for crying out loud. I mean A&H did it for the AB168.

    The excuse of “someone has to pay” is moot since someone always has to pay for anything- and as a sales guy, I’m saying there are plenty of people that will pay for it. But feel free to keep using your wireless argument that “everyone should have AXIENT D/EM 6000 Dante” against the 5 reasons I listed above where my suggestion would be useful/helpful in both production and installed environments.

    Attachments:
    You must be logged in to view attached files.
    #93359
    Profile photo of jay.mostacho
    jay.mostacho
    Participant

    Thanks guys but this is the “Feature Suggestions” section. I’m not looking for “how to’s”- very familiar with all the i/o and cards available to “make it work”. I’m merely making a suggestion for a 1RU INPUT ONLY box like that of the DXO12. Kinda like why you don’t only have a hammer in the tool box. Sometimes you don’t have the rack space and/or don’t need the extra i/o. Before the DXO12 there were AES cards, DX32, on board AES/analog outputs. Someone had a brilliant idea and now I’m selling DXO12’s for amp racks and WIEM racks- serves a great purpose. I can see the input version going in keyboard racks, wireless racks, playback racks, racks where you just need a few more inputs and not 16. Also, when going into house of worship/performance art venue and you are only upgrading the console system and you have to work with whatever input legacy equipment they may have that isn’t Dante compatible.

    Dropping in a 168 or 4816 or even a DX32 in every situation is just egregious from an integration perspective- both in cost and in function.

    Cheers!

Viewing 3 posts - 1 through 3 (of 3 total)