These forums are read only, please use our new forums here.

Main :: POD HD


Support forums for all POD HD products


h5s file format...
by HwyStar on 2012-12-02 10:12:33

Does anyone know where the file specs are for the setlist files (*.h5s)?   Just curious since the file layout, using notpad.exe looks pretty staight forward.  Each record appears to be preceeded by an "HP5E" marker.



Re: h5s file format...
by johanneszab on 2012-12-02 15:45:29

There aren't any. Why should there for a proprietary file format?



Re: h5s file format...
by HwyStar on 2012-12-02 16:45:01

I know there is a tool that has already been created for printing setlists but it is not a windows based printing program. I was sort of thinking of creating a setlist print program that does not use the command line. It would be GUI based.   It would give you a standard windows open file dialog window and select your printer dialog when prompted to print. This way you could print to pdf files and send to other band mates if you like.



Re: h5s file format...
by johanneszab on 2012-12-02 17:00:36

I guess he did the same as me did, and you already started too: Figure it out on your own.

If you don't want to do all that stupid stuff again, i can send you everything i know about the file formats. I wanted to gpl my pod hd tool anyways.

But since you already know where the single presets start in the setlist, there should be a 16 byte long string that defines the name. Should be straightforward to extract it with your knowledge then.



Re: h5s file format...
by HwyStar on 2012-12-02 18:44:42

I just created a test setlist and the name is stored in the record 40 characters after the "H5EP" marker and the string of the name is 32 characters long.  That should be easy to pull out.

Do you know where the tempo is stored at in the record?

Thanks johanneszab!



Re: h5s file format...
by johanneszab on 2012-12-03 05:01:13

Oops, my bad, sorry. I didn't mean to misinform you, it's certainly 32 characters long. The 16 bytes were just for the HD 300/400.

So, the Tap Tempo is stored in the setlists files for HD 500/Desktop/Pro (.hxs) at 0xDB8 - 0xDBB, so 4 bytes as a 32-bit floating point number. I've just checked it with tap tempo 30, and the result was 0x41F00000, whichs fits.

Then it recurs all 0x1028 bytes. So:

1. 0xDB8 -- 0xDBB

2. 0x1DE0 -- 0x1DE4

3. ..

..

64. ..

I've just written my exam today, so i've some free time to write some "documentation" about my findings, .. just in case you want to add some more.



Re: h5s file format...
by HwyStar on 2012-12-03 06:52:56

Perfect johanneszab!

That's all I need for now.  Over the next few weeks I will play with this little project.  It's kind of funny since I don't have a HD500 yet but I am considering one.  I downloaded the editor to see if I liked the interface to control the POD.  Seems to work well enough.

While thinking through this setlist print program it gives me some ideas to use. Using the Line 6 Edit program for functionaility:

1)  Allow the printing option of printing on legal paper...  In the past when I have created setlists for bands I would print the setlists on legal size paper so that the player could tape the setlist to the floor.  Using 14 x 8.5 allows the font to be much larger and you can read the songs from a distance or standing over it.

2)  There is no vehicle within the Line 6 editor to create an ending mark in the set list for the breaks between sets (of a Line 6 setlist).  One solution is if you create a patch called "Break" at around the 13th to 16th slot my program can format the break on its printout.  I would also ignore printing "New Tone".

3)  My program could hold song notes to print, by song name/patch...  The Line 6 editor does not store notes by patch but my program could store notes or other fields of info like key signature, song starting notes, vocalist, etc.

Anyway, I want to think this through before I jump into it.  Thanks for your help johanneszab.



Re: h5s file format...
by HwyStar on 2012-12-03 17:40:19

I got to thinking about my last post and I was flippin out there...  I went back in to Line 6 Edit and studied it and not everyone uses it the way I was proposing. 

I coded the "Windows" program and created an exe (attached).  This program copies the contents of the selected file to the clipboard.  After the copy to the clipboard you can paste the contents into a spreadsheet or a word processor document.  Print it or modify it from there.

Instructions:

1)  Download the file to your computer and put it any where you want to on your hard drive.

2)  Extract the file SetList.asc from the file SetList.asc.zip.

3)  Rename the extracted file from: SetList.asc  to:  SetList.exe

4)  Create a shortcut to the program or double click on it in Explorer.

5)  Point to the directory where you have saved your SetList or Bundle. 

6)  If you are wanting to work with a Bundle file make sure you click on the drop down next to the file name to select the "Bundle" file type.

7)  The info is copied to the clipboard - done!

The only thing I could not get my head around was coping the Tempo into the clipboard.  My programming language did not want to read the long using the ascii file driver I had to use to keep it simple.  I will continue to give this some thought and if I can update it with Tempo I will.

I coded this for the POD HD500.  I do not have the software for HD300 or HD400 and I do not know if it will work for those file formats...  The program is only reading the file so it shouldn't hurt anything if you try it on a 300 or 400 file.  Don't know!  It will just toast your clipboard's contents.



Re: h5s file format...
by BeerHump on 2012-12-03 22:57:35

Good on ya HwyStar! Why this functionality isn't included in the editor is a complete mystery to me. It would seem to be a pretty straifgtforward thing to do (not meaning to diminish your efforts BTW). Maybe you could send the devs the code and they could tart it up to be a part of the next editor release! 



Re: h5s file format...
by HwyStar on 2012-12-04 05:48:26

Thanks BeerHump!  No big thang.  Usually it doesn't go this easy at work.  Yes, it would be super easy for Line 6 to implement this code in the edit program.  I am guessing about ten lines of code since everything is resident in memory. 

I have another compiler that compiles iOS software so if all goes well with this program I will transfer the logic of this program over to a Mac program.




The information above may not be current, and you should direct questions to the current forum or review the manual.