I made an almost perfect recreation of the pattern font pre 3.0, it is based on Devin Cook’s C64 Angled, so all credits to him.
Improvements:
Download
PatternFont.txt (change extension to .ttf)
PatternConfig.xml (587 Bytes)
can you walk me through the process of installing this, please?
Sure! just drag the files to
macOS:
/Applications/Renoise.app/Contents/Resources/Skin/Fonts (right click app, show package contents to access)
Windows
C:\Program Files\Renoise x.x.x.… (should be the same)
btw I changed the extension to bypass forum’s filetype restrictions 
question - where do i drag the PatternConfig.xml ? same folder?
i did get the .txt rename to .ttf - i might actually put these into Paketti and see if I can’t figure out a way of putting them there with a script, then quit Renoise, restart Renoise and see if can then prompt the user to change the font settings or something.
but anyway, some way of shipping them. - a multiplatform configuration / font system is on my todo-list but the todo-list is pretty long
EDIT: ok i see - the .ttf font putting in is pretty safe. but of course PatternConfig.xml is something where you gotta retain the original default one.
woo!
it did not quit Renoise after adding it, but after restarting Renoise, it’s in. and i wrote another flavor that lets me dump the original settings back in. this is great! thanks @Bluethereal !
now, what should these be called, please?
Ur welcome! Yeah older or classic is fine 
I reserved the “small” size to default deja vu mono so we keep both options
Changing the contents of an application bundle on MacOS will break the application’s signature seal and thus invalidate the application with Gatekeeper. This will probably force the application to run in a sandbox, or MacOS won’t launch it at all.
Please don’t do this from a tool.
it still runs perfectly on macOS. there was no extra verification step or extra hurdles. just works.
Would it be much hassle to make it possible to reference fonts and textures in theme files? This would open even more theming possibilities. This should be optional of course, so if a theme doesn’t reference fonts and/or textures Renoise will just use the default. Maybe Renoise could add the necessary folder structure to the user directory and then look for such files, this way a user don’t has to touch the default files.
I’m indeed running Sequioa! Now that you mention signature invalidation, I’ve had Ableton invalidated for changing its icon just once lol but maybe because I changed the bundle before I launched it for the first time, never for modifying the Resources folder of any app, in fact to install live themes you have to modify the app bundle too. I also could imagine this would be a problem between macOS updates but I’ve been having modified bundles since ever without issues.
i can eventually work this into the Paketti Theme Selector - once i have more font stuff + patternconfig.xml stuff configured.
making it possible to configure the background, font, and theme and group them together is on my todolist.
Sweet. I’m curious how you manage it on different operating systems to overwrite the default/selected textures and fonts.
As much as I like your work, I would prefer a native solution so themes will work on a bare installation of Renoise.
That definitely will break things. The question is just when it breaks and how.
On windows and Linux this also won’t work because those files are usually not world readable when installed.
If you still want to do such things, do it for yourself only and not in a published tool that is used by others.
i fully agree. a native solution would be good.
a native solution would be great for a lot of things.
but since we can’t have them, i’ll do little experiments and see what happens.
i still think it is beyond ridiculous that i have to edit config.xml to enable scripting terminal & editor, instead of having a preference checkbox for showing it.
but does anyone notice a theme here?
when i make a config.xml changer, taktik immediately pounces on me and goes “naw, don’t do that, that’s a bad idea”.
then we don’t have this, i make it, taktik immediately pounces on me and goes “naw, don’t do that, that’s a bad idea”.
looking forward to figuring out what the next bad idea is.
My job is allowing certain features in Renoise to be customized by people and also to point out the limitations.
If I, as a user, am installing a VST plugin I surely don’t want that it modifes my system installed files when running it. Same is true for Renoise scripting tools.
I can understand your thoughts but to enable the scripting console and such should be no problem for a dev. A regular user don’t need it in most cases, Renoise still is a application for music creation and not a IDE or scripting environment at first place. No offense here, just a little reminder.
I dont grok why it cant be in the renoise preferences as a checkbox.
the way to manage it is like this: (for now regards patternconfig.xml + files)
detect if it’s windows, macOS or none of the above (=Linux)
then figure out which version of Renoise you’re using v.3.4.4 or sommat, then use that for injecting the folder to the windows path, and the linux path. then just copy them in and retain the original version. then tell the user in status-bar to restart Renoise.
there’s a “default renoise patternconfig.xml” stored in Paketti.
what if it was hidden behind multiple prompts with switches between where the “Yes/Continue” “No/Cancel” keeps fluctuating randomly per each prompt, and the user needs to very consciously decide to read and decide multiple times, yes, i want to do this?
and yes, of course, destructive unwanted modifications that are not selected by the user, is a completely different thing. i’ve as far as i know, removed all of those. everything needs to be consciously enabled for stuff to happen.
Why doesnt Renoise support custom font choosing from the interface it cant be that difficult. Renoise feels too hidebound sometimes
