Home › Forums › General › News and releases › status update
- This topic has 16 replies, 4 voices, and was last updated 12 years, 11 months ago by atom.
-
AuthorPosts
-
May 31, 2011 at 11:29 am #125
Just wanted you to know i haven’t forgotten i just didn’t have enough time on my hands to do a proper build, however what i managed to do in the meantime
– some performance fixes (very important ones and less important ones)
– the delay when destroying a plugin instance of Ctrlr is now 500ms (half a second) and is configurable via the overrides file (witch i have not yet mentioned and has been there for quite some time)
– a major fix for Windows + Live, there was a problem with the keyboard (it was not working in Live on windows), since there was no good workaround or permanent fix i went around the problem
and created a Wrapper for Live on windows, it’s a bit weird but it does what it should and the keyboard works
– tabs are working already i just need to make some fixes that make them usableso expect those changes in the next build, i hope to do it tomorrow, but i can’t promise anything.
June 1, 2011 at 7:33 am #1548Yes!! Sounds great.
TABS are going to make a huge difference for my Blofeld panel. Can’t wait!
June 3, 2011 at 11:23 am #1549"atom":2fgh6u8o wrote:Just wanted you to know i haven’t forgotten i just didn’t have enough time on my hands to do a proper build, however what i managed to do in the meantime– some performance fixes (very important ones and less important ones)[/quote:2fgh6u8o]
Did you really managed it and have you tried it out before the upload of 526? It’s the same like before. Very easy example: Take the standalone version, open a new pannel & select a MIDI out device, create a slider & use it.
You’ll recognise immediately that the CPU usage increases extremely in "Activity Monitor" (Mac). It’s about 10%-20% per EACH component on my 2.66 GHz Quadcore!June 3, 2011 at 11:54 am #1550well i was testing it in the same setup and was better but like i wrote i didn’t really do a lot of testing, the weird thing is that it should be the same on windows and mac but it’s not, on windows it’s all running smoothly and OSX acts different, i’ll double check it today i think i should have some time on my hands.
June 3, 2011 at 2:30 pm #1551That would be really nice!
June 3, 2011 at 6:56 pm #1552Ok could someone with a MAC try the JuceDemo (http://sourceforge.net/projects/juce/fi … g/download) this is an example application for the JUCE library, i’m getting some very high cpu usage when doing some slider tweaking in the Widgets demo.
June 3, 2011 at 8:10 pm #1553OK, if you want that we test something – please tell exactly(!) what to do. I never used this Juce nor Widged or whatever. Don’t want spend hours on that. I’ve downloaded it… open Juce…. and now?
June 3, 2011 at 8:33 pm #1554Demo->Widgets, and move any of the sliders rapidly. Also try the component rotation in the right upper hand corner, when doing this check out the CPU usage on the system.
June 3, 2011 at 8:51 pm #1555OK, I clicked the link above… downloaded it… open the .dmg… and see an icon which looks like half an orange… when I click this "The Jucer" opens… but I can’t find the option "Demo->Widges"…?
On the other habd I assume that if this causes in YOUR case high CPU peaks – it should be the same in MY case!?June 3, 2011 at 9:11 pm #1556June 3, 2011 at 9:34 pm #1557OK, now I got it. Also the Juce demo causes the CPU increament very high when tweaking some parameters..
So: what does it mean for us Mac users now? Will Ctrlr stay like this (until Jules [i:27p53hi7]maybe[/i:27p53hi7] would fix it)?June 3, 2011 at 9:46 pm #1558well i already posted this on the juce forum i’ll try to find out what’s going on there is an option to switch the rendering engine that might help, i’ll try that now and see if that helps, i’m also waiting for some response from the JUCE community.
June 3, 2011 at 10:25 pm #1559OK, thanks for your effort.
June 3, 2011 at 10:26 pm #1560the rendering engine switch didn’t help at all, but as you can see this is not really a Ctrlr problem more of a JUCE problem, but i’m still on it testing all possible scenarios.
June 3, 2011 at 10:52 pm #1561"atom":2k44wfbl wrote:the rendering engine switch didn’t help at all, but as you can see this is not really a Ctrlr problem more of a JUCE problem, but i’m still on it testing all possible scenarios.[/quote:2k44wfbl]well, this is one of those [i:2k44wfbl]if you want to be on the bleeding edge, sometimes you’ve gotta be willing to bleed a little[/i:2k44wfbl] scenarios. ” title=”Razz” />
I hope this gets worked out soon, I’m sure it will.Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen
June 4, 2011 at 12:47 pm #1562Want to let you know that I’m the next days away from home/studio/computer – so I’ll test again when I’m back and being curious what happens in the meantime. ” title=”Smile” />
June 6, 2011 at 1:37 pm #1563as for the performance issues on the OSX i guess JULES explains it best:
-
AuthorPosts
- The forum ‘News and releases’ is closed to new topics and replies.