Reply to thread

Message

<blockquote data-quote="Erik Jerde" data-source="post: 132115" data-attributes="member: 8276">Re: Digico SD iPad appI&#039;ve been playing with the SD iPad app for the past week on a SD9 and SD8.&nbsp; Standard software, no waves.Both consoles were already networked and on quality networks with wifi access already setup.The app is really good for a first version.&nbsp; I did have some crashing issues but that was solved by rebooting my ipad.&nbsp; If you&#039;ve got a cell network ipad it is critical that you disable the cell network.&nbsp; I just put it in airplane mode then turn on the wifi.&nbsp; This is true even if you&#039;ve got a solid wifi connection.&nbsp; Apparently the SD app is unable to identify and bind itself to only the wifi NIC.A major area for improvement is the whole connection process.&nbsp; If you&#039;re using a DHCP network and want to have regular ipad connectivity then you&#039;ll need to setup a DHCP reservation for your ipad or a fixed ip address.&nbsp; In the console you can setup an ipad once but on the ipad you have to enter in the console details (address, connection ports) frequently.&nbsp; With subsequent uses of the same console I&#039;ve had to re-enter all the connection information, none of it, or sometimes just one of the ports.&nbsp; Seems somewhat random.&nbsp; It would be great to have a way to save console connections to a library for quick access.&nbsp; It would be even better to have an auto-detect process that eliminates the requirement to input ip address and connection ports.It would be nice to have a notification on the console to let you know when an ipad has connected.&nbsp; This should be an option.&nbsp; Same sort of thing as when you connect to the console using the PC remote software.No FX rack access in the app.&nbsp; I&#039;d think this should be easy for built-in effects, but waves integration might be a challenge point.Macros was confusing at first till I realized you needed to assign an OSC trigger for them to show up.&nbsp; You can&#039;t have a macro assigned to a button and an OSC trigger - you have to duplicate the macro and assign a copy to each trigger.&nbsp; I setup a tap tempo macro to see how accurate it is.&nbsp; Not as accurate as a hard button on the console but not so far off as to be unusable.&nbsp; Good for &quot;roughing in&quot; a tempo while away from the desk.&nbsp; This was on a good wifi connection.The buss routing section is fantastic, it would be nice if something like it was implemented on the actual console.&nbsp; In short you can see and toggle all the buss assignments for the selected 12 channel bank on one screen.&nbsp; Every SD console operator I&#039;ve shown that too has reacted the same way.Dynamics type can&#039;t be changed in the app.&nbsp; No access to digitubes from the app.&nbsp; No way to unmute a channel that is muted by a control group without unmuting the control group (this is possible on the surface).Navigation of the console banks can be challenging because they are laid out identical to the console.&nbsp; It would be great if the &quot;ribbon&quot; at the top of the screen could be re-arranged in the app (and just for the app).&nbsp; This doesn&#039;t mean changing the contents of the banks to be different from the console, just make it so I can put right and left banks right next to eachother instead of having to scroll down to find the bank you want.&nbsp; Even better would be if this configuration could be saved to the session in a library that can be recalled.&nbsp; That way you can have different functional setups for each session and those can be different as session requirements change.In the upper left hand corner it lists session name and current snapshot.&nbsp; Touch it to save session.&nbsp; That&#039;s nice.&nbsp; Wouldn&#039;t have found that if I hadn&#039;t randomly poked it.&nbsp; (It&#039;s probably in the manual I didn&#039;t read).That last note is worthwhile.&nbsp; I only used the manual to setup the initial connection.&nbsp; Using the app was pretty self evident.&nbsp; Kudos to the DiGiCo team on a good first version.&nbsp; I hope they keep improving it.</blockquote>

[QUOTE="Erik Jerde, post: 132115, member: 8276"] Re: Digico SD iPad app I've been playing with the SD iPad app for the past week on a SD9 and SD8. Standard software, no waves. Both consoles were already networked and on quality networks with wifi access already setup. The app is really good for a first version. I did have some crashing issues but that was solved by rebooting my ipad. If you've got a cell network ipad it is critical that you disable the cell network. I just put it in airplane mode then turn on the wifi. This is true even if you've got a solid wifi connection. Apparently the SD app is unable to identify and bind itself to only the wifi NIC. A major area for improvement is the whole connection process. If you're using a DHCP network and want to have regular ipad connectivity then you'll need to setup a DHCP reservation for your ipad or a fixed ip address. In the console you can setup an ipad once but on the ipad you have to enter in the console details (address, connection ports) frequently. With subsequent uses of the same console I've had to re-enter all the connection information, none of it, or sometimes just one of the ports. Seems somewhat random. It would be great to have a way to save console connections to a library for quick access. It would be even better to have an auto-detect process that eliminates the requirement to input ip address and connection ports. It would be nice to have a notification on the console to let you know when an ipad has connected. This should be an option. Same sort of thing as when you connect to the console using the PC remote software. No FX rack access in the app. I'd think this should be easy for built-in effects, but waves integration might be a challenge point. Macros was confusing at first till I realized you needed to assign an OSC trigger for them to show up. You can't have a macro assigned to a button and an OSC trigger - you have to duplicate the macro and assign a copy to each trigger. I setup a tap tempo macro to see how accurate it is. Not as accurate as a hard button on the console but not so far off as to be unusable. Good for "roughing in" a tempo while away from the desk. This was on a good wifi connection. The buss routing section is fantastic, it would be nice if something like it was implemented on the actual console. In short you can see and toggle all the buss assignments for the selected 12 channel bank on one screen. Every SD console operator I've shown that too has reacted the same way. Dynamics type can't be changed in the app. No access to digitubes from the app. No way to unmute a channel that is muted by a control group without unmuting the control group (this is possible on the surface). Navigation of the console banks can be challenging because they are laid out identical to the console. It would be great if the "ribbon" at the top of the screen could be re-arranged in the app (and just for the app). This doesn't mean changing the contents of the banks to be different from the console, just make it so I can put right and left banks right next to eachother instead of having to scroll down to find the bank you want. Even better would be if this configuration could be saved to the session in a library that can be recalled. That way you can have different functional setups for each session and those can be different as session requirements change. In the upper left hand corner it lists session name and current snapshot. Touch it to save session. That's nice. Wouldn't have found that if I hadn't randomly poked it. (It's probably in the manual I didn't read). That last note is worthwhile. I only used the manual to setup the initial connection. Using the app was pretty self evident. Kudos to the DiGiCo team on a good first version. I hope they keep improving it. [/QUOTE]

Verification