Save the file.4. Apply the patch by command:patch -p1 < patch.patch5. cd into linux folder within the source code folder and give the command:ln -s ../solaris/oss6. Return to the previous directory. And compile jackd2 USING GCC4 by the following commands:./waf configure --portaudio --dbus --classic --alsa./waf buildsu -c './waf install'7. Now the command:ls /usr/lib64/jack/should print the file jack_oss.soIf the name of that file is not printed, manually copy this precious file into the needed folder:su -c 'cp build/linux/jack_oss.so /usr/lib64/jack/'

8. Now you can try to run jackd2 with oss support. Close all audio programs running. Activate vmix in ossxmix. Deactivate src and ratelock. Issue:/usr/local/bin/jackd -S -v -doss -r48000 -C/dev/dsp -P/dev/dsp -p1024 -n2 -w16 (Don't try to run jackd2 with -w32 when vmix is enabled - you will get terrible hissing sound from the left speaker which can burn your tweeter!!!)

Set master volume in ossxmix to the low level. Start carla and load some soundfont. Press the wrench button in carla to see virtual keyboard. Press the keys on virtual keyboard. You will get sounds which confirms that jackd2 now works with oss.

You may try to run jackd2 with vmix disabled. Enable ratelock in this case in ossxmix. Set sampling rate to that of jackd2 in ossxmix (for juli@ soundcard). Close carla if it's running. Issue:

/usr/local/bin/jackd -S -v -doss -r48000 -P/dev/dsp -p512 -n3 -w32

Check if you have sound via carla the same way.

If you have any strange artifacts like slowering or speeding of playback with vmix disabled you may try to activate hw resampling on juli@ by checking src box.

Enjoy!

Our motto is EXPAND THE POTENTIAL EXPONENTIALLY!

Last edited by ossuserr on Sat Jan 09, 2016 10:33 pm, edited 1 time in total.

The benefit of jackd1 over jackd2 is that you do not have to run a2jmidid -e to get midi input visible in patchage. And benefit II is that jackd1 with oss is bugless while with jackd2 you can get a terrible hissing noise with at least one setting.Now i am running jackd2 with oss with the command: /usr/local/bin/jackd -S -v -doss -r48000 -P/dev/dsp -e -p512 -n3 -w32Pay attention to -e option. I guess it activates exclusive mode like that of ossplay -R.

I have got to know that by design jackd2 can't have -X before -d. But -doss does not have -X option at all and jackd2 will refuse to start. So you can't activate alsa-sequencer for jackd2 by the command starting jackd2. You can only have midi input support via a2jmidid -e. To make it clear once and forever.

Such noise can be produced by OSS4 resamplers at downsampling(e.g. 192kHz → 48kHz, or 96kHz → 48kHz). It depends on audio files.See also: _https://wiki.archlinux.org/index.php/Open_Sound_System#Changing_the_Sample_Rate

This looks like more a bug of jackd2. Moreover 44100 or 48000 samples of kontakt in carla were tested. Also the bug demonstrates itself only with -w32 and only left speaker is producing the sound as if the signal became mono.

Better turn off vmix and use -w32. Jackd's internal format is 32float for cards that support 32-bit. I could not get 32bit mode with emu10k1 which is 16bit. But linuxmusicians recommended to use 32bit mode to have less clipping at peaks

After upgrading operating system to some new packages and reverting back i can no longer use jackd2 for unknown reason. Perhaps something got broken.For those who experience the same problem, i give the way to return to jackd1.You should install version =jack-audio-connection-kit-0.121.3-r2 on gen2 because only this version has dbus and dbus can be needed for many things.1. Switch gcc to 4.x.y version.2. Go to folder jack-1.9.10/ from which u installed jackd2 and issue:su -c './waf uninstall'3. emerge -av =jack-audio-connection-kit-0.121.3-r24. If u have juli@ card, close ossxmix, switch off vmix in osscore, restart oss, launch ossxmix and switch off vmiz in ossxmix. Set sampling rate to 44100 and check ON ratelock and SRC in ossxmix.5. Start jackd by: jackd -Xalsa_midi -P80 -t1000 -m -v -doss -r44100 -C/dev/null -P/dev/dsp -i0 -o2 -p512 -n2 -w32If you don't have alsa modules installed and u have not edited ulimit for realtime support use the command and if you card does not support 32bit mode:jackd -t1000 -m -v -doss -r44100 -C/dev/null -P/dev/dsp -i0 -o2 -p1024 -n2 -w16

6. If jackd does not start and segmentation fault is reported, try to unmerge, then change GCC version to something like 4.9.3 or lower and recompile jackd1 again.If you get errors like

alsa.so: undefined symbol: fast_randUnknown driver "oss"

It means that you have not uninstalled jackd2 successfully. Try to uninstall it again and then recompile jackd1. Delete jack module manually also before recompiling jackd1:rm -f /usr/lib64/jack/jack_oss.so

As you can see jackd2 support is still on expetimental phase and no one knows what makes it work or not work. Perhaps if you don't have testing libs and packets installed you have more chances to successfully build and use jackd2. I personally don't see any benefits in jackd2 because jackd1 is not dead and being developed. And jackd1 also supports dbus.

If you get Segmentation fault error at starting jackd1 it sometimes means that -C or -P options are set incorrectly within jackd starting command. For example, i get such an error with -C/dev/null . Perhaps you may have the same error with jackd2. Try to change the launching command before uninstalling jackd2. jackd2 may start to work.This assumption was wrong. I manaed to build jackd2 again. You should not use -C option with jackd2 at all!I can't compile jackd with --mixed and --profile options. What does it mean? mixed provides both 32 and 64 bit libs. Without 32-libs some applications may crash like airware manager and this means you won't be able to use kontakt soundfonts.Perhaps my last build is less successful to some uknown reasons because previously airwave manager worked like charm. So keep trying building jackd2.

Remember that if you update portage or layman (by the commands emerge --sync, layman -S, eix-sync) your custom-modified ebuild can be replaced by the ebuild from portage and you will have to repeat the entire above procedure to reinstall jackd2 1.9.10.

Thank you ossuser so much for this newer version of the patch. I was trying to find a way to patchthe ossdriver for the newer versions of jackd2 but could never could get it to work; as a result I hadto stick the the ossdriver patch for the jackd2 version 1.9.7.

I am using currently using ubuntustudios 14.04 with realtime kernel and the sound quality is extraordinary.

My only question about this newer ossdriver patch I have is why is the DSP Load always on 100% whenstarting jackd2?

When running jackd 1.9.7 I get lower DSP Loads (12%) when starting jackd2.