Ledtranceguy Blog, LEDs, Trance and other EDM, and Festivals


vvv Click on the categories below to see other topic specific pages vvv




More pages: November 2026 October 2026 August 2026 July 2026 June 2026 May 2026 April 2026 March 2026 February 2026 January 2026 December 2025 November 2025 October 2025 September 2025 August 2025 July 2025 June 2025 May 2025 April 2025 March 2025 February 2025 January 2025 December 2024 November 2024 October 2024 September 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 October 2023 September 2023 August 2023 July 2023 June 2023 May 2023 April 2023 March 2023 February 2023 January 2023 December 2022 November 2022 October 2022 September 2022 August 2022 July 2022 June 2022 May 2022 April 2022 March 2022 February 2022 January 2022 December 2021 November 2021 October 2021 September 2021 August 2021 July 2021 June 2021 May 2021 April 2021 March 2021 January 2021 December 2020 November 2020 September 2020 July 2020 March 2020 February 2020 January 2020 December 2019 November 2019 October 2019 August 2019 July 2019 June 2019 May 2019 April 2019 March 2019 February 2019 January 2019 December 2018 November 2018 October 2018 August 2018 July 2018 June 2018 May 2018 April 2018 March 2018 February 2018 January 2018 November 2017 August 2017 July 2017 June 2017 May 2017 April 2017 March 2017 February 2017 January 2017 December 2016 November 2016 September 2016 August 2016 June 2016 May 2016 February 2016 January 2016 November 2015 September 2015 August 2015 June 2015 January 2015 September 2014 August 2014 May 2014 September 2013 May 2012 January 2012 December 2011 August 2011 July 2011 May 2011 January 2011 December 2009 November 2009 April 2009 March 2009 October 2008 May 2007 November 2006 October 2005 September 2005 November 2004 October 2004 September 2004 August 2003 July 2003 February 2002 November 2001 October 2001 September 2001 July 2001 June 2000


Welcome to the Trance/EDM/Festival/LEDs sub-section of my blog


If you enjoy random EDM events and festival pictures and/or want to connect: And if you are curious about my LED outfit, you can read more about it on my led peacock engineer medium post and if you'd like to read all my festivals or dreamstate, or clubbing posts, please click on the links higher on the page to get taken to those categories.






π 2026-11-14 01:01 in Clubbing
This was a dreasmstate pre-party and double night, first went to Great Northern to see Blurr, I hadn't been there is a while, still great decors:









I would have stayed longer, especially see my friend Khromata, but it was time to head out to go to Public Works to see Dave who had gone through hell and earth across the FAA plane meltdown to fly to San Francisco:







π 2026-11-06 01:01 in Arduino, Electronics
This was my 3rd time in Pasadena Hackaday Supercon, and it was their 10th year. I'm sad I didn't go the other 7 years :)

I came suitably equipped with blinkies :)
I came suitably equipped with blinkies :)

New venue this year, bigger and nicer:


in the college of design
in the college of design


cool car designs
cool car designs

Many people will cool things ;)

working hard
working hard





nice custom PCB, well done
nice custom PCB, well done


I need to carry my batteries like this when I board planes :)
I need to carry my batteries like this when I board planes :)



I setup shop for the day, working on ESP32 MatrixPortal networking:


I found out my batteries need anti-stress protection
I found out my batteries need anti-stress protection

hot glue to the rescue
hot glue to the rescue

And cool stuff:





The badge this year was a bit eink screen, very cool



it came with very cool art
it came with very cool art

people made cool hacks
people made cool hacks

I just had enough time to add my name and face
I just had enough time to add my name and face



some people took the job seriously
some people took the job seriously

and what's a badge without SAOs
and what's a badge without SAOs

I went to multiple workshops:



cool idea, changing RF into sound
cool idea, changing RF into sound

back at blingiton
back at blingiton

this time I had to port my code to an RP2350 which was much more challenging than planned
this time I had to port my code to an RP2350 which was much more challenging than planned

Talks:






I did a lightening talk for Framebuffer::GFX:


and how I got to meet so many DJs thanks to it
and how I got to meet so many DJs thanks to it

action shot, with my older code that didn't refresh the badge quickly enough
action shot, with my older code that didn't refresh the badge quickly enough

I went for the badge competition, but didn't win despite having networked badgeds running demos across multiple chips, including an RP2350 from the new BlingItOn workshop, whicn I barely got working after 24H of loads of work with 18mn to spare :)


Then it was time to hang out at a bar to close the weekend:



Good times, looking forward to next year

