Re: [LMMS-devel] RTshift --> help!

Quoting Mariano Macri : > Hi everyone! > If someone could please explain what exactly is the "sweep RTShift amount" > (In: papuInstrument aka FreeBoy) that would be very helpful ? > > Thanks! > A bit technical, but: http://gbdev.gg8.se/wiki/articles/Gameboy_sound_hardware#Frequency_Sweep Basical

Re: [LMMS-devel] Dynamic transposition?

The green base note dot in the instrument editor can have global automation, but it can't be dragged to a regular automation track for some reason. It's not a good solution, but you should be able to shift the pitch that way. Quoting Tres Finocchiaro : > A pitch automation that is on a bunc

Re: [LMMS-devel] Roadmap to 1.2

Quoting Tres Finocchiaro : > 1.2 isn't lost, just on hold... here's a reminder of what we have to look > forward to in 1.2 > Well, the MIDI export mentioned might need quite a bit of care and attention to be release

Re: [LMMS-devel] Roadmap to 1.2

Quoting Tres Finocchiaro : > Our major bugs before a release candidate are: > >- *#2318* - ControllerView causes hard crash Scratch that, just merged #2456. https://github.com/LMMS/lmms/pull/2456 -- ra...@iki.fi softrabbit on #lmms --

Re: [LMMS-devel] Which Jack packs should I have to compile LMMS?

Quoting Roberto Giaconia : > Still, compiling LMMS fails, not because of libsoundio which is found, but > because of some other header files. > After trying to use dependencies command again, I found out I had the wrong > jack libraries. > > The problems is that, in a way or another, synaptic asks

Re: [LMMS-devel] Roadmap to 1.2

Quoting Tres Finocchiaro : >- Once ~38 items are decided, we need to merge forward any 1.1. bugfixes >to master that never made it in. Looks to me like that's just the Ukrainian translation. It's the only thing that's happened in stable-1.1 since it was merged into master in June. --

Re: [LMMS-devel] MIDI import bug

Quoting midi-pascal : > Will you modify the code in your PR or should I wait for it to be pulled > in the master branch? > Your choice :-) Will push some changes to the PR soon-ish. -- ra...@iki.fi softrabbit on #lmms ---

Re: [LMMS-devel] CLang scan build

Quoting Tres Finocchiaro : > Thanks Yann. > > The vast majority of those (about 307 of them, or 90%) are introduced with > some older 3rd party LADSPA plugins, namel: > >- 67% - SWH LADSPA Plugin >- 12% - Tap LADSPA Plugin >- 7% Calf LADSPA Plugin >- 4% Zyn Instrument Plugin > >

Re: [LMMS-devel] MIDI import bug

Quoting midi-pascal : > The idea of naming the imported tracks and CC is a very nice feature too! > However the tracks name import does not work as expected: > The tracks are named Track 1, Track2... Track n, even if they have a > name in the original MIDI file. It did work back when I first made

Re: [LMMS-devel] MIDI import bug

Quoting midi-pascal : > There is a problem when importing some MIDI files: > If MIDI events notes are short, i.e. as in a drums track (~ 3 ticks) > they are not imported at all. > They do not make any sound and do not appear in the piano roll view either. > > I will try to figure what the problem

Re: [LMMS-devel] discussion of default workflow : form-focus

Quoting musikbear : > Take a look at this: > http://youtu.be/2xQIJ3EHV8M > I sugest this for presets, in the video, but i Went for coffe as this was in > 'processing', and it hit me, that ALL windows should have /this/ behavior. > ALL should be default 'stay-up'. This would be better for workflow

Re: [LMMS-devel] Blender example?

Quoting Vesa : > Should we just deprecate PatMan? Is there anyone, even one person, still > using it today? Well, if I needed a sample player that handles multiple samples in a preset (which AFP doesn't) and can bend and filter every note separately (which SF2 player can't)... but I rarely do

Re: [LMMS-devel] Coverity code scanning

Quoting Tres Finocchiaro : > Thanks for sharing that service looks very useful. > I thought cppcheck had been mentioned here on the list or on the issue tracker at some point, but looks like maybe it wasn't. In short: $ sudo apt-get install cppcheck $ cd $LMMS_SRC $ cppcheck -j2 --force src i

