Add support for custom preset folder for Xbox app

[ghost]

We have UWP support for the milk drop engine. This required OpenGLES3 for Xbox and windows universal. I have completed the requirement and packed the library for x86, x64, and arm. The system needs to support user control of presets because that is the best part of the whole visualizer. Also the app needs some projectM branding in the logo art that i will add. The source has been merged back into this repo and free release is available for Xbox and PC and Phone at https://www.microsoft.com/en-us/p/eyetune/9ndcvh0vcwjn

[revmischa]

Neat! Why not call it projectM tho?
If you want to chat - #projectM on freenode

[ghost]

projectm within the App Store has been claimed. Thoughts on the name eyetune for the new projectm client? I base this on two reasons: 1. Project M confused a few of my friends when they searched for it, something with super smash brothers 2. Project M is already released in other app stores, but it’s not a part of this code. That is outrageous, the client requires a different name. What if I want to release on android or iOS? What am I supporting? I can’t because there is already a projectM on those App Stores and I can’t update it to work for my nieces’ iPad. That annoys me.

…

On Apr 27, 2019, at 11:06 AM, Mischa Spiegelmock ***@***.***> wrote: Neat! Why not call it projectM tho? If you want to chat - #projectM on freenode — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[votedan]

Amazing work. Perhaps you could mention proectM in the title at the end in brackets so people can find it?

Do you think there is hope for multiple monitor support on PC?

[revmischa]

both are annoying.. the smash bros clone stole the name. the ios/android versions are from the same original codebase but with proprietary modifications :(
what about projectW? W is windows and M upside-down

[ghost]

I really like eyetune because it rips on 🍏 haha

…

On Apr 27, 2019, at 3:37 PM, Mischa Spiegelmock ***@***.***> wrote: both are annoying.. the smash bros clone stole the name. the ios/android versions are from the same original codebase but with proprietary modifications :( what about projectW? W is windows and M upside-down — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[revmischa]

I mean okay but... not really

[ghost]

I am open to compromise, however I have already pushed the app to the windows store with the eyetune name. I have actually been working on uwp visualizer long before I started contributing here. Do you have an Xbox or windows pc/phone to test it out?

…

On Apr 27, 2019, at 4:40 PM, Mischa Spiegelmock ***@***.***> wrote: I mean okay but... not really — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ghost]

Ok I have reserved a few more names for the App, hopefully we won’t have any issues with rename process. I reserved “projectM” and “Milkdrop” and “visualized”. Any thoughts here? I am leaning towards milkdrop

[revmischa]

i think projectM makes sense. maybe put milkdrop in the description but calling it milkdrop is a little misleading

[ghost]

Okay, I will initialize change of name to projectm.

…

On May 5, 2019, at 11:23 AM, Mischa Spiegelmock ***@***.***> wrote: i think projectM makes sense. maybe put milkdrop in the description but calling it milkdrop is a little misleading — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[teotigraphix]

same original codebase but with proprietary modifications

How does this work the the LGPL? I thought if you changed to code you need to release it for source code availability.

The Android version online hasn't been updated since 2016. I am going to be making something from this library, so if I can get deep into it, you have another contributor.

[revmischa]

@teotigraphix there is definitely interest - take a look at the recent PR projectM-visualizer/projectm#191

[Drakonas]

Are there any updates on this? If I gain access to the app's folder in C:\Program Files\WindowsApps, I can see there is a folder called "e" with a bunch of .milk presets and a folder called "p" with a smaller number of .milk presets. What is the organization here?

Secondly, where do the textures go? There is no folder for it?

I agree with the OP. Most of the power behind MilkDrop is the open nature of the preset format. There are projects like this Cream of the Crop collection with presets that work with ProjectM and MilkDrop, and locking it to the built-in presets really limits its capability. Most of the included presets for ProjectM/MD are very old and not as snazzy as a lot of packs out there.

[kblaschke]

AFAIK the Windows Store version has some limitations that are imposed by the WinRT platform, most notably running sandboxed. I think there must be a way to allow the app to access files outside the app package, but both the author and the user need to enable it. In this case, using presets from the outside system should be possible.

Sadly, EyeTune seems to have entered the same state of abandonment as the Android app. We'll shortly out-source the code for these integrations into separate repositories, which will make it more visible when the code base was last changed and if there's still active development happening. Authors of the main projectM library mostly have no way of pushing updates to those store versions as they were done by individual authors. The only exception would be the iTunes plug-in on macOS which is maintained by @revmischa .

[teotigraphix]

@kblaschke I was always interested in this and still with the Android app, but I could never get this to compile on my dev machine. :) Maybe if stuff gets moved around, I could try the Android app again, I have apps since 2016, so if I got it up, I could maintain it for the foreseeable future. I can't remember what was wrong with compiling(on my machine Windows 10) though.

[kblaschke]

With the new build system and C API it should get easier to build and integrate projectM. Android is always tricky, especially if you throw the NDK into the mix. I was able to build the projectM library using CMake, but didn't try the app itself. Not sure if it's compatible with the new IntelliJ-based Android Studio.