Doom9's Forum - View Single Post

Mosu · 21st July 2015, 19:59

I don't really want to change them either. My current plan is to save each of the job queue's job in a separate file. That way the application has to write far fewer bytes each time the settings are changed. Additionally changing a single job will only require writing that single job's file.

That being said: the INI files themselves do become kind of huge, especially if you've got as many tracks as you do (more than 20 appended files with > 10 tracks each). I know that this is kind of normal for Blu-ray discs, and therefore there are limits to how fast it'll become, I guess. The INI format isn't the most efficient storage format, unfortunately. It only really supports one level of groups, and therefore deeply-nested structures require listing all of the intermediate group names time and again:

Code:

job%200\muxConfig\input\files\0\appendedFiles\0\tracks\12\aacSbrWasDetected=false
job%200\muxConfig\input\files\0\appendedFiles\0\tracks\12\additionalOptions=
job%200\muxConfig\input\files\0\appendedFiles\0\tracks\12\appendedTo=68604232
…

Maybe I will have to change to some other formats capable of storing deeply-nested structures more efficiently (YAML, JSON, even XML…). But let's see how well storing each job in a separate file works.

21st July 2015, 19:59	#3452 \| Link
Mosu MKVToolNix author Join Date: Sep 2002 Location: Braunschweig, Germany Posts: 4,352	I don't really want to change them either. My current plan is to save each of the job queue's job in a separate file. That way the application has to write far fewer bytes each time the settings are changed. Additionally changing a single job will only require writing that single job's file. That being said: the INI files themselves do become kind of huge, especially if you've got as many tracks as you do (more than 20 appended files with > 10 tracks each). I know that this is kind of normal for Blu-ray discs, and therefore there are limits to how fast it'll become, I guess. The INI format isn't the most efficient storage format, unfortunately. It only really supports one level of groups, and therefore deeply-nested structures require listing all of the intermediate group names time and again: Code: job%200\muxConfig\input\files\0\appendedFiles\0\tracks\12\aacSbrWasDetected=false job%200\muxConfig\input\files\0\appendedFiles\0\tracks\12\additionalOptions= job%200\muxConfig\input\files\0\appendedFiles\0\tracks\12\appendedTo=68604232 … Maybe I will have to change to some other formats capable of storing deeply-nested structures more efficiently (YAML, JSON, even XML…). But let's see how well storing each job in a separate file works. __________________ Latest MKVToolNix is v101.0 If I ever ask you to upload something, please use my file server.