Re: [LMMS-devel] mmp's xml syntax

Quoting musikbear : > you misunderstand. mmp is formally 'well formatted', it is /leagal/ to use > selfclosing tags, it is however making file opp. difficult, because there is > no reconiceable end-tag, and begin-tags can be difficult to reconize. This sounds like you're reading the XML through so

Re: [LMMS-devel] Better JACK support

> On 12/19/2014 04:10 AM, Tres Finocchiaro wrote: > Does anyone object to me wrapping the open bugs into a single bug > report so that they can be addressed as a WIP when the opportunity arises? > https://github.com/LMMS/lmms/issues/276 Maybe not a JACK problem: "I changed to JACK and re-tried. T

Re: [LMMS-devel] Moving on...

Quoting Vesa : > Making more progress with tempo track... > > > Soon, proper sampletrack playback from any position should be a > possibility. Cool, but... where's the roadmap you were going to write? Not that this circus turning into a one man show necessarily is bad, but if that is to be avo

Re: [LMMS-devel] Uh... what?

Quoting Vesa : > #0. Current situation: Each automation can control many knobs, range of > automation is the range of the first connected knob > > #1. Each automation track only controls one knob, if you need it to > control several, you'll have to daisy-chain the knobs together by linking > > #2.

Re: [LMMS-devel] Uh... what?

Quoting Vesa : > On 11/19/2014 07:33 PM, Raine M. Ekman wrote: >> Was there anything in the message that could be interpreted as >> commands to the mailing list software? I've had a list or two and they >> could be admined through mail, no fancy web interfaces needed. &g

Re: [LMMS-devel] Uh... what?

Den 19 nov 2014 18:56 skrev Vesa : > > On 11/19/2014 06:49 PM, Vesa wrote: > >> Your mail to 'LMMS-devel' with the subject > >> > >> Options > >> > >> Is being held until the list moderator can review it for approval. > >> > >> The reason it is being held: > >> > >> Message may co

Re: [LMMS-devel] Going forward: LMMS 2.0

Quoting Vesa : > On 11/07/2014 12:56 PM, Raine M. Ekman wrote: > The current situation isn't exactly "one thread per note" either, it's > one threadable job per note, one threadable job per audioport, and one > job per mixer channel. All my idea does is basically

Re: [LMMS-devel] Going forward: LMMS 2.0

A few quick comments. Quoting Vesa : > *#2. Revise some core parts of LMMS > Get rid of the idea of rendering each note in its own thread. Instead, > move to a more conventional approach: one thread per track. The > reasoning here is simple: most people have at most 4 cores at their > disposal,

Re: [LMMS-devel] Can't render or play a project - infinitely loud nothing

Quoting Vesa : > Ok... what about non-x86 architectures, such as ARM? I'm not sure if > LMMS runs on ARM, if anyone has any ARM hardware, it'd be great if they > could try out compiling LMMS on it. This is a secondary concern though, > as we can just #ifdef it if it becomes an issue. Seems like ol

Re: [LMMS-devel] Can't render or play a project - infinitely loud nothing

Quoting Vesa : > On 10/21/2014 03:32 PM, Vesa wrote: >>> _mm_setcsr( _mm_getcsr() | 0x8040 ); >>> >>> >>> The plugins and LMMS engine/audio code will need to be built with >>> fastmath and SSE2, the gcc arguments are: >>> >>> -ffast-math -mtune=generic -msse -msse2 -mfpmath=sse >>> Note that t

Re: [LMMS-devel] LMMS t-shirts?

Quoting Shane Ambler : Start with image and caption suggestions, the same image can be used on several products, and possibly with slight modifications if you want to also offer it on something round like a clock (depending on the site used for products). Logo, small, left chest. That's the kin

Re: [LMMS-devel] VST root folder issue in LMMS

Quoting musikbear : > diiz wrote >> On 10/10/2014 01:51 AM, Tres Finocchiaro wrote: >>> BTW, I don't know C++, I just make changes until the software compiles >>> and let those who do know C++ tell me what I did wrong. :) >> >> Well, you know, that was exactly where I was at when I submitted my >>

Re: [LMMS-devel] XSS in your Project in regarding

Quoting Tres Finocchiaro : > Php can check the header and block requests from 3rd party domains (modern > web browsers actually do this automatically unless the site explicitly > allow cross domain resources), but I don't have access to see our current > site and it would be my first time doing th

