Conquistador's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 121 through 135 (of 1,598 total)
  • in reply to: Preview 2.24: Embedded plugin editors in the rack #17158
    Conquistador
    Participant

    Merry Christmas all ! 🙂

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17144
    Conquistador
    Participant

    This is a bizarre conclusion to the issue raised here some time ago. I could easily hide the inserts e.t.c for the tracks and Mixer and just use the Inspector but there is no way I want to lose all that functionality when all that was asked for was more UI consistency LOL!

    Frits did a wonderful job achieving that (beyond that I would say) but I suspect he should have just asked (as AFAICT he always has) if anyone wants the larger text or even larger button option as that appears to be the only way to get larger text back or more legible text unless anti aliasing is revised in some way or the suggestion I put forward is taken up.

    I know I was one of the people who said the large button look was not optimal and that led to him removing it but I assumed because Frits said nothing about it that the larger text option was still there. It appears larger text would have to mean larger buttons. I am happy to settle for more legible text instead if that is an easier problem to solve by optionally disabling anti aliasing for text used in Tracks and Mixer buttons.

    In hindsight I should have said he should leave those buttons at the original larger size and made either larger or smaller buttons and text on buttons the default. Seeing as the smaller text option was removed that would certainly be one my suggestions now. :-k

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17143
    Conquistador
    Participant

    @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.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17140
    Conquistador
    Participant

    @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. ❓ ❓ ❓

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17138
    Conquistador
    Participant

    @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

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17132
    Conquistador
    Participant

    Screenshots as promised… 😉

    This is with ClearType on. Reaper IMO has much clearer text compared to Podium here. I really do not know why Podium looks much less clear compared to Reaper :-k

    Podium is on the left and Reaper is on the right. Look at the “Fabfilter Timeless” text for the inserts.

    But if I switch off ClearType…can you spot the difference between the two applications “Fabfilter Timeless” text now? I can hardly tell them apart…below…

    Podium is far sharper than the first image now that Cleartype is off and matches (maybe even goes further than) Reapers text for clarity in the second image. Quite a difference and quite easy to see IMO with those screen shots.

    So Podium it appears benefits clearly from having anti aliasing disabled for certain areas (inserts on tracks and mixer strips) but anti aliasing is very helpful elsewhere in Podium that is why I think adding some kind of option to disable anti aliasing for the Insert, Source and Input buttons (just for the tracks and mixer strips) will solve this problem.

    I hope that helps.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17131
    Conquistador
    Participant

    I am surprised but it appears Reaper does use anti aliasing but not as strong as Podium by default. I say this because this option reduces antialising but both settings in Reaper (on or off) are clearer than Podium with ClearType on. Its as if Podiums fontsmoothing is a bit too heavy. Or there is some other approach Reaper uses to successfully minimize fuzzy text or…small text that is not too well defined.:-k

    A description of the option under the arrow can be found next to the “Find” button. My cursor was resting over the option to get the info line.

    I am not an expert on text so feel free to correct if I am wrong but I am going by what I see. I’ll get a screen shot up to compare.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17130
    Conquistador
    Participant

    @Zynewave wrote:

    I’m surprised that you think the aliased font looks clearer than the anti-aliased font. I have the opposite perception. Maybe it looks different on Windows 7.

    Could be different on Windows 7…but I also much prefer anti aliased fonts just not for very small text.

    That is why I suggested an option to disable anti aliasing for the Mixer and Tracks Inserts, Source and Input buttons (only). Not for the entire Podium interface. That could easily be achieved for the most part by simply not using ClearType at all. But that solution will cost me ClearType usage elsewhere in Podium for bigger text where it is very useful.

    Disabling anti aliasing for other areas in Podium is not of any interest to me. The rest of Podium benefits hugely from anti aliasing as do 99% of other areas of Windows and other apps.

    Please post a screenshot, or compare with my earlier screenshot on page2.

    Ok will do.

    I’ve seen screenshots of Reaper skins that use anti-aliased fonts, so maybe it depends on whether the default fonts used in Reaper does not support anti-aliasing. Or is there an option for this in the Reaper preferences?

    I just fired up the Reaper demo for a quick comparison but I’ll check and see.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17126
    Conquistador
    Participant

    @Zynewave wrote:

    The problem is that some of the icons are photographic images with multiple color shades, meaning that they cannot easily be filled with the current text color in the color scheme. It’s gonna require some work, but I’ll try experimenting with dyeing the images.

    Thanks for the explanation. It did seem strange but makes more sense now. Looking forward to your experiments. 🙂

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17125
    Conquistador
    Participant

    @Zynewave wrote:

    Puzzling. The font used in the inspector (with small size option) is the same as used in the mixer. Maybe you just need to wipe your monitor with a damp piece of cloth? 😛

    Damp cloth? Only if you send me one of those new Zynwave monitor wipes with free shipping. ➡ :mrgreen: 😛

    Please post/email a screenshot showing the problem. Note that the fonts used in Podium will be anti-aliased if you have the ClearType option enabled in Windows.

    That was it. ClearType. =D> I had Samplitude and Reapers Mixers up and tested with Clear type on and off and it made no difference to the mixer inserts in those hosts. None. The text remained quite sharp.

    Podium…it was easily clear the difference it made. The absence of font smoothing in Podium matched the other two hosts for clarity. The other two apps text (for inserts) made the text appear clearer and sharper as there is no font smoothing. Font smoothing really does not appear to work well with very small text but when switched off one can easily make out even a very small font size in Podiums mixer. (Inserts in this case).

    The “small font” option was made permanent when the new smaller buttons were implemented in 2.23. The normal font is too big for the smaller buttons. I had a look at screenshots of mixers in other hosts, and from what I can see it is quite common to use a small font in mixer effect slots.

    Indeed the fonts used in Samplitude and Reapers mixer inserts is AFAICT exactly the same size as Podium

    So is there a solution or halfway house here? Well I don’t think enlarging the text will help as there is probably no need, I don’t think you need to sharpen the text either but…Samplitude and Reaper appear to disable font smoothing for their Mixer inserts perhaps to avoid the problem I had with smaller text not really benefiting from it and losing some degree of definition.

    So can you please add an option to disable font smoothing / aliasing for the track and mixer inserts as well as source and input text in the mixer and tracks? That would solve the problem completely, having tested Podium with ClearType on (Tracks and Mixer inserts + Source, Input text) and comparing with it off.

    Can you please add this option? 🙂

    in reply to: Restricted to Podium license owners
    Conquistador
    Participant
    This content is restricted to Podium license owners.
    in reply to: Preview 2.24: Embedded plugin editors in the rack #17075
    Conquistador
    Participant

    @thcilnnahoj wrote:

    Yeah, I mentioned this too, I believe, though with a different solution. It doesn’t only affect the mixer buttons but almost all icons. 🙁
    Try the track select buttons in the rack for an example how it’s done right!

    Thanks for pointing that out. So it seems this problem is not isolated to the Mixer and Editor Profile bar. :-k It kind of goes against the other recent graphical enhancements in Podium. Hopefully Frits can have another look at this problem.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17074
    Conquistador
    Participant

    @thcilnnahoj wrote:

    @Conquistador wrote:

    @Frits I asked this earlier…where has the option to increase the size of text in the mixer and / or tracks been moved to? I can’t find it anywhere.
    :-k

    At the moment, there’s only the small mixer font size left. During the 2.23 beta’s, there was still an option for that (after you yourself, among others) found the selector buttons too big for the mixer. Maybe that’s changed since they can be zoomed now. In that case, I hope Frits hasn’t fed his code to the shredder…! (Font size option’s still there in the rack, by the way :wink:)

    Yes they were awkward in size but it was the button size not really the text that was my problem. I guess the silence from Frits is due to him digging through that code shredder looking for that option 😛

    I wonder what went through Frits mind after reading my question about larger text in the mixer in this thread…perhaps it went something like this…:P

    :-k “oh no…I think it has been deleted”

    THEN…

    :-s “where is that line of code already? I am sure it was here this morning” 8-[

    THEN

    :frustrated: “Conquistador just had to ask for this now didn’t he? Typical CQSD post eh? Why am I not surprised? It will take months for me to shove that code back into Podium without breaking 10 other features..it just had to be Conquistador asking for this” 🙄

    THEN

    :-({|= “Oh well…time for some guitar” 😉

    “Arrgh if I could just find that silly line of code”#-o #-o #-o

    It appears he has deleted that option a long time ago during beta 2.23 (gulp). I don’t remember him asking if anyone wanted the option there so I assumed he would leave it there and certainly not delete it from Podium. ❗

    @ Frits if you get the small text in Podiums track /mixer inserts, Source and input to be as sharp as Reaper or even Samplitude (after a brief check here) then I could do without the option to make them larger. Hope that helps.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17066
    Conquistador
    Participant

    @kingtubby wrote:

    Edit: Further thoughts. Using “add parameters” encourages the user to click on the text in the expectation that the option to add parameters will be available there, rather than where it is currently. Would it be possible to move the right-click add parameters menu to the “…parameters” text?

    @ Kingtubby

    I was just thinking the exact same thing… 🙂 I was just trying to repro LP’s inspector bug (especially as UA made it sound so easy to do :P) and I instinctively clicked on the “No parameters are added to the rack editor” text expecting the Parameter list to show up.

    So yeah…that is an even better idea. i would be much happier with parameter choices being made available after clicking on the text instead of a right click menu in this case.

    @ LP and UA…

    Yup…now I can repro that bug. It seems to only appear when the inspector is dragged as far left as possible (as you both said) but also only when the scroll bar appears. I also noticed that it seems to go away even when the inspector is dragged fully left if the divider between the Rack and Track panel is pulled down far enough so that the scroll bar is not visible.
    Strange. :-k

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17061
    Conquistador
    Participant

    @LiquidProj3ct wrote:

    @Conquistador wrote:

    Ok (sorry I misunderstood you) 😳 a bug report it is then 😛 🙂

    Funny enough…FWIW I cannot replicate it. I am running a 1900 x 1200 screen here and a font as tiny as the one in your image would be practically indecipherable at 1900 x 1200, so I would definitely notice it if I was able to replicate it here. I just thought I would try the “import plugin” bug you mentioned and I cannot replicate that either. Beta 5.

    It doesn’t matter man 😉 Anyway Podium shouldn’t be in full screen mode. When Podium isn’t maximized is when you can replicate the bug.

    Still cannot replicate it. Sorry. Podium was definitely not maximised this time. I Minimised and Maximised several times and when minimised I moved the GUI around and reduced the size of the Podium screen even further, still no problem with the text for the DX10 parameters. Our set ups of course are different (likely in more than a few ways) so something is triggering that problem on your system but here I just cannot see it. Hopefully Frits can reproduce it :-k

Viewing 15 posts - 121 through 135 (of 1,598 total)
© 2021 Zynewave