Cosmos-f
-
- KVRist
- 163 posts since 26 Sep, 2012 from bavaria
I totally want to give this a chance because I am really intrigued by the sounds and workflow, but I can't even get it installed on my mac. I put the component files in the component folder like i did with dozens of other plugs, but Cosmos-f won't show up neither in Logic/Mainstage nor AULab. I can't even find it in the AUmanager. Which company name is it supposed to show up under? Do I find it in the instruments or the MIDI controlled effects? The manual gives very little info on all this.
-
- KVRist
- 163 posts since 26 Sep, 2012 from bavaria
I can't wait to test this, so any help is very appreciated. Does no one have the same problem? I did rescan the AU components several times now, but cosmos-f doesn't show up in any host. Where do you find it on your host apps?
I didn't get a reply from the developer either.
I didn't get a reply from the developer either.
-
Sampleconstruct Sampleconstruct https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=191286 - KVRAF
- 16795 posts since 12 Oct, 2008 from Here and there
The AU plug-in version 1.0 worked fine in Logic, the update 1.1 fails to validate so maybe that's your problem. I'm in Kontakt with the dev but he hasn't fixed it yet.monas wrote:I can't wait to test this, so any help is very appreciated. Does no one have the same problem? I did rescan the AU components several times now, but cosmos-f doesn't show up in any host. Where do you find it on your host apps?
I didn't get a reply from the developer either.
-
- KVRist
- 163 posts since 26 Sep, 2012 from bavaria
so i've been messing around with the standalone version that i still have saved from the time before the plugin came out. i like the fact that even though the synth engine is pretty conventional (additive/substractive, granular) the whole approach is still so different that it inevitably leeds you to different places than other synths would.
but it still seems like a premature release and the price is way too high for that. Clicks are definitely a big problem, and i believe that it totally is the developers responsibility to avoid them. i can't see where any of my settings would be "unreasonable" but still i constantly run into clicks. there's a flaw in the code or the maths that the developer needs to fix. other granular tools don't click either and that's surely not because they are less advanced.
i find the gui a bit annoying as well because it seems to sacrifice intuitive handling to design and esoteric appeal.
also the fact that the shop is still up, eventhough the latest and only available version don't work on osx is weird. it doesn't even mention the problem on the page, and the developer doesn't resond to email.
i found the old price perfectly reasonable but i have to agree that +$200 is surreal for this. i am holding back for now until these issues are sorted.
but it still seems like a premature release and the price is way too high for that. Clicks are definitely a big problem, and i believe that it totally is the developers responsibility to avoid them. i can't see where any of my settings would be "unreasonable" but still i constantly run into clicks. there's a flaw in the code or the maths that the developer needs to fix. other granular tools don't click either and that's surely not because they are less advanced.
i find the gui a bit annoying as well because it seems to sacrifice intuitive handling to design and esoteric appeal.
also the fact that the shop is still up, eventhough the latest and only available version don't work on osx is weird. it doesn't even mention the problem on the page, and the developer doesn't resond to email.
i found the old price perfectly reasonable but i have to agree that +$200 is surreal for this. i am holding back for now until these issues are sorted.
-
- KVRian
- 989 posts since 27 Jun, 2011
The 'lite' version is only $115. All you really lose is morphing and feed-forward.
The 'lite' attribute doesn't do the single engine justice. They should call the lite version just 'Cosmos f' and the big version "Cosmos f: Galaxy Edition".
The 'lite' attribute doesn't do the single engine justice. They should call the lite version just 'Cosmos f' and the big version "Cosmos f: Galaxy Edition".
-
- KVRist
- 163 posts since 26 Sep, 2012 from bavaria
morphing seems to produce the most radical sounds though and it gives a whole new level of control on top of cosmos-f. it also makes it a potential live instrument. i wouldn't want to miss that.
-
- KVRist
- 163 posts since 26 Sep, 2012 from bavaria
I got me a license and i was hoping i could report more positive things but I have to say that I am having the most horrible
customer experience of my entire life:
Cpu seems to be pretty high compared to other granular tools and synths so and i kindly asked about what's up with that and how to keep things lower. I only got a snippy reply basically saying that if I know so much about dsp to judge this then I can probably solve the problem myself. Then he went on braging about his supposedly "top-professional" customers, his genius software and wanted to have personal infos about me to see if i qualify for a support request. I've NEVER seen anything like this before.
My main problem is still the clicking that constantly occurs (mostly at the end of every macro cycle), and renders most of my experiments useless. Especially when you apply compression and reverb to your sounds these artefacts get boosted to an annoying level. According to the developer the artefacts at the end of the macro cycle can be avoided either by using a soft window on meso events (like hanning, adsr, etc.) or by using the 'l'-switch. But none of these methods work. Though he refuses to acknowledge any bugs or give any further infos.
Likewise almost all the modulations cause clicks and audio disruptions. There's a complete lack of smoothing when parameters are modulated which makes all of the more unusual and stochastic modulation shapes useless. He refuses to comment on that as well.
There seems to be a severe lack of understanding of basic dsp concepts, like how to avoid artefacts in a sampling app, how to incorporate modulations, how to applying useful parameter scalings, etc and a lot of the presets have the same clicking issues. So far all the click-free sounds I could get out of cosmos-f are pretty much straightforward looping sounds, with no stochastics or modulations. I could have done that with other tools as well, without investing over 200$.
The worst thing is that this individual cost me days of productivity. I've been asking him the same simple technical questions over and over again, but he refuses to give a straight answer about whats wrong and instead just winds his way around and tells me to read the manual again. wtf?! It sickens me to think of the fact that I am paying this guys rent.
I hope anyone wants to share their experiences with the program here because the developer understands questions and bug reports as personal insults and reacts as uncooperative and unprofessional as it can get when the most obvious problems are even mentioned. He even clearly stated that he refuses to answer any of my further questions. Needless to say how that makes you feel just after having paid over 200$ and putting your trust in someone.
Also, can anyone maybe recommend a de-click plugin? I've heard Izotope RX being mentioned, but it's way too pricy for just a click-remover. I've also found the wave arts one for 50$ but it doesn't really do anything. any ideas?
customer experience of my entire life:
Cpu seems to be pretty high compared to other granular tools and synths so and i kindly asked about what's up with that and how to keep things lower. I only got a snippy reply basically saying that if I know so much about dsp to judge this then I can probably solve the problem myself. Then he went on braging about his supposedly "top-professional" customers, his genius software and wanted to have personal infos about me to see if i qualify for a support request. I've NEVER seen anything like this before.
My main problem is still the clicking that constantly occurs (mostly at the end of every macro cycle), and renders most of my experiments useless. Especially when you apply compression and reverb to your sounds these artefacts get boosted to an annoying level. According to the developer the artefacts at the end of the macro cycle can be avoided either by using a soft window on meso events (like hanning, adsr, etc.) or by using the 'l'-switch. But none of these methods work. Though he refuses to acknowledge any bugs or give any further infos.
Likewise almost all the modulations cause clicks and audio disruptions. There's a complete lack of smoothing when parameters are modulated which makes all of the more unusual and stochastic modulation shapes useless. He refuses to comment on that as well.
There seems to be a severe lack of understanding of basic dsp concepts, like how to avoid artefacts in a sampling app, how to incorporate modulations, how to applying useful parameter scalings, etc and a lot of the presets have the same clicking issues. So far all the click-free sounds I could get out of cosmos-f are pretty much straightforward looping sounds, with no stochastics or modulations. I could have done that with other tools as well, without investing over 200$.
The worst thing is that this individual cost me days of productivity. I've been asking him the same simple technical questions over and over again, but he refuses to give a straight answer about whats wrong and instead just winds his way around and tells me to read the manual again. wtf?! It sickens me to think of the fact that I am paying this guys rent.
I hope anyone wants to share their experiences with the program here because the developer understands questions and bug reports as personal insults and reacts as uncooperative and unprofessional as it can get when the most obvious problems are even mentioned. He even clearly stated that he refuses to answer any of my further questions. Needless to say how that makes you feel just after having paid over 200$ and putting your trust in someone.
Also, can anyone maybe recommend a de-click plugin? I've heard Izotope RX being mentioned, but it's way too pricy for just a click-remover. I've also found the wave arts one for 50$ but it doesn't really do anything. any ideas?
-
- KVRAF
- 4380 posts since 15 Sep, 2010
Really sorry to hear that man. Horrible support for plugins that expensive is really annoying, and more importantly very frustrating. Maybe Simon had a better experience?? I know he's been in contact with him (I think).
Anyway, personally I tried the demo twice and both time I gave up. All those clicks were for me simply inacceptable for a plugin at that price. Why should I run a de-click plugin right after it to make it sounds good? After reporting that here in previous posts, someone once even told me that 'clicks' is part of the granular charm lol. Well not for me, at least not when my goal is to create smooth and velvet clouds of grains to make a deep drony pad… The concept behind it is definitely fresh and interesting, but for me it seems the overall plugin is still unpolished. I hope you're gonna have a better experience with the support in the near future cause 200$ is A LOT
Anyway, personally I tried the demo twice and both time I gave up. All those clicks were for me simply inacceptable for a plugin at that price. Why should I run a de-click plugin right after it to make it sounds good? After reporting that here in previous posts, someone once even told me that 'clicks' is part of the granular charm lol. Well not for me, at least not when my goal is to create smooth and velvet clouds of grains to make a deep drony pad… The concept behind it is definitely fresh and interesting, but for me it seems the overall plugin is still unpolished. I hope you're gonna have a better experience with the support in the near future cause 200$ is A LOT
-
- KVRist
- 163 posts since 26 Sep, 2012 from bavaria
I have to say I like having the option of introducing clicks by choosing a rectangular window function when i find it suitable for a certain sound aesthetic. But here it's just clicking no matter what you do. I think the developer just has his head in the clouds of fancy theoretical approaches but can't be bothered to get his hands dirty with some necessary polishing work and basic dsp standards. it's really sad. I can only hope someone else persuades him to fix things up because he won't answer to me and I'm also tired of the communication.
-
- Banned
- 10196 posts since 12 Mar, 2012 from the Bavarian Alps to my feet and the globe around my head
What happened with the "warning" thread? I cannot find it anymore...
Was there a solution?
Was there a solution?
-
- KVRAF
- 4380 posts since 15 Sep, 2010
-
- Banned
- 10196 posts since 12 Mar, 2012 from the Bavarian Alps to my feet and the globe around my head
Without solution?Neon Breath wrote:Been locked.
-
- KVRAF
- 4380 posts since 15 Sep, 2010
I think so. Not from what I've read so far. Thread was going to nowhere...Tricky-Loops wrote:Without solution?Neon Breath wrote:Been locked.