[bucksParticipant]

Hi Rohan,

You can use a different role in Director and the Surface.

The IP Controllers inherit the role of the device which has been used to connect to them.

So a surface connected IP Controller will use the same role as the surface.

This however only limits scene recalls from the IP Controller.

So a physical FOH surface should be unaffected by a scene recall via a softkey on an IP Controller attached to a Director session providing the role ID’s are different.

This doesn’t change the existing situation of a surface having a singular selected mix, and the IP Controller sharing this select.

Does that make sense?

cheers

Andy.

[bucksParticipant]

Hi AJ

The role setup moved fairly late on in development.

It’s under surface setup / surface preferences.

Hope this helps

[bucksParticipant]

Hi Tor

Auto tracking allows you to make changes to a scene or a range of scenes by monitoring what the user has adjusted.

So let’s say you start auto tracking and you adjust a PEQ and a preamp gain, the console takes note of these changes and only these values are updated within the scenes selected.

Using the old scene system you would have had to manually tell the console which params you wanted to update. Auto tracking is a way of defining the scope of the update automatically by ‘watching’ what the user has changed.

Absolute mode is the same as previous releases, the value you see on the fader or pot is the value you will get in all the selected scenes.

In relative mode, let’s say we have a preamp at 0dB in scene 1, and +5dB in scene 2, if I select both scenes for update, then recall scene 1 and enter auto tracking with relative selected then boost the preamp by 2dB you would end up with 2dB in scene 1 and 7dB in scene 2. So relative respects the current scene values and applies a delta to the existing value.

In abs mode you would have got 2dB in both scenes.

Worth noting relative applies to preamp gains, send levels etc. Not everything can be relatively updated. For all non relative updatable parameters which are scoped, they are done in absolute mode instead.

Hope that make sense?

[bucksParticipant]

Hi Guys

Hopefully I can add a bit to George’s post and clear up some misunderstanding.

V1.42 was released to address unresponsive UI’s. This fix addressed issues with the drivers for the onboard SATA storage which were causing problems. V1.42 upgrades the linux kernel to achieve this.

George’s issue here was the actually touch controller had stopped working under certain circumstances. So the desk was still operational, hardware buttons / faders etc working, but ‘mouse’ clicks via the touch screen were not being processed correctly. We actually plugged a mouse in via the USB port to prove the point.

So the problems that V1.42 addresses and George’s issue are separate, and shouldn’t stop anyone upgrading.

Hope this helps.

Cheers

Andy.
Allen & Heath.

[bucksParticipant]

Hi Paul

I’m sorry to hear you’re having problems.

The code changes discussed above were introduced in V1.12 so you already have them.

The procedure for the log file cleanup is simply to power cycle the desk.

If this doesn’t resolve the issue, there is something else at play.

Either way it would be best to contact Allen & Heath Tech Support and open a ticket so your issue can be investigated.

Hope this helps.

Andy
A&H

[bucksParticipant]

Hi All

I’ve just got approval from Apple, the iPad app should be in the AppStore in the next hour.

Cheers

Andy.

Andy
A&H

[bucksParticipant]

Hi Guys

We posted the iPad App to Apple on Monday.

The problem is the variability in the time taken to approve the app by Apple.

The review status has changed to “Under Review”, which normally means less than 24 hours to completion.

I’ll release the App as soon as its approved.

Sorry for the delay.

Cheers

Andy
A&H

[bucksParticipant]

Hi All

I’ve just been dealing with this unit, and thought I’d share the solution in case anyone else ever experiences a slow boot with static IP address allocation.

The GLD defaults are:

I/P 192.168.1.50
Mask 255.255.255.0
Gateway 192.168.1.254

This unit had its gateway set to:

192.168.1.255

This isn’t a valid gateway address ( .0 and .255 are reserved ). If either the netmask or gateway are invalid or not compatible with the chosen I/P address, you may experience the slow boot issue.

A brief and slightly dry tutorial is here:

https://support.microsoft.com/kb/164015

By re-entering the defaults above, normal operation should resume.

We’re also looking into providing a reset button to avoid this issue in future.

Cheers

Andy
A&H

[bucksParticipant]

Hi Ryan

All versions.

Although for the 1st year in the field these problems were unheard of.

