planet.linuxaudio.org

September 16, 2019

blog4

Elektronengehirn Berlin concert 18.September

On wednesday the 18. September I will perform the first time my piece for modular synthesizer and real estate data with my project Elektronengehirn. The concert will be at Experimentik Berlin, Germany. It is part of my art project The Big Crash. For the soundpiece I created a software which harvest real estate websites for their ads to gather pictures and prices. The pictures are analyzed with Machine Learning software performing an image segmentation and object recognition. The resulting fragments are used in further artpieces of The Big Crash but also serve here as controldata for additive synthesis. The prices and squaremeters of the advertised Berlin flats are used to control an analog modular synthesizer.


by herrsteiner (noreply@blogger.com) at September 16, 2019 08:11 PM

September 15, 2019

digital audio hacks – Hackaday

Scratch Built Media Player Channels 1980s Design

No, you aren’t looking at a 30 year old Teac graphic equalizer that somebody modified. The MWA-002 Network Music Player created by [GuzziGuy] is built entirely from new components, and easily ranks up there with some of the most gorgeous pieces of homebrew audio gear we’ve ever seen. Combining modular hardware with modern manufacturing techniques, this 1980s inspired build is a testament to how far we’ve come in terms of what’s possible for the dedicated hacker and maker.

The enclosure, though it looks all the world like a repurposed piece of vintage hardware, was built with the help of a CNC router. It’s constructed from pieces of solid oak, plywood, and veneered MDF that have all been meticulously routed out and cut. Even the front panel text was engraved with the CNC and then filled in with black paint to make the letters pop.

Internally, the MWA-002 is powered by a Raspberry Pi 3 running Mopidy to play both local tracks and streaming audio. Not satisfied with the Pi’s built-in capabilities, [GuzziGuy] is using a Behringer UCA202 to produce CD-quality audio, which is then fed into a TPA3116 amplifier. In turn, the output from the amplifier is terminated in a set of female jacks on the player. Just like the stereo equipment of yore, this player is designed to be connected to a larger audio system and doesn’t have any internal speakers.

The primary display is a 256×64 Futaba GP1212A02A FVD which has that era-appropriate glow while still delivering modern features. [GuzziGuy] says it was more difficult to interface with this I2C display than the LCDs he used in the past due to the lack of available libraries, but we think the final product is proof it was worth the effort. He bought both the VFD spectrum analyzer and LED VU meter as turn-key modules, but the center equalizer controls are completely custom; with dual MCP3008 ADCs to read the state of the sliders and the Linux Audio Developer’s Simple Plugin API (LADSPA) to tweak the Pi’s audio output accordingly.

We’re no strangers to beautiful pieces of audio gear here at Hackaday, but generally speaking, most projects involve modernizing or augmenting an existing device. While those projects are to be admired, the engineering that goes into creating something of this caliber from modular components and raw building materials is really an accomplishment on a whole different level.

by Tom Nardi at September 15, 2019 02:00 PM

September 14, 2019

Libre Music Production - Articles, Tutorials and News

The future of LMP

LMP will continue to live on as a static site, so all content will continue to be available. We are in the process of moving the site. Stay tuned for more news.

Thank you for all support, content, comments and visits!

Now on to produce some Libre Music! :)

by admin at September 14, 2019 06:14 AM

September 12, 2019

Internet Archive - Collection: osmpodcast

An error occurred

The RSS feed is currently experiencing technical difficulties. The error is: invalid or no response from Elasticsearch

September 12, 2019 12:58 AM

August 29, 2019

blog4

performance Tina Mariane Krogh Madsen / Sall Lam Toro 31.August Aarhus (DK)

Tina Mariane Krogh Madsen will be performing together with artist Sall Lam Toro for the first time at Performancefestival organized by PERFORMANCErum and Udstillingsstedet Spanien19C as part of Aarhus Festuge in Aarhus (DK).

The performance DECONSTRUCTING, DISTORTING, QUEERING DREAMS will be on the 31st August from 17-20h CET at selected places in Aarhus and at Spanien 19C, Kalkværksvej 5A, 8000 Aarhus (DK).



About the performance:

DECONSTRUCTING, DISTORTING, QUEERING DREAMS is an interdisciplinary project that interweaves performance art, interaction, video, sound and movement, with live coding and online streaming. The project is rooted in the breakdown of stereotypical notions of places, their heritage and environment. It wishes to shift the perception of center and periphery through the creation of art with distribution as strategy. The project has an experimental format that links several sites together. Sall Lam Toro performs at three different locations in Aarhus, and Tina Mariane Krogh Madsen is situated in Spanien 19C creating an environment that combines live coding with video, sound interactions with objects and artefacts, as well as direct web communication with Sall Lam Toro. These interactions are streamed live and merged with Madsen's sonic universe. The networked activity should be perceived as a performance space in itself, as an actant, where the performers share materials, thoughts, quotes, and instructions live via the web. The performance has a duration of 3 hours.


The performance coordinates which shows Sall Lam Toro's start positions will be shared on this website before the performance, where also additional notes, writings and documentations will be shared:

by herrsteiner (noreply@blogger.com) at August 29, 2019 10:21 PM

August 24, 2019

Talk Unafraid

A focused approach

In my last post on astrophotography I wrote about planning for dark skies and about my plans to build an observatory. Well, finances haven’t permitted for the observatory – this year – so this month I opted to get my existing telescope and mount working at their theoretical best.

This mostly boiled down to:

  • Improving the ability to achieve and hold accurate focus
  • Getting the mount running as smoothly and accurately as possible
  • Making small improvements to the way I set things up
  • Getting the optics as precisely collimated as possible

If I do all those things then the limiting factors should be the intrinsic limits of the kit I have and the environment, and I should be able to produce some great pictures with all that! So I started off, knowing the focuser was mechanically weak and a real problem in terms of operating the scope, by replacing the focuser.

Focusers and motors

This started out as a “undo 4 bolts, replace 4 bolts” project and turned into a bit more work. It also required me to remove the secondary mirror for the first time, which meant tooling up to collimate that properly – my laser isn’t enough to set the position completely.

The new, on the left, and the old. Note the chunkier construction, much bigger bearings, and the larger motors. The new one’s also larger, and internally baffled to help cut down on stray light.