See more images for Pasadena Hackaday Supercon 2026
π 2026-11-01 01:01 in Arduino, Clubbing, Festivals
I upgraded my LED outfit from 64x96 to 128x192 over 5 years ago, increasing the resolution 4 times, which allowed me to show much better graphics. During that time, I still had an old off the shelf 64x64 P3.5 LED panel which was nice and thin, and not too power hungry. But the remote software was not great, and the memory was limited. Also, they were old style circuit boards that did not like any flexing and broke easily (I have literally broken more than 10 of those in the last 10 years or so).

End result


And these are the old 64x64 panels:

with 64x64 P3.5, you can of course see the bigger pixels
with 64x64 P3.5, you can of course see the bigger pixels

as I mentioned, they broke easily
as I mentioned, they broke easily

here the bottom right corner is broken
here the bottom right corner is broken

Story

For a long time, I had been wanting to run my own code on my LED backpack, but I also wanted higher resolution, so I held off. While I was at it, I also wanted my backpack to be synced with my LED outfit, so after I did the work to make my LED Outfit v8 with independent front and back screens that are not connected physically (they do share power for convenience reasons), the same wifi code that keeps them in sync was now easy to add to an external display like one in a backpack, so the only thing left was to get said display.
For size reasons, LED backpacks are sized to work with P3.5 64x64 panels, which also means they work perfectly with P1.875 128x128 panels. My only need was to find some that were bright enough and would not break right away. This is where Hongren Su from Azerone, who has been my trusted panel seller for years now, got me 2 sets of P1.825 PWM panels (they run a different PWM chip), which ensured they'd have high refresh rates and work pretty well in daylight too. Thankfully, earlier this year, kindgoc9 made a fork of the hzeller RPI RGB Panel code, and added support for enough PWM panels that both kinds I got, just worked.

First, I had to significaly improve the robustness of my wifi code, which took a bit of time as the ESP32s like to save power but in the process woudl also lose broadcast packets I used to discover other screens. Google gemini helped figure this out, and with my guidance, I made some more robust code that works most of the time. Most of the time is because unsurprisingly, I found at a festival that there can be so much RF noise, that my ESP32 AP is not visible by the other chips, or my phone, so I'll need to implement some workarounds for that, but otherwise it worked well.

First, I had to find some driver settings to get around some display issues, and found that adding a higher GPIO slowdown, fixed it:


Before long, I got my 3 LED panel displays to sync, plus 2 smaller 128x128 backpack ones:




wrote some extra code to shrink the graphics on 128x128 displays
wrote some extra code to shrink the graphics on 128x128 displays

I buitl 2 different kinds to see what would work best. This pre-made panel was great since it would be bulletproof and not bend, but there was no room to add my electronics:


the other bad news is that it's pretty battery hungry and I need 2x70Wh for a full night
the other bad news is that it's pretty battery hungry and I need 2x70Wh for a full night

the panel + 2 LED strips took around 100Wh for 7H, pretty hungry but 2 70Wh batteries do the job
the panel + 2 LED strips took around 100Wh for 7H, pretty hungry but 2 70Wh batteries do the job

for comparison, my full front and back outfit (without extra LEDs) took 125Wh for the same 7H-ish
for comparison, my full front and back outfit (without extra LEDs) took 125Wh for the same 7H-ish

not the most professional setup, but ok for the first time ;)
not the most professional setup, but ok for the first time ;)

my 2nd prototype uses raw panels and a nice metal frame done by Hongren Su from Azerone
my 2nd prototype uses raw panels and a nice metal frame done by Hongren Su from Azerone


the 2 kinds of panels look the same from the display side (and yes, they work with USB packs that can do 12V USB-PD)
the 2 kinds of panels look the same from the display side (and yes, they work with USB packs that can do 12V USB-PD)

Power Use

That was the tricky part. For comparison, the 64x64 ones I made run by just an ESP32 S3, used 1.5W of power or so. The first version of the rPi one, was taking 12W (!)


So to lower that down, I did this:

  • I had 2 kinds of PWM panels, the one without shift register used 2W fewer, easy win
  • I downgraded the Rpi3a to an Rpi0 2wl, that was another watt or so, saved
  • The step down converters, I had a tobsun that was big, and a nice and flat 16A BEC, but it took 1W more :(
  • And then I realized that I got the entire thing below 10W even on bright displays, that USB-C can give 3A/15W on 5V, so I just skipped the step down and powered with straight 5V from the battery pack
  • This got the whole thing down to 5-7W dependind on how bright the display, is:


    almost 10H runtime, great news!
    almost 10H runtime, great news!

    And the great news is I was able to empty an entire 60Wh pack, and it worked for 9h49mn, which enough for most nights.

    π 2026-10-30 01:01 in Clubbing, Festivals
    Insomniac never sleeps, they have so many festivals, plenty of which I haven't seen yet, even though if my count is correct, this was my 97th festival since I started doing this 23 years ago ;) (this is only counting multi-artist real festivals, I had to exclude things like Armin only or Tiesto in Concert as they don't qualify), so I was curious to check out Escape after hearing great things about the decor and of course, the costumes that people bring for Halloween (I did remember the LA crowds for Halloween for Monster Massive back in the days).
    Of course, it was at the familiar San Bernardino NOS, which I still enjoy and have fond memories of, from former Dreamstates and Beyond Wonderland. Yeah, SBD is not the nicest city, but it feels safe enough, especially compared to south central LA/Banc of California area :)


    Grounds

    So, how was Escape? It felt like a Halloween Beyond Wonderland, and I mean that as a good thing: wonderful decor on a different theme obviously and the layout was familiar:



    Thankfully Day 1 had rain just before the festival, but not during, so it was pleasant to get around:

    welcome to escape
    welcome to escape



    the voodoo room was beautiful
    the voodoo room was beautiful





    beautiful spider
    beautiful spider

    Hi Insomniac folks, little mistake for this one, the VIP wifi password wasn't posted anywhere, I had to get a picture of a picture of a picture from someone working there. On the plus side, since barely anyone had the password, Wifi worked great ;)


    Insomniac continued to put great effort into Passport, rewarding its most loyal members:





    Props for the burning man art:




    and it worked under the rain
    and it worked under the rain

    They had multiple performing stages, including a huge outdoor one, where the performers continued under the rain, props to them:


    And OMG, the monkey from mainstage was absolutely impressive:




    Day 1 without the rain, allowed for drone shows






    The People

    Insomniac festivals are of course fun because of the people, but even more so during Halloween:









    For me, it was also a special test day, the first time I got to try the new LED backpack I just designed to be a similar resolutino than my LED outfit, and synchronize over Wifi (which was challenging as Wifi sometimes got overwhelmed by the festival RF noise):


    4 displays in sync, outfit front and back, and 2 backpacks :)
    4 displays in sync, outfit front and back, and 2 backpacks :)


    Remote Demo

    I got to meet another LED euthusiast who had the exact umbrella I needed ;)


    Festival

    Day 1 was the best day since the weather was quite nice. Day 2 sadly had near constant rain, as predicted, so at least I was ready:

    arrived just before sunset, not many people, yet
    arrived just before sunset, not many people, yet








    Conclusion

    Yes, there was literally 0 trance, I knew that. Honestly this festival had not been on my list before as none of the music was really stuff I enjoyed that much, but verious kinds of EDM, some a bit more fun then others, but Crazy Frog was heard more than once ;) Jokes aside, it was pretty enough and had enough entertainment that I'm glad I went.

    The rain on day 2 sucked, it was mostly non stop, but thankfully light rain. Also the main stages were covered, so you only got wet while going around between them. And unlike Ultra Miami that had a ridiculous policy to not allow umbrellas despite torrential rain, Insomniac did allow them thankfully (and some were even beautifully decorated with LEDs). All the festival gear and stages kept working, even the outdoor stage with cabaret and burlesque shows kept going, huge thumbs up to the performers!

    The rest, I'd compare Escape to Beyond Wonderland at NOS: solid festival with beautiful decor and plenty of costumed staff that really added to the atmosphere. It's another solid festival from Insomniac. The only thing that felt missing was the lacking wifi (cell was mostly not working, not convenient to find lost friends, or call an uber) and as I mentioned the VIP wifi that was not published anywhere, so it was difficult to know what the password, was. Yes, make fun of me for wanting to stay connected :) (although jokes aside, it's impossible to make correct IG stories without connectivity when you cannot expand tag or location names).

  • Video summary:
  • Photo Album
  • Instagram Stories
  • π 2026-10-15 01:01 in Electronics, Hiking, Linux

    Making Garmin MTP units like Montana 710 not immediately shut down when plugged into a linux machine

    This is a bit of a long page, so the TLDR, is:
    Create /etc/udev/rules.d/99-garmin-passthrough.rules with
    ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="091e", ATTR{power/control}="on", ATTR{power/autosuspend}="-1"
    

    save and run "udevadm control --reload-rules; udevadm trigger"

    this ensures linux will not autosuspend the port which in turn causes the montana not to shut down, allows virtualbox to grab the port, hand it over to windows, and have basecamp work again. Yeah!

    So many Crashes and Bugs with Montana 700

    I have been a Garmin GPS user for over 20 years, starting with a Vista, upgraded to Oregon 700 and stayed with that for many years until they were discontinued, and my last one died. From there the Montana was the only Garmin GPS with a touchscreen and reasonable on screen keyboard to create new waypoints on the fly when I travel, so despite its size and weight (both too big compared to a more capable cell phone), I went with that.

    The Montana 700 worked just like the ancient Vista HCx, it emulated a usb storage drive when you plug it in USB and I could mount it on linux as a drive, move files around like gmapsupp_xxx.img files when I had too many and wanted to hide some to avoid overwhelming the GPS. Also, it was easy to just copy all the tracks to linux and store them forever (I have all my tracks from the last 20+ years, you never know, haha).

    This is also the time garmin introduced garmin explorer that was meant to sync all the tracks and waypoints of your GPS to the garmin cloud. It's a great idea in principle, in practise it was written poorly and never fixed in the last 2 years I've seen it, so with lots of tracks and 4000+ waypoints, I got:

  • over 24H to sync the waypoints to the cloud through some inefficient one by one copy with huge latency between each. Sad...
  • the copy/compare/sync is unreliable so it eventually duplicated all my waypoints both in the cloud and on my unit. Terrible....
  • at the same time, it likely had bugs or a memory leak that caused my GPS to shut down while I was recording tracks, leaving me with lost tracks when the GPS shut down, even more sad
  • I unfortunately confirmed that anything that causes an OS or serious application error that can cause a coredump (I'm going to guess it's not a memory protected OS and dates back to windows 3.1 memory management days), the unit shuts down and stops recording instead of rebooting
  • during that time the web explorer cloud site never had a properly working export mode where I could download all my data in a simple GPX file. The file would miss track names, or waypoints, or waypoint types. It's really not so hard to write something like this but as of this writing it's still broken in different ways and apparently not a priority to fix
  • turning off garmin explore fixed many of the crashes with the Montana 700, even if it brought it back to the level of an Oregon 700, however I found another vexing bug where when recording a track for multiple days while plugged in, usually a moving diving boat, the unit would shut down on its own after a day or two and stop recording too, losing part of my track.
  • I even got the unit/software to be wedged enough that the power button would register a beep as normal, but refuse to shut down the unit, to the point that I had to remove the battery to force a shutdown.
  • During all of these issues, I got coredumps, but while I was hopeful they would allow garmin to fix their software and OS (even with bad/corrupted maps or unexpected data, the unit should never crash). Unfortunately, since it's probably not a full OS with full memory protection and the software is not written to withstand imperfect data, as far as I know, nothing I reported, ever got fixed. It's also possible that they were just memory overflows with no protection either, and this example below clearly shows code was allowed to corrupt data (here sprites):

    All that said, while nothing I reported got fixed, not even the unit rebooting after a crash instead of just shutting down, garmin support did their best to help, even if nothing may have happened in the end. As part of that, they did rule out bad hardware by replacing my 700 twice, and after I still got more problems, all the way to the unit refusing to shut down, they gave me one more swap to a garmin 710 which is new hardware and upgraded to USB-C (I was indeed surprised that the 700 upgraded from super obsolete mini-USB to pretty obsolete micro-USB, and didn't have USB-C yet).

    Stopping using 3rd party openstreetmap gmapsupp.img files and moving to Garmin Topoactive data

    Unfortunately none of the coredumps gave any clue if we were hitting hardware bugs, or software bugs, and whether they were linked to the openstreetmap maps I was using when travelling in other countries. This is where I have to thank Leslie and Elizabeth from garmin support for pointing out that topoactive maps that were added in the last years are actually free repackaging of openstreetmap data in a way that has been verified not to crash the garmin software. This is not to say that the openstreetmap maps I was used to getting from the net, were crashing the montana, but it's technically possible. Big bummer that the many coredumps I gave never got anyone to say why the unit was crashing and whether it could be linked to bad map data. That said, the new topoactive data is much simpler to get than what I was doing manually and moving to the sdcard in a bunch of gmapsupp_country.img files, so I happily switched to that. Links:
  • https://support.garmin.com/en-US/?faq=24WYX2WS2aAJvm5lYQgAM7
  • https://support.garmin.com/en-US/?faq=UXl1PP15829qvEX6jdqekA
  • Upgrading from Montana 700 (usb-storage) to Montana 710 (MTP)

    At the same time, Garmin kindly authorized upgrading me to a Montana 710 at their cost, which I assume they did without ever being able to figure out if the 700 hardware was it fault. At the same time, I vouched to fully switch to topoactive maps, which is actually one great thing garmin implemented and that I'm happy to switch to.

    However, I still need to get the data off it (tracks and waypoints) and cannot use garmin explorer as explained above due to how broken it is, so I still need to use garmin basecamp in virtualbox with my windows 7 image, the last ok-ish windows :)
    When switching to USB-C garmin also switched from USB-storage (drive emulation) to MTP, which is reasonable. Linux has supported MTP for over 10 years, and it also works in windows 7, so no problem in theory. In practise, everytime I plugged the GPS in and activated storage mode (when using garmin spanner mode so it asks me before doing so), the GPS said it was switching to usb-storage mode, and then would shut down.
    When plugged in a real windows machine (not through virtualbox), it worked perfectly fine, and I tried with 7 other linux machines, including one 15 years old with a very old linux kernel, and each time it shut down, bummer.

    By then, I was pretty screwed because I did need basecamp and virtualbox to work, and eventually google gemini looked at the logs before shutdown:

    kernel: [94868.932764] usb 3-5: new high-speed USB device number 34 using xhci_hcd
    kernel: [94869.136992] usb 3-5: New USB device found, idVendor=091e, idProduct=0003, bcdDevice= 0.01
    kernel: [94869.136998] usb 3-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    kernel: [94869.740855] usb 3-5: reset high-speed USB device number 34 using xhci_hcd

    Turns out the problem was this, as explained by The entire crash and shutdown loop was driven by the kernel's runtime USB autosuspend dropping link power at the 2-second mark.

    When no host kernel driver binds to the interface, the kernel suspends the port. The Montana firmware interprets that link drop as a physical cable disconnect, terminates storage negotiation, executes an emergency waypoint flush, and turns off. Keeping the link energized via ATTR{power/autosuspend}="-1" completely resolves the failure mode, allowing any VM to claim the device without racing against link power down.

    The montana is wrong, but garmin support made it clear that because it works on windows, they were not super interested in diagnosing or fixing it. Maybe with this page, they'll consider a fix, but in the meantime, the workaround is this:

    Create /etc/udev/rules.d/99-garmin-passthrough.rules with ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="091e", ATTR{power/control}="on", ATTR{power/autosuspend}="-1"

    save and run "udevadm control --reload-rules; udevadm trigger"

    this ensures linux will not autosuspend the port which in turn causes the montana not to shut down, allows virtualbox to grab the port, hand it over to windows, and have basecamp work again. Yeah!

    now it works
    now it works

    basecamp loading maps via MTP in virtualbox on linux
    basecamp loading maps via MTP in virtualbox on linux

    MTP shows both filesystems, the built in storage and sdcard
    MTP shows both filesystems, the built in storage and sdcard


    More pages: November 2026 October 2026 August 2026 July 2026 June 2026 May 2026 April 2026 March 2026 February 2026 January 2026 December 2025 November 2025 October 2025 September 2025 August 2025 July 2025 June 2025 May 2025 April 2025 March 2025 February 2025 January 2025 December 2024 November 2024 October 2024 September 2024 August 2024 July 2024 June 2024 May 2024 April 2024 March 2024 February 2024 January 2024 December 2023 November 2023 October 2023 September 2023 August 2023 July 2023 June 2023 May 2023 April 2023 March 2023 February 2023 January 2023 December 2022 November 2022 October 2022 September 2022 August 2022 July 2022 June 2022 May 2022 April 2022 March 2022 February 2022 January 2022 December 2021 November 2021 October 2021 September 2021 August 2021 July 2021 June 2021 May 2021 April 2021 March 2021 January 2021 December 2020 November 2020 September 2020 July 2020 March 2020 February 2020 January 2020 December 2019 November 2019 October 2019 August 2019 July 2019 June 2019 May 2019 April 2019 March 2019 February 2019 January 2019 December 2018 November 2018 October 2018 August 2018 July 2018 June 2018 May 2018 April 2018 March 2018 February 2018 January 2018 November 2017 August 2017 July 2017 June 2017 May 2017 April 2017 March 2017 February 2017 January 2017 December 2016 November 2016 September 2016 August 2016 June 2016 May 2016 February 2016 January 2016 November 2015 September 2015 August 2015 June 2015 January 2015 September 2014 August 2014 May 2014 September 2013 May 2012 January 2012 December 2011 August 2011 July 2011 May 2011 January 2011 December 2009 November 2009 April 2009 March 2009 October 2008 May 2007 November 2006 October 2005 September 2005 November 2004 October 2004 September 2004 August 2003 July 2003 February 2002 November 2001 October 2001 September 2001 July 2001 June 2000

    Contact Email