GeekJosh
Currently not working with new update
Unfortunately, I no longer have a PC based VR headset so I'm unable to update the app to work with the new version of BoxVR
No worries, I had a look at the code myself but apparently 4 years of c# and a year of python at university level was not enough to use in a real world project. I just wouldn't know where to start to make sense of yours haha
I have looked into this further and have found that your program only gets as far as making .mom files and only when the game is opened, they have a new way of generating tracking whereby they now have a .track file which contains jsonified objects which lists beats and intensity of the beats along with a few other properties. Seems like this is using a built in program or some such. I was just wondering if you could provide any insight despite not working on it any more or if you can advise how I can look into their software better to see what is being used during song creation.
Sorry to be a pain I was just curious as I would like to make this possible with the latest update if I can and if you'd allowed it but that's only if I get that far
Since none seems to be able to work on this go make your voice heard here: https://steamcommunity.com/app/641960/discussions/3/1640915206495257644/
Exact error is :
spectrogram.py:1074: RuntimeWarning: invalid value encountered in maximum
But it's just a warning and the madmom.txt seems to be created correctly. Here's an exemple output file
0.150 1 0.500 2 0.840 3 1.190 4 1.530 1 1.880 2 2.220 3 etc
So basically "time _beatInBar "
I'm trying to figure out where it goes wrong. Or more exactly does it even go wrong ? Was that kind of output enough in the past boxVR version ?
Nowadays for each playlist there is a : 1/ a trackdefinition per song (.wdef.txt) containing stuff such as duration, bpm, tags, trackid, etc 2/ a TrackData per song (.trackdata.txt) containing wich contains the actual notecharts. The "1,2,3,4" produced by madmom seem to correspond to the _beatInBar values in the new format. but what about everything else ? _avgEnergy ? _segments ? etc. Are those new information ? 3/ a .workoutplaylist.txt containing ids of each song, author name, etc
Created a pull request https://github.com/GeekJosh/BoxVR-Playlist-Manager/pull/6 which works with the latest Box VR version as of today. I haven't rigorously tested it, however I have created a few playlists and they seem to be working just fine. Deleting/renaming/moving songs around also seems to be working as expected. I did have to remove some of the features that were there initially, as I haven't had time to implement them yet. I may add them to my branch at some point.
