Please ensure Javascript is enabled for purposes of website accessibility Jump to content

reyrios10

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by reyrios10

  1. Those were god suggestions.  I checked the grill and move the amp around just in case something was stucked there.  Couldn't find anything. I even used a dusting air can to cleaning between the grille and the speaker.

     

    Then I tried it with the headphones and I can hear the "blown" sound as well.  So something is wrong with my firmware update.  Unfortunately, I don't have a warranty anymore but I might have to take to a service store to see if it would be feasible and able to be fixed.

     

    Unless anyone else has anything other ideas?

     

     

  2. Once I upgraded my Spider V 120 to 1.05 or 2.0 all of my distortion sounds have this buzzing or almost like a blown speaker sound.  If I downgrade to 1.01 or x.03 for example, everything sounds fine, except that I don't the classic amp setting from 2.0.  So I can assume is not a blown speaker and a firmware issue.

     

    I have tried everything I know.  Factory Reset (FR).  Downgrading to 1.01, FR, installing each firmware up until 2.0, factory resetting each time. Installing 1.05, FR, installing 2.0.  Doing the upgrade from my iPad, from my PC using Line6 Updater, from my PC using the downloaded file.  Every time I have the same outcome. 

     

    Has anyone seen this?  Any other things I can try?

  3. I had the same issue. Support sent me this and it solved the problem:

     

    Please do exactly this: First install the older version of firmware, the one before 2.0, then once finished performer a factory reset on the amp. Once you've done this update to 2.0 again and the issue should disappear. Let me know how you make out afterwards.

    • Thanks 1
  4. Application: Spider V Remote.exe

    Framework Version: v4.0.30319

    Description: The process was terminated due to an unhandled exception.

    Exception Info: System.NullReferenceException

       at MainApplication.WindowsCommon.App.AppProperties.getAppProperty(System.String)

       at MainApplication.WindowsCommon.Editor.Editor..ctor()

     

    Exception Info: System.Reflection.TargetInvocationException

       at System.RuntimeTypeHandle.CreateInstance(System.RuntimeType, Boolean, Boolean, Boolean ByRef, System.RuntimeMethodHandleInternal ByRef, Boolean ByRef)

       at System.RuntimeType.CreateInstanceSlow(Boolean, Boolean, Boolean, System.Threading.StackCrawlMark ByRef)

       at System.RuntimeType.CreateInstanceDefaultCtor(Boolean, Boolean, Boolean, System.Threading.StackCrawlMark ByRef)

       at System.Activator.CreateInstance(System.Type, Boolean)

       at System.RuntimeType.CreateInstanceImpl(System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, System.Object[], System.Threading.StackCrawlMark ByRef)

       at System.Activator.CreateInstance(System.Type, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo, System.Object[])

       at System.Activator.CreateInstance(System.Type, System.Object[])

       at System.Xaml.Schema.SafeReflectionInvoker.CreateInstanceCritical(System.Type, System.Object[])

       at System.Xaml.Schema.SafeReflectionInvoker.CreateInstance(System.Type, System.Object[])

       at System.Xaml.Schema.XamlTypeInvoker.CreateInstance(System.Object[])

       at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstanceWithCtor(System.Xaml.XamlType, System.Object[])

       at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CreateInstance(System.Xaml.XamlType, System.Object[])

       at System.Xaml.XamlObjectWriter.Logic_CreateAndAssignToParentStart(MS.Internal.Xaml.Context.ObjectWriterContext)

       at System.Xaml.XamlObjectWriter.WriteStartMember(System.Xaml.XamlMember)

       at System.Xaml.XamlWriter.WriteNode(System.Xaml.XamlReader)

       at System.Windows.Markup.WpfXamlLoader.TransformNodes(System.Xaml.XamlReader, System.Xaml.XamlObjectWriter, Boolean, Boolean, Boolean, System.Xaml.IXamlLineInfo, System.Xaml.IXamlLineInfoConsumer, MS.Internal.Xaml.Context.XamlContextStack`1<System.Windows.Markup.WpfXamlFrame>, System.Windows.Markup.IStyleConnector)

       at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri)

       at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri)

       at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean)

       at System.Windows.Application.LoadComponent(System.Object, System.Uri)

       at MainApplication.WindowsCommon.App.MainContainer.InitializeComponent()

       at MainApplication.WindowsCommon.App.MainContainer..ctor()

       at MainApplication.MainWindow.<paramValueServerInitializationComplete>b__2_0()

       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

       at System.Windows.Threading.DispatcherOperation.InvokeImpl()

       at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)

       at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)

       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

       at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)

       at System.Windows.Threading.DispatcherOperation.Invoke()

       at System.Windows.Threading.Dispatcher.ProcessQueue()

       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

       at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

       at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

       at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)

       at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)

       at System.Windows.Application.RunDispatcher(System.Object)

       at System.Windows.Application.RunInternal(System.Windows.Window)

       at System.Windows.Application.Run(System.Windows.Window)

       at MainApplication.App.Main()
  5. Faulting application name: Spider V Remote.exe, version: 1.0.0.0, time stamp: 0x59a0ac3d

    Faulting module name: KERNELBASE.dll, version: 10.0.15063.608, time stamp: 0xadaa6ed6

    Exception code: 0xe0434352

    Fault offset: 0x000eb832

    Faulting process id: 0x3b60

    Faulting application start time: 0x01d338681bcbdb60

    Faulting application path: C:\Program Files (x86)\Line6\Spider V Remote\Spider V Remote.exe

    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

    Report Id: 8b985866-6bda-442d-88ec-e19354e9acda

    Faulting package full name: 

    Faulting package-relative application ID: 

  6. @deadlocked...  Actually, you can still use the Amplifi Remote witht the Spider V.  N ot the BT capability BUT you can still edit and get tone matching via USB!!!  I do it all the time!

    What would be the advantage to using the Amplifi Remote app vs Spider Remote?  Do you get a different set of tones from the cloud?

×
×
  • Create New...