[Solved] trial setup is impossible

Can you please try the following:

1) Close rekordbox. Launch 'Font book' from the Launcher. Click Command-A to select all fonts, then select 'Resolve Duplicates'. Close the Font Book, re-open rekordbox and test.

If that doesn't work...

2) Close rekordbox. Open Font Book, select 'Validate Font' from the File menu to check fonts on the system are not broken. Close Font Book, open rekordbox and test.

If that still doesn't work...

3) Close rekordbox, open Font Book. Select 'Restore Standard Fonts' from the File menu. Please note that this will remove non standard fonts from the system (actually they are put aside in the Fonts(removed) folder. So they will not be deleted). Close Font Book, open rekordbox and test.

Let me know if any of those steps helped.

re
the trial version is working now ... yes!!!
but i have the trouble with the police of the font size of the grid view is two big when bpm is up to 100 i can't see it , is the same for the time remaining and the clock ... what can i do for that

@Knzy > Can you please take a screenshot of the problem so I can better understand the issue?

http://postimg.org/image/i8drmt8z1/
voila
and thank you

@Knzy > Do you have your system font size set to something other than the default? Because rekordbox will properly display most 3 digit (plus decimal) BPMs without issue.

no i change nothing of the default setting where can i see the default setting
just to be sur
if you see the clock and the time is the same

No - I mean within your operating system. Did you change the system font size?

Nop

I did the two solutions because it's write me no problem found
but when i launch rekordbox the problem was solved!!!!
THANK YOU

thank you and sorry for my english

@Knzy > Awesome, glad that solved it for you. :) Enjoy!

Nice one Pulse!! I never would have thought of that. Would this be considered desired behavior or a bug (so to speak)? In other words do you believe the designers intended for some of the text to be affected by generic font sizing?

I apologize for asking "out of turn" but I was already curious of this and it is within topic :)

It's something they found during the Early Adopter Program testing - some users had system fonts which caused the problem, the steps above "reset" things (so to speak). It's not to do with the OS font sizes.

Ahhh. Nice to know. Great work.