ValhallaFreqEcho: Add new delay sync times, or keep the same?

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion

ValhallaFreqEcho: Add new delay sync times, or keep the same?

Keep the same sync times. I need FreqEcho to be compatible with old projects
5
6%
Add new sync times
76
94%
 
Total votes: 81

RELATED
PRODUCTS

Post

Hi everyone,

I'm working on a ValhallaFreqEcho update. The current changes:

- 64 bit versions for OSX and Windows
- Knob behavior defaults to up/down, instead of circular
- Font changed to Futura
- GUI changes for improved legibility
- Resizable GUI

While working on the update, I noticed that the sync delay time selection code was buggy, in that it might not save the sync time correctly with the project. I've been working on fixing this, but this will make things incompatible with older projects that use FreqEcho. However, those older projects may not be saving their state correctly as well.

If I fix this bug, and break project compatibility, I might as well add more sync times to the delay options. I would add all of the delay sync options from ÜberMod, as well as 1/32 and 1/64 delays (plus the T and dotted versions of those delays).

So, what do you think? Keep things the same way that they are in the current version of ValhallaFreqEcho, even if that is kind busted? Or, fix the bug, and add new sync options?

Sean Costello

Post

I voted for new sync times. But I guess a valid question would be, for users that have legacy projects, if it would be a possibility to have the current version and the updated version side by side? To make it FreqEchoMkII so to speak?
I have no idea of the amount of extra work that would take, so it may not be a valid option at all...

Post

BDeep wrote:I voted for new sync times. But I guess a valid question would be, for users that have legacy projects, if it would be a possibility to have the current version and the updated version side by side? To make it FreqEchoMkII so to speak?
I have no idea of the amount of extra work that would take, so it may not be a valid option at all...
It wouldn't take much extra work, but it would take a few hours of computing time, as Xcode chokes on compiling Juce projects when I make a change like that. I'm not sure why.

Anyway, that's an interesting idea. I'll add it as a poll option. EDIT: Or maybe I won't - not sure how to add options to the poll once it is posted.

Sean Costello

Post

Given the direction this poll is taking, I figure you can forget the idea of two versions and just implement the new sync times :-D

Post

+1 for a new Plug-In ID so that old projects remain untouched. I've only used FreqEcho for live FX so I am not affected by a change but I guess many users would welcome this.

Post

IIRC, Automation is still facked up.

That, IMO, downgrades a lot of the plug capabilities :roll:
Professional technicians are assessed by the abilities they possess.
Amateur technicians are assessed by the tools they possess - and the amount of those tools, with an obvious preference to the latest hyped ones.
(Gabe Dumbbell)

Post

Tp3 wrote:IIRC, Automation is still facked up.

That, IMO, downgrades a lot of the plug capabilities :roll:
Awwww, SAD EYE ROLL SMILEY FOR FREE PLUGIN!!!!!!

:D

A fair point. I've put some automation fixes in the new version as well. I haven't released this, so the version you are working with is 2.5 years old. The new version will still have the same mapping between sliders and low-level controls, but will have a better awareness of automation.

EDIT: It is worth noting that I am working on the slider/low-level mapping for upcoming plugins. This is something that is kinda busted in Juce, but Andy Simper/Cytomic has posted some ideas in the Juce forum on how to fix this. It is taking me a while to incorporate this, and it is enough of an annoying slowdown for my next plugin that I decided to put a new FreqEcho build out there, just to feel kinda productive. I can't incorporate this into the older plugins without totally breaking things, so it will have to be for new work only.

Sean Costello

Post

I voted for fixing/adding new stuff. I figure that they can just remember how it was set before, and then re-do it in a few minutes after they update. If they have so many projects that it's going to take alot of work to do something so simple, they probably were never going to finish them in the first place ;D

Post

valhallasound wrote:EDIT: Or maybe I won't - not sure how to add options to the poll once it is posted.
KVR (or rather phpBB or maybe just the version KVR uses) doesn't support this.

I voted for the first. It's not that I have projects that would break but something about being forced to use the imprecision of milliseconds - I sort of like having one plug that works this way. On second thought though if sync times are broken somehow though ... there's no option to re-vote either :lol:

Random thought - one slider with two modes - one for milliseconds, one for sync, one for sync time +/- milliseconds? There are a fair number of plugs that do sync with a percentile swing, but some effects layering differently shifted copies require millisecond softs of offsets. (Or maybe this is where JUCE isn't quite there.)
Last edited by xh3rv on Tue Jul 10, 2012 6:43 pm, edited 1 time in total.

Post

I think I will go for the new plugin ID. The current plugin is ValhallaFreqEchoMkI, so I'll name the new one ValhallaFreqEchoMkII.

Screenshot of the new version:

Image

Post

xh3rv wrote: Random thought - one slider with two modes - one for milliseconds, one for sync, one for sync time +/- milliseconds? There are a fair number of plugs that do sync with a percentile swing, but some effects layering differently shifted copies require millisecond softs of offsets.
I will look into this for a future version. This current update is mainly intended to add 64-bit versions, fix a few bugs (knob behavior, automation stuff), and get the GUI in line with the rest of my plugins. In the future, I want to look into true stereo, envelope follower/LFO, stuff like that - but I need to get another commercial plugin out the door, so those changes will have to wait.

Sean Costello

Post

valhallasound wrote:
Screenshot of the new version:

Image
Ahh, nice - welcome to the family :)

Post

Sampleconstruct wrote:
valhallasound wrote:
Screenshot of the new version:

Image
Ahh, nice - welcome to the family :)
I need to get ValhallaShimmer to come to the resizable 64 bit family reunion as well. The "valhallashimmer" logo isn't really in keeping with the other plugins, but I LOVE the spacing of the font in ValhallaShimmer, so it stays as it is.

Sean Costello

Post

valhallasound wrote: I need to get ValhallaShimmer to come to the resizable 64 bit family reunion as well. The "valhallashimmer" logo isn't really in keeping with the other plugins, but I LOVE the spacing of the font in ValhallaShimmer, so it stays as it is.

Sean Costello
Every family needs a black sheep!

Post

valhallasound wrote:
Tp3 wrote:IIRC, Automation is still facked up.

That, IMO, downgrades a lot of the plug capabilities :roll:
Awwww, SAD EYE ROLL SMILEY FOR FREE PLUGIN!!!!!!

:D
No no !!

I am mighty grateful for what this plug gives. :hail:

It just that at the time, this problem FREQed me out :D

And I DID my "thank you" (well, 75% "thank you !" - the full licence of Shimmer is not mine. YET :oops:)
Professional technicians are assessed by the abilities they possess.
Amateur technicians are assessed by the tools they possess - and the amount of those tools, with an obvious preference to the latest hyped ones.
(Gabe Dumbbell)

Post Reply

Return to “Effects”