From the original SynthMaker forum (2004–2014), with its members’ names and dates.
sunsynth ·
As an addition 2 my previous 'older' ideas (Partslist, schematic-Print etc.) here a new one:
I have really complex schematics and because they have so many connections i recently use more and more of this wonderfull wireless Links...
But after a week (or sometimes even faster 😉 i don't remember where in the hell was modul/link etc. named xxx...
So a great feature would be the possibility 2 search inside a schematic, then doubleclick the part/modul in the toolbox beneath the search field and jump to the location inside the schematic where it sits...
SUNsynth
aliasant ·
+10
Acrobat ·
uuh aah yyyes! +666 😈
stw ·
this is a MUST!
infuzion ·
sunsynth wrote: I have really complex schematics and because they have so many connections I recently use more and more of this wonderful wireless Links... But after a week (or sometimes even faster 😉 I don't remember where in the hell was modul/link etc. named xxx...
The current OSM I'm working on has 14,923 modules & 182,700 Primitives, even after a few rounds of reduction. Now I have a live Mono wireless transmitter called "Main Out". Since I am not the primary author of the OSM, I have no idea where it goes.
I hope the devs are following this thread, since the lack of a OSM search &/or tree view makes SM much less convenient to use to develop larger VSTs.
stw ·
infuzion wrote: I hope the devs are following this thread, since the lack of a OSM search &/or tree view makes SM much less convenient to use to develop larger VSTs.
+1 !!!
TomC ·
infuzion wrote: Since I am not the primary author of the OSM, I have no idea where it goes.
That's an easy excuse. I AM always the primary author, and have sometimes no idea where the wireless connection ends 🙂
Therefore ++ for a search function.
Tom
Andrew J ·
Would also be very useful for finding all instances of the font selector (which we now know is one of the culprits for slow VST loadtimes).
Acrobat ·
Andrew J wrote: font selector (which we now know is one of the culprits for slow VST loadtimes).
! didn't know that !
anyway
+1
exonerate ·
Yep, needed 🙂
Tom7777 ·
Would also be very useful for finding all instances of the font selector (which we now know is one of the culprits for slow VST loadtimes).
Not always, it depends on the users pc i think because if im thinking of the right module it lists all there installed fonts, so oviously if they are a designer of some type and have lots it has to list all of them if it works in the vst like it does in SM, imo on that module there should be something like a show amount of fonts float/int input so it lists only 5 etc unless you enter more. I usually take them out as i only usually use arial font anyway untill the final decided gui design. Probably only needed to SM devs but might work this way for all so could slow things down a load for some users as you say, on this pc i have loads so it actually goes off the visible screen which reminds me of the idea i requested for dynamically adjusting schematic areas (resizing depending on modules) but that never happened as well as various other things unfortunately 🙁
Andrew J ·
OK, let me re-phrase. When we find things that could be useful for us in optimising our schematics, it would be great if we had a search function that would help us track down all the things we are looking for.
Tom7777 ·
Yeah i know, sorry didn't mean to annoy i just figured i should have mentioned about that in the reply 🙂 that way i can recommend a fix for the font selector and bump a old idea also without making new topics 😀
But yeah i definately agree a search inside project would be very helpful +1 vote
rl ·
+ 14,923
infuzion wrote: The current OSM I'm working on has 14,923 modules....
xmidiman ·
+1!
Acrobat ·
I voted 2 times!
So I vote for the third time: yes! 😀
sunsynth ·
Great Acrobat!
Damn, i should've started my 1st poll at the beginning... 365 Views!
tektoog ·
+1
sunsynth ·
Thanks Tektoog...
Now u - yeah u - one of the rest 5134 registered users - wake up and vote 4 this needed option!!! 😈 😇
Iman ·
+1
DigitalWhiteByte ·
+1x1000 needful
tor ·
Think i made this suggestion once my self 🙂
But any ways +333
stw ·
So who's gong to contact malc personally?
sunsynth ·
O.K. - I'll do it 😉
Have more wishes/questions on my 'wait list'...
pall ·
I did not know about this thread. Otherwise would not have started the Wireless Link thread. Sorry! In any event; + +
philter5 ·
BUuuuuuuuuuuuuuuuuuuuuump 😈
pall ·
Hello philter5. You are okay? 😀
infuzion ·
I think one can create a search using other scripting tools manipulating SM, but it should be part of SM.
+1
infuzion ·
stw wrote: So who's gong to contact malc personally?
I just did, he found a single float array that kept growing without being cleared, & the array size was in the millions for the file I sent him. Needless to say, deleting that reduced the OSM file size by alot: 46,600k. But finding that little bug in 1000s of other modules on my HD will be almost impossible. If the OSM was a simple text file like in C++, that search & replace would take about as long to type it in the search box as it would to replace them all.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker