And the other way around as well, people having the Classic only don't have much use probably for the G2 conversion.

exept that they can listen to patches with the demo g2 software

Sven, you should see me right now, smiling from ear to eye for the nice twists you come up with at times. I love you for that, honestly.

I'll first post a full mixed version (the computer is working right now), as delivered by by g2ools. Then, when and once I feel like it and/or you and/or Matt indiindicate that the time is right, I'll make a G2 only version as well, in addition to the mixed one, is that OK with you ? OK with all, I mean, ?_________________Jan

This is definitely not something to do very often, the total conversion, it needs many cycles and repeatedly so, seemingly or something. Time to get some sleep, hope it's done after that._________________Jan

1.3 will be abble to translate many patches that dont translate propperly now... so its good enough for a first run on the lib...

biggest problem in the moment are morphs on switches and that patches can become too big...

what can be optimized in the next version..but..
that next version will need a bit longer and it would be good if all bugs are found up to that optimisation phase..otherwise they probably stay in there forever because such a freeware projekt cant be serviced like a comercial product...
We have found many little and big bugs and tweaks and they are getting hard to find but duo the complexity of the item there must be some more...
You would have to test any module with any morph to ensure that there are no bugs...too much for one person..especially because some things can sneak in again as it happened with V1.2...

So its good to have the patches together up to that point to encourage people that have booth machines report back on bad conversions..
I hope some will do so...
After that period i am ok with having an own thread for each patch if that is what you like to have... just for the moment a public accessible lib with both formats in the same folder would be helpfull...
And probably also usefull allready because people also could point to good ones that can be listed in a best of cattegory later...
So as earlier its accesible as better..And version 1.3 that should be there very soon is defenetly qualified to do the first run.. at least what i can say i had a succesfull run on all patches i tried today... no 100% guaranty possible with just one beta tester but the heavies like wrong lfo rates..missing grey blue handling wrong level settings are ironed out in most areas... at least on my general test patches it went all fine...
But i cant ensure that there are no conflicts in any configuration..
The lib itself is a good random source for any eventuallity a patch can have... A realworld test..but its to big to be browsed by one person..
all bugs i found today was related to switches and missing limiters on delay modulations... szise of cause..buts much easier to reduce a patch than building it by hand...
Most of the applied models are not self optimizing yet..so an emulation of the Nm1 pulsewidth mod can be removed when the PW mod input is down...for example.. a thing that will happen automatical at one point.
Certain areas have this optimisations allready ..others are kept simple to dont risk new bugs in working areas..

Or AD enevlopes can be replaced with ADSR´s..but there you have to set the release time one tick longer than the decay to reduce the level loss on short triggers (like internal sequencing) to "only" 1,7 db...

1,7 db in a feedback patch can be too much..so even when this can be done by the program automatical its discussable if this should be a default setting...

but.. be carefull..the conversion forces now blue mixers to stay blue... they might get red when you remove modules..

So first step before altering a patch is to look for blue mixers that get red cables..and make them stable by adding note quantizers if necessary...
often it is necessary because a red signal in a blue mixer usually is fm modulation that is sensible to resolution. I asked for a flag in future update to set these note quantizers automatical... but for now that was the easiest and most resource safing fix.

Would be cool if a future update of the G2 allows to set that permanently for modules because its a sound design tool as we have seen in your noodle patch you posted lately.

1.3 is translating this patch much better allready..but because the delay line optimisation is not done yet ist not as good as my manual fix yet...
a asymetric limiter set on 50 needs to be before the delaytime mods on wild patches to keep delaytimes within the range that is possible on the Nm1... or on chained delay lines that have even numbers you can reduce them by factor 2 and have the mod on twice the converters = original Nm1 value...

Because the complexity of the different delay line questions this point was at the end of the list and still needs to be implemented..

WHy not create an ISO volume, throw the files in there ... then zip the ISO file?_________________A Charity Pantomime in aid of Paranoid Schizophrenics descended into chaos yesterday when someone shouted, "He's behind you!"

If you are on a PC, then chances are you haven´t been playing much around with disk images / volume files. This is a perfectly valid way to transport files and it´s easy too. You don´t have to burn the file. It will do just fine to mount the volume file. Doesn´t XP come with at least some basic disk/volume file tools

Also, you should have tools there somewhere to simply morph a folder to ISO file directly.. or create an empty rewriteable ISO volume file and then mount it and throw batches of files into it._________________A Charity Pantomime in aid of Paranoid Schizophrenics descended into chaos yesterday when someone shouted, "He's behind you!"

Well, if only OS X heads will be able to handle this, then I guess this was a really bad idea. But frankly, is handling of disk image files really seen as a messy affair on the PC? _________________A Charity Pantomime in aid of Paranoid Schizophrenics descended into chaos yesterday when someone shouted, "He's behind you!"

Don't know about that Stein ... XP is a bit retarded you know, like when you do del *.pch /S it will happily delete all *.pch2 files just as well (where of course the DIR command does it OK, bright tooling)

Anyway, I'm beaming up the zipped ISO now and will see if I can find out about how such could be made workable under XP. Meanwhile I'll construct a G2 only and a classic only zip as well, damn it it might even have to write my own del command for that ... oh wait I have cygwin, maybe that'll do it OK._________________Jan

Anyways, I´m pretty sure there must be some free tools out there for handling disk images and such on XP.

I expect the guys to complain if the ISO idea was a bad one. Anyone? _________________A Charity Pantomime in aid of Paranoid Schizophrenics descended into chaos yesterday when someone shouted, "He's behind you!"

Ok, there are a lot of files that are not patches in it. pff, what a mess.

I took the collection and removed the catagorized patches as they are duplicates within the author directories. I'm going to eventually write a script to use the patches in the categories to build a table or html page of links to the author directories. It's a waste to have 2 exact patches in 2 different locations. So I'm only dealing with the 011_Patches subdirectory. I've updated all < version 3 patches to version 3 and removed all corrupted unfixable patches. There are only 24 patches out of 30000 that either crashed the editor when loading or the editor posted an error message.

BlueHell if you want access to my server with the latest collection, PM me and I'll set you up an account to grab the files. I have it password protected to decrease my bandwidth usage.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum

Please support our site. If you click through and buy from our affiliate partners, we earn a small commission.