2.4.4 Is here to address some of the bugs people have been finding in the last release. Hope this solves most of the issues that have been holding people back from using the previous patch!
Patch notes:
Presets now recall correctly again
USBs with over 50 videos dont crash anymore and switch correctly
re tested usb webcam inputs are still correctly selectable
bugfixes for elektron device 0vel noteons
bugfixes for mezzz “hypno mode” echoes for Mezzz 1.4
It now starts out in 640 resolution instead of 720 like before. I play with the “Render Resolution Scaling” settings and can only get it to go to lower resolutions, but never up to 720p. Is this expected?
Also when I tweaked the resolution settings for a bit, the entire system crashed and just says something about “Failed to start /etc/rc.local Compatibility”.
I didn’t see this in the release notes, so I guess these issues are not addressed in 2.4.4?
720p means 1280×720p and Hypno has never run at this res, it also hasn’t displayed the resolution in most previous versions, Hypno’s engine runs at a max of 720x480p, otherwise it chops the resolution down to fill widescreens and other aspect ratios so the max is different depending on which screen is hooked up.
To clarify; youre experiencing a crash when switching resolutions in engine or using the config setting to force a resolution (that was added last patch)?
Got it thanks, u used to get 720x480 on the last 2.4 release with thesame display plugged in on this CM3 unit? This readout only got added last patch.
I dont believe the resolution negotiation changed on the pi3 in a long while, I was debugging the pi4 based units mostly, so id be surprised if this changed.
Sorry but I don’t remember what version I was running before I installed 2.4. It was probably a year since I upgraded. Prior to 2.4 I never saw any resolution indicator, but the bootup screen always displayed fine.
Since I installed 2.4 the bootup screen is cropped and I’m unable to read a portion of the text during bootup. After booting is complete I see a readout of resolution: 640x360. I am unable to configure a higher resolution. I assume these 2 issues are related.
Was successful in getting the cut down 2.4 pi3/cm release onto my original hypno, but balena is complaining that 2.4.4 is too big to fit. Tried it on two first gen Hypnos and same deal.
Personally enjoying the increased performance of the video sampling function. Mezzz integration is super fun and adds a bunch of extra control, amongst others.
So give the update another go, perhaps from a different perspective.
@Intelligence.Limited Your username is quite an accurate description of you huh? The benefit of offline hardware is that theres no pressure to update whatsoever so DON’T, another is that you can divest and sell your unit at any time. There are no significant features/bugfixes in these last few updates for pi3 variants so just move on.
There are 4 variations of the Hypno hardware (more if you count different eMMC sizes) and we cant even build new CM3 Hypnos for testers since it was surprise discontinued by pi foundation in 2020 so yeah things slip through.
I recently did budget time for testing to help find issues but yes the scale is small enough that I can’t pay a team of experienced testers and I can’t rly demand deadlines on volunteers’ work cuz thats not cool either (the people on the beta channel on chat). I am very thankful to have some awesome talented people on the team, here on forum and on that beta channel now and usually issues get ironed out or flagged in the first couple of weeks of the firmware’s release.
Well done giving me another instance of regretting starting a forum. There I go wasting my time with a reply. Now I’m seriously considering taking this site down entirely as its wasting both of our time.
The rest of you please hang tight for the smaller image ( these images take a while to rebuild/export ), I had my smaller eMMC in my CM3 Hypno and didn’t realize, my b.
I would happily deliver, in person if you’re near portland, my cm3 hypno for your team to test with in exchange for a suitably discounted pi4. I have 3 now, 2 cm3’s and a pi4. One of the 3’s is in a eurorack with a sensory translator and the other i promised to a friend (at hefty discount due to pi4 upgrade). So i have a vested interest in keeping my eurorack version going and it’d be sweet for my friend to get a new pi4 instead of an old cm3. Let me know if you’re interested.
Correct currently 1 UVC device is available at one time so capture card/webcam switching isn’t possible at the moment but I agree this would be a good addition.
@hitek Can you remind me how large your eMMC storage is on your CM3? I just received a very early CM3 based unit (batch 1 I believe, before I was doing proper serials) and was able to flash the latest firmware on it as it was the 32GB eMMC. Problem is that I forgot to document all the eMMC sized that have been shipped but I was the under the impression it was 32GB variants and thats certainly working for me.
I am preparing a larger community post with updates on the hardware lifecycle but a quick good news is that I have tested the CM4s and it is working with the old CM3 DIMM slot boards so if your eMMC is not large enough this may be a good option moving forward (w/ a slight accompanying performance boost for decoding video which is nice). I have uploaded a composite image for this on the wiki so that the hardware composite jack is working in this setup.
Both my CM3’s report 31.3GB in Balena. The boards are marked v4 and v5 on mine with the v4 having a printed SN (YH1062), and the v5’s SN is in sharpie (YH1418).
Currently both run 2.4 as 2.4.4 is too big.
P.S. Where can I buy a RPI CM4S? I couldn’t find the SODIMM version on Mouser’s site and the page you link to doesn’t show where to buy it. Any ideas?
I just tried to uncompress the image on my second mac (I have 2 Airs in house) and sure enough Balena did tell me that the CM3 the image was made from is too small which is quite frankly absurd, perhaps this could be some sort of strange bug…
However Etcher did seem to still allow me to flash from the compressed (.img.gz) image, strange but worked just fine. I guess this is what I did for the recent repair. Does this work for you?
I ordered CM4S from waveshare.com; The disadvantage of upgrading is that the composite/hdmi outs no longer switch automatically.
I have just made, tested flashing and re-uploaded the same CM3 image and hopefully this doesn’t happen with this image? → Dropbox
(if you can confirm I will put the link on the wiki also)
I can confirm on my windoze box that the Reup image is smaller (31,268,536,320) than the previous one and successfully flashed to my CM3 from the compressed image. I didn’t try flashing from uncompressed. I will say it took an extraordinarily long time and I had to skip the verify at the “finishing” stage as it was taking forever. I’ll try flashing my other one from uncompressed image and report back.
Any ideas?