Re: [LMMS-devel] Top Level Domain: Final decision

Why should the Italians care about the British Indian Ocean Territory? Quoting Israel : > can we use io? > Do they allow for non italian organizations to use it? some countries > do not want people outside of their country to use it. > that is why I suggested the others :) just in case. > > On

Re: [LMMS-devel] Making all native presets and samples in the same key

I'd start by listing the presets something like this: # basetone 9 = A, list all others egrep -o 'basetone="[0-8].?"' */*.xpf Organic/pad_ethereal.xpf:basetone="0" TripleOscillator/AmazingBubbles.xpf:basetone="11" TripleOscillator/Fat-TB303-Arp.xpf:basetone="4" TripleOscillator/FutureBass.xpf:bas

Re: [LMMS-devel] Pulseaudio keeps going weird

Quoting Vesa : > Your only options are ALSA or Jack. However, Jack support on LMMS can be > a bit glitchy. So your best bet is ALSA, and closing down LMMS whenever > you need sound somewhere else. If you don't need to do any MIDI communication in or out of LMMS, I'd suggest ALSA out to the "def

Re: [LMMS-devel] allow users to position widgets

ot, at least for the piano/b&b editors. Not that I'm too fond of stuff jumping around under the pointer causing misclicks, but I'm assuming this would be an optional feature, or at least tweakable? > On 06/25/2014 12:37 PM, Raine M. Ekman wrote: >> Let's see... &

Re: [LMMS-devel] allow users to position widgets

Quoting Jonathan Aquilina : > with my last comment i am referring ot windows with the various tools kinda > like photoshop does. no menus except the basic file etc and the rest are > flotable windows that float and can be dragged and moved around on screen. > Some say there already are too many w

Re: [LMMS-devel] Lmms 1.0 and Gentoo

This on master branch, not quite up to date, but I assume nothing has happened in this area in the last few days... Removed the libxinerama-dev package on Ubuntu and tried to build. Cmake doesn't complain about anything, but make goes like this: Linking CXX executable RemoteZynAddSubFx /usr/bin

Re: [LMMS-devel] Fwd: Re: LB302 accent

Citerar Vesa : > On 06/18/2014 09:48 AM, Raine M. Ekman wrote: >> Citerar Vesa : >>> In the original TB-303, it wasn't, it was a simple on/off switch. >> Yes and no. It had a simple on/off switch for programming the note, >> and a knob for how strong the acce

Re: [LMMS-devel] Ubuntu 14.04 package

Citerar "Raine M. Ekman" : > There are PPAs already carrying fresh LMMS, right? Like this first one > Google found for me: https://launchpad.net/~irie/+archive/lmms - 4 > Ubuntu releases covered, no huge web of dependencies that gets pulled > in when you install one packag

Re: [LMMS-devel] Ubuntu 14.04 package

Citerar Vesa : > On 06/18/2014 02:36 AM, Tres Finocchiaro wrote: >> >> >> > Maybe we should put a downloadable .deb package up on our homepage for >> > the time being? >> > >> >> +1. I tend to favor this anyways since the dependencies generally >> remain consistent and the package managers still

Re: [LMMS-devel] Fwd: Re: LB302 accent

Citerar Vesa : > On 06/18/2014 08:57 AM, Louigi Verona wrote: >> Just to remind of my short notice there, that I thought accent was a >> gradual parameter? Linux DSSI plugin and now an internal plugin in >> Carla has accent and it is gradual. > > > In the original TB-303, it wasn't, it was a simpl

Re: [LMMS-devel] Building for Windows on Ubuntu 14.04

Quoting Tres Finocchiaro : > I'm stuck here: >> *$ for MINGW in mingw32-x mingw64-x ; do> sudo apt-get install $MINGW-qt >> $MINGW-sdl $MINGW-libvorbis \ $MINGW-fluidsynth $MINGW-stk $MINGW-glib2 >> $MINGW-portaudio \ $MINGW-libsndfile $MINGW-fftw $MINGW-flac $MINGW-fltk >> \ $MINGW-libsample

Re: [LMMS-devel] Building for Windows on Ubuntu 14.04

