I've switched this back to confirmed since upstream is aware of the
issue and the exact patch to the kernel that is required to fix it has
been provided in this bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed in Ubuntu 16.10 with kernel 4.8.0-30.
ted@teds-laptop:~$ uname -a
Linux teds-laptop 4.8.0-30-lowlatency #32-Ubuntu SMP PREEMPT Fri Dec 2 04:38:54
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
ted@teds-laptop:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:
Upstream dev here.
There is a bug in the ALSA drivers that causes the playback problem you
describe. Kernel bug 177571 is the one:
https://bugzilla.kernel.org/show_bug.cgi?id=177571. That patch needs to
be added to Ubuntu's kernel to fix this.
The relevant patch in the linux kernel 4.8.y tree:
Upstream dev here.
There is a bug in the ALSA drivers that causes the playback problem you
describe. Kernel bug 177571 is the one:
https://bugzilla.kernel.org/show_bug.cgi?id=177571. That patch needs to
be added to Ubuntu's kernel to fix this.
The relevant patch in the linux kernel 4.8.y tree:
On 12/08/2016 05:16 PM, Ted Felix wrote:
>The Ubuntu kernel team would be most interested in the kernel bug
> report here:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=177571
>
>Let us know if you decide to escalate with Ubuntu.
Looks like someone else bea
** Summary changed:
- rosegarden 16.06 plays only first note, locks up PC when trying to use HP
timer
+ rosegarden 16.06 plays only first note, locks up PC when trying to use HR
timer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 12/09/2016 05:30 PM, D. Michael McIntyre wrote:
> On 12/09/2016 09:18 AM, Ted Felix wrote:
>>Well then maybe it's just me. Let's hope so.
> It definitely does not appear that this issue is a serious show stopper.
> I imagine most people today build with Qt5 anyway.
Ye
On 12/08/2016 11:22 PM, Aere Greenway wrote:
> I ran the test on my Ubuntu Unity system (64-bit), Athlon, touch-screen,
> and was unable to reproduce the problem - the LEDs look fine in every case.
>
> I'm pretty sure that system was upgraded from 16.04.
Well then maybe it's just me. Let's
On 12/08/2016 06:22 PM, Aere Greenway wrote:
> I tried it on fresh-install (and updated) Lubuntu 16.10 system, and did
> not observe the LEDs problem (both with Fast and Safe graphics.
Thanks for running all these tests. It's probably something very
specific to Ubuntu 16.10 with GNOME/Unity.
On 12/08/2016 11:57 AM, Aere Greenway wrote:
> On all of my Ubuntu 16.10 testing (on both newly-installed, and upgraded
> systems), I didn't observe the problem with the LEDs.
Did you switch to "Safe" graphics mode in the preferences?
> The problem where it won't play, was in common with all
On 12/07/2016 02:21 PM, D. Michael McIntyre wrote:
>> 2. The LEDs look really bad. They've become a single tiny point.
> What Qt are you building against? I can get a binary distribution of
> that version and test stuff like that without a distro upgrade.
OK, I've got a test case for you.
On 12/07/2016 04:12 PM, Ted Felix wrote:
> On 12/07/2016 10:30 AM, Ted Felix wrote:
>> 2. The LEDs look really bad. They've become a single tiny point.
>Should be real easy to fix.
Maybe not. Looks like it's a Qt4 issue. In Qt5, it works fine even
after deleting the Ros
On 12/07/2016 10:30 AM, Ted Felix wrote:
> 2. The LEDs look really bad. They've become a single tiny point.
I had a hunch this was something to do with the Rosegarden.conf. If
I delete my Rosegarden.conf, the LEDs become points. If I then change a
setting, like "Start JACK autom
On 12/07/2016 02:21 PM, D. Michael McIntyre wrote:
>> 2. The LEDs look really bad. They've become a single tiny point.
> What Qt are you building against? I can get a binary distribution of
> that version and test stuff like that without a distro upgrade.
Looks like it's Qt 4.8.7.
Ted.
I've just finished upgrading to Ubuntu 16.10 and I've noticed a
couple of issues so far.
1. The ALSA time bug is here, so playback doesn't work. Bug #1537.
2. The LEDs look really bad. They've become a single tiny point.
Might be good to postpone 16.12 until I can do a little digging.
On 11/21/2016 06:49 PM, D. Michael McIntyre wrote:
> Now that my adventures have forced me to go play with software on other
> platforms, I thought I'd pop in and state that Rosegarden's auto-scroll
> behavior is smooth as a newborn kitten, and Ted Felix hit a home run
> with that
On 11/06/2016 07:03 PM, D. Michael McIntyre wrote:
> The way it was supposed to work, when you imported MIDI it would try to
> fuzzy match you with "General MIDI Device" and try to assign that to a
> playable port.
That sounds simple. I'll keep it in mind when I get there.
> I remember the
On 11/06/2016 10:40 AM, John A wrote:
> The only hiccup now is that I get a weird doubling with drum programs,
Sounds like a "Local On"/"Local Off" problem. Though with only drum
programs, that seems unusual. Check out this article on thru routing.
It might help:
On 11/05/2016 10:30 AM, D. Michael McIntyre wrote:
> Basically I just work and sleep now, and it doesn't seem likely I will
> ever contribute meaningfully again. My involvement here seems to have
> run its course.
Thank you for continuing to do the releases. That's quite
meaningful. Along
On 10/25/2016 10:06 PM, John A wrote:
> I have managed to get the data to record from the
> Korg into RG, but still not in sync
In what way is it not in sync? Timing across tracks? Something else?
> From reading the handbook, it seems that setting each channel to
> 'Receive External'
On 10/15/2016 02:00 PM, Aere Greenway wrote:
> All of the several '.rg' files that cause Rosegarden to crash when
> loading them, can be loaded and played using version 15.12 of
> Rosegarden. But when you try to load them with version 16.06, a crash
> occurs.
Thanks for catching this. It
On 09/24/2016 07:37 AM, David Faure wrote:
> On vendredi 23 septembre 2016 23:20:26 CEST D. Michael McIntyre wrote:
>> I think the .qm
>> files are the generated translations, and they DO want to be in the
>> resource bundle, while the .ts files do NOT want to be there.
> Correct.
OK, I see
On 09/09/2016 07:33 PM, Michael wrote:
> cmake .. -DCMAKE_INSTALL_PREFIX=[PREFIX] -DCMAKE_BUILD_TYPE=[Debug]
The square brackets mean these things are optional. You're not
supposed to type in the square brackets. Try deleting your "build"
directory (rm -rf build), recreate it (mkdir
On 09/01/2016 08:57 AM, Yves Guillemot wrote:
> Done: Tickets #1534 and #1533.
> I included a recipe to create a sample file and BTW I found what looks like
> another bug.
Good stuff. Thanks.
Ted.
--
On 08/30/2016 09:56 AM, Yves Guillemot wrote:
> BTW there is something which looks like a RG bug here:
...
> I'll write a ticket about it.
Please do. Be sure to include a sample file. I have a feeling
you've found a case I missed.
Ted.
On 08/25/2016 03:28 PM, Yves Guillemot wrote:
> Here there is something weird: Why is GM Recorder used in place of flute ?
> Why English Horn in place of oboe ? Why Piccolo in place of clarinet ? etc...
>
> This looks like a bug somewhere:
>Recorder is #75 in GM and Flute is #74
>English
I've been sitting on these until the release was done. Changes are
mainly in the Track Parameters box. It's mostly cleanup, so there
should be minimal change to the TPB's usual behavior. Things to test:
Serialization of CollapsingFrame's state has been standardized
([r14714]
I've been cleaning up TrackParameterBox and I'm looking right now at
the "Preset" field in the "Create segments with" section. This field is
enabled/disabled to indicate changes have been made. However, on my
system, the difference between enabled and disabled is very subtle. So,
I was
On 06/25/2016 09:01 AM, Ted Felix wrote:
> I can't launch the Document Properties dialog starting with 16.02.
Fixed in r14693. Please test.
Ted.
--
Attend Shape: An AT Tech Expo July 15-16. Meet us at AT P
On 06/28/2016 02:09 PM, Ted Felix wrote:
> After some digging, the problem has gone away. Probably the updates
> I just did today. linux-libc-dev was included in the bunch.
And now it's back. Argh! More digging...
On 06/26/2016 06:48 PM, Ted Felix wrote:
> I dodged the bullet this time. The problem was introduced in r14628.
>I'll open a bug report and toss this one up to David
Bug report opened:
https://sourceforge.net/p/rosegarden/bugs/1525
On 06/26/2016 11:21 AM, D. Michael McIntyre wrote:
> Hit play, hit stop, play button stays pushed. Record button staying
> pushed. Lots of GUI out of sync with the transport problems everywhere.
>Seems connected to the new solo functionality, maybe.
I dodged the bullet this time. The
On 06/26/2016 11:21 AM, D. Michael McIntyre wrote:
> Hit play, hit stop, play button stays pushed. Record button staying
> pushed. Lots of GUI out of sync with the transport problems everywhere.
>Seems connected to the new solo functionality, maybe.
I did have to update
On 06/25/2016 08:00 PM, D. Michael McIntyre wrote:
> It works fine here. To be clear, Composition -> Edit Document
> Properties works fine here.
Figures.
Feels like a gcc improvement is highlighting a coding subtlety. Or
perhaps just a valid shift in interpretation of the spec. Like
I can't launch the Document Properties dialog starting with 16.02.
Probably a show-stopper for the next release if it's not just me.
I'll have a closer look. Here's the debug output:
[RosegardenMainWindow] RosegardenMainWindow::slotEditDocumentProperties
WARNING: Rosegarden::Exception:
On 06/24/2016 12:53 PM, Ted Felix wrote:
> Try doing the same with LibreOffice. E.g. open a Writer document,
> then do a shutdown without closing the app. Do they leave a lock file
> around?
The answer is "yes". LibreOffice does the same thing. At least we
are
On 06/17/2016 05:12 PM, Lorenzo Sutton wrote:
> And here is an example .rgd file generated from the default banks
> installed (in /usr/local/share/yoshimi/banks in my case):
>
> https://github.com/lorenzosu/rosegarden_yoshimi_banks/blob/master/yoshimi.rgd?raw=true
I'm looking at this right
I've just finished implementing a new track "Archive" feature. See
Feature #418:
https://sourceforge.net/p/rosegarden/feature-requests/418/
Grab the latest svn and test if you can.
Setting a track as "Archived" is essentially a deeper mute that isn't
affected by mute/unmute all.
The archive feature is ready to go. Should I go ahead and push the
commits now, or wait until after the 16.06 delivery?
Ted.
--
Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San
Francisco, CA to
* Archive mode? Is this going to make it in?
I've just posted an update to the feature tracker.
https://sourceforge.net/p/rosegarden/feature-requests/418/
Let me know if you want me to push what I have. It's ready. I was
just going to do some cleanup on the Led code. It can wait.
On 06/17/2016 05:12 PM, Lorenzo Sutton wrote:
> Well here's my go at it:
Thanks. We'll have a look and add it to Rosegarden's collection of
device files.
Ted.
--
What NetFlow Analyzer can do for you? Monitors
On 06/15/2016 06:51 PM, Abrolag wrote:
> On the next startup, if I start Yoshimi first, Rosegarden connects and resets
> most of the controls to (now) wrong values. Changing bank root was a
> particular
> problem (now pretty much resolved) because it then meant Yoshimi was pointing
> to
>
On 06/15/2016 10:40 AM, Abrolag wrote:
> On Mon, 16 May 2016 20:39:59 -0400
> Ted Felix <t...@tedfelix.com> wrote:
>> Try the latest with the bank and program checkboxes unchecked and let
>> me know if this part is now fixed. It should be. If not, it should be
&
On 06/15/2016 09:48 AM, Vegard Svanberg wrote:
> Simply put, when I record using my keyboard, it appears that Rosegarden
> (or something) feeds the recorded MIDI immediately back to the keyboard.
It is supposed to do that. You need to turn "Local" off on the K-11.
With Local Off, you can
Just finished implementing solo LEDs. If you can, please grab the
latest svn and test. Quick start:
Clicking on a solo LED puts it in solo. Shift-clicking adds another
track to solo. The solo button on the transport and the editors is a
quick way to solo the selected track. The solo
On 05/21/2016 02:19 AM, Mike Rose wrote:
> But still - is there no way the ruler can be increased vertically?
It certainly can. If you don't mind making modifications to the
code, building, and testing, then try this:
- In TrackEditor::init() increase barButtonsHeight to 35 pixels.
- In
On 05/16/2016 04:25 PM, Lorenzo Sutton wrote:
> No wait! I still want to be able to mess with volume and controllers
> (knobs in tracks and automation in the matrix).
> What I would like to exclude is sending them when the file *loads*,
Ok. I'll have to think some more about that. It's
On 05/16/2016 09:44 AM, Lorenzo Sutton wrote:
> Hi Ted, what do you mean with controllers removed? You mean explicitly
> removing them from the device set-up? This (I think) would disable use
> of controller rulers (as reverse to adding controllers which enables
> rulers) and that would be rather
On 05/13/2016 06:06 AM, Lorenzo Sutton wrote:
> Does this solve the problem where if I open yoshimi (or it is already
> opened) and load a state file *before* opening file in rosegarden,
> rosegarden will fire a set of program changes which effectively mangle
> my yoshimi state?
Probably not.
On 05/04/2016 01:35 PM, Abrolag wrote:
>> https://sourceforge.net/p/rosegarden/bugs/1516/
> Any chance of some progress on this. I've just tried build 14635 and the
> problem is still there. I've actually reverted to 14235 on my DAW :(
Should have a fix in a week or two. This is proving to be
On 04/26/2016 09:46 AM, David Faure wrote:
> So the "sequencer" is the thing that plays an entire piece in the background ?
Yes.
> I notice, though, that with --no-sequencer,
> RosegardenDocument::initialiseStudio()
> is not called. Is it still OK to play sounds then?
Probably not. In
On 04/26/2016 08:29 AM, David Faure wrote:
> Do I understand correctly that the --no-sequencer command-line option is
> supposed to disable
> any sound output?
I don't think so. I think it's supposed to disable the sequencer thread.
> From what I can see, extending the selection
On 04/18/2016 09:19 AM, Silas Mortimer wrote:
> This is particularly a problem in that I'd like to set them up to run
> together (leaving blank patterns in Hydrogen while the part in
> Rosegarden plays), but when I try to set Rosegarden's timing to
> JACK-determined, it goes all wonky.
I'm not
On 04/18/2016 09:19 AM, Silas Mortimer wrote:
> To get a more or less similar beat
> setting, I have Rosegarden set up at 180 BPM, while Hydrogen is down
> to 120 BPM.
That's a ratio of 2/3. Check the time signatures. Are they the same?
Ted.
On 03/31/2016 09:45 AM, Yves Guillemot wrote:
> There is a small issue (repeatedly occurring with RG) about UTF8 garbage in
> the displayed lock file name when the .rg file uses non ASCII characters (I
> did
> the first test with a file name containing a diacritic).
I'm testing with
On 03/31/2016 09:45 AM, Yves Guillemot wrote:
> Then I tried a less obvious case:
>
> - Create a new composition in RG and save it in a file. Keep RG open.
> - Create again a new composition in another RG instance
> - Try to save the last composition in the same file as fhe first one.
> =>
On 03/31/2016 09:45 AM, Yves Guillemot wrote:
> An other (very) small problem is the "Could not lock file" message which may
> be
> unclear for some users.
> An improvment should be to add in the popup a first sentence explaining that
> two different RG instances try to access the same file.
On 03/31/2016 09:45 AM, Yves Guillemot wrote:
> Then I tried a less obvious case:
Thanks for finding that. I'll have a look.
> There is a small issue (repeatedly occurring with RG) about UTF8 garbage in
> the displayed lock file name when the .rg file uses non ASCII characters (I
> did
>
On 03/21/2016 08:16 AM, D. Michael McIntyre wrote:
> Anyway, this is pretty much a thing now as far as I can see. Nice work
> so far!
Thanks for playing with it. There are some more improvements now, os
it might be a little better. I'll see if I can reproduce any of these
things you've
On 03/17/2016 05:21 AM, Bric wrote:
> what is the status of NRPN support in RG ?
There is no plan to support it since no one has opened a feature request.
https://sourceforge.net/p/rosegarden/feature-requests/
Ted.
On 03/18/2016 05:58 AM, Bric wrote:
> On 03/17/2016 12:27 PM, Abrolag wrote:
>> It *is* effectively supported :)
>> Just break it down into individual controller values.
> Yup. I just saw that - Julie S. has a post from 2008 about using
> controller the way Abrolag suggest... Except I don't see
On 03/07/2016 06:22 PM, Bric wrote:
> According to this bug tracker -
> https://sourceforge.net/p/rosegarden/bugs/1411/ - there has been a fix.
> Is this true through the latest version(s)?
Should be. Definitely worth building the latest to find out.
Ted.
On 03/02/2016 03:02 PM, Alfredo Crolle wrote:
> I select for a midi trace a voice (program) e.g. 123:Wind in bank 0:3 of
> imported a340.sf2 soundfont, but I get selected 123:seashore in qsynth
> channel window, that corresponds to bank 0:0.
It sounds like you need to modify the device (Studio
Like us on facebook:
https://www.facebook.com/rosegardensequencer
Follow us on Twitter @rosegarden_m
https://twitter.com/rosegarden_m
Ted.
--
Site24x7 APM Insight: Get Deep Visibility into Application
On 02/23/2016 07:55 AM, Rosegarden SVN repository wrote:
> Recover a classic version of GM.rgd and load it into the new default autoload
Ouch. Sorry about that. Didn't know that stuff gets translated.
Comments in various parts of the code led me to believe otherwise. I
certainly would've
On 02/22/2016 03:43 PM, Abrolag wrote:
> This works perfectly for me!
Great! If you can look over the Thru Routing user guide, I'd
appreciate feedback:
http://www.rosegardenmusic.com/wiki/doc:using_thru_routing
Ted.
On 02/21/2016 06:33 PM, Abrolag wrote:
> I have two MIDI keyboards. One set to transmit on CH1 and the other on CH2,
> and if I set Rosegarden Tracks 1 & 2 to only listen on those respective
> channels I can record both at the same time. However the record monitoring is
> only of the instrument
On 02/02/2016 08:58 AM, Cyr Bol wrote:
> As you say: it works when "I set Rosegarden to record".
>
> But, when you are not recording, all events go to the currently selected
> track. So, your splitted keyboard configuration is gone, which makes it
> diffcult (for me) to compose using RG.
>
> Can
On 01/20/2016 08:00 PM, Abrolag wrote:
> As I remember ARM cores manage significantly fewer clock cycles per
> instruction, so CPU frequency is not such a reliable guide.
Yeah. It's never a reliable guide. You never really know what'll
run until you try it.
Ted.
On 01/18/2016 02:43 PM, Home Stephens wrote:
> Interestingly, both of my example files have a number of volume events
> (type 7 I believe) throughout. I would have thought that these should have
> been type 11 expression events which is a percentage of volume.
Expression is used for
On 01/16/2016 04:57 PM, Home wrote:
> When I import midi files, I find that for most files the Midi Mixer has
> no affect.
I suspect that the files have volume control change messages
sprinkled throughout. MIDI tracks with dynamics (loud/soft transitions)
will have this problem.
Ted.
On 01/08/2016 07:49 AM, D. Michael McIntyre wrote:
> On 01/07/2016 06:44 PM, Ted Felix wrote:
>> I'm working on something similar with the drag/copy stuff right now.
>> I'll add this to my list of things to look at.
>
> The only consistent way I can find to jiggle
On 01/08/2016 08:48 AM, Bob Tennent wrote:
> Can someone at least tell me where Settings information is
> stored?
~/.config/rosegardenmusic/Rosegarden.conf
Ted.
--
___
On 01/07/2016 06:28 PM, D. Michael McIntyre wrote:
> Dump 20 segments into the composition in one shot, and the segment
> canvas doesn't become aware of its new size.
> If there is no scrollbar, it stays that way. If I force there to be a
> scrollbar, it's useless, because it isn't aware of the
On 01/06/2016 05:04 AM, D. Michael McIntyre wrote:
> Ended up with 2,187 new segments. One per event.
Good stress test for Composition.
Ted.
--
___
Rosegarden-devel
On 01/02/2016 05:51 AM, Holger Marzen wrote:
> Same effect. I chatted with FalkTX, maintainer of KXStudio, and he had a
> similar effect. Rosegarden didn't crash when opening the file dialog but
> freezed.
>
> I'll ask him if he's still encountering that freeze.
Ok. I'll look a little more
On 01/01/2016 05:41 PM, Holger Marzen wrote:
> Unfortunately Rosegarden still crashes when trying to open a file. It
> crashes before opening the file dialog.
I'm guessing it's libraries.
#3 0x7f8109b61862 in gnome_vfs_mime_get_value () from
/usr/lib/x86_64-linux-gnu/libgnomevfs-2.so.0
On 01/01/2016 06:15 PM, Holger Marzen wrote:
>>> Unfortunately Rosegarden still crashes when trying to open a file. It
>>> crashes before opening the file dialog.
>
> #14 0x7f811c8f9e6e in Rosegarden::RosegardenApplication::notify(QObject*,
> QEvent*) ()
> at
>
On 12/31/2015 06:20 PM, D. Michael McIntyre wrote:
> Kindly give her another whirl.
Debug and release builds are working fine for me now.
Ted.
--
___
Rosegarden-devel
On 12/31/2015 01:27 PM, Ted Felix wrote:
> From the tar file, a debug build with tests (a default debug build)
> is not possible since the make-release-tarball script removes the "test"
> directory before generating the tar file.
As a workaround, building the test
On 12/31/2015 09:32 AM, D. Michael McIntyre wrote:
> == ROSEGARDEN 15.12, codename "Peace" RELEASED ==
Thanks, Michael.
Found one issue...
From the tar file, a debug build with tests (a default debug build)
is not possible since the make-release-tarball script removes the
It appears that I've introduced a crash with r14419. I'm going to
back it out for now.
Ted.
--
___
Rosegarden-devel mailing list
Rosegarden-devel@lists.sourceforge.net -
On 12/15/2015 11:19 AM, Chris Lamb wrote:
Yep, works great. (Both in ./libnetlink.c and ./kacpimon/libnetlink.c)
Ok, this should be fixed upstream in [32f291].
https://sourceforge.net/p/acpid2/code/ci/32f291
I'll do an official release 1/15/2016. Unless you'd like it sooner.
Ted.
On 12/15/2015 11:19 AM, Chris Lamb wrote:
Yep, works great. (Both in ./libnetlink.c and ./kacpimon/libnetlink.c)
Ok, this should be fixed upstream in [32f291].
https://sourceforge.net/p/acpid2/code/ci/32f291
I'll do an official release 1/15/2016. Unless you'd like it sooner.
Ted.
On 12/15/2015 06:00 AM, Chris Lamb wrote:
acpid fails to build from source in unstable/amd64:
libnetlink.c: In function 'addattr_l':
libnetlink.c:497:54: error: comparison between signed and unsigned integer
expressions [-Werror=sign-compare]
if ((int)NLMSG_ALIGN(n->nlmsg_len) +
On 12/15/2015 06:00 AM, Chris Lamb wrote:
acpid fails to build from source in unstable/amd64:
libnetlink.c: In function 'addattr_l':
libnetlink.c:497:54: error: comparison between signed and unsigned integer
expressions [-Werror=sign-compare]
if ((int)NLMSG_ALIGN(n->nlmsg_len) +
On 12/03/2015 10:02 AM, Abrolag wrote:
> Having said that, why does Rosegarden want to set all channel bank MSBs to 0
> *except* 10 which it sets to 1?
That's just what's in the default composition. GM1 specifies nothing
should be sent. If you switch to GM.rgd, you should get that. GM2
On 11/23/2015 02:12 PM, Abrolag wrote:
> The first question is why on earth all these repeats?
That's likely just a side-effect of the size and complexity of the
code. Someone wrote some code to do this, then someone else came along
and wrote some more code to do this, and so on. Since it
On 11/13/2015 03:59 PM, David Faure wrote:
> Qt5 support added (patch updated). But the code isn't fully ready for Qt5,
> I guess the Qt5 port hasn't been merged yet?
The status of the Qt5 port is in patch #53:
https://sourceforge.net/p/rosegarden/patches/53/
"As of [r13745], all Qt5 code
On 11/13/2015 03:37 PM, David Faure wrote:
> * The about dialog is displaying a BUILDKEY, computed as a sha1 of the
> sources. Is this useful ?
It's a nifty thing, but I've never needed it. I guess it was put
there to detect users/distros tampering with the source? So if they
report a
On 11/13/2015 03:37 PM, David Faure wrote:
> All done (for Qt4 at least)
Working fine here.
Only very minor hiccups that were expected. Had to do a "make
distclean" with the old build system (make clean might have worked too,
but I figured I'd go all out) to get all the old garbage out
On 11/13/2015 07:31 AM, D. Michael McIntyre wrote:
> People who do this stuff for a living see an amazing shiny new toy, and
In my experience, professional developers hate version control. They
have to be forced to use it under penalty of being fired.
> I just see hard work, confusion, and
On 11/12/2015 08:55 AM, D. Michael McIntyre wrote:
> In any event, this is not a decision I want to make without input from
> Ted Felix, in particular. He is the true maintainer. I just make noise
> sometimes.
All the build systems are the same to me. I avoid them equally.
On 11/11/2015 07:12 PM, D. Michael McIntyre wrote:
> I'm open to suggestions from anyone.
There is one bug outstanding in the big-tuplet-rewrite branch: bug #1432.
Ted.
--
On 10/24/2015 12:50 PM, Holger Marzen wrote:
> Compiles out of the box but introduced a bug.
I've just committed Tito's fix for this. It's r14244. Please test
and let us know how it goes.
Ted.
--
On 10/25/2015 07:34 AM, D. Michael McIntyre wrote:
> The 15.10.2 release is hanging until I know whether to go without r14110
> or to go with Tito's patch. If you'll be kind enough to advise me, Ted,
> I will do the release in the next 24 hours.
I committed the patch as r14244. I've tested
On 10/24/2015 12:50 PM, Holger Marzen wrote:
> My bass track with the
> whysynth dssi plugin drops notes randomly when the same note is played
> several times and the end of one note is at the same position like the
> beginning of the next - as it happens when quantizing.
>
> This issue doesn't
On 10/24/2015 01:38 PM, Ted Felix wrote:
> On 10/24/2015 12:50 PM, Holger Marzen wrote:
>> My bass track with the
>> whysynth dssi plugin drops notes randomly
I am able to reproduce this with hexter. To reproduce you need a
synth plugin and repeating legato notes. Just drop
On 10/24/2015 02:02 PM, Ted Felix wrote:
> I'll do a little bisecting and see if I can track it down to a
> specific commit.
r14110 is the commit that introduces this regression
On 10/24/2015 02:44 PM, Ted Felix wrote:
> r14110 is the commit that introduces this regression.
I recommend backing this commit out and doing a 15.10.2 release.
601 - 700 of 1017 matches
Mail list logo
