Forum Replies Created

Viewing 15 posts - 46 through 60 (of 540 total)
  • Author
    Posts
  • #57279
    Profile photo of Stix
    Stix
    Participant

    If you mean INPUT monitoring to your DAW then yes you u should be able to do that ok if your DAW supports that, or you could use other software as you mentioned just for monitoring. Dante Via might be worth looking at so you can send Dante monitor outputs to your computers sound card etc.

    #57275
    Profile photo of Stix
    Stix
    Participant

    YES YES YES! These are all great suggestions and all on my wish list also! So consider this a +1 for all!

    #57274
    Profile photo of Stix
    Stix
    Participant

    +1 for this!

    Also need ability to Insert a scene, and to COPY a scene TO MANY! This was always a bit of a pain on iLive and appears worse in Director as it’s paste one scene at a time at the moment by the looks. This is required especially for Theatre use to pre set many blank scenes with recall filter settings pre stored ready for “save” to be used. Either that or some other way to apply preconfigured recall filter settings to many scenes at once.

    #57246
    Profile photo of Stix
    Stix
    Participant

    OK Weird – just tried that on my Mac and it works fine – just can’t get it to work on my PC. Windows 7, Touch screen Acer all in one.

    #57096
    Profile photo of Stix
    Stix
    Participant

    Not sure but one option would be to use a Matrox Dual head to go external video card as the Mac would see that as one monitor.

    #54141
    Profile photo of Stix
    Stix
    Participant

    Just on a side topic – you say you are wanting to use the QU for additional inputs – are you using all 64 iLive DSP channels? What mix rack are you using? I ask because if you require more input channels then perhaps you could look at sub hiring another mix rack and linking them in extended or dual rack mode for up to 128 channels all within the iLive framework and avoid trying to get two different boards scenes to talk nicely?
    Just a thought.

    #54122
    Profile photo of Stix
    Stix
    Participant

    You may get more than you bargain on if you link them together. If the midi specs are similar on QU to the iLive then perhaps faders, mutes, pans etc might also remote operate so you may need to filter or convert the midi data to just contain scene commands. Checking the Midi documentation for both desks might be a good starting point.

    #53999
    Profile photo of Stix
    Stix
    Participant

    5. In PFL section, you should choose what signal would you like to hear instead of always listen to Main. Maybe you choose to hear an Aux or a Matrix.

    And I think you mean – “when PFL is cleared or off”. Good idea – and also do that on the iLive! Most of the time I’m feeding speakers from Groups to Matrix sends and almost nothing goes through the main L/R busses except FX

    #53331
    Profile photo of Stix
    Stix
    Participant

    Early iLive firmware had meters working on the DCA masters – then some people who couldn’t get their head around that complained so A&H got rid of it to avoid confusion. Personally I really liked the feature and would prefer it back! Or a user option for it?

    #52588
    Profile photo of Stix
    Stix
    Participant

    Logic always uses output 1-2 for its main stereo out/ solo buss etc. This is a pain so you have to work around it. If you are using Dante then you can repatch there.
    I’m a Logic fan but quick flexible patching is something it sucks at! If you are just using for virtual soundcheck then other programs work better such as Tracks Live by Waves or Reaper and these are also free or very cheap!

    #52382
    Profile photo of Stix
    Stix
    Participant

    To get to scenes above 128 you may need to send two command messages – first a Bank Change value “01”, then the Program Change. Leave the ID the same and stay on Channel 1
    I don’t have a Pro 2 but look in the program Change drop down for Bank Change which is Controller 0. A value of 01 = bank two (Scenes above 128), then also send the program change.

    This reference from another site might be helpful:
    We need to use 2 messages to contain the bank number because, due to MIDI’s design, it’s not possible to transmit a value greater than 128 in just one controller message. Remember that a bank number can go as high as 16,384, and you need 2 MIDI controller messages to send such a large value. But, since most modules do not have more than 128 banks anyway, these modules typically only use the MSB message (ie, controller number 0) to select bank, and ignore any LSB message (ie, controller number 32).

    B0 00 01 Switch to bank 2 (NOTE: only the MSB message needed)
    C0 02 Switch to the third patch in this bank
    The patch doesn’t actually change until the module receives the Program Change message. The Bank Select message(s) must precede the Program Change message. Otherwise, the module would select the third patch in whatever bank the module was currently set to. (In other words, when the module receives Bank Select messages, it doesn’t change any patches. Rather, it simply notes what the “current bank” is, and any subsequent Program Change messages will switch to patches within that bank.

    What this also means for scene recalls is that ideally you need to send Bank Select message before every individual Program Change even to select patches from bank 1 (scenes 1-128). Otherwise the module (mixer) will assume it is still in the last selected bank – if that was Bank 2 then a program change only message would recall a scene above 128!

    #51782
    Profile photo of Stix
    Stix
    Participant

    Did the latest show scene contain everything – ie was it a “store all” scene? If it had been edited to contain less information or wasn’t a store all then that could explain your situation. Also – when was the last time you actually “saved” your show? You said you renamed it, and copied it to the USB but did you save it first? If not then when you load that back it will only recall the show as it was stored which may have been some time ago. Note that saving a “scene” is not actually stored anywhere permanent until the show that contains it is saved!

    #51590
    Profile photo of Stix
    Stix
    Participant

    The iLive can recall scenes via program change messages. This from the iLive Midi Manual:
    For Scene 1 to 128
    Scene SS 1 to 128 = 00 to 7F
    Select bank Recall Scene
    BN, 00, 00, CN, SS
    For Scene 129 to 250
    Scene SS 129 to 250 = 00 to 78
    Select bank Recall Scene
    BN, 00, 01, CN, SS

    The Pro 2 MIDI output can include a globally-enabled outgoing message that contains the recalled scene number and is sent out for all recalled scenes. Also, up to eight messages with user-selectable content are stored per scene and sent out whenever the scene is recalled. So you will need to program the Pro 2 to send the correct program change message for each scene recalled.

    Midas Pro 2 Scene Midi

    #50650
    Profile photo of Stix
    Stix
    Participant

    Luckily for me it was on a friends iPad that I discovered this issue. I wont upgrade until I know the A&H apps work on the new OS. STILL waiting for a Mac Yosmite fix for Editor! It almost seems that every time Apple does an OS upgrade it screws things up for A&H software!

    #50467
    Profile photo of Stix
    Stix
    Participant

    In my experience digital Clicks and pops are almost always related to clock sync issues or sometimes by sound card buffer settings being to high. Try increasing the buffer size.

Viewing 15 posts - 46 through 60 (of 540 total)