New line characters

michelkeijzers · Post by **michelkeijzers** » Mon Oct 17, 2011 11:18 pm

For set list slot descriptions, you can use new line characters, i.e. define yourself when to start a new line. You can even add more than four lines, in that case you get automatically a scroll bar.

The disadvantage is that you have to use PCG tools for it, but who is going to add all those text on the Kronos display itself anyway?

Btw, the current version of PCG Tools does not support it, the next update will.

I also tried tab characters, but that does not work.

Below a picture how it looks like in PCG Tools, I don't have a camera now nearby to make a picture how it looks on the Kronos.

cynkh · Post by **cynkh** » Wed Oct 19, 2011 7:56 pm

Don't worry about the picture. With OS version 1.5 you should be able to connect a USB web cam to the Kronos!

Cheers!

michelkeijzers · Post by **michelkeijzers** » Wed Oct 19, 2011 8:00 pm

cynkh wrote:Don't worry about the picture. With OS version 1.5 you should be able to connect a USB web cam to the Kronos!

Cheers!

That would be nice

However, the new line feature is very handy. I already programmed most of the patch (names) and info in about 15 minutes.
Every song (set list slot) has the following info:

Full song name - Full band/performer name
Names of sounds including splits for both keyboards
Controller info
Init info and warnings (e.g. portamento keep when saving)

cynkh · Post by **cynkh** » Wed Oct 19, 2011 8:03 pm

michelkeijzers wrote:
cynkh wrote:Don't worry about the picture. With OS version 1.5 you should be able to connect a USB web cam to the Kronos!

Cheers!
That would be nice

However, the new line feature is very handy. I already programmed most of the patch (names) and info in about 15 minutes.
Every song (set list slot) has the following info:

Full song name - Full band/performer name
Names of sounds including splits for both keyboards
Controller info
Init info and warnings (e.g. portamento keep when saving)

Is it using 0x0D 0x0A for the newline or just 0x0A?

michelkeijzers · Post by **michelkeijzers** » Wed Oct 19, 2011 8:07 pm

To be honest, I haven't even checked yet ... I just made the 'return' key valid as acceptable key in the edit screen of PCG Tools and it worked on the Kronos ... I also tried the TAB key but everything after the TAB was not visible (can be used for 'hidden' text if such thing would be useful). And I don't know if it will be saved correctly (but returns do).

However, I need to check if it is one or two characters because I need to count it (should not be above 512 length).

cynkh · Post by **cynkh** » Wed Oct 19, 2011 8:11 pm

michelkeijzers wrote:To be honest, I haven't even checked yet ... I just made the 'return' key valid as acceptable key in the edit screen of PCG Tools and it worked on the Kronos ... I also tried the TAB key but everything after the TAB was not visible (can be used for 'hidden' text if such thing would be useful). And I don't know if it will be saved correctly (but returns do).

However, I need to check if it is one or two characters because I need to count it (should not be above 512 length).

That's kind of weird about the TAB character. It could be useful for saving information you don't want printed to the screen, like you said. Since the slot for the information is fixed you're not saving any space by not having all 512 characters present (unless you're compressing the file, in which case 512 null-bytes compress quite nicely

).
Great job, though! How's the new K61 treating you?

Cheers!

michelkeijzers · Post by **michelkeijzers** » Wed Oct 19, 2011 8:20 pm

I just checked, it is a 0D and 0A character.

I thought earlier about adding extra information to a PCG which could be used by PCG Tools internally. I want eventually to make a set list generator, which can print set lists for a band based on the set list slots. With the extra (but invisible info) I could store specific information about each slot, such as which slots belong together as one song, or if it is using acoustic guitars (needed for people mixing) etc.

What slots belong together as a song I also could use to make move/up down more intelligently or sorting.

I also thought about adding complete new chunks (or one new chunk) but I guess the Kronos will not save it if you change something on the Kronos itself.

michelkeijzers · Post by **michelkeijzers** » Wed Oct 19, 2011 8:21 pm

By the way, I checked it is a 0D and 0A character, so I have to correct the max. characters that can be typed.

michelkeijzers · Post by **michelkeijzers** » Wed Oct 19, 2011 8:23 pm

