Reading Jupiter-80 sound sets on a PC/Mac

By 'going through' I mean, we have two documents (well three if you count the .CSVs that kimsnarf has geenrated - registrations and livesets (both of which contain tone detail). They are both top-down. So to get them bottom-up - which as you rightly suggest is the perfect and most useful scenario - one has to use the search function for firstly all 2,300 of the Tones and then all 2,000 of the Livesets. This of course is only the OSv2 sounds. Then there's the OSv1 sounds (same size of task). Then there's the Synth legends vol 1. Then there's the analogue collection from Roland.de. Yikes :(

If you know of a way to automate please tell! My eyes are burning, my hands hurt and brain is half what it used to be trying to work all of this out lol!

I do wish Roland would just give us a librarian... It's catch 22 I suppose, if we sit around and do nothing but complain, we might get one. But if we are proactive and work it out the hard way, they may just say, 'well they've worked it out, they don't need a librarian now' :-/

Yes I can write something to do it automatically, don't waste your time doing it by hand. I can probably do it next week as I am on vacation right now.

ps we need a librarian no matter what, this is really just a crude list to help out some people, but create set lists for gigging, etc... a librarian is absolutely crucial and most ideally it would be built into their ios app so that you can edit patches and arrange them in any order you want using the editor/librarian.

Anyway, I don't think the people that matter at Roland are reading any of this, so don't worry about it.

Dewdman42 wrote:

Yes I can write something to do it automatically, don't waste your time doing it by hand. I can probably do it next week as I am on vacation right now.

That would be fantastic, sir!

Let me know what you need and I'll do all I can to support :)

Dewdman42 wrote:

ps we need a librarian no matter what, this is really just a crude list to help out some people, but create set lists for gigging, etc... a librarian is absolutely crucial and most ideally it would be built into their ios app so that you can edit patches and arrange them in any order you want using the editor/librarian.

Anyway, I don't think the people that matter at Roland are reading any of this, so don't worry about it.

Agree with all points!

once I write the script to automate it we can decide what could make it better, then its easy to re-run it. For example, the order of tone names is not indicated in this CSV files..what order should the final list be in.

To all of you: Thanks for your hard work and your efforts! We others, who are just goofing around here, are watching with excitement... ;)

@cello: Your JP-80 website is outstanding!

This is all I have time to do right now and I didn't have time to check for accuracy, but check this out and look for any errors or ommissions to see if I automated it correctly.

I took the live_sets v2 file provided previously and twisted it around so that that list is by tonename. I don't think this includes tones which are not in use by any livesets, right? In any case, this is CSV file where column 1 is the name of the tone and all columns after are each of the live sets using it. One tone is used a lot, making the CSV file very wide. JP8 Strings 1 is used in almost 700 live sets if my script worked correctly.

Anyway check it out, going back to vacation mode now...

Brilliant, Dewdman42; many thanks for this! That's really clever stuff

From my own manual exercises I knew that JP8 Strings 1 was used in a lot of livesets - but 700 of them?! Wow. Having said that, in most instances they are inactive/mute. But this is one folks shouldn't delete - it is actually a very nice tone in it's own right anyway!

I've done random checks and all seems to be correct. But will scour some more during today.

Thanks again and enjoy your vacation :)

cello wrote:

Brilliant, Dewdman42; many thanks for this! That's really clever stuff

From my own manual exercises I knew that JP8 Strings 1 was used in a lot of livesets - but 700 of them?! Wow. Having said that, in most instances they are inactive/mute. But this is one folks shouldn't delete - it is actually a very nice tone in it's own right anyway!

I've done random checks and all seems to be correct. But will scour some more during today.

Thanks again and enjoy your vacation :)

Really clever and very useful stuff around this forum ! Well done!

JP8 Strings 1 is the strings base of almost all my string sounds on the integra7 too! Awesome tone alone, as a base behind Pianos, whatever...

ok since that worked out, here are the rest of the CSV's, twisted around

cheers

You are the man!

Thank you so much - I have added these to new zip downloads. :)

Great work.

Great teamwork going on here!

I have now given the Analog Synth Collection the same treatment as the other sound sets. That is, I have extracted a list of registrations (and dependencies) and a list of live sets (and dependencies). This sound set is apparently based on the original version 2 sound set, as a lot of the sounds are the same. I have therefore also created two smaller lists for only the registrations and live sets that are new in this collection. All the lists are attached for completeness.

In case anyone wants to try this at home or further the effort, here is the script I made for twisting around the CSV to show dependencies. For the lay man, this is an awk script, which means you need OSX or linux to run it, sorry windows users. I could have used something else, but awk is really easy for this kind of task and I'm super familiar with it so I just wanted to crank it out. Anyway, maybe someone in the future can improve up on it or convert to python or something, so here it is.

BEGIN {
   maxtoneuse=0
   FS=","
}

NR > 1 {
   for(i=2;i<=5;i++) {

      alltones[$i]=1

      ind=$i","$1
      if (masteridx[ind]!=1) {

         masteridx[ind]=1

         toneusecount[$i]++
         ind=$i","toneusecount[$i]
         tonesets[ind]=$1

         if(toneusecount[$i] > maxtoneuse) {
            maxtoneuse=toneusecount[$i]
         }
      }
   }

}

END {

   printf("Tone Name")

   for(j=1;j<=maxtoneuse;j++) {
      printf(",Live Set %d", j)
   }
   printf("\n")
      
   for (tonename in alltones) {
      printf("%s", tonename)
      for(i=1;i<=toneusecount[tonename];i++) {
         ind=tonename","i
         printf(",%s", tonesets[ind])
      }
      printf("\n")
   }

}

To run it on osx/linux, save the above into a file called foo.awk and use the following command line with the appropriate file.csv:

awk -f foo.awk file.csv

Note that is the one that does the tone dependencies. The script for liveset dependencies is modified from that because of different columns in the CSV but essentially works the same way.

And here are the AnalogSynth csv's with dependencies turned around. I am not sure I understand what the New set is for, but anyway here they are: