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

bbehrens

Members
  • Posts

    5
  • Joined

  • Last visited

Profile Information

  • Registered Products
    6

Recent Profile Visitors

468 profile views

bbehrens's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

4

Reputation

  1. Not with Line 6, it won't. I believe that the Variax design team is pretty much all gone. There has been no further development with respect to modelling guitars by any company and Yamaha (which now owns Line 6) is not interested since they have their RevSstarr (mis-spelling was intentional). But the technology is very much still out there and would probably be better than ever if machine learning was incorporated into the process. I also believe that the Gibson Hex pickups might be worth looking into using for a better modelling technology. But the same roadblocks would still exist in any approach. Time. Money. And the fact that guitar players do not like guitars built after 1970 even though nearly all guitar players typically play better modern built guitars than most made back then. Sorry. Open Source is still available to the motivated and willing. I would LOVE to see that happen.
  2. Thanks datacommando and rd2rk, I have updated the Support Ticket with some additional information from rd2rk. I don't like finding bugs! Save your congratulations for Line 6 who will squash the problem like a... bug?!?!?
  3. Thanks, I always keep Reaper at the latest version v6.78 Win64. I was posting in the hopes that others with other DAWs would reply and see if the issue is present in other DAWs as well.
  4. I think that I have found a bug in Helix 3.5 New Cabinet Models. I thought that I liked the sound of a Dual Cab (1x12 Grammatico with the 2x15 Brute Bas Cabinet) with the US Double Nrm Amp Model. I found two issues: 1) It crashed Helix Native in Reaper and I suspect other DAWs as well.
  5. Helix v2.81 not changing tuning of all JTV string tunings when changed via Snapshots. Helix Firmware: v2.81 OS: Windows 7 Global Settings: Default to Helix v2.81 Bug: Some String Tunings do nto change when String Tunings are designated to change for different Snapshots. (Step by step description of how to reproduce bug) Preset input set to Multi Snapshot 1 Variax settings Tuning (Preset) set to snapshots [Custom] and Strings 1-6 set to String 6 Tuning Preset: [0 (E)] String 5 Tuning Preset [0 (A)] String 4 Tuning Preset [0 (D)] String 3 Tuning Preset [0 (G)] String 2 Tuning Preset [0 (B)] String 1 Tuning Preset [0 (E)] Snapshot 2 Variax settings Tuning (Preset) set to snapshots [Custom] and Strings 1-6 set to String 6 Tuning Preset: [-1 (E)] String 5 Tuning Preset [-1 (A)] String 4 Tuning Preset [-1 (D)] String 3 Tuning Preset [-1 (G)] String 2 Tuning Preset [-1 (B)] String 1 Tuning Preset [-1 (E)] Snapshot 3 Variax settings Tuning (Preset) set to snapshots [Custom] and Strings 1-6 set to String 6 Tuning Preset: [+3 (E)] String 5 Tuning Preset [+3 (A)] String 4 Tuning Preset [+3 (D)] String 3 Tuning Preset [+3 (G)] String 2 Tuning Preset [+3 (B)] String 1 Tuning Preset [+3 (E)] Change from Snapshot 1 to 2 and 3 Does not consistently change all of the String Tunings to the tunings designated in each Snapshot with a Variax JTV-69.
×
×
  • Create New...