Leaderboard

I’VE FOUND A FIX FOR THIS PROBLEM!!! I noticed that the only Setlists that were locked to Current Preset / Current Snapshot, were Setlists that had NOT had a preset added AFTER updating to v1.4. So I tried adding a random Preset to a Setlist that was locked within a Song, and when I go back in to the Song and try to add a Flag, not only can I add a Flag from the Setlist that was previously locked to Current Preset/Snapshot, but even better, ALL the correct Flags from before the v1.4 update were back in place in the Song again, and work as they should. If you don't want the Preset you just added in that particular setlist, you can clear it from the Setlist, and you'll still have access to that Setlist within the Song when you try to add a Preset and/or Snapshot Flag. I have shot a video, which is 276mb, but that is sadly far too big to upload here, so I don't know how to share that with you guys - hopefully my explanation will be enough.

I've sent a bug report so hopefully this is now on radar for the developers...

Possibly, did you check your Global Midi Settings? They have changed in 1.4. My Midi system went crazy, until I went into Global Midi, and turned OFF Matrix 1/4" Midi, Matrix XLR Midi, Matrix Phones Midi, then everything worked again with a restart.

I expect you’ll find this is not a problem. You don’t need to boost it. The dry signal is tapped and sent to the DAW directly from the Helix Rack input, meaning it is the same level that is received at the Input jack and then fed to the preset for processing. The dry signal is recorded at that level on the assumption that you will be reamping it using a plug-in such as Helix Native. You will find it adequate even though it seems low. I find the same thing when recording a dry and wet signal simultaneously. Then, when I use the same Helix preset in Helix Native and apply it to the ch7 signal the level matches the wet signal. You may need to apply a slight Input boost in Helix Native, or whatever plug-in you use. When the levels are matched the wet and reamped dry signals sound identical. Incidentally, I have the same setup. Helix Rack, Ch7 dry recording, and Cakewalk Sonar. If you aren’t using Helix Native you might want to check it out. Presets are directly transferable between the device and the plug-in.

Hi, Just wanted to confirm that the issue is now resolved! The registry workaround didn't work, but I downloaded Microsoft's Windows MIDI Troubleshooting and Repair tool: https://github.com/microsoft/MIDI/releases Interestingly, the tool showed that Windows was still running Mode 0 (Windows MIDI Services) despite the registry changes. I switched to Mode 1 (Legacy MIDI) using the tool, restarted Windows, and Workbench HD immediately connected to my Variax through the Helix Rack! The nice thing is that I can simply switch back to Mode 0 when I'm finished using Workbench HD, so there's no need to permanently disable the newer MIDI functionality, allthough it would be nice if you can point me to a more permanent solution so I don't have to restart my pc. Thanks again for pointing me in the right direction! Hopefully this will help others experiencing the same issue with Windows 11. cdegardin Oct 12, 01:16 AM Hi, there was a Windows 11 update for MIDI2.0, which led to some applications and MIDI ports not working anymore (like Workbench HD) But HX Edit was not affected by this. If you do this workaround Workbench HD should connect again : 1. Open Registry Editor (regedit.exe) 2. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 1. Create a new DWORD (32-bit) Value named: UseLegacyMidi 1. Set its value to: 1 1. Restart Windows. It should now connect https://microsoft.github.io/MIDI/kb/how-to-change-api-mode/ In Helix Rack, make sure to enable MIDI over USB in the Global Settings/MIDI&Tempo WOrkbench HD can connect via Helix Rack, but not Line6 Central (even if you see the Variax, updates are not possible that way, this is normal) Best regards Line 6 /Ampeg Support Europe

Thanks. So I’m not going crazy…. at least not yet …. just a little slow on the uptake ;-) I haven’t used IRs since the OG Helix new Cab engine was released so I missed that change.

Again...you can change what IR is loaded per snapshot. This is a screen shot from the online manual link I posted above. It was available on the OG Helix devices, also. Audio dropout was always minimal on the OG devices in my experience. I haven't tried on the stadium yet, so I can't tell you if it's noticeable or not.

agree with you

Just want to check the basics….. You don’t mention your Variax model. Is it JTV or later? If not you need to be using the original Workbench program, not Workbench HD.

