Re: [Rosegarden-user] Entering values for LADSPA plugins directly
On Saturday, August 25, 2012, Holger Marzen wrote: I cannot set the values directly. Setting them with the mouse (turning the knob) works but is way too coarse. Entering the value in the input field or using up and down arrows always leads to the minimum value of 0.25. Same thing here with the latest development build. You're not crazy. Using the AM pitch shifter thing as a test bed, the knob that moves in integer increments seems to be working just fine. The knob that lets you set a floating point value has big problems. The display appears to be limited to two decimal places of precision, but the arrow buttons obviously let you make changes in finer increments than that. The result is that you have to click repeatedly in order to see a visible change. Once you've made the change, either by using the arrow buttons or by typing a value directly, that change gets corrupted somewhere along the way. Try to change to 1.03 and the result is the knob gets set to some fantastically wrong number like 1e-10. That kind of wildly nonsensical number is usually an uninitialized variable, but it seems like there could definitely be type conversion and/or precision issues mixed up in here too. I'm weak on floating point math, so this might be a common pattern I don't even recognize. I spent some time poking around, and only started to get the idea of how all of these many intricate little puzzle pieces fit together. This would just take more time than I have to sort through and work out, but it's probably a really simple and obvious problem. -- D. Michael McIntyre -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
Re: [Rosegarden-user] Please help: no sound 11.11.42-51.17 earlier [suse 12.x kDE]
On Sun, 26 Aug 2012, k...@trixtar.org wrote: OpenSuse-12.1 or 12.2 KDE4 Some soundfonts fluidsynth are installed This works, I can hear the midi: fluidsynth -a alsa -l /0/sa14/comp/build-common/music/sf2-filez/Unison.sf2 /0/sa14/guitar/midi/mmp.mid At least you have some MIDI sound. The problem is that command tells Fluidsynth to use Alsa audio, which locks Alsa audio in exclusive mode, and Jackd (Qjackctl) can't access the Alsa audio for audio output. Here's my Fluidsynth command: fluidsynth -a jack -j -r 44100 -g 0.40 -o synth.midi-bank-select=xg /full-path-to/soundfonts/Unison.sf2 you can skip the -o synth.midi-bank-select=xg, if you don't care about Yamaha XG midi stuff. Note the -a jack tells Fluidsynth to use Jackd audio output instead of Alsa audio. So you need to have jackd already running, or if you use Qjackctl you need to have jackd started within Qjackctl. After I have qjackctl started jackd, I can get the full command by looking at the output of: ps -ef | grep jackd | grep -v grep and that command starts from the /usr/bin/jackd, until the end of that output text line. Once you get all the parameters selected as you want in qjackctl, the command to start jackd may be helpful if you want to use the commandline instead of qjackctl. Anyway, once you have both qjackctl and fluidsynth started, click on Connect button of qjackctl. Within the qjackctl connection window, The Audio tab is the jackd audio (not Alsa audio) connections. The MIDI tab is for jack MIDI connections. The ALSA tab is for Alsa MIDI connections. Select Audio tab, make sure fluidsynth is connected to system. Select ALSA tab, select 14:Midi through on the left list (output ports), select Fluid synth on the right list (input ports), click on Connect button within that qjackctl connection window. This is the If you don't see 14:Midi through, you may need to load some kernel modules into memory with the modprobe command. Here are my midi kernal modules loaded: lsmod | grep -i midi snd_seq_midi3592 0 snd_rawmidi12701 1 snd_seq_midi snd_seq_midi_event 3620 2 snd_seq_oss,snd_seq_midi snd_seq35462 11 snd_seq_midi_event,snd_seq_oss,snd_seq_dummy,snd_seq_midi snd_seq_device 3969 5 snd_seq,snd_rawmidi,snd_seq_oss,snd_seq_dummy,snd_seq_midi I don't remember which one is the one that shows up as 14:Midi through, I believe it is snd_seq_midi, but I could be wrong. The Audio tab selection above is automatically connected by the -j option of the fluidsynth command. If you use fluidsynth without the -j option, you will need to manually connect it to the jack audio output to hear any sound using jackd. The ALSA tab selection above is connect the virtual midi-through port to the fluidsynth Alsa MIDI input port. Now you can test play a midi file with: aplaymidi -p 14 /full-path-to/some-midifile.mid the -p 14 option of aplaymidi tells it to send Alsa MIDI output to port 14, which is the same as the virtual midi-through port shown in qjackctl connection window under ALSA tab. Again, the order of apps that need to get started are: jackd (manually, or via qjackctl) fluidsynth using jack audio output, not Alsa audio output (manually, or via qsynth), make sure to specify a GM soundfont file within fluidsynt, or qsynth. connect both jack audio, and alsa MIDI connections. play a sample midi file with aplaymidi. Once you get all tha working, you should have at least a vague idea of the difference between jack audio vs Alsa audio, as well as some idea about Alsa MIDI connection. Now you can try to start Rosegarden, then try to connect the first rosegarden Alsa MIDI output port to FLUID synth directly, or connect rosegarfen Alsa MIDI output port to 14:Midi through, and 14:Midi through to FLUID synth. PluseAudio is so hard wired into KDE that I cannot uninstall it While trying to find my way in the ncurses also mixer sliders I lost all sound and had to recover the entire partition from a backup. I don't use PulseAudio at all, so I don't know for sure if it can cause problem, but I have heard plenty, so I stay away from it. If I try Qjackctl with server path: pasuspender --jackd on launch it gives 21:53:56.441 Patchbay deactivated. 21:53:56.443 Statistics reset. 21:53:56.444 ALSA connection change. 21:53:56.448 ALSA connection graph change. when I click Start it continues with 21:56:02.022 JACK is starting... 21:56:02.022 /usr/bin/pasuspender --jackd -v -dalsa -dhw:0 -r48000 -p1024 -n2 -H 21:56:02.025 JACK was started with PID=5731. 21:56:02.027 JACK was stopped with exit status=1. 21:56:04.065 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info. The problem may be that PulseAudio is already stared and grab a
Re: [Rosegarden-user] Entering values for LADSPA plugins directly
On Sun, 26 Aug 2012, D. Michael McIntyre wrote: On Saturday, August 25, 2012, Holger Marzen wrote: I cannot set the values directly. Setting them with the mouse (turning the knob) works but is way too coarse. Entering the value in the input field or using up and down arrows always leads to the minimum value of 0.25. Same thing here with the latest development build. You're not crazy. Using the AM pitch shifter thing as a test bed, the knob that moves in integer increments seems to be working just fine. The knob that lets you set a floating point value has big problems. The display appears to be limited to two decimal places of precision, but the arrow buttons obviously let you make changes in finer increments than that. The result is that you have to click repeatedly in order to see a visible change. That's not for every plugin a big problem. I noticed that the phaser gets finer LFO-changes than those displayed. So if I klick the arrow 2 times then the 2-decimal-value doesn't change but the LFO-frequency changes. Back to the AM pitch shifter: Changing the values with an editor in the .rg-file works. Not really user-friendly but it's a workaround. Frank Zappa's advice in The Slime is That's right, folks, don't touch that dial! Once you've made the change, either by using the arrow buttons or by typing a value directly, that change gets corrupted somewhere along the way. Try to change to 1.03 and the result is the knob gets set to some fantastically wrong number like 1e-10. That kind of wildly nonsensical number is usually an uninitialized variable, but it seems like there could definitely be type conversion and/or precision issues mixed up in here too. I'm weak on floating point math, so this might be a common pattern I don't even recognize. My stomach says that it's a casting problem. Unfortunately my Ubuntu 11.10 has not the needed library- and header versions, so I can't compile RG here and try to find the bug My holidays before christmas should give me the time zo update my Ubuntu to 12.04 LTS. Best Regards Holger -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
