Jump to content
Sign in to follow this  
Crito

Spider V + Spider Edit (iOS) - The Missing User Guide?

Recommended Posts

So... I bought the Spider V 120 a few days ago, and I've been creating some tones using the iOS Spider Edit app. Except for the fact that I keep losing contact with the amp (I think because the thunderbolt input on my iPhone 6 is flaky), I've managed to tweak a few tones to my liking. My question is: why doesn't Line 6 at least have a FAQ on how to use the Spider Edit app? (Or have I just been unable to find it?). It took me three days to stumble upon how to assign an expression pedal to a specific parameter (in case you don't know: by tapping twice on the parameter). I still don't know exactly where my tones are being stored (on the phone? in the cloud?). Nor do I know, except by trial and error, which stages of processing can be manually dragged to other other positions in the signal chain.

 

I understand why Line 6 might have decided that it was just too much trouble to support both mobile device apps and Mac/PC apps, but is it really that much trouble to create a simple user guide for the mobile app? Is Line 6 really that financially stressed?

Share this post


Link to post
Share on other sites

So... I bought the Spider V 120 a few days ago, and I've been creating some tones using the iOS Spider Edit app. Except for the fact that I keep losing contact with the amp (I think because the thunderbolt input on my iPhone 6 is flaky), I've managed to tweak a few tones to my liking. My question is: why doesn't Line 6 at least have a FAQ on how to use the Spider Edit app? (Or have I just been unable to find it?). It took me three days to stumble upon how to assign an expression pedal to a specific parameter (in case you don't know: by tapping twice on the parameter). I still don't know exactly where my tones are being stored (on the phone? in the cloud?). Nor do I know, except by trial and error, which stages of processing can be manually dragged to other other positions in the signal chain.

 

I understand why Line 6 might have decided that it was just too much trouble to support both mobile device apps and Mac/PC apps, but is it really that much trouble to create a simple user guide for the mobile app? Is Line 6 really that financially stressed?

The Spider App is a huge source of contention for users. It works, or doesn't work, connects, or won't connect. Devices of all kinds tested and confirmed.

 

You, like many others are saying the same thing. In most cases, it seems the larger the user content in presets, the more the app has problems. There are some users on guitar forums (UG, TGP) that looked into it. They "rooted" tablets. "My Tones" files are hidden in the app. There's no user access to these files. The other problem is the file that is generated with a preset writes to one basic file that gets updated with each save or new preset. According to these guys there are no individual preset or preset file extensions for each. Most tested say the bigger that file gets, the worst time they have with preset management, app crashing. Consensus from programmers is that they can fix this with individual preset files vs having one massive xml file. That requires modification of the app. Everything about the app so far, even though there are many posts here, reviews on dealer sites regarding the faulty app, just has not been given much priority.

 

Suggestion Line 6 reps give is to vote for Win Mac editors on Ideascale:

Yes, that requires users to create another acct for Ideascale. Use the link below. Don't start a new topic.

https://line6.ideascale.com/a/dtd/Spider-V-Computer-Interface/859001-23508

 

There are a few videos online at Youtube showing the editor app usage examples.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×