I want to say goodbye to the forum, as i sold my Helix today after 10 years. Thanks a lot for your great support and also thanks to line 6 for buiding a great device and supporting it in a hilarious way ,keeping it up to date for 10 years - this doesn't exist often in the modern world. And it also keeps the value high, while electronics normally loose almost everything when they get outdated. Why i sold it? Honestly, the Helix was always way over the top to what i need and what i can handle. So many possibilities of course create a certain complexity and i never really lerned how to use it in the full range. So til now, it was difficult and took a long time to me to dial in tones. I just now went to a much simpler device (Valeton GP200), far below the abilities of a Helix (wich i mostly dodn't need). Therefore it's more intuitive to use (of course - because of much less possibilities) and i get faster sounds wich sounds good to my ears. But therefore it's mch cheaper, smaller form factor, lighter..... What i will miss:

What i will miss: - the better audio device (Valeton only supports 44.1 KHz) - The Mic in with 48 volts - Parametric EQs as blocks, not only as global EQ - Some unusual patches like the organ patch from Glenn de Laune - Quality of some effects, especially when it comes to pitch shifting and polyphonic things. So enjoy your devices, they're really something great.

You can easily invert that. Just activate the block you want on the "lightning" state manually and deactivate the other (not using the switch). That'll flip the on/off and the light status.

Hey fellow Helix/HX folks — long-time user here. Been gigging with a Helix since 2015, then switched to an HX Stomp later for portability. Wanted to share something I've been building. I kept wanting a preset editor I could open on whatever was in front of me — laptop, iPad, phone, whatever — without installing anything or having the unit plugged in. Couldn't quite find that anywhere, so I built it myself. Figured some of you might find it useful too. Helrig (helrig.com) — free, runs entirely in your browser: Drag in a .hlx from any of them — Helix Floor, LT or Rack, HX Stomp, Stomp XL, HX Effects, even Helix Native — or pull presets straight out of a .hxb backup or .hls setlist. Start from blank or load a sample to poke around Full signal chain and parameter editing, snapshots included Search blocks by their Line 6 name or by the gear they're modeled after — tube screamer, Fender reverb, JCM-800, whatever you actually think in Auto-detects the device on import and matches the DSP budget/footswitch layout automatically DSP budget enforcement like HX Edit — won't let you overbuild past what the device can actually run Hover a path's DSP icon to see the cost of every block on it, or open the full usage report for the chain — honestly my favorite feature; it's saved me from guessing more times than I'd like to admit Convert a preset between devices, and it tells you exactly what it had to change to fit — rather than quietly mangling it Undo and redo with a named history — "Add Deluxe Comp", not forty rows of "Edit" Share a preset with a link if you want to; the rest of your library stays private and you can revoke it any time Nothing gets uploaded — the file stays in your browser the whole time, no account needed There's an optional account that adds a cloud library — setlists, labels, version history — if you want presets synced across machines. Entirely optional; the editor is identical without it. Direct USB sync to the hardware is in progress but not live yet — right now it's file-in, file-out. Unofficial/independent project, not affiliated with or endorsed by Line 6 or Yamaha — just a fan-built tool made with a lot of respect for what they've built with Helix/HX, still the best guitar gear after almost 11 years. Rough edges still get fixed fast — if something looks wrong or a block/parameter shows up unlabeled, tell me and I'll dig into it. Feature requests welcome too, including "I wish HX Edit did X" type stuff — that's usually where the good ideas come from.

btw…. I have submitted a feature request that Customtone be updated to include associated Clone files in a Stadium Preset download. If you agree you can submit another request for this here: https://line6.com/company/contact/productfeedback/

I submitted a Bug Report, and got an email back saying they were changing my Bug Report to a Support Request, as this is a known problem. My advice is, if you're having the same issue, then submit a bug report and they'll respond similarly, with instructions on what to do to hopefully resolve the situation

Yes! HX Edit 3.80 works with Golden Gate. I have my Stomp XL connected to my M1 mini running the latest Golden Gate OS and all is well!

Hey everyone, Just wanted to share a quick update regarding global MIDI CC footswitch emulation on the Helix Stadium / Stadium XL. In my touring rig (50+ songs), I rely heavily on DAW automation triggering physical footswitches rather than individual block mapping. After discussing this with Line 6 support, they confirmed that while this feature is in their broader plans, Stadium has a much more complex routing and mapping architecture than the OG Helix, so there is currently no timeline for it due to engineering complexity. However, support explicitly mentioned that product managers prioritize feature requests based on the official Product Feedback tally count. If you also need legacy MIDI footswitch emulation for your workflow — please take a minute to submit a quick request via their official feedback form here: https://line6.com/company/contact/productfeedback/ The more requests they get in the system, the higher the chance this feature will be prioritized in upcoming firmware updates. Let us make our voices heard!

