Linux-audio-user October 2015

linux-audio-user@lists.linuxaudio.org

70 participants
59 discussions

[LAU] OT? Downloaded youtube videos with subtitles

by Ivan K

I was very excited to find a video of the complete Tristan and Isolde on YouTube recently, complete with English subtitles. I used the youtube-dl utility to grab the video, but when I began playing the copy on my hard-drive with totem, to my horror, the English subtitles were not there! To repeat, the subtitles are on youtube.com but not in the .webm file that I downloaded with youtube-dl. Can someone coach me how to download a version with the English subtitles? Or are there subtitles in my downloaded version and totem is just not playing them? Thank you for your help. P.S. On the totem menu under View, there is a command called Subtitles but this prompts me for another file. Is there a subtitle file in addition to the video file that I need to download from youtube? Thanks again.

10 years, 3 months

Re: [LAU] Migrating from Garage Band to Free Software: Choices?

by Ralf Mardorf

On Tue, 27 Oct 2015 11:43:57 -0430, Luigino Bracci wrote: >Well, GarageBand can help the amateur musician wanting to do a song >for a TV commercial for a few bucks, but the musician dreaming to >create a new, personal style and change the world needs some other >type of tools. My impression after using GarageBand just a few minutes is, that it can be used to easily get a result that deeply impress listeners. But how many really different songs can you produce using the same sounds by the same playing techniques? I'm using tools like Ardour, Qtractor etc. were it takes much longer to get a result that deeply impress listeners and perhaps the result won't impress a listener at all, but the result would be what I played, nothing that is restrained by provided patterns. >But, as I understand, creating new, free soundfonts (free as in >freedom) can help solve the problem... am I wrong? Yes and no. It depends on what you're missing. Sometimes you need better soundfonts, but sometimes you can't simply play the samples, you need to add effects and/or edit the MIDI data, or you need special instruments to play the samples. There are very good MIDI drum sets available to play drum samples, instead of using a keyboard. IOW which sounds you used with Linux were not as good, as the sounds you used with GarageBand? Perhaps somebody could recommend a good soundfont or effect you could use with Linux, or a Linux helper tool.

10 years, 3 months

[LAU] send a midi CC signal to my midi controller from bash

by Athanasios Silis

hi all I have a BCR2000 and I want to init some controllers to some values. init is done by a bash script so I would like to set the value in a bash script and send it out to the BCR2000. the controller shows up on jack , under a2j , but i am not sure which program - if any - exists out there that can send this midi signals. thank you in advance for your help!

10 years, 3 months

[LAU] mcpdisp 0.0.5 released

by Len Ovens

The Mackie Control Display Emulator has a new release 0.0.5. This adds the scribble display to control surfaces that use the Mackie Control Protocol but do not have their own display such as the BCF2000 and midikb. mcpdisp presents a jack midi port that will accept mackie control protocol display messages that would normally appear on the surface "scribble strip" and displays them on the screen. The strip LEDs and meters are displayed as well. New things: * Fixed INSTALL file for no mcpdisp.sh. * Added Assign display. * Added timecode/beats display. * Added Strip meters. * Added command line parameters for help, version, master and time. * Made window title more descriptive. * jack client name shows mcpdisp-ext if no -m * Start work on global buttons. * Finished Transport LEDs and flip, assign and View LEDs. * Set MIDI in port to type Terminal/Physical. * Set Display in to accept whole display of text at a time. * Move midi parsing out of real time. * Only update time/beats when new time/beat data comes in. Source is available from: https://github.com/ovenwerks/mcpdisp Home page: http://www.ovenwerks.net/software/mcpdisp.html -- Len Ovens www.ovenwerks.net

10 years, 3 months

[LAU] re Zoom R16

by reSet Sakrecoer

Hi all! I found this old discussion about the Zoom R16 in the archive of LAU. http://linuxaudio.org/mailarchive/lau/2012/3/14/188926 Strangely, in that archive there is a missing reply from Mr. Brett McCoy. (You can find the missing one a the bottom of this archive: http://linux-audio.4202.n7.nabble.com/Zoom-R16-td7748.html ) Mr. McCoy claims to have enabled the Zoom R8 (yes, there is quite a difference between r16 and r8) as a multi-input soundcard for ardour and also as a control surface in 12.04 64bits. There is no information as to which driver is being in use in his post. And searching the web only leads me to various WIP to get the R16 running on linux. My question is, has anyone got any news about this device and a possible drivers? Specifically to Mr. Brett McCoy: what driver did you use to make jack aware of your r8? Thank full for any hints, yours, -- Set Hallström AKA reSet Sakrecoer http://sakrecoer.com