The holes in the tube didn’t quite fit the new plate, so I had to drill new holes – I measured very carefully, several times, with different measurement approaches (not wishing to recreate the Hubble problem of relying on a single instrument). The position isn’t critical but it makes life easier if it’s in the right place.

Nervous drilling

The focuser I went for was a Baader Steeltrack Diamond. To summarise the choice, there’s only a few major groups of manufacturers – Moonlite and friends sit at the “fine for visual, okay for imaging” end of things with traditional Crayford designs. Then you’ve got people like Baader and JTW who are a bit more serious about focuser slop and rigidity. Then there’s Feather-Touch. FT appear to be held in messianic regard by literally everyone, which I can only assume is for good reason. They’re also two to three times the price. Which rules them out. Baader’s Diamond NT focuser appeared to be very well regarded mechanically, and having bought a number of parts from them I knew they were of good quality.

It didn’t disappoint – it’s very well made, and manual movement of the focuser when it arrived was buttery. I popped the fine focus knob off and prepared it for the addition of the focus motor

If you’ve not done imaging before you might think that motorising a focuser is a bit excessive – and indeed when I started out I just focused manually once at the start of the evening and then left the camera to it. But to get the most out of a telescope, frequent or constant refocusing is needed, to compensate for contraction of the telescope and optics due to temperature change. It’s also useful to be able to let the computer focus for you to achieve the most precise focus.

Again, there are many options here. I opted for a lower cost option which was fairly well reviewed, the Primaluce Lab Sesto Senso focus motor. This despite it missing a key feature, temperature compensation. This feature automatically moves the motor based on a temperature reading, rather than having the computer do it for you. However, most software supports doing this. Sadly, KStars/Ekos does not – yet.

The new focuser and motor installed on the tube

Spot the difference

After installing the focuser and motor I had to re-install the secondary and collimate it – this was actually pretty straightforward. However I also wanted to replace the centre spot on my telescope with a “hotspot” to make barlow laser and autocollimator checks easier, so the primary mirror came out too. Both got a very gentle soak and rinse with no agitation, and then the old primary spot was removed with some isopropyl alcohol.

The old spot and mirror in its cell
The mirror, spotless!
Spotting the mirror using a Cats Eye template, weighted down with cotton wool. There was a lot of careful staring at this before I affixed the spot.
The completed install.

After this there was just a lot of very time consuming adjustment to get everything set up as well as possible. This mostly just involved staring down cheshire eyepieces and then moving things very slowly with an allen key until it all looked like it should.

A quick barlowed laser check as part of reassembly, looking down the tube – you can see the reflection of the centre trefoil in the middle, which is actually a reflection off a piece of paper in the bottom of the barlow in the focuser.

I still need to add an autocollimator to my toolbox, but the Catseye ones are quite dear, so that’s a “next month” purchase. That will however be the last tool I need to add there, I think!

Mount problems

I had been seeing issues with my tracking the last few attempts I made to set up, so wanted to verify my mount was mechanically sound. This mostly involved adjusting the worm carrier blocks – large metal blocks which form both part of the housing and the mechanism by which the worm meshing can be adjusted. This, again, involved a lot of slackening off one thing, tightening another, then rotating the whole axis through 360 degrees to make sure nothing bound or stuck.

Dismantling an axis driver to check everything is okay – the worm carrier block is the lower bit of metal, where the big gear sits. Behind this is the worm gear shaft.

After a lot of measurement, trying to work out what was going on, I realised it was the obvious thing – polar alignment. My Polemaster – a camera that sits on the mount to do a polar alignment – wasn’t getting good enough results, and that was all I was using. I used a method called drift alignment and improved from ~15 arcminutes accuracy down to about 2 arcminutes. This has radically improved my guiding, which is now down at around 1 arcsecond – where it should be! The adjustment knobs on the EQ6-R Pro are the limiting factor now – it’s just not possible to get the alignment much better.

Balancing the mount more carefully has helped, too, and I’ve rotated the telescope in its tube so the focuser points at the RA axis. This means that as the axis rotates the weight distribution remains constant. It also means I can’t really use the telescope for visual observation, but I’ve not done that in a long while!

I’ve also added some Celestron anti-vibration pads to the tripod. While a cubic metre or two of concrete would be better, these should help isolate vibration from the ground and also help with oscillation in the tripod itself as a result of mount movement.

To help minimise the number of cables coming off the mount I’ve also put my INDI server on the tube itself by mounting a Raspberry Pi, 12V-5V step-down, and USB hub. This also helps to counterbalance the focuser around the Dec axis. There’s now only three cables to the mount – 12V, Ethernet, and the mount control cable.

The other major upgrades I’ve made lately have been on guidescope mounting – I now have some very solid aluminium guidescope brackets that a colleague at work milled for me. This does appear to have solved the differential flexure problem. I still want to upgrade the camera and explore off-axis guiding, but it’s a great improvement.

Worth it?

It’s too early to say, really, but the indication is that probably, together, this has all produced a much improved system for astrophotography for not much (in AP terms) money. This image of M101, the Pinwheel galaxy, I produced last night with less than 2 hours of light:

Precise focus has helped massively, though temperature compensation and per-filter focus offset automation would be very welcome additions to Ekos – it might even be enough to push me back to Sequence Generator Pro, though I’m very much enjoying the INDI/Linux approach so far (bugs that require me to completely shut down KStars mid-session aside). The mount guiding is definitely a big upgrade over where it was – I think I had broadly been getting lucky with this over winter, though I suspect the colder atmosphere might’ve helped the Polemaster.

All in all it’s a good step forward – now I just need some really cold clear skies!

by James Harrison at August 24, 2019 06:34 PM

July 24, 2019

rncbc.org

Qtractor 0.9.9 - Summer'19 Release batch #3


Hello all,

For the third time and hopefully the last in the current northern estival season comes the final batch-of-one:

