Hi, list. Anyone familiar with WhySynth issues and perhaps OSC? When I run Whysynth it starts fine and the GUI starts. Sound works, but the GUI doesn't open. I have read this issue is caused by the computer's name not resolving, but mine does resolve, so something else is causing this. I turned off iptables to see if it was a firewall issue and that didn't help much. Since the DSSI and GUI run and sound works, but the GUI doesn't show, I am thinking it still may be an issue with a port or some other OSC issue. I am not so familiar with trouble-shooting OSC. Anyone got any pointers on trouble-shooting it. What utilities are there? Could it be some other trouble? Thanks, Sean

On 05/14/2013 02:18 AM, Sean Beeson wrote: > It was suggested to me to try and use 0.0.0.0 localhost in my /etc/hosts > file, bu that's not doing anything. > > With netstat I'm seeing that both jack-dssi-host and WhySynth_gtk are > opening ports, but the GUI still doesn't open up. > > What I'm seeing is this: > > [sean@localhost ~]$ jack-dssi-host whysynth.so > > jack-dssi-host: Warning: DSSI path not set > jack-dssi-host: Defaulting to > "/usr/local/lib64/dssi:/usr/**lib64/dssi:/usr/local/lib/** > dssi:/usr/lib/dssi:/home/sean/**.dssi" > > > jack-dssi-host: OSC URL is: > osc.udp://localhost:19884/**dssi/whysynth/WhySynth/chan00 > > host: Ready > WhySynth_gtk starting (pid 22764)... > > ---- > and this from netstat.... > > udp 0 0 *:19884 *:* > 22757/jack-dssi-hos > udp 0 0 *:19885 *:* > 22764/WhySynth_gtk > I am not having this problem. Perhaps start jack-dssi-host -v for further clues. What version of whysynth are you using? whysynth-dssi-20120729-1.fc18.**x86_64 ______________________________**_________________ music mailing list music(a)lists.fedoraproject.org https://admin.fedoraproject.**org/mailman/listinfo/music<https://admin...

Hi: On 05/14/2013 12:01 PM, Sean Beeson wrote: > Brendan, > > Thanks for the reply. > > I have the same version installed-- whysynth-dssi.i686 20120729-1.fc18 > @fedora. > > It's really looking like a network/name/port resolution issue then. > Since I'm not getting any Selinux messages, I can probably eliminate > that as well. Sometimes, SELinux will prevent something, but not report it. It's worth switching to "permissive" mode for a trial run, just to be sure. If it works with SELinux in permissive mode, I'll point you to the documentation you can use to figure things out... but docs.fedoraproject.org isn't working at the moment... > Do you know of any other simple and quick programs for me to test OSC > with, BTW? It's not simple, but everybody should always have SuperCollider and PureData installed at all times, just in case. Christopher _______________________________________________ music mailing list music(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/music

On 05/15/2013 01:46 AM, Sean Beeson wrote: > Christopher, Thanks for the input. > > I went to permissive, which I'll run in to lighten my computer's load > anyway. Unfortunately, that didn't clear up the issue. You mean, to reduce processor use? Do you notice any effect? I wouldn't expect it would make a difference.

If you run in verbose mode you should see a successful OSC update request. If you do and still no GUI, it maybe something else. jack-dssi-host -v whysynth.so <snip> WhySynth_gtk starting (pid 4176)... jack-dssi-host: OSC: got update request from <osc.udp://fedora18:14218/** dssi/whysynth/WhySynth/chan00>

On 05/15/2013 01:46 AM, Sean Beeson wrote: > Christopher, Thanks for the input. > > I went to permissive, which I'll run in to lighten my computer's load > anyway. Unfortunately, that didn't clear up the issue. You mean, to reduce processor use? Do you notice any effect? I wouldn't expect it would make a difference. Christopher