Topic: Preview 2.24: Embedded plugin editors in the rack

@Zynewave wrote:

Beta 6 is up. Minor changes and some bug fixes. I think I still need a couple of days working through all the bug reports.

It’s hard to test though if we don’t know what to check for! 🙂 Are you taking on bugs related to changes in 2.24 only, or the ones reported in the releases forum too?

@Zynewave wrote:

@thcilnnahoj wrote:

Question: Since the selected embedded parameters remain the same across different arrangements, I assume they stored within the project (or the device definitions) then. If so, would it be possible (without too much trouble on your end) to export such a parameter list setup to reuse in other projects?

The two flags for rack/mixer embedding are stored in the properties of the parameter object. I could add two check-boxes to the parameter properties dialog, but I don’t think that is necessary. If you save a track template then the flags will be included. The embedded flags will be recalled if you load the template into another project, unless that project already has a definition for the plugin.

Hmm, okay, that’s at least workable. But there’s no way then to import them into existing projects other than merging them or deleting devices and reimporting them via track templates, which I reckon would not be advised!

@thcilnnahoj wrote:

But Reaper’s fonts are not anti-aliased at all in either of your screenshots, CQSD. Are you sure ClearType has an effect on Reaper in your setup?

I think there is a bit of confusion here 🙂 I don’t think Reaper uses Anti aliasing the same way Podium does. The fact that it has an option to reduce it and another to switch it on for “Fades and envelopes” (in the option screenshot) suggest it clearly does use Anti aliasing but somehow differently compared to Podium. If there is any anti aliasing for inserts its much more subtle compared to Podium and a result more effective IMO.

Your screenshot comparisons between R & P actually prove that IMO. I can still see the differences between the two apps. Clearly.

They’re identical at larger sizes, but the smaller ones make you wonder if it’s the same font, really.

Its very strange I must say. I guess certain apps have a different approach to anti aliasing. I just think Podiums is not as clear as a few others I have tried with very small text. It can be clearer. I initially though it needed to be enlarged. Adding the option I suggested would eliminate the need to have various options for anti aliasing. Just one IMO is needed.

All the screenshots I could find of Samplitude were taken with anti-aliasing disabled in Windows, so I can’t tell if the mixer fonts would still be the same if you turned it on.

Samplitude definitely spreads font smoothing about a bit but not consistently. 😉 The Mixer inserts do not have any font smoothing or anti aliasing at all. ClearType has no effect here on Samplitudes mixer inserts (on or off). The Samplitude comparison was brought up only for the Mixer inserts. They avoid any anti aliasing and look sharper as a result.

The whole anti aliasing problem is strange but I think its quite important when dealing with smaller text. I thought my resolution was too high and considered even getting a smaller monitor to run at 1600 x1200 (or 1080) but after seeing Reaper and Samps mixer i see there is no need for that hence my suggestions to Frits for an additional option for anti aliasing or we go back to getting those buttons enlarged again which I suspect is not likely to happen but then again I don’t think that is needed now as its definitely a font smoothing issue not a font size problem in Podium. :-k

@druid wrote:

As for Reaper offering anti-aliasing options for lines (if I understood correctly); that WOULD be application-specific, and nothing to do with fonts, as far as I know.

No idea for sure. My usage of Reaper is only at demo level but maybe yes, I guess it is very likely application specific but I am not sure. In any case Reaper appears to split up certain elements for anti aliasing treatment or the reduction of it (text, envelopes e.t.c). The results are very good however it does it. :-k

Here is some info on anti aliasing…(with more to the left of the screen in the link on fonts)…

http://msdn.microsoft.com/en-us/library/dd183433(VS.85).aspx

Had a problem getting this link to work but paste into your browser to see the full article.

It looks like in theory it might help Frits with Podium (from a developers perspective). Its a guess of course as I am no expert in this area but this info from the link looks like it might help???

“You can adjust the appearance of text by changing the contrast value used in the ClearType algorithm. The default is 1,400, but it can be any value from 1,000 to 2,200. Depending on the display device and the user’s sensitivity to colors, a higher or lower contrast value may improve readability. To change the contrast, call SystemParametersInfo with SPI_SETFONTSMOOTHINGCONTRAST. The following code sets the contrast value to 1,600.”

Maybe something like that can be adjusted in Podiums code or exposed to a user to change in a more simplified way. ❓ ❓ ❓

@thcilnnahoj wrote:

These options will not make it any better, though… :-k

They might work from a developers perspective though. Frits could say “no it will not help at all” or “possibly”. But without his perspective on it we can only continue to guess and speculate which of course has limited use beyond a certain point.

You can set all these parameters yourself (system-wide) with this Microsoft tool. I found a piece of information that speaks of a control panel entry giving access to these options that’s already built into Windows 7 from the start – maybe you could try to look for it and test it for yourself.

I used the built in version of that in Windows 7 which is exactly the same and probably even better (as it appears to offer different options based on your initial choice) several times before I even mentioned the problem on this thread to avoid wasting Frits time.

It made no difference to Podiums Mixer inserts unless I switched off ClearType completely. That solved the problem 100% but…other areas that benefit greatly from ClearType in Podium now looked much less appealing as a result. Which bring me back to…

“adding some kind of option to disable anti aliasing for the Insert, Source and Input buttons (just for the tracks and mixer strips)”

My guess is that Reaper uses different font rasterization/smoothing types in different places, maybe even circumventing Windows’ settings

thcilnnahoj…I think you are 100% right here. I see no other conclusion to arrive at here. That must be it. It appears the options are wider and deeper as a result of more detailed optimisations and offering anti aliasing for some parts of Reaper while reducing it for others definitely works very well.

Let bugs be bugs for a while and enjoy the festivities. 😛
Merry Christmas from me too!

Yes, merry christmas to all fellow Podium-lovers 8) .

Yeah …put your feet up Frits, you deserve it after an amazing year of refinements and upgrades to Podium.

Merry Christmas all 😀