Jump to content

ozanerkal

Members
  • Posts

    9
  • Joined

  • Last visited

Profile Information

  • Registered Products
    3

Recent Profile Visitors

545 profile views

ozanerkal's Achievements

Rookie

Rookie (2/14)

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

Recent Badges

4

Reputation

  1. ADDITION: OK, so I posted my last post in the other thread about this issue and someone commented that it didn't work for him. He says, however, that he additionally deleted all traces of Native as told in the Native Manual and that did the trick. That makes me think that having previously taken the same steps as he did, probably paved my path and that my "simple solution" in the above post wouldn't have worked without those steps. So I had to add this info here.. Clean Native first and then follow my post right above..
  2. Oh, so my method didn't work.. well I actually didn't mention my previous attempts in my last post as I had no success with them, but now I think maybe they paved the path.. What I did previously: 1. Delete all traces of Native like you did, as told in the Manual (which didn't include my last step) 2. Re-download and reinstall Native So now I think these two steps, combined with the last (deleting/renaming the Library > Application Support > Line 6>Helix Native folder) do the trick. BTW, I'm sure a clean install on a new computer would work OK. We had problems because we were migrating from older systems. Thanks for the feedback.
  3. Please Read For M1 Pro + Monterey Related Problems: (I posted this under another thread but this thread also seems to be related) SOLVED... & it was so easy.. ONLY ONE STEP (OK, two.. no uninstalling or reinstalling or re-downloading needed) Thanks to you all, so I had to post it here: System: Macbook Pro w/M1 Pro + Monterey. Problem was: New computer came with Monterey, migrated everything from old Macbook w/M1 + Big Sur, all but Native worked. Solution: 1. (Not sure if this step is necessary but probably it helped) Run Logic, go to Plugin Manager and if Helix Native isn't validated, quit, run again in Rosetta, go to Plugin Manager, select Native and "rescan selection" and see it get enabled.. then quit Logic. 2. In Finder top menu bar, click Go, press the Option/Alt Key to reveal "Library". Under Library > Application Support > Line 6 find "Helix Native" folder and rename or delete it (rename is better just in case) That's it. NOTE THAT YOU'LL LOSE ALL PRESETS AND IR'S AND SETTINGS.. I had them on my Helix Floor.. Now run Logic WITHOUT Rosetta, check if Native's still "enabled".. and then in a new track, insert Native and VOILA! Just like I guessed, an existing setting or preset must have caused the problem and it was located in that folder that I renamed. Once it was renamed or deleted, Native recreates that folder this time without the problem. I didn't have to delete Native at all, I just luckily found where the problem was and it's gone.. Finally I can use Native after 2 months.. All the posts here helped, so thank you, hope this works for others :)
  4. SOLVED... & it was so easy.. ONLY ONE STEP (OK, two.. no uninstalling or reinstalling or re-downloading needed) Thanks to you all, so I had to post it here: System: Macbook Pro w/M1 Pro + Monterey. Problem was: New computer came with Monterey, migrated everything from old Macbook w/M1 + Big Sur, all but Native worked. Solution: 1. (Not sure if this step is necessary but probably it helped) Run Logic, go to Plugin Manager and if Helix Native isn't validated, quit, run again in Rosetta, go to Plugin Manager, select Native and "rescan selection" and see it get enabled.. then quit Logic. 2. In Finder top menu bar, click Go, press the Option/Alt Key to reveal "Library". Under Library > Application Support > Line 6 find "Helix Native" folder and rename or delete it (rename is better just in case) That's it. NOTE THAT YOU'LL LOSE ALL PRESETS AND IR'S AND SETTINGS.. I had them on my Helix Floor.. Now run Logic WITHOUT Rosetta, check if Native's still "enabled".. and then in a new track, insert Native and VOILA! Just like I guessed, an existing setting or preset must have caused the problem and it was located in that folder that I renamed. Once it was renamed or deleted, Native recreates that folder this time without the problem. I didn't have to delete Native at all, I just luckily found where the problem was and it's gone.. Finally I can use Native after 2 months.. All the posts here helped, so thank you, hope this works for others :)
  5. Hi, my Macbook Pro (M1 Pro+Monterey) came in November and I migrated all my data from my old Macbook Pro (M1+Big Sur) with success. Since then, everything works fine except Helix Native.. I'm aware that Big Sur was OS11 and Monterey is OS12. This means major update, so we may of course have some incompatibilities, but it's been a pretty long time now and it's getting annoying. I messaged Line6 Support but the reply was something like "you can't authorize more than 4 computers with Native.. (not my case)" and "Monterey is not yet supported officially" and this link: https://line6.com/support/announcement/104-apple-m1-macos-11-and-12-compatibility-with-line-6-software/ So I decided I'd wait, but then there's your post saying you deleted and reinstalled everything. I also tried to do it: First I deauthorized and reauthorized my computer (just in case) and then manually found and deleted the plug-in from its locations as explained in the Native Manual. Then I reinstalled Native.. but no change.. The strange thing is, although I deleted everything, my presets were still there after reinstall. So I think maybe the presets are causing the problem but I can't find and erase them manually. Have to ask: 1. Did you find and erase them? 2. Did you uninstall and reinstall Logic too? Can you specify the details of what you did exactly, I must be missing something.. Thanks
  6. Thanks to all replies. This has been very helpful and I'm kinda into it now.
  7. Hi everyone, I just got my helix (second hand, like new) Most of the time, no problems and I'm also very satisfied with my tone so far. But sometimes it just won't boot. The boot screen acts normal, with the moving spirals etc., but it doesn't disappear and the home screen doesn't come. Added to that, the top left of the display reads ":-28" in red characters. (See the Image attached) I believe I saw this happen with FW 2.10 which was loaded when I bought it. Now I'm on 2.12 and I still have it. Anyone else having this? I mean it's no big deal as it's not happening all the time, but if it's a sign of something important, I should solve this problem right? Thanks
  8. Hey all, I've had the HD500 since early 2013. Used it for all my live situations for 2 years, then I started to carry my rack which includes an Axe-Fx II XL. The Axe-Fx was intended for recording needs originally, but after I added a wireless system and an IEM to the rack, I felt it would be easier to go live with the rack. Of course, compared to the POD, it was way too heavy, but I was only playing 2-3 times a year with my metal band so it was no problem. Now, with a new project that I'm involved, and another on its way, I'm going to get into more live situations. So I turned back to the POD, upgraded the FW, made new presets that sound way better than the previous ones, and I really LIKE IT! Not only the sounds, I like the connectivity options too.. The Balanced XLR outs go to the FOH, 1/4" out to the IEM (to hear myself at least, if no out from the FOH is available). I'm happy to reconnect with my POD. Oh and at home, the best experience is when i connect it to an Atomic CLR. Yes, I wouldn't have had an Atomic if I hadn't had the Axe-Fx but I do, so I gave it a try and being known for its transparency, the CLR gives me the real intended sound of the POD and is a true reference for what I will get at a venue where I get direct out to FOH. PS. The only drawback with my POD is the Parametric Global EQ which is completely impossible to use. I have a thread about it here at the forum.
  9. The main reason I upgraded my PODHD500's firmware was because it has a global EQ feature. But after the upgrade, I discovered that it's a Parametric EQ. I had to find guides on how to use a Parametric EQ (P. EQ) and now what I understand is that P. EQ is mostly used for recording. It's an advanced form of frequency tweaking, with many parameters related to different frequency ranges. Inside a DAW, a typical P. EQ is in a window where you can see all the parameters at the same time and also a colourful graphical representation of what the consequences of your work will look like. I mean, a P. EQ is very comprehensive when you have a computer screen. But WHY THE HELL would someone place a P. EQ on a device like the PODHD500 when it only has a 2" lo-res B&W display? how can I even start to tweak it when I can only see one freq. range at a time and nothing about the 4 other ranges? Even if I did see them would those numbers immediately mean anything to me? No, because there's no graphical representation... So far, the only use of the P. EQ for me was, I accidentally turned a few knobs and was afraid I changed something critical, came to the forums, found the default settings for the EQ, set them back to default and tuned the EQ off.. pufff.. I guess most of us are not experienced sound guys and the POD is not suitable for a P. EQ. but I'm sure we all can use a Graphic EQ. At least we all know how to reset all the faders on a G. EQ back to zero in case something goes wrong. Maybe a P. EQ is much better in the hands of an experienced sound guy but I think it's no use as we can't really use it. So would Line6 consider changing it to a Graphic EQ?
×
×
  • Create New...