Forum Topics Related To Lagrange
Anyone who has posted in a forum topic can add products to its related section.
Simply visit a forum topic and click the:
2 December 2016 at 2:04am
Hi, this sounds really cool, I cant get it to load in FL Studio though. I've tried the vst3 and the dll in 32 and 64-bit mode, but it just gives me an error when I try laod the effect.
2 December 2016 at 6:55am
Hi tx81z, .
Thanks for letting me know and sorry to hear you are having trouble.
The plugin has been tested in FL studio. Indeed a couple of the demo tracks were written with it.
Can you give me more information about the error and perhaps I can help get it up and running for you?
Just to be clear, .
- The current version is 64-bit.
- You will require only the .DLL file taken out of from the zip.
- Place the .DLL file in your VST folder as configured in FL studio here: https://www.image-line.com/support/FLHelp/html/basics_externalplugins.htm#vstfolders.
Please let me know how you get on, .
3 December 2016 at 3:33pm
No luck so far.
I'm using fl studio 12.4 64-bit on Windows 10.
When I scan it with plugin manager the status shows up as 'error'.
It doesdetect whether its 32 or 64-bit though.
I can manually identify it as an effect, then try to use it i nthe mixer but it fails to load.
The debugging log shows this:
Loading project: version 11.5.5
Wrapper says: TVSTPlug.Create - id=0
Wrapper says: Failed to load plugin dll (handle=0)
PDC updated. Latency on master: 2ms.
Mixer threading map rebuilt: 3 layer (s)
Layer 1: 1 unit (s)
Unit 1: track (s)
I tried it on my other win10 machine as well, and with a different VST host.
My only guess is maybe it is relying on some shared library I dont have?
THIS POST HAS BEEN REMOVED
3 December 2016 at 4:12pm
Thanks for getting back to me.
You may well be right about the dlls. I am preparing a new version (0.85) which uses different build options.
Please give this a try and let me know how you get on.
3 December 2016 at 11:19pm
hey thanks for updating so quickly, 0.85 is working for me now.
very cool effect, the built in help was also very useful.
2 December 2016 at 4:03am
From the sound demos I would give it a high note in the KVRDC16 but I'm in 32-bit only and can't actually demo it. Any plans for 32-bit version? I'm in no hurry for changing to 64-bit at the moment.
2 December 2016 at 9:12am
Hi Chris.r, .
For you? anything.
Could I ask though that you let me know if the following works, I lack a 32-bit test machine and I want to be sure it doesn't ask for a bunch of other dlls or hits any other unexpected snags.
If you let me know it's ok I will add it to the zip provided for others.
2 December 2016 at 5:28pm
Haha. This is the most promising reply I ever had in my life! :D.
Unfortunately the download link is not working...
THIS POST HAS BEEN REMOVED
THIS POST HAS BEEN REMOVED
2 December 2016 at 7:34pm
Hi Chris, .
Well, that's interesting. It seems KVR are kindly adding a hyphen between '32' and 'bit' in my posts ...including the links! I spy a grammar auto-corrector lurking in the posting system.
Please try either the original link which I've corrected at the server end or: http://static.kvraudio.com/files/3214/lagrange32-bit.zip
Please drop us a message via firstname.lastname@example.org if this still doesn't work or to let me know how you get on with the 32-bit version and if all is good I'll add it to the distribution zip.
Thanks for your patience, .
2 December 2016 at 10:46pm
The plugin is working like a charm in Sonar.
2 December 2016 at 8:30pm
Thanks Mr. Elton, hope You'll continue to develope also the 32-bit version... ^_^.
13 December 2016 at 1:21pm
The 32-bit version is here to stay, I'd not anticipated the demand.
A Mac version is now on the way also.
20 December 2016 at 11:11am
I reckon that Mac version from the start could have got you the win. Shame... Although I voted for the Youlean Myself, I don't think it needs a booth at a trade show. Not exactly new tech to show off. This on the other hand May have gotten my vote but I don't test Audio on my PC anymore.
Can't wait tho :)
12 December 2016 at 10:48am
Just downloaded it, tried it on "Natural Grand" in Steinberg Halion Sonic 2, sounds absolutely wonderful.
13 December 2016 at 1:24pm
Thanks, I'd love to hear what tracks you make with Lagrange. Please be sure to PM me a link.
4 January 2017 at 9:48am
I tried Lagrange in Bitwig 1.3.15 today, but both the 32- and the 64-bit versions give errors during scanning. Does anyone else have trouble in Bitwig?
4 January 2017 at 12:38pm
Hi Eclectus, .
I've not used Bitwig before, but having had a go and it seems to be working ok here (I did the following):
- Clean Install of Bitwig.
- On Browser - Configuration: pointed the Plug-ins location at a folder containing the unzipped lagrange files.
- On Browser - Devices: dragged in the Lagrange effect to a channel.
You mentioned errors during scanning, is it possible to try the following:
- From the menu select Options > Preferences.
- Select the Plugin Management tab.
- select "show errors found with plugins" button.
- If Lagrange is listed, copy those errors to the clipboard or take a screenshot (snipping tool from windows).
- Paste those errors back here.
Dave @ UrsaDSP.
27 January 2017 at 11:35pm
thanks for this plugin. I use it a lot for sound design. May I ask if we can expect some minor gui / workflow tweaks? E.g: The changing text in the helpbox drives me crazy :-) it would be cool if we could hide the box. Also a different color are highly appreciated on my side the red is quite hard to look at for a longer time - maybe some blueish. Different knobs? Maybe more Ableton Live like and less 'analog'. And the key-modifier 'ctrl' also for the mouse wheel not only for dragging the knob.
31 January 2017 at 6:38pm
Thanks, that's great feedback. I've read it many times now and taken it all on board. The help bit feels like wasted space for me also (once its served its purpose).
As well as audio improvements and other plugins, I'm currently working on a website that will hopefully allow users who donate toward development to save presets and UI preferences in a way that jumps between systems (mostly because it is a fun challenge, you understand).
This is what UrsaDSP means to me, it's about exploring things. New audio tricks e.g. my take on granular echo, but also the UI e.g. things like that 'active' backlight on the limit controls, but also how it's put together.
The UI is entirely vector drawn in real time, no pre-rendered button bitmaps here. This means that changing the base colour shouldn't be too hard - I may allow the user to pick a hue for the backing and a hue for the highlights.
The style of the UI is also an interesting project for me - I realise that most people are going for these hyper modern flat colour controls, but I wanted to see how analogue I could go despite the real-time vector drawn method.
You're not the first to mention how I'm eschewing a trend that is popular for a good reason and I get what you're saying, I really do. Those UIs are nice and clean, snappy and easy on the eye in a stark kinda way. Perhaps I'll look at other UI styles sometime, but I'm also still hopeful that if I keep working at it I'll get closer to something that makes my look and feel stand out from the crowd. Who knows, perhaps in a few years time once everyone has got tired of looking at knobs that don't actually look like something you can touch my UI will have something of a quirky charm, or perhaps I'll just have fun trying.
Either way, thanks for taking the time to write, It means loads to me that people are still discovering and using my plug-in and then sharing their thoughts.
31 January 2017 at 9:25am
This plugin is amazing. That sort of effect I wanted for so long time. Really hope development will continue.
Thanks a lot, Dave.
9 March 2017 at 9:57am
Is there some way to reset the "RMS Limit dB"?
I've found that when I switch to Flangoid or Phasoid mode and set the Variable Delay to maximum, the limiter engages and then just stays on no matter what I do.
It cripples the plugin entirely and it has no effect on the input at all no matter what I do.
The only solution I've found is to remove the plugin and add it to the track again.
9 March 2017 at 11:31am
How rare, I hit this for the first time myself last night. It is an issue that happens if you have the fixed and var delays set to high (out of bounds read).
If you could let me have a screen shot of the settings that cause it that would help me make sure I've found and squashed the bug for your case as well as the one I found.
The fix is in the next release which is out soon (a few weeks?). The release is mostly about macOS support but will also include a presets system and a slightly bigger delay buffer for the fixed delay to allow people to do BPM based delays (if they can be bothered to do the maths for the fixed delay required).
Pressing play on your DAW _should_ reset all buffers and limiters, the code does that whenever the plug-in start is triggered, however DAWs are very varied in whether they actually do the things they are supposed to. I know Reaper works because that's what I use most.
Thanks for letting me know.
9 March 2017 at 9:08pm
I'm on Reaper and pressing play does indeed reset it. So that's great to know.
Regarding the particular settings, I just played around with it and all of the other settings have no impact on this issue as far as I can tell.
On Flangoid or Phasoid mode, I can start from the default in an empty project, with no input, and turn the Variable delay all the way up and it happens.
It's around 650+ that it kicks in.
Turn off the feedback - still the same.
Maximum high and low cut - still the same.
Fixed delay on minimum - still the same.
Grain rate and Density up or down - still the same.
I know that to debug the best information for you is systematic and organized and what I'm giving is pretty loose, so the best I can say is that I twiddled all of the knobs and tried them all at max or minimum, alone and in combinations and none of it changed the result.
10 March 2017 at 6:56am
Thanks for taking the time to get back to me. Much appreciated.
I'm confident the next release will address this.
I've dropped you a pm with further details.
19 April 2017 at 2:25pm
This is strange, just downloaded latest Mac beta 0.93 and on Logic Pro X's Plugi-n Manager successfully validated.
But tried to test in Audio or Instruments track and no UrsaDSP on the audio FX list. Maybe have to wait next 0.94 version.
19 April 2017 at 2:50pm
Hi, I'm not aware of any issues with Logic Pro, indeed a number of people helped me test it on that DAW.
MacOS 10.9 or later is required, but I would expect that to object during the validation process.
Please PM me with details of your system and I'll do what I can do get you up and running.
6 June 2017 at 5:06pm
Really strange. I use Lagrange regularly and middle out nowhere Ableton Live did not recognize the plugin and Reaper crash when I load the plugin. No changes or update of OS or DAW. Rellay strange. Any help?
6 June 2017 at 6:14pm
Hi Autobot, .
Most likely cause is corrupted presets.
Just rename the 'Ursa' bit of the preset folder.
On a Mac that's "~/Library/Ursa/Lagrange"
On Windows: just put %APPDATA% into file explorer and the preset folder will be called ursa.
The plugin will rebuild the default presets and you can then move old ones back if you want them.
If that fails please feel free to drop me an email.
There is a fix in the works to make the preset loading less fickle but I was hoping to add a bit more before release.
6 June 2017 at 6:35pm
Nice. It worked. Thank you I was almost near to cry. No everything is fine again.
8 December 2017 at 10:10pm
Hi, using Lagrange in in Studio One 3.5.3 on OS X and 2 of the settings result in the effect only coming out the right channel. Phasoid and Smooth Rand. This is on 0.93 and both VST and au.