Page 1 of 2
Eating Half of my CPU!
Posted: Sun Apr 19, 2009 2:12 am
I love this plugin, but I have a serious problem:
I am on a dual G4 computer, which means I have to CPU processors available in Logic 8. When I have Decimort active, the CPU levels which are running at an average of 40% shoot directly to the max when Decimort is active. Other d16 plugins don't seem to have this problem. Only Decimort, which sucks because I love the sound of this plugin. But until this issue is fixed, unfortunately, I can't use it.
I have another problem!
Posted: Sun Apr 19, 2009 3:46 am
The GUI stopped working on this plugin too. I can use the plugin if I switch my plugin view in Logic to Controls instead of the GUI.
Man, I'm starting to feel queasy about my purchase. I love the sound of these things, but what the heck is going on with the DSP and GUI issues? Yikes
Posted: Mon Apr 20, 2009 11:25 am
The problem lays within the compilator we use, seems everything works fine when we compile it on Intel based platforms, but Decimort especially is very heavy for PPC based computers, G4 especially because it's technologically older processor.
We do everything accordingly with the Apple's specification, all our sources are compiled as Universal Binaries and those pass every test provided by Apple.
In a case of Decimort the whole case is very painful, because this particular plug-in is the heaviest one of whole Silverline family, considering CPU resources it needs.
We're going to investigate it deeper when we finlize AU versions of our instruments and we'll see if some optimization were made in new version of framework we use, and if it'll work better within the next update of Decimort. But I cannot guarantee it'll help.
We'd like to give You two options, wait and see if updating framework will help to Decimort in a case of efficiency on G4 plaftorm, or refund for this particular plug-in.
Posted: Mon Apr 20, 2009 4:10 pm
Thanks. I think I'll stay on for the ride. I'll be moving to an Intel laptop as soon as Universal Audio releases UAD for the card slot (any time now hopefully). I realize it's difficult to cater to Intel, G5 and G4 processors all at once, and I can't wait to get off my old piece of crap. It's a daily drain on my creativity.
The sound of your plugins is astounding. I'm impressed by your candor and the fullness of your explanations. I'm sure in time, I'll get my money's worth. I think my biggest concern at this point (although I'd love it if that plugin became more CPU efficient) is the fact that the GUI crapped out on both the plugins I'm using in my current song.
Thank you for the kind offer. You've convinced me to exercise some patience.
Posted: Thu May 21, 2009 10:30 am
IÂ´m solving this problem with buying a mac pro with hellofalot memory
I love the plugin but it kills my g5...so have to do something
intel vs. ppc
Posted: Thu May 21, 2009 2:52 pm
yeah, i'm realizing ppc is dead now. i'm just waiting for the uad2 for laptops to get released. then i'm off my ppc for good. problem solved, lol. i can't wait to stop using my old piece of crap. metaphorically speaking, it's held together with scotch tape. i even bought my first plugin that won't even run on ppc (aether reverb). didn't realize it when i bought. no matter though. it's a great plugin and will be waiting for me when i migrate.
Posted: Sat Jul 18, 2009 3:56 am
I am now fully moved to a MacBook Pro Core 2 Duo, and I still have interface problems. Nothing is moving in the Decimort AU interface at all; however my newer Mac does seem to handle the load much better than my old G4 piece of crap. Any thoughts?
Posted: Mon Jul 20, 2009 12:53 pm
Does it happen when You insert only single instance of Decimort to Your project or it happens only when there're few more Silver Lines there?
Does it happen when there's ONLY Decimort in a project?
What hosting application do You use on MacBook?
I assume, since it's new machine You have Leopard installed there.
Posted: Mon Jul 20, 2009 3:45 pm
logic pro 8.0.2
I believe I had more than one of your plugins active in the song (not at home, so I can't verify atm), but it doesn't seem to matter of the other plugin was on a frozen track or not (rendered so plugins are temporarily disabled on that track).
Posted: Wed Jul 29, 2009 7:07 am
Any progress on addressing this problem?
Posted: Wed Jul 29, 2009 10:39 am
We're working currently to provide full compatibility for our products with Leopard, it concerns all our plug-ins. Due technical differences between Tiger, Leopard and GUI technologies on MacOS used by hosts' developers (Carbon and Cocoa).
Posted: Wed Jul 29, 2009 2:18 pm
Thanks for the response.
Posted: Tue Oct 27, 2009 4:59 am
In July, you said you were working on your plugins, but I haven't heard of any updates and it's now October. Your plugins are the only ones among over 500 that I use which have this GUI problem. Your last response is starting to feel a bit empty, since nearly half a year has gone by, yet you've released other new products in this time. I have had problems with your plugins non-stop since I bought them, starting with my older G4 and OS 10.5 and ending with my MacBook Pro and OS 10.6. You assured me that running your plugins on Intel would resolve the issue, but all the same problems persisted. Then you said you are working on it, yet there is no progress in 5 months? Where is the support to your customers? It's difficult not to feel neglect here.
Posted: Tue Oct 27, 2009 9:59 am
All our plug-ins use single programming framework, and this is matter of fixing the framework to make all our plug-ins not causing such issues (I mean GUI) on MacOS anymore. We've this already solved.
We're going to release SilverLine updates one by one - first Toraverb is expected. We've found way how to improve Decimort considering its CPU usage without degrading quality, and that's the reason why this update's release time is prolonging. I'm sorry.
Posted: Tue Oct 27, 2009 3:05 pm
What does the GUI have to do with sound quality engineering? This response is confusing to me. I recognize the problems with GUI, but you mention audio quality in addition. Are you trying to make the plugins more CPU efficient at the same time?
I'm a little encouraged that you say you have been working on the GUI problem. There are a lot of people including me who feel somewhat ripped off by d16. Your plugins are NOT cheap, so one expects them to work as advertised, yet some of the four I purchased haven't worked properly since I bought them roughly a year ago.
They do sound good. I can't help but feel excited at the thought of them all working as they should. I hope your team follows through on what you are saying here.