Thanks for that info, that makes sense.
I was sure that someone had written custom code for bitmap panels back some time ago but couldn’t remember who did it first. I know MSM had a custom panel ported from v0.6 to v1.0.
Current Computerscare plugin has a nice bitmap panel. Code is complicated because of its animated GIF support, but looking at that code got me a leg up on what I needed for my Imagine module, which is awaiting the next library update to make it’s debut.
1 Like
Oh yeah, forgot about that one. I’ll take a look at the code just out of interest.
If it’s helpful, my much simpler code is at pachde1/src at main · Paul-Dempsey/pachde1 (github.com)
src/pic.*, src/Imagine/pic_widget.*
Also used in src/Copper, where the color picker images are generated at runtime. But then you were already building my module, so this is for anyone else watching this thread.
2 Likes
Ok, I wait. Thank you all for your help, in the meanwhile!
1 Like
‘Pacman’ potentiometers… 
Thank you, thank you, thank you all! @pachde , @Steve_Russell , @carbon14 , @baconpaul , @Jens.Peter.Nielsen , @Ahornberg , @cschol , @Yeager
@1beat_Zip1measure I swear that if I was able enough to make even a simple oscillator, that would be my style. Either I blatantly copy some other VCO (with the author permission) and slap my texture on it or I have to find some other solution.
I’d like to be able to port WINDZ, DRONEZ, and ALIENZ from mschack and, leaving the very same functions, repainting in 8-Bit style but it seems there are a lot of problems both in porting those modules in 2.0 AND retexturing them…
Well, so far I am so happy! Going to update the gihub page as well!
2 Likes
Most open source VCOs have a license that grants you permission to do exactly that. Often it’s the panel graphics of the name that is the source of contention, but since you would presumably not use them… Go read the license files for the ones you want to copy.
Hello there! I’ve read the LICENSE.TXT and there I read:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
Now, if I got it right, I can do the following things (given I am able to do those):
- take the source code
- as far as I am concerned I would like to maintain the original names because I lovede them (maybe change the font to something more 8-bit-esque)
- update the graphic to my 8-bit style
- update the code to the 2.0 compliances
- put the same LICENSE.TXT inside the github or somewhere else
- wait for the ok from the bossess
OF COURSE the issue is and will be the #4 I am reading again the pages of the manual but, like everytime, I lose myself in a jungle of jargon and I cannot get out of it sane. Is there a resource like “Coding VCV for (VERY) dummies” somewhere…
That sound correct. You should also put something in to mention that this stuff came from MSCHACK, since it’s a) polite, and b) required by the license you linked to. Rack tends to put this kinds of things in a LICENSE-dist.txt file.
BTW, I know ppl have expressed interest in updating these modules. Might be some history and/or work that can be found…
1 Like
@baconpaul has had a look into it and if I recall correctly it isn’t a simple upgrade like most modules being updated to VCV Rack 2.
Yeah, that sounds familiar. It would of course be much easier to re-skin some VCOs that are already ported to 2.0.
I would have do it just for the politeness thing and because I’ve used them soooo much in the past with a lot of fun. I didn’t know the correct name of the file, though, I was sure it was LICENSE.TXT so thanks for the info!
I know… 
As far as I know THIS is the only thing I’ve found out. Thing is, I’ve used Cardinal and it tend to crash more often than not, especially when I use old patches and this annoy me quite some. Also, some patches do not sound as intended.
Do you know of any other project in that direction (that exclude Cardinal, possibly? Nothing against that software but I prefer to use VCV unless otherwise very good advices)
The problem is that I don’t know how to contact mschack himself to ask permission to update those 3 modules only (yeah yeah, you can laugh at me. The reality will be that I will ask to someone to dirt his or her hands instead of me… 
) even if the licence.txt should allow me without even ask the original author (but in my point of view, better supersafe than sorry).
Once the upgrade is done, doing the graphic is a piece of cake for me.
BUT I think that at this point would be sage to open a new thread; my topic have been brilliantly resolved (I will never end to thank you all for that) and I think a new one is about to pop up…
Looking back on our convo which I found in our discord dms, the primary issue was that the modules modify widgets directly in data from json, assuming the module and widget always ci exist and can co link which was true in 0.6 etc. but that would have to be changed to data which the widget reads from the module. It didn’t look impossible but it didn’t look trivial when we looked.