[Request] System as part of output path #500

Closed
opened 2026-01-29 16:17:27 +00:00 by claunia · 5 comments
Owner

Originally created by @mnadareski on GitHub (Feb 27, 2023).

Originally assigned to: @mnadareski on GitHub.

Add a new option (disabled by default) to include the shortname OR longname of the system in the output path. This may be useful for... someone.

Originally created by @mnadareski on GitHub (Feb 27, 2023). Originally assigned to: @mnadareski on GitHub. Add a new option (disabled by default) to include the shortname OR longname of the system in the output path. This may be useful for... someone.
claunia added the enhancement label 2026-01-29 16:17:27 +00:00
Author
Owner

@IcySon55 commented on GitHub (Feb 27, 2023):

Tag on Media Type as an optional path component as well for those that care. ^_^ (default off, default after system, can it be toggled to before system? up for discussion.)

@IcySon55 commented on GitHub (Feb 27, 2023): Tag on Media Type as an optional path component as well for those that care. ^_^ (default off, default after system, can it be toggled to before system? up for discussion.)
Author
Owner

@mnadareski commented on GitHub (Mar 5, 2023):

I mentioned this in Discord, but I'd prefer to have a static order to the output, so "SYSTEM/MEDIA" with either being toggleable. Not intending on getting this looked at until after next stable at earliest.

@mnadareski commented on GitHub (Mar 5, 2023): I mentioned this in Discord, but I'd prefer to have a static order to the output, so "SYSTEM/MEDIA" with either being toggleable. Not intending on getting this looked at until after next stable at earliest.
Author
Owner

@IcySon55 commented on GitHub (Mar 6, 2023):

I may have some other ideas about this as well. ^_^

@IcySon55 commented on GitHub (Mar 6, 2023): I may have some other ideas about this as well. ^_^
Author
Owner

@mnadareski commented on GitHub (Oct 18, 2023):

Implementation note: use templated values such as %SYSTEM% to define the points of replacement. This allows it to not be a setting. All of the values need to be defined ahead of time, though.

How would system changes be handled? Are the "real" and "templated" paths going to have to be stored separately?

@mnadareski commented on GitHub (Oct 18, 2023): Implementation note: use templated values such as `%SYSTEM%` to define the points of replacement. This allows it to not be a setting. All of the values need to be defined ahead of time, though. How would system changes be handled? Are the "real" and "templated" paths going to have to be stored separately?
Author
Owner

@Deterous commented on GitHub (Jan 8, 2024):

The user being able to input variables into the Output Path box seems the best approach. The following could be evaluated once dumping has started to determine the output path:

  • %SYSTEM% (e.g. /PlayStation 2/)
  • %SYS% (short version, becomes /PS2/)
  • %MEDIA% (e.g. /CD-ROM/)
  • %PROGRAM% (e.g. /DiscImageCreator/)
  • %PROG% (short version, becomes /DIC/)
  • %LABEL% (Volume Label)
  • %DATE% (e.g. /20240108/)
  • %DATETIME% (e.g. /20240108-093002/)

The default output path could then be manually set to something as complex as e.g. ISO/%SYS%/%MEDIA%/%PROGRAM%/%DATE%

@Deterous commented on GitHub (Jan 8, 2024): The user being able to input variables into the Output Path box seems the best approach. The following could be evaluated once dumping has started to determine the output path: - `%SYSTEM%` (e.g. /PlayStation 2/) - `%SYS%` (short version, becomes /PS2/) - `%MEDIA%` (e.g. /CD-ROM/) - `%PROGRAM%` (e.g. /DiscImageCreator/) - `%PROG%` (short version, becomes /DIC/) - `%LABEL%` (Volume Label) - `%DATE%` (e.g. /20240108/) - `%DATETIME%` (e.g. /20240108-093002/) The default output path could then be manually set to something as complex as e.g. `ISO/%SYS%/%MEDIA%/%PROGRAM%/%DATE%`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/MPF#500