10 years, 3 months

[LAU] Boss BR-80 (SD card question)

by Michael Nelson

Hello all, I'm thinking of getting a Boss BR-80, which is a little portastudio-type device. I've found a couple of old threads about using one as a USB soundcard, which seems to resolve one of my queries, but I have another. I'd like to be able to plug the SD card into my computer, and save the audio files, so I can edit and mix externally. I think that the device will master to wave file, but saving individual tracks seems to require a Windows conversion utility. That is of no use to me. I don't even know what filesystem is on the SD card. Does anyone have one of these? Could someone shed some light on this for me? If not, I might buy one anyway, and report my findings back here. Thanks all, Michael

10 years, 3 months

[LAU] killling zombie jack

by Atte

Hi Old problem here, decided to try to get to the bottom of this. Normally I start jack from qjackctl and mostly everythings fine. However sometimes "something" makes jack hang and I cannot kill it, so I have to reboot :-( When started proberly from qjackctl the process is called jackd. If I forget to start jack before renoise and renoise is configured to use jack, renoise starts its own jack. This is called jackdbus. It seems I have both "jackd", "jackd2" and "jackd2-firewire" installed, probably because I was testing which one worked better with my new kernel. 1) How can I kill-kill jack when it's hanging? 2) What's the prober way of having two versions of jack installed, making sure I'm *always* using one version as default (specifically, how to make qjackctl and renoise use the same version)? Sorry if this is all too obvious... NB: Running debian jessie + liquorix sid Cheers -- Atte http://atte.dk http://a773.dk

10 years, 3 months

[LAU] Music made with linux: a773 - "is she"

by Atte

Hi New track out, "is she", hope you enjoy! Made in renoise :-) https://soundcloud.com/a773/is-she Cheers -- Atte http://atte.dk http://a773.dk

10 years, 3 months

[LAU] muse registration fails

by Menno

Hi, i have tried several times to register into the forum of the Muse sequencer, every time it tells me: An error occurred with the image verification. Please try again. So i can never register. (and yes, i have read and filled in the Captcha correctly :)) Any ideas? -- View this message in context: http://linux-audio.4202.n7.nabble.com/muse-registration-fails-tp97616.html Sent from the linux-audio-user mailing list archive at Nabble.com.

10 years, 3 months

[LAU] Rosegarden 15.10

by Will Godfrey