Quoting Tres Finocchiaro : > A wiki is probably the best place, even if it needs feedback. > > Attached is a quick github translation of it. > > Here's a working copy of it: > https://github.com/tresf/lmms/wiki/Compile-lmms-Windows Looks like we duplicated some effort: https://github.com/softrabb

Re: [LMMS-devel] Building for Windows on Ubuntu 14.04

Quoting I'm Umcaruje : > That manual basicly covers it all up, very nicely written! I would just add > that you should do chmod u+x on both the scripts, otherwise it wont run > (happened on my Xubuntu 14.04). Oh yeah, that possibility didn't occur to me. OTOH, maybe we could assume a developer k

Re: [LMMS-devel] Building for Windows on Ubuntu 14.04

Quoting Tres Finocchiaro : > Fantastic! Can you wikify this on your own github and then we can bring it > over to the official page once proper access has been granted? Sure, right after some QA. If anyone can spot errors or anything, please share :) I'm especially confused by the need to run

[LMMS-devel] Building for Windows on Ubuntu 14.04

Getting this to work involves a few points where one might choose the wrong path, so here's a little something about building for Windows. Maybe there should be a wiki page on the subject? Many thanks to Umcaruje for a few crucial hints! ### Installing packages for cross compiling # Toby h

Re: [LMMS-devel] gentoo and lmms 1.0.2 issue

Citerar Jonathan Aquilina : > That is not the issue. It is choosing the backend which doesnt get set When LMMS asks me to choose a backend on startup, I check with "lsof |grep snd" to see who is holding the sound device captive. Sometimes it's an LMMS I forgot on another desktop, sometimes so

Re: [LMMS-devel] Double name on presets

Quoting Tres Finocchiaro : > Perhaps the functionality could be changed to stop saving the preset name. > > Some people really like doing some file management things with file names > so there might be a small amount of push back on this... i.e. > zyn_preset_01.xpf = "Blast Off!". In this case,

Re: [LMMS-devel] Things learned while working on the sampletrack branch

Quoting Tres Finocchiaro : > Most of these make the song-editor > front-row-and-center for track content, and the beat/bassline is simply a > child of that interface. Are you saying that isn't the case now? I've always seen the B&B editor as a very close relative of a drum machine... > So

Re: [LMMS-devel] Problem with model step, and studies in sample-exact controls

Citerar Vesa : > Part of the problem is no > sample-exactness in playback, but part is because the step size prevents > gradual change so that even with sample-exactness the problem still > exists. Solving this would make peak/LFO controllers much more useful > and flexible, as you could connect th

Re: [LMMS-devel] Using VSTs on Windows makes LMMS crash every max 10 minutes.

Citerar "giakk...@hotmail.it" : > For the autosave function, is there any way to have it back? Try turning it on and see what happens. If LMMS starts crashing again, it might be the VST+autosave combination that's causing it. And then some technical speculation: As of now LMMS won't autosave wh

Re: [LMMS-devel] Wiki revival

Citerar Stian Jørgensrud : > If you want to write articles, click edit on the link above and copy the > exact name of the article you want to write. Search for it and then click > create. If you aren't registered reply to this message. A lot, if not most > of the text, can be copied over from the

Re: [LMMS-devel] Wiki revival

Citerar Stian Jørgensrud : > LMMS has its own wiki! http://lmms.sourceforge.net/wiki/index.php/Main_Page > As a matter of fact it also have it's own manual in pdf format, which I > currently consider better as the wiki > https://sourceforge.net/projects/lmms/files/UserManual/ This was created by >

[LMMS-devel] Should master be the default branch on github?

"Closes #xxx" markings in pull requests only close issues in the default branch. If it's safe to change, maybe make master the default to enable that feature? -- ra...@iki.fi softrabbit on #lmms -- "Accelerate De

Re: [LMMS-devel] collaborato

Citerar Vesa : > If there has to be an option for downloading presets/samples/whatever > from LSP or elsewhere, fine... but it should be configurable, it should > not break existing functionality, and it needs to be implemented better. > > Particularly, the file browser shouldn't get broken so horr

Re: [LMMS-devel] Feeling a little testy

Not much yet. I've barely had time to keep up with reading my inbox lately. Quoting "Lukas W." : > @Raine > May I ask what has become of your efforts? It really would be great if > we had at least a few tests. :-) > > 2014-04-12 11:44 GMT+02:00 Jonathan Aquilina : >> I think if there are people w

