build 1.0.24 does not work

[ListeningGarden]

hey all,

i just grabbed build 1.0.24 to play around with the new ghost echo feature, but the build itself seems to be completely broken. it will not load audio from a file to play it, nor will it process audio through the input feature directly from a daw. almost all of the windows and dropdowns appear to be nonfunctional as well - the effects tab simply shows a blank list of "item" names, the samplers do not show any graphs, and so on

i experience the issue loading the latest build available through github, directly loaded into cabbage as well as any standalone/vst builds. happy to provide any additional help/testing/info if needed!

[micah-frank-studio]

Ah - be sure to grab the latest Cabbage Build and let me know! https://dev.azure.com/rorywalsh/cabbage/_build/results?buildId=2443&view=artifacts&pathAsName=false&type=publishedArtifacts

[ListeningGarden]

updated to the latest installer at that link as i was still using the public build (2.8.0) and lore itself now loads and process audio properly, but unfortunately not completely out of the woods yet! whenever i try to load ghostecho, it crashes lore. this happens when running through cabbage directly or with a standalone/vst build

[nlajh]

I compiled Lore 1.0.24 with Cabbage 2.8.145 (that I got through Micah's link mentioned before), and also experienced the issue reported by ListeningGarden that Lore crashes (in Windows 10) when selecting GhostEcho. Cause seems to me in EffectsManager.orc (at the very end).

REPLACING

instr 10, Empty endin

instr 11, Cassette endin

instr 12, Particle endin

instr 13, Cassette endin

instr 14, ImpulseVerb endin

BY

instr 10, Empty endin

instr 11, Cassette endin

instr 12, Particle endin

instr 13, FilterVerb endin

instr 14, ImpulseVerb endin

instr 15, Scrambler endin

instr 16, GhostEcho endin

SOLVED the issue for me. (But I encounter another issue when I add (synthetic or other room) IR (.wav) files into the IRs folder... they are displayed in the LoV of the ImpulseVerb effect, but are not loaded when I select one after -I think- the seventh entry from that LoV. I suppose I have to add them manually to ImpulseTables.orc (and maybe even need to recompile Lore for that?), but it would be nicer ofcourse when Lore would make a list automatically/dynamically, and/or would offer a browse function to an IR file (or similar: (LFO) wavetable when Lore may support that). I also changed for my tests in ImpulseVerb.orc the "cabbageSetValue Scombo1, 4" into "cabbageSetValue Scombo1, 1" to cause that the IR on top will become default, otherwise -with a long list- always the 4th entry will be shown as the default).

Thanks Micah for the work, and also to other testers/users: Good luck!

[micah-frank-studio]

@nlajh @ListeningGarden Hey - so sorry for the delay here - my inbox is just impossible these days 😫 Oh, yeah, how are you updating? Did I not push EffectsManager.orc to the repo? Yep - that seems to be it - will push it again.... sorry!

but are not loaded when I select one after -I think- the seventh entry from that LoV. I suppose I have to add them manually to ImpulseTables.orc (and maybe even need to recompile Lore for that?), but it would be nicer ofcourse when Lore would make a list automatically/dynamically, and/or would offer a browse function to an IR file (or similar: (LFO) wavetable when Lore may support that).

Yes, I think the IRs might be fixed and predetermined in the code - let me see if I can make the system more flexible.

[ListeningGarden]

hey, @micah-frank-studio no worries! things have been a bit hectic here as well.

i've downloaded the updated files from the repo and attempted to render the file as a vst to load into my daw as before. bitwig is unable to load the vst and silently produces an error preventing it from being visible. the error log produced reports the following:

...\VST3\lore\lore.vst3

com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Not a plug-in file

i have downloaded newer versions of the cabbage nightlies, but no build seems to fix the issue

[NFATR]

I've had the same issue as ListeningGarden, Reaper is scanning Lore.vst3 on opening but it's not appearing in plugin window and is repeatedly showing in the "failed to scan" dropdown in plugin menu.

Previous to updating cabbage build, I exported and it scanned fine, ran as plugin but wouldn't load audio files or display any input signal.

[NFATR]

Update: Works perfectly as an AU, issues is just with VST and VST3.

[lamech]

Howdy, FWIW 1.0.25 works for me as both an AU instrument and an AU effect, with latest Cabbage 2.8.155 build.

macOS Monterey 12.8 Logic Pro 10.7.5

[micah-frank-studio]

@NFATR @ListeningGarden Are we on Windows or OSX? I've tested it in Reaper in Windows and I cannot find any issues... If you are on OSX it could be signing issue? 🤷‍♂️

And be sure to pull the latest Lore 1.0.25

And new user guide updated here: https://ec2.puremagnetik.com/Lore%20_%20Experimental%20Sound%20Console%20User%20Guide%201.0.1.pdf

[ListeningGarden]

@micah-frank-studio i'm testing on windows, just to clarify

i have pulled today's update 1.0.27 and have successfully built and loaded as vst/vst3 in bitwig, so i'm going to go ahead and put this issue to rest. thank you 💗