01GT

If you look towards the top of the screen that you are on right now, you should see "Knowledge Base" right next to where it says "Forums" in bold. Click on "Knowledge Base", then click on "Spider V" under the amps section. The second sticky is the listing of all of the Spider V mk ii presets. Bank 22-31 are the "artist presets" and come with Spider V mk ii. So your amp should already have these on it. Also, besides the presets, there is some good info there. Check it out. Here is a link >>>> Spider V MkII Factory Presets list - Spider V - Line 6 Community

For the Win 10 and Remote 2.00 issue try this >>>> Fixed My Spider V Remote 2.00 Issue with Win 10 - Spider V - Line 6 Community The next issue you are going to have after running Remote 2.00 w/ Win 10 is the "no Internet" issue. For that, the fix is in this thread >>>> Spider V Remote no internet access detected - Page 2 - Spider V - Line 6 Community

Anyone have the Internet connection issue with Remote 2.00 should go to this thread for the fix: Spider V Remote no internet access detected - Spider V - Line 6 Community

Yeah, this fix did allow the Internet to Remote 2.00 -- it worked for me too. Nice job, JinxJinxsen! To get it working I also had to take the additional step to go to Fiddler "Options" and select "Decrypt HTTPS traffic" (install and trust these general Fiddler certificates) NOTE TO OTHERS: Fiddler must be open for Remote 2.00 to recognize the Internet connection

I run a Spider V 240HC mk ii w/ FBV3 board (+ EX1 expression pedal & G10T) using Remote 2.00 (Win 10) into my own 2x12 cabinet loaded with vintage EVM 12L speakers. There was a much older issue that some people could not run Remote 2.00 with Win 10, and were stuck running the older 1.03 version that is missing a lot of the 2.00 functionality. I was one of those people, but I found the fix for it, so this (I believe) should no longer be an issue for anyone else either. See this thread for the fix >>>> Fixed My Spider V Remote 2.00 Issue with Win 10 - Spider V - Line 6 Community More recently there was a Microsoft Windows update from last week that has disabled Remote's Internet access. Line 6 is working this currently (... I am assuming ...). But Remote still works perfectly fine; you just can't access tones in the cloud. All other Remote 2.00 functionality is intact. For me, I have had more success building all of my tones from the ground up myself instead of using the cloud tones, so the Internet-access issue does not even affect me. It took me longer to do it that way, but my final tones are better than what I was hearing in the cloud, and that was due (I believe) due to my very different speaker setup from what everyone else is running. As to what direction you should go? For me, purchasing everything with GC sales and Line 6 "25% off" coupons I have only $785 invested in my current Line 6 setup (includes 240HC, FBV3 board, EX1 pedal, and G10T cordless transmitter). That is a LOT of functionality, flexibility and power for very little money ... along with the fact that it also makes me the mayor of TONE CITY. Just looking at the other similarly priced non-Line 6 offerings compared to the Spider V, the other stuff just does not offer as much as Line 6. The Black Star stuff is intriguing, but their horror stories regarding lack of user support was a little scary to me personally. This is all just my singular and non-endorsed (unfortunately) opinion, though ... LOL.

