2015/10/24 14:43:44
Amicus717
Hi folks,
 
I upgraded my install of Cakewalk Platinum to Jamaica Plain, and since that time, the Fantom Synth no longer works. I can load it up, and open the synth in Sonar Platinum, load a patch, etc, but when I try to play, the Fantom is totally silent. I've already installed the registry hack that allowed it to work under Windows 8/10, and it was working just fine prior to the new patch. But since then, not a peep out of it.
 
Anyone else experience this?
 
Amicus
2015/10/24 15:08:18
Doktor Avalanche
Is it receiving midi? Can you generate a sound from it without using a controller?

Are there any updates for this softsynth you can install? Is it 64 bit or 32 bit?
2015/10/24 15:49:21
Amicus717
Its the synth built into the VS700 -- so its 32 bit, updated to the latest drivers and firmware, and it is receiving midi. The synth has a built in software gui keyboard you can use with the mouse, and that keyboard responds when I use my hardware keyboard, echoing what I play - I play middle c on my hardware keyboard, the middle c on the synth's gui keyboard plays also. So the Fantom is clearly seeing what I'm playing on my M-Audio keyboard. But the synth makes no sound.
2015/10/24 23:59:53
Amicus717
Thanks for the links. Unfortunately, they did not help.
 
Have any other VS700 owners updated to Jamaica Plain? Any issue with the Fantom synth? The synth was working fine last week, and aside from the monthly update, nothing has changed in my setup. So, I'm really not sure what else it could be...
 
Update: I took another look at the Cakewalk forum posting linked above, and tried the suggestions again. This time, I did get audio from the Synth. I first loaded the Fantom into a new project (as a simple instrument track). The synth seemed to load and it was getting midi input, but it was silent. So I inserted an additional audio track, as per the forum posting, selected Stereo VS-700 Fantom VS as the input for the audio track, turned on input echo -- and suddenly I could hear the Fantom synth. I've never had to do that before. Previously, I would just load the Fantom synth as a simple instrument track like any of my other synths, and it would work fine. That no longer is the case. I'm wondering why...
2015/10/25 16:25:40
Doktor Avalanche
So it's was just a matter of the echo button not being on?

I suspect you previously had it set in sonar preferences to turn this on automatically when track is in focus. Check the settings there.

Or....maybe...there was direct monitoring set up in V700 if it is available. Your interface is outside the scope of my knowledge here. Check manual or maybe others will advise.

Personally I prefer to manually turn on echo button myself in Sonar and I don't bother with direct monitoring via audio interface any more.
2015/10/30 08:02:04
Rob[at]Sound-Rehab
Amicus717
Hi folks,
 
I upgraded my install of Cakewalk Platinum to Jamaica Plain, and since that time, the Fantom Synth no longer works. I can load it up, and open the synth in Sonar Platinum, load a patch, etc, but when I try to play, the Fantom is totally silent. I've already installed the registry hack that allowed it to work under Windows 8/10, and it was working just fine prior to the new patch. But since then, not a peep out of it.
 
Anyone else experience this?
 
Amicus




I just checked on this ...
 
Fantom - if used with several MIDI tracks plus one audio track that receives the hardware synths output - works as usual ...
 
Fantom - if used as instrument track (which I normally don't do) does no longer work - it remains silent because if you split the instrument track to MIDI plus audio track, you see that it now creates a patch point called something like fantom and routes to that but does not route to/from the actual Fantom I/O (which would be FANTOM MIDI OUT and VS-700 FANTOM audio IN) ... hence it is silent (i.e. routing MIDI to nirvana) ...
 
That's certainly something to be aware of, especially if you generally use instrument tracks (which I rarely do, never on multi-IN or multi-OUT) ... me, personally, it does not bother as it works the other way and the patch point functionality is worth so much more than this (in my case rarely used) legacy synth ...
 
 
 
 
2015/10/30 23:22:51
Amicus717
Thanks! And, yeah I've got it working as you mentioned above. Took me a little bit to figure all that out. I'm running a VStudio 700, and in this era of constant software updates and patches, the Vstudio's aging, unsupported drivers make me nervous. I tend to assume the worst when a new patch comes out and something that worked before the patch, no longer works immediately after applying the patch.
2015/11/07 18:47:28
e.Blue
Amicus717
Thanks! And, yeah I've got it working as you mentioned above. Took me a little bit to figure all that out. I'm running a VStudio 700, and in this era of constant software updates and patches, the Vstudio's aging, unsupported drivers make me nervous. I tend to assume the worst when a new patch comes out and something that worked before the patch, no longer works immediately after applying the patch.




Actually, in this case you were correct to assume the worst. Under Jamaica Plain, the Fantom VS no longer works like it was originally designed to. Routing MIDI to the 'FANTOM (VS-700)' (hardware) output (and turning Echo on) instead sending it to the 'Fantom VS 1' synth output was actually a work-around that you could use instead of applying the registry fix.
 
One of the problems with this work-around is that you can't audition MIDI files from the Media browser through the Fantom hardware output, only through the now broken 'Fantom VS 1' synth output.
 
So basically it appears that whatever the registry fix used to 'fix' is no longer being fixed.
2015/11/08 11:21:47
Rob[at]Sound-Rehab
e.Blue
 
Actually, in this case you were correct to assume the worst. Under Jamaica Plain, the Fantom VS no longer works like it was originally designed to. Routing MIDI to the 'FANTOM (VS-700)' (hardware) output (and turning Echo on) instead sending it to the 'Fantom VS 1' synth output was actually a work-around that you could use instead of applying the registry fix.
 
One of the problems with this work-around is that you can't audition MIDI files from the Media browser through the Fantom hardware output, only through the now broken 'Fantom VS 1' synth output.
 
So basically it appears that whatever the registry fix used to 'fix' is no longer being fixed.




I'm afraid we will see more of that in the (near?) future as the VS700 is officially legacy and no one will ever care about it anymore.
 
What I'm really afraid, though, is once Cake starts changing CV layout and introduces e.g. some auto-hide features of certain channels (e.g. showing only tracks that feed into a certain bus or aux channel), most of the VS-700 channel strip control will leave us (because it is already broken when it comes to hidden strips).
 
So eventually each of us will have to decide what to turn off: Sonar upgrades or VS-700 ???
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account