One Synth Challenge 7 - Felix.

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
RELATED
PRODUCTS

Post

Max, I'm still getting the Galileo bug where it crashes Cubase 5. The exact error message reads:
Assertion Failed: next_event>time_stamp>=current_sample_clock file..\..\se_sdk\SEModule_base. cpp, line 198
Maybe not exactly that as I can't read my own handwriting lol.

Post

MA-Simon wrote::roll: ...i have to say... I thougt that i read somewhere ONLY tu use one VST + EVENTUALLY some free things. A LITTLE bit of a reverb freebie and a LITTLE bit of an Delay freebie BUT. So i have done my track like that.
As ever I'll give my tuppence worth on effects in OSC having been a very honest donkey in the past. :P

I'll restate my view that the "essence" of a synth has to be kept in submissions. It's difficult to define but, anything that substantially changes what the VST is able to do should be a no no.

Looking at Yeagers amazing list, I'll point out the filter FX in use - as examples, Tone2 Bifilter and Ohmforce Frohmage as a place I wouldn't want to be. Was the original Bifilter a freebie by the way? I'd like a download link if anyone has one :D :D

Anyway, listened to the track concerned and the acid test is, did I think it sounded like Felix? IMHO I'd say about about 60% did with the rest belonging to the outside of the envelope.

The choice is ultimately ours. If we don't approve, we don't vote it's as simple as that. Our opinion is king and of course Tatties comes from a burning bush... :lol:

Best of luck all,
Mouxbar

Post

MadPsyance wrote:Max, I'm still getting the Galileo bug where it crashes Cubase 5. The exact error message reads:
Assertion Failed: next_event>time_stamp>=current_sample_clock file..\..\se_sdk\SEModule_base. cpp, line 198
Thank you for this bug report, I think it's very important! ;) I had exactly the same error today trying Galileo with Presonus Studio One and these are not very good news for SE users... The problems comes with those hosts which fully implement the VST3 SDK (FL8, Cubase5, Studio One and other I think); SE plugins are VST2: all SE plugins, not only Galileo. I've checked also the last plugins developed with the SE1.1 beta and are VST2. After scratching my head all the day I think now it's clear the problem is related with Synthedit itself and not Galileo. The SEModule_base.cpp, if I'm right, is a piece of code of the SE SDK which manage the patch selector module. I think the most modern hosts have some sort of incompatibility with some VST2 instructions and this causes the crashes.

I have to report this to Jeff, there's nothing as a users that I can do, I think...

Anyway, don't know how can be useful, there's a "new" version of Galileo available. With this one I had no more problems on Studio One, if someone is brave enough to try :hihi:

I had also prepared a short test tune on FL5 which now is working ok, if someone on FL want to try to load it with the last releale of Galileo here it is: http://maxsynths.altervista.org/_alterv ... eotest.zip

Anyway I have to ask to Jeff. Thanks for the patience guys!

Cheers,
Max

Post

@MadPsyance: can you check if you get the same error with DSK Zith?
http://www.kvraudio.com/get/2482.html

Post

tattiemannie wrote:Oh .... here's that idea for the cover/label of the proposed felix album!

Image
:-o
My fiance's sister in law killed her cat a few years back this way, by accident of course. :cry:

Post

MaxSynths wrote:@MadPsyance: can you check if you get the same error with DSK Zith?
http://www.kvraudio.com/get/2482.html
Ok, I'll have to try it after work though. Will post results later tonight.

Post

MadPsyance wrote:
MaxSynths wrote:@MadPsyance: can you check if you get the same error with DSK Zith?
http://www.kvraudio.com/get/2482.html
Ok, I'll have to try it after work though. Will post results later tonight.
Thank you so much! ;) You are contributing to save the SE comunity from the evil space bugs! :hihi:

Post

slugfest99 wrote: Looking at Yeagers amazing list, I'll point out the filter FX in use - as examples, Tone2 Bifilter and Ohmforce Frohmage as a place I wouldn't want to be. Was the original Bifilter a freebie by the way? I'd like a download link if anyone has one :D :D
Yes it is a bit much I guess but I used both to shape the noise to make a snare and the aaahhh sound.
Don't know what came over me, in the other OSC's I just used a compressor and some reverb and that was all.
Maybe because this synth has NOTHING, no FX no unison no detuning of separate osc's no velocity sensitivity... just one filtertype, I felt the need to use more...
And the fact that this track wouldn't sit right made me use desperate measures :lol:

I'm sorry :hihi:

BTW the tone2 Bifilter can be downloaded here : http://www.kaosaudio.com/tone2-bifilter-free/

It's not where I got it from, but it's the same version 1.61 and it can be freely distributed.

Have fun.

Post

In order to stop the thread hijack with the Galileo issues, anyone which wants to contribute to solve the problem can post here

Cheers,
Max

Post

I did a Stripped version of : (Not) All Cats are Grey

18 x Felix

Fx :