It may just be the number of units in use has statically started to highlight these issues, or there may be localized factors which make the manifestation more prevalent.

In any case upgrading to the latest is recommended.

Cheers

Andy.

Andy
A&H

[bucksParticipant]

Hi All

Some more information on Martin’s crash.

There are 2 separate bugs here which are unrelated but cause the same point of failure:

1) An O/S indexing service generating large temporary files
2) USB Key hot unplug generating excessive event log entries

Both eventually cause the on board storage to fill up and the desk will fail to boot.

Martin’s failure was type 1, but type 2 is more common.

V1.12 maintenance release contains 2 changes to address these issues:

1) We’ve disabled the indexing service, to prevent it creating temporary files.

2) We check the log file size on the next boot, and clear them up if they are preventing the system from booting correctly.

The thing to note here is the log files ( for type 2 ) are created because the system was busy writing to a USB key, and the key was removed before the write was completed.

Our modification in V1.12 will therefore get a console broken in this way working again AFTER a reboot, but doesn’t prevent it from happening in the first place. Further after the disk has filled up, and before the console has been rebooted, the console will be unable to store shows / libraries to the disk – its full!

To prevent this situation you need to wait for the write to USB Key to completely finish. There’s usually a light which flashes on the device, but often the write activity happens in bursts with gaps in between. This can cause the user to think its finished, when actually its just gearing up for another write!

The USB Key manufacturer has a slight bearing because some are faster than others. You are less likely to hot unplug a fast key, because its more likely to be finished! Also some manufactures use large caches to improve write performance, and haven’t actually completed the write, but tell the console they have!

In addition to the fixes in V1.12 we’re looking into suppressing the event log entries altogether for a future firmware update which would stop the event log from overflowing.

But …

The user will still run the risk of loosing data if the key was removed before the write completes.

The best advice is therefore to give the USB key writes a bit of breathing space. Count to 10 before pulling the key out after a write!

V1.12 should go live on the website later today.

Hope this helps.

Andy
A&H

[bucksParticipant]

Hi Ron

Thanks for the update.

We’re going to need some more info to track this down, could you open a ticket at:

https://allen-heath.helpserve.com/

Could you include iOS versions / hardware models which work and don’t work along with the firmware version on the desk.

Also the make and model of the AP would be good to include on the ticket.

We will also need the event logs from the desk after a successful and failed connection.

Many thanks

Andy
A&H

[bucksParticipant]

Hi Ron

A good diagnostic to try, is connecting a laptop wirelessly to the AP, then ping the desk or another computer on the wired side of the network via the AP.

To do this open up a command prompt (Start -> run -> cmd), then ping the IP Address for a good 5 minutes:

ping -n 300 xx.xx.xx.xx

You should see:

Reply from xx.xx.xx.xx

and a response time.

If the response times are large or you see intermittent “Request timed out” you need to speak to your IT guy about it.

The desk will trip the lost comms if it doesn’t get a response from the desk in 10 seconds, so if you see drops in the ping test in this order of magnitude, then the AP / router could be your problem.

Let me know how it goes.

Cheers

Andy
A&H

[bucksParticipant]

Hi Guys

The OneMix update has now also been approved.

You should see it showing up in the App store over the next 24 hours.

Cheers

Andy
A&H

[bucksParticipant]

quote:

---

Originally posted by zblebt

Does it solve the problem with iPad 4?

iDR 48
T112
iPad3 + TL-WDR4300

---

Yes, we tested with an iPad 4 here and found some problems which the update addresses. Let us know if you have any problems.

Cheers

Andy
A&H

[bucksParticipant]

Hi Massimo,

1) Out of the box the GLD comes with static IP address allocation. What works well for a lot of people is leaving the console alone on static’s, but also using a DHCP lease pool for iPads / Laptops. This has the advantage that if the router is absent the desk will still boot, and means you don’t have to worry about statically allocating multiple ipads / laptops. You have to make sure the 2 address ranges don’t overlap though. So typically you’d start your DHCP lease pool at 192.168.1.100 and have say 100 addresses in the pool. This approach gives you the best of both worlds.

2) Custom 1 and 2 are stored on the iPad only. They’re intended for the iPad operator to have their own view of the console – independent of the banks / layers on the hardware.

3) We’ll add it to the list.

Cheers

Andy
A&H

[Author]

Posts