Also check your Global Midi Settings, there are 3 new midi commands sent out. I had to go in my Global Midi Settings and turned OFF Matrix 1/4" Midi, Matrix XLR Midi, and Matrix Phones Midi, then everything worked again with a restart. Then I had to basically set my EXT Amp Settings to the opposite of what I had them to get the EXT Amp switching to work again. Now it's all working again. Hope this helps.

Are you logged in?

…. but you don’t need to do anything about this …. There’s nothing wrong. Once the dry signal is recorded you can boost it if you wish using plugins or the Sonar channel controls, including ProChannel.

Based on the advice in this thread, I understand that the HX Effects uses solid-state switching rather than a mechanical relay, and that the EXT AMP command can be configured to switch RING to SLEEVE. Before connecting my equipment, I would like to clarify the electrical compatibility of this specific combination. Is the HX Effects EXT AMP output electrically compatible with the Victory Sheriff 22's footswitch input, given that the Sheriff uses latching short-to-sleeve switching on the RING contact of a TRS cable? The forum reply mentions that the HX Effects can only switch positive voltages. What voltage and polarity range is supported by the HX Effects EXT AMP output? How exactly should I measure the voltage between RING (+) and SLEEVE (-) at the Sheriff 22 footswitch input? Should the amplifier be powered on, and should the original footswitch be connected or disconnected during the measurement? Is measuring the voltage between RING and SLEEVE sufficient to establish compatibility, or are there any other electrical characteristics I need to check? Can I safely use a standard TRS cable with the HX Effects configured as follows? Global Settings → Preferences → Pedal 1 (or 2) Jack = EXT AMP Command Center → Instant Command → EXT AMP Select = 2 (Ring to Sleeve) Latching operation My goal is to switch between Channel I and Channel II on the Sheriff 22 while simultaneously changing HX Effects snapshots. I would prefer to verify electrical compatibility before connecting the two devices, to avoid risking damage to either unit. Thank you for your help. I repeat: That should work just fine. You will not hurt your amp or the HX when connecting them via TRS because the Victory is a modern amp that has to comply with modern safety regulations. The measurement stuff is for the case that it doesn't work to figure out why.

Thanks so much for the responses. Mine has a port at that same location. I'm in Canada so I don't have access to the support hotline or text - my guess is that that particular port must be for some final assembly testing and that they left the testing cable in the unit. Everything seems to be working fine with no issues that I can see so far.

Bumping this thread after checking out Firmware 1.4 Unfortunately, global MIDI footswitch emulation is STILL missing. It's incredibly frustrating to see a major firmware update packed with new amps and playback/Showcase tools, while the most fundamental live-automation MIDI functionality from the OG Helix remains omitted. As I mentioned earlier, my entire touring setup (50+ automated tracks in DAW) relies on MIDI triggering physical footswitches. Having to map every individual block per preset instead of triggering the switch itself is a dealbreaker. Because of this single omitted feature, my Stadium XL is still sitting in its box in October 2026, and I'm forced to stick with my original Helix on tour. Line 6, please... prioritize restoring physical MIDI footswitch emulation for v1.5!

