colugomusic
patreon
Blockhead v0.34.0 alpha
🕑 Added 2024-03-04 17:32:39 +0000 UTCVideo explaining the new things
www.youtube.com/watch?v=uWSIRbpt-fk
Update Notes
NOTE: Old project files will be incompatible with this version.
NOTE: I've had one user report that Windows Defender has been identifying crash_dump.exe as a trojan. This is just a tiny program that will generate a crash dump when Blockhead crashes. To do that it needs to adjust the security privileges of the crashing process which is apparently similar to the kind of thing that malware might do so that is probably why Defender is misidentifying it. It's not a big deal if crash_dump.exe gets quarantined by your antivirus or if you want to delete it manually, all that will change is a crash dump won't be generated anymore when Blockhead crashes. I think you can also add an exclusion rule to Windows Defender though I'm not sure how to do it myself.
Feature: Soft snapping. Hold down P to adjust the block snapping amount.
Feature: Block squashing. Press Q to toggle squashing on/off or click the sidebar button. (Note: Macro squashing is currently not implemented.)
Feature: Block shifting. Hold down G and move the cursor left/right to shift the positions of all blocks to the left of the cursor. Hold down H to shift the blocks to the right of the cursor. (Suggestions for better default key bindings are welcome.)
Feature: 'Insert Gap' submenu added to Meta Block context menu.
New command-line argument: '--full-memory-crash-dumps'. If this is enabled then Blockhead will generate a full-memory crash dump when it crashes (as opposed to the smaller crash dumps it usually generates.) The resulting file will be very large and will take a while to generate. Don't turn this on unless you are working with me to debug a crash and I ask you to turn it on.
Bugfix: Crash when an amplitude parameter is set to 'silent' and the decrement arrow is pressed.
Bugfix: Possible crash when sample is deleted.
Bugfix: Braindead performance/memory issue where certain operations would cause Blockhead to make a copy of the entire project state and then store it in memory.
Bugfix: Blocks can snap to the covered end of a truncated block.
Bugfix: Visual issues with block borders overlapping each other.
Bugfix: Changing mute state of an audio source doesn't trigger a rebake of its dependant audio sinks.
Bugfix: Can't scroll down to the bottom of the workspace if the total height of all tracks exceeds the height of the workspace viewport.
Bugfix: Envelope envelope points are not positioned correctly when the left edge of the block falls off the left edge of the workspace.
Bugfix: Block resizer handles don't work right when screen scaling > 1.
Bugfix: Macro open button doesn't move when the macro moves on the screen while not expanded.
Bugfix: Choke shading doesn't update when the block is resized.
Bugfix: Meta block loop button becomes unlit when block changes lane.
Bugfix: Choke envelope block shading does not appear when block is not expanded.
Links
Manual (WIP): https://docs.google.com/document/d/1y6je_g2oNnxClL1eXV20dcQpoyZEkek5LTxQPyEFT0w
Known Issues: https://trello.com/b/MT1A3Zob/blockhead-issues
Discord: Blockhead (discord.com)
Development Videos: https://www.youtube.com/@colugo5172/videos
Comments
Colugo Music
yes i think this one is a bit crashy . so far i have fixed some crashes in the following places: - when blockhead is closed - when a new project is created - when a project is loaded and there are some more crash dumps reported via discord which i haven't looked at yet. i will try to address all of them for the next build.
iurics10
seeing alot of random crashes in this version. (macos version)
Colugo Music
Thanks! I will give it a try. Usually crash_dump.exe is not changing so I assume I wouldn't have to do this often. I haven't had any report of Blockhead itself being flagged as a virus yet, possibly it is safe because it is technically an exported Godot project which might be recognized by MS at this point.
Simon
Re the false positive, I get the same thing with some small utility apps I develop. It's a PITA but for every release I have to: - download the compiled app (even on the machine it was compiled on) - wait a day (Defender will upload it to MS in the background and identify it as a virus) - download it again - it will be flagged with a false positive and quarantined - submit it as a developer at Microsoft Security "Intelligence" and ask for it to be analyzed https://www.microsoft.com/en-us/wdsi/filesubmission - after a few hours, a day, it comes back saying the app is not a threat "at this time" - then wait another day for everyone's Defender definitions to update, then I can release it. Every release, every time.