Qtractor 0.9.9 (summer'19) is out!

These are the changes for this Summer'19 release:

  • Fixed editing and display of 'Pgm Change' events on the MIDI clip editor (aka. piano-roll).
  • Introducing tempo/beat-detection support on the Clip / Tempo Adjust... dialog (provided libaubio >= 0.4.1 is available); and now also featured with some rough visual clues ;).
  • Updated for the newer Qt5 development tools (>= 5.13).
  • Imply asking for a brand new filename (ie. Save As...) whenever the session file original sample-rate differs from the current audio device engine (ie. JACK).
  • Configure updated to check for qtchooser availability.
  • Fix MIDI through for LV2 plug-ins that have no MIDI output event/atom ports.

Description:

Qtractor is an audio/MIDI multi-track sequencer application written in C++ with the Qt framework. Target platform is Linux, where the Jack Audio Connection Kit (JACK) for audio and the Advanced Linux Sound Architecture (ALSA) for MIDI are the main infrastructures to evolve as a fairly-featured Linux desktop audio workstation GUI, specially dedicated to the personal home-studio.

Website:

http://qtractor.org
https://qtractor.sourceforge.io
http://qtractor.sourceforge.net

Project page:

https://sourceforge.net/projects/qtractor

Downloads:

https://sourceforge.net/projects/qtractor/files

Git repos:

https://git.code.sf.net/p/qtractor/code
https://github.com/rncbc/qtractor.git
https://gitlab.com/rncbc/qtractor.git
https://bitbucket.org/rncbc/qtractor.git

Wiki (help still wanted!):

https://sourceforge.net/p/qtractor/wiki/

License:

Qtractor is free, open-source Linux Audio software, distributed under the terms of the GNU General Public License (GPL) version 2 or later.

Enjoy && Lots of fun.

Donate to rncbc.org

by rncbc at July 24, 2019 06:00 PM

July 22, 2019

Audio – Stefan Westerfeld's blog

SpectMorph 0.5.0 released

A new version of SpectMorph, my audio morphing software, is now available on www.spectmorph.org. SpectMorph is a VST/LV2/JACK synthesis engine which is based on the idea of analyzing audio samples and combining them using morphing.

SpectMorph could always create sounds by morphing between the musical instruments bundled with SpectMorph. With this release, a new graphical instrument editor was added, which allows loading custom samples. So SpectMorph users can now create user defined instruments and morph between them.

Here is a screencast which demonstrates how to do it.

Besides this big change, the releases contains a few smaller improvements. A detailed list of changes is available here.

Finally, here is some new music made with SpectMorph:

by stw at July 22, 2019 02:45 PM

July 18, 2019

rncbc.org

Vee One Suite 0.9.9 - Summer'19 Release batch #2


Summery cheers!

The Vee One Suite of old-school software instruments are here released for the northern estival sesson:

All still available in dual form:

  • a pure stand-alone JACK client with JACK-session, NSM (Non Session management) and both JACK MIDI and ALSA MIDI input support;
  • a LV2 instrument plug-in.

The changes for this second batch of the Qstuff* Summer'19 release series are:

  • Randomization of current parameters and partials is now available through a new top-level push-button and the context-menu respectively (partials randomization is applicable to padthv1 only).
  • Zero-crossing detection algorithm has been improved, most specially to mitigate transient clicks across offset and/or loop points (whether applicable to samplv1 and drumkv1 only).
  • Updated for the newer Qt5 development tools (>= 5.13).
  • Per instance custom tuning (micro-tonal) option has been added to the previously existing global settings (cf. Help > Configure... > Tuning > Global, Instance).
  • New DCF, LFO and DCA Enabled parameters (DCA disabling is applicable to samplv1 and drumkv1 only).
  • Configure updated to check for qtchooser availability.

The Vee One Suite are free, open-source Linux Audio software, distributed under the terms of the GNU General Public License (GPL) version 2 or later.

 

synthv1 - an old-school polyphonic synthesizer