I am running Spider V 240 HC with FBV3 with an EX-1 expression pedal connected to it (along with Remote 2.00 with Win10). Overall, I really like the FBV3 a lot. It is a great extension of the amp and Remote 2.00. The basics about this thing are well established and agreed upon at this point: nice metal construction, bright display, color LEDs, excellent having foot access to looper and tuner, etc., etc. Here are some other observations: 1) There have been some that complained about the price. Considering that a decent Wah pedal is about a $100+, the FBV3 price seems very fair considering the huge amount of additional functionality you get plus having the 8 different Wah pedals you can select along with the high-quality pedal on the FBV3. You can get this item for $240 out the door at Guitar Center if you just wait for one of GC's "15% off one item" coupons. Very fair price to me... 2) In Remote 2.00, the programmability of the FS1-5 switches on the FBV3 was more extensive than I expected. That was a nice bonus. 3) I initially thought that the amp's looper was controlled by the FBV3's "Tap" button. Nope, it is actually controlled using the FBV3's "Function" button. The FBV3's pilot guide (i.e., manual) only discusses use of the Function button when hooked up to Firehawk (no mention of use with Spider V at all). As such, I initially thought the "Function" button when using Spider V had no function at all, which I thought was odd. Line 6 should really have AT LEAST some small blurb on the "Function" button in the manual in the "when used with Spider V" context. 4a) When adding the EX1 pedal, the FBV3 automatically configures the on-board pedal to only being a Wah such that the pedal's toe-button turns it on and off, instead of switching back and forth between being a Wah and Volume pedal. Hence, the on-board FBV3 pedal becomes a full-time on/off Wah pedal, and the EX1 pedal becomes a full-time on-only Volume pedal. Originally, I was thinking of using the EX1 for delay modulation stuff, but I have decided (at least for now) that I really prefer having totally separate Volume and Wah pedals. Considering the EX1 is quite cheap (especially when using one of Line 6's "25% survey completion" coupons) any one with a FBV3 should at least consider getting an EX1 too. 4b) You can use the EX1 for things besides the extra volume pedal. It would be nice if that was written down somewhere to know what it can be used for, and how to actually use it. Right now, this information is far from clear or even available. If someone knows where this is documented, please let me know. 5) I was also initially thinking that the "FBV Control" app that you can download from Line 6 would also provide additional FBV3 control similar to how Remote works with the Spider V amp. Nope. That app is pretty much only for using the FBV3 as a MIDI controller for "other device" (i.e., non-Line 6, non-Spider, etc.) controls. Once hooked up to a Spider V, it automatically reverts to its Spider configuration settings. All told, that is perfectly fine with me, but it would be nice if this stuff was in the Pilot manual. 6) I thought the FBV3 would use a small power adapter. Nope. I was very impressed to find that there is no separate power adapter at all. It gets all the power it needs from the ethernet cable coming from the amp to power the LEDs for 13 footswitches, the bright display, the two pedal-dedicated LEDs, and whatever the internal circuitry needs. I know LEDs and displays use very little power, but for a fair-sized board like this one to get all its power from the ethernet alone is surprising ... at least to me. As such it means it has only one wired connection (plus the optional EX1 1/4" connection, if desired).

Yes, me too. Spider V 240HC with Remote 2.00 (Win 10) is still running perfectly fine, but -- just recently -- there is no longer an Internet connection acknowledged by Remote even when I have a strong Internet connection -- so Remote has no connection to "Cloud", and "My Tones" has all previously stored tones listed but is in "Offline Mode". There was a large Microsoft update that went out last Monday. I agree with the above post that I bet that MS update is what screwed everything up. (To Line 6: Are you picking up the phone to call MS to ask WTF? If MS does not issue another Windows update to fix it, then you will have to fix it with a Remote 2.01 version ... right?)

Or ... I am thinking ... you plug your guitar into the first effect with a normal cord, and plug the G10T into the output of the last chained effect (instead of being plugged into the guitar). As such, your guitar would no longer be cordless, but the G10T -- as some benefit -- would replace that last final cord from the effects boxes.

No, you are allowed. The cool thing about Line 6 is that every time you buy some of their gear, they give you a 25% coupon off anything for just filling out a survey on whatever you bought. I got my Spider V 240HC mk ii head for a good discount from GC, then after I filled out the survey on the head I got a 25%-off coupon that I used to save $25 off the G10T transmitter (reg $100); then I filled out the survey on the transmitter and got another 25% coupon that I am right about to use on a FBV3.

Fixed My Spider V Remote 2.00 Issue with Win 10 - Spider V - Line 6 Community

Answering my own question: Found it >>>> Recording with Spider V | Line 6 - YouTube

Just make sure you look at the "Android compatibility and connectivity" threads. Either way, I hope your issue gets fixed. When fixed, please come back here and post the final solution. Good luck!

I am just getting started. Where is this video?? Can someone give me link, please?

Remote ver 2.00 and Spider V 20 do work together (at least per Line 6's Remote 2.00 release notes). I have a 240HC head into a Win 10 machine so I can't provide much help to your specific problem. But there are some other threads on Android connectivity with Remote. I recommend you look at those.

You need to be running Remote 2.00. Once in Remote, log in to "My Tones" with your normal log-in. After being logged in, go to "Cloud" to find/search the tone you want. Once you find it, just double-click on it for it to load into Remote (so you can see all of its settings and use it if connected to the amp, etc.). To save it, you need to click on "Load/Save", then click on "Save Changes to My Tones". I have only had my Spider V since this last Feb/2021, but I have been able to search,/download/save at will with no problems at all. I just did one right now just to make sure. I have saved a ton of the presets with no problem. If you are having problems running Remote 2.00 on Win 10, that is a different issue. I was having that same problem, but I fixed that and posted a forum thread to fix it (hey, Line 6, how about kicking me a refurbished FBV3 for my trouble?? : ).

Thanks for reminding me -- I just downloaded mine. What you need to do is be logged into the main Line 6 website (Line6.com). So ... get out of the forums because that log-in is different. Then log-in to Line6.com. From there, select "Personal Info". That will bring up a new screen where (on the left side) you can select "Purchase History". Your download link should be in there. Mine was, and I had no problem with download either.

Строка 6 должна увидеть это и добавить его в доступную документацию.

See this thread: Fixed My Spider V Remote 2.00 Issue with Win 10 - Spider V - Line 6 Community

If this ends up being the formula to fix the Spider V Remote 2.00 for Win10, then Line 6 should send me a refurbished FBV3 or something. Don't you think?? Spider V 240HC mk ii: I had three older Win10 machines that had no problems with Spider V Remote 2.00. THEN I got a brand new Dell Intel-i5-10th-gen Win10 machine where Remote would start to launch for a few seconds then go away, and that was it (you only see the "launch spider" graphic for a few seconds). The only way to run Remote was use the down-rev Remote 1.03 version which loses a lot of the Remote 2.00 functionality. However, after reading everything, I was able to fix it and get Remote 2.00 running perfectly on this machine that had this problem. I read all this stuff about "C++ redistributable files", etc. that I did not understand, but seemed to find the right formula for it to work for me. What I did: 1) Install both the latest Spider V "Drivers" software and Spider V "Updater" software (then using the Updater, I updated the 240HC head and G10T to latest firmwares). Remote 2.00 still did not work, but I figured it would need to be done regardless. From there, I still had to use the Remote 1.03 software since that would work. 2) Uninstall the existing Remote 1.03 version 3) Download and launch the MS Visual Studio 2019 executable file (https://visualstudio.microsoft.com/) 4) When performing the Visual Studio 2019 install, I additionally installed it with these three add-on items (there is a long list of selectable items that you can add on as part of the Visual Studio install) A) SQL Server Express 2016 B) & C) there were two available "C++ redistributable file" add-on's available for selection (I included both of them ... why not?) 5) As part of the Visual Studio 2019 install, I performed the re-boot as directed. 6) Launched Visual Studio 2019 to make sure fully working, etc. 7) Re-install Remote 2.00 and re-booted 8) Launch Remote 2.00 ... and -- holy crap -- it worked!!!! Hopefully this will work for the bunch of others also affected by this!!!!