Re: [LMMS-devel] resid on gentoo

Quoting Tres Finocchiaro : > Gentoo was questioning fundamentally whether or not the source of this > package *should* even be bundled to begin with, or rather be a dependency > that the original source package provides. Sorry Lukas, I get it now. :) > > The changes seem to be specific to muting (

Re: [LMMS-devel] Is there a reason that libstk is not bundled?

Ok, I see. Looks like the same error as before, which means my stab at a quick fix didn't do much good. The change is in stable-1.0 and master since a while back, there's no special fork to try or anything. Quoting Tres Finocchiaro : > @Raine, > > I tried for 1.0.0-stable and get this: > ht

Re: [LMMS-devel] Is there a reason that libstk is not bundled?

Citerar Tres Finocchiaro : > Ok, never mind I got it working, required some small changes. > https://github.com/LMMS/lmms/pull/638 > > Here's it live in action :) > http://i.imgur.com/bcFAIff.png What, still no OpulenZ? I thought I fixed the C99 compatibility problems... Is there something else

Re: [LMMS-devel] Lmms 1.0 and Gentoo

Citerar Jonathan Aquilina : > 2) gentoo has a policy if something like zynsubaddfx is available through a > system install it is preferred over having it bundled with lmms. In our > version of zynsubaddfx are we using something that is modified and patched > to suite the needs of LMMS? The 2.4.0 o

[LMMS-devel] Feeling a little testy

