freewheeling-user — Mailing List for Freewheeling Users

[Freewheeling-user] video demo fweelin

[arnaud f <arn...@gm...>]

Hi,

Just to share with you a very basic demo of freewheelin, with other linux
softwares (rakarrack +, MDA piano, Hydrogen...) on my Youtube channel :
https://www.youtube.com/watch?v=GuMLe-jBf4I
Hope you'll enjoy it !

Bye

Re: [Freewheeling-user] freewheeling status update

[bill-auger <bil...@pe...>]

the mac port has been broken for many years though so no one can compile it

https://github.com/free-wheeling/freewheeling/issues/2

if ever someone decides to get this working on mac again they will find that it needs to use nettle now as well

Re: [Freewheeling-user] freewheeling status update

[Danni C. <dan...@gm...>]

> there still exists a "-git" package that
> was changed to link to openssl which voids the GPL - this, as you may
> remember, is what originally spurred the move to github


If this this is case then technically freewheeling has been breaking the
GPL for many many years since it has always linked against openssl on Mac
and still does.

Re: [Freewheeling-user] freewheeling status update

[Danni C. <dan...@gm...>]

>
> the openssl conflict arose - there still exists a "-git" package that
> was changed to link to openssl which voids the GPL - this, as you may
> remember, is what originally spurred the move to github - but
> unfortunately it's maintainer also is unresponsive - the openssl conflict
> arose - there still exists a "-git" package that
>

Yeah sorry this was sending itself as a digest and it took a great deal of
effort on sourceforget to change my settings all of which put replying on
this list above my can be bothered threshold.

It turns out that the functions that freewheeling was using in are openssl
compatible shims for th e real functions in libgnutls. These are not
packaged with arch (and from previous experience often break on other
distros) it was however relatively straight forward to port the code to use
libgnutls without the shims. The patched code is on my github now.

Also just for the record this wasn't the reason for the move to github. I
previously had to patch some issues with multithreading that would cause
freewheeling to fail to load quite often on modern hardware.

[Freewheeling-user] freewheeling status update

[Bill A. <mr....@gm...>]

there hasnt been much activity on the mailing list lately but there
has been quite a bit on github so i figured an update was in order -
since the move to github there have been a number of patches including
at least one major bug fix, all GCC compiler warnings fixed, the
autotools files updated, and the wiki fully restored

recently, ive been looking into the freewheeling distro packages and
discovered that debian had fixed many of the same issues years ago in
their package and i been trying to contact the maintainer to let him
know that the debain patches are probably not necessary any more if
they track the new upstream repo - unfortunately he has not responded
- i asked the debian "MIA" team about this and they said they were
already in the process of locating him or orphaning his packages if he
is not found so that someone else can adopt them because he also
maintains some other important audio packages - but debian is slow to
jump to extreme measures so it may be several months before an updated
packages gets in - i also spoke with the debian-multimedia team and
they said they could help me take over if need be so freewheeling's
future in debian is probably secure

at first look i thought that debian were the only ones still packaging
freewheeling (which trickles down to derivatives such as ubuntu and
mint) but i also found freewheeling was in the repos of other distros
as well such as PLD, nixOS, and SourceMage - most of the recent
patches were contributed by the PLD package maintainer (Jajcus) and a
nixOS package maintainer (magnetophon) helped with the loopidity
documentation recently so i know that they are tracking the github
repo now - the SourceMage package is like ancient though
(VERSION=0.5.2) but i sent them email just today so i dunno how that
will play out

then there is arch - i know if freewheeling was ever in the official
arch repos but there was a stable package in AUR that was removed when
the openssl conflict arose - there still exists a "-git" package that
was changed to link to openssl which voids the GPL - this, as you may
remember, is what originally spurred the move to github - but
unfortunately it's maintainer also is unresponsive - for this one i
asked another AUR maintainer to post a flag on it so that someone in
arch will take notice eventually - if anyone on this mailing list is
an AUR maintainer feel free to take this over - ive added a packaging
directory to the freewheeling sources including a PKGBUILD that builds
on stable versions according to git tags so this would be an easy
chore - but as PKGBUILDs are so easy to make, maintain, and install
ive never had any inclination to join AUR myself

i have not yet started building freewheeling on OBS which provides
package repos for other distros such as fedora and opensuse but this
will probably happen eventually - that should cover a good 90% of
GNU/Linux users - if anyone knows how to make a gentoo ebuild plz do
chime in - it might be fun to investigate how easy it would be to port
freewheeling to windows

[Freewheeling-user] loopidity looper wiki

[Bill A. <mr....@gm...>]

i've been asked in the past about documentation or screencasts for
loopidity but there was none at the time - user's have been nudging me
recently so i created some basic documentation with a getting started
tutorial for those who are interested

https://github.com/bill-auger/loopidity/wiki

[Freewheeling-user] freewheeling upstream may need to move

[Bill A. <mr....@gm...>]

as you may know there has been recent interest in reviving freewheeling
development but the state of the upstream is unfortunate - JP has not been
active on this list in a very long time - both of the email addresses i
have for him are defunct and he is not responding to sourceforge messages
(probably for the same reason) - there is one other person 'Rik' who has
limited admin access to the sourceforge fork and i have been discussing
with him how to get freewheeling back on track properly but his permission
set is limited so it is still not clear if the sourceforge fork can be
fully or even partially revived - it may not even be possible to post a
notice on the sourceforge landing page that the sourceforge fork is frozen
and development has moved elsewhere

for the sake of the wiki documentation i started a fork on github -  in
case that moving the upstream is the only option i put this on an
"organization" for free-wheeling so that the project can have multiple
maintainers - currently the github fork is based on a fresh import from
sourceforge using the github auto-importer tool - on top of that i updated
the autotools files to the current debian 9 version on one branch and on
another branch i fixed the gnutls/openssl issue for arch - that issue was
actually fairly trivial - only the MD5 functions were used and that only
for making unique loop filenames so either gnutls or openssl were both
overkill anyways - the arch branch also builds on debian so it could
probably be merged into master once it is verified that freewheeling still
builds on other major distros such as fedora

https://github.com/free-wheeling/freewheeling/

