Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: File Operations > Move to: regression/new feature? (Read 738 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

File Operations > Move to: regression/new feature?

Hello everyone!

Been using foobar for 10 years, and all of a sudden the behavior of "File Operations > Move to > ..." changed.
(I verified this for 1.54 as well as, 1.5 on two different computers).

So far (up until the very least 1.3.x) using the "..." option yielded the last used operation. I'd use a template on some songs, edit a couple of others, hit the "..." and get the same operation, which was very useful in case of using a modified preset.
Now, however, I get the last used "..." operation instead of the last (whatever) operation.

Is this intentional? While I can see the upside of the new behavior (sorta quick save whithout the need to save a proper template), this messes with my workflow.

If this is not intentional, maybe it can reverted but the bugged behavior still be included as a quick save option?

If need be, I can provide a dump of all components or other things; however, since this has been working for me for 10 years and I didn't make any changes recently...

Thanks :)

Re: File Operations > Move to: regression/new feature?

Reply #1 –
I see no change in behavior between the latest foobar2000 and version 1.3.20. Perhaps you should provide more detailed steps to reproduce the issue.

Re: File Operations > Move to: regression/new feature?

Reply #2 –
Expected behavior:
no matter what I choose as a move option
Move to: <some template>, or
Move to: <some modified template>, or
Move to: ...
...

"Move to: ..." gave me the exact same mapping

Now, "Move to: ..." gives me only the exact same mapping that was used with "Move to: ..."
So, I use
Move to: <some template>,or
Move to: <some modified template>
the option "Move to: ..." doesn't care but gives me the last mapping used with "Move to: ..."

There isn't anything else I'm doing inbetween moving files (other than editing...) and I have not changed my workflow. As I said, it worked as expect up until 1.3.15 (or something); I noticed this on my music machine so I updated an old foobar install to the latest stable release and got the same behavior.

Both computers are running Windows 10 Home, and use the same components:
Core (2020-06-29 11:49:42 UTC)
    foobar2000 core 1.5.5
foo_albumlist.dll (2020-06-29 11:49:14 UTC)
    Album List 4.7
foo_burninate.dll (2016-06-17 22:42:29 UTC)
    Audio CD Writer 3.0.3
foo_cdda.dll (2020-06-29 11:48:58 UTC)
    CD Audio Decoder 1.5.5
foo_converter.dll (2020-06-29 11:49:06 UTC)
    Converter 1.5.5
foo_dsp_eq.dll (2020-06-29 11:49:00 UTC)
    Equalizer 1.2.2
foo_dsp_std.dll (2020-06-29 11:48:56 UTC)
    Standard DSP Array 1.5.5
foo_facets.dll (2016-06-17 22:42:29 UTC)
    Facets 1.0
foo_fileops.dll (2020-06-29 11:48:58 UTC)
    File Operations 1.5.5
foo_freedb2.dll (2020-06-29 11:48:58 UTC)
    Online Tagger 0.7
foo_input_monkey.dll (2020-07-20 20:41:28 UTC)
    Monkey's Audio Decoder 2.3.1
foo_input_std.dll (2020-06-29 11:49:32 UTC)
    FFmpeg Decoders 3.4.6-0ac9001
    Standard Input Array 1.5.5
foo_jesus.dll (2016-06-17 22:42:29 UTC)
    Autosave & Autobackup 10
foo_out_upnp.dll (2016-06-17 22:42:29 UTC)
    UPnP MediaRenderer Output 1.0 beta 15
foo_playcount.dll (2016-06-17 22:42:29 UTC)
    Playback Statistics 3.0.2
foo_playlist_revive.dll (2016-06-17 22:42:29 UTC)
    Playlist Revive 0.2
foo_plorg.dll (2016-06-17 22:42:29 UTC)
    Playlist Organizer 2.6
foo_quicksearch.dll (2016-06-17 22:42:29 UTC)
    Quick Search Toolbar 3.6
foo_quicktag.dll (2016-06-17 22:42:29 UTC)
    Quick Tagger 1.0.3
foo_random_pools.dll (2016-06-17 22:42:29 UTC)
    Random Pools 0.1.5
foo_removeplayed.dll (2016-06-17 22:42:29 UTC)
    Remove played Files 1.4.0
foo_rgscan.dll (2020-06-29 11:49:10 UTC)
    ReplayGain Scanner 1.5.5
foo_run.dll (2020-07-20 20:41:29 UTC)
    Run services 0.3.8
foo_textdisplay.dll (2016-06-17 22:42:29 UTC)
    Text Display UI Element 1.1 beta 1
foo_tfsandbox.dll (2017-06-28 18:54:16 UTC)
    Title Formatting Sandbox 1.0.3
foo_ui_std.dll (2020-06-29 11:49:18 UTC)
    Default User Interface 1.5.5
foo_uie_biography.dll (2016-06-19 16:55:48 UTC)
    Biography View 0.4.2.4
foo_uie_esplaylist.dll (2016-06-17 22:42:29 UTC)
    EsPlaylist 0.1.3.9
foo_uie_lyrics3.dll (2016-06-17 22:42:29 UTC)
    Lyric Show Panel 3 0.5
foo_unpack.dll (2020-06-29 11:49:06 UTC)
    ZIP/GZIP/RAR Reader 1.8
foo_upnp.dll (2018-11-10 22:02:28 UTC)
    UPnP/DLNA Renderer, Server, Control Point 0.99.49
foo_verifier.dll (2020-07-20 20:41:28 UTC)
    File Integrity Verifier 1.2.1

I also went through the change log, but found nothing that hinted to a change.
I know, this post is kinda just a repeat of the initial one, but since I'm not doing all that much (basically just using "Move to"), I don't know how I could shed more light.
Is there anything more I could share?
 

Re: File Operations > Move to: regression/new feature?

Reply #3 –
You provided more details this time but perhaps I still don't understand what you are saying.
I downgraded my foobar2000 v1.3.20 test install to version 1.3.15.

I saved a "test" preset with filename pattern "%album artist%\'('%date%')' %album%\%tracknumber%. %title%".

I used "Move to -> ..." action on a test track and changed the target pattern to "%tracknumber% - %title%" and hit "Run".

I then used the "Move to -> test" action to move the test track to a different location with the stored preset.

Now when I open the "Move to -> ..." menu it suggests the pattern "%tracknumber% - %title%".

And this is how I see it behaving still in foobar2000 v1.6 beta 7.