And the Kronos treats me well. One key has to be repaired some time (it's a bit slow going up but not a problem for most playing).

I have only spend time playing programs/combis and now I'm busy finding sounds for the band ... eventually I will probably also tweak more (I only did small tweakings, mostly controller rechanging).

cynkh · Post by **cynkh** » Wed Oct 19, 2011 9:16 pm

michelkeijzers wrote:And the Kronos treats me well. One key has to be repaired some time (it's a bit slow going up but not a problem for most playing).

I have only spend time playing programs/combis and now I'm busy finding sounds for the band ... eventually I will probably also tweak more (I only did small tweakings, mostly controller rechanging).

That's unfortunate about the keyboard needing repair already; it's good to hear it's not affecting you too badly though.
It's absolutely a dream to tweak with! I'm still 6 months later having trouble deciding what my favorite synth engine is since every time I turn on the K61 I migrate to a different area. It's hard to go wrong tweaking with presets, though. It's not like the old days (for me

) of tweaking the parameters of an NS5R only to find I've only just slightly modified the tone!

Well, happy tweaking and jamming!

Veel geluk!

michelkeijzers · Post by **michelkeijzers** » Wed Oct 19, 2011 9:27 pm

I have 2 years warranty and don't have gigs next months so I can bring it to repair in a month or two.

I want to convert 5 songs per evening if possible so next week on our first rehearsal they are available for playing ... still am doubting about which organ sound I have to use.

And then I also have to spend some time learning Joomla to create a website for the band AND continue programming with PCG Tools (and I forgot something else too ... oh yes ... I'm married quite some time ago).

How's your application going?

cynkh · Post by **cynkh** » Wed Oct 19, 2011 10:03 pm

michelkeijzers wrote:I have 2 years warranty and don't have gigs next months so I can bring it to repair in a month or two.

I want to convert 5 songs per evening if possible so next week on our first rehearsal they are available for playing ... still am doubting about which organ sound I have to use.

And then I also have to spend some time learning Joomla to create a website for the band AND continue programming with PCG Tools (and I forgot something else too ... oh yes ... I'm married quite some time ago).

How's your application going?

The app is coming along now that I've deciphered the layout. I was misreading the MIDI implementation docs and missing bits from each value. Some (rather most) values for the synth patches span multiple bytes but aren't lined up on word or byte boundaries so offset X might contain 3 bits of parameter 1, 4 bits of parameter 2 and 1 bit of parameter 3 while offset Y and Z might together make up just one parameter. It's taken me a bit to get my head around a nice, generic way to load in all the values (and more importantly how to spit them out!). Now I'd like to generate a form of XML to describe the PCG layout in general, a PolysixEX (e.g.) patch within the PCG and also a Polysix (e.g., again) patch in Korg Legacy Collection.
Like I said, it's been rough but a lot of fun!! (Now watch Korg just go and release a conversion utility that does this anyways...

)

Cheers and good luck with conversion of your own!

michelkeijzers · Post by **michelkeijzers** » Wed Oct 19, 2011 10:39 pm

cynkh wrote:
michelkeijzers wrote:I have 2 years warranty and don't have gigs next months so I can bring it to repair in a month or two.

I want to convert 5 songs per evening if possible so next week on our first rehearsal they are available for playing ... still am doubting about which organ sound I have to use.

And then I also have to spend some time learning Joomla to create a website for the band AND continue programming with PCG Tools (and I forgot something else too ... oh yes ... I'm married quite some time ago).

How's your application going?
The app is coming along now that I've deciphered the layout. I was misreading the MIDI implementation docs and missing bits from each value. Some (rather most) values for the synth patches span multiple bytes but aren't lined up on word or byte boundaries so offset X might contain 3 bits of parameter 1, 4 bits of parameter 2 and 1 bit of parameter 3 while offset Y and Z might together make up just one parameter. It's taken me a bit to get my head around a nice, generic way to load in all the values (and more importantly how to spit them out!). Now I'd like to generate a form of XML to describe the PCG layout in general, a PolysixEX (e.g.) patch within the PCG and also a Polysix (e.g., again) patch in Korg Legacy Collection.
Like I said, it's been rough but a lot of fun!! (Now watch Korg just go and release a conversion utility that does this anyways...)

Cheers and good luck with conversion of your own!

Yes I can understand all the analyzing of bits and bytes. For my app I only need a small bunch of PCG bytes (tough it gets more and more). I think making a XML format is very useful, especially if you later want to do more conversions or other usage of the PCG. I also have made some help functions (like reading bytes and setting bytes), and soon I also will add bit functions so I don't have to do all the bit shifting in the higher level software anymore.

I don't expect Korg will make such conversion possible, they are way to busy with the basic functionality. That's why I'm not going to add many editing features (it will be the function of the editor that will be published next month by Korg).

However as soon as you have done your conversion you probably will find new possibilities for your framework.