seeing as only debian, mint, and ubuntu are still carrying binaries i could
set up an instance on the OpenSuse Build Service to build packages for
other distros - but other than that IMHO nothing more needs to be done -
the program is already stable, the codebase was well constructed so is
still quite viable moving forward, and because JP had the foresight to
license it GPL+ it still has a future standing on it's own - the only
potential snags for the project are related to the sourceforge website but
not the program itself - i did not at all plan to become the new maintainer
but freewheeling is a great piece of software and it should have
stewardship (ideally with discussion and consensus from the community
guiding the project's direction)

ideally development can continue on sourceforge seeing as most of the links
on the web will always point there but let me know if you would like to
join the github team if we must go that route - also it by no means must
move to github - i am currently working on the development of the notabug
website which is a community-operated non-commercial code host - i have the
same fork as github mirrored there as well and i would be as happy to make
that freewheeling's new home

https://notabug.org/freewheeling/freewheeling

Re: [Freewheeling-user] Freewheeling Wiki

[Bill A. <mr....@gm...>]

Michaël -

sry about the delay - i have been trying to co-ordinate this properly
rather than jump to an ad-hoc solution - JP has not responded on
sourceforge and both of the email addresses i have for him are defunct -
there is one other person 'Rik' who has limited admin access to the
sourceforge fork and i have been discussing with him how to get
freewheeling back on track properly but his permission set is limited so it
is still not clear if the sourceforge fork can be revived or if it is even
possible to post a notice that development has moved elsewhere

what we do know is that the wiki can not be restored on sourceforge - i
spent some time last week re-constructing, updating, and styling the wiki
files i had to render properly on github - i suppose that will need to be
it's new home

https://github.com/free-wheeling/freewheeling/wiki

Re: [Freewheeling-user] Freewheeling Wiki

[Michaël C. <mi...@ca...>]

On Sat, Oct 29, 2016 at 6:34 AM, Bill Auger <mr....@gm...> wrote:
> i had completely remade the freewheeling wiki several years back when
> sourceforge ate the original freewheeling wiki - JP was self-hosting that
> version for a while but it looks like that is gone too - anyways i still
> have all the files in mediawiki format if you want to host them - or perhaps
> Danni Coy would like to put them on the github fork though it would take
> some effort to make them compatible with github wiki format

I'd be really glad to have my hands on those files.  I can
(temporarily, I guess) put them online on my server, but this may
confuse potential users.  I wholeheartedly agree that it'd be better
if it were uploaded next to the sources, though.

Cheers;
M.

Re: [Freewheeling-user] github fork (Bill Auger)

[Bill A. <mr....@gm...>]

danni -

i hope i am not coming across as too negative - i would be quite interested
to see freewheeling development move forward in a direction that is
beneficial to the entire community such as adding new useful features and
tech support - the reason for being so vocal up-front is because everything
that has been done or is proposed so far seems only to customize the
program for one person's preference of distro and tools but nothing that
could be considered as a general improvement other than fixing the compiler
warnings - so it is not at all clear in which direction it is moving or
whether i or anyone else should be interested



> Yeah I must have looked for an existing version on Github to fork to save
bandwidth essentially (my internet is pretty dodgy).

this does not require any extra bandwidth - github has a built-in importer
- you just click "import repository" and paste in the freewheeling
sourceforge SVN address and github does the rest - that is almost certainly
how tnovelli did it - i did this today into a new org account to make a
clean fork so i could poke around at it



> gnutls-openssl is badly broken on arch - The only reason this is used is
to generate MD5 hashes.

if i discovered a program that would not compile on my system but does
compile on nearly every other system i would not jump to the conclusion
that the program is broken and in need of repair but my first thought would
be that my OS is broken and i should ask them to fix it or else choose
another distro

i poked at this a bit today and i was able to get freewheeling to build on
a 32-bit qemu install of arch with JACK1 by replacing the gnutls-openssl
dependency with nettle and tweaking the function calls accordingly in
fweelin_core.cc - i then pushed those changes to github and compiled it on
a debian 9 64-bit hardware install with JACK2 and it seems to be running
fine on both systems - but ive done this initially only on a side branch as
not to impose it on all users before it is thoroughly tested on several
distros such as arch, debian, fedora, opensuse, and ubuntu (maybe even
slackware and gentoo) ideally every distro that has or once had a
freewheeling package - only then could it be determined which distros will
be supported and which will not be - and even then it would still be
debatable whether to merge this change into master or to maintain a
separate branch just for arch users -
https://github.com/free-wheeling/freewheeling/tree/arch



> I switched to CMake because I don't know autotools and I have no
intention of learning or supporting this build system. I am not aware of
any project that still uses autotools except for legacy reasons. I was
thinking of porting Freewheeling to current SDL which would have broken the
build system but at this point I don't know if I am going to do anything
major.

generally speaking - if it aint broke - dont fix it - doing so can lead
down a rabbit hole of complexity for little benefit if it is not absolutely
necessary - the same applies to SDL btw - SDL1.2 is not deprecated - it is
still supported and available on all major distros - also SDL2 is much
heavier so unless you absolutely needed to use some of the extra features
it provides that would probably be a degradation rather than an improvement

the same (if it aint broke - dont fix it) can be said regarding cmake - i
have compiled a countless number of programs on *nix and i can honestly say
that the overwhelming majority of them used the standard GNU build system
`./configure && make && make install` - 90% would be a conservative
estimate - it is quite surprising that someone would have the impression
that autotools is a fringe 'legacy' toolset - i was interested enough to
find out how my estimate compared to any formal surveys that i researched
this a bit but i could find only one - it was based on the packages in
ubuntu and concluded (although less than my estimate) that autotools or
standalone makefiles were more widely used than all other build systems
combined including java and others (which i was ignoring) - as such it
would be in your own best interest to become familiar with it and if you
ever do something that breaks it i would use that as a learning opportunity
-
http://voices.canonical.com/jussi.pakkanen/2012/09/21/relative-popularity-of-build-systems/

again tho im not intending to discourage the use of cmake - there is no
reason they can not both co-exist but you should definitely add bulid
instructions for cmake - and as long as such drastic changes are not made
then you would not need to worry about supporting the original build system
- it already works - just dont break it and yer golden

Re: [Freewheeling-user] github fork (Bill Auger)

[Danni C. <dan...@gm...>]

>
> it is good to see an interest in continuing development of freewheeling and
> i have reviewed danni's fork on github and i must say that it has a number
> of issues that should be addressed
>
> * this first one is not terribly important but is worth noting - danni's
> github fork was forked from another github user 'tnovelli' who added only
> one commit three years ago and that commit was actually deleted on danni's
> fork - based on tnovelli's github activity history it seem quite clear that
> this person does not use github very much and is probably not interested in
> being the upstream maintainer - in any case danni has never offered any
> merge requests upstream - in a situation like this it would probably be
> best for danni to delete the existing fork and recreate it as a stand-alone
> it is good to see an interest in continuing development of freewheeling and
> i have reviewed danni's fork on github and i must say that it has a number
> of issues that should be addressed
>

Yeah I must have looked for an existing version on Github to fork to save
bandwidth essentially (my internet is pretty dodgy).


> * the github issue tracker is not enabled for either of the tnovelli and
> kayosiii forks and so the mailing list is the only way for anyone to
> contact the developers - i would suggest enabling the issue tracker for bug
> reports in order to reserve the mailing list for general discussions
>

I will look into this.

* regarding cmake - providing users options is a good thing in general and
> i would not have made an issue of this except that the entire set of
> autotools files were deleted which is not giving users any option but is
> merely replacing the most standard option with a new one for no apparent
> reason - JP put a great deal of effort into making freewheeling a fully GNU
> compliant program which this change dis-mantles - this was not even done
> cleanly as some autotools files such as 'missing' and the original build
> instructions remain in the repo orphaned and no new instructions for
> building with cmake were added - i just compiled today `./configure && make
> && make install` from the debian sources on debian 9 with no problems so i
> dont see any valid reason for removing the autotools support files
>

 I switched to CMake because I don't know autotools and I have no intention
of learning or supporting this build system. I am not aware of any project
that still uses autotools except for legacy reasons. I was thinking of
porting Freewheeling to current SDL which would have broken the build
system but at this point I don't know if I am going to do anything major.


> * regarding openSSL - it is a well-known albeit contentious fact that
> linking a GPL program to openSSL is a violation of the GPL - according to
> the AUR PKGBUILD the original dependency on arch was 'gnutls' which is
> available in arch core and 'gnutls-openssl' is available in the AUR repos
> if needed so not only was it unnecessary to make this change in order to
> compile on arch but it makes the fork un-licensed and un-distributable - i
> can not (nor can anyone else) contribute to or download this fork until
> this issue is resolved


gnutls-openssl is badly broken on arch - that is to say that the current
version of gnutls is not the one that gnutls-openssl builds against,
installing it would remove a non trivial amount of software from my system
quite a few pieces of which I depend on. I was unaware of the restriction
of linking against OpenSSL, The only reason this is used is to generate MD5
hashes. Quite frankly I will see if there is another library that provides
this functionality or look into another hashing algorythm

Re: [Freewheeling-user] Freewheeling-user Digest, Vol 47, > Issue 1

[Bill A. <mr....@gm...>]

Michaël -

erm - no there is no documentation at all - perhaps this would be a good
time to make a screencast

it is very simple to use tho - that was the primary design goal for it to
be operated mainly with only one or two foot pedals - the only major
short-coming now is that i need to add MIDI support for that - i use it now
by putting an extra PC keyboard on the floor and stepping on the space-bar
to trigger recording - not the most elegant controller but it is fully
functional in this way so MIDI support has not been a priority

[Freewheeling-user] github fork

[Bill A. <mr....@gm...>]

it is good to see an interest in continuing development of freewheeling and
i have reviewed danni's fork on github and i must say that it has a number
of issues that should be addressed

* this first one is not terribly important but is worth noting - danni's
github fork was forked from another github user 'tnovelli' who added only
one commit three years ago and that commit was actually deleted on danni's
fork - based on tnovelli's github activity history it seem quite clear that
this person does not use github very much and is probably not interested in
being the upstream maintainer - in any case danni has never offered any
merge requests upstream - in a situation like this it would probably be
best for danni to delete the existing fork and recreate it as a stand-alone
base fork to avoid confusing users with an un-maintained upstream

* the github issue tracker is not enabled for either of the tnovelli and
kayosiii forks and so the mailing list is the only way for anyone to
contact the developers - i would suggest enabling the issue tracker for bug
reports in order to reserve the mailing list for general discussions

* regarding cmake - providing users options is a good thing in general and
i would not have made an issue of this except that the entire set of
autotools files were deleted which is not giving users any option but is
merely replacing the most standard option with a new one for no apparent
reason - JP put a great deal of effort into making freewheeling a fully GNU
compliant program which this change dis-mantles - this was not even done
cleanly as some autotools files such as 'missing' and the original build
instructions remain in the repo orphaned and no new instructions for
building with cmake were added - i just compiled today `./configure && make
&& make install` from the debian sources on debian 9 with no problems so i
dont see any valid reason for removing the autotools support files

* regarding openSSL - it is a well-known albeit contentious fact that
linking a GPL program to openSSL is a violation of the GPL - according to
the AUR PKGBUILD the original dependency on arch was 'gnutls' which is
available in arch core and 'gnutls-openssl' is available in the AUR repos
if needed so not only was it unnecessary to make this change in order to
compile on arch but it makes the fork un-licensed and un-distributable - i
can not (nor can anyone else) contribute to or download this fork until
this issue is resolved

Re: [Freewheeling-user] Freewheeling Wiki

[Bill A. <mr....@gm...>]

Wolfgang -

thanks for the tip - i looked that project over and it has one major flaw
which is that the developer has not licensed it - aside from that it is not
clear what it actually does anyways - it uses the pandoc program to do the
actual work and im pretty sure that pandoc can handle the conversions on
it's own

even with such convenience tools one should not expect the conversions to
be perfectly faithful and must be inspected and tested manually to ensure
all links, images, etc are still available and working

Re: [Freewheeling-user] Freewheeling-user Digest, Vol 47, > Issue 1

[Michaël C. <mi...@ca...>]

Quite nice!  Would you have a video of a live session with loopidity?

Cheers;
M.

On Sat, Oct 29, 2016 at 6:39 AM, Bill Auger <mr....@gm...> wrote:
> Jakub -
>
> i should think that freewheeling would run on raspbian OOTB - from what i
> know of it the raspbian OS is essentially a re-branded debian
>
> as for windows i would not expect too much trouble porting it - a few years
> back i wrote a similar program that is heavily inspired by freewheeling - i
> originally targeted *nix using SDL and JACK just as freewheeling and when i
> decided to try porting it to windows one day i found it was very easy to do
> - my looper has a very limited feature set compared to freewheeling designed
> for a narrow use-case - namely for hands-free live use with auto-record so i
> dont know if it would suit your needs but feel free to check it out if you
> like https://github.com/bill-auger/loopidity
>
>
> ------------------------------------------------------------------------------
> The Command Line: Reinvented for Modern Developers
> Did the resurgence of CLI tooling catch you by surprise?
> Reconnect with the command line and become more productive.
> Learn the new .NET and ASP.NET CLI. Get your free copy!
> http://sdm.link/telerik
> _______________________________________________
> Freewheeling-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>

Re: [Freewheeling-user] Freewheeling-user Digest, Vol 47, > Issue 1

[Bill A. <mr....@gm...>]

Jakub -

i should think that freewheeling would run on raspbian OOTB - from
what i know of it the raspbian OS is essentially a re-branded debian

as for windows i would not expect too much trouble porting it - a few
years back i wrote a similar program that is heavily inspired by
freewheeling - i originally targeted *nix using SDL and JACK just as
freewheeling and when i decided to try porting it to windows one day i
found it was very easy to do - my looper has a very limited feature
set compared to freewheeling designed for a narrow use-case - namely
for hands-free live use with auto-record so i dont know if it would
suit your needs but feel free to check it out if you like
https://github.com/bill-auger/loopidity

Re: [Freewheeling-user] Freewheeling Wiki

[Bill A. <mr....@gm...>]

i had completely remade the freewheeling wiki several years back when
sourceforge ate the original freewheeling wiki - JP was self-hosting that
version for a while but it looks like that is gone too - anyways i still
have all the files in mediawiki format if you want to host them - or
perhaps Danni Coy would like to put them on the github fork though it would
take some effort to make them compatible with github wiki format

[Freewheeling-user] Freewheeling Wiki

[Michaël C. <mi...@ca...>]

Hi there people!

I was a regular user of freewheeling around 2012, and I wish to
experience again the bliss of looping.  First, thanks a lot to Danni
Coy for his amazing work; compiling on Arch is now a breeze, and
everything runs smoothly.  Now, it's been a while since I last used
FW, and I wanted to read again the Wiki; alas, it's now well gone,
even on archive.org.  Does any of the (former?) maintainers have a
copy of it?  I do think there is still a great demand for such a
software (mind you, 28 downloads this week on Sourceforge), and an
accessible documentation is half the work.

Let this project rise from its hiatus!

M.

Re: [Freewheeling-user] Freewheeling-user Digest, Vol 47, Issue 2

[Danni C. <dan...@gm...>]

I am not personally planing to work on Windows support.

running FW on a small embedded system like R Pi is on my list of
things to do however.

On Sat, Oct 1, 2016 at 12:19 AM,
<fre...@li...> wrote:
> Send Freewheeling-user mailing list submissions to
>         fre...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/freewheeling-user
> or, via email, send a message with subject or body 'help' to
>         fre...@li...
>
> You can reach the person managing the list at
>         fre...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Freewheeling-user digest..."
>
>
> Today's Topics:
>
>    1. Re: Freewheeling-user Digest, Vol 47, Issue 1 (jk.man)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 30 Sep 2016 16:19:21 +0200 (CEST)
> From: "jk.man" <jk...@se...>
> Subject: Re: [Freewheeling-user] Freewheeling-user Digest, Vol 47,
>         Issue 1
> To: <fre...@li...>
> Message-ID: <RWv.YTMt.2M{dh8p{AJ6...@se...>
> Content-Type: text/plain; charset="utf-8"
>
>
> Danni Coy, big kudos for contributing to this project. I am glad someone
> takes care of this wonderful piece of software. Is there any way fw would
> one time in future work on windows too? ie - as VST plugin?
>
> Also anyone know if fw would be able to run on raspberry pi? I am thinking
> of making portable fw based loop station. Arduino is no option (tho i would
> love to have microcontroller based loop station) so raspberry came to my
> mind. Also some cheap netbooks wouldnt have enough cpu power for that ,
> right?
>
>
>
>
> Regards,
>
> Jakub
>
> long time user of freewheeling!
>
>
> ---------- P?vodn? zpr?va ----------
> Od: fre...@li...
> Komu: fre...@li...
> Datum: 29. 9. 2016 23:16:36
> P?edm?t: Freewheeling-user Digest, Vol 47, Issue 1
>
> "Send Freewheeling-user mailing list submissions to
> fre...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
> or, via email, send a message with subject or body 'help' to
> fre...@li...
>
> You can reach the person managing the list at
> fre...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Freewheeling-user digest..."
>
>
> Today's Topics:
>
> 1. lately I have been seeing this threading error a lot - (Danni Coy)
> 2. started working on freewheeling (Danni Coy)
> 3. Re: started working on freewheeling (Carlos sanchiavedraz)
> 4. Re: started working on freewheeling (Danni Coy)
> 5. Re: started working on freewheeling (Dan Easley)
> 6. Re: started working on freewheeling (Danni Coy)
> 7. Re: started working on freewheeling (Danni Coy)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 22 May 2013 23:22:15 +1000
> From: Danni Coy <dan...@gm...>
> Subject: [Freewheeling-user] lately I have been seeing this threading
> error a lot -
> To: fre...@li...
> Message-ID:
> <CAG...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I get this most of the time but not always. Can somebody give me some
> pointers as to what to look for as a fix.
>
> CORE: Register ringbuffer writer thread: 140289223677760
> CORE: Register ringbuffer #0: 0x1432720
> MEMMGR: Stacksize: 131072.
> CORE: Register ringbuffer writer thread: 140289224001280
> CORE: RingBuffer 0x1432720: Update reader and writer threads to 2
> CORE: ERROR: SRMWRingBuffer thread count mismatch. (writers 1 vs threads 2)
>
> The last little bit of debug I added myself, the first is the classes local
> copy
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Fri, 18 Jul 2014 16:36:36 +1000
> From: Danni Coy <dan...@gm...>
> Subject: [Freewheeling-user] started working on freewheeling
> To: fre...@li...
> Message-ID:
> <CAG...@ma...>
> Content-Type: text/plain; charset=UTF-8
>
> not making any huge promises
> but here is the github account https://github.com/kayosiii/freewheeling
>
> what has happened so far -
> Converted freewheeling to use cmake as the build system.
> A few tweaks to get freewheeling to build for me - might break on OSX
> fixed a threading problem which was causing freewheeling to
> usually not start up for me.
>
> What is next -
> improve joystick support.
>
> I have started a port to libsdl2 but that still requires me to get
> everything working...
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 18 Jul 2014 12:57:17 +0200
> From: Carlos sanchiavedraz <csa...@gm...>
> Subject: Re: [Freewheeling-user] started working on freewheeling
> To: Danni Coy <dan...@gm...>
> Cc: fre...@li...
> Message-ID:
> <CA+...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 2014-07-18 8:36 GMT+02:00 Danni Coy <dan...@gm...>:
>> not making any huge promises
>> but here is the github account https://github.com/kayosiii/freewheeling
>>
>> what has happened so far -
>> Converted freewheeling to use cmake as the build system.
>> A few tweaks to get freewheeling to build for me - might break on OSX
>> fixed a threading problem which was causing freewheeling to
>> usually not start up for me.
>>
>> What is next -
>> improve joystick support.
>>
>> I have started a port to libsdl2 but that still requires me to get
>> everything working...
>>
>> --------------------------------------------------------------------------
> ----
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> Freewheeling-user mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>
> That's great, Danni. Please keep on going and comment your progress.
> It would be great if Freewheeling get to (code)life again.
>
> --
>
> C. sanchiavedraZ:
> * NEW / NUEVO: www.sanchiavedraZ.com
> * Musix GNU+Linux: www.musix.es
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 18 Jul 2014 21:42:04 +1000
> From: Danni Coy <dan...@gm...>
> Subject: Re: [Freewheeling-user] started working on freewheeling
> To: Carlos sanchiavedraz <csa...@gm...>
> Cc: fre...@li...
> Message-ID:
> <CAG...@ma...>
> Content-Type: text/plain; charset=UTF-8
>
> ok improving joystick support is done...
>
> new syntax for your config files is
> <joystick var="[variable name]" id="[SDL device id string]" />
> freewheeling will find the device num matching the id this is equivelent to
> <declare var="[variable name]" type="int" init="[SDL device number]"/>
>
> multiple joysticks of the same type are supported eg both sides of the
> ebm-ps2 unit will work.
> if they are physically different devices though then you can't bank on
> the order being right
>
> On Fri, Jul 18, 2014 at 8:57 PM, Carlos sanchiavedraz
> <csa...@gm...> wrote:
>> 2014-07-18 8:36 GMT+02:00 Danni Coy <dan...@gm...>:
>>> not making any huge promises
>>> but here is the github account https://github.com/kayosiii/freewheeling
>>>
>>> what has happened so far -
>>> Converted freewheeling to use cmake as the build system.
>>> A few tweaks to get freewheeling to build for me - might break on OSX
>>> fixed a threading problem which was causing freewheeling to
>>> usually not start up for me.
>>>
>>> What is next -
>>> improve joystick support.
>>>
>>> I have started a port to libsdl2 but that still requires me to get
>>> everything working...
>>>
>>> -------------------------------------------------------------------------
> -----
>>> Want fast and easy access to all the code in your enterprise? Index and
>>> search up to 200,000 lines of code with a free copy of Black Duck
>>> Code Sight - the same software that powers the world's largest code
>>> search on Ohloh, the Black Duck Open Hub! Try it now.
>>> http://p.sf.net/sfu/bds
>>> _______________________________________________
>>> Freewheeling-user mailing list
>>> Fre...@li...
>>> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>>
>> That's great, Danni. Please keep on going and comment your progress.
>> It would be great if Freewheeling get to (code)life again.
>>
>> --
>>
>> C. sanchiavedraZ:
>> * NEW / NUEVO: www.sanchiavedraZ.com
>> * Musix GNU+Linux: www.musix.es
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 18 Jul 2014 10:11:48 -0400
> From: Dan Easley <dan...@gm...>
> Subject: Re: [Freewheeling-user] started working on freewheeling
> To: Carlos sanchiavedraz <csa...@gm...>
> Cc: Freewheeling-user <fre...@li...>, Danni
> Coy <dan...@gm...>
> Message-ID: <hf5...@em...>
> Content-Type: text/plain; charset=utf-8
>
> if jp is still monitoring this list: i'd love to have the original pd/max
> patches you used early on to prototype fweelin. (i think i'm remembering
> that right.) i'd love to build similar functionality as freewheeling into
> puredata (with which i am a novice) - i think the pd environment would
> facilitate os/device portability and code contribution.
>
> i don't want the above idea to distract from work towards freewheeling with
> its current codebase: it's always been a beautiful instrument, precisely
> envisioned and realized. configuration possibilities rival the best
> broadcast facility setups i've seen.
>
> i do wonder if some early design constrictions were required by the slower
> hardware/subsystems of the day. i'd like to see the gui in a windowed
> environment with each controller in its own window, some basic config
> options split off to other windows - sort of the real-time GIMP of loops. i'
> d love a pattern editor specifically to sequence scenes (one of my musical
> goals has been to tie the freewheeling approach to appalachian dance music,
> which is mostly AABB in form, but sometimes weirder - like AAABB or ABCB.)
>
> as a supportive end-user rather than a developer, i can't comment on the
> build system or threading methods, but can appreciate your sense of
> priorities. thank you!
>
>
> Carlos sanchiavedraz <csa...@gm...> wrote:
>
>>2014-07-18 8:36 GMT+02:00 Danni Coy <dan...@gm...>:
>>> not making any huge promises
>>> but here is the github account https://github.com/kayosiii/freewheeling
>>>
>>> what has happened so far -
>>> Converted freewheeling to use cmake as the build system.
>>> A few tweaks to get freewheeling to build for me - might break on OSX
>>> fixed a threading problem which was causing freewheeling to
>>> usually not start up for me.
>>>
>>> What is next -
>>> improve joystick support.
>>>
>>> I have started a port to libsdl2 but that still requires me to get
>>> everything working...
>>>
>>> -------------------------------------------------------------------------
> -----
>>> Want fast and easy access to all the code in your enterprise? Index and
>>> search up to 200,000 lines of code with a free copy of Black Duck
>>> Code Sight - the same software that powers the world's largest code
>>> search on Ohloh, the Black Duck Open Hub! Try it now.
>>> http://p.sf.net/sfu/bds
>>> _______________________________________________
>>> Freewheeling-user mailing list
>>> Fre...@li...
>>> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>>
>>That's great, Danni. Please keep on going and comment your progress.
>>It would be great if Freewheeling get to (code)life again.
>>
>>--
>>
>>C. sanchiavedraZ:
>>* NEW / NUEVO: www.sanchiavedraZ.com
>>* Musix GNU+Linux: www.musix.es
>>
>>---------------------------------------------------------------------------
> ---
>>Want fast and easy access to all the code in your enterprise? Index and
>>search up to 200,000 lines of code with a free copy of Black Duck
>>Code Sight - the same software that powers the world's largest code
>>search on Ohloh, the Black Duck Open Hub! Try it now.
>>http://p.sf.net/sfu/bds
>>_______________________________________________
>>Freewheeling-user mailing list
>>Fre...@li...
>>https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>
> ------------------------------
>
> Message: 6
> Date: Sat, 19 Jul 2014 10:17:42 +1000
> From: Danni Coy <dan...@gm...>
> Subject: Re: [Freewheeling-user] started working on freewheeling
> To: Dan Easley <dan...@gm...>
> Cc: Freewheeling-user <fre...@li...>
> Message-ID:
> <CAG...@ma...>
> Content-Type: text/plain; charset=UTF-8
>
> I have always taken the design as being the way it is for
> philosophical reasons rather than technical. Freewheeling's strengths
> have been that once set up properly you can use it in a performing
> environment just as you would with a piece of dedicated hardware. It
> keeps complex human computer interactions to a minimum which is
> something I want when I am standing up in a darkened room with a
> guitar in my hand.
>
> having said that - I do like your idea of being able to chain samples
> together in a loop.
>
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 30 Sep 2016 07:16:01 +1000
> From: Danni Coy <dan...@gm...>
> Subject: Re: [Freewheeling-user] started working on freewheeling
> To: Freewheeling-user <fre...@li...>
> Message-ID:
> <CAG...@ma...>
> Content-Type: text/plain; charset=UTF-8
>
> Some more updates,
>
> - switched from gnutls-openssl to ssl for md5 handling - this makes it
> possible to build freewheeling on current Arch Linux.
> - fixed all the compile warnings
> - fixed crash on deleting a loop when compiled with a recent version of GCC.
>
> I am back to working on a SDL2 port.
>
>
> On Fri, Jul 18, 2014 at 4:36 PM, Danni Coy <dan...@gm...> wrote:
>> not making any huge promises
>> but here is the github account https://github.com/kayosiii/freewheeling
>>
>> what has happened so far -
>> Converted freewheeling to use cmake as the build system.
>> A few tweaks to get freewheeling to build for me - might break on OSX
>> fixed a threading problem which was causing freewheeling to
>> usually not start up for me.
>>
>> What is next -
>> improve joystick support.
>>
>> I have started a port to libsdl2 but that still requires me to get
>> everything working...
>
>
>
> ------------------------------
>
> ----------------------------------------------------------------------------
> --
>
>
> ------------------------------
>
> _______________________________________________
> Freewheeling-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>
>
> End of Freewheeling-user Digest, Vol 47, Issue 1
> ************************************************"
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> ------------------------------------------------------------------------------
>
>
> ------------------------------
>
> _______________________________________________
> Freewheeling-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>
>
> End of Freewheeling-user Digest, Vol 47, Issue 2
> ************************************************

Re: [Freewheeling-user] Freewheeling-user Digest, Vol 47, Issue 1

[jk.man <jk...@se...>]

Danni Coy, big kudos for contributing to this project. I am glad someone 
takes care of this wonderful piece of software. Is there any way fw would 
one time in future work on windows too? ie - as VST plugin?

Also anyone know if fw would be able to run on raspberry pi? I am thinking 
of making portable fw based loop station. Arduino is no option (tho i would 
love to have microcontroller based loop station) so raspberry came to my 
mind. Also some cheap netbooks wouldnt have enough cpu power for that ,
right?




Regards,

Jakub

long time user of freewheeling!


---------- Původní zpráva ----------
Od: fre...@li...
Komu: fre...@li...
Datum: 29. 9. 2016 23:16:36
Předmět: Freewheeling-user Digest, Vol 47, Issue 1

"Send Freewheeling-user mailing list submissions to
fre...@li...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/freewheeling-user
or, via email, send a message with subject or body 'help' to
fre...@li...

You can reach the person managing the list at
fre...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Freewheeling-user digest..."


Today's Topics:

1. lately I have been seeing this threading error a lot - (Danni Coy)
2. started working on freewheeling (Danni Coy)
3. Re: started working on freewheeling (Carlos sanchiavedraz)
4. Re: started working on freewheeling (Danni Coy)
5. Re: started working on freewheeling (Dan Easley)
6. Re: started working on freewheeling (Danni Coy)
7. Re: started working on freewheeling (Danni Coy)


----------------------------------------------------------------------

Message: 1
Date: Wed, 22 May 2013 23:22:15 +1000
From: Danni Coy <dan...@gm...>
Subject: [Freewheeling-user] lately I have been seeing this threading
error a lot -
To: fre...@li...
Message-ID:
<CAG...@ma...>
Content-Type: text/plain; charset="iso-8859-1"

I get this most of the time but not always. Can somebody give me some
pointers as to what to look for as a fix.

CORE: Register ringbuffer writer thread: 140289223677760
CORE: Register ringbuffer #0: 0x1432720
MEMMGR: Stacksize: 131072.
CORE: Register ringbuffer writer thread: 140289224001280
CORE: RingBuffer 0x1432720: Update reader and writer threads to 2
CORE: ERROR: SRMWRingBuffer thread count mismatch. (writers 1 vs threads 2)

The last little bit of debug I added myself, the first is the classes local
copy
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Fri, 18 Jul 2014 16:36:36 +1000
From: Danni Coy <dan...@gm...>
Subject: [Freewheeling-user] started working on freewheeling
To: fre...@li...
Message-ID:
<CAG...@ma...>
Content-Type: text/plain; charset=UTF-8

not making any huge promises
but here is the github account https://github.com/kayosiii/freewheeling

what has happened so far -
Converted freewheeling to use cmake as the build system.
A few tweaks to get freewheeling to build for me - might break on OSX
fixed a threading problem which was causing freewheeling to
usually not start up for me.

What is next -
improve joystick support.

I have started a port to libsdl2 but that still requires me to get
everything working...



------------------------------

Message: 3
Date: Fri, 18 Jul 2014 12:57:17 +0200
From: Carlos sanchiavedraz <csa...@gm...>
Subject: Re: [Freewheeling-user] started working on freewheeling
To: Danni Coy <dan...@gm...>
Cc: fre...@li...
Message-ID:
<CA+...@ma...>
Content-Type: text/plain; charset=ISO-8859-1

2014-07-18 8:36 GMT+02:00 Danni Coy <dan...@gm...>:
> not making any huge promises
> but here is the github account https://github.com/kayosiii/freewheeling
>
> what has happened so far -
> Converted freewheeling to use cmake as the build system.
> A few tweaks to get freewheeling to build for me - might break on OSX
> fixed a threading problem which was causing freewheeling to
> usually not start up for me.
>
> What is next -
> improve joystick support.
>
> I have started a port to libsdl2 but that still requires me to get
> everything working...
>
> --------------------------------------------------------------------------
----
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Freewheeling-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freewheeling-user

That's great, Danni. Please keep on going and comment your progress.
It would be great if Freewheeling get to (code)life again.

-- 

C. sanchiavedraZ:
* NEW / NUEVO: www.sanchiavedraZ.com
* Musix GNU+Linux: www.musix.es



------------------------------

Message: 4
Date: Fri, 18 Jul 2014 21:42:04 +1000
From: Danni Coy <dan...@gm...>
Subject: Re: [Freewheeling-user] started working on freewheeling
To: Carlos sanchiavedraz <csa...@gm...>
Cc: fre...@li...
Message-ID:
<CAG...@ma...>
Content-Type: text/plain; charset=UTF-8

ok improving joystick support is done...

new syntax for your config files is
<joystick var="[variable name]" id="[SDL device id string]" />
freewheeling will find the device num matching the id this is equivelent to
<declare var="[variable name]" type="int" init="[SDL device number]"/>

multiple joysticks of the same type are supported eg both sides of the
ebm-ps2 unit will work.
if they are physically different devices though then you can't bank on
the order being right

On Fri, Jul 18, 2014 at 8:57 PM, Carlos sanchiavedraz
<csa...@gm...> wrote:
> 2014-07-18 8:36 GMT+02:00 Danni Coy <dan...@gm...>:
>> not making any huge promises
>> but here is the github account https://github.com/kayosiii/freewheeling
>>
>> what has happened so far -
>> Converted freewheeling to use cmake as the build system.
>> A few tweaks to get freewheeling to build for me - might break on OSX
>> fixed a threading problem which was causing freewheeling to
>> usually not start up for me.
>>
>> What is next -
>> improve joystick support.
>>
>> I have started a port to libsdl2 but that still requires me to get
>> everything working...
>>
>> -------------------------------------------------------------------------
-----
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> Freewheeling-user mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>
> That's great, Danni. Please keep on going and comment your progress.
> It would be great if Freewheeling get to (code)life again.
>
> --
>
> C. sanchiavedraZ:
> * NEW / NUEVO: www.sanchiavedraZ.com
> * Musix GNU+Linux: www.musix.es



------------------------------

Message: 5
Date: Fri, 18 Jul 2014 10:11:48 -0400
From: Dan Easley <dan...@gm...>
Subject: Re: [Freewheeling-user] started working on freewheeling
To: Carlos sanchiavedraz <csa...@gm...>
Cc: Freewheeling-user <fre...@li...>, Danni
Coy <dan...@gm...>
Message-ID: <hf5...@em...>
Content-Type: text/plain; charset=utf-8

if jp is still monitoring this list: i'd love to have the original pd/max 
patches you used early on to prototype fweelin. (i think i'm remembering 
that right.) i'd love to build similar functionality as freewheeling into 
puredata (with which i am a novice) - i think the pd environment would 
facilitate os/device portability and code contribution.

i don't want the above idea to distract from work towards freewheeling with 
its current codebase: it's always been a beautiful instrument, precisely 
envisioned and realized. configuration possibilities rival the best 
broadcast facility setups i've seen.

i do wonder if some early design constrictions were required by the slower 
hardware/subsystems of the day. i'd like to see the gui in a windowed 
environment with each controller in its own window, some basic config 
options split off to other windows - sort of the real-time GIMP of loops. i'
d love a pattern editor specifically to sequence scenes (one of my musical 
goals has been to tie the freewheeling approach to appalachian dance music, 
which is mostly AABB in form, but sometimes weirder - like AAABB or ABCB.) 

as a supportive end-user rather than a developer, i can't comment on the 
build system or threading methods, but can appreciate your sense of 
priorities. thank you!


Carlos sanchiavedraz <csa...@gm...> wrote:

>2014-07-18 8:36 GMT+02:00 Danni Coy <dan...@gm...>:
>> not making any huge promises
>> but here is the github account https://github.com/kayosiii/freewheeling
>>
>> what has happened so far -
>> Converted freewheeling to use cmake as the build system.
>> A few tweaks to get freewheeling to build for me - might break on OSX
>> fixed a threading problem which was causing freewheeling to
>> usually not start up for me.
>>
>> What is next -
>> improve joystick support.
>>
>> I have started a port to libsdl2 but that still requires me to get
>> everything working...
>>
>> -------------------------------------------------------------------------
-----
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> Freewheeling-user mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>
>That's great, Danni. Please keep on going and comment your progress.
>It would be great if Freewheeling get to (code)life again.
>
>-- 
>
>C. sanchiavedraZ:
>* NEW / NUEVO: www.sanchiavedraZ.com
>* Musix GNU+Linux: www.musix.es
>
>---------------------------------------------------------------------------
---
>Want fast and easy access to all the code in your enterprise? Index and
>search up to 200,000 lines of code with a free copy of Black Duck
>Code Sight - the same software that powers the world's largest code
>search on Ohloh, the Black Duck Open Hub! Try it now.
>http://p.sf.net/sfu/bds
>_______________________________________________
>Freewheeling-user mailing list
>Fre...@li...
>https://lists.sourceforge.net/lists/listinfo/freewheeling-user

------------------------------

Message: 6
Date: Sat, 19 Jul 2014 10:17:42 +1000
From: Danni Coy <dan...@gm...>
Subject: Re: [Freewheeling-user] started working on freewheeling
To: Dan Easley <dan...@gm...>
Cc: Freewheeling-user <fre...@li...>
Message-ID:
<CAG...@ma...>
Content-Type: text/plain; charset=UTF-8

I have always taken the design as being the way it is for
philosophical reasons rather than technical. Freewheeling's strengths
have been that once set up properly you can use it in a performing
environment just as you would with a piece of dedicated hardware. It
keeps complex human computer interactions to a minimum which is
something I want when I am standing up in a darkened room with a
guitar in my hand.

having said that - I do like your idea of being able to chain samples
together in a loop.



------------------------------

Message: 7
Date: Fri, 30 Sep 2016 07:16:01 +1000
From: Danni Coy <dan...@gm...>
Subject: Re: [Freewheeling-user] started working on freewheeling
To: Freewheeling-user <fre...@li...>
Message-ID:
<CAG...@ma...>
Content-Type: text/plain; charset=UTF-8

Some more updates,

- switched from gnutls-openssl to ssl for md5 handling - this makes it
possible to build freewheeling on current Arch Linux.
- fixed all the compile warnings
- fixed crash on deleting a loop when compiled with a recent version of GCC.

I am back to working on a SDL2 port.


On Fri, Jul 18, 2014 at 4:36 PM, Danni Coy <dan...@gm...> wrote:
> not making any huge promises
> but here is the github account https://github.com/kayosiii/freewheeling
>
> what has happened so far -
> Converted freewheeling to use cmake as the build system.
> A few tweaks to get freewheeling to build for me - might break on OSX
> fixed a threading problem which was causing freewheeling to
> usually not start up for me.
>
> What is next -
> improve joystick support.
>
> I have started a port to libsdl2 but that still requires me to get
> everything working...



------------------------------

----------------------------------------------------------------------------
--


------------------------------

_______________________________________________
Freewheeling-user mailing list
Fre...@li...
https://lists.sourceforge.net/lists/listinfo/freewheeling-user


End of Freewheeling-user Digest, Vol 47, Issue 1
************************************************"

Re: [Freewheeling-user] started working on freewheeling

[Danni C. <dan...@gm...>]

Some more updates,

- switched from gnutls-openssl to ssl for md5 handling - this makes it
possible to build freewheeling on current Arch Linux.
- fixed all the compile warnings
- fixed crash on deleting a loop when compiled with a recent version of GCC.

I am back to working on a SDL2 port.


On Fri, Jul 18, 2014 at 4:36 PM, Danni Coy <dan...@gm...> wrote:
> not making any huge promises
> but here is the github account https://github.com/kayosiii/freewheeling
>
> what has happened so far -
>     Converted freewheeling to use cmake as the build system.
>     A few tweaks to get freewheeling to build for me - might break on OSX
>     fixed a threading problem which was causing freewheeling to
> usually not start up for me.
>
> What is next -
>     improve joystick support.
>
> I have started a port to libsdl2 but that still requires me to get
> everything working...

Re: [Freewheeling-user] started working on freewheeling

[Danni C. <dan...@gm...>]

I have always taken the design as being the way it is for
philosophical reasons rather than technical. Freewheeling's strengths
have been that once set up properly you can use it in a performing
environment just as you would with a piece of dedicated hardware. It
keeps complex human computer interactions to a minimum which is
something I want when I am standing up in a darkened room with a
guitar in my hand.

having said that - I do like your idea of being able to chain samples
together in a loop.

Re: [Freewheeling-user] started working on freewheeling

[Dan E. <dan...@gm...>]

if jp is still monitoring this list: i'd love to have the original pd/max patches you used early on to prototype fweelin. (i think i'm remembering that right.)  i'd love to build similar functionality as freewheeling into puredata (with which i am a novice) - i think the pd environment would facilitate os/device portability and code contribution.

i don't want the above idea to distract from work towards freewheeling with its current codebase: it's always been a beautiful instrument, precisely envisioned and realized.  configuration possibilities rival the best broadcast facility setups i've seen.

i do wonder if some early design constrictions were required by the slower hardware/subsystems of the day.  i'd like to see the gui in a windowed environment with each controller in its own window, some basic config options split off to other windows - sort of the real-time GIMP of loops.  i'd love a pattern editor specifically to sequence scenes (one of my musical goals has been to tie the freewheeling approach to appalachian dance music, which is mostly AABB in form, but sometimes weirder - like AAABB or ABCB.) 

as a supportive end-user rather than a developer, i can't comment on the build system or threading methods, but can appreciate your sense of priorities.  thank you!


Carlos sanchiavedraz <csa...@gm...> wrote:

>2014-07-18 8:36 GMT+02:00 Danni Coy <dan...@gm...>:
>> not making any huge promises
>> but here is the github account https://github.com/kayosiii/freewheeling
>>
>> what has happened so far -
>>     Converted freewheeling to use cmake as the build system.
>>     A few tweaks to get freewheeling to build for me - might break on OSX
>>     fixed a threading problem which was causing freewheeling to
>> usually not start up for me.
>>
>> What is next -
>>     improve joystick support.
>>
>> I have started a port to libsdl2 but that still requires me to get
>> everything working...
>>
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> Freewheeling-user mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>
>That's great, Danni. Please keep on going and comment your progress.
>It would be great if Freewheeling get to (code)life again.
>
>-- 
>
>C. sanchiavedraZ:
>* NEW / NUEVO:     www.sanchiavedraZ.com
>* Musix GNU+Linux: www.musix.es
>
>------------------------------------------------------------------------------
>Want fast and easy access to all the code in your enterprise? Index and
>search up to 200,000 lines of code with a free copy of Black Duck
>Code Sight - the same software that powers the world's largest code
>search on Ohloh, the Black Duck Open Hub! Try it now.
>http://p.sf.net/sfu/bds
>_______________________________________________
>Freewheeling-user mailing list
>Fre...@li...
>https://lists.sourceforge.net/lists/listinfo/freewheeling-user

Re: [Freewheeling-user] started working on freewheeling

[Danni C. <dan...@gm...>]

ok improving joystick support is done...

new syntax for your config files is
<joystick var="[variable name]" id="[SDL device id string]" />
freewheeling will find the device num matching the id this is equivelent to
<declare var="[variable name]" type="int" init="[SDL device number]"/>

multiple joysticks of the same type are supported eg both sides of the
ebm-ps2 unit will work.
if they are physically different devices though then you can't bank on
the order being right

On Fri, Jul 18, 2014 at 8:57 PM, Carlos sanchiavedraz
<csa...@gm...> wrote:
> 2014-07-18 8:36 GMT+02:00 Danni Coy <dan...@gm...>:
>> not making any huge promises
>> but here is the github account https://github.com/kayosiii/freewheeling
>>
>> what has happened so far -
>>     Converted freewheeling to use cmake as the build system.
>>     A few tweaks to get freewheeling to build for me - might break on OSX
>>     fixed a threading problem which was causing freewheeling to
>> usually not start up for me.
>>
>> What is next -
>>     improve joystick support.
>>
>> I have started a port to libsdl2 but that still requires me to get
>> everything working...
>>
>> ------------------------------------------------------------------------------
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> _______________________________________________
>> Freewheeling-user mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freewheeling-user
>
> That's great, Danni. Please keep on going and comment your progress.
> It would be great if Freewheeling get to (code)life again.
>
> --
>
> C. sanchiavedraZ:
> * NEW / NUEVO:     www.sanchiavedraZ.com
> * Musix GNU+Linux: www.musix.es

Re: [Freewheeling-user] started working on freewheeling

[Carlos s. <csa...@gm...>]

2014-07-18 8:36 GMT+02:00 Danni Coy <dan...@gm...>:
> not making any huge promises
> but here is the github account https://github.com/kayosiii/freewheeling
>
> what has happened so far -
>     Converted freewheeling to use cmake as the build system.
>     A few tweaks to get freewheeling to build for me - might break on OSX
>     fixed a threading problem which was causing freewheeling to
> usually not start up for me.
>
> What is next -
>     improve joystick support.
>
> I have started a port to libsdl2 but that still requires me to get
> everything working...
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Freewheeling-user mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freewheeling-user

That's great, Danni. Please keep on going and comment your progress.
It would be great if Freewheeling get to (code)life again.

-- 

C. sanchiavedraZ:
* NEW / NUEVO:     www.sanchiavedraZ.com
* Musix GNU+Linux: www.musix.es