Info tool for sfs files

[HYPNAGOGIA]

Personally, can't wait to see what you're cooking

I do have question, though.
What good is this tool for Macs, being that Orion was Windows only?
I'm guessing I'm just not quite understanding what this tool will actually do to grasp why it's useful for Macs ¯\_(ツ)_/¯

[Jouni]

Found one new copy of Orion source code from backup disk, it's some beta 8.0 so missing something from full 8.0, but I can add hopefully working 8.0 file support too. Obviously there might be something new I'm not aware as the development continued some months after I moved on.

So updating those few this regard that.. other than that the app is ready and I sent (hopefully it came through) message to Richard to check it out before making it public.

What comes to the macOS version, it's useful for me as today I'm 100% mac user (Logic Pro X) and developer and Windows is usually just last resort. I can run Orion in Parallels https://www.parallels.com/, that much what is needed. I will make Windows version of the app later, it's mostly just setting up the compiler in the Parallels. Maybe later to automate it in some app building service.

[Jouni]

Done now to certain point, and there's also 64-bit Windows version, was fairly easy at least to do locally.

Video how it (command line tool) works (for geeks):

http://www.kettureaktio.fi/orionology/orionology-1.1.0.mp4

macOS: http://www.kettureaktio.fi/orionology/orionology-mac-1.1.0.zip
Windows (64-bit): http://www.kettureaktio.fi/orionology/orionology-win-1.1.0.zip

I'll make the source code open source when Richard has time to check it briefly. I'm sure he's very busy with Obsession right now.

App does not have any specific added tools such as midi export and not all data is displayed, even though it's loaded in memory. Treat app as alpha in that sense. A place to start from, if something is needed.

[megawattt]

Many thanks Jouni.

Being a die hard Orion user this tool will come in very handy , will midi export be added in the future ?

[Jouni]

If I can find need for midi export in such what Orion cannot do right now. Orion midi export was slightly simple, but effective.

That said, after Richard gives the go, the source code will be open source for this tool. Then anyone brave enough can make features they need. I'll merge them in if needed.

[HYPNAGOGIA]

Cool!

Thanks Jouni.
Hope to see if this source comes out. Wouldn't mind taking a look under the hood

[Jouni]

Okay, Richard has probably looked (hopefully) the source code now and he did say earlier that maybe just make it public.

So the source code in it's current form can be found (and the prebuilt release links): https://gitlab.com/stardrivestudio/orionology

Hopefully it is useful for someone and giving small insight into Orion, even though it's not using Orion's code directly and just some of the data structure definitions (copy paste).

[BMS]

Wow, this is quite the thing! Thanks Jouni

I'd previously been using PowerGREP and specific Regexes to pull the names of samples from the binaries into a list, and then using those lists to rebuild self contained sample folders for each *.sfs file. Same with pulling the VST names that were used in projects for reference.

This is amazing in that it converts it all to plaintext, and gives far more information about all sorts of things.

Tried redirecting the output of this into a text file from CMD/PS, so I could automate some things but I only seem to get the last bit which is written to the host, (input, filename, version and all good part.)

I'll see if I can figure out how to pipe the INFO and DEBUG stuff into a txt file/csv if it's possible, would be MEGA handy.

[BMS]

Best I could do to get the Orionology output to write into a txt file in Powershell (in the time I had to look was)

Start-transcript
Then run orionology on a file
Then stop-transcript

Crap I know!

Redirecting the output stream only sent the bit at the end that's actually written to the host to the file otherwise, probably isn't doing a proper stdout, so couldn't store in a var or pump out with out-file or whatever.

Hopefully get some more time to look into that, cause would be handy to run this command over a bunch of files and get txt files outputted from each sfs.

[Jouni]

I can't remember the details anymore without looking the code, but I recall I used the logging package for it. It might go to stderr (in macOS), don't know how it functions in powershell.

[BMS]

Thanks for the reply, never got around to digging any deeper myself there, still very a insightful tool you made here for inspecting files one at a time.

[BMS]

Been toying actually in a bit of downtime this morning actually.

With help from a good friend, he wrote, and I tweaked a simple PowerShell script which runs through a folder of .sfs songs and make a text file for each song with the info that comes out of ORIONology in each one.

From there I've been running various regexes on those files to collect the names of samples I'd used in old tunes / vsts and build a master list.

Will run find and move script I have using that list to collate all those samples from across my old backup/archive/sample pool drives into a failsafes folder, or even make a folder for each respective song and 'collect' all the stray samples so I can be sure that I can dump a load of older unwanted samples and stuff that got mixed in but still have my legacy projects open with no missing samples.

I did this before but using a crude way of searching for data across the binaries with regexes, which worked but I'm sure some stuff got missed. I'm going to compare this to see if I get better results.

Once again, Thank you so much Jouni for making/Richard for allowing this tool.