Free Update: Resolume 4.1.2 The Empire Strikes Bug
Free Update: Resolume 4.1.2 The Empire Strikes Bug
This update shows again that at the end of the trilogy, the light side always triumphs. We caught a lot of bugs, and we blew up the Death Star. We defeated Darth Midi Lag and toppled the evil Emperor Syphon Crash. We even freed Han Solo from the clutches of Jabba the VST Plugin Not Showing Up.
We're still not okay with kissing our sister though.
Free download here and check the release notes below. May the force be with you. Always.
[NEW] Modify default clip behaviour in the preferences
[FIXED] Syphon crashes Avenue on OS X 10.5
[FIXED] Crash: Right-click the clip playhead on the layer when no clip is playing
[FIXED] Crash: Set negative mask width or height in Advanced output
[FIXED] Possible crash when removing layers
[FIXED] MIDI starts lagging over time with composition midi map
[FIXED] Layer opacity composition MIDI shortcut can not be removed
[FIXED] Composition MIDI shortcuts get duplicated on startup
[FIXED] Timecode sometimes only plays clip in one layer
[FIXED] SMPTE framerate setting not remembered
[FIXED] Arrow keys change blend modes after you select a layer or select something from a dropdown
[FIXED] When adding a layer with shortcut CTRL+L while midi mapping, 2 layers are created
[FIXED] Dashboard linked parameter is not movable anymore by mouse/MIDI/OSC
[FIXED] MIDI output not always working for layer focused shortcuts
[FIXED] Dropping a VST effect before another effect doesn't list the effect
[FIXED] Order of VST effects changes randomly after saving and reopening
[FIXED] Crash: Relocate AV files then reset the in/out point by right clicking
[FIXED] Crash when pressing relocate in the layer window, while the clip has been ejected
[FIXED] Memory leak with Relocate window
[FIXED] Crash when sending a LOT of MIDI and then opening advanced output
[FIXED] Update FFGL and VST plugin folder locations after update
[FIXED] Possible crash on startup with OS X Capture devices
[FIXED] VDIG capture devices are throwing errors that crash resolume
[FIXED] Crash when loading composition with a mask that points to an unexisting file
[FIXED] Middle C now actually like, correct and stuff
[FIXED] Crash when sending layer to slice and using active layer triggering
[FIXED] Alpha not always showing correctly when using advanced output
[FIXED] Retriggering a clip via DMX is not possible
[FIXED] Relocate window does not appear when loading a deck from a different composition
[FIXED] Multi-clip deselect not always working
[FIXED] When a copy of a slice is made the original will stay selected
- Tschoepler
- Posts: 467
- Joined: Fri Mar 13, 2009 04:26
Re: Free Update: Resolume 4.1.2 The Empire Strikes Bug
Now who's your daddy!


████▀ ▄█ tschoepler.net █████ zweifarbton.net █▄ ▀████
Re: Free Update: Resolume 4.1.2 The Empire Strikes Bug
Update fixed the horrible APC40 Lag! Arena is usable again! AWESOME! Thank you!!!!!!!
Re: Free Update: Resolume 4.1.2 The Empire Strikes Bug


Re: Free Update: Resolume 4.1.2 The Empire Strikes Bug
Thanks for the update!
Why not store FX somewhere outside the Application folder, and just add/overwrite them if they need to be updated?
It replaces the whole old config (4 custom plugin locations) with one new pointing to the Resolume defaults. Please don't wipe out the pointers to my other FFGLs when updating! PLEASE![FIXED] Update FFGL and VST plugin folder locations after update
Why not store FX somewhere outside the Application folder, and just add/overwrite them if they need to be updated?
Re: Free Update: Resolume 4.1.2 The Empire Strikes Bug
I hate to be the bearer of bad news, Rene, but we felt that experienced users like yourself are able to figure out that the folder locations are gone, and are knowledgable enough to replace them.
However, novice users resort to all sorts of unnecessary panic reactions when they find out all the effects and blend modes are gone. Every update, our inbox is flooded with dozens of these mails, and we figure that an even larger amount doesn't take the time to write and is needlessly frustrated by fruitless reinstallation attempts.
We do not update excessively often, so we hope you can find it in your heart to take a minute to add your source locations again after an update.
However, novice users resort to all sorts of unnecessary panic reactions when they find out all the effects and blend modes are gone. Every update, our inbox is flooded with dozens of these mails, and we figure that an even larger amount doesn't take the time to write and is needlessly frustrated by fruitless reinstallation attempts.
We do not update excessively often, so we hope you can find it in your heart to take a minute to add your source locations again after an update.
Re: Free Update: Resolume 4.1.2 The Empire Strikes Bug
Hey Joris,
of course, I can and will re-setup my config - as I did every time since Resolume 3.0.0. And nonetheless I'm happy about every new update. Really!
The reason for my initial request was, that I could not believe that I'm the only one who is annoyed with this little issue - at least all the Mapio users must have faced the same little bug again and again (obviously they just fixed it instead of complaining). But if nobody says a word, nothing will ever change.
So in future I will re-setup my config knowing that at least I tried.
Also I'm aware that you guys have to work on other much more important extensions, updates, and bug fixes (maybe that's why I didn't ask for improvement until 4.1.2?) and please keep on the good work, and maybe some day somebody will pick this low hanging bug-fix fruit...
of course, I can and will re-setup my config - as I did every time since Resolume 3.0.0. And nonetheless I'm happy about every new update. Really!
The reason for my initial request was, that I could not believe that I'm the only one who is annoyed with this little issue - at least all the Mapio users must have faced the same little bug again and again (obviously they just fixed it instead of complaining). But if nobody says a word, nothing will ever change.
So in future I will re-setup my config knowing that at least I tried.
Also I'm aware that you guys have to work on other much more important extensions, updates, and bug fixes (maybe that's why I didn't ask for improvement until 4.1.2?) and please keep on the good work, and maybe some day somebody will pick this low hanging bug-fix fruit...