feedback needed :)
-
hey everyone, i'm finally at the point where im ready to send these new VIs off to get feedback on, they're built for Rhapsody so you'll need that first if you don't have it:
https://librewave.com/rhapsody/
specifically i need to hear about:
- download / installation / loading issues
- performance (CPU & Mem) ideally in a full song context within a DAW
- overall tone / sound quality (clicking / popping, different sounds with different SR's etc)
- any dream features that wouldn't overly convolute the "vision" of a simple, lightweight, great sounding VI
the first two instruments are stereo aggressive DI guitars & aggressive picked DI bass, obviously intended for the angrier side of the music wheel :)
sidenote: this is the first place I'm asking for feedback, so if the website has issues or doesn't work properly please let me know
You can download them & listen to audio demos etc here:
https://iamlamprey.com/software/
Thanks in advance!
-
@iamlamprey I have tested it on my Windows 11. Working perfectly. Very nice RR. But More features are needed like Strumming specially for Guitar. And Guitar fretboard visualization is required. What chord and key is being pressed etc. Without that a guitar instrument is incomplete.
Anyway, sound wise it is fantastic. keep it up. good work
Bollywood Music Producer and Trance Producer.
-
@iamlamprey said in feedback needed :):
download / installation / loading issues
performance (CPU & Mem) ideally in a full song context within a DAW
overall tone / sound quality (clicking / popping, different sounds with different SR's etc)No problem found.
Tested on FL , Live, Cubase 12 -
Nice. I'd like a velocity curve editor but that's just me. How come your guitar goes down to C0?
-
@DabDab said in feedback needed :):
More features are needed like Strumming specially for Guitar. And Guitar fretboard visualization is required. What chord and key is being pressed etc. Without that a guitar instrument is incomplete.
A note-delay based strumming feature probably isn't too difficult to implement so that's a strong "maybe",
I've never liked the fretboard interface (or string selection/tuning stuff either), in my experience the people that most often make use of those features (guitarists) would rather just record guitars, and most non-guitarists don't care
These instruments are really designed for a "draw in MIDI and hear a decent guitar on playback" type of thing, and the backend needs to stay as robust as possible to cater to percussion, piano, glocks etc so I'm not sure if I'll bother with the fretboard stuff
@d-healey said:
Nice. I'd like a velocity curve editor but that's just me.
Palm mutes use Low Velocities so it would probably need to be a stepped curve or something, but it's possible
How come your guitar goes down to C0?
That's Loris! There's only 3 strings in the recorded samples, and Loris fills in the gaps across the entire keyrange, I'm leaving it at C0 for anyone that wants to go crazy with the low-tuning, or do some whacky sound-design stuff with the ADSR
I have most of the writeup done regarding the technical side of things so that'll be up soon :)
Edit: thanks again both of you for the feedback and suggestions
-
@iamlamprey said in feedback needed :):
I've never liked the fretboard interface (or string selection/tuning stuff either), in my experience the people that most often make use of those features (guitarists) would rather just record guitars, and most non-guitarists don't care
Oh the struggles I've had the last few months creating a fretboard system :) which will be in the Rhapsody boilerplate soon if you need it. But I mostly agree with you here. However in my case I've recorded every fret on every string so a fretboard is a good visual way for the user to be able to choose which version of a note is played by moving a virtual hand up/down the fretboard. It's also useful if you have the functionality for editing chord voicings - but I haven't included that.
I think for most guitar instruments a fretboard UI isn't needed.
@iamlamprey said in feedback needed :):
Palm mutes use Low Velocities so it would probably need to be a stepped curve or something, but it's possible
Yeah I thought the instrument was glitchy because all I was getting was muted sounds, I had to give a bit more force to get the sustains. I guess my keyboard curve is setup differently to yours. A table can be used to add velocity scaling, the difficult bit is adding it to your UI without disrupting the aesthetic.
-
I have downloaded both instruments and ya they sound good my only fault is that bug with peq still remains in 2.3.3 of rhapsody on offloading i really like the split pane would love to see a way of adjusting velocity as mentioned.
https://pixeldrain.com/ is a good 3rd party way of sharing files or adding downloads without using the website hosting bandwidth. They also offer a top up pay as you go function so no nasty unexpected bills.
I bookmarked you site and will be checking back frequently.
-
@ospfeigrp said in feedback needed :):
https://pixeldrain.com/ is a good 3rd party way of sharing files or adding downloads without using the website hosting bandwidth. They also offer a top up pay as you go function so no nasty unexpected bills.
I really thought you were a bot for a moment.
-
@d-healey sorry, i just recently started using them myself and found them good. i am trying my level best to help.
-
@d-healey said
which will be in the Rhapsody boilerplate soon if you need it
I'll definitely check it out when it's ready and gauge how implementable it is
a good visual way for the user to be able to choose which version of a note is played
i think this is where i probably diverge a bit, even though i come from a guitarist background, a riff or chord was always a group of pitches to me and it didn't matter which strings were involved as long as all of the notes were correct
imo the end listener isn't going to care if the played chord is physically possible or not, and with Loris basically giving me one giant guitar string the tonal differences between them can be mitigated
obviously it's still a cool feature and a lot of producers will probably gravitate toward the familiarity of it
I guess my keyboard curve is setup differently to yours
my MIDI keyboard broke so I haven't even tested one with NB yet
@ospfeigrp said
https://pixeldrain.com/ is a good 3rd party way of sharing files or adding downloads without using the website hosting bandwidth.
Actually in this thread Aaron mentioned that because the files are so small, I can just use Github to host them for free and with thousands of file calls, if they catch onto me and suspend me or anything I'll definitely look into alternatives
There's also dropbox's direct download option but I think it's capped at a few thousand downloads a month, which might not work for free instruments since they do tend to go viral
-
@iamlamprey said in feedback needed :):
i think this is where i probably diverge a bit, even though i come from a guitarist background, a riff or chord was always a group of pitches to me and it didn't matter which strings were involved as long as all of the notes were correct
I find the fret position makes a huge difference to the sound. As you get higher the notes (even though they're the same) sound brighter. And obviously there is a huge difference between playing the open strings and playing the same note fretted.
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
Sounds really cool, congrats!
IMHO, there are just 2 things.
-
You can use more user friendly general terms rather than using Waveguides and Residue.
-
They will go really viral and they are of great quality. Therefore, it would be fair for users to at least sign up for a newsletter list in exchange for downloading these products. They can download it after Newsletter Subscription.
-
-
@d-healey said in feedback needed :):
As you get higher the notes (even though they're the same) sound brighter.
Yeah this is something I wrestled with for a while, I tried using a single note and spanning it with Loris and catching the harsh frequencies with a dynamic EQ but it just didn't sound the same as sampling the higher string/fret
And obviously there is a huge difference between playing the open strings and playing the same note fretted.
A caveat with this is that (at least in my experience) bright strings are sought after in aggressive music as they help cut through dense mixes, open strings are a lot brighter so I've intentionally used the lower open samples as the "main samples" that take up most of the keyrange
finding a balance between brightness without it being too harsh on the higher notes was key
@orange said
You can use more user friendly general terms rather than using Waveguides and Residue.
Yeah this is definitely something I'm still battling with, I heard Alex Hormozi mention that the average american reads at a 3rd grade level so the writecopy should be fed to a literacy test algorithm. that being said, I think the average VI enthusiast isn't your typical customer, and they're generally more curious about the "story" of an instrument or piece of software, so I'm trying to find a copy that's easy enough to read, while still having some of that technical aspect
Plus "digital waveguide" sounds way cooler than "wavetable synth"
They can download it after Newsletter Subscription.
There's a free tier for the Patreon which can essentially serve as a mailing list, the website needs to be Static to work with github pages, and there's a button inside the plugin to open the store page instantly so I'm trying to avoid "gatekeeping" the download behind a signup, I personally hate the friction and I'm trying to keep it as few steps as possible between discovering the instrument, and having it on the users HDD
I really appreciate the feedback guys! It's all going on the blackboard (btw I bought sticky blackboard paper for like $4 and it's the best investment I've ever made)