Let me first say that I love this thing; feels so much more inspiring to play through the Helix Stadium than the Kemper for me. Love the plethora of effects/routing options/amp models. That being said, I have noticed some issues in the past month of ownership that I feel could easily be fixed with future updates. The list: 1) HEEL DOWN TUNER Maybe this is just coming from Kemper, but I am so used to having the tuner activate when the volume pedal is in the heel down position. I rely on this for quick tuning changes between songs more than I anticipated, and I feel like it’s an easy thing to add. 2) DEDICATED LOOPER STOP BUTTON I do a fair bit of live looping for solo acoustic gigs; with the Kemper, there was a dedicated stop button to store the loop/not have it autoplay for when I want to loop a section and play it later. From what I’ve seen, Helix Stadium does not currently support this, which makes live looping much more restrictive than on the Kemper. 3) INVERTED COLOR OPTION FOR SCRIBBLE STRIPS Most of my gigs have been outside during the day, and even at max brightness I really cannot see the touchscreen or the scribble strips at all (especially wearing sunglasses). I feel like a simple solution would be to invert the blacks & whites on the scribble strips so that it could be black text on white background. Or maybe there are polarized screen protectors that help with this? If anyone has dealt with this issue and has another solution, please let me know. 4) NO DIRECT MONITORING USING HELIX STADIUM AS INTERFACE The Kemper has a very simple option on the output section to turn on/off Direct Monitoring when using as an interface (mostly for reamping purposes); I am not seeing a simple option like this on the Helix Stadium XL. Again, this may just be me not looking hard enough, so if anyone knows how to make this work please let me know. These are not dealbreakers by any means (the looper one a bit more so than others), but I really do feel these are easily addressable/improvable issues in future updates. Hoping the powers that be see this and consider implementing these changes. Would love to hear other people’s experiences!

I am sorry but there are not very many guitar players that have a need for three independent output jacks on their guitar. And someone more knowledgeable than I will probably provide a better answer. I am going to show you what appears in the Stadium App Editor (and similarly on the Stadium screen itelf). There are the following inputs" None, Instrument 1, Instrument 2, Instrument 1+2, Mic, S.PDIF, Return 1, Return 2 Return 3, Return 4,Return 1/2, Return 3/4, USB 3/4, USB 4/5, and USB 7/8. Both Instrument 1, 2 and 1+2 have the following input parameters: Input Z has the following options: First Block, First Enabled (Block), 10K Ohm, 22K Ohm, 32K Ohm, 70K Ohm, 90K Ohm, 136K Ohm, 230K Ohm, and 1M Ohm. Trim has the range from -24.0 dB to +6.0 dB The Noise Gate is actually my preferred noise gate as it does a better job for me than the modelled Noise Gates in the box. Return 1 only has the Trim Control and Noise Gate and not the Input Impedance values. What Units are you considering that would have more than this? Just curious. I hope that this at least helps.

Hi fellow music/helix enthusiasts! Although I love the new Helix Stadium XL, it had the same downside for me as all modelers: it requires a lot of programming, thinking and tinkering with settings to create the sound you wanted. Guitar playing is just a hobby and I'd rather spend my spare time playing, not building patches. Factory patches might come close, but there's so many of them and they can be hard to navigate. Since I'm an IT professional and I'm using AI to assist me in many endeavors, I wondered if I could have Claude Code assist me in my hobby. Turns out I could. Now I can tell Claude a bit about the song or sound I'd like to create in plain English, it'll check public resources on which amps and effects to best use, put initial settings to match the request and build the patch. I tell it which guitar and or pickup it should be created for, and it adjusts the parameters to make it sound right. I'm not saying it's always spot on, but it often is (from the start). The only thing that remains doing is import the preset, play through it and adjust anything that you still like differently (or ask Claude Code to do that for you). Claude still doesn't have ears, but this cut down my patch creation time by at least an hour, often more. When I'd like patches to be leveled for a specific PA for use in a gig, it assists me. Since I assume there's more musicians out there with the same problem and time constraints, I decided to document and share how one would go about to have AI assist you in creating and/or editing your patches, so you have more time for playing/practicing. It takes about 10-20 minutes to get the AI show on the road with Claude code. I didn't share any proprietary content or patches, so you'll have to load these from your own device (everything is in the documentation). https://github.com/g3rtg3rt/helix-stadiumXL-claudeCode-integration

Unlike some other devices, the Helix Floor/LT/Rack allow any preset to be placed in any slot. There are 8 "Setlists" which are simply "BANKS" of 128 presets. Backup the Factory setlists if you think you might need those presets, then copy a BLANK SETLIST over the FACTORY setlists and you've got 1024 (8*128) potential preset locations to use any way you like. If you need to quickly get from a preset in SETLIST 1 to a preset in some other setlist, use MIDI.

On another forum a few days ago, we heard that 1.4 was close to release, and 1.5 is in dev (or something to that effect). I'm going to guess 1.5 is still happening this year.

FYI…. Since this is a paid utility please make sure any further posts promoting it are made in the Promote Your Patches area of this user forum, per the Terms of Use. Line 6 created an area specifically for users to promote their offerings rather than posting in the product specific forums. https://line6.com/support/forum/96-promote-your-patches/

