One-Synth-Challenge 53: Feldspar - Submissions and gossip

[Davias]

Hi,

I have a little problem

I had the good idea of replacing Feldspar with the new version compiled to avoid multicore crashes... And now all my presets are broken, I had no problem with the older version, just I wanted to see if cpu hit was different... Of course I have deleted the old install too, and Contralogic website is only offering the last version as far as I know... So for now my tracks is playing all weird sounds I didn't program, does anyone still have the old version of Feldspar please ?

I hope someone does or I don't know what will happen with my entry

EDIT : I'm saved, found back the old dll on my laptop :p

I wonder what is different is the new dll.

[bjporter]

Hi,

I have a little problem

I had the good idea of replacing Feldspar with the new version compiled to avoid multicore crashes... And now all my presets are broken, I had no problem with the older version, just I wanted to see if cpu hit was different... Of course I have deleted the old install too, and Contralogic website is only offering the last version as far as I know... So for now my tracks is playing all weird sounds I didn't program, does anyone still have the old version of Feldspar please ?

I hope someone does or I don't know what will happen with my entry

I have it... did you rename the .dll's? I can send you feldspar.dll, feldspar2.dll, etc

[Davias]

Thanks Bjporter But I found it back. My dll is from 2005, I wonder how old is yours.

I didn't renamed the dll because all plugs are bridged in Renoise and I didn't have the crash. Just replaced today with the new one thinking "newer is better" ^^

But it seems something changed in the detune mode between the version I had and the last version... I'm happy I found back the good dll for my track but a bit because I planed to share my bank again, but now I'm wondering if it will be compatible with the last version...

[bjporter]

Thanks Bjporter But I found it back. My dll is from 2005, I wonder how old is yours.

I didn't renamed the dll because all plugs are bridged in Renoise and I didn't have the crash. Just replaced today with the new one thinking "newer is better" ^^

But it seems something changed in the detune mode between the version I had and the last version... I'm happy I found back the good dll for my track but a bit because I planed to share my bank again, but now I'm wondering if it will be compatible with the last version...

Great! Here's the link anyways:
https://dl.dropboxusercontent.com/u/220 ... ldspar.rar

[bjporter]

What I did was created a folder called 'Feldspar Updated' and put the dlls in there so I had a few different versions in the VST list of my DAW.

[Davias]

Thanks Bjporter But I found it back. My dll is from 2005, I wonder how old is yours.

I didn't renamed the dll because all plugs are bridged in Renoise and I didn't have the crash. Just replaced today with the new one thinking "newer is better" ^^

But it seems something changed in the detune mode between the version I had and the last version... I'm happy I found back the good dll for my track but a bit because I planed to share my bank again, but now I'm wondering if it will be compatible with the last version...

Great! Here's the link anyways:
https://dl.dropboxusercontent.com/u/220 ... ldspar.rar

Thanks for your help ! I will download it again just to be safe, I don't want another surprise like that I want to finish my track ^^

[V'ger]

Hi V'ger

Can I get a rules clarification.

Seems that Jules got the Trakction3 plugins working inside Tracktion4, so can I use in my challenge entry Final Mix from Mackie [ Trakction3 ] now that I am using Tracktion 4 ? It is a bit of hypothetical question atm, as I don't have an entry ready yet!

Regards, James

Yes like the others say this is Ok.

[chris_b]

I also remember that Jackson (one of the preset programmers) did a very cool demo tune called 'duckbill' or something like that

I found it and put it on soundcloud:

soundcloud.com/contralogic/feldspar-demo-duckbilled

But it seems something changed in the detune mode between the version I had and the last version...

Hm.. I thought I'd checked everthing was the same in the current version - I guess I wasn't thorough enough.

I'll look into it, but wait until the end of the month to release a update.

[V'ger]

Good but with a sampled top drum kit on it will anyway lift anything at least 50%.

[pedalsteeldrummer]

My submission for this month...

Enjoy!

pedalsteeldrummer


Eos

In Ancient Greek mythology, Eos was the goddess of the dawn who rose each morning to herald the light of a new day


http://soundcloud.com/pedalsteeldrummer/eos


TRACK NOTES:

Created for the KVR One-Synth-Challenge 53: Feldspar.

All sounds from Contralogic's "Feldspar" synth. I adapted some of the preset patches (Pad Pitch, Saws Gliding, Throbbing); all the other sounds I programmed myself.

18 instances of Feldspar. Mixed in Cockos Reaper 4.4 with native fx (ReaEQ, ReaComp, ReaVerbate, JS: LOSER/Saturation). Mastered in Reaper with native fx (ReaXcomp, ReaEQ, JS: LOSER/StereoField) and free fx (TLs Maximizer).

DR8
www.pleasurizemusic.com/en/our-aim
better and more dynamic sound

[evo2slo]

Need some troubleshooting advice.

I'm using Bootcamp on my mac running Windows 7 with Cubase 7. Been working fine for the last week with 28 instances of the latest Feldspar version, but now suddenly when I open my project there's a loud buzzing sound and the cpu meter is maxed out, and I have to reboot, or I get the 'check online for a solution/close the program' message. When I click for details it lists feldspar.dll as the problem. Older versions of my project open fine, so I think maybe this one got corrupted somehow?

I'm really unfamiliar with Windows and am wondering if there is any type of simple repair procedure that I should try?

Otherwise I'll just submit the rough mix mp3 I exported yesterday, as I don't have time to redo everything.

[bjporter]

Need some troubleshooting advice.

I'm using Bootcamp on my mac running Windows 7 with Cubase 7. Been working fine for the last week with 28 instances of the latest Feldspar version, but now suddenly when I open my project there's a loud buzzing sound and the cpu meter is maxed out, and I have to reboot, or I get the 'check online for a solution/close the program' message. When I click for details it lists feldspar.dll as the problem. Older versions of my project open fine, so I think maybe this one got corrupted somehow?

I'm really unfamiliar with Windows and am wondering if there is any type of simple repair procedure that I should try?

Otherwise I'll just submit the rough mix mp3 I exported yesterday, as I don't have time to redo everything.

Send it to me bro I'll take a look - it should be compatible with Cubase 6 (per http://homerecording.com/bbs/user-forum ... ty-356501/)

Use dropbox or something.

[evo2slo]

Thanks bj! I've been rebooting over and over and it finally loaded ok. I'm going to try and export the stems and open them in a fresh project. I think I really pushed it with the number of instances I had going at the same time. If I'm not able to export them successfully I'll take you up on your offer.

[bjporter]

Thanks bj! I've been rebooting over and over and it finally loaded ok. I'm going to try and export the stems and open them in a fresh project. I think I really pushed it with the number of instances I had going at the same time. If I'm not able to export them successfully I'll take you up on your offer.

Sounds good

Glad to hear you've got windows up and running, so now you'll be in many OSC to come. Are you doing the Cafe Contest? I think i've got an idea for that.

[V'ger]

A tip for crashy and unopenable project files apart from using your DAWs recovery mode (if it has one), is to remove the (suspected) offending dll from your VST folder, then open the project disabling or muting (whatever works best on your DAW) all or most instances then saving to a new project file. Now put back the dll in the VST folder and re-open the project and you can enable or unmute instance by instance (saving to new projects as you go along), until you find the offending number of instances or whatever it was that caused the project to malfunction, sometime this will work.

And cheers for the submissions so far