Forum Replies Created
-
AuthorPosts
-
2013/06/17 at 8:56 am #34245
Hi Pascal,
Thanks for your detailed reproduce procedure.
I have followed your procedure, and can confirm that I get the same problem. We shall investigate further and fix for the next firmware release.In addition…
On investigation it has been found that the error is all about adding an external input source to one of the mixes. If this external input source has no mic-pre (i.e. USB, SigGen, I/O Port In and Rack FX), then it is possible to induce this error. A yellow triangle in the south toolbar will appear, the source selection will need to be changed to clear this error.Antony Jackson
Software Manager
Allen & Heath Limited2013/06/14 at 11:17 am #34232Rick et al.
Further to what Andy has said, we have to make sure the Firmware is available before the app, as if we did it the other way around then people may update their iPads before the Firmware, and this would be irreversible.
Antony Jackson
Software Manager
Allen & Heath Limited2013/03/27 at 8:50 am #33582Hi Jörn,
I’ll put this onto the (long) feature request list. It doesn’t do this at present as it is not the only function of the select keys, the second function is to listen (via PFL), to the signal at this point in the signal path. Some engineers wish to have another screen (e.g. metering) on the touch screen at all times whilst mixing, and this is why we don’t switch to “Processing” by default.
Antony Jackson
Software Manager
Allen & Heath Limited2013/03/22 at 8:42 am #33535Yes, it will stop responding to this UDP when soft shutdown.
Antony Jackson
Software Manager
Allen & Heath Limited2013/03/21 at 8:52 am #33525Hi Jordan,
Yes the console will continue to reply to pings after the soft shutdown. You could use the “GLD Find” UDP message to be able to determine whether the console has been soft shutdown. This UDP message is sent to the console on port #51320(UDP) using the above string in the data. We use this as a broadcast send to find units on the local sub-net, but it should reply equally as well with a directed UDP message.
HTH.Antony Jackson
Software Manager
Allen & Heath Limited2013/03/21 at 8:25 am #33524This is getting very strange. We don’t know how DHCP would be getting enabled from a firmware update. The network settings live in a standard Ubuntu file /etc/network/interfaces, this file should not be touched during a firmware update. What is more, for it to change to DHCP it would need to have a line in this file changed from “iface eth0 inet static” to “iface eth0 inet dhcp”, so as you can see it is not just a simple boolean. We do many firmware updates here and have never had this issue, but too many of you are now reporting it to be coincidence, so if any of you experience this in the future could you give technical support detailed information, i.e. network settings prior to firmware update, firmware updating from and to, does it retain the setting for static setup, or does it change to some sort of default?
Antony Jackson
Software Manager
Allen & Heath Limited2013/03/20 at 9:05 am #33518Hi Chris,
The V1.11 is a standalone version and you can update from any previous version to V1.11.
Antony Jackson
Software Manager
Allen & Heath Limited2013/03/19 at 8:48 am #33501Hi Rick,
The release notes for V1.11 include what is new in V1.1.
Antony Jackson
Software Manager
Allen & Heath Limited2013/02/22 at 11:55 am #33198Hi Peta,
There is no iDR 8 /4 forum, so there is no better forum to post this on.
What version of software are you running? Current settings are only stored from V3.60 onwards. If you are running V3.60 or later, then check you are not recalling a preset on power-up that is overwriting the Input Patch Bay settings.
Regards,Antony Jackson
Software Manager
Allen & Heath Limited2013/02/12 at 9:00 am #33090I’ve just measured the boot time of the GLD, using V1.10, and settings based on the “Template2 LRM”, but with audio from the AR2412 to IEM listened to on headphones. The result I get is …. drumroll…. 43s.
As is said in the release notes for V1.10 “Rare cases that could cause the GLD-80 to lock up due to a problem in a USB subsystem
have been fixed.”.Antony Jackson
Software Manager
Allen & Heath Limited2013/01/31 at 2:59 pm #32924Hi All,
Firstly – you are all correct. The control of the stage box(es) are done over TCP/IP (either thru an ACE tunnel, or directly via Ethernet, etc.). So the networking of control messages is not a problem – and not too dissimilar to using Editor or MixPad. The problems come with the surface audio, obviously there is only 1 PAFL bus, so that would need to be shared (without doing major changes to the architecture), and similarly with talkback. It would be reasonably OK to say the 2nd surface has no talkback and shares the PAFL, but there are other audio issues. One of the major problems is that the Surface PreAmp type (analogue / digital / dual analogue) depends upon what surface is connected and what card(s) are fitted to them, in the case of modular iLive, this information is Tx’d to the stage box on connection. To simplify things you could designate a “Primary” and secondary surface, with only the primary surface being able to supply audio inputs to the rack, but this starts to get complex as the non-primary surface may be switched on first and if this is because the primary is about to be switched on, then fine, but if we now intend it to be used as a single surface, this would need a clear message to the user so as not to confuse (think hire stock here). This connection order problems become vast when you have dual stage boxes as well! Due to these complexities, and the relatively small number of requests for this functionality we decided not to add the feature. I may be worth noting that V1.9 did add some of the work that would be necessary for dual surface. If you point 2 surfaces at a single stage box then you now get individual control of processing (i.e. the sel buttons work independently), which they didn’t in V1.8.
Antony Jackson
Software Manager
Allen & Heath Limited2013/01/28 at 9:02 am #32863Jeff,
Thanks for the report, I can confirm that this is indeed a bug in the firmware, we are working on a solution that will be included in the next software release.Antony Jackson
Software Manager
Allen & Heath Limited2012/11/27 at 9:08 am #32246The diagram is missing the I/O port as an option for inserts – but yes you can select the I/O port in the software – sorry for any confusion.
Antony Jackson
Software Manager
Allen & Heath Limited2012/11/08 at 10:28 am #31971Hi Everyone,
We are putting the final touches to the V1.9 software packages. My current best estimate for its availability would be Monday 12th. I’ll let you know if there is to be any delay to that schedule.Antony Jackson
Software Manager
Allen & Heath Limited2012/10/04 at 9:12 am #31558Hi Ross,
The direct outputs are pre-fade by default, and in all the template shows. The option that changes this can by found in the input routing screens pull-up. Options are available for “Follow Fader”, “Follow Mute”, and the audio source point.
Antony
Antony Jackson
Software Manager
Allen & Heath Limited -
AuthorPosts