Editmote Support - Digital Rebellion

How to resolve iOS billing problems

Thu, 13 Dec 2012 12:19:50 -0700

On the App Store all purchases are handled by Apple. We have no knowledge of the details of your purchase and have no control over it. If you have a billing question or problem it must be directed to Apple.

You can do this by contacting iTunes support.

Troubleshooting Editmote connection issues

Thu, 29 Nov 2012 13:15:09 -0700

Try the following steps if Editmote is unable to connect to your computer.

1. Make sure that the Editmote Preference Pane is installed on your Mac and that the switch is in the On position.

2. Ensure your Mac and iOS device are connected to the same wi-fi network.

3. Make sure you have the latest versions of Editmote and the preference pane.

4. In the Editmote preference pane, try turning the switch off, waiting a few seconds and then turning it back on again.

5. Try force-quitting the Editmote iOS app by going back to the home screen, double-tapping the Home button, tapping and holding over the Editmote icon in the panel that pops up, then tapping the X or - symbol next to it.

6. If you have set the preference pane to listen on a specific network interface (by default it is set to Any), make sure that the interface is connected to a network that your iOS device is capable of accessing.

7. In the Security pane of System Preferences, make sure the Firewall is not set to Allow only essential services.

8. If the Firewall is set to Set access for specific services and applications, make sure the Editmote preference pane is added to the list (it is is located at /Library/PreferencePanes/Editmote.prefPane/MacOS/EditmoteListener by default).

9. Try disabling your network connection and then re-enabling it. If you are connected to a wireless network, this will involve going to the Airport icon in the top-right corner of the screen, selecting Turn Airport Off, waiting a few seconds and then switching it back on.

If you are connected to a cabled network, it will require unplugging the cable, waiting a few seconds and plugging it back in.

10. If you are on a corporate network, you may have a hardware firewall. In this case, go to the Editmote preference pane in System Preferences, specify a custom port and make sure this port is open on your firewall. Also try opening 36015, which is the fallback port if something goes wrong.

11. Try choosing a specific network interface and port to listen on and then connect manually to this IP address and port from within Editmote.

Files open in the wrong application

Sat, 07 Jul 2012 14:36:25 -0600

Problem:
You may experience a situation where project files open in one of our applications instead of its source application. For example, some users have found that XML files generated from Final Cut Pro open in XML Repair instead of Final Cut Pro.

Solution:
If OS X is not explicitly told which application a file should open in and there are many applications on the system capable of opening that type of file, it will guess at what the appropriate application should be. These guesses can often be incorrect.

To force OS X to open a file type in a particular application, ctrl-click on the file in the Finder and click Get Info. Under the Open With section, select the desired application from the list and click Change All.

Reporting iOS application crashes

Thu, 29 Dec 2011 20:05:19 -0700

If you experience a crash in one of our iOS applications, we recommend that you file a bug report and send us the log directly. While iTunes does automatically submit crash logs to us, it waits for a certain threshold to be met before doing so. This limits our ability to fix automatically-submitted crashes quickly and some more obscure bugs will never meet the threshold and so we'll never know about them.

Crash logs are copied to your computer when you sync with iTunes. They are located at ~/Library/Logs/CrashReporter/MobileDevice/[name of device] and/or ~/Library/ Logs/CrashReporter/MobileDevice/[name of device].symbolicated. You can submit these to us via the Report a Bug link on the relevant application's support page or by using the Leave Feedback link within the app itself.