Custom Monolith Extension possible

[ustk]

@danh you're right, it has to be changed in the source.
It would be nice to have a setting for this extension so we all have the possibility of setting a personalized extension easily.

[d.healey]

@ustk said in Custom Monolith Extension possible:

so we all have the possibility of setting a personalized extension easily.

Are you ashamed of your library's HISE origins :p

[ustk]

@d-healey It is absolutely not a question of being ashamed but the intention of a personalized branding image.
That been said, I am not releasing a sample-based instrument anytime soon :)

[d.healey]

@ustk said in Custom Monolith Extension possible:

personalized branding image

Just change your brand to Cat Hammock Audio and you're sorted, no need to edit the source code :)

[DabDab]

@d-healey said in Custom Monolith Extension possible:

@ustk said in Custom Monolith Extension possible:

so we all have the possibility of setting a personalized extension easily.

Are you ashamed of your library's HISE origins :p

This is not a question of shame or pride , if we can create own Extension for monolith it looks very professional to end user. And to be honest .ch1 never looks very professional. Pardon me for my opinion. I love and like HISE very much. If we can create own user presets extension then why not Custom extension for Monolith? It should be a future feature request.

[d.healey]

@dabdab said in Custom Monolith Extension possible:

.ch1 never looks very professional

What is a professional file extension?

[Tania Ghosh]

@danh said in Custom Monolith Extension possible:

@dabdab Yes I think @Tania-Ghosh asked this a while back, the answer was to change the source code I believe.... Have a search on the forum

Yeah, I tried but did not get success. If you investigate HiseLosslessAudioFormat.cpp and WavetableTools.cpp you can see there is a String array of { ".hlac", ".ch1", ".ch2", ".ch3", ".ch4", ".ch5" } . But after modification every time HISE only generates .ch1 file and recognize only .ch1 file. I don't know what the genius @Christoph-Hart has done for ch1 file instead custom Extensions. I hope @Natan , @DanH , @ustk may help you regarding this.

[Tania Ghosh]

And yeah my opinion is HISE should have a custom monolith extension.

[DabDab]

@d-healey said in Custom Monolith Extension possible:

@dabdab said in Custom Monolith Extension possible:

.ch1 never looks very professional

What is a professional file extension?

Professional extension means as a company it will be custom. No other will use the same extension. Imagine you are a big renowned company ( I know you are still imagine ) you need to use custom File extension for monolith. It will be your entity.
One more point every one who uses sample based HISE compiled plugins get .ch1 extension. It should be unique and different.

[d.healey]

@dabdab said in Custom Monolith Extension possible:

Imagine you are a big renowned company

I always try to think of things from the customer's point of view instead of the company's. I prefer standardisation to reimplementation. Hiding the file format from the customer by changing the extension is not a great benefit to anyone.

Do you also want to change the hr extension, since the user is more likely to interact with this than the ch files?

[DabDab]

@d-healey No, HR is just an Archive format. Ch1 files are loaded in Samples folder that is always reflected to End user. And I am not trying to hide an extension. I would like to request more extension or monolith extension customization.

changing the extension is not a great benefit to anyone.

of course benefit. Everybody who uses HISE has different approach, our works are different, Our talent are different, our purposes of Plugins are different then why same extension for Sample based plugins? If you say end user will come to HISE forum by knowing .CH1 file extension then this is another issue.

And one more thing

Is it Channel 1 or CH for Christoph-Hart ? Then Why CH1? Why not .hart?

/

[d.healey]

@dabdab It's channel. If you use multi-mic samples you'll get ch1, ch2, ch3, etc.

[DabDab]

It's channel. If you use multi-mic samples you'll get ch1, ch2, ch3, etc.

OK. Great.

I guess OGG vorbis or something JUCE coding is the mastermind behind .ch extension.

[Christoph Hart]

Shouldn't we all have something better to do than talking about the file extension?

I won't change it, if you do, modify the source code and hope for the best.

[A Former User]

@christoph-hart

[DabDab]

I won't change it

Sometimes only a good teacher pushes hard to solve a puzzle by yourself.

[d.healey]

@dabdab https://file.org/extension/dbb

[DabDab]

@d-healey No problem, I can now change it to my own Extension.

[d.healey]

@dabdab Does it work with multiple channels?

[DabDab]

@d-healey said in Custom Monolith Extension possible:

@dabdab https://file.org/extension/dbb