Driver installed?

LT has only 8 assignable switches. But you can disable the up/down buttons with a hack I provided in that video above. However, still you are stuck with exactly 8 buttons that you can assign things to in Command Center, no way to make the up/down buttons do anything else on the LT.

I've seen Trower a few times over the years and his pedal layout is consistent and very minimal. Strat (usually neck pickup) >> overdrive >> wah >> univibe >> Marshal plexi. I believe there are a couple of rig rundowns you can find on youtube.

I have also been testing Showcase MIDI song selection extensively with a Helix Stadium XL and the app Easy Performer, and I wanted to share my experience. I can confirm the behavior described in this thread: CC63 works correctly by itself and changes the Playlist. CC10 works correctly when the desired Playlist is already active. However, sending CC63 followed by CC10 does not reliably select the requested song from the newly selected Playlist. I also tried adding delays between the commands, but could not make it consistently reliable. I eventually found a workaround that is much more reliable for my setup. I created a "MASTER" pad in Easy Performer that sends CC63 = 0, selecting the main SONG LIBRARY. Once the Showcase is in that state, I can use individual song pads that send only CC10 to select the desired song. There is an important detail: for this workflow to work reliably, the currently selected song must already be paused/finished. The MIDI command then puts the new song into a queued/paused state. I have not been able to make the newly selected song start playing automatically through MIDI. So my workflow is: MASTER → select SONG LIBRARY SONG PAD → select song (Queue/Paused) then manually Play This is much more reliable than trying to send Playlist + Song selection together. To me, this suggests that the issue may be related to how Showcase handles the change of Playlist/context before processing the subsequent CC10 command, rather than simply being a problem with MIDI transmission. Hopefully this additional information can help reproduce and eventually fix the issue.

Use HX Edit to back up your Presets. then perform a Factory Reset. Line 6 Device Factory Reset Procedures | Line 6 Knowledge Base If that doesn't work, contact support.

Has anyone followed the following tutorial link for the 10 tutorial videos? While it may not be exactly the learning path some may want it is free for now.

EOL is a two step process. First the mfr stops development, focusing their resources on new products. Then, when sales drop below where it's profitable to build it, they stop production. It may or may not be a Law of Nature, but it IS a Law of Business.

I've never come across something that doesn't work because the MIDI is too intensive; and they publish the setlist and song MIDI info against each song, so it's clearly designed to select a setlist and song within that list. I've submitted a bug report, definitely worth you doing it too, the more they get the more likely they are to fix it

Long time Line6 owner here. I would like to know when Apple silicon versions of the Pod Go Wireless are going to be available. I keep getting pop-up messages that support for Intel apps is ending soon. Any word on development? Worried that my apps will stop working. Thanks

Warning! Please read the note at the bottom first: 1) Download from this site and install the latest driver made for your device and operating system to ensure your computer recognizes it properly. 2) Download and install the latest Editor for your device. 3) If you have presets on your device that you don't want to lose, save them to your computer using the Editor. 4) Install the latest firmware using the Line6 Central app, which you can download from this site, and if prompted during the process, choose not to keep any existing presets. By doing this you will also get all the factory presets back. 5) Perform a Global Reset, ie: Power off the POD HD Pro X completely. Press and hold the Left Arrow button on the directional navigation pad. Turn on the power switch while keeping the button held down until the screen indicates a reset or normal boot sequence begins. This action restores all global utility settings and set list names back to factory defaults without erasing your custom user patches/presets. 6) Finally, if you want, reload your previously saved presets. PS If you happen to already have model pack add-ons installed on your device, I don't know if they'll be retained after reinstalling the firmware if your Line 6 account is different from the original purchaser's. From what I understand, the app that normally handled license activation/deactivation was discontinued about a year ago and was called License Manager. So theoretically, it shouldn't be possible to activate or deactivate model packs at this time, but I'm not entirely sure. However based on what officially written here: --> Line 6 Monkey and Line 6 License Manager retiring on April 10th, 2026 If you own any model pack licenses, you must transfer them to your devices prior to April 10th, 2026. After that, model packs are either effectively locked to the devices they are installed on, or they cannot be installed or transferred to other devices. _______________________________________________________________________________________________________________________________________________________________________ All about POD HD500/X help and useful tips

