Main menu
You are here
Qsynth 0.3.5 - Spring Cleaning Pt.2
Ashes to ashes, dust to dust, funk to funky. Yawn. Cut the non-sense, there's no burial service nor Bowie's song here. Just blowing some aging stuff, maybe giving the patine that it deserves ;) Almost one long year has gone by and sadly enough, there's no big new and flashy features to show off. But, nevertheless,
Qsynth 0.3.5 is out from the closet!
Hope you enjoy the (not so big) news :) Have fun.
Description:
Qsynth is a FluidSynth GUI front-end application written in C++ around the Qt4 toolkit using Qt Designer. FluidSynth is an excellent command line software synthesizer based on the Soundfont specification.
Website:
Project page:
Downloads:
- source tarball:
qsynth-0.3.5.tar.gz - source package (openSUSE 11.2):
qsynth-0.3.5-2.rncbc.suse112.src.rpm - binary packages (openSUSE 11.2):
qsynth-0.3.5-2.rncbc.suse112.i586.rpm
qsynth-0.3.5-2.rncbc.suse112.x86_64.rpm - binary packages (Ubuntu 9.10):
qsynth_0.3.5-2.rncbc.ubuntu910_i386.deb
qsynth_0.3.5-2.rncbc.ubuntu910_amd64.deb
Change-log:
- Initial widget geometry and visibility persistence logic has been slightly revised as much to avoid crash failures due to wrong main widget hidden state.
- General source tree layout and build configuration change.
- Most modal message dialog boxes (eg. critical errors) are now replaced by system tray icon bubble messages where available.
- Reverb and Chorus parameter ranges have been revised to match and comply with fluidsynth back-end (libfluidsynth).
- Fluidsynth channel info and unset program interfaces are now in use where available (libfluidsynth >= 1.1.1, EXPERIMENTAL).
- Global configuration state is now explicitly saved/committed to disk when Options dialog changes are accepted and applied.
- Output peak level meters get their long deserved gradient look.
- Automatic crash-dump reports, debugger stack-traces (gdb), back-traces, whatever, are being introduced as a brand new configure option (--enable-stacktrace) and default enabled on debug build targets (--enable-debug).
- Added Czech (cs) translation, contributed by Pavel Fric.
- The channel preset selector (Channels/Edit...) has been seriously crippled for ages, only showing the presets of the last loaded soundfont, now fixed.
- Minimum number of MIDI channels allowed on engine setup has been dropped from the old value 16 to as low as 1 (one), not that it makes a difference, as (lib)fluidsynth internals just rounds it to the nearest multiple of 16 anyway.
- Cleanup to knobs source, simplified from redundant stuff.
Weblog (upstream support, yours truly):
License:
Qsynth is free, open-source software, distributed under the terms of the GNU General Public License (GPL) version 2 or later.
Cheers && Enjoy.
Comments
sad, very sad
Another feature included in the tarball but not mentioned in the changelog is a new CMake based build system, that can be used in Linux, Windows and Mac OSX instead of autotools. Why wasn't mentioned?
And BTW... Either you don't read the email, or you are extremely unfriendly.
sorry, very sorry
I may have missed your email Pedro, that's true and I am very sorry that you take offense from that.
I have no excuses either and to speak frankly I actually thought the change-log included some reference to that new CMake build system alternative. I mean, I didn't really check it either, due to my own sloppy incompetence. I always assumed you had done all things right, how can you find that unfriendly? :)
Anyhow, the change-log it's pasted from the ChangeLog file that is found in the source tree--I may have missed to include a reference to yours CMake build novelty but the fact is that you could have done it yourself. Aha, you missed it too (after all you have commit privileges to the tree haven't you? ;)
Please, forgive me. All my apologies are now public, right? Hope you understand and stay friends again.
Cheers
p.s. and yes, my email provider is intermittently blacklisted as a spam source and that might be the only and lousy excuse i can give away. sorry again.
No need to apologize
Just fix your mail
QSynth does not play midi files
Hello Rui Nuno Capela!
In Ubuntu 9.10 I used to export midi files from Rosegarden, then play them with QSynth, work them with Audacity and save them in .wav and .mp3 format. You can listen the results on http://www.concerto-news.nl/inbewerking.html
But now in Ubuntu 10.04, when I want to play a midi file with QSynth (right-click on the file, open with qsynth), nothing happens. No error message, QSynth does not even start up.
Rosegarden plays very beautiful with QSynth, but then I cannot record the sound with Audacity.
When I import a midi file in Rosegarden and try to play the file, then I see QSynth work (a flashing green drop in the the system tray), but I hear no sound.
Can you help me? I was so glad to discover QSynth..
Greetings, Wim
Re: QSynth does not play midi files
Please, give some more details about your new system. In particular which version of libfluidsynth and qsynth packages or whether you're building from source. Are you sure you have a proper soundfont file loaded in Qsynth?
Cheers
Re: QSynth does not play midi files
Hello!
My computer has a Tyan Tiger K8W mainboard, two Opteron 250 processors an 4 GB RAM.
Operating system Ubuntu 10.04, kernel 2.6.32-22-generic (#33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010).
libfluidsynth1 1.1.1-2build1
qsynth 0.3.4-1
I do not know how to build a package from source, I use the packages as Ubuntu provides them.
The soundfont is fine: Stefans Cathedral Pipe Organ from http://www.hammersound.com/cgi-bin/soundlink.pl?action=view_category&cat...
When I use Rosegarden with QSynth, everything works great and I can export midi files, but I can not save the sound as a .wav or .mp3 file.
So I want QSynth to play the midi files without using Rosegarden, record the sound with Audacity and then I can save them.
Greetings, Wim
Re: QSynth does not play midi files
Well, there actually seem to be a problem with libfluidsynth 1.1.1 re. playing MIDI files after all. Somehow it shutdowns the audio engine (eg. JACK) when it starts playing a MIDI file, like after you drag-and-drop one over the main Qsynth window.
However, there's this way for you to render audio from a MIDI file playback: you setup the audio driver to file and enter a filename (.wav) into the audio device name. From that moment all audio output will be written to that file instead of sent to soundcard/speakers/whatever it was before. Drag and drop the MIDI file for immediate playback and just wait (in silence) for the duration of the whole sequence. Then you can change back the audio driver to its previous setting. After all that you can open the resulting wav file into audacity and prepare for some editing or some listening and trimming of course.
HTH
Re: QSynth does not play midi files
Hello!
Thanks, it works.
One problem: when I drop de MIDI file on Qsynth, the sound begins with a sort of vibrato. I can stop that by moving the speed- or the depth- knob, but at the same moment the beginning of my .wav file is damaged. Do you have a workaround for that too?
My standard settings to get a beautiful cathedral sound are:
00:55:56.643 Qsynth1: fluid_synth_set_reverb(0.7,0.1,0.7,0.7)
00:55:56.643 Qsynth1: fluid_synth_set_chorus(10,1,0.3,0,0)
And maybe another problem in the messages:
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
I guess it is also a Fluidsynth failure and you can not help it?
Greetings, Wim
ulimits?
Hi Wim, as for the second prob, I might be wrong but first I would check "ulimit -r" and "ulimit -l".
xruns with Qsynth
Hi
I noticed Qsynth was causing xruns in Ubuntu Lucid. The problem seems to appear only when I click on the "setup" button (6 to 8 sudden xruns).
I tried with various kernel (rt, lowlatency...) with the same effects.
I also have to say that this happens at almost all latencies. Besides, I am using zynaddsubfx without any xruns at 64 period (4,35 ms).
Any idea how to solve this?
Many thanks !!
Re: xruns with Qsynth
Which libfluidsynth version?
Seems like an issue from latest 1.1.1, due to recent threading changes it's probably locking the whole internal synth process while reading engine settings. But not sure... better ask on the fluid-devel list?
I'm not seeing these xruns on my side, at least when pressing the "Setup". However, I am sure that (re)starting any engine with new settings, will indeed cause a burst of xruns no matter what. This is in fact a side-effect behavior and it only got worst with libfluidsynth >= 1.1.x. I'm afraid there's not much to do on the Qsynth camp. Fact is, depending on your system and what not, it is very probable for that to occur on all fluidsynth versions, just more aggressive now.
Byee
hi you were right! it was a
hi
you were right! it was a libfluid problem; I change over to a previous one and it solved everything. Not a single xrun anymore and high performance! Rock'n'roll !
Thanks again and keep going!
Qsynth 0.3.5 -
Great post!Please keep up the good work. Appreicate you efforts for sharing.
Add new comment