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


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by PierM

  1. If there is no enough market demand, make no sense for them to keep a pipeline just to sell a bunch of guitars, nor to start a Variax II project. A production pipeline costs lot of money, and we all know how little Yamaha cares of niches products. Also, the Variax technology is really old, so to me looks like it's the right time to move on. Im not longer using the variax tones, they are thin and lifeless for me these days and software is totally unusable on modern OS, so I dont care much anymore, but still I have to say my JTV 59 has one of the best neck profile and best fretboard feeling I have in my arsenal. Means I will be still using my JTV as a regular guitar for many years to come, and that always been the real bonus of these instruments.
  2. Buy a 60W solderer and a solder sucker and remove the USB socket and all the soldering material from the back of the socket, on the PCB - and see if it does boot. Good luck.
  3. If this happened out of the blue, I'd contact support.
  4. PierM

    DAW Audio input

    Don't be lazy when asking for help. We need more details about your setup and Helix connections and monitoring system to better help you. Of course what you are reporting doesnt sound right.
  5. Point is Boss is shady with his standards, so they dont clearly states their "raccomended" adapter is a TYPE A TRS. People will just buy a cable looking like it, without knowing the TRS soldering is different, and it wont work. Since the standard is TYPE B, it's very common to buy this last one. I have seen this a million times.
  6. No, isnt that easy. The RC500 doesnt use DIN, but TRS Type A. Standard is Type B, so if OP isnt using a proper TRS to DIN Type A, it will never work.
  7. Have you set the MIDI PC RX correctly? (OFF/USB/MIDI Port/Both) Also remember BOSS uses TRS MIDI Type A, so you need a proper cable adapter otherwise it wont work.
  8. Not sure what you mean, but if you are a musician and want to communicate with l6, this should be the right contact;
  9. I wouldnt connect the Helix USB to an hub. Typical cause of com stability problems.
  10. Because it would need an almost complete re-code. There are solid rumors of a light version of MacOs version that should run in new iPads Pro (starting from the series 6 M2) and live together with the standard iPadOS. Fingercrossed!
  11. HX Stomp is just an another PCB based electronic device, with 99% of the components directly soldered on the board. Unless you have the skills, the experience and proper tools to work with such devices, I wouldnt even try. Isnt exactly like changing a pot in a strat and you risk to create even more damages. :) For a pro this is a very easy task, and shouldnt cost you much. Same with L6 taking care of it, probably a bit more expensive but with extra guarantees that it's gonna be a correct job.
  12. Interesting philosophy. So spending my time to make a video for you, was rude. Asking you to use higher buffers was rude. Suggesting to upgrade all GPU drivers was rude. Suggesting to not unload the plugins, but to act on their mix levels instead to prevent performance inbalance, was rude. Did you even try any of these suggestions? Welcome to my ignore list, enjoy the good company. o/
  13. PierM

    Register Used Gear

    Please do not start multiple threads for the same issue. Yes you can. You just have to contact support and prove you are the new legit owner. The serial will be removed from the previous owner and you'll be able to register on your own account. Happened to me twice. I did sell a bunch of L6 gear without deleting it from my list in the account (I totally forgot), and I've seen those serials were gone from my gear list, couple of weeks after the sell, as per request of the new owner to L6.
  14. Yes. You just need a L6 account (like this one you are using to post) to access the download function. The gear registration isnt mandatory, but I'd suggest to ask the previous owner to delete that HX Stomp serial from his Account if registered, so that you can register it under your account for assistance and support purposes. You can still add this serial, asking support to L6 and proving you are the new owner of this unit.
  15. To me looks your problem isn't Native, but FL Studio. :) Jokes apart, if the instances are bypassed this will cause a big CPU/RAM spike when you'll turn them on again. Not sure what kind of studio work you are doing, so I cant offer particular suggestions or opinions, but usually I do rather keep all Native instances working, as well as most demanding blocks (like timing blocks, reverbs, delays, pitch etc). I do control both Native instances overall volume (signal mix) and demanding blocks (instead of using bypass I do command their level in the path), via extra controls acting via MIDI, so that I don't create an imbalance in the CPU/RAM when loading/unloading all these elements while working. Also this allow me to keep an eye on the project resource average requirement, avoiding surprises along the way. But again, I don't know FL Studio and depends what kind of project you are dealing with. Anyway, have you tried using much higher audio buffers, I mean like 1024 or 2048? This will help with all those plugins being loaded and unloaded all the time.
  16. Running 20 or even 30 instances of Native isnt an issue per se, totally true. You will get clipping with CPU load as soon as signals are hitting all blocks involved in each of those istances. I start getting CPU spikes even with just 4 instances...but of course if nothing is being played through those tracks, CPU isnt doing much. And then depends what blocks are being used in each of those instances. With poly pitch for example, things can go bananas pretty quick. Btw this shouldnt be a problem for normal studio work, where CPU spikes arent big deal, and you could always use crazy high buffers. I believe OP isnt actually getting particular issues, just asking Native and his system to do miracles. :)
  17. Six instances of reatime Native without tracks freeze it's just a huge effort you are asking to your system.
  18. It's system dependant, I'm pretty sure about that. And probably it also depends on what's being used into the presets. Who knows. I've a zen approach to music, so I can deal with that 4 second close. :)
  19. Just did a quick video so we can see if we are on the same page (Live 11, MacBook Pro M1). If you watch it, turn on the audio as I slammed the mouse clicks so you can hear when I load the plugin and when I unload it. As you can see it opens pretty much instantly, but it takes some time to close (average 4 seconds or more, just random). Always been like that for me (no difference between Live, or Gig Performer or whatever other DAW I used), so I never felt the need to flag it as a problem to solve. 20-07-23%2C 14 33
  20. I understand the feeling; when these things happen and you dont get the answers you were expecting, it can be annoying. Said that, Im also a long time Native user (no FL Studio tho), and I dont remember any of these problems in both Windows and MacOS platforms. Plugin opens as any other similar plugin (I wouldnt compare the time needed to open a Valhalla plugin with the time needed to open Native - for example...That's quite a big difference). Also no issues with VST3 and Live 10, nor 11. It's true Native requires more time than other plugins to be closed, this is something I have in any DAW. Always been like that since early versions, could be something related to its memory management, but yeah, never been a big deal for me. If you wait for Line 6 to rework their code to improve the unload timing, you'd probably get old. I'd try to reorganise my workflow to avoid too many load and unload of Native during a session if waiting few seconds to close it's something you can't deal with. :) Keep in mind Native has a busy UI, so there is some GPU work behind it. It needs extra cycles to render all that interface, and I wouldnt be surprised to find that your issues are related to that. Try updating your GPU drivers, and if you are using a double GPU system, check you are running DAWs with the powerul GPU available.
  21. Hi. Has been discussed a billion of times. So you can do a search in the forums or;
  22. There is a global bypass but it does require two buttons (MODE button + TAP footswitch) to be pressed simultaneously.
  • Create New...