Forum Replies Created

Viewing 15 posts - 1 through 15 (of 154 total)
  • Author
    Posts
  • #93516
    Profile photo of lightingman117
    lightingman117
    Participant

    Even basic Midi control of faders/mixes would be enough for backward compatibility IMO.

    #93513
    Profile photo of lightingman117
    lightingman117
    Participant

    Couldn’t agree more.

    FWIW, https://dev-core.org/mixing-station/ will work.

    I don’t have IOS backups though.

    #93504
    Profile photo of lightingman117
    lightingman117
    Participant

    I have long lamented the fact that both the Apple & Android APP stores don’t allow versioning of apps. I think it’s absurd, should be very easy to implement and very useful for specifc use-cases like ours to download past major versions.

    There are some workarounds:
    Mackie makes a completely new app for each release version they make, hilarious, but it works.
    Yamaha has backward compatibility as far back as V2.01 (tested myself, might be even further) from V4.00 mixpad software.

    For A&H:
    iOS – backup of iPad/Device with older version app
    iOS – jailbroken IOS & app store to sideload
    Android – Sideload APK from alternative websites (this works great). https://www.androidauthority.com/best-app-stores-936652/

    I wish A&H would at least host all firmware versions, offline app versions, and APK’s in an FTP for us. It would at least give us an official source to download from instead of APKMirror etc.

    #93433
    Profile photo of lightingman117
    lightingman117
    Participant

    Every setting is the same?

    Attachments:
    You must be logged in to view attached files.
    #93316
    Profile photo of lightingman117
    lightingman117
    Participant

    Create a new user called ‘broadcast’
    Give them permissions to edit mix 12 (or whatever it is) and whatever other things you want them to be able to do.

    Unfortunately, the permissions isn’t as granular as dLive and you can’t individually control which channels and processing the broadcast mixer can do.

    For instance, they might want to EQ a double patched kick drum and vocal mic for broadcast. Allowing access on the user profile to input processing will give them access to all of the channels, which will then be editing FOH.

    An alternative to a mix output would be to send USB audio from tie-lines to reaper or similar and do a mixdown in the computer for broadcast.

    #93144
    Profile photo of lightingman117
    lightingman117
    Participant

    +1 to all accounts

    Would love per ch direct out pick points instead of global.
    Was a lifesaver on M7CL with in-ears.

    Tie-lines for recording…

    #92390
    Profile photo of lightingman117
    lightingman117
    Participant

    +1
    Library button for this would be the perfect method 🙂

    (The fader layout screen is a bit full/busy already.)

    #91567
    Profile photo of lightingman117
    lightingman117
    Participant

    22fuzzi,

    While Keith gives us the official A&H answer I have successfully connected a SQ and dLive and they do see eachother’s clock.

    I have tested audio routing as well. And it works quite well. There is a caveat with skipping some input sockets on the dLive but it works.

    There’s a post I made in the FB dLive group with details.

    I don’t know how stable it is or if it will persist through different firmwares and I haven’t used it in a live situation; but it did work.

    #90373
    Profile photo of lightingman117
    lightingman117
    Participant

    Thanks, I did search. I also do go back and do the +1 for relevant threads. I also know some was already suggested.

    Simply making the Dev team easily able to add desired features to TFS.

    #90009
    Profile photo of lightingman117
    lightingman117
    Participant

    +1

    #88107
    Profile photo of lightingman117
    lightingman117
    Participant

    That’s interesting, my understanding is they have a dev team for each product.

    I kinda doubt that with the way things are implemented/deployed.

    #87813
    Profile photo of lightingman117
    lightingman117
    Participant

    Hah, okay that is funny. Why not the ability to select an aux too?

    Why not add PEQ while we’re at it?

    But in all seriousness, it would be nice to add the TB to the IO page that way we can get IP-DO & Busses into the TB input. [if possible]

    Just realized this is a 161×64 engine once you include the TB.

    #87812
    Profile photo of lightingman117
    lightingman117
    Participant

    +1

    My truncated list of improvements includes these:
    Midi Sel
    Midi Mix
    Midi softkey

    The problem is…which UI (director, surface, etc) do I send the command to?
    [Don’t want random midi softkey presses affecting all surface/UI/Director instances on the network… (needs to be specific)]

    #87811
    Profile photo of lightingman117
    lightingman117
    Participant

    I’m confused, you can do this? [unless I’m mistaken at the pick point, but it should be post (after) faders]

    #87804
    Profile photo of lightingman117
    lightingman117
    Participant

    Beyond that, it would be really useful for something like the C1500 where you have only so many faders & layers & softkeys…

    Being able to add an input or output processing channel without having to put on a surface would be nice.

Viewing 15 posts - 1 through 15 (of 154 total)