Returning to CsoundUnity and updating old project
here’s mine:
i’m on Unity 2022.3.14 but it looks like you have more options than me in Logcat.
also it appears that Debug.Log won’t actually print anything in Logcat or it’s highly inconsistent - there’s a huge thread i just scrolled through on it. i changed everything to Debug.LogWarning, so we’ll see if anything shows.
okay @giovannibedetti - a small modicum of progress but some important info to share:
- Debug.LogError did print the info but only on a BuildAndRun and not while just running the build. and the path is exactly what they stated in the UnityAPI
- Build and Run will ERASE the PersistentDataPath folder and replace it. and THIS is what was causing the crashes, because the SF2 files were erased as soon as i did Build And Run
- i used your script that copies from StreamingAssets but i had compilation errors because your version is the 4.0 version not 3.5 and it references a WAFU namespace that doesn’t exist for me, so i commented out the code that added audio files.
and now that it doesn’t crash when playing back SF2 files i get - nothing. no sound. Csound is definitely working as the playbar moves and that is driven by the Layer’s time division. i did try sfplay3 as well as sfinstr3 - both of these opcodes played the sound font in the editor just fine but the build is utterly silent on the Quest.
i can’t really get you good logs from Csound in logcat unless all Debug.Log messages are replaced by Debug.LogError - and even then this will likely only print during a Build and Run session.
if you had a Unity project for Quest Android using a sound font i could test that and see but as it looks right now it’s not seeming to work at all, no matter what opcode i use. i’m heading to bed now at this point. some progress but still discouraging.
This is Unity 2022.3.52f1:
If you connect a device you will see it listed under the drop down menu that now says “No device”.
If you start the app, you will see it under the drop down menu that now says “No filter”.
It should work if you start the app without using Build and Run too.
If you don’t like Android Logcat you can simply use adb to log Unity output (maybe add adb to your path so that it’s easier to use).
Simply use this command to log Unity output on your terminal:
adb logcat -s UnityI’m not sure this is true.
In my past experience it will create the folder if it doesn’t exist, but the next runs will keep the content of the folder.
Yes correct, but as you did you can safely comment the part related to audio files.
I’ll make some tests and upload a project that uses soundfonts today.
But you can simply import the SFDIR sample from the CsoundUnity package and build it for Android.
It was working 
I remember an issue with soundfonts some months ago though:
it should have been fixed in this commit:
it’s the Build part that wipes the files, not the Run part. and i can verify, as i did copy them over to the same path earlier via AFT.
i just looked at the samples and grabbed a couple that seemed cool and i don’t see any sample marked as SFDIR. if you could link that i’d appreciate it! especially if plays easily or autoplays.
i also remember that thread on sf2 files - but as i recall, the audio was weird and transposed i think? but it wasn’t about not hearing any audio at all, unless i’m misremembering. so i don’t think my issue is related.
Yes sorry, the sample related with sfonts is under Environment Vars.
Here is a project that runs on the Quest (just tried on a Quest 2)
I just imported the sample and built with IL2CPP on and for ARM64
https://drive.google.com/file/d/1Xtr9KnpX2hA_yuVscGtspE1gEk0S4dxF/view?usp=drive_link
Sometimes sfonts have different volume ranges, so I guess it’s worth trying other values for volumes, as if you don’t get any error it could simply be that the volume is too low
mille grazie G! i will test this in a few hours.
interesting though about the volume - i just figured if the volume is fine in the editor it should be fine in the build. i checked to make sure no sources were 3D. at any rate i just need to find if i’m going crazy or there really is an issue on Quest3.
1 Like
I just tried to Build and Run after duplicating one of the Sound Fonts in Windows. The folder doesn’t seem to be touched by the Build process
To be honest, I think that there is still an issue with pitches (it seems slightly higher than I would expect, like a tone higher).
This could be an issue with the sampling rate being different on the Android device (for example on my Pixel 4a Csound runs at 28000Hz)
But you can handle that rescaling the pitch in some way
well it is on my Mac. those files were there. i didn’t touch the folder and only did Build And Runs. once i finally got logcat to print ANYTHING from Unity i ran the ChatGPT script you sent, and that showed no files but the expected path as listed by Unity API. went back to check via AFT and they weren’t there. so somewhere along the line the folder got replaced. i haven’t been doing serial builds but i am replacing the previous build several times.
Uhm that is strange.
I will test on my Mac now
Edit:
Android File Transfer on the Mac is a nightmare
i’d say ‘very limited’ but it does work. but there is the matter of whether a different app accessing the quest maybe doesn’t play well with Unity?
Files are still there after build and run
Note: this is my phone
Btw on the Quest you should really use Meta Quest Developer Hub
https://developers.meta.com/horizon/documentation/unity/ts-odh/
Download it from here:
https://developers.meta.com/horizon/downloads/package/oculus-developer-hub-mac
yeah i have it. i find it a mixed bag in terms of needing it. obviously all official Meta builds i use it, but it’s more than once forgotten the Q3 and i have to manually register it. tends to sour my opinion of it.
1 Like
I just reinstalled it and apparently there’s no way to put files into an app folder 
So I guess it’s possible that the folder gets erased on build.
Then you will definitely need the script that copies the soundfonts there on start.
1 Like
…and which works great BTW, after my light editing.
