Explicitly hiding playlist when starting AIMP from the command line.

[Artem]

Please, try on build 3070. I've added parameters for /MUTE switch: specify /MUTE=0 to unmute or /MUTE=1 to mute.

[ivanlc]

Hi Artem.

Maximum respect for creating this build for me. 🙇‍♂️

I didn't expect you to even bother replying, never mind creating a custom build! 🤗

... Unfortunately, however, build 3070 doesn't seem to support the /DEBUG switch; only one instance is allowed whether or not the /DEBUG switch is specified.

Also, I've tried specifying /MUTE=0 and /MUTE=1, but each time the one instance opens, it isn't muted; rather the volume is set to zero, which isn't the same thing. I can do this with the /VOLUME switches - which isn't ideal because it sets the volume to zero instead of muting it...

Is the /DEBUG functionality available in build 3070 at all or have you perhaps (unintentionally) omitted it...?

 

[Artem]

I didn't expect you to even bother replying, never mind creating a custom build!

This is not a custom build, I've added parameters to official branch.

Unfortunately, however, build 3070 doesn't seem to support the /DEBUG switch

Apparently, you haven't read the changelog, as AIMP6 has a separate key for running a second copy, and /DEBUG only activates debugging.

rather the volume is set to zero, which isn't the same thing

No, it does not. Of course, if you've set volume to zero, the mute will do nothing

[ivanlc]

Hi again Artem.

I need give you "props" (which means "proper respect" in English street jargon 😉) for officially implementing the /NEWINSTANCE switch...🙇‍♂️

This makes a lot more sense than /DEBUG did...(!) 👍/👌

(Although I can completely understand that in the early years of the app's development - before it (quite rightfully) became one of the most popular and feature-rich audio apps as it is now - running multiple instances would have been something that only you (as the developer) and serious audiophiles like myself would really have needed to do. 🎵🎶)

I also need to give you (even more👌) props for implementing the explicit /MUTE switch.

... Now I know how to use it correctly (initially, it didn't work because I'd put "=" between the word "MUTE" and the value...🤦‍♂️), all 12 instances of AIMP open exactly where I want them to on the desktop - and without the NOISE of 12 different radio stations all streaming at maximum volume...!! 😱/😖

Now could I also suggest adding a /PLAYLIST switch...?

The playlist window is typically much bigger than the player window and so takes up a lot more space on the desktop.

I think that being able to show or hide it for particular instances of the app with a "/PLAYLIST 1" and a "/PLAYLIST 0" switch would be an incredibly useful feature...🙏

... What do you think...?

[Artem]

Now could I also suggest adding a /PLAYLIST switch...?

The playlist window is typically much bigger than the player window and so takes up a lot more space on the desktop.

I think that being able to show or hide it for particular instances of the app with a "/PLAYLIST 1" and a "/PLAYLIST 0" switch would be an incredibly useful feature...🙏

As I say before, it depends from used skin. Some skin may not have separate playlist window.

[ivanlc]

Actually, it's no longer a problem. 

Since I always do a portable install, what I've done is install two copies of AIMP in two different directories.

Then, using PowerToys Workspaces, I simply start 12 copies - for each of which the playlist is turned off - each instance streaming one of the 12 stations I listen to.

I then start a single playlisted instance to the left of the other 12, which is set to play the tracks on the HDD which I want to play when not streaming.

Since i can now explicitly mute/unmute each instance thanks to your de-XORing the switch,
 (🙇🏿‍♂️) the cacophony situation is avoided. 👍🏿

My only issue was that after carefully curating the index of the station each of the non-playlisted instance plays, PowerToys wouldn't start them. However, a restart of the system fixed this issue, so everything is now pretty much copasetic...😊