Recording fixes: date folders on top, and multi-track honours the Source setting
Two issues Ed found testing: * The default recordings path was recordings\<machine>\, so date folders nested under a machine-name folder. Dropped the per-machine subfolder — recordings now nest by date at the top (recordings\<yyyy-MM-dd>\...); the machine name still appears in split-track file names. * Multi-track always created the "me" (sent) track regardless of the Source setting, so a receive-only recording wrongly produced a track of your own machine. Multi-track now follows Source like single-file does: peer (received) tracks unless "sent only", and your own (sent) track only when Source is "both" or "sent only". Held for next release. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
6b1e65f418
commit
fc4ad3bb92
@@ -127,11 +127,10 @@ public sealed class RecordingSettings
|
||||
|
||||
/// <summary>Default folder path used when <see cref="Folder"/> is blank. Computed at
|
||||
/// call time (not cached) so a launch from a different exe directory picks up that
|
||||
/// directory rather than the first-load one. The per-machine subfolder lets two
|
||||
/// machines sharing a Dropbox-backed RemSound install keep their recordings tidily
|
||||
/// separated by sender identity.</summary>
|
||||
/// directory rather than the first-load one. Recordings nest by DATE inside this — the
|
||||
/// machine name lives in the split-track file names, not a top-level folder.</summary>
|
||||
public static string DefaultFolder() =>
|
||||
Path.Combine(AppContext.BaseDirectory, "recordings", Environment.MachineName);
|
||||
Path.Combine(AppContext.BaseDirectory, "recordings");
|
||||
|
||||
/// <summary>Returns the resolved folder this profile would record into right now —
|
||||
/// either the explicit <see cref="Folder"/> if set, or <see cref="DefaultFolder"/>.
|
||||
|
||||
Reference in New Issue
Block a user