Thanks for thoughtful reply

Okay, so I got the G10T wireless transmitter to go with my Spider V 240HC head. It works great. But it does not charge unless the amp is turned on. So I am thinking to just turn the amp on and then charge it up a few hours before use (instead of leaving on continuously)? Is that what other people do? Or do others leave their amp on 24/7? What does Line 6 recommend?

I had installed Spider V Remote 2.00 on three Windows-10 PCs with no problems. THEN I upgraded one of those three with a brand new (just got it in fact) Windows 10th-gen-i5 tower from Dell. With that machine, every time I launch 2.00 I get the initial "Spider screen" for three seconds then it goes away -- and that's it. I initially figured that I must have some weird firewall thing going on keeping Remote 2.00 from launching properly. So I took down all of the firewall stuff, performed multiple remove/re-installs of Remote and still (very frustratingly) could not get it to work. Then looking into these forums, there are others with the same issue that had installed down-rev version of Remote to make it work. I tried that, and everything came to life. So, I got Remote going on that new Dell tower now, but I have to run Remote 1.03 to do it (the most current version before the current 2.00). I am at least grateful to have Remote working, but a little bummed out since I lose all of the new 2.00 functionality. Hopefully Line 6 will fix this issue with a 2.01 release??? EDIT: I also removed/re-installed the Line 6 Spider Drivers 1.95 (current version) too as part of the above process, but that was no help either. Maybe there is a a combination of Remote 2.00 with an older-rev Driver that would work? That was the only thing I did not try.

The definition of "static cling" is a buildup of static such that (via charged ionic attraction) the item is attracting excessive dust or even garments and such. It is "static cling" that causes electronic equipment to become excessively dusty while not the things right around it. There is not a noise associated with "static cling" which makes your post confusing. Is it an "audible static" that you are hearing, or a "static cling" that you are some way feeling or seeing?

Maybe some smarter people have better ideas than me, but .... I don't see any solution other than entering the amp, disconnecting the existing the speaker, and creating yourself an external out to go to your cabinet. Because of that, I say, "Yes, get the new head and just call it day". If you do get the head, you can wire your new cabinet for either stereo (individual 8 Ohm connections; one connection to each speaker) or mono (single 4 Ohm connection). I have the head, and have it connected to a single 2x12 cab w/ EVM 12Ls, and I connect the head to cabinet with dual stereo connections.

I recently got a Spider V 240HC head, and installed Remote on three different computers all with Win 10 (one machine was 10+ years old w/ questionable processor speed/RAM, and the other two machines were fairly new). All had all their Windows updates, etc. The Spider V Remote app worked perfectly with no issues on ALL three of my machines -- no issues whatsoever. The USB "printer cable" I used on all three was a brand new USB 3.0 high quality cable (no looking for an old printer cable in the closet). Also, you need to make sure that the "Select" switch on the back of the amp is set to "MAC/PC/ANDROID". If you are still having problems, then likely it is a driver problem in your computer -- see the link in one of the posts above that have all the proper updated drivers, etc. Post back here what you found out.