Recent Posts

Pages: [1] 2 3 ... 10
1
Support and Feedback / Just want to say Hello!
« Last post by NicoleWill on Today at 20:45:32 »
thuoc cialis gia bao nhieu https://cialisusy.com/ - cialis without a prescription
kesan sampingan cialis
lisinopril cialis interaction cheap cialis online cialis how long
2
I tried foobar.. I got the same issue. classic Winamp and other players I have, have no issue. only foobar.

Foobar is doing something different with their association in registry compare to all other apps I have that support this.
Normally you want to open all on the "open" command. but they do not do that.
They have the correct settings in the registry but they disabled them by adding a "LegacyDisable" key

So I got it working by removing or rename the "LegacyDisable" key under HKEY_CLASSES_ROOT\foobar2000.MP3\shell\open\
And for FLAC I guess it is under foobar2000.FLAC  so you need to do this for all extensions

3
Support and Feedback / Re: Launching of apps associated to file types
« Last post by pstrg on July 29, 2020, 02:33:47 »
Looks like something was caught this time.

4
Thank you for the replies.  Its one of those features that I got used to using for many years. Due to that 'training', I keep trying to do it in MC even though I know it's not there.
5
Ehh Nothing ? That is not correct.
It should always print out the result code in the log like
"<DATE> <TIME> ShellExecute Error 0"

Did you remove the custom filetype setup you did?

But I don't really know what this will give you. It will probably give you an error code that is sent from Windows that is nonsens.
There must be something with how foobar is registered that is wrong/missing if for now it queue files if multiple files are launched

6
Support and Feedback / Re: Launching of apps associated to file types
« Last post by pstrg on July 28, 2020, 22:33:53 »
I appreciate your patience.
Application debug now enabled as well.
After I select a number of files and hit Enter, nothing happens and no new data appears on the log window.

https://i.imgur.com/oZ7HRyT.jpg[/img]]http://imgur.com
7
Quote
As I said before. You need to enable loglevel "debug" for it to show the error sent from Windows.
MC is not launching foobar2000. MC tell windows to open these file with whatever you have configured with file associations.
MC is forwarding all to Windows. It should be the same as Windows Explorer does. It does the same thing.
I works for me for winamp and other program. FooBar2000 I never tested on that. And I currently do not have the ability to do that

Please note that logging was already enabled...
In fact, just in case, tried each of the four Debug settings (Eval, Trace, Result, Begin/End).
In all cases, upon selecting files and hitting Enter, nothing shows up on the debug tab(s).



That is  "Filesystem Log" (Log for Filesystem scanning and such) If you look at the top you see "Application Log"set the loglevel for this to "Debug"
The log for filesystem log you can disable again. It is very verbose and you do not need that.

8
Support and Feedback / Re: Launching of apps associated to file types
« Last post by pstrg on July 28, 2020, 19:01:07 »
Quote
As I said before. You need to enable loglevel "debug" for it to show the error sent from Windows.
MC is not launching foobar2000. MC tell windows to open these file with whatever you have configured with file associations.
MC is forwarding all to Windows. It should be the same as Windows Explorer does. It does the same thing.
I works for me for winamp and other program. FooBar2000 I never tested on that. And I currently do not have the ability to do that

Please note that logging was already enabled...
In fact, just in case, tried each of the four Debug settings (Eval, Trace, Result, Begin/End).
In all cases, upon selecting files and hitting Enter, nothing shows up on the debug tab(s).



9
Addendum

Besides the (already existing) Windows associations, forced association of some audio files like this:



Then, selected a number of such files and, with mouse still over the selection, hit Enter - nothing happened (no new lines in Application Log either).
You can probably not do that if you want the program to queue all files instead of opening X numbers of instance of foobar.

I Now for winamp you needed to do "Winamp.exe /add <filename>"  to make it do the queue. for foobar I have no idea.

Also If I remeber it correct the fileextension need to be *.mp3 *.flac and so on as you see in the default item for viewers/editors.
10
Sure, sent the other log because the Application Log contains nothing related either to multi-file or single file events.
It's just like this:

Code: [Select]
...
2020-07-28 09:43:27.061 Initializing extension : File Utils
2020-07-28 09:43:27.064 Initializing extension : Multi Rename
2020-07-28 09:43:27.065 Initializing extension : File Viewer
2020-07-28 09:43:27.068 Initializing extension : Picture Tools
2020-07-28 09:43:27.069 Initializing Complate
2020-07-28 09:43:27.540 Application Ready!
2020-07-28 09:43:27.541 Start background thread to check if new version exists.
2020-07-28 09:43:28.273 No new version found

Note that I duly understand what you repeated in the previous replies to my issue.
What is not clear to me is
- why is CM able to launch foobar2000 as expected when I try to open a single file
- but does nothing at all if I try to open more than one simultaneously.
Shouldn't it emulate the usual File Explore behavior?

As I said before. You need to enable loglevel "debug" for it to show the error sent from Windows.
MC is not launching foobar2000. MC tell windows to open these file with whatever you have configured with file associations.
MC is forwarding all to Windows. It should be the same as Windows Explorer does. It does the same thing.
I works for me for winamp and other program. FooBar2000 I never tested on that. And I currently do not have the ability to do that

Pages: [1] 2 3 ... 10