I played at an outdoor festival this weekend on a stage with a canopy, using a sunshade over the Stadium, with the brightness of the scribble strips set to 100%, and still I could barely read the scribble strips. The problem is two-fold. The OLEDs aren't nearly bright enough, and the glass picks up reflections so you have to move around to find an angle where you can read the text. The scribble strips for the active buttons were faint, but they could be seen. The OLED pixels for the inactive buttons are dimmed so they were nearly impossible to read even when I bent over for a closer look. The LED rings around the buttons could not be seen. Had it not been for the canopy, I believe that the Stadium may have been rendered unusable. I submitted a support ticket a while back about the poor visibility of the scribble strips. I doubt that they can turn up the brightness much without damaging the OLEDs, but there are some things that could be done to improve the visibility. My suggestion is that they could create a "performance" setting which eliminates dimming of the inactive buttons. Instead, all OLEDs would be at maximum brightness, and the active buttons would have the pixel colors inverted to designate the buttons which are active. Something similar to the attached concept image. They still wouldn't have the high visibility of an LCD display, but it would be an improvement. I love my Stadium, but I have a number of outdoor gigs this summer and if I end up in direct sunlight situation, the Stadium may be unusable. I play in three different bands and I'm one of those guys that creates a lot of song-specific presets, so memorizing what each button does in order to use the unit blindly is not an option. I really don't want to do it, but I plan to take my Boss GT-1000 as a backup to all outdoor gigs just in case the Stadium is impossible to use.

Just a thought; If they cannot make the scribble strips any brighter then another possible solution that might make the text more visible is to reverse the colors (white background with black text). It could be a simple global setting. I don't know if this would improve visibility or not, but its something they could try.

I’m having the same trouble as others. Can’t keep it connected to the helix editor for more than 30 seconds max.

Mine periodically disconnects. My WiFi signal is strong, so it must be a bug.

Please add Dante support for the Stadium via the Nexus port! This would add tremendous value to the Stadium for many church musicians. Our church uses Dante for many digital inputs and being able to send stems from Showcase via Dante would be incredible! Without Dante support I am left looking for a way to work around the only current option which is to send 8 digital channels out via the D10 through optical. I would need to somehow convert the TOSLINK optical to 8 XLRs via some sort of stage box. I suspect this would be expensive, bulky, and impractical. A Dante out where I could have 8+ audio channels would be awesome!! This is what I am currently doing with my Helix. I am sending two mic channels out of the XLR's for vocal and talkback. I am sending two digital outs via the AES to a Dante AVIO converter for my guitars and keyboard. We are running click and track through a MacBook running Ableton. I would love to consolidate all of these through Stadium with Dante output!

Don't you mean 'not really what I am waiting for'? Not sure how you can extrapolate to 'most people'. I happen to prefer the Grammatico and am certainly not waiting for another high-gain amp/channel.

All four have to be matched, so all four have to be replaced at the same time with a matched set,... in this case, the whole Quad.

Hi I have one tube gone bad in my spidervalve hd100, can I change the bad valve alone, or do I need to change a pair or quad. In most valve amps the valves are working in pairs so i'd expect to replace a pair of tubes not a whole quad.

Tube choices to use,... Spider Valve: 12AX7B China for pre-amps. 5881WXT Sovtek (matched pair), with the base cup bottom. 5881WXT Sovtek (matched quartet), with the base cup bottom for the HD-100 and HD100 MkII. Soft, medium or hard, the ratio between vacuum-to-inert gas in the tube,... all tubes used have to be mediums. Low microphonic 12AX7EH for the pre-amp is fine. Power amp tube choices are crucial, and must be properly biased by a tech or Line 6 authorized service center who knows the product. Don't do this yourself, the shock hazard is too great,... and it hurts when you get electric shock. Leave it to a tech trained who is for this. These valve amps are particular about tubes and tube brands. Do Not use substitutes, No Mesa, Groove Tube, Tung-Sol, Ruby or JJ substitutes. No hot rodding of an already Bogner hot rod.

1) On the JTV-59 Bridge, Loosen the small Allen "set-screw at the back of the tailpiece" first 2) Raise the bridge by inserting the correct larger size Allen wrench into the top of the bass side bridge post 3) After the action is set the way you like, re-tighten the small Allen screw from step #1