Or IOW: I've had it with these melon-farming bugs on this Monday-to-Friday project! Command line rendering broke for the second time this year. Apparently almost no-one uses it, but OTOH it's the one thing in LMMS you actually can test without almost any effort (stay tuned for a 1-minute t

Re: [LMMS-devel] LMMS in portuguese language (?)

Quoting Esteban Viveros : > Well.. I tried it, but translation don't work... I tried pt-br and pt and I > have this: > > esteban@DeathStar ~ $ LANG=pt-br lmms > > (process:3135): Gtk-WARNING **: Locale not supported by C library. > Using the fallback 'C' locale. > Got bus address: > "unix:abstra

Re: [LMMS-devel] LMMS in portuguese language (?)

Quoting Tres Finocchiaro : >> >> Hum... Ok.. I can see we don't have portuguese translation 100% complete.. >> I can work in it too... Finocchiaro, you know if that's the reason >> (incomplete translation yet) because I can't use LMMS in portuguese ? >> > > No, I do not know the answer to this. P

Re: [LMMS-devel] Live performance mode and remote control interface on tablets

y possible with OSC, but possibly not needed. Citerar Jonathan Aquilina : > Very valid point. BTW you only sent this to me. From what Im seeing this > seems to be very mac specific or is that not a correct assumption to make? > > > On Tue, Apr 1, 2014 at 9:46 AM, Raine M. Ekman wrot

Re: [LMMS-devel] Live performance mode and remote control interface on tablets

Citerar Jonathan Aquilina : > Another thing I have noticed is that they have what they call a remote. It > connects via wifi which is a good thing imho as well as a bad one. I was > not able to connect it to FL on mac, but again that could be a bug with the > mac crossover wrapped version. The who

Re: [LMMS-devel] Building LMMS for OSX

Quoting Vesa : > On 03/31/2014 09:04 PM, Tres Finocchiaro wrote: >> ** /plugins/CMakeLists.txt* >>- Omit ADD_SUBDIRECTORY(opl2, when apple (or clang) is detected > > Same here: I think we shouldn't disable building of plugins for any > platform, definitely not in upstream - they should rather

Re: [LMMS-devel] ENV/LFO idea...

Citerar Vesa : > 1. Introduce a new type of native plugin: note effect. These are effects > which work the same as effect plugins, but they get applied for the > note-specific audiostreams. Of course this means they only function on > non-MIDI-based, native multistream instruments (basically, all w

Re: [LMMS-devel] Just a thought

Citerar Jonathan Aquilina : > Where does one view said doxygen documentation? > So far, it's on one's own system... "make doc" (I think) and it gets built. That could of course be mentioned on the developer wiki, too. Wouldn't hurt to put docs for the master branch online when the New Site

Re: [LMMS-devel] Just a thought

Citerar Jonathan Aquilina : > I think though the comments in the code should be moved to the wiki or some > sort of documentation outside of the code itself. If those that want to > create instruments etc they don't want to stay going through the code to > figure out what it does. I would say they

Re: [LMMS-devel] AFP loop points

Quoting Vesa : > To properly implement a release phase for a sustain loop, the length of > note release would need to be dependent on the note frequency, but I > don't currently see a way to do this. There's desiredReleaseFrames() > which is meant to return the desired frame amount, but it doesn't

Re: [LMMS-devel] stable-0.4-new-fx-mixer merged

Citerar Vesa : > On 03/28/2014 10:20 AM, Raine M. Ekman wrote: >> Citerar Tobias Doerffel : >>> - rewritten undo/redo support >> As this probably is something concerning most parts of LMMS, I wonder >> if there's some documentation to read, or does undo/redo wo

Re: [LMMS-devel] AFP loop points

Citerar Vesa : > Ok, due to some unexpected difficulties (The note release system working > differently than I thought it did), I'm going to abandon the idea of a > sustain-loop mode, which doesn't seem feasible in the current LMMS > architecture, at least not the way I'd want to implement it. OK,

Re: [LMMS-devel] stable-0.4-new-fx-mixer merged

Citerar Tobias Doerffel : > - rewritten undo/redo support As this probably is something concerning most parts of LMMS, I wonder if there's some documentation to read, or does undo/redo work automagically enough that one mostly doesn't need to know anything about it? -- ra...@iki.fi softr

Re: [LMMS-devel] Building LMMS for OSX

Citerar Vesa : > On 03/27/2014 05:09 AM, Tres Finocchiaro wrote: >> @Toby, >> >> Thanks kindly. 77%: >> >> I'm guessing this next message suggests the OpulenZ code has some >> compatibility issues with clang as well: >> >> Linking CXX shared module libOPL2.so >> Undefined symbols for arch

Re: [LMMS-devel] Building LMMS for OSX

Citerar "Raine M. Ekman" : > Citerar Tres Finocchiaro : >> I'm guessing this next message suggests the OpulenZ code has some >> compatibility issues with clang as well: >> >> Linking CXX shared module libOPL2.so >>> Undefined symbols for architec

Re: [LMMS-devel] Building LMMS for OSX

Citerar Tres Finocchiaro : > I'm guessing this next message suggests the OpulenZ code has some > compatibility issues with clang as well: > > Linking CXX shared module libOPL2.so >> Undefined symbols for architecture x86_64: >>"_OPL_CALC_CH", referenced from: >> _YM3812UpdateOne in fmop

Re: [LMMS-devel] usr/lib/lmms ubuntu package

Quoting Tres Finocchiaro : >> >> I noticed 1.0 dumping core on exit, is that what you're talking about? >> > Yes. > > >> Had the same behavior with a self-built 1.0, too. > > I didn't recall this behavior, but I would have to rebuild/retest to know > for sure. OK, turns out I've for some reason m

Re: [LMMS-devel] FX channel selector in the instrument track widget?

Maybe put the fx channel selection in the tool menu, along with the "delete track" function and whatever? Another thing to consider could be dropping the tool button and moving that menu (with "rename track" as a context menu to the track name? Quoting Tobiasz Karon : > Great! I think this w

Re: [LMMS-devel] usr/lib/lmms ubuntu package

Quoting Tres Finocchiaro : > Some notes: > 3. The 12.04 core dump/error report still exists for this build I noticed 1.0 dumping core on exit, is that what you're talking about? Had the same behavior with a self-built 1.0, too. -- ra...@iki.fi softrabbit on #lmms -

Re: [LMMS-devel] usr/lib/lmms ubuntu package

Quoting Israel : > It is built for 12.04 (please test 64bit if you have it) > 13.10( any arch testing appreciated) > 14.04 (32 bit especially!) 12.04, 64 bit, upgrade from 0.4.15. (or 0.9.92 if you ask my lmmsrc.xml :) Now that I think about it, that earlier version was from some PPA, but that

Re: [LMMS-devel] Building LMMS for OSX

Quoting Tres Finocchiaro : > How much work would it be to make the source file `gong_1424.c` (and > possibly others) compile with Clang? > > https://github.com/LMMS/lmms/blob/stable-0.4/plugins/LadspaEffect/swh/gong_1424.c From the hints in the bug report at SF, I'm guessing adding -std=gnu89 t

Re: [LMMS-devel] LMMS 1.0.0 compilation issues

I vaguely remember that conversation, but can't find it in the archive... if the official line is that Qt 4.6 is too old to be supported, shouldn't the CMakeLists.txt file be updated? Now it says: SET(QT_MIN_VERSION "4.3.0" COMPONENTS QtCore QtGui QtXml) Citerar Nikko Rocksalot : > > > I

Re: [LMMS-devel] Any critical issue left?

There's the critical issue of mixing top and bottom posting. That really needs to be stamped out... please, stick to the style of the previous message and don't make it harder to read for the rest of us. :) As for branches, branching 1.0 off of master and only applying bug fixes to it or so

Re: [LMMS-devel] Filter tracking

Quoting Tobias Doerffel : > besides being a nice idea, I'm asking my self, whether there is an > actual meaningful use case for this? The resulting sound would be > completely different for notes at different keys. That would pretty much be the point, yes... Note tracking filters are a fairly co

Re: [LMMS-devel] Filter tracking

Quoting Vesa : > On 03/15/2014 10:42 AM, Raine M. Ekman wrote: >> I have to disagree a bit on the knob function. Why not make it work >> in cents or octaves when the filter is tracking note frequency? >> Something like a range of +/-X octaves with 0 being the not

Re: [LMMS-devel] Filter tracking

I have to disagree a bit on the knob function. Why not make it work in cents or octaves when the filter is tracking note frequency? Something like a range of +/-X octaves with 0 being the note. That way the relation is more obvious. Sent from my Xperia™ smartphone Vesa wrote: >Since we have

Re: [LMMS-devel] Idea: optionally use librubberband for pitch scaling in AFP

Citerar Vesa : > Currently AFP works by simple scaling of pitch by resampling the sample > buffer. This is probably sufficient for most purposes. > > But what if we provided an additional, optional feature: scale pitch > with librubberband, which can scale pitch without changing the > length/tempo

Re: [LMMS-devel] A pair of feature requests(I can program them maybe)

Citerar Rubén Ibarra Pastor : > QMLAnimator: A widget that animates and gets at full screen when > playing notes according to parameters, pitch, volume, portamento, > etc. I think this would help if we want to do Live Shows with LMMS. > I would wish to do one soon, at least an amateur one

Re: [LMMS-devel] Rethink time signature: instead of one global time sig, have a time sig for each pattern

Citerar Vesa : > You have to also remember that time sig in LMMS doesn't work exactly the > same way as time sig in sheet music. In traditional notation, the lower > part signifies which note length corresponds to one beat, for example: > in 4/8 time, an 8th note would be one beat, meaning that one

Re: [LMMS-devel] Rethink time signature: instead of one global time sig, have a time sig for each pattern

Citerar Vesa : > Actually now that I think about this, I think this is one thing we could > do before 1.0.0 (since it will break backwards compatibility): modify > time signature so that the denominator is constrained to binary > exponents, like it is on actual time signatures. Time sigs that LMMS

Re: [LMMS-devel] Rethink time signature: instead of one global time sig, have a time sig for each pattern

Citerar Vesa : > I think we should rather move to a model, where instead of one global > time signature we could just allow setting a time signature for each > pattern individually - you could mix in 5/8 patterns at the same time > with 3/9 patterns, at the same time. This would be implemented for

Re: [LMMS-devel] Stems not in sync after export [0.4.14-rc1]

Quoting Tobiasz Karon : > On 1 Mar 2014 20:28, "Raine M. Ekman" wrote: >> OTOH, now instruments produce sound also when muted. I exported your > 50-tracker at a speed of 3 minutes/track from a generic x86 build of > 0.4.15, which couldn't play it live with the drums

Re: [LMMS-devel] Stems not in sync after export [0.4.14-rc1]

Quoting Tobiasz Karon : > Yes, there was a lot of tempo automation. I used only ZynAddSubFX, no > samples or other instruments. Yes I used export tracks. > > Well, maybe a warning, that the export tracks might not work as expected > and is being worked on, rather than disabling it completely. With

Re: [LMMS-devel] Stems not in sync after export [0.4.14-rc1]

Quoting Tobiasz Karon : > I've just exported a 51-track tune onto stems (it took about one and half > an hour to render), imported it into Ardour, and... it's *useless*. Is that the competition entry you advertised in another thread? -- ra...@iki.fi softrabbit on #lmms ---

Re: [LMMS-devel] Stems not in sync after export [0.4.14-rc1]

Quoting Vesa : > On 02/28/2014 11:38 PM, Tobiasz Karon' wrote: >> Hey! >> >> I've just exported a 51-track tune onto stems (it took about one and >> half an hour to render), imported it into Ardour, and... it's *useless*. >> >> The timing of individual tracks is off sometimes as much as *few >> se

Re: [LMMS-devel] rc1 bugs

Citerar Tres Finocchiaro : > Secondly, is the "create new project from template" button in the toolbar > unfinished at this point? It doesn't appear to be functional, at least in > Windows. Last time I looked the button worked fine. You need to have some templates in the right place (a template

Re: [LMMS-devel] LMMS 0.9.91 (1.0.0-RC2)

Should be in the normal places: man lmms lmms --help Don't know how one would find out about this on less Unixish systems, though. Maybe there's a Youtube tutorial for it? Citerar Jonathan Aquilina : > Is it documented anywhere? > > > On Tue, Feb 25, 2014 at 9:09 AM,

Re: [LMMS-devel] LMMS 0.9.91 (1.0.0-RC2)

Has worked fine for as long as I can remember. Citerar Jonathan Aquilina : > exactly what I am thinking something like that. Does some functionality > already exist like that? > > > On Tue, Feb 25, 2014 at 8:59 AM, Raine M. Ekman wrote: > >> Citerar Jonathan Aquilina :

Re: [LMMS-devel] LMMS 0.9.91 (1.0.0-RC2)

Citerar Jonathan Aquilina : > Tres you got me thinking here. > > What is everyones take on the following. > > How about having a command line option to export an mmp or what ever the > current supported format is for projects and allow users versed in the > command line to export a song in a hurry

Re: [LMMS-devel] Bitinvader

Citerar Tobias Doerffel : > Ok, then let's go for it. It's better to break things before 1.0.0 ;-) > Once 1.0.0 is out, I feel that compatibility will get even more > important. This is also why I'm not sure how to handle e.g. the update > of the CAPS LADSPA plugins. In 0.9.x they renamed everythin

[LMMS-devel] Proposal: centralize editor grid calculations

So, I had a look at grid drawing in the Automation Editor lately, related to issue #283. The problem there comes from the X coordinates being calculated in too many places: both in the timeline and in the grid. What I'm thinking of doing is moving all the time<->X coordinate conversions i

Re: [LMMS-devel] Time display widget

Citerar Vesa : > On 02/13/2014 12:30 AM, Tobiasz Karo? wrote: >> >> Maybe the automated tempo time calculation could be aided with >> maintaining a time table. >> > > IMO the best way would be to do away with tempo automation as it > currently is, and instead implement a global tempo map. It could

Re: [LMMS-devel] Release critical bugs for 1.0.0?

I'm with the "release 1.0.0 and add undo later" crowd. Or has 1.0.0 been widely advertised as having undo? And IMO there have been enough changes to get them out in the wild and let the users find new bugs... :) Citerar Tobias Doerffel : > Hi, > > yes AFP is one of the plugins to be fixed

[LMMS-devel] Release critical bugs for 1.0.0?

Some more bugs should probably be marked for 1.0.0, as they would look pretty bad in a release. I nominate #281, "MIDI keyboard pitch wheel crash" for this honour: https://github.com/LMMS/lmms/issues/281 Any others? -- ra...@iki.fi softrabbit on #lmms -

Re: [LMMS-devel] Old vs New SID Emulator art

Quoting "Bill Y." : > Thoughts, comments, feedback. > > https://drive.google.com/file/d/0BwJ-TpACk7OsZ0JwRjRwd3pwREk/edit?usp=sharing > Pretty nice. The buttons could IMO have a clearer indication of state, e.g. the selected waveform is much easier to spot in the old artwork. -- ra...@iki.fi

  1   2   >