Author Topic: Bliss / Cas-Stunts track editor  (Read 26189 times)

afullo

  • Otto's Student
  • **
  • Posts: 354
    • View Profile
    • DoomItalia
Re: Bliss / Cas-Stunts track editor
« Reply #195 on: January 10, 2021, 08:48:05 AM »
I agree: as a beta, interested pipsqueaks can compile it by themselves.

dreadnaut

  • Corkscrew Cad
  • ***
  • Posts: 1075
    • View Profile
    • chezDreadnaut
Re: Bliss / Cas-Stunts track editor
« Reply #196 on: January 10, 2021, 11:45:32 AM »
But even though it's not in the menu, that is already available!  Just edit the configuration file. Where it says "format=bliss" or whatever, change it to "format=none" or "format=trackblaster". Let me know if that works for you.

Ah, I knew that, then I forgot! Thanks for updating things :)

It could be useful to have options listed in the configuration, for example (probably with incorrect descriptions):
Code: [Select]
; Default format for new tracks
; Possible values:
; - bliss: binary metadata at the end of the track data
; - text: text metadata in a separate .smd file
; - none: no metadata
; Default:
;  format = bliss
format=bliss

Cas

  • Helen`s Lover
  • **
  • Posts: 650
  • Think different. That's OK... as long as you think
    • View Profile
    • Dimioca Labs
Re: Bliss / Cas-Stunts track editor
« Reply #197 on: January 10, 2021, 07:49:47 PM »
Dreadnaut:
Yes, there's something I should change about the config file. Currently, when you save the configuration, Bliss deletes the old config file and creates a brand new one from the configuration in memory. This is not good. What it should do instead if read the current configuration file and replace the relevant lines so they match the current configuration in memory. This way, one could add their own comments to the file and things like that and this would also make it easier to add what you suggest as I could just include that in the original config file that comes with Bliss.

One detail I wanted to point out about how I implemented the change in the menu option now. There are two different things in Bliss in memory at any time: the default file format and the current track default file format. Let's call them DTF (default track format) and CTF (current track format, not capture the flag). The DTF is the format in which your track will be saved as default if you create a new one from scratch. This is what you can change from the Settings menu. Bliss will warn you if you set this to Raw only if it wasn't Raw already. The CTF is the format in which the track you're currently editing is going to be saved by default. When you start a new track, the CTF is set to the DTF, but if you load an existing track, the CTF will be set to that track's current format. This prevents accidentally changing a file format because of making a little change. If your DTF is Raw and you access the Track Info menu (for metadata), you will get a warning saying that the CTF has been set to one-file. You still can save the track as Raw, only it won't be the default option in the menu and your DTF has not changed. When you create a new track, it will be Raw again. Let me know if this doesn't make much sense to you. I tried to make it as logical as possible, but it is kind of complex.

Afullo:
Thank you. That's right. Otherwise, at this stage, we'd be compiling over and over again. I'm sure I'm going to have to make a few more changes, so the best thing is to keep both the stable and the unstable versions in the website.
« Last Edit: January 10, 2021, 07:59:40 PM by Cas »
Earth is my country. Science is my religion.