Jump to content

usedbyanr

Members
  • Posts

    53
  • Joined

  • Last visited

Profile Information

  • Registered Products
    1

usedbyanr's Achievements

Contributor

Contributor (5/14)

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

Recent Badges

7

Reputation

  1. I don't believe there's any public information but the PGP files are just simple JSON. You can make a change, export and diff the files to see what changes. Other's have figured out what's in there because there's a few websites that will load a Helix preset and display it visually. The formats are nearly the same with different extensions. If you look at the PGB files in a hex editor you will see they start with AF6L. Google "AF6L beginning of file" and you will stumble across a Helix backup file parser project. I assume the files are the same with different extensions. Not to rain on your parade but, my guess is that some of your ideas are not something that would be in a preset file. For example, the color of a delay is likely built into the Pod Go firmware and Pod Go Edit rather than reading it from the file. Volumes are dependent on the individual amp simulations and gain settings from whatever pedals you have selected.
  2. This is your crash from the dump file. 09:55:27 [832 mils] : Loading effect Helix Native (VST3) 09:55:27 [832 mils] : VSTInventory - found GUID, isInstrument = 0, DLL is C:\Program Files\Common Files\VST3\Line 6\Helix Native (x64).vst3, bits is 64 09:55:27 [940 mils] : Writing dump file: C:\Users\natha\AppData\Roaming\Acoustica\Mixcraft\Mixcraft-Crash.dmp 09:55:28 [ 55 mils] : Exception in module C:\Program Files\Common Files\VST3\Line 6\Helix Native (x64).vst3 (loaded at 0x16840000) at location 0x002E7B38, line number 0x002E6B38 09:55:28 [244 mils] : Access Violation at 0000000016b27b38: 66 83 3c 59 00 75 f6 45 33 ff 41 8b Registers: Rax:0000000000000000 Rbx:0000000000000000 Rcx:0000000000000000 Rdx:0000000000000000 Rsi:00000000113098c0 Rdi:0000000000000000 Rsp:000000000014bd50 Rbp:000000000014be69 You can see that registers Rbx and Rcx are zero. This is the disassembly of the offending bytes in the line above with timestamp 09:55:28. The cmp WORD PTR [ecx+ebx*2], 0x0 instruction is comparing the value read from address [ecx+ebx*2] to zero. The address [ecx+ebx*2] = [0+0+2]. That is what we call a NULL pointer reference. It's not actually a NULL because the address value is 2 but anything in the first 4K of address space is off limits to protect against NULL pointer access violations. That code looks very familiar but I don't have the code around it to verify. What version of Native is that crash dump from? You should see that crash in the Event Viewer under applications at roughly the same timestamp. Do you have an SD card plugged into your machine? First post on the topic. Second post on the topic.
  3. Does it crash the DAW or just Helix Native? Have you opened the windows event log and looked for an error? (I don't have Windows 11 but it should be similar. On Windows 10 you would click the start menu button and then type event as a search. Event Viewer should show up. Run it. Go to Windows Logs->Application in the viewer tree) Helix Native crashes often seem to be the authorization code crashing. The description of the error (usually an access violation/NULL pointer issue is the problem) from the event log is a good starting place for diagnosis.
  4. I don't have a whole lot of experience but the manual states that the 60w only has USB MIDI while the other two have the MIDI DIN plug as well. I believe you can plug a MIDI foot board into the DIN plug. I'm guessing you are stuck with the laptop for the 60w. I believe the Pod Go is the same. I'm pretty sure one of the replies in the 60w or 100w thread you mention went with the 100w specifically for that reason.
  5. I don't have enough experience to say whether they are modeling the power amp or not. If I had to make a guess I would say the amp models are emulating it and the hardware power amp is relatively clean. I think you would want that so your XLR out sounds like your amp and the modeler input also doesn't have a lot of coloring. The three types of cabs are just different configurations (1x12, 2x12, 4x12) rather than speaker types. I'm too inexperienced to know the difference between them other than volume and possibly bottom end. It seems more like a simple shortcut for your front of house signal rather than micing it yourself. The pilot's guide suggests that plugging in your modeler bypasses the preamp unless you don't have the switch set properly. I would think it would sound horrible with a modeler plugged into the effects return and the switch not set to power amp unless you were just using it for pedal emulation. I wish we knew more about the speaker.
  6. I don't believe the 4CM is necessary at all. (Maybe you are just using the acronym as a generic term for a modeler to amp connection.) Based on the diagram in the Catalyst Pilot's Guide, it's just a connection from the modeler's mono output to the amp's FX return in power amp mode. There's a few F12M-150, F12-X200 videos by Celestion UK that show you how to replace the speakers in a few different amps that have access to the power amp (Roland JC-120) bypassing the pre-amp. That's pretty much exactly what this is doing. If it sounds good it would be a significantly cheaper option than most of the other options for the home player.
  7. I wish there was some definitive information regarding FRFR. A video demonstrating a modeler into the power amp would have been nice. The "What’s different between Catalyst and Spider V MkII?" question in the FAQ states "Full-range tweeter not included' but that doesn't mean it's not something like the F12M-150 where the tweeter is built into the cone. They specifically went out of their way to include a direct line to the power amp that states for use with a modeler. The AUX IN also states "An auxiliary audio input for running external audio sources directly (unprocessed) into the amplifier’s speakers.". To me that implies the ability to play more than the traditional range that a guitar speaker would have. I guess we just have to wait for some videos.
  8. Maybe it's just my ears but I had AKG K240 headphones on when I posted this and the most I can hear is a slight almost imperceptible sound gap in the left ear at that delay.
  9. I'm relatively new to guitar but I'm pretty sure the image below is exactly what you are asking about. A 20 ms delay is too short for me to perceive but bumping it up seems to do what you want. I hope that helps.
  10. I have a Pod Go connected to Eris E5 XT monitors with XLR cables (XLR on the speaker end, TRS on Pod Go because that's all it has). I get the exact same pop when I turn the Pod Go on. I think there is a minor pop when turning the Pod Go off. I just assumed it was normal and changed the sequence that I use for powering up. I don't care to hear that and I was unsure if it was doing anything to the monitors. It seems like it may be a Presonus monitor thing rather than the Helix/Pod Go.
  11. Just guessing here but this sounds a lot like you are just in Stomp mode and need to hit the MODE switch.
  12. Did you do the factory reset like it suggested on the update page? This is usually the first reply I see to every Helix update so it must apply here.
  13. The first place I would look is the Windows Event Log. System Events is probably the best place to start considering what is happening. https://www.dummies.com/computers/operating-systems/windows-10/how-to-use-event-viewer-in-windows-10/
  14. What amp is everyone using when this happens? I have posted about an issue where the Pod Go has no output in the morning after leaving it on overnight. I returned the first unit because Line 6 could not replicate the bug report and that is what they suggested I do. The same happens on the new unit so it's not a hardware issue. I'm fairly certain it's a bug in the Orange amp.
  15. I have not used Helix Native other than the limited trial but there was a similar issue at the time where it would crash before the interface would come up and it didn't seem related to the SD card thing. I don't know if it was the DAW's fault or Helix Native. It was stuck in some state where it thought it was authorized but wasn't. That prevented the UI from working and maybe the DAW expected something different. If you shut off your internet connection and then attempted to use it, the login screen would pop up asking for a re-auth. You could turn your connection back on, re-auth and then it would work. Last ditch attempt I guess.
×
×
  • Create New...