That sounds correct (or at least expected). The classroom installer doesn't really support running beta versions in a classroom situation, so it will only ever create a C:\ProgramData\Synthesia folder.
You can just copy that over to a C:\ProgramData\SynthesiaDev folder and it should work the same for beta versions.
10.5 preview r4792, r4801 - New Synth!
Archived development updates.
-
KaleidonKep99
- Posts: 54
- Location: Cagliari, Sardegna, Italy
There's a small issue with the new built-in synthesizer.
Since the BASS device is initialized on startup, and does not get freed when the built-in synthesizer is turned off, MIDI drivers such as my OmniMIDI and Claudio's VirtualMIDISynth 1.x won't work, and fail to initialize with a BASS_ERROR_INIT error.
It would be better for Synthesia to free BASS when not in use, and maybe free the DLLs with FreeLibrary too (To allow OmniMIDI/VMS to load their DLLs, if they're more up-to-date than Synthesia's).
I'm not forcing you to fix it, but it would be nicer to give more freedom to the user on the MIDI output device they want to use!
Since the BASS device is initialized on startup, and does not get freed when the built-in synthesizer is turned off, MIDI drivers such as my OmniMIDI and Claudio's VirtualMIDISynth 1.x won't work, and fail to initialize with a BASS_ERROR_INIT error.
It would be better for Synthesia to free BASS when not in use, and maybe free the DLLs with FreeLibrary too (To allow OmniMIDI/VMS to load their DLLs, if they're more up-to-date than Synthesia's).
I'm not forcing you to fix it, but it would be nicer to give more freedom to the user on the MIDI output device they want to use!
Hmm... I didn't realize BASS used a global, system-wide initialization. My guess would have been per-process. Sorry for the collision. It seemed like it should have been safe.
With any luck though, Synthesia's BASS should be using the DLLs in the Synthesia directory, so anything used by other drivers shouldn't be locked. Although, upon closer inspection on that page, the "If a DLL with the same module name is already loaded in memory, the system checks only for redirection and a manifest before resolving to the loaded DLL..." is a little worrisome.
I wonder if throwing a LOAD_LIBRARY_SEARCH_APPLICATION_DIR in there also avoids that behavior, too.
EDIT: Ah ha! It's because WASAPI is exclusive. I suppose that means everybody on the system has to play nice together or step on each other's toes.
For what it's worth, Synthesia does call BASS_Free when you close the synth. The only thing it's not doing is releasing the DLL. (It does dynamic binding and I was hoping to avoid all the pointer lookups each time. But I suppose it's not that large a price to pay.)
EDIT 2: It looks like just putting a "Synthesia.exe.local" file (contents doesn't matter; can be empty) in the same folder with Synthesia.exe will force it to use DLLs in that same folder. (The same is presumably true for your synth, too.)
With any luck though, Synthesia's BASS should be using the DLLs in the Synthesia directory, so anything used by other drivers shouldn't be locked. Although, upon closer inspection on that page, the "If a DLL with the same module name is already loaded in memory, the system checks only for redirection and a manifest before resolving to the loaded DLL..." is a little worrisome.
I wonder if throwing a LOAD_LIBRARY_SEARCH_APPLICATION_DIR in there also avoids that behavior, too.EDIT: Ah ha! It's because WASAPI is exclusive. I suppose that means everybody on the system has to play nice together or step on each other's toes.
For what it's worth, Synthesia does call BASS_Free when you close the synth. The only thing it's not doing is releasing the DLL. (It does dynamic binding and I was hoping to avoid all the pointer lookups each time. But I suppose it's not that large a price to pay.)
EDIT 2: It looks like just putting a "Synthesia.exe.local" file (contents doesn't matter; can be empty) in the same folder with Synthesia.exe will force it to use DLLs in that same folder. (The same is presumably true for your synth, too.)
-
KaleidonKep99
- Posts: 54
- Location: Cagliari, Sardegna, Italy
I think BASS checks if there's another version of itself loaded into memory, and if it is, it just returns false in DllMain, forcing LoadLibrary to pass a pointer to the existing library. And I don't think that DLL redirection will help at all...
BASS does use per-process initialization, but the *_Init functions can only be called once per app.
I'll make OmniMIDI free the libraries when midiOutClose is called, to allow Synthesia to use its own DLLs when my synth is closed. (In case you want to implement the load-'n-free libraries thing I suggested!)
BASS does use per-process initialization, but the *_Init functions can only be called once per app.
I'll make OmniMIDI free the libraries when midiOutClose is called, to allow Synthesia to use its own DLLs when my synth is closed. (In case you want to implement the load-'n-free libraries thing I suggested!)
-
ibruethsch
- Posts: 4
Hello
I tried version 10.5.4801 on my android (S5 Android 6.01).
To make Synthesia to use my own soundfont .sf2 is easy.
Using a good Soundfont .sf2, the sound is muuuch better then 10.4
The latency is still a problem. I feel uncomfortable with it.
Whereas with SAMSUNG Soundcamp (and IGrand) the latency on the same device is very good.
So – I will still use my workaround: learning with synthesia on one device and listen the sound on the second device (my midikeyboard send signals to both devices at same time)
Best regards
Bernd
I tried version 10.5.4801 on my android (S5 Android 6.01).
To make Synthesia to use my own soundfont .sf2 is easy.
Using a good Soundfont .sf2, the sound is muuuch better then 10.4
The latency is still a problem. I feel uncomfortable with it.
Whereas with SAMSUNG Soundcamp (and IGrand) the latency on the same device is very good.
So – I will still use my workaround: learning with synthesia on one device and listen the sound on the second device (my midikeyboard send signals to both devices at same time)
Best regards
Bernd
Yeah, when I tested it, Android latency (even on newer devices) is still kind of all over the place. Samsung's own page on Soundcamp mentions "proprietary professional audio technology" for achieving lower latency. They do allow other apps to integrate with their Pro Audio SDK, but it's not clear the effort is worth it for the five or six Samsung-only devices it benefits.
-
KaleidonKep99
- Posts: 54
- Location: Cagliari, Sardegna, Italy
The API will also be deprecated on January 1st, 2019. So yea, it's not even worth trying!
-
ibruethsch
- Posts: 4
@Nicholas
Thanks that you consider that.
>> Android latency (even on newer devices) is still (a problem)..<<
That was one question I had in minde, but didn’t tell. My old S5 still works fine, so - no reason to upgrade.
@Kaleidon
I’m not sure if “deprecate” is the right word. The app will no longer be maintained from Samsung. And it is announced that it will not run on android pie (= android 9). And it will be removed from Google Play. But it still work. And you can download it from e.g. apkpure.
>> So yea, it's not worth trying! (to integrate Synthesia in Soundcamp)<< - yes I double that.
kind regards
Bernd
Thanks that you consider that.
>> Android latency (even on newer devices) is still (a problem)..<<
That was one question I had in minde, but didn’t tell. My old S5 still works fine, so - no reason to upgrade.
@Kaleidon
I’m not sure if “deprecate” is the right word. The app will no longer be maintained from Samsung. And it is announced that it will not run on android pie (= android 9). And it will be removed from Google Play. But it still work. And you can download it from e.g. apkpure.
>> So yea, it's not worth trying! (to integrate Synthesia in Soundcamp)<< - yes I double that.
kind regards
Bernd
If I understand what you want correctly, I think you can do that by choosing different pianos for each hand and then setting the volume for each piano as you wish. Some of the pianos have very similar sounds and it takes a good ear to hear that they are different.