synthv1 0.9.9 (summer'19) is out!

synthv1 is an old-school all-digital 4-oscillator subtractive polyphonic synthesizer with stereo fx.

LV2 URI: http://synthv1.sourceforge.net/lv2

website:
https://synthv1.sourceforge.io
http://synthv1.sourceforge.net

project page:
https://sourceforge.net/projects/synthv1

downloads:
https://sourceforge.net/projects/synthv1/files

git repos:
https://git.code.sf.net/p/synthv1/code
https://github.com/rncbc/synthv1.git
https://gitlab.com/rncbc/synthv1.git
https://bitbucket.org/rncbc/synthv1.git

 

samplv1 - an old-school polyphonic sampler

samplv1 0.9.9 (summer'19) is out!

samplv1 is an old-school polyphonic sampler synthesizer with stereo fx.

LV2 URI: http://samplv1.sourceforge.net/lv2

website:
https://samplv1.sourceforge.io
http://samplv1.sourceforge.net

project page:
https://sourceforge.net/projects/samplv1

downloads:
https://sourceforge.net/projects/samplv1/files

git repos:
https://git.code.sf.net/p/samplv1/code
https://github.com/rncbc/samplv1.git
https://gitlab.com/rncbc/samplv1.git
https://bitbucket.org/rncbc/samplv1.git

 

drumkv1 - an old-school drum-kit sampler

drumkv1 0.9.9 (summer'19) is out!

drumkv1 is an old-school drum-kit sampler synthesizer with stereo fx.

LV2 URI: http://drumkv1.sourceforge.net/lv2

website:
https://drumkv1.sourceforge.io
http://drumkv1.sourceforge.net

project page:
https://sourceforge.net/projects/drumkv1

downloads:
https://sourceforge.net/projects/drumkv1/files

git repos:
https://git.code.sf.net/p/drumkv1/code
https://github.com/rncbc/drumkv1.git
https://gitlab.com/rncbc/drumkv1.git
https://bitbucket.org/rncbc/drumkv1.git

 

padthv1 - an old-school polyphonic additive synthesizer

padthv1 0.9.9 (summer'19) is out!

padthv1 is an old-school polyphonic additive synthesizer with stereo fx

padthv1 is based on the PADsynth algorithm by Paul Nasca, as a special variant of additive synthesis.

LV2 URI: http://padthv1.sourceforge.net/lv2

website:
https://padthv1.sourceforge.io
http://padthv1.sourceforge.net

project page:
https://sourceforge.net/projects/padthv1

downloads:
https://sourceforge.net/projects/padthv1/files

git repos:
https://git.code.sf.net/p/padthv1/code
https://github.com/rncbc/padthv1.git
https://gitlab.com/rncbc/padthv1.git
https://bitbucket.org/rncbc/padthv1.git

 

Donate to rncbc.org

Enjoy && Take fun!

by rncbc at July 18, 2019 06:00 PM

News – Ubuntu Studio

Ubuntu Studio 18.10 Reaches End-Of-Life (EOL)

As of today, July 18, 2019, Ubuntu Studio 18.10 has reached the end of its support cycle. We strongly urge all users of 18.10 to upgrade to Ubuntu Studio 19.04 for support through January 2020 and then after the release of Ubuntu Studio 19.10, codenamed Eoan Ermine, in October 2019 which will also be supported […]

by eeickmeyer at July 18, 2019 01:00 AM

June 26, 2019

Talk Unafraid

When the skies are bright, plan for darkness

Gotten a bit quiet here, hasn’t it? Well, here in the UK, it’s wonderfully sunny and bright. We don’t get proper darkness, and the planets are in an awful position, so imaging deep-space objects is a bit of a non-starter, or at least challenging. We’ve also had a run of crap weather, just to drive the point home.

I’ve been using the time instead to plan out my next astro-related project (though I may well push the execution out to 2020, just to make sure I have the cash to get it done right) – a fully automated roll-off roof observatory. The logic behind this is simple – my next “improvements” to my imaging system that I can make are:

  1. Upgrade the camera – already got a pretty good camera, so this means something quite high-end (>£3-4k), and would just get me more sensitivity/bigger pixels/larger field of view
  2. Upgrade the telescope – already got a decent Newtonian so a meaningful upgrade means either a high-end Newtonian/R-C astrograph (£3-4k) or a decent large-aperture apochromatic refractor (£4-5k)
  3. Add a second telescope – to do planetary imaging I could add a SCT or long-focal-length scope of some other sort, but the planets will be too low for the next couple of years for serious imaging, and it’d still be £2-3k of investment
  4. Update my telescope’s other parts (focuser, focus controller) and invest in tools (collimation, etc) – more reasonable investment (£1-2k) but just gets me slightly better images – this is my favourite option if I don’t do the observatory this year
  5. Build an automated observatory – easily doubles the number of images I can capture with my existing kit, thus acting as a massive force multiplier for my previous investments – but £4-5k at least!

So the biggest “bang for buck” is definitely the observatory, but only if it is fully automated. I’ve lost track of the number of nights where the sky was beautiful and clear, the clouds nowhere to be seen, ground and ambient temperatures low enough to make seeing incredibly clear – and I’ve been packing away the telescope at midnight because I’ve got work tomorrow, despite the further 7 or 8 hours of imaging I could have. And then there’s all the “well, it might be good enough, but…” nights – nights where the forecast says it won’t be good enough, but you might get lucky; often this involves going out frequently to stare at the sky, setting up if I feel optimistic, and usually being disappointed – but often not.

With a fully automated and remotely driven set-up the setup time is nil, as is the tear-down time. With the scope set up permanently, with the camera and other components mounted, there’s much more scope (no pun intended) for tweaking and tuning in advance of an imaging night, and fine tuning on cold-but-cloudy nights that just isn’t possible when you’re stripping the whole thing down each night. Being able to work in the dry and the day has a lot of appeal.

System-wise, full automation is pretty simple – you need a box with relays to drive motors and read sensors, a proper cloud/rain sensor (hard-wired to the relay box, so if any computers fail there’s a pretty dumb box responsible for shutting the roof when it rains), and a system capable of automating the selection of targets (what’s good tonight?), acquisition of images (frame the target, autofocus, guide and image), and the observatory start-up/shut-down. I’m most of the way here – I need the relay box and auto-focuser. The rest is already ready – I’ve been using INDI/Ekos/KStars for a while which can do all of this. The main INDI instance for the observatory will run on a 1U server in the observatory, with an INDI server on a Raspberry Pi 4 strapped to the telescope doing actual image acquisition and telescope equipment control. This makes the pier-to-desk cables simple – 12V for power, USB for the mount, and an Ethernet cable for the rest, with just 12V and Ethernet onto the telescope itself.

Making a plan

So, the objectives of this build are:

  • Full automation – but at a minimum, a roll-off roof which can open and close under all circumstances for safety – so I can program the observatory to image opportunistically
  • Imaging-stable pier, with room to expand – just the one pier, but room to set up a second non-isolated pier for a small solar/planetary telescope (isolation is less critical for these applications)
  • “Warm” room with enough room for a server rack, desk, chair and a little storage – somewhere I can sit while setting up
  • Good visibility down to ~30 degrees everywhere
  • Strong enough to resist opportunistic forced entry and 100mph wind when closed

Beyond this – it’s basically a shed! So I’ve started by getting a bunch of books on shed design and construction and reading them. My day job at the moment is (mostly) telling people how to properly build a fibre optic network, so I know a reasonable amount about concrete, aggregates, rebar, admixtures and slab design. Making a good solid observatory is mostly about mass, just like in acoustic isolation design, and I’ll be using almost an entire ready-mix concrete truck worth of C40 low-moisture concrete to pour the base slab and the (isolated) pier. The framing and design of walls, floors and doors is all fairly simple, though benefits from careful planning to make sure all the services will work and the structure remains rot-and-rat free for a few decades.

Some basic renders of the general layout – working floor-up. Note the duct from pier to warm room to allow for cables to reach the telescope safely

The tricky bit is the roll-off roof – I need to keep this building rodent-proof and ideally near-airtight to aid in humidity/temperature control. I will use forced, filtered airflow for cooling with a positive pressure maintained to minimise dust ingress. Active cooling with the roof shut will help cool-down times and avoid any kit getting too hot in summer. This means the roof needs to seal well onto the frame when shut. I also need to be able to shut the roof at any time – that means any internal rafters need to be minimal or non-existent, so the telescope doesn’t have to be “pointed down” to let the roof pass. This means when the mount fails or is unsure of its position the roof can still shut safely to keep the rain out. The roof needs to roll back enough to give good visibility, so the whole thing has to roll onto rails that extend beyond the back of the warm room. To further improve visibility and keep rain off the rails, some of the side walls will be mounted on the roof so the walls “lower” as the roof rolls off. There’s a lot of complexity in this (and it has to be something I can build), so this is taking some time to work out.

I’ve started designing in detail in Autodesk Fusion 360 – while I’ve used Sketchup for this sort of thing in the past, Fusion 360 in Direct Modelling (non-parametric mode) is about as user-friendly and can produce much prettier outputs as well as decent engineering drawings.

An early rendering of the pier and shuttering for the initial concrete pour
An early drawing with some detail/section views to show the base layout and design – the deep, chunky base should help isolate the pier from surface vibrations/movement, and the really deep and heavy pier root should by virtue of being heavy do the rest

I’ve also reconstructed my current telescope and mount with photogrammetry so I can build a digital model and check the motion all works – I haven’t gotten around to tidying up the mesh into some simpler models, but it’s a great reference for getting the dimensions and motion right.

Location, location, location

The other question is where to put this – I dithered quite a bit and in the end took a lot of level photos around the garden at twilight with a Ricoh Theta S 360 degree camera at roughly my telescope’s aperture height. With the moon visible in each photo and knowing where and when I took the photos, I could align the photos to north with a fairly simple Python script which spat out a nice set of data for horizon plotting.

Plotting horizons straight out of images. Probably should release the code for this…

It turns out there’s only a few places where I don’t enjoy visibility to 30 degrees pretty much everywhere, so I decided to plug the panorama for my favoured location into Stellarium – this turns out to just involve having a panorama with a transparent sky and a small .ini file to set north properly.

My observatory’s home, Stellarium-ready
… and loaded into Stellarium, so I can see how things will look – spending all the time with Photoshop’s background eraser to get the trees properly semitransparent makes a big impact on the visuals of this (though in summer they’re somewhat more opaque!)

The chosen location makes power and network connectivity simple enough – with 25 metres of mains cable and single-mode fibre I can connect to proper mains and Ethernet, only one switch hop away from my storage arrays.

Security is a concern – that field is adjacent to a footpath, though set back from the road, and there have been break-ins in the area. Other than making the building fairly secure against “opportunistic” crooks – reinforcing the door, lack of windows, and a solid lock – there’s not a lot that can be done. PIR sensors externally won’t work due to the abundant wildlife, so a combination of internal sensors and an alarm to make a racket if someone does force the door or climb in through the open roof will have to do. CCTV around the perimeter might work but could work just as well as an attractant as a deterrent, and wildlife would probably again make alarming impossible. I’m also planning on using a worm geared or lead screw based roof mechanism, which should be very hard to force open.

Making plans

I took the view early on in this that I wanted to build this myself. I’m still not 100% sure about this, but I think it’s a reasonable project and something I should be able to do! I am budgeting for some help, though, and will have to hire kit in regardless – a mini digger for the groundwork, compactor to pack down aggregates, concrete vibrator to settle concrete in the forms, etc.

I also need planning permission. I started with a footprint that wouldn’t normally need it, so long as the building isn’t tall – but I’m in a conservation area, which means “permitted development” doesn’t really apply. I’m not concerned about getting planning permission – it’s a small building in an otherwise empty field (except for a shed we’re going to remove) and will blend in just fine. Having to go through planning permission also means I can relax around some of the limits that I’d otherwise be avoiding.

Working through the material costs there’s easily £2k, maybe £3k of materials – labour would be another £1-2k atop that if not more. That’s quite an investment, and I’m really keen to make sure that everything about this is right – giving up power to a third party feels risky. It may be that when I get the design done I sit down with some local builders that I trust and see what they say.

The first step remains the plan and design, which is taking time – but I think time invested here is time well spent. I may not start until later in the year, or even early next year – one more winter without it wouldn’t be the end of the world. It’s going to be a fun project if I can get the plan right!

MORE DOMES

Fans of domes will be wondering why I haven’t just dropped £3k on a nice big Pulsar/insert-vendor-here dome. The answer is simple:

  • It’s not £3k, it’s £7k by the time you’ve automated it
  • It’s impossible to insulate the roof nicely – you end up slapping neoprene sheets up with glue just to stop condensation build-up raining on your scope
  • They’re relatively small and uncomfortable to work in unless you get big ones which are even more money
  • They only allow for a single telescope
  • They’re definitely harder to get through conservation area planning permission committees

I’ve looked at a few other dome designs and while there’s some good contenders they all have similar problems. I did consider making a “clever” geodesic dome – something I could build pretty cheaply but which would still have decent wind resistance – but automation remains the problem. Ground-level domes (where the whole structure rotates, rather than using a rotating section on a cylinder) make the construction simpler, but the bearing and rotation mechanism have to cope with increased gravity load and all of the wind loading. Cylinder-style observatories have similar problems.

The round/dodecahedral designs of these structures also make literally everything harder. Want to bolt a light to a wall? It’s not flat, so if you want it level/flat you now get to make a bracket… weatherproofing, insulation, and more all get more complicated. Having four flat walls which never move makes life simple – mounting insulation, cable entry glands, coolers, dehumidifiers, fans/filters, lights, shelves, etc is all so much simpler.

So – no dome here for now.

And another thing…

While we’re building a light-shielded box in a quiet location with power and networking, what else could we do? I’m also going to include infrastructure to support a small ground-level dish and motors for radioastronomy, as well as some mounts for meteor spotting cameras, an all-sky camera, and a weather station. I won’t have all this on day one, but putting a little extra concrete in now is way easier than doing it again later, and it means I can put in cable ducts to make wiring it up simpler. The cost of the pads, etc is tiny and turns those future projects from a pain into something much simpler.

by James Harrison at June 26, 2019 09:19 PM

June 24, 2019

News – Ubuntu Studio

Regarding Ubuntu’s Statement on 32-bit i386 Packages

By now you may have seen Ubuntu’s blog post (Statement on 32-bit i386 packages for Ubuntu 19.10 and 20.04 LTS) and saw that it mentions Ubuntu Studio as being one of the catalysts behind the change-of-plans. You may also be wondering why Ubuntu Studio would be concerned with this. While we did cease building 32-bit […]

by eeickmeyer at June 24, 2019 08:47 PM

GStreamer News

GStreamer Rust bindings 0.14.0 release

A new version of the GStreamer Rust bindings, 0.14.0, was released.

Apart from updating to GStreamer 1.16, this release is mostly focussed on adding more bindings for various APIs and general API cleanup and bugfixes.
The most notable API additions in this release are bindings for gst::Memory and gst::Allocator as well as bindings for gst_base::BaseParse and gst_video::VideoDecoder and VideoEncoder. The latter also come with support for implementing subclasses and the gst-plugins-rs module contains an video decoder and parser (for CDG), and a video encoder (for AV1) based on this.

As usual this release follows the latest gtk-rs release, and a new version of the GStreamer plugins written in Rust was also released.

Details can be found in the release notes for gstreamer-rs and gstreamer-rs-sys.

The code and documentation for the bindings is available on the freedesktop.org GitLab

as well as on crates.io.

If you find any bugs, missing features or other issues please report them in GitLab.

June 24, 2019 08:00 PM

June 19, 2019

Linux – CDM Create Digital Music

VCV Rack hits 1.0; why you need this free modular now

Software modular VCV Rack just hit a major milestone – it’s now officially version 1.0, with polyphony, full MIDI, module browsing, multi-core support, and more. And since it’s a free and open platform, you don’t want to sleep on this.

VCV and developer Andrew Belt have hit on a new formula. Rack is free and open source on Mac, Windows, and Linux, and it’s free for developers to make their own modules. It also has tons of functionality out of the box – both from VCV and third-party developers. But then to support ongoing development, those developers offer some superb paid modules. Once you’re hooked, spending a little extra seems a good investment – because, well, it is.

All those modules… now seen in the new 1.0 visual browser.

Crucially, it’s a good deal for developers as well as users. Independent software developers, VCV included, are able to communicate directly with users, who in turn feel good about supporting the platform and community by spending some money. And hardware makers have a new way of reaching new audiences, as well as offering up try-before-you-buy versions of some of their modules. (Open source hardware makers like Mutable Instruments and Music thing were early adopters, but I hear some other names are coming.)

Maybe you’ve heard all this. But maybe you weren’t quite ready to take the plunge. With version 1.0, the case is getting pretty strong for adding Rack to your arsenal. Rack was appealing early on to tinkerers who enjoyed messing around with software. But 1.0 is starting to look like something you’d rely on in your music.

And that starts with polyphony, as shown by the developer of the VULT modules, which include many of my own personal favorites:

Rack 1.0

1.0 is really about two things – new functionality for more flexible use in your music, and a stable API for developers underneath that makes you feel like you’re using modules and not just testing them.

Mono- to polyphonic, on demand. Modules that want to support polyphony now can add up to 16 voices. Cables support polyphony. And the built-in modules have added tools for polyphonic use of course, too.

Polyphony, now a thing – and nicely implemented, both in UI and performance under the hood.

Multi-core accelerated engine. Adding polyphony, even on newer machines, means a greater tax on your CPU. There are a number of under-the-hood improvements to enable that in Rack, including multi-core support, threading, and hardware acceleration. This is also partly built into the platform, so third-party modules supporting Rack will get a performance boost “for free,” without developers having to worry about it or reinvent the wheel.

Adjustable performance: From the menu you can now adjust CPU performance based on whether you want lower CPU usage or more modules.

Adjust priority of the CPU based on your needs (more modules with higher CPU usage, or fewer modules but lower CPU).

MIDI out. You could always get MIDI into Rack, but now you can get it out, too – so you can use sequencers and modulation and so on to control other equipment or via inter-app MIDI routing, other software. There are three new modules – CV-GATE, CV-MIDI, and CV-CC. (VCV describes those as being suitable for drum machines, synths, and Eurorack and talks about hardware, but you could find a lot of different applications for this.)

Assign MIDI control easily. Previously, controlling Rack has been a bit of a chore: start with a MIDI input, figure out how to route it into some kind of modulation, assign the modulation. Many software racks work this way, but it feels a bit draconian to users of other software. Now, via the MIDI-MAP module, you can click a parameter onscreen and just move a knob or fader or what have you on your controller – you know, like you can do in other tools.

That will be essential for actually playing your patches. I can’t wait to use this with Sensel Morph and the Buchla Thunder overlay but… yeah, that’s another story. Watch for that in the coming days.

Meet the new MIDI modules, which now support output, mapping, and even MPE.

Numeric pad input as well as revised gamepad support. Now in addition to gamepads (which offer some new improvements), you can hook up numeric keyboards:

MPE support: MPE (MIDI Polyphonic Expression) now works with MIDI-CV. That makes Rack a fascinating new way of controlling MPE instruments.

Enter parameters manually. You can also now right-click a parameter and type in the value you want.

Browse modules visually. All the previous options for navigating your collection of virtual modules textually are still there – type module names, use tags, search by manufacturer or type. But now you also get a pretty visual browser so you can spot the module you want at a glance, and click and drag to drop modules into place. VCV isn’t the first computer modular to offer this – Softube has an awfully pretty browser, for one – but I find the Rack 1.0 browser to be really quick and easy. And it’s especially needed here as you quickly accumulate loads of modules from the Web.

Get new modules by sorting by build. This feature is actually on the VCV website, but it’s so important to how we work in Rack that it’s worth a mention here. Now you can search by build date and find the latest stuff.

Sort by build now on the plugins interface on the Web.

Move and manage modules more easily. You can now disable modules, force-drag them into place, and use a new, more flexible rack. The rack is also now infinite in all four dimensions, which is a bit confusing at first, but in keeping with the open-ended computer software ethos of software modular. (Take that, you Eurorack people who live in … like … normal physical space!)

You can also right-click modules to get quick links to plugin websites, documentation, and even source code. And you can see changelogs before you update, instead of just updating and finding out later.

Undo/redo history. At last, experiment without worry.

Parameter tooltips. No need to guess what that knob or switch is meant to do.

You can check out the new features in detail on the changelog (plus stuff added since 1.0, in case you live in the future and me in the past!):

https://github.com/VCVRack/Rack/blob/v1/CHANGELOG.md

Or for even more explanation, Nik Jewell describes what all those changes are about:

An unofficial guide to the Rack v1 Changelog

Getting started

Rack 1.0 will break compatibility with some modules, while you wait on those developers to update to the new API (hopefully). Andrew tells us we can run the old (0.6.x) and new Rack versions side by side:

To install two versions that don’t clash, simply install Rack v1 to a different folder such as “Program Files/VCV/Rack-v1” on Windows or “/Applications/Rack-v1” on Mac. They will each use their own set of plugins, settings, etc.

You can duplicate your Rack folder, and run the two versions side by side. Then you’re free to try the new features while still opening up your old work. (I found most of my previous patches, even after updating my modules, wound up missing modules. Rack will make the incompatible modules disappear, leaving the compatible ones in place.)

Right from the moment you start up VCV Rack 1.0, you’ll find some things are more approachable, with a new example patch and updated Scope. And for existing users, be prepared that the toolbar is gone, now replaced with menu options.

Here are some useful shortcuts for getting around the new release:

Now you can right-click a plug-in for an updated contextual menu with presets, and links to the developer’s site for documentation and more.

Double-click a parameter: initialize to default value

Right-click a parameter: type to enter a specific value.

Ctrl-click a connected input, and drag: clones the cable connected there to another port. (This way you can quickly route one output to multiple inputs, without having to mouse back to the output.)

Ctrl-E: Disables a module. (You can also choose the context menu.)

Ctrl- / Ctrl+ to zoom, or hold down control and use a scroll wheel.

Ctrl-drag modules. This is actually my favorite new feature, weirdly. If you control drag a module, it shoves other modules along with it into any empty space. It’s easier to see that in an animation than it is to describe it, so I’ll let Andrew show us:

Do check out the Recorder, too:

All the new internal modules to try out:
CV-MIDI
CV-CC
CV-Gate
MIDI-Map
Recorder

And developers, do go check out the migration guide.

Full information:

https://vcvrack.com/

The post VCV Rack hits 1.0; why you need this free modular now appeared first on CDM Create Digital Music.

by Peter Kirn at June 19, 2019 01:25 PM

June 17, 2019

Linux – CDM Create Digital Music

Sonarworks Reference 4.3: more headphones, features for calibrating your mixes

Sonarworks Reference 4.3 has a bunch of new features – more headphones, better performance, and it won’t blind you in a dark studio. The goal: make sure your mixes sound consistent everywhere. And with both high-end and consumer cans on the supported list, they seem to want everybody to give this a go.

I think the biggest challenge Sonarworks has here is that even I would have imagined calibration was something for engineers, but not necessarily producers. But once you hear the results, anyone can hear what this does. The thing is, headphones and studio monitors really aren’t flat. And especially outside of perfectly tuned studio environments, neither are working environments. Testing and calibration improves that enough that anyone can hear.

I’ve been using Sonarworks Reference religiously since the fall. The biggest challenge has been that there are two modes. One sounds really great, but adds a ton of latency. That’s especially rough if you want to work with calibration switched on all the time. The other is low-latency, but doesn’t sound as good. Those differences are, again, noticeable to anyone.

The big improvement in Reference 4.3 is to let you have both – with a mixed filter mode that operates with minimal latency but still delivers accurate results. That for me makes Reference way more useful. In fact, given this involved a ground-up rewrite, I’m surprised Sonarworks didn’t call this Reference 5. (It’s a free update, though!)

You also get new headphone profiles, which show both some high-end Beyerdynamic models but also the sort of consumer listening cans a lot of us use on the go with our smartphones and such. Those seem to target new users as well as ones traveling.

Beyerdynamic Custom Studio
Beyerdynamic MMX 300
Direct Sound EXTW37 Pro
Direct Sound Serenity Plus
Direct Sound Studio Plus
Marshall Major III
Marshall Major III Bluetooth
Marshall Monitor Bluetooth

More important than the addition of new individual models, though, they’ve added on-demand profile delivery, so you can add support inside the tool. There are already over a couple hundred of these, and they keep adding more.

There are some other improvements, too:

Dark mode – some people hate these; I love them, since I work in a lot of dim / late night environments

A better menu/tray bar, which is critical as you modify settings as you work

Integrated room measurement inside the Systemwide and plugin tools

Better virtual sound device performance (I need to test this across my Mac and Windows machines)

The little tool that gets you up and running when you start I already liked, and wrote about previously, but they’ve enhanced that even more

The new tool for getting started. Before.

After.

Previously, I did some deep dives into this software and answered reader questions:

What it’s like calibrating headphones and monitors with Sonarworks tools

Your questions answered: Sonarworks Reference calibration tools

I need to follow up with them on how Linux support is coming, as CDM was the first to write about that and some of you I know were interested (as am I)!

Also since I last covered Reference, Sonarworks has started offering a bundle with pre-calibrated headphones. These theoretically deliver more precise calibration than what you’d get from any profile, since they’ve tested the actual harder. It’s pricey, because it includes the already-expensive HD650 headphones from Sennheiser.

But those are terrific headphones, and headphones are crucial to precise mixing and mastering. I imagine these would be a great investment for a producer or especially studio or engineer wanting to invest in a full calibration package at once. (Feel free to shout about whether Sennheiser or Beyerdynamic are better in comments, though!) In fact, I think if you’re thinking of buying the HD650s, you should spring for the bundle.

The bundle, with Sennheiser HD650.

I have talked to more producers about this tool than engineers (though my mastering engineer collaborator is a believer), so I would be interested to hear about that use case more.

And yes, this is another member of our music tech industry now located in Riga, Latvia, along with Gamechanger, Erica Synths, and others. It’s a surprising new hotbed.

The post Sonarworks Reference 4.3: more headphones, features for calibrating your mixes appeared first on CDM Create Digital Music.

by Peter Kirn at June 17, 2019 01:56 PM

June 12, 2019

GStreamer News

GStreamer Conference 2019 announced to take place in Lyon, France

The GStreamer project is happy to announce that this year's GStreamer Conference will take place on Thursday-Friday 31 October - 1 November 2019 in Lyon, France.

You can find more details about the conference on the GStreamer Conference 2019 web site.

A call for papers will be sent out in due course. Registration will open at a later time. We will announce those and any further updates on the gstreamer-announce mailing list, the website, and on Twitter.

Talk slots will be available in varying durations from 20 minutes up to 45 minutes. Whatever you're doing or planning to do with GStreamer, we'd like to hear from you!

We also plan to have sessions with short lightning talks / demos / showcase talks for those who just want to show what they've been working on or do a mini-talk instead of a full-length talk. Lightning talk slots will be allocated on a first-come-first-serve basis, so make sure to reserve your slot if you plan on giving a lightning talk.

There will also be a social event again on Thursday evening.

There are also plans to have a hackfest the weekend right after the conference on 2-3 November 2019.

We hope to see you in Lyon, and please spread the word!

June 12, 2019 02:00 PM

June 08, 2019

digital audio hacks – Hackaday

C++ Reverbs From A Matlab Design

The guitar ‘Toing’ sound from the ’70s was epic, and for the first time listener it was enough to get a bunch of people hooked to the likes of Aerosmith. Reverb units were all the rage back then, and for his DSP class project, [nebk] creates a reverb filter using Matlab and ports it to C++.

Digital reverb was introduced around the 1960s by Manfred Schroeder and Ben Logan. The system consists of essentially all pass filters that simply add a delay element to the input signal and by clubbing a bunch together and then feeding them to a mixer. The output is then that echoing ‘toing’ that made the ’80s love the guitar so much. [Nebk]’s take on it enlists the help of the Raspberry Pi and C++ to implement the very same thing.

In his writeup, [nebk] goes through the explaining the essentials of a filter implementation in the digital domain and how the cascaded delay units accumulate the delay to become a better sounding system. He also goes on to add an FIR low pass filter to cut off the ringing which was consequent of adding a feedback loop. [nebk] uses Matlab’s filter generation tool for the LP filter which he includes the code for. After testing the design in Simulink, he moves to writing the whole thing in C++ complete with the filter classes that allows reading of audio files and then spitting out ‘reverbed’ audio files out.

The best thing about this project is the fact that [nebk] creates filter class templates for others to play with. It allows those who are playing/working with Matlab to transition to the C++ side with a learning curve that is not as steep as the Himalayas. The project has a lot to learn from and is great for beginners to get their feet wet. The code is available on [GitHub] for those who want to give it a shot and if you are just interested in audio effects on the cheap, be sure to check out the Ikea Reverb Plate that is big and looks awesome.

by Inderpreet Singh at June 08, 2019 08:00 AM

April 15, 2019

KXStudio News

Carla 2.0.0 is finally here!

After many years, Carla version 2.0.0 is finally here!

Carla is an audio plugin host, with support for many audio drivers and plugin formats.
It has some nice features like automation of parameters via MIDI CC (and send output back as MIDI too) and full OSC control.

Version 2.0 took this long because I was never truly happy with its current state, often pushing new features but not fully finishing them.
So the "solution" was to put everything that is not considered stable yet behind an experimental flag in the settings.
This way we can have our stable Carla faster, while upcoming features get developed and tagged as experimental during testing.

Preparations for version 2.1 are well under way, a beta for it will be out soon.
But that is a topic for another day.

Changes since 2.0-RC4

  • Fix missing argument in note-on/off osc example
  • Fix word-wrap in add-plugin dialog
  • Fix Windows README.txt line endings
  • Build windows binaries with -mstackrealign
  • Don't show side panel in carla-control
  • Show "Label/URI" instead of just "Label"
  • Keep application signals alive (so Ctrl+C works even while engine is closed)
  • Update copyright year

Downloads

To download Carla binaries or source code, jump on over to the KXStudio downloads section.
Carla v2.0.0 is available pre-packaged in the KXStudio repositories and UbuntuStudio backports, plus on ArchLinux and Ubuntu since 19.04. On those you can simply install the carla package.
Bug reports and feature requests are welcome! Jump on over to the Carla's Github project page for those.

Videos

There is no manual or quick-start guide for Carla yet, apologies for that.
But there are some videos of presentations I did regarding Carla's features and workflows, those should give you an introduction of its features and what you can do with it:

@ Sonoj 2017

@ LAC 2018

by falkTX at April 15, 2019 06:17 AM

March 22, 2019

KXStudio News

Changes in KXStudio repos, regarding Carla and JACK2

This is a small notice to everyone using Carla and JACK2 with the KXStudio repos.

First, in preparation for Carla 2.0 release, the (really) old carla package is now the new v2.0 series, while carla-git now contains the development/latest version.
If you are not interested in testing Carla's new stuff and prefer something known to be more stable, install the carla package after the latest updates.

Second, a change in JACK2 code has made it so a restart of the server is required after the update.
(but for a good reason, as JACK2 is finally getting meta-data support; this update fixes client UUIDs)
If you use jackdbus (likely with KXStudio stuff), you will need to actually kill it.
If that does not work, good old restart is your friend. :)

One important thing to note is that the lmms package now conflicts with the carla-git one.
This is because some code has changed in latest Carla that makes v2.0 vs development/latest ABI-incompatible.
In simpler terms, LMMS can only either be compiled against the stable or development version of Carla.
The obvious choice is to use the stable version, so after the updates if you notice LMMS is missing, just install it again.
(If you have carla-git installed, carla will be installed/switched automatically)

I tried to make the transition of these updates as smooth as possible, but note that you likely need to install updates twice to complete the process.

In other news, we got a new domain!^-^)/
Also Carla v2.0 release date has been set - 15th of April.
Unless a major issue is found, expect a release announcement on that day.
See you soon then! ;)

by falkTX at March 22, 2019 12:58 AM

February 23, 2019

The Ardour Youtube Channel is here

@paul wrote:

ardour.org is pleased to announce a new youtube channel focused on videos about Ardour.

We decided to support Tobiasz “unfa” Karon in making some new videos, based on some of the work he has done in other contexts (both online and at meetings). unfa’s first video won’t be particularly useful for new or existing users, but if you’re looking for a “promotional video” that describes what Ardour is and what it can do, this may be the right thing to point people at.

In the near-term future, unfa will be back with some tutorial videos, so please consider subscribing to the channel.

Thanks to unfa for this opening video, and we look forward to more. If people have particular areas that they’d like to see covered, mention it in the comments here (or on the YT channel).

Posts: 21

Participants: 10

Read full topic

by @paul Paul Davis at February 23, 2019 06:53 PM