Another thing I recently found out - there's no way to make fonts look as sharp on Mac as on Windows.
So Mac version looks more blurry.
This is because OSX does not support sub-pixel antialiasing (so-called ClearType on Windows).
Check how it looks on Mac and compare with the previous screenshot.
Not sure you will see the difference though, cause sub-pixel antialiasing depends on your monitor (actually it depends on arrangement of R-G-B cells within screen pixel)
PS. But since I introduced GUI scaling it is not a big issue imho. Just use 125% GUI, looks fine.
BlueARP VST Arpeggiator development - let's discuss! (Apple M1 ready, 4K)
-
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
You do not have the required permissions to view the files attached to this post.
Last edited by graywolf2004 on Tue Apr 28, 2020 9:37 am, edited 1 time in total.
-
- KVRAF
- 7023 posts since 28 Apr, 2004 from france
Graywolf, thank you for the constant stream of updates, it's much appreciated.
-
- KVRian
- 1241 posts since 25 Jan, 2017
just saw the video on YT, nice update 
Little issue I found on the latest build (2.3.0)
This happens using the mouse wheel to scroll between themes.
After the last theme, scrolling down one more time makes the gui disappear.
Little issue I found on the latest build (2.3.0)
This happens using the mouse wheel to scroll between themes.
After the last theme, scrolling down one more time makes the gui disappear.
Thanks for the new version, looks nice.-
- KVRAF
- 5378 posts since 25 Jan, 2014 from The End of The World as We Knowit
I like your method of slow, incremental development. Everything works together well.
FYI in OSX 10.14 the size/scaling does not tell the host to increase the window size, so the elements get larger in the same size window.
Also, where should I put the manual to Open Manual>English in OSX?
FYI in OSX 10.14 the size/scaling does not tell the host to increase the window size, so the elements get larger in the same size window.
Also, where should I put the manual to Open Manual>English in OSX?
F E E D
Y O U R
F L O W
Y O U R
F L O W
-
- KVRer
- 8 posts since 29 Apr, 2020
Hello.
I've noticed in changelog that now settings are located in the windows user directory for avoid filesystem permission problems. Its a good thing but this break the portability of BlueArp, that i think its important. I suggest to let the user choose the preferred settings location, system user or portable. Cause there is no installer (where normally an user could choose where to save the settings) maybe u could add an option directly into the plug-in?
Another thing is about the arpeggiator. I use Reaper, and BlueArp works really flawless. Only one thing seem to be bugged. Switching the arp mode from ON to THRU or OFF (and vice versa) works only if i switch it through the vst interface, clicking by mouse.
But If i add the arp mode envelope to my track, when the envelope go to ON BlueArp produces a buggy sound, like an heavily gated sound of the current played vsti (also if all the BlueArp stuff is set to default). Seems like the arpeggiator is not fully synchronized to daw and then produce only a part of the waveform (like first or last part). Thanks in advance.
I've noticed in changelog that now settings are located in the windows user directory for avoid filesystem permission problems. Its a good thing but this break the portability of BlueArp, that i think its important. I suggest to let the user choose the preferred settings location, system user or portable. Cause there is no installer (where normally an user could choose where to save the settings) maybe u could add an option directly into the plug-in?
Another thing is about the arpeggiator. I use Reaper, and BlueArp works really flawless. Only one thing seem to be bugged. Switching the arp mode from ON to THRU or OFF (and vice versa) works only if i switch it through the vst interface, clicking by mouse.
But If i add the arp mode envelope to my track, when the envelope go to ON BlueArp produces a buggy sound, like an heavily gated sound of the current played vsti (also if all the BlueArp stuff is set to default). Seems like the arpeggiator is not fully synchronized to daw and then produce only a part of the waveform (like first or last part). Thanks in advance.
-
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
Thanks, fixed this in 2.3.1Niowiad wrote: Sun Apr 26, 2020 8:08 pm just saw the video on YT, nice update
Little issue I found on the latest build (2.3.0)
This happens using the mouse wheel to scroll between themes.
After the last theme, scrolling down one more time makes the gui disappear.
-
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
Which DAW? I just re-tested VST in REAPER - resizes fine. MFX in Logic - fine. VST in MuLab - as you describe, so you need to reopen window. Have no idea why. It calls NSView->setFrameSize in the code, which should do resize. Do other plugins resize well (I don't know any plugin to test it).Michael L wrote: Mon Apr 27, 2020 2:33 am I like your method of slow, incremental development. Everything works together well.
FYI in OSX 10.14 the size/scaling does not tell the host to increase the window size, so the elements get larger in the same size window.
Also, where should I put the manual to Open Manual>English in OSX?
Regarding manual - my bug I didn't include it into package.
Get it here:
http://www.graywolf2004.net/files/m/Blu ... 229_EN.pdf
If you right-click on BlueARP.vst -> Show package Contents and place pdf into Contents->Resources subfolder, it should open from bluearp menu. Normally, it should be there, this time I didn't include it.
-
- KVRian
- 530 posts since 8 Apr, 2018
Where can I download 2.3.1? The website shows 2.3.0
-
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
I'm right in the process. I made a minor update requested by Unify and will upload it within an hour.
-
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
Update: BlueARP v2.3.1
http://graywolf2004.net/wp/?page_id=35
Changes:
1. Added 'Random' option to STEP TYPE lane (requested for Unify).
2. BugFix: GUI skin, GUI scale goes out of bounds
3. BugFix: manual wasn't embedded into package (OSX only)
PS. Interesting info I just extracted from my website logs, distribution of bluearp downloads: around 75% - VST for windows, 20% - VST for OSX, 5% - MIDI-FX for OSX.
http://graywolf2004.net/wp/?page_id=35
Changes:
1. Added 'Random' option to STEP TYPE lane (requested for Unify).
2. BugFix: GUI skin, GUI scale goes out of bounds
3. BugFix: manual wasn't embedded into package (OSX only)
PS. Interesting info I just extracted from my website logs, distribution of bluearp downloads: around 75% - VST for windows, 20% - VST for OSX, 5% - MIDI-FX for OSX.
-
- KVRist
- 315 posts since 13 Jun, 2009
First, I made some rather small modifications (hoping improvements) to factory skins. Those I can share, link will be near bottom of this post.
Recent blue arp updates broke most of my skins I got from web. For a few days I tried to fix and I think I found solution to it.
Anyone using Telurca and satYatunes skins probably experienced this also.
I made modifications for a few of them, my favorites. Sadly, after I read their license files seems that I'm not allowed to redistribute without their permissions but I´ll write here easy fix:
Open Telurica.ini or satYatunes.ini skins file in text editor (you can still get them from blue arp pages) and in the header of each skin file inside ini (there are multiple inside 1 ini file) rename skin name, example:
Original: [scheme_satYatunes-EasyBlue]
Modified: [satyatunes easyblue]
Difference is that all are lower case letters and no any special signs.
Do this for each one, scroll trough ini file. It takes only one unmodified skin title for blue arp to crash.
If crashes:
Remove last skin file that caused this and reload blue arp or check if you edited all correctly. You can also copy main ini file and delete all but 1 skin, then copy again main file and delete all but another 1 skin etc etc. That´s safest way to test. Add new ini file with only 1 skin to skins folder, only 1, and try to load blue arp. Then next etc.
Haven't wrote but skins ini files goes to skins folder of the blue arp, I think that implies itself.
How to modify and make your own:
You have to experiment which is which, here is for titles (midi, matrix editor, gui -on left side of the blue arp):
Red:
// -- block label (yellow lines)
panels_BlockLabelColor=$0000ff
Yellow:
// -- block label (yellow lines)
panels_BlockLabelColor=$00EBFF
Green:
// -- block label (yellow lines)
panels_BlockLabelColor=$6cff00
Blue:
// -- block label (yellow lines)
panels_BlockLabelColor=$FFA373
Blue arp use those codes differently than you can find online color codes so you have to experiment or copy from other skins.
panels_TopPanelColor is for top panel as name suggests.
panels_InfoPanelColor is for bottom right info.
If during making your own skin colors after you open blue arp vst there is just black screen then go to:
C:\Users\YOUR_USER_NAME\AppData\Roaming\BlueARP\BlueARP.ini
Open BlueARP.ini with text editor and modify
skin_index=0
Remove last skin file that caused this and reload blue arp.
If Telurica and/or satYatunes approve in here for me to share I´ll share other skins too. Or they can test and update their original files by my instructions (saves time).
Preview of few I'm sharing: You can open Blue arp and compare with this pics.
Here are some of those I cant share (although modified originals): List of skins I did so far, bellow red line are the ones I cant share: And finally the skins file to download (sorry for TLTR but most things are important in some cases): Its inside zip file. Place in Blue arp skins folder. In case of blue arp crash/black screen (it shouldnt but just in case) read solutions I wrote above
Recent blue arp updates broke most of my skins I got from web. For a few days I tried to fix and I think I found solution to it.
Anyone using Telurca and satYatunes skins probably experienced this also.
I made modifications for a few of them, my favorites. Sadly, after I read their license files seems that I'm not allowed to redistribute without their permissions but I´ll write here easy fix:
Open Telurica.ini or satYatunes.ini skins file in text editor (you can still get them from blue arp pages) and in the header of each skin file inside ini (there are multiple inside 1 ini file) rename skin name, example:
Original: [scheme_satYatunes-EasyBlue]
Modified: [satyatunes easyblue]
Difference is that all are lower case letters and no any special signs.
Do this for each one, scroll trough ini file. It takes only one unmodified skin title for blue arp to crash.
If crashes:
Remove last skin file that caused this and reload blue arp or check if you edited all correctly. You can also copy main ini file and delete all but 1 skin, then copy again main file and delete all but another 1 skin etc etc. That´s safest way to test. Add new ini file with only 1 skin to skins folder, only 1, and try to load blue arp. Then next etc.
Haven't wrote but skins ini files goes to skins folder of the blue arp, I think that implies itself.
How to modify and make your own:
You have to experiment which is which, here is for titles (midi, matrix editor, gui -on left side of the blue arp):
Red:
// -- block label (yellow lines)
panels_BlockLabelColor=$0000ff
Yellow:
// -- block label (yellow lines)
panels_BlockLabelColor=$00EBFF
Green:
// -- block label (yellow lines)
panels_BlockLabelColor=$6cff00
Blue:
// -- block label (yellow lines)
panels_BlockLabelColor=$FFA373
Blue arp use those codes differently than you can find online color codes so you have to experiment or copy from other skins.
panels_TopPanelColor is for top panel as name suggests.
panels_InfoPanelColor is for bottom right info.
If during making your own skin colors after you open blue arp vst there is just black screen then go to:
C:\Users\YOUR_USER_NAME\AppData\Roaming\BlueARP\BlueARP.ini
Open BlueARP.ini with text editor and modify
skin_index=0
Remove last skin file that caused this and reload blue arp.
If Telurica and/or satYatunes approve in here for me to share I´ll share other skins too. Or they can test and update their original files by my instructions (saves time).
Preview of few I'm sharing: You can open Blue arp and compare with this pics.
Here are some of those I cant share (although modified originals): List of skins I did so far, bellow red line are the ones I cant share: And finally the skins file to download (sorry for TLTR but most things are important in some cases): Its inside zip file. Place in Blue arp skins folder. In case of blue arp crash/black screen (it shouldnt but just in case) read solutions I wrote above
You do not have the required permissions to view the files attached to this post.
-
- Banned
- 7624 posts since 13 Nov, 2015 from Norway
Love your work Graywolf 
:
:EnergyXT3 - LMMS - FL Studio | Roland SH201 - Waldorf Rocket | SoundCloud - Bandcamp
-
- KVRian
- Topic Starter
- 805 posts since 15 Apr, 2012
I kinda feel bad about the fact that you did so much work on this. Probably this are things that I can fix quickly. I didn't check Telurica skins (my bad), only checked included "studio" skins. So maybe I messed something up with backwards compatibility, so I will fix this in next release.bojanboyss wrote: Fri May 01, 2020 10:54 pm First, I made some rather small modifications (hoping improvements) to factory skins. Those I can share, link will be near bottom of this post.
...
I changed naming of tags, but all old color tags shhould be supported, I will re-check this.