2 x Classic Delay -> Toms/Snare/Lead
2 x Classic Flanger -> Toms/Lead
1 x Classic Chorus -> Synthpad
1 x Classic Compressor -> Snare
1 X George Young W1 Limiter -> Kick
1 x TL3-3127-LEA -> Kick
2 x NonameEQ -> Bass
1 x TLs SaturatedDriver -> Bass
1 x BassChorusV23 -> Bass
2 x Reacomp -> Bass/Kick/Toms/Lead
1 x Endorphine -> Toms
1 x MDA Detune -> Lead

Master Fx :

1 x CLAS
1 x TLs Maximizer

Some track-EQ's, no automation.

Removed all tone2 filters/Frohmage/Boogex/JB Smash Pro demo.
So its basically EQ compressors chorus Flanger and delay !

And did some additional EQing to match the original more or less.

For those who are interested... listen Here :

http://www.box.net/shared/vnkz4g2i7z

8)

Post

That deadline is closing in!!! ... Will we get one more track squeezed in?

I think in light of the discussion re. fx, I will consider adjusting the guidance for the next comp. I suppose it will all depend on which synth we use, and whether there are already built in fx etc.... I'll have a think about it, and will post what I think before the next comp kicks off.

Max, best of luck with your corrospondence with Jeff .. I hope there is a fix ... especially as you say it will affect all SE built plugs :(

Post

tattiemannie wrote:Max, best of luck with your corrospondence with Jeff .. I hope there is a fix ... especially as you say it will affect all SE built plugs :(
Further discovery: it affects all modules developed using the SE SDK1, the modules based on SDK2 are safe (I think :D). Well maybe we finally understood what is and where is the SE bug... :phew:

Ok going to listen to the tunes again before the vote... :D

Max

Post

Well Max, that understanding is progress at least :) ... and fuels my optimism that a solution to Galileos future may be found.

Yeah, think I'll have a listen as well, and casually stay 'on hand' to help with any last minute ...." Oh F**k I've uploaded the wrong track!!!! help!!" type requests :hihi:

Back to galileo briefly though, If we are going to have 'backwards compatibilty' issues with more synths in future, I dont think it would be a bad idea for anyone wishing to retain use of all stuff they've grown to love, to keep their eyes peeled for PCs which have been abondoned/binned ... or abinnedoned?? Its a shame that a load of good components which would keep our sturdy old machines working forever are being thrown into landfill.
I may be a crusty old single core dude, but I rarely have probs with any Vst other than outrageous cpu demands! .. Galileo works great for me on FL8!

Anyway, well leave the galileo thing to you, and anyone else who can provide any more testing and valuable pieces of info which will help you in the right direction. :)

Just a quick round up of outstanding issues before we move onto the voting thread.

ALBUM!
Is everyone in? can everyone provide a .wav version of their track? even if it has to be a conversion from the mp3? I can open a folder for collection ... but there is a 100meg limit! (PM me if this is an issue).
What about that 'Lego in the washing machine' pic? A good start? innapropriate? Will I coordinate this project? Or does Mac wanna take this on? Any other ideas? ... I suggest we stay on this thread beyond the closing date for submissions to discuss this project.

NEXT SYNTH?????
What is it to be? we can continue discussing this through the voting thread. There is not a lot to go on right now, so any pick up on what has gone before, or any new ideas will be galloping alongside the head of the pack!

PRIZES! :) :)
With such a high number of entries, there will prob be 5 runners up prizes in addition to the winners prize. it would be great if Max and Rob could could confirm/update which and how many of each prize they are willing to donate for this comp, and how they feel about the possibility of multiple winners/tie break ( an issue we have had to deal with in the last two comps!)
Rob,max, either PM me or post here. ANYONE ELSE WISHING TO DONATE A PRIZE WILL BE MOST WELCOME AND BE LOVED! PM me or post here!
Participants prize(s) ... If anyone can be bothered to read back the last 3 pages, they will know what I'm working on, and there's still time for feature requests! Discussion on this issue will continue in the voting thread.

PRESETS.
If anyone would like to pass on preset files, PM me or post here, and I'll link you to a folder .... this request is usually ignored, but I do think its worth giving something back to developers, or to those inspired to use our chosen synth. Dont worry if the sound you have used in your track has been EQ'd to give it the character it presents, everyone has EQ!

Right! ... see you on the other side eh?

Post

A quick one about prices Tattiemannie. I have no problems to donate more than one for each comp anyway there's one thing that must be considered: if prices are distributed very quickly this can slow down the interest for the competition. Maybe there should be some sort of play-off when there is more than one winner just to make tha challenge more interesting; maybe it's something that can be decided if some rules have to be rewritten.

About the allowed FX... I think that something like this is reasonable: the composer can use anykind of FX which comes with the synth. Other FX allowed are: reverb, delay, eq and compressor. These effects must be used in a traditional way, for example the EQ should be used to enhance or cut some frequencies but not in "alternative" ways (for example like a filter to sweep frequencies and create a "new" sound). Well it's only an idea, but I think a few words about FX are necessary because there is some stuff out there that can really transform a frog in a beautiful chick :D

About Galileo and SE plugins: Jeff is very sloooow with the replies :hihi: But I think I've found the solution to the problem on my own. I will share any useful info in a later moment (maybe you are interested as a SE user :D)

Good Night guys!

Post

Uploaded "untitled_for_osc7 - marcusz."

Post Reply

Return to “Instruments”