Just seen this and thought it might be of interest. The Rosegarden team is pleased to announce the release of version 15.10 of Rosegarden, an audio and MIDI sequencer and musical notation editor for Linux. One tester comments, "You'll be pleased to know that this puts Rosegarden ahead of all the other sequencers I've tried for all CCs including bank changes, program changes and NRPNs." http://www.rosegardenmusic.com/ With this major bugfix release, Ted Felix untangled a very old problem with instrument parameters that stumped quite a few developers over the years. Tito Latini joined the project briefly, and went on a bit of a rampage, fixing bug after bug. Yves got in on the effort, and contributed several important fixes. Even Michael wrote a little code here and there. This is one of the best releases we've turned out in years, and we strongly encourage everyone to upgrade immediately! BUG FIXES * Fix various bugs with control rulers: control items outside the segment, add and/or move control items after horizontal zoom, recorded MIDI CC after horizontal zoom * Fix MIDI export with events before the bar 1 of the composition (bug 1258) * Fix importing banks from soundfonts (bug 1417) * Fix double note-offs in playback (bug 1427) * Fix split points during MIDI import (bug 1429) * Fix scrolling while drawing loop/range in notation/matrix views (bug 1222) * Also fixed scrolling for control items in notation view * Fix noteoffs in loop mode (bug introduced in r14092) * Fix midi input after r14095 * Fix problem with sustaining notes while adding notes with the pencil tool * Also avoids moving playback position in playback mode, allowing editing of a loop in real-time * Fix subordering of grace notes added before Indication events (bug 1215). If we add a grace note before an Indication event, the event of the grace note precedes the indication. If we add an Indication event where there is a grace note, the inserted event precedes the grace note * Fix drawing of the control ruler in notation view after horizontal zoom * No weird message with synth plugin and pedal sign in notation editor (bug 1424) * Ignore duplicated noteoffs immediately. Also avoid a useless event-type zero (SND_SEQ_EVENT_SYSTEM) when a noteoff is duplicated * Fix event scheduling in DSSI synth (bug 1109). Before the bug fix, an immediate event could occur after a future event and if the immediate event (realtime) was a note, it was time shifted and shortened (also with zero duration) * Fix black space beside track headers (bug 1441) * Fix persistent invisibility on rests (bug 633) * Fix several interrelated bugs involving performance vs. display duration causing cut and paste operations on notation quantized notes to behave strangely (bug 1440) * Fix erroneous split of rest when inserting triplets (bug 980) * Fix excessive warning dialogs during step recording (bug 1445). Avoid step recording unless the edit view is the active window. Fail silently when inappropriate tool is selected, rather than bombarding user with cryptic errors * Fix DSSI synth used with unsuitable channel setup after stop-recording * CMI: Fix potential memory corruption * Fix segfault if a Segment is not in a Composition * Use getGreaterDuration() where it is opportune (reduces duration-related glitches) * Fix selection drawing after mouse-button release with matrix-velocity tool. * Fix bug #1446 First step: A segment which is not linked with a still existing segment is no longer flagged as "linked" when saved in a .rg file. Second step: A segment previously linked then left alone when others segments have been deleted is now copied into the clipboard as a plain segment and no longer as a linked one * Fix segfault in ~EventSelection (bug 1449) * Fix copying a linked segment with arrow tool and Ctrl+move (bug 1450) * Fix settings memory in the quantize dialog (bug 1447). (It turns out this had been broken for five years!) * Fix rests after "Remove Notation Quantization" command * Fix duration in "Fix Notation Quantization" command * Event quantize command doesn't change segment duration * Fix "Open hand cursor is obnoxious" (bug 1452) * Control rulers handle volume and expression controllers properly (bug 1451) * Limit event duration in "Fix Notation Quantization" command * Normalize rests in "Fix Notation Quantization" command * Fix the region to normalize the rests during the quantizazion * Fix the position of the last micro event of a segment * Ignore quantized events moved outside the segment * Don't move events outside a segment in notation view * Update selection drawing after editing in velocity ruler * Update selection drawing in matrix view when a segment status is to refresh * Use MidiBank::partialCompare() instead of op== * MidiBank::operator==() is a full comparison of all fields as is proper. partialCompare() compares all fields except name (bug 1443) * Discover and fix two more bugs similar to Bug #1443 * Fix notation time and duration in linked segment (bug 1453 and numerous related, unreported bugs) * Constant thickness for a selection in matrix view * Optimize the range to normalize the rests after quantization * "Paste events" command doesn't change the time/duration of a segment * Fix snap to grid in matrix view * Fix rare track height issue when recording; if recording caused the track heights to change, and stopping also caused the track heights to change, the height of the TrackButtons would get out of sync * MidiFile: Improve alien chunk handling; findNextTrack() now implements alien chunk skipping as recommended by the MIDI spec * MidiFile: Improve header chunk handling; Also reduced the scope of some variables in parseTrack() to make the code a little easier to follow * Fix 1455 and other related problems with LilyPond complex alternate endings * Fix broken MIME type so our files display in graphical file managers with our icons again (fixes 1454) * Fancy repeat endings should now be correctly handled in LilyPond export * Fix translation of error messages from LilyPondExporter * Fixes bug #1439, MIDI Import Modifies Bank Selects. Now,all bank selects and program changes are imported as-is. Once a track is imported, the events at time zero are checked to see if any of them can be moved to the Instrument configuration NEW FEATURES * Velocity ruler enhancement: Change the velocity items of the notes selected in matrix or notation view; Without selection, pick and drag a velocity item * Improve MIDI file conductor track handling on import (r14227) * Change track/segment naming: Previously, tracks created from different channels in a MIDI track would be named "Imported MIDI". Now, they have the same name as the MIDI track they came from. Previously the MIDI instrument name was used to name the segments. Now it is added to the end of the track name in parens. Segments are now named after their tracks. If no names are found, we fall back on the general MIDI program names. OTHER PEOPLE WHO CONTRIBUTED TO ROSEGARDEN DEVELOPMENT * Tito Latini -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song.

10 years, 3 months

2026

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 October 2015