Linux-audio-user

linux-audio-user@lists.linuxaudio.org

3 participants
20662 discussions

by Joel Nash

Hi, I'm looking for ecasound experts, I’m using csound to write audio files that I then mix with ecasound. I want to know more about how ecaound reads the audio files. What I tried in ecasound was -audioloop so that the same file is read over (simple enough). I’ll then make adjustments to this file and whilst maintaining the same name on the same path for that file and then recompile csound to essentially make a new file. When ecsound “realises” this it has to stop? I then have to exit and reopen ecasound and play the file again. Is it possible to have ecasound just continue reading the file thats named in the command? what makes stop reading the file? ...perhaps before ecasound loops again it can reload the file into the buffer to I don't can to hit command interrupted and restart the engine each time I make an edit to the file thats looping? I hope this is clear enough of an idea here. Many many, thanks

7 years, 1 month

[ANN] Qsynth 0.5.3 - An Autumn'18 Release

by Rui Nuno Capela

Hello? Do you remember? Should have been (back in) September,... well, whatever... FluidSynth [2] V2 is in there now, rejoice! Qsynth 0.5.3 (autumn'18) is now released! Qsynth [1] is a FluidSynth [2] GUI front-end application written in C++ around the Qt [3] framework using Qt Designer. Website: https://qsynth.sourceforge.io http://qsynth.sourceforge.net Project page: http://sourceforge.net/projects/qsynth Downloads: http://sourceforge.net/projects/qsynth/files - source tarball: http://download.sf.net/qsynth/qsynth-0.5.3.tar.gz - source package (openSUSE Tumbleweed): http://download.sf.net/qsynth/qsynth-0.5.3-14.rncbc.suse.src.rpm - binary package (openSUSE Tumbleweed): http://download.sf.net/qsynth/qsynth-0.5.3-14.rncbc.suse.x86_64.rpm - AppImage [6] package: http://download.sf.net/qsynth/qsynth-0.5.3-5.x86_64.AppImage Git repos: https://git.code.sf.net/p/qsynth/code https://github.com/rncbc/qsynth.git https://gitlab.com/rncbc/qsynth.git https://bitbucket.com/rncbc/qsynth.git Change-log: - Current FluidSynth version information added to command line output (-V, --version). - Overhaul adaptations to the FluidSynth API V2 (>= 2.0.0). - AppStream metadata updated to be the most compliant with latest freedesktop.org specification and recommendation. License: Qsynth [1] is free, open-source Linux Audio [4] software, distributed under the terms of the GNU General Public License (GPL) version 2 or later [5]. See also: http://www.rncbc.org/drupal/node/1944 References: [1] Qsynth - A fluidsynth Qt GUI Interface https://qsynth.sourceforge.io http://qsynth.sourceforge.net [2] FluidSynth - A SoundFont Synthesizer A real-time software synthesizer based on SoundFont 2 specifications http://www.fluidsynth.org [3] Qt framework, C++ class library and tools for cross-platform application and UI development http://qt.io/ [4] Linux Audio consortium of libre software for audio-related work http://linuxaudio.org [5] GPL - GNU General Public License http://www.gnu.org/copyleft/gpl.html [6] AppImage, Linux apps that run anywhere http://appimage.org/ Enjoy && keep having fun! -- rncbc aka Rui Nuno Capela

7 years, 1 month

Re: [LAU] GxPlugins.lv2, Wayland and X (Was: Re: Linux-audio-user Digest, Vol 140, Issue 9)

by Chris Caudle

On Wed, October 10, 2018 6:16 am, Dale Powell wrote: > I found this post: > https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-serv… > > Where it states that the default Ubuntu 18.04 BB installation comes with > Wayland enabled, and you need to disable Wayland to use X instead. It seems Canonical made things way more difficult than it should be. On Fedora there is a settings button where you select or enter your user name on the gdm login screen. There you can select Gnome (defaults to Wayland), Gnome on Xorg, KDE Plasma (defaults to Xorg), KDE Plasma on Wayland, and if you have other desktop environments those have menu entries as well. There should be no need to disable either xorg or wayland, the system should be able to start the correct environment when needed. My system goes back and forth, I typically use Plasma on Xorg, one of my kids used to use Gnome on Wayland, but some game didn't handle graphics correctly on Wayland so switched back to Gnome on Xorg. The screen goes blank for about a quarter or half second when switching back and forth between a Wayland desktop and an Xorg desktop, but that is the only noticeable effect. -- Chris Caudle

7 years, 1 month

Re: [LAU] GxPlugins.lv2, Wayland and X (Was: Re: Linux-audio-user Digest, Vol 140, Issue 9)Re: Linux-audio-user Digest, Vol 140, Issue 10

by Juha Siltala

> On October 8, 2018 2:27:50 AM HST, Juha Siltala wrote: > > > > > Hmm, do they work on Ubuntu 18.04's Gnome3-based user interface > > > running on top of Wayland (without X)? > > > > AFAIK any X client will work in a Wayland session just fine, thanks > > to > > XWayland. > > > > JS > > XFCE won't run on Ubuntu 18.04 unless you set Ubuntu to use X instead > of Wayland. And it doesn't run reliably even then. In that case, maybe Ubuntu's Wayland or XWayland implementation is a bit "special". It is *supposed* to work just like that so that you don't even know, and it does work on most systems. JS

7 years, 1 month

GxPlugins.lv2 v0.5 released

by Hermann Meyer

Hi Today I released a new version of the GxPlugins.lv2 package. GxPlugins been Lv2 plugins based on circuit simulations from various pedals. True mostly they are distortion pedals from the last century. :lol: Some of them been amp simulations, some been plain filters. However, this release introduce the switch from GTK based user interfaces to Xlib based ones. This means, they will work now flawless in nearly any host, at least in any I've tried so far. As well this release add a couple of more sims, from changelog: add GxHeathkit.lv2 add GxFz1b.lv2 add GxFz1s.lv2 add GxKnightFuzz.lv2 add GxLiquidDrive add GxDOD250.lv2 add GxMicroAmp add GxTubeDistortion As a side note, GxPlugins been developed with the MOD as host in mind, therefore they are optimized to use as less CPU power as possible, therefore they work best at the SampleRate the MOD use, which is 48kHz. They work as well on 96kHz (by downsampling), but don't use them in projects with 44,1kHz or 88,2kHz. So, here you go: https://github.com/brummer10/GxPlugins.lv2/releases regards hermann

7 years, 1 month

Receiving multiple inputs over network uzing zita-n2j

by ahmethungari

Hi everyone, I'm trying to set a single laptop to receive two different inputs over network from two other computers. So, there are two sender computers and one receiver. I'm trying to use zita-njbridge. On sender computers I run sender1 $ zita-j2n --chan 1 192.168.1.5 5000 sender2 $ zita-j2n --chan 1 192.168.1.5 5001 And on receiver computer I try to run receiver $ zita-n2j --chan 1 192.168.1.5 5000 --buff 65 receiver $ zita-n2j --chan 1 192.168.1.5 5001 --buff 65 And the second zita-n2j comand gives an error "Address already in use" I thought having two different port numbers for different senders would allow me to run zita-n2j twice on the same computer, but apparently I was wrong. Is there any possibility to do so? I can also accept zita-njbridge alternatives as an answer. All I want to do is to receive two (or more) sources over network on a single computer and then mix them. -- Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html

7 years, 1 month

Re: [LAU] Jacks and sockets - Was: Berlin Linux Audio meeting @ c-base 2018-10-09

by Tim

On 10/07/2018 04:45 AM, Ralf Mardorf wrote: > On Sat, 2018-10-06 at 17:36 -0400, Tim wrote: >> On 10/06/2018 03:51 PM, Ralf Mardorf wrote: >>> https://www.roland.com/us/products/gkc-5_10/ >> >> Most folks become aware that even the best quality single-conductor >> (with shield ground) 1/4" guitar cables eventually break. It happens >> to all of them. Usually at the entry point to the plug, or in the >> plug itself. > > Hi, > > I confirm this and most likely anybody else does, too. > >> Now take that hard-learned experience with a single-conductor cable >> and apply it to *thirteen* conductors. Guess what happens... >> >> (Jacks for these DIN type plugs are usually never a problem if >> secured and soldered properly. Usually far less trouble than >> other types of jacks.) >> >> Often, the cause of the cable's break is the plug's strain relief >> being too tight - ironically the very thing that is supposed >> to help prevent breakage in the first place. >> >> I can't be too harsh on this product for the price/weight range. >> But yeah, buy TWO of them to be safe. > > Hi, > > the reason that I like to get more information about this Roland cable > is, that there are a lot of less expensive 13 pin DIN cables available > by the Internet and I do not only need a backup cable, I also want to > get a shorter cable than those sold by Roland. > > Some of the non-Roland cables seem to be without a locking mechanism, > but other provide a locking mechanism, e.g. the CD changer cables. I > wonder about the used cables. Are all cable cores of the original Roland > cable audio cables or are the cores a mix of different kind of cables? > Do other 13-pin DIN cables provide the same pin to pin connection as the > Roland cable? Since we know that some elChepo audio cables are ok for > 50 cm short cables, but 3 m long cables worsen sound quality, while more > expensive cables are still ok for cables way longer than 3 m, I wonder > what 13-pole cables are good and which are bad. When using the Roland > cable for the "normal" guitar pickups, too, the sound quality of the > audio signal from the "normal" pickups is good. Unfortunately there is > no printing on the Roland cables. If I want to build my own cables, what > cables and what jacks might be good? > > My favoured electronic part dealer provides only one 13-pin din jack > that fits, it's without locking mechanism and seemingly an elCheapo. The > dealer calls it "monitor plug" and yes, my Atari SM124 has got a 13-pin > din jack without locking mechanism, too. The dealer seems not to sell > any 13 cores cables at all. > > Ordering jacks and cable from perhaps different dealers + time exposure > might not be worth the effort, to build a non-Roland cable, but perhaps > ordering a CD changer cable could be a solution to replace an original > Roland cable. > > Regards, > Ralf Hm, I'm seeing wildly varying prices for the cables on ebay. The originals seem... a little over-priced. I can see why you'd be shopping around, I would too :-) Best advice I would say is read any user reviews accompanying them, since they seem to be from people who actually use them for this specific purpose. Usually I wouldn't worry about the locking mech, but in this case since one end goes into the guitar that would be important. Most of the ones I'm seeing appear to have the lock. Be sure to only look at ones that are for this Roland-compatible purpose. Other cables may be 13 pins but they may not be pin-compatible, and even if they are, the wires and shield may not be a good thickness, insulation, stiffness etc. Especially those CD changer cables, may not be the right thing. In those, some of the wires may be individually shielded which carry audio, and the other wires may be just control signals, so it's not really the right thing. Randomly selected, this one for example promises to be pretty good: https://www.ebay.com/itm/usa-seller-LOCKING-13-PIN-CABLE-SYNTH-ROLAND-GKC-3… I was going to talk about the GKC wires carrying raw, weak un-buffered signals from the pickup... but it turns out that's *not* true ! Looky here, I found a schematic of the GK2/3 at the top of this page: https://www.vguitarforums.com/smf/index.php?topic=73.0 And here is the VG-88 service manual: https://elektrotanya.com/roland_vg-88_sm.pdf/download.html According to those diagrams, the cable carries power, and *buffered* signals, and some up/down switches and volume control signals. Therefore, some of the wires (the six pickup signals) might be individually shielded and the others not, with a master shield ground surrounding the whole lot. Thus the cable core itself may be a special cable not easily found to buy. But I'm not sure, possibly a normal 13-conductor cable would actually be OK since the signals are buffered. If you find such a wire and decide to attempt to make your own cable, some advice I can offer is to have a can of technician 'freeze spray' handy. Or a can of compressed air 'duster' (Dust-Off etc.) turned upside down will also do. The reason is that when attempting to solder such tiny wires to such plug pins, you only have a few millimeters of exposed copper followed by a few millimeters of wire insulation before the wire disappears into the cable. The heat from the soldering iron can *easily* melt that insulation and before you know it you have a mess of melted insulation on your hands and you'll have to cut the cable and start over. So after each application of heat from the iron, be sure to immediately freeze the area to prevent the heat from traveling further down the wire melting the insulation. Also you'd better have nerves of steel and steady hands soldering thirteen tiny wires to thirteen tiny plug pins. It can be frustrating, I know. Probably not worth the effort, I would buy a cable. Tim.

7 years, 1 month

Jacks and sockets - Was: Berlin Linux Audio meeting @ c-base 2018-10-09

by Ralf Mardorf

On Sat, 6 Oct 2018 10:31:55 -0700 (PDT), Len Ovens wrote: >There are more robust ethernet rj45 solutions: >https://www.avshop.ca/wire-amp-cable-connectors-ethernet/neutrik-ne8fdp-rj4… >https://www.avshop.ca/wire-amp-cable-connectors-ethernet/neutrik-ne8mc-1-et… > >I don't know if the cycle count improves at all though. It does improve the steadiness of the jack to socket connection itself and provides a strain relief. IMO it's a good idea. I would like to continue talking about jacks. If somebody does know something about the jacks and cables used for https://www.roland.com/us/products/gkc-5_10/ , please reply off-list. However, off-list I was asked to stop my annoying off-topic writing regarding jacks. My apologies for disturbing the important "Berlin Linux Audio meeting" notes.

7 years, 1 month

[ANN] Submit your Open Source Music FM Synthesizer Challenge entry now!

by Christopher Arndt

Hi Synth Lovers, there are only less than *eight days* left in the Open Source Music FM Synthesizer Challenge to finish and submit your entry. The competition entry submission form is now finally online (sorry for the long delay), so please submit your entries here before Oct 14th, 2018 23:59:59 UTC: https://fmchallenge.osamc.de/submit/ I encourage you all to submit your tracks as soon as possible even if they are not finished yet. Each submitted entry is first in draft status, until you publish it. Only then* will the track be publicly visible and really enter the competition. If it stays in draft status until the deadline, it does *not* enter the competition, so there's no harm in submitting your track now, even if you are not sure whether you will finish it in time. But you won't miss the deadline, just because there are technical difficulties or your upload to Archive.org doesn't pass the checks. * I also need to approve it. I will basically just check the description and production notes for spam and conformance to the rules and usually approve it within minutes if everything is ok. P.S. The first one to break the web application gets to keep the pieces! ;) Seriously, if there are any problems with the submission form or the site, please contact me via <fmchallenge(a)osamc.de> immediately. P.P.S.S. There will be another announcement on Monday about an very desirable sponsored prize for the winner, so keep an eye out! I'm looking forward to hear what you came up with! -- Christopher Arndt Open Source Audio Meeting Cologne https://fmchallenge.osamc.de/ fmchallenge(a)osamc.de

7 years, 1 month

Berlin Linux Audio meeting @ c-base 2018-10-09

by Daniel Swärd

Hi all. Next meeting at c-base is on Tuesday 2018-10-09. I'll be in the mainhall from 20:00. At the last meeting we were jamming a bit in the soundlab and that was fun, so I've reserved the soundlab for us again. If we're going to go down to the soundlab, I'd suggest that we collect people in the mainhall between 20:00 and 20:30 before going downstairs. Cheers /Daniel

7 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-user