qutecsound-devel Mailing List for CsoundQt
Brought to you by:
mantaraya36
Menu
▾
▴
qutecsound-devel — Developer mailing list for QuteCsound
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2014 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
(25) |
Mar
(43) |
Apr
(6) |
May
(17) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
(9) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
(1) |
Aug
(3) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
(5) |
Apr
(6) |
May
(2) |
Jun
(3) |
Jul
(8) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(4) |
Aug
(7) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: joachim h. <jh...@jo...> - 2022-01-22 22:15:40
|
strange --- i did a complete rebuild of CsoundQt (with QtCreator 4.19.0 / Qt 5.12.2), but the problem with the syntax highlighting persists. there was no problem in the previous version (1.0.0.-rc2). when i choose breeze-dark, the toolbar looke like the attaeched screenshot. don't you have the annoying problem with confirmation in closing? when i have three tabs, and i only open csoundqt, and close immediately, i have to tell each single tab that i do not want to save changes (which do not exist). i am wondering why we have so different behaviour. did you also build from develop? or are you on another branch? j On 22/01/2022 18:37, Eduardo Moguillansky wrote: > Tests here do not reflect your problems with syntax highlighting. Here > is what I see: > > Also with "classic" color theme: > > Regarding the theme, you say "breeze-dark" is not working. Can you be > more specific? If you have a dark theme on your desktop, can you post a > screen shot of how csoundqt looks with the dark theme? > > Thanks for testing! > > Eduardo > > > > On 22.01.22 12:23, joachim heintz wrote: >> ...forgot screenshot ... >> >> On 22/01/2022 11:39, Eduardo Moguillansky wrote: >>> >>> On 22.01.22 10:32, joachim heintz wrote: >>>> hi - >>>> >>>> i saw the message about >>>> https://github.com/CsoundQt/CsoundQt/releases/tag/v1.1.0 and pulled >>>> and built from develop. this all went fine, but i have two questions: >>>> >>>> 1. Help > About CsoundQt still shows 1.0.0-rc2. has this just been >>>> forgotten, or do i have to build from another source? >>> >>> Thanks, yes this was forgotten. >>> >>>> >>>> 2. i usually have my UDOs in an included file, like >>>> #include "udos.inc" >>>> is it easy to extend syntax highlighting to inlcuded files? >>>> >>> This would be nice, indeed. It is not difficult itself, but in order >>> to not become too unresponsive it might not be a live update as it is >>> now when editing a source --which means that you might need to do >>> some sort of "reload" action in order for opcodes in included files >>> to be updated if such files are modified during editing another file. >>> >>>> once i am sure this is the correct build, i can send more feedbacks >>>> from tests (dark theme is not working for me, for instance). >>> >>> Support for dark theme here means that if you are using a dark theme >>> already (in your desktop) csoundqt should adapt certain things to >>> make such a theme is usable. This is a very fragile situation in >>> general, most particularly in linux under gnome and I have literally >>> no idea how it works under macos, so help is really needed here. What >>> was done is to adapt the styling to let the underlying palette take >>> over and removing certain assumptions regarding csoundqt being mostly >>> a dark text over light background. >>> >>> NB: the "theme" choice in the settings is limited to the icon theme >>> and should probably be renamed to reflect this. >>> >>> >>>> >>>> best - >>>> joachim |
|
From: joachim h. <jh...@jo...> - 2022-01-22 11:23:21
|
...forgot screenshot ... On 22/01/2022 11:39, Eduardo Moguillansky wrote: > > On 22.01.22 10:32, joachim heintz wrote: >> hi - >> >> i saw the message about >> https://github.com/CsoundQt/CsoundQt/releases/tag/v1.1.0 and pulled >> and built from develop. this all went fine, but i have two questions: >> >> 1. Help > About CsoundQt still shows 1.0.0-rc2. has this just been >> forgotten, or do i have to build from another source? > > Thanks, yes this was forgotten. > >> >> 2. i usually have my UDOs in an included file, like >> #include "udos.inc" >> is it easy to extend syntax highlighting to inlcuded files? >> > This would be nice, indeed. It is not difficult itself, but in order to > not become too unresponsive it might not be a live update as it is now > when editing a source --which means that you might need to do some sort > of "reload" action in order for opcodes in included files to be updated > if such files are modified during editing another file. > >> once i am sure this is the correct build, i can send more feedbacks >> from tests (dark theme is not working for me, for instance). > > Support for dark theme here means that if you are using a dark theme > already (in your desktop) csoundqt should adapt certain things to make > such a theme is usable. This is a very fragile situation in general, > most particularly in linux under gnome and I have literally no idea how > it works under macos, so help is really needed here. What was done is to > adapt the styling to let the underlying palette take over and removing > certain assumptions regarding csoundqt being mostly a dark text over > light background. > > NB: the "theme" choice in the settings is limited to the icon theme and > should probably be renamed to reflect this. > > >> >> best - >> joachim |
|
From: joachim h. <jh...@jo...> - 2022-01-22 11:22:42
|
allright - thanks for explaining.
here some issues on a first test. i have built from current develop on
debian 11.
1. syntax highlighting is convoluted and mostly missing, as can be seen
in the screenshot:
only "invalue" and "out" are highlighted, not "poscil", "port",
"vdelayx" and "schedule".
this is with "classic" color theme, but no change for "light" and "dark".
2. any open tab ALWAYS asks for confirming modifications, even if no
edit at all has been done.
3. "breeze-dark" is not working. as you mention, probably because i
have a dark theme already ("Debian" on LXQt). i agree it should be made
clear that this refers only to the toolbar.
cheers -
joachim
On 22/01/2022 11:39, Eduardo Moguillansky wrote:
>
> On 22.01.22 10:32, joachim heintz wrote:
>> hi -
>>
>> i saw the message about
>> https://github.com/CsoundQt/CsoundQt/releases/tag/v1.1.0 and pulled
>> and built from develop. this all went fine, but i have two questions:
>>
>> 1. Help > About CsoundQt still shows 1.0.0-rc2. has this just been
>> forgotten, or do i have to build from another source?
>
> Thanks, yes this was forgotten.
>
>>
>> 2. i usually have my UDOs in an included file, like
>> #include "udos.inc"
>> is it easy to extend syntax highlighting to inlcuded files?
>>
> This would be nice, indeed. It is not difficult itself, but in order to
> not become too unresponsive it might not be a live update as it is now
> when editing a source --which means that you might need to do some sort
> of "reload" action in order for opcodes in included files to be updated
> if such files are modified during editing another file.
>
>> once i am sure this is the correct build, i can send more feedbacks
>> from tests (dark theme is not working for me, for instance).
>
> Support for dark theme here means that if you are using a dark theme
> already (in your desktop) csoundqt should adapt certain things to make
> such a theme is usable. This is a very fragile situation in general,
> most particularly in linux under gnome and I have literally no idea how
> it works under macos, so help is really needed here. What was done is to
> adapt the styling to let the underlying palette take over and removing
> certain assumptions regarding csoundqt being mostly a dark text over
> light background.
>
> NB: the "theme" choice in the settings is limited to the icon theme and
> should probably be renamed to reflect this.
>
>
>>
>> best -
>> joachim
|
|
From: joachim h. <jh...@jo...> - 2022-01-22 09:59:05
|
hi - i saw the message about https://github.com/CsoundQt/CsoundQt/releases/tag/v1.1.0 and pulled and built from develop. this all went fine, but i have two questions: 1. Help > About CsoundQt still shows 1.0.0-rc2. has this just been forgotten, or do i have to build from another source? 2. i usually have my UDOs in an included file, like #include "udos.inc" is it easy to extend syntax highlighting to inlcuded files? once i am sure this is the correct build, i can send more feedbacks from tests (dark theme is not working for me, for instance). best - joachim |
|
From: joachim h. <jh...@jo...> - 2021-10-14 17:30:26
|
hi tarmo - i checked today the dmg build which you have on your website on a mac (11.6). there is a problem with the audio module. portaudio reports an "internal error -9998". jack is not recognized although it runs. the previous csoundqt 0-9-8-1 runs ok on the same machine. i can check again whenever you have a new version. best - joachim |
|
From: joachim h. <jh...@jo...> - 2021-08-23 23:23:15
|
which kind of documentation do you mean? On 23/08/2021 21:59, Tarmo Johannes wrote: > Hi! > > I merged the changes to develop and pushed to github. Now the only hard > thing is to write documentation about it... > > tarmo > > Kontakt joachim heintz (<jh...@jo... > <mailto:jh...@jo...>>) kirjutas kuupäeval N, 19. august 2021 > kell 16:10: > > i did some work on the examples and just pushed. so please merge any > time you like. > > just to let you know i get these linker issues at the very end of my > compilation: > > /usr/bin/ld: /home/jh/src/Qt5/5.15.2/gcc_64/lib/libQt5WebEngineCore.so: > .dynsym local symbol at index 3 (>= sh_info of 3) > /usr/bin/ld: /home/jh/src/Qt5/5.15.2/gcc_64/lib/libQt5WebEngineCore.so: > .dynsym local symbol at index 4 (>= sh_info of 3) > ... etc up to > /usr/bin/ld: /home/jh/src/Qt5/5.15.2/gcc_64/lib/libQt5WebEngineCore.so: > .dynsym local symbol at index 20 (>= sh_info of 3) > > not sure it is in any way related to the examples (probably not). it > does not prevent me from building CsoundQt either. > > cheers - > j > > > On 17/08/2021 22:34, joachim heintz wrote: > > yes definitely! i will try your changes and clean some examples > > tomorrow; if all is ok please merge then. > > cheers - > > j > > > > > > On 16/08/2021 23:02, Tarmo Johannes wrote: > >> Hi! > >> > >> Thanks for noticing this! There was a hardcoded limit to filling > the > >> menus, I increased that to 256, so even big folders should build up > >> nicely. > >> Pushed to git. > >> > >> Does it seem OK to merge it to the develop branch (after some > tiding > >> up) soon? > >> > >> Best! > >> tarmo > >> > >> Kontakt joachim heintz (<jh...@jo... > <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>>>) > kirjutas kuupäeval R, 13. august 2021 > >> kell 22:54: > >> > >> wonderful! > >> > >> i checked several examples, and all worked fine =) > >> > >> i found one issue in the FLOSS examples, 05 Sound Modification: > >> i see only examples up to 05H02 in the dropdown menu. > >> the other examples (05H03 and following) are in the source > folder but > >> not in my built. > >> > >> can you check if it is the same for you? > >> > >> (please pull first; idid some small changes to some examples.) > >> > >> cheers - > >> joachim > >> > >> > >> > >> > >> On 12/08/2021 22:37, Tarmo Johannes wrote: > >> > Hi! > >> > > >> > I finished now a new system for managing examples, it is > done > >> at the > >> > moment in separate path "examples": > >> > https://github.com/CsoundQt/CsoundQt/tree/examples > <https://github.com/CsoundQt/CsoundQt/tree/examples> > >> <https://github.com/CsoundQt/CsoundQt/tree/examples > <https://github.com/CsoundQt/CsoundQt/tree/examples>> > >> > <https://github.com/CsoundQt/CsoundQt/tree/examples > <https://github.com/CsoundQt/CsoundQt/tree/examples> > >> <https://github.com/CsoundQt/CsoundQt/tree/examples > <https://github.com/CsoundQt/CsoundQt/tree/examples>>> > >> > > >> > 1) I moved the examples from source root directory to > >> > src/Examples/CsoundQt (maybe there is a better name for it, > >> Joachim?). > >> > src/Examples will be the place where we can put all the > examples > >> from now on > >> > 2) the Examples menu is filled automatically according the > >> subfolders in > >> > the Examples path. It means we can easily add new categories, > >> regroup > >> > the examples etc - managing the examples does not require > >> touching the > >> > CsoundQt source code any more > >> > 3) I moved source materials from FLOSS ans McCurdy one > level > >> up, to > >> > src/Examples/SourceMateriald and got rid of the > duplicates this > >> way. I > >> > changed the current references to ../../SourceMaterials in > >> csd-s. New > >> > source materials can be put there, too, if needed for new > >> examples. > >> > 4) The examples folder should be found automatically in most > >> cases, but > >> > for special occasions, I added an option under > >> > Configuration->Environment to set the path of examples > folder, if > >> user > >> > needs to. > >> > > >> > I still think it is good to move the examples out to > another repo > >> > (CsoundQt/Examples perhaps?) and use it as a git > submodule - so > >> it can > >> > be pulled easily together with CsoundQt source but it is > >> possible to > >> > pull also just source, without examples (this is probably > good > >> for linux > >> > packagers), too. The benefit is that managing examples gets > >> independent, > >> > you can always download newest version from git as zip, > also it > >> gets > >> > more easy and clearer to handle, so we can hope to get more > >> people to > >> > contribute and take care of the example base. I don't > know how > >> to do > >> > the submodule thing, to be honest, but I will figure out, > if you > >> agree > >> > it makes sense. > >> > > >> > Joachim, if you have a chance to test if the examples > work, would > >> be great! > >> > > >> > tarmo > >> > > >> > > >> > Kontakt joachim heintz (<jh...@jo... > <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>> > >> > <mailto:jh...@jo... <mailto:jh...@jo...> > <mailto:jh...@jo... <mailto:jh...@jo...>>>>) > >> kirjutas kuupäeval E, 2. august 2021 kell > >> > 23:11: > >> > > >> > hi - > >> > > >> > sounds great what you say about your work on this! > thanks a > >> lot for > >> > doing it so fast. > >> > > >> > i am not sure i understand your discussion well, > about the > >> own repo for > >> > the examples. but i'd definitely prefer to have the > examples > >> > *included* > >> > in CsoundQt, as it was. i think the examples are one > of the > >> pros for > >> > CsoundQt, and we should not require to be always > online or > >> something (i > >> > just was in the middle of germany and had no internet > access, > >> not even > >> > mobile ...). > >> > > >> > cheers - > >> > joachim > >> > > >> > > >> > > >> > On 02/08/2021 17:01, Tarmo Johannes wrote: > >> > > Hi! > >> > > > >> > > 1) Started work on moving all examples to > src/Examples. I > >> do it in a > >> > > separate branch (examples) just for any case. I > have not > >> pushed > >> > it yet > >> > > though. > >> > > > >> > > I moved the main examples to Examples/CsoundQt and > >> expanded a bit > >> > the > >> > > folders where the examples can be found.. The only > >> example/csd > >> > that has > >> > > to be delivered within the resources with the > binary is > >> Eduardo's > >> > > AudioMidiTest.csd as I find it absolutely > necessary to > >> have it > >> > by the > >> > > program in all times. > >> > > > >> > > The menu gets populated automatically quite fine, it > >> needs some > >> > more > >> > > work (Getting Started submenus and Stria Synth), I > moved > >> all > >> > resources > >> > > files to Examples/SourceMaterials Next step is to > change > >> McCurdy and > >> > > Floss examples so that they would use the one path and > >> would not > >> > > duplicate the files. > >> > > > >> > > Now I have to finish but hopefully I will put it > out for > >> testing > >> > soon. > >> > > > >> > > > >> > > 2) Moving the examples to separate git repo is > very good > >> idea, I > >> > think. > >> > > Eduardo, did you have in mind that it is the CsoundQt > >> program > >> > that does > >> > > the git pull or it the user/packager who pulls it > via git > >> submodules > >> > > before building? The first case won't probably > work since > >> most of > >> > users > >> > > don't have git installed. > >> > > > >> > > > >> > > Greetings, > >> > > tarmo > >> > > > >> > > Kontakt Eduardo Moguillansky > >> (<edu...@gm... > <mailto:edu...@gm...> > >> <mailto:edu...@gm... > <mailto:edu...@gm...>> > >> > <mailto:edu...@gm... > <mailto:edu...@gm...> > >> <mailto:edu...@gm... > <mailto:edu...@gm...>>> > >> > > <mailto:edu...@gm... > <mailto:edu...@gm...> > >> <mailto:edu...@gm... > <mailto:edu...@gm...>> > >> > <mailto:edu...@gm... > <mailto:edu...@gm...> > >> <mailto:edu...@gm... > <mailto:edu...@gm...>>>>>) kirjutas kuupäeval R, 30. > >> > > juuli 2021 kell 14:42: > >> > > > >> > > Another idea: > >> > > > >> > > Maybe the examples could be moved to their own > repo. > >> In linux > >> > (or in > >> > > the other platforms as well) this repo could be > >> cloned/pulled by > >> > > csoundqt. Then the examples and their > resources would > >> be in > >> > > predictable places and the resources can be > accessed by > >> > relative paths. > >> > > > >> > > eduardo > >> > > > >> > > On 30.07.21 13:35, Tarmo Johannes wrote: > >> > >> Yes, > >> > >> > >> > >> I agree it makes sense to rework it. On MacOs > and > >> Windows > >> > with the > >> > >> installers it is no problem, on Linux we must > make > >> sure that the > >> > >> examples can be found, perhaps there should be an > >> option in the > >> > >> configuration. > >> > >> > >> > >> Greetings, > >> > >> Tarmo > >> > >> > >> > >> R, 30. juuli 2021 13:43 joachim heintz > >> <jh...@jo... <mailto:jh...@jo...> > <mailto:jh...@jo... <mailto:jh...@jo...>> > >> > <mailto:jh...@jo... > <mailto:jh...@jo...> <mailto:jh...@jo... > <mailto:jh...@jo...>>> > >> > >> <mailto:jh...@jo... > <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>> > <mailto:jh...@jo... <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>>>>> > >> > kirjutas: > >> > >> > >> > >> thanks for the reply, tarmo! > >> > >> > >> > >> the inclusion of sound files into some of > the csd > >> > examples is > >> > >> not only > >> > >> an issue for ImitativeAdditive.csd. > there are a > >> couple > >> > of other > >> > >> examples which i would like to change, > too. so > >> moving the > >> > >> examples to > >> > >> another category is no solution. > >> > >> > >> > >> after your explanation i have two ideas: > >> > >> > >> > >> 1. would it be possible (and not too hard) to > >> treat the > >> > current > >> > >> /examples in the same way as > src/Examples? this > >> means that > >> > >> they are not > >> > >> compiled, but just copied. i think this is > >> actually also > >> > >> better because > >> > >> then the users can access the csd files. > and we > >> could > >> > add the > >> > >> sound > >> > >> files in a similar way i did it with the > floss > >> manual > >> > examples. > >> > >> i think this would be the best solution. > >> > >> > >> > >> 2. if not possible, the method you described > >> should be > >> > allright: > >> > >> "Thus the fox.wav added this way should be > >> copied (by > >> > Qt) to a > >> > >> temporary > >> > >> location first and the path should be > given to > >> Csound via > >> > >> --env:SSDIR+= > >> > >> or setting environment variable." > >> > >> > >> > >> let me know what you think; cheers - > >> > >> > >> > >> joachim > >> > >> > >> > >> > >> > >> On 30/07/2021 11:34, Tarmo Johannes wrote: > >> > >> > Hi! > >> > >> > > >> > >> > Sorry, I did see your email but waited > for a > >> good > >> > moment to > >> > >> try it out. > >> > >> > I did not yet but for now I can explain the > >> background: > >> > >> > > >> > >> > there are two places for examples - > <CsoundQt > >> source > >> > >> folder>/examples > >> > >> > and and <source>/src/Examples > >> > >> > > >> > >> > The first gets compiled as binary code to > >> CsoundQt as Qt > >> > >> resource, the > >> > >> > second, the "extended examples" (Floss, > McCurdy, > >> > Stria) gets > >> > >> installed > >> > >> > to the system as normal folders. > >> > >> > > >> > >> > The problem is that Qt can read from the > >> compiled-in > >> > >> resource but Csound > >> > >> > not. Thus the fox.wav added this way > should be > >> copied (by > >> > >> Qt) to a > >> > >> > temporary location first and the path > should be > >> given to > >> > >> Csound via > >> > >> > --env:SSDIR+= or setting environment > variable. > >> Quite some > >> > >> hassle. > >> > >> > > >> > >> > One solution is to add the material to > the end > >> of csd with > >> > >> the <CsFileB > >> > >> > filename="fox.wav"></CsFileB> (I forgot > which > >> tool > >> > helps to > >> > >> do it) (like > >> > >> > in case of > Synths/Scanned_Synthes_Sandbox.csd) > >> > >> > but anyway - I think at some point > Andés and > >> René > >> > discussed > >> > >> it and > >> > >> > decided that no large source materials are > >> added to > >> > >> src/examples - it > >> > >> > makes just the CsoundQt binary grow. > >> > >> > > >> > >> > Much simpler way would be to put > >> > ImitiativeAdditive.csd into > >> > >> the real > >> > >> > folder under "src/Examples" where > fox.wav is > >> is in > >> > >> > src/Examples/FLOSS Manual > >> Examples/SourceMaterials/ > >> > and set > >> > >> the SSDIR > >> > >> > relative to the csd. Perhaps it makes > sense to > >> do another > >> > >> folder like: > >> > >> > > >> > >> > src/Examples/Other (please think about > a good > >> name) > >> > and then > >> > >> > --env:SSDIR+=../FLOSS Manual > >> Examples/SourceMaterials > >> > >> > should work. > >> > >> > > >> > >> > I am not sure at the moment if the Examples > >> menu gets > >> > populated > >> > >> > automatically or we need to create another > >> entry. in > >> > the code. > >> > >> > > >> > >> > Please let me know what you think and if I > >> can help > >> > somehow? > >> > >> > > >> > >> > tarmo > >> > >> > > >> > >> > Kontakt joachim heintz > (<jh...@jo... <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>> > >> > <mailto:jh...@jo... > <mailto:jh...@jo...> <mailto:jh...@jo... > <mailto:jh...@jo...>>> > >> > >> <mailto:jh...@jo... > <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>> > <mailto:jh...@jo... <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>>>> > >> > >> > <mailto:jh...@jo... > <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>> > >> > <mailto:jh...@jo... > <mailto:jh...@jo...> <mailto:jh...@jo... > <mailto:jh...@jo...>>> > >> <mailto:jh...@jo... <mailto:jh...@jo...> > <mailto:jh...@jo... <mailto:jh...@jo...>> > >> > <mailto:jh...@jo... > <mailto:jh...@jo...> <mailto:jh...@jo... > <mailto:jh...@jo...>>>>>>) > >> > >> kirjutas kuupäeval R, 30. juuli 2021 kell > >> > >> > 10:31: > >> > >> > > >> > >> > hi tarmo, hi eduardo - > >> > >> > > >> > >> > i wrote an email to the csoundqt dev > >> list. think this > >> > >> would be > >> > >> > great to > >> > >> > include in csoundqt 1.0.0. can you > >> help? the > >> > text below. > >> > >> > > >> > >> > i want to include "fox.wav" in > >> > >> Examples/Synths/ImitiativeAdditive.csd. > >> > >> > > >> > >> > what is the best way to achieve this? > >> > >> > > >> > >> > in the McCurdy and FLOSS examples, > i once > >> inserted the > >> > >> option: > >> > >> > > --env:SSDIR+=../SourceMaterials > >> > >> > > >> > >> > i tried the same here (locally, no > push to > >> git): > >> > >> > 1. i created a folder > "SourceMaterials" > >> in the > >> > examples/ > >> > >> directory, > >> > >> > with > >> > >> > fox.wav in it. > >> > >> > 2. i inserted this around line 4600 in > >> > src/qutecsound.cpp: > >> > >> > QStringList sourceMaterials; > >> > >> > sourceMaterials << > >> > >> ":/examples/SourceMaterials/fox.wav"; > >> > >> > subMenus << sourceMaterials; > >> > >> > subMenuNames << > >> tr("SourceMaterials"); > >> > >> > 3. and in application.qrc: > >> > >> > > <file>../examples/SourceMaterials/fox.wav</file> > >> > >> > > >> > >> > after recompiling, the folder > >> "SourceMaterials" > >> > shows up > >> > >> in the menu, > >> > >> > but the fox.wav is not found by csound. > >> > >> > > >> > >> > perhaps i forgot one step? > >> > >> > > >> > >> > but anyway, i think it is a nasty > way to do > >> it. > >> > so back > >> > >> to the > >> > >> > question > >> > >> > above: how can it be done better, > properly? > >> > >> > > >> > >> > cheers - > >> > >> > joachim > >> > >> > > >> > >> > >> > > >> > > >> > _______________________________________________ > >> > Qutecsound-devel mailing list > >> > Qut...@li... > <mailto:Qut...@li...> > >> <mailto:Qut...@li... > <mailto:Qut...@li...>> > >> > <mailto:Qut...@li... > <mailto:Qut...@li...> > >> <mailto:Qut...@li... > <mailto:Qut...@li...>>> > >> > > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel> > >> > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel>> > >> > > >> <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel> > >> > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel>>> > >> > > >> > > > > > > _______________________________________________ > > Qutecsound-devel mailing list > > Qut...@li... > <mailto:Qut...@li...> > > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel> > > > _______________________________________________ > Qutecsound-devel mailing list > Qut...@li... > <mailto:Qut...@li...> > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel> > |
|
From: joachim h. <jh...@jo...> - 2021-08-19 13:10:57
|
i did some work on the examples and just pushed. so please merge any time you like. just to let you know i get these linker issues at the very end of my compilation: /usr/bin/ld: /home/jh/src/Qt5/5.15.2/gcc_64/lib/libQt5WebEngineCore.so: .dynsym local symbol at index 3 (>= sh_info of 3) /usr/bin/ld: /home/jh/src/Qt5/5.15.2/gcc_64/lib/libQt5WebEngineCore.so: .dynsym local symbol at index 4 (>= sh_info of 3) ... etc up to /usr/bin/ld: /home/jh/src/Qt5/5.15.2/gcc_64/lib/libQt5WebEngineCore.so: .dynsym local symbol at index 20 (>= sh_info of 3) not sure it is in any way related to the examples (probably not). it does not prevent me from building CsoundQt either. cheers - j On 17/08/2021 22:34, joachim heintz wrote: > yes definitely! i will try your changes and clean some examples > tomorrow; if all is ok please merge then. > cheers - > j > > > On 16/08/2021 23:02, Tarmo Johannes wrote: >> Hi! >> >> Thanks for noticing this! There was a hardcoded limit to filling the >> menus, I increased that to 256, so even big folders should build up >> nicely. >> Pushed to git. >> >> Does it seem OK to merge it to the develop branch (after some tiding >> up) soon? >> >> Best! >> tarmo >> >> Kontakt joachim heintz (<jh...@jo... >> <mailto:jh...@jo...>>) kirjutas kuupäeval R, 13. august 2021 >> kell 22:54: >> >> wonderful! >> >> i checked several examples, and all worked fine =) >> >> i found one issue in the FLOSS examples, 05 Sound Modification: >> i see only examples up to 05H02 in the dropdown menu. >> the other examples (05H03 and following) are in the source folder but >> not in my built. >> >> can you check if it is the same for you? >> >> (please pull first; idid some small changes to some examples.) >> >> cheers - >> joachim >> >> >> >> >> On 12/08/2021 22:37, Tarmo Johannes wrote: >> > Hi! >> > >> > I finished now a new system for managing examples, it is done >> at the >> > moment in separate path "examples": >> > https://github.com/CsoundQt/CsoundQt/tree/examples >> <https://github.com/CsoundQt/CsoundQt/tree/examples> >> > <https://github.com/CsoundQt/CsoundQt/tree/examples >> <https://github.com/CsoundQt/CsoundQt/tree/examples>> >> > >> > 1) I moved the examples from source root directory to >> > src/Examples/CsoundQt (maybe there is a better name for it, >> Joachim?). >> > src/Examples will be the place where we can put all the examples >> from now on >> > 2) the Examples menu is filled automatically according the >> subfolders in >> > the Examples path. It means we can easily add new categories, >> regroup >> > the examples etc - managing the examples does not require >> touching the >> > CsoundQt source code any more >> > 3) I moved source materials from FLOSS ans McCurdy one level >> up, to >> > src/Examples/SourceMateriald and got rid of the duplicates this >> way. I >> > changed the current references to ../../SourceMaterials in >> csd-s. New >> > source materials can be put there, too, if needed for new >> examples. >> > 4) The examples folder should be found automatically in most >> cases, but >> > for special occasions, I added an option under >> > Configuration->Environment to set the path of examples folder, if >> user >> > needs to. >> > >> > I still think it is good to move the examples out to another repo >> > (CsoundQt/Examples perhaps?) and use it as a git submodule - so >> it can >> > be pulled easily together with CsoundQt source but it is >> possible to >> > pull also just source, without examples (this is probably good >> for linux >> > packagers), too. The benefit is that managing examples gets >> independent, >> > you can always download newest version from git as zip, also it >> gets >> > more easy and clearer to handle, so we can hope to get more >> people to >> > contribute and take care of the example base. I don't know how >> to do >> > the submodule thing, to be honest, but I will figure out, if you >> agree >> > it makes sense. >> > >> > Joachim, if you have a chance to test if the examples work, would >> be great! >> > >> > tarmo >> > >> > >> > Kontakt joachim heintz (<jh...@jo... >> <mailto:jh...@jo...> >> > <mailto:jh...@jo... <mailto:jh...@jo...>>>) >> kirjutas kuupäeval E, 2. august 2021 kell >> > 23:11: >> > >> > hi - >> > >> > sounds great what you say about your work on this! thanks a >> lot for >> > doing it so fast. >> > >> > i am not sure i understand your discussion well, about the >> own repo for >> > the examples. but i'd definitely prefer to have the examples >> > *included* >> > in CsoundQt, as it was. i think the examples are one of the >> pros for >> > CsoundQt, and we should not require to be always online or >> something (i >> > just was in the middle of germany and had no internet access, >> not even >> > mobile ...). >> > >> > cheers - >> > joachim >> > >> > >> > >> > On 02/08/2021 17:01, Tarmo Johannes wrote: >> > > Hi! >> > > >> > > 1) Started work on moving all examples to src/Examples. I >> do it in a >> > > separate branch (examples) just for any case. I have not >> pushed >> > it yet >> > > though. >> > > >> > > I moved the main examples to Examples/CsoundQt and >> expanded a bit >> > the >> > > folders where the examples can be found.. The only >> example/csd >> > that has >> > > to be delivered within the resources with the binary is >> Eduardo's >> > > AudioMidiTest.csd as I find it absolutely necessary to >> have it >> > by the >> > > program in all times. >> > > >> > > The menu gets populated automatically quite fine, it >> needs some >> > more >> > > work (Getting Started submenus and Stria Synth), I moved >> all >> > resources >> > > files to Examples/SourceMaterials Next step is to change >> McCurdy and >> > > Floss examples so that they would use the one path and >> would not >> > > duplicate the files. >> > > >> > > Now I have to finish but hopefully I will put it out for >> testing >> > soon. >> > > >> > > >> > > 2) Moving the examples to separate git repo is very good >> idea, I >> > think. >> > > Eduardo, did you have in mind that it is the CsoundQt >> program >> > that does >> > > the git pull or it the user/packager who pulls it via git >> submodules >> > > before building? The first case won't probably work since >> most of >> > users >> > > don't have git installed. >> > > >> > > >> > > Greetings, >> > > tarmo >> > > >> > > Kontakt Eduardo Moguillansky >> (<edu...@gm... >> <mailto:edu...@gm...> >> > <mailto:edu...@gm... >> <mailto:edu...@gm...>> >> > > <mailto:edu...@gm... >> <mailto:edu...@gm...> >> > <mailto:edu...@gm... >> <mailto:edu...@gm...>>>>) kirjutas kuupäeval R, 30. >> > > juuli 2021 kell 14:42: >> > > >> > > Another idea: >> > > >> > > Maybe the examples could be moved to their own repo. >> In linux >> > (or in >> > > the other platforms as well) this repo could be >> cloned/pulled by >> > > csoundqt. Then the examples and their resources would >> be in >> > > predictable places and the resources can be accessed by >> > relative paths. >> > > >> > > eduardo >> > > >> > > On 30.07.21 13:35, Tarmo Johannes wrote: >> > >> Yes, >> > >> >> > >> I agree it makes sense to rework it. On MacOs and >> Windows >> > with the >> > >> installers it is no problem, on Linux we must make >> sure that the >> > >> examples can be found, perhaps there should be an >> option in the >> > >> configuration. >> > >> >> > >> Greetings, >> > >> Tarmo >> > >> >> > >> R, 30. juuli 2021 13:43 joachim heintz >> <jh...@jo... <mailto:jh...@jo...> >> > <mailto:jh...@jo... <mailto:jh...@jo...>> >> > >> <mailto:jh...@jo... >> <mailto:jh...@jo...> <mailto:jh...@jo... >> <mailto:jh...@jo...>>>> >> > kirjutas: >> > >> >> > >> thanks for the reply, tarmo! >> > >> >> > >> the inclusion of sound files into some of the csd >> > examples is >> > >> not only >> > >> an issue for ImitativeAdditive.csd. there are a >> couple >> > of other >> > >> examples which i would like to change, too. so >> moving the >> > >> examples to >> > >> another category is no solution. >> > >> >> > >> after your explanation i have two ideas: >> > >> >> > >> 1. would it be possible (and not too hard) to >> treat the >> > current >> > >> /examples in the same way as src/Examples? this >> means that >> > >> they are not >> > >> compiled, but just copied. i think this is >> actually also >> > >> better because >> > >> then the users can access the csd files. and we >> could >> > add the >> > >> sound >> > >> files in a similar way i did it with the floss >> manual >> > examples. >> > >> i think this would be the best solution. >> > >> >> > >> 2. if not possible, the method you described >> should be >> > allright: >> > >> "Thus the fox.wav added this way should be >> copied (by >> > Qt) to a >> > >> temporary >> > >> location first and the path should be given to >> Csound via >> > >> --env:SSDIR+= >> > >> or setting environment variable." >> > >> >> > >> let me know what you think; cheers - >> > >> >> > >> joachim >> > >> >> > >> >> > >> On 30/07/2021 11:34, Tarmo Johannes wrote: >> > >> > Hi! >> > >> > >> > >> > Sorry, I did see your email but waited for a >> good >> > moment to >> > >> try it out. >> > >> > I did not yet but for now I can explain the >> background: >> > >> > >> > >> > there are two places for examples - <CsoundQt >> source >> > >> folder>/examples >> > >> > and and <source>/src/Examples >> > >> > >> > >> > The first gets compiled as binary code to >> CsoundQt as Qt >> > >> resource, the >> > >> > second, the "extended examples" (Floss, McCurdy, >> > Stria) gets >> > >> installed >> > >> > to the system as normal folders. >> > >> > >> > >> > The problem is that Qt can read from the >> compiled-in >> > >> resource but Csound >> > >> > not. Thus the fox.wav added this way should be >> copied (by >> > >> Qt) to a >> > >> > temporary location first and the path should be >> given to >> > >> Csound via >> > >> > --env:SSDIR+= or setting environment variable. >> Quite some >> > >> hassle. >> > >> > >> > >> > One solution is to add the material to the end >> of csd with >> > >> the <CsFileB >> > >> > filename="fox.wav"></CsFileB> (I forgot which >> tool >> > helps to >> > >> do it) (like >> > >> > in case of Synths/Scanned_Synthes_Sandbox.csd) >> > >> > but anyway - I think at some point Andés and >> René >> > discussed >> > >> it and >> > >> > decided that no large source materials are >> added to >> > >> src/examples - it >> > >> > makes just the CsoundQt binary grow. >> > >> > >> > >> > Much simpler way would be to put >> > ImitiativeAdditive.csd into >> > >> the real >> > >> > folder under "src/Examples" where fox.wav is >> is in >> > >> > src/Examples/FLOSS Manual >> Examples/SourceMaterials/ >> > and set >> > >> the SSDIR >> > >> > relative to the csd. Perhaps it makes sense to >> do another >> > >> folder like: >> > >> > >> > >> > src/Examples/Other (please think about a good >> name) >> > and then >> > >> > --env:SSDIR+=../FLOSS Manual >> Examples/SourceMaterials >> > >> > should work. >> > >> > >> > >> > I am not sure at the moment if the Examples >> menu gets >> > populated >> > >> > automatically or we need to create another >> entry. in >> > the code. >> > >> > >> > >> > Please let me know what you think and if I >> can help >> > somehow? >> > >> > >> > >> > tarmo >> > >> > >> > >> > Kontakt joachim heintz (<jh...@jo... >> <mailto:jh...@jo...> >> > <mailto:jh...@jo... <mailto:jh...@jo...>> >> > >> <mailto:jh...@jo... >> <mailto:jh...@jo...> <mailto:jh...@jo... >> <mailto:jh...@jo...>>> >> > >> > <mailto:jh...@jo... >> <mailto:jh...@jo...> >> > <mailto:jh...@jo... <mailto:jh...@jo...>> >> <mailto:jh...@jo... <mailto:jh...@jo...> >> > <mailto:jh...@jo... <mailto:jh...@jo...>>>>>) >> > >> kirjutas kuupäeval R, 30. juuli 2021 kell >> > >> > 10:31: >> > >> > >> > >> > hi tarmo, hi eduardo - >> > >> > >> > >> > i wrote an email to the csoundqt dev >> list. think this >> > >> would be >> > >> > great to >> > >> > include in csoundqt 1.0.0. can you >> help? the >> > text below. >> > >> > >> > >> > i want to include "fox.wav" in >> > >> Examples/Synths/ImitiativeAdditive.csd. >> > >> > >> > >> > what is the best way to achieve this? >> > >> > >> > >> > in the McCurdy and FLOSS examples, i once >> inserted the >> > >> option: >> > >> > --env:SSDIR+=../SourceMaterials >> > >> > >> > >> > i tried the same here (locally, no push to >> git): >> > >> > 1. i created a folder "SourceMaterials" >> in the >> > examples/ >> > >> directory, >> > >> > with >> > >> > fox.wav in it. >> > >> > 2. i inserted this around line 4600 in >> > src/qutecsound.cpp: >> > >> > QStringList sourceMaterials; >> > >> > sourceMaterials << >> > >> ":/examples/SourceMaterials/fox.wav"; >> > >> > subMenus << sourceMaterials; >> > >> > subMenuNames << >> tr("SourceMaterials"); >> > >> > 3. and in application.qrc: >> > >> > <file>../examples/SourceMaterials/fox.wav</file> >> > >> > >> > >> > after recompiling, the folder >> "SourceMaterials" >> > shows up >> > >> in the menu, >> > >> > but the fox.wav is not found by csound. >> > >> > >> > >> > perhaps i forgot one step? >> > >> > >> > >> > but anyway, i think it is a nasty way to do >> it. >> > so back >> > >> to the >> > >> > question >> > >> > above: how can it be done better, properly? >> > >> > >> > >> > cheers - >> > >> > joachim >> > >> > >> > >> >> > >> > >> > _______________________________________________ >> > Qutecsound-devel mailing list >> > Qut...@li... >> <mailto:Qut...@li...> >> > <mailto:Qut...@li... >> <mailto:Qut...@li...>> >> > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel >> <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel> >> > >> <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel >> <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel>> >> > >> > > > _______________________________________________ > Qutecsound-devel mailing list > Qut...@li... > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel |
|
From: joachim h. <jh...@jo...> - 2021-08-17 20:35:07
|
yes definitely! i will try your changes and clean some examples tomorrow; if all is ok please merge then. cheers - j On 16/08/2021 23:02, Tarmo Johannes wrote: > Hi! > > Thanks for noticing this! There was a hardcoded limit to filling the > menus, I increased that to 256, so even big folders should build up nicely. > Pushed to git. > > Does it seem OK to merge it to the develop branch (after some tiding > up) soon? > > Best! > tarmo > > Kontakt joachim heintz (<jh...@jo... > <mailto:jh...@jo...>>) kirjutas kuupäeval R, 13. august 2021 > kell 22:54: > > wonderful! > > i checked several examples, and all worked fine =) > > i found one issue in the FLOSS examples, 05 Sound Modification: > i see only examples up to 05H02 in the dropdown menu. > the other examples (05H03 and following) are in the source folder but > not in my built. > > can you check if it is the same for you? > > (please pull first; idid some small changes to some examples.) > > cheers - > joachim > > > > > On 12/08/2021 22:37, Tarmo Johannes wrote: > > Hi! > > > > I finished now a new system for managing examples, it is done at the > > moment in separate path "examples": > > https://github.com/CsoundQt/CsoundQt/tree/examples > <https://github.com/CsoundQt/CsoundQt/tree/examples> > > <https://github.com/CsoundQt/CsoundQt/tree/examples > <https://github.com/CsoundQt/CsoundQt/tree/examples>> > > > > 1) I moved the examples from source root directory to > > src/Examples/CsoundQt (maybe there is a better name for it, > Joachim?). > > src/Examples will be the place where we can put all the examples > from now on > > 2) the Examples menu is filled automatically according the > subfolders in > > the Examples path. It means we can easily add new categories, > regroup > > the examples etc - managing the examples does not require > touching the > > CsoundQt source code any more > > 3) I moved source materials from FLOSS ans McCurdy one level up, to > > src/Examples/SourceMateriald and got rid of the duplicates this > way. I > > changed the current references to ../../SourceMaterials in > csd-s. New > > source materials can be put there, too, if needed for new examples. > > 4) The examples folder should be found automatically in most > cases, but > > for special occasions, I added an option under > > Configuration->Environment to set the path of examples folder, if > user > > needs to. > > > > I still think it is good to move the examples out to another repo > > (CsoundQt/Examples perhaps?) and use it as a git submodule - so > it can > > be pulled easily together with CsoundQt source but it is possible to > > pull also just source, without examples (this is probably good > for linux > > packagers), too. The benefit is that managing examples gets > independent, > > you can always download newest version from git as zip, also it gets > > more easy and clearer to handle, so we can hope to get more > people to > > contribute and take care of the example base. I don't know how > to do > > the submodule thing, to be honest, but I will figure out, if you > agree > > it makes sense. > > > > Joachim, if you have a chance to test if the examples work, would > be great! > > > > tarmo > > > > > > Kontakt joachim heintz (<jh...@jo... > <mailto:jh...@jo...> > > <mailto:jh...@jo... <mailto:jh...@jo...>>>) > kirjutas kuupäeval E, 2. august 2021 kell > > 23:11: > > > > hi - > > > > sounds great what you say about your work on this! thanks a > lot for > > doing it so fast. > > > > i am not sure i understand your discussion well, about the > own repo for > > the examples. but i'd definitely prefer to have the examples > > *included* > > in CsoundQt, as it was. i think the examples are one of the > pros for > > CsoundQt, and we should not require to be always online or > something (i > > just was in the middle of germany and had no internet access, > not even > > mobile ...). > > > > cheers - > > joachim > > > > > > > > On 02/08/2021 17:01, Tarmo Johannes wrote: > > > Hi! > > > > > > 1) Started work on moving all examples to src/Examples. I > do it in a > > > separate branch (examples) just for any case. I have not > pushed > > it yet > > > though. > > > > > > I moved the main examples to Examples/CsoundQt and > expanded a bit > > the > > > folders where the examples can be found.. The only example/csd > > that has > > > to be delivered within the resources with the binary is > Eduardo's > > > AudioMidiTest.csd as I find it absolutely necessary to > have it > > by the > > > program in all times. > > > > > > The menu gets populated automatically quite fine, it > needs some > > more > > > work (Getting Started submenus and Stria Synth), I moved all > > resources > > > files to Examples/SourceMaterials Next step is to change > McCurdy and > > > Floss examples so that they would use the one path and > would not > > > duplicate the files. > > > > > > Now I have to finish but hopefully I will put it out for > testing > > soon. > > > > > > > > > 2) Moving the examples to separate git repo is very good > idea, I > > think. > > > Eduardo, did you have in mind that it is the CsoundQt program > > that does > > > the git pull or it the user/packager who pulls it via git > submodules > > > before building? The first case won't probably work since > most of > > users > > > don't have git installed. > > > > > > > > > Greetings, > > > tarmo > > > > > > Kontakt Eduardo Moguillansky > (<edu...@gm... <mailto:edu...@gm...> > > <mailto:edu...@gm... > <mailto:edu...@gm...>> > > > <mailto:edu...@gm... > <mailto:edu...@gm...> > > <mailto:edu...@gm... > <mailto:edu...@gm...>>>>) kirjutas kuupäeval R, 30. > > > juuli 2021 kell 14:42: > > > > > > Another idea: > > > > > > Maybe the examples could be moved to their own repo. > In linux > > (or in > > > the other platforms as well) this repo could be > cloned/pulled by > > > csoundqt. Then the examples and their resources would > be in > > > predictable places and the resources can be accessed by > > relative paths. > > > > > > eduardo > > > > > > On 30.07.21 13:35, Tarmo Johannes wrote: > > >> Yes, > > >> > > >> I agree it makes sense to rework it. On MacOs and Windows > > with the > > >> installers it is no problem, on Linux we must make > sure that the > > >> examples can be found, perhaps there should be an > option in the > > >> configuration. > > >> > > >> Greetings, > > >> Tarmo > > >> > > >> R, 30. juuli 2021 13:43 joachim heintz > <jh...@jo... <mailto:jh...@jo...> > > <mailto:jh...@jo... <mailto:jh...@jo...>> > > >> <mailto:jh...@jo... > <mailto:jh...@jo...> <mailto:jh...@jo... > <mailto:jh...@jo...>>>> > > kirjutas: > > >> > > >> thanks for the reply, tarmo! > > >> > > >> the inclusion of sound files into some of the csd > > examples is > > >> not only > > >> an issue for ImitativeAdditive.csd. there are a > couple > > of other > > >> examples which i would like to change, too. so > moving the > > >> examples to > > >> another category is no solution. > > >> > > >> after your explanation i have two ideas: > > >> > > >> 1. would it be possible (and not too hard) to > treat the > > current > > >> /examples in the same way as src/Examples? this > means that > > >> they are not > > >> compiled, but just copied. i think this is > actually also > > >> better because > > >> then the users can access the csd files. and we > could > > add the > > >> sound > > >> files in a similar way i did it with the floss manual > > examples. > > >> i think this would be the best solution. > > >> > > >> 2. if not possible, the method you described > should be > > allright: > > >> "Thus the fox.wav added this way should be copied (by > > Qt) to a > > >> temporary > > >> location first and the path should be given to > Csound via > > >> --env:SSDIR+= > > >> or setting environment variable." > > >> > > >> let me know what you think; cheers - > > >> > > >> joachim > > >> > > >> > > >> On 30/07/2021 11:34, Tarmo Johannes wrote: > > >> > Hi! > > >> > > > >> > Sorry, I did see your email but waited for a good > > moment to > > >> try it out. > > >> > I did not yet but for now I can explain the > background: > > >> > > > >> > there are two places for examples - <CsoundQt > source > > >> folder>/examples > > >> > and and <source>/src/Examples > > >> > > > >> > The first gets compiled as binary code to > CsoundQt as Qt > > >> resource, the > > >> > second, the "extended examples" (Floss, McCurdy, > > Stria) gets > > >> installed > > >> > to the system as normal folders. > > >> > > > >> > The problem is that Qt can read from the > compiled-in > > >> resource but Csound > > >> > not. Thus the fox.wav added this way should be > copied (by > > >> Qt) to a > > >> > temporary location first and the path should be > given to > > >> Csound via > > >> > --env:SSDIR+= or setting environment variable. > Quite some > > >> hassle. > > >> > > > >> > One solution is to add the material to the end > of csd with > > >> the <CsFileB > > >> > filename="fox.wav"></CsFileB> (I forgot which tool > > helps to > > >> do it) (like > > >> > in case of Synths/Scanned_Synthes_Sandbox.csd) > > >> > but anyway - I think at some point Andés and René > > discussed > > >> it and > > >> > decided that no large source materials are added to > > >> src/examples - it > > >> > makes just the CsoundQt binary grow. > > >> > > > >> > Much simpler way would be to put > > ImitiativeAdditive.csd into > > >> the real > > >> > folder under "src/Examples" where fox.wav is is in > > >> > src/Examples/FLOSS Manual Examples/SourceMaterials/ > > and set > > >> the SSDIR > > >> > relative to the csd. Perhaps it makes sense to > do another > > >> folder like: > > >> > > > >> > src/Examples/Other (please think about a good name) > > and then > > >> > --env:SSDIR+=../FLOSS Manual > Examples/SourceMaterials > > >> > should work. > > >> > > > >> > I am not sure at the moment if the Examples > menu gets > > populated > > >> > automatically or we need to create another > entry. in > > the code. > > >> > > > >> > Please let me know what you think and if I can help > > somehow? > > >> > > > >> > tarmo > > >> > > > >> > Kontakt joachim heintz (<jh...@jo... > <mailto:jh...@jo...> > > <mailto:jh...@jo... <mailto:jh...@jo...>> > > >> <mailto:jh...@jo... > <mailto:jh...@jo...> <mailto:jh...@jo... > <mailto:jh...@jo...>>> > > >> > <mailto:jh...@jo... > <mailto:jh...@jo...> > > <mailto:jh...@jo... <mailto:jh...@jo...>> > <mailto:jh...@jo... <mailto:jh...@jo...> > > <mailto:jh...@jo... <mailto:jh...@jo...>>>>>) > > >> kirjutas kuupäeval R, 30. juuli 2021 kell > > >> > 10:31: > > >> > > > >> > hi tarmo, hi eduardo - > > >> > > > >> > i wrote an email to the csoundqt dev list. > think this > > >> would be > > >> > great to > > >> > include in csoundqt 1.0.0. can you help? the > > text below. > > >> > > > >> > i want to include "fox.wav" in > > >> Examples/Synths/ImitiativeAdditive.csd. > > >> > > > >> > what is the best way to achieve this? > > >> > > > >> > in the McCurdy and FLOSS examples, i once > inserted the > > >> option: > > >> > --env:SSDIR+=../SourceMaterials > > >> > > > >> > i tried the same here (locally, no push to > git): > > >> > 1. i created a folder "SourceMaterials" in the > > examples/ > > >> directory, > > >> > with > > >> > fox.wav in it. > > >> > 2. i inserted this around line 4600 in > > src/qutecsound.cpp: > > >> > QStringList sourceMaterials; > > >> > sourceMaterials << > > >> ":/examples/SourceMaterials/fox.wav"; > > >> > subMenus << sourceMaterials; > > >> > subMenuNames << tr("SourceMaterials"); > > >> > 3. and in application.qrc: > > >> > <file>../examples/SourceMaterials/fox.wav</file> > > >> > > > >> > after recompiling, the folder "SourceMaterials" > > shows up > > >> in the menu, > > >> > but the fox.wav is not found by csound. > > >> > > > >> > perhaps i forgot one step? > > >> > > > >> > but anyway, i think it is a nasty way to do > it. > > so back > > >> to the > > >> > question > > >> > above: how can it be done better, properly? > > >> > > > >> > cheers - > > >> > joachim > > >> > > > >> > > > > > > _______________________________________________ > > Qutecsound-devel mailing list > > Qut...@li... > <mailto:Qut...@li...> > > <mailto:Qut...@li... > <mailto:Qut...@li...>> > > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel> > > > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel>> > > > |
|
From: joachim h. <jh...@jo...> - 2021-08-13 19:54:37
|
wonderful! i checked several examples, and all worked fine =) i found one issue in the FLOSS examples, 05 Sound Modification: i see only examples up to 05H02 in the dropdown menu. the other examples (05H03 and following) are in the source folder but not in my built. can you check if it is the same for you? (please pull first; idid some small changes to some examples.) cheers - joachim On 12/08/2021 22:37, Tarmo Johannes wrote: > Hi! > > I finished now a new system for managing examples, it is done at the > moment in separate path "examples": > https://github.com/CsoundQt/CsoundQt/tree/examples > <https://github.com/CsoundQt/CsoundQt/tree/examples> > > 1) I moved the examples from source root directory to > src/Examples/CsoundQt (maybe there is a better name for it, Joachim?). > src/Examples will be the place where we can put all the examples from now on > 2) the Examples menu is filled automatically according the subfolders in > the Examples path. It means we can easily add new categories, regroup > the examples etc - managing the examples does not require touching the > CsoundQt source code any more > 3) I moved source materials from FLOSS ans McCurdy one level up, to > src/Examples/SourceMateriald and got rid of the duplicates this way. I > changed the current references to ../../SourceMaterials in csd-s. New > source materials can be put there, too, if needed for new examples. > 4) The examples folder should be found automatically in most cases, but > for special occasions, I added an option under > Configuration->Environment to set the path of examples folder, if user > needs to. > > I still think it is good to move the examples out to another repo > (CsoundQt/Examples perhaps?) and use it as a git submodule - so it can > be pulled easily together with CsoundQt source but it is possible to > pull also just source, without examples (this is probably good for linux > packagers), too. The benefit is that managing examples gets independent, > you can always download newest version from git as zip, also it gets > more easy and clearer to handle, so we can hope to get more people to > contribute and take care of the example base. I don't know how to do > the submodule thing, to be honest, but I will figure out, if you agree > it makes sense. > > Joachim, if you have a chance to test if the examples work, would be great! > > tarmo > > > Kontakt joachim heintz (<jh...@jo... > <mailto:jh...@jo...>>) kirjutas kuupäeval E, 2. august 2021 kell > 23:11: > > hi - > > sounds great what you say about your work on this! thanks a lot for > doing it so fast. > > i am not sure i understand your discussion well, about the own repo for > the examples. but i'd definitely prefer to have the examples > *included* > in CsoundQt, as it was. i think the examples are one of the pros for > CsoundQt, and we should not require to be always online or something (i > just was in the middle of germany and had no internet access, not even > mobile ...). > > cheers - > joachim > > > > On 02/08/2021 17:01, Tarmo Johannes wrote: > > Hi! > > > > 1) Started work on moving all examples to src/Examples. I do it in a > > separate branch (examples) just for any case. I have not pushed > it yet > > though. > > > > I moved the main examples to Examples/CsoundQt and expanded a bit > the > > folders where the examples can be found.. The only example/csd > that has > > to be delivered within the resources with the binary is Eduardo's > > AudioMidiTest.csd as I find it absolutely necessary to have it > by the > > program in all times. > > > > The menu gets populated automatically quite fine, it needs some > more > > work (Getting Started submenus and Stria Synth), I moved all > resources > > files to Examples/SourceMaterials Next step is to change McCurdy and > > Floss examples so that they would use the one path and would not > > duplicate the files. > > > > Now I have to finish but hopefully I will put it out for testing > soon. > > > > > > 2) Moving the examples to separate git repo is very good idea, I > think. > > Eduardo, did you have in mind that it is the CsoundQt program > that does > > the git pull or it the user/packager who pulls it via git submodules > > before building? The first case won't probably work since most of > users > > don't have git installed. > > > > > > Greetings, > > tarmo > > > > Kontakt Eduardo Moguillansky (<edu...@gm... > <mailto:edu...@gm...> > > <mailto:edu...@gm... > <mailto:edu...@gm...>>>) kirjutas kuupäeval R, 30. > > juuli 2021 kell 14:42: > > > > Another idea: > > > > Maybe the examples could be moved to their own repo. In linux > (or in > > the other platforms as well) this repo could be cloned/pulled by > > csoundqt. Then the examples and their resources would be in > > predictable places and the resources can be accessed by > relative paths. > > > > eduardo > > > > On 30.07.21 13:35, Tarmo Johannes wrote: > >> Yes, > >> > >> I agree it makes sense to rework it. On MacOs and Windows > with the > >> installers it is no problem, on Linux we must make sure that the > >> examples can be found, perhaps there should be an option in the > >> configuration. > >> > >> Greetings, > >> Tarmo > >> > >> R, 30. juuli 2021 13:43 joachim heintz <jh...@jo... > <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>>> > kirjutas: > >> > >> thanks for the reply, tarmo! > >> > >> the inclusion of sound files into some of the csd > examples is > >> not only > >> an issue for ImitativeAdditive.csd. there are a couple > of other > >> examples which i would like to change, too. so moving the > >> examples to > >> another category is no solution. > >> > >> after your explanation i have two ideas: > >> > >> 1. would it be possible (and not too hard) to treat the > current > >> /examples in the same way as src/Examples? this means that > >> they are not > >> compiled, but just copied. i think this is actually also > >> better because > >> then the users can access the csd files. and we could > add the > >> sound > >> files in a similar way i did it with the floss manual > examples. > >> i think this would be the best solution. > >> > >> 2. if not possible, the method you described should be > allright: > >> "Thus the fox.wav added this way should be copied (by > Qt) to a > >> temporary > >> location first and the path should be given to Csound via > >> --env:SSDIR+= > >> or setting environment variable." > >> > >> let me know what you think; cheers - > >> > >> joachim > >> > >> > >> On 30/07/2021 11:34, Tarmo Johannes wrote: > >> > Hi! > >> > > >> > Sorry, I did see your email but waited for a good > moment to > >> try it out. > >> > I did not yet but for now I can explain the background: > >> > > >> > there are two places for examples - <CsoundQt source > >> folder>/examples > >> > and and <source>/src/Examples > >> > > >> > The first gets compiled as binary code to CsoundQt as Qt > >> resource, the > >> > second, the "extended examples" (Floss, McCurdy, > Stria) gets > >> installed > >> > to the system as normal folders. > >> > > >> > The problem is that Qt can read from the compiled-in > >> resource but Csound > >> > not. Thus the fox.wav added this way should be copied (by > >> Qt) to a > >> > temporary location first and the path should be given to > >> Csound via > >> > --env:SSDIR+= or setting environment variable. Quite some > >> hassle. > >> > > >> > One solution is to add the material to the end of csd with > >> the <CsFileB > >> > filename="fox.wav"></CsFileB> (I forgot which tool > helps to > >> do it) (like > >> > in case of Synths/Scanned_Synthes_Sandbox.csd) > >> > but anyway - I think at some point Andés and René > discussed > >> it and > >> > decided that no large source materials are added to > >> src/examples - it > >> > makes just the CsoundQt binary grow. > >> > > >> > Much simpler way would be to put > ImitiativeAdditive.csd into > >> the real > >> > folder under "src/Examples" where fox.wav is is in > >> > src/Examples/FLOSS Manual Examples/SourceMaterials/ > and set > >> the SSDIR > >> > relative to the csd. Perhaps it makes sense to do another > >> folder like: > >> > > >> > src/Examples/Other (please think about a good name) > and then > >> > --env:SSDIR+=../FLOSS Manual Examples/SourceMaterials > >> > should work. > >> > > >> > I am not sure at the moment if the Examples menu gets > populated > >> > automatically or we need to create another entry. in > the code. > >> > > >> > Please let me know what you think and if I can help > somehow? > >> > > >> > tarmo > >> > > >> > Kontakt joachim heintz (<jh...@jo... > <mailto:jh...@jo...> > >> <mailto:jh...@jo... <mailto:jh...@jo...>> > >> > <mailto:jh...@jo... > <mailto:jh...@jo...> <mailto:jh...@jo... > <mailto:jh...@jo...>>>>) > >> kirjutas kuupäeval R, 30. juuli 2021 kell > >> > 10:31: > >> > > >> > hi tarmo, hi eduardo - > >> > > >> > i wrote an email to the csoundqt dev list. think this > >> would be > >> > great to > >> > include in csoundqt 1.0.0. can you help? the > text below. > >> > > >> > i want to include "fox.wav" in > >> Examples/Synths/ImitiativeAdditive.csd. > >> > > >> > what is the best way to achieve this? > >> > > >> > in the McCurdy and FLOSS examples, i once inserted the > >> option: > >> > --env:SSDIR+=../SourceMaterials > >> > > >> > i tried the same here (locally, no push to git): > >> > 1. i created a folder "SourceMaterials" in the > examples/ > >> directory, > >> > with > >> > fox.wav in it. > >> > 2. i inserted this around line 4600 in > src/qutecsound.cpp: > >> > QStringList sourceMaterials; > >> > sourceMaterials << > >> ":/examples/SourceMaterials/fox.wav"; > >> > subMenus << sourceMaterials; > >> > subMenuNames << tr("SourceMaterials"); > >> > 3. and in application.qrc: > >> > <file>../examples/SourceMaterials/fox.wav</file> > >> > > >> > after recompiling, the folder "SourceMaterials" > shows up > >> in the menu, > >> > but the fox.wav is not found by csound. > >> > > >> > perhaps i forgot one step? > >> > > >> > but anyway, i think it is a nasty way to do it. > so back > >> to the > >> > question > >> > above: how can it be done better, properly? > >> > > >> > cheers - > >> > joachim > >> > > >> > > > _______________________________________________ > Qutecsound-devel mailing list > Qut...@li... > <mailto:Qut...@li...> > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > <https://lists.sourceforge.net/lists/listinfo/qutecsound-devel> > |
|
From: Tarmo J. <trm...@gm...> - 2021-08-12 20:37:59
|
Hi! I finished now a new system for managing examples, it is done at the moment in separate path "examples": https://github.com/CsoundQt/CsoundQt/tree/examples 1) I moved the examples from source root directory to src/Examples/CsoundQt (maybe there is a better name for it, Joachim?). src/Examples will be the place where we can put all the examples from now on 2) the Examples menu is filled automatically according the subfolders in the Examples path. It means we can easily add new categories, regroup the examples etc - managing the examples does not require touching the CsoundQt source code any more 3) I moved source materials from FLOSS ans McCurdy one level up, to src/Examples/SourceMateriald and got rid of the duplicates this way. I changed the current references to ../../SourceMaterials in csd-s. New source materials can be put there, too, if needed for new examples. 4) The examples folder should be found automatically in most cases, but for special occasions, I added an option under Configuration->Environment to set the path of examples folder, if user needs to. I still think it is good to move the examples out to another repo (CsoundQt/Examples perhaps?) and use it as a git submodule - so it can be pulled easily together with CsoundQt source but it is possible to pull also just source, without examples (this is probably good for linux packagers), too. The benefit is that managing examples gets independent, you can always download newest version from git as zip, also it gets more easy and clearer to handle, so we can hope to get more people to contribute and take care of the example base. I don't know how to do the submodule thing, to be honest, but I will figure out, if you agree it makes sense. Joachim, if you have a chance to test if the examples work, would be great! tarmo Kontakt joachim heintz (<jh...@jo...>) kirjutas kuupäeval E, 2. august 2021 kell 23:11: > hi - > > sounds great what you say about your work on this! thanks a lot for > doing it so fast. > > i am not sure i understand your discussion well, about the own repo for > the examples. but i'd definitely prefer to have the examples *included* > in CsoundQt, as it was. i think the examples are one of the pros for > CsoundQt, and we should not require to be always online or something (i > just was in the middle of germany and had no internet access, not even > mobile ...). > > cheers - > joachim > > > > On 02/08/2021 17:01, Tarmo Johannes wrote: > > Hi! > > > > 1) Started work on moving all examples to src/Examples. I do it in a > > separate branch (examples) just for any case. I have not pushed it yet > > though. > > > > I moved the main examples to Examples/CsoundQt and expanded a bit the > > folders where the examples can be found.. The only example/csd that has > > to be delivered within the resources with the binary is Eduardo's > > AudioMidiTest.csd as I find it absolutely necessary to have it by the > > program in all times. > > > > The menu gets populated automatically quite fine, it needs some more > > work (Getting Started submenus and Stria Synth), I moved all resources > > files to Examples/SourceMaterials Next step is to change McCurdy and > > Floss examples so that they would use the one path and would not > > duplicate the files. > > > > Now I have to finish but hopefully I will put it out for testing soon. > > > > > > 2) Moving the examples to separate git repo is very good idea, I think. > > Eduardo, did you have in mind that it is the CsoundQt program that does > > the git pull or it the user/packager who pulls it via git submodules > > before building? The first case won't probably work since most of users > > don't have git installed. > > > > > > Greetings, > > tarmo > > > > Kontakt Eduardo Moguillansky (<edu...@gm... > > <mailto:edu...@gm...>>) kirjutas kuupäeval R, 30. > > juuli 2021 kell 14:42: > > > > Another idea: > > > > Maybe the examples could be moved to their own repo. In linux (or in > > the other platforms as well) this repo could be cloned/pulled by > > csoundqt. Then the examples and their resources would be in > > predictable places and the resources can be accessed by relative > paths. > > > > eduardo > > > > On 30.07.21 13:35, Tarmo Johannes wrote: > >> Yes, > >> > >> I agree it makes sense to rework it. On MacOs and Windows with the > >> installers it is no problem, on Linux we must make sure that the > >> examples can be found, perhaps there should be an option in the > >> configuration. > >> > >> Greetings, > >> Tarmo > >> > >> R, 30. juuli 2021 13:43 joachim heintz <jh...@jo... > >> <mailto:jh...@jo...>> kirjutas: > >> > >> thanks for the reply, tarmo! > >> > >> the inclusion of sound files into some of the csd examples is > >> not only > >> an issue for ImitativeAdditive.csd. there are a couple of other > >> examples which i would like to change, too. so moving the > >> examples to > >> another category is no solution. > >> > >> after your explanation i have two ideas: > >> > >> 1. would it be possible (and not too hard) to treat the current > >> /examples in the same way as src/Examples? this means that > >> they are not > >> compiled, but just copied. i think this is actually also > >> better because > >> then the users can access the csd files. and we could add the > >> sound > >> files in a similar way i did it with the floss manual examples. > >> i think this would be the best solution. > >> > >> 2. if not possible, the method you described should be allright: > >> "Thus the fox.wav added this way should be copied (by Qt) to a > >> temporary > >> location first and the path should be given to Csound via > >> --env:SSDIR+= > >> or setting environment variable." > >> > >> let me know what you think; cheers - > >> > >> joachim > >> > >> > >> On 30/07/2021 11:34, Tarmo Johannes wrote: > >> > Hi! > >> > > >> > Sorry, I did see your email but waited for a good moment to > >> try it out. > >> > I did not yet but for now I can explain the background: > >> > > >> > there are two places for examples - <CsoundQt source > >> folder>/examples > >> > and and <source>/src/Examples > >> > > >> > The first gets compiled as binary code to CsoundQt as Qt > >> resource, the > >> > second, the "extended examples" (Floss, McCurdy, Stria) gets > >> installed > >> > to the system as normal folders. > >> > > >> > The problem is that Qt can read from the compiled-in > >> resource but Csound > >> > not. Thus the fox.wav added this way should be copied (by > >> Qt) to a > >> > temporary location first and the path should be given to > >> Csound via > >> > --env:SSDIR+= or setting environment variable. Quite some > >> hassle. > >> > > >> > One solution is to add the material to the end of csd with > >> the <CsFileB > >> > filename="fox.wav"></CsFileB> (I forgot which tool helps to > >> do it) (like > >> > in case of Synths/Scanned_Synthes_Sandbox.csd) > >> > but anyway - I think at some point Andés and René discussed > >> it and > >> > decided that no large source materials are added to > >> src/examples - it > >> > makes just the CsoundQt binary grow. > >> > > >> > Much simpler way would be to put ImitiativeAdditive.csd into > >> the real > >> > folder under "src/Examples" where fox.wav is is in > >> > src/Examples/FLOSS Manual Examples/SourceMaterials/ and set > >> the SSDIR > >> > relative to the csd. Perhaps it makes sense to do another > >> folder like: > >> > > >> > src/Examples/Other (please think about a good name) and then > >> > --env:SSDIR+=../FLOSS Manual Examples/SourceMaterials > >> > should work. > >> > > >> > I am not sure at the moment if the Examples menu gets > populated > >> > automatically or we need to create another entry. in the code. > >> > > >> > Please let me know what you think and if I can help somehow? > >> > > >> > tarmo > >> > > >> > Kontakt joachim heintz (<jh...@jo... > >> <mailto:jh...@jo...> > >> > <mailto:jh...@jo... <mailto:jh...@jo...>>>) > >> kirjutas kuupäeval R, 30. juuli 2021 kell > >> > 10:31: > >> > > >> > hi tarmo, hi eduardo - > >> > > >> > i wrote an email to the csoundqt dev list. think this > >> would be > >> > great to > >> > include in csoundqt 1.0.0. can you help? the text below. > >> > > >> > i want to include "fox.wav" in > >> Examples/Synths/ImitiativeAdditive.csd. > >> > > >> > what is the best way to achieve this? > >> > > >> > in the McCurdy and FLOSS examples, i once inserted the > >> option: > >> > --env:SSDIR+=../SourceMaterials > >> > > >> > i tried the same here (locally, no push to git): > >> > 1. i created a folder "SourceMaterials" in the examples/ > >> directory, > >> > with > >> > fox.wav in it. > >> > 2. i inserted this around line 4600 in src/qutecsound.cpp: > >> > QStringList sourceMaterials; > >> > sourceMaterials << > >> ":/examples/SourceMaterials/fox.wav"; > >> > subMenus << sourceMaterials; > >> > subMenuNames << tr("SourceMaterials"); > >> > 3. and in application.qrc: > >> > <file>../examples/SourceMaterials/fox.wav</file> > >> > > >> > after recompiling, the folder "SourceMaterials" shows up > >> in the menu, > >> > but the fox.wav is not found by csound. > >> > > >> > perhaps i forgot one step? > >> > > >> > but anyway, i think it is a nasty way to do it. so back > >> to the > >> > question > >> > above: how can it be done better, properly? > >> > > >> > cheers - > >> > joachim > >> > > >> > > > _______________________________________________ > Qutecsound-devel mailing list > Qut...@li... > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > |
|
From: joachim h. <jh...@jo...> - 2021-08-02 20:10:46
|
hi -
sounds great what you say about your work on this! thanks a lot for
doing it so fast.
i am not sure i understand your discussion well, about the own repo for
the examples. but i'd definitely prefer to have the examples *included*
in CsoundQt, as it was. i think the examples are one of the pros for
CsoundQt, and we should not require to be always online or something (i
just was in the middle of germany and had no internet access, not even
mobile ...).
cheers -
joachim
On 02/08/2021 17:01, Tarmo Johannes wrote:
> Hi!
>
> 1) Started work on moving all examples to src/Examples. I do it in a
> separate branch (examples) just for any case. I have not pushed it yet
> though.
>
> I moved the main examples to Examples/CsoundQt and expanded a bit the
> folders where the examples can be found.. The only example/csd that has
> to be delivered within the resources with the binary is Eduardo's
> AudioMidiTest.csd as I find it absolutely necessary to have it by the
> program in all times.
>
> The menu gets populated automatically quite fine, it needs some more
> work (Getting Started submenus and Stria Synth), I moved all resources
> files to Examples/SourceMaterials Next step is to change McCurdy and
> Floss examples so that they would use the one path and would not
> duplicate the files.
>
> Now I have to finish but hopefully I will put it out for testing soon.
>
>
> 2) Moving the examples to separate git repo is very good idea, I think.
> Eduardo, did you have in mind that it is the CsoundQt program that does
> the git pull or it the user/packager who pulls it via git submodules
> before building? The first case won't probably work since most of users
> don't have git installed.
>
>
> Greetings,
> tarmo
>
> Kontakt Eduardo Moguillansky (<edu...@gm...
> <mailto:edu...@gm...>>) kirjutas kuupäeval R, 30.
> juuli 2021 kell 14:42:
>
> Another idea:
>
> Maybe the examples could be moved to their own repo. In linux (or in
> the other platforms as well) this repo could be cloned/pulled by
> csoundqt. Then the examples and their resources would be in
> predictable places and the resources can be accessed by relative paths.
>
> eduardo
>
> On 30.07.21 13:35, Tarmo Johannes wrote:
>> Yes,
>>
>> I agree it makes sense to rework it. On MacOs and Windows with the
>> installers it is no problem, on Linux we must make sure that the
>> examples can be found, perhaps there should be an option in the
>> configuration.
>>
>> Greetings,
>> Tarmo
>>
>> R, 30. juuli 2021 13:43 joachim heintz <jh...@jo...
>> <mailto:jh...@jo...>> kirjutas:
>>
>> thanks for the reply, tarmo!
>>
>> the inclusion of sound files into some of the csd examples is
>> not only
>> an issue for ImitativeAdditive.csd. there are a couple of other
>> examples which i would like to change, too. so moving the
>> examples to
>> another category is no solution.
>>
>> after your explanation i have two ideas:
>>
>> 1. would it be possible (and not too hard) to treat the current
>> /examples in the same way as src/Examples? this means that
>> they are not
>> compiled, but just copied. i think this is actually also
>> better because
>> then the users can access the csd files. and we could add the
>> sound
>> files in a similar way i did it with the floss manual examples.
>> i think this would be the best solution.
>>
>> 2. if not possible, the method you described should be allright:
>> "Thus the fox.wav added this way should be copied (by Qt) to a
>> temporary
>> location first and the path should be given to Csound via
>> --env:SSDIR+=
>> or setting environment variable."
>>
>> let me know what you think; cheers -
>>
>> joachim
>>
>>
>> On 30/07/2021 11:34, Tarmo Johannes wrote:
>> > Hi!
>> >
>> > Sorry, I did see your email but waited for a good moment to
>> try it out.
>> > I did not yet but for now I can explain the background:
>> >
>> > there are two places for examples - <CsoundQt source
>> folder>/examples
>> > and and <source>/src/Examples
>> >
>> > The first gets compiled as binary code to CsoundQt as Qt
>> resource, the
>> > second, the "extended examples" (Floss, McCurdy, Stria) gets
>> installed
>> > to the system as normal folders.
>> >
>> > The problem is that Qt can read from the compiled-in
>> resource but Csound
>> > not. Thus the fox.wav added this way should be copied (by
>> Qt) to a
>> > temporary location first and the path should be given to
>> Csound via
>> > --env:SSDIR+= or setting environment variable. Quite some
>> hassle.
>> >
>> > One solution is to add the material to the end of csd with
>> the <CsFileB
>> > filename="fox.wav"></CsFileB> (I forgot which tool helps to
>> do it) (like
>> > in case of Synths/Scanned_Synthes_Sandbox.csd)
>> > but anyway - I think at some point Andés and René discussed
>> it and
>> > decided that no large source materials are added to
>> src/examples - it
>> > makes just the CsoundQt binary grow.
>> >
>> > Much simpler way would be to put ImitiativeAdditive.csd into
>> the real
>> > folder under "src/Examples" where fox.wav is is in
>> > src/Examples/FLOSS Manual Examples/SourceMaterials/ and set
>> the SSDIR
>> > relative to the csd. Perhaps it makes sense to do another
>> folder like:
>> >
>> > src/Examples/Other (please think about a good name) and then
>> > --env:SSDIR+=../FLOSS Manual Examples/SourceMaterials
>> > should work.
>> >
>> > I am not sure at the moment if the Examples menu gets populated
>> > automatically or we need to create another entry. in the code.
>> >
>> > Please let me know what you think and if I can help somehow?
>> >
>> > tarmo
>> >
>> > Kontakt joachim heintz (<jh...@jo...
>> <mailto:jh...@jo...>
>> > <mailto:jh...@jo... <mailto:jh...@jo...>>>)
>> kirjutas kuupäeval R, 30. juuli 2021 kell
>> > 10:31:
>> >
>> > hi tarmo, hi eduardo -
>> >
>> > i wrote an email to the csoundqt dev list. think this
>> would be
>> > great to
>> > include in csoundqt 1.0.0. can you help? the text below.
>> >
>> > i want to include "fox.wav" in
>> Examples/Synths/ImitiativeAdditive.csd.
>> >
>> > what is the best way to achieve this?
>> >
>> > in the McCurdy and FLOSS examples, i once inserted the
>> option:
>> > --env:SSDIR+=../SourceMaterials
>> >
>> > i tried the same here (locally, no push to git):
>> > 1. i created a folder "SourceMaterials" in the examples/
>> directory,
>> > with
>> > fox.wav in it.
>> > 2. i inserted this around line 4600 in src/qutecsound.cpp:
>> > QStringList sourceMaterials;
>> > sourceMaterials <<
>> ":/examples/SourceMaterials/fox.wav";
>> > subMenus << sourceMaterials;
>> > subMenuNames << tr("SourceMaterials");
>> > 3. and in application.qrc:
>> > <file>../examples/SourceMaterials/fox.wav</file>
>> >
>> > after recompiling, the folder "SourceMaterials" shows up
>> in the menu,
>> > but the fox.wav is not found by csound.
>> >
>> > perhaps i forgot one step?
>> >
>> > but anyway, i think it is a nasty way to do it. so back
>> to the
>> > question
>> > above: how can it be done better, properly?
>> >
>> > cheers -
>> > joachim
>> >
>>
|
|
From: Tarmo J. <tar...@ot...> - 2021-08-02 16:02:29
|
Hi!
1) Started work on moving all examples to src/Examples. I do it in a
separate branch (examples) just for any case. I have not pushed it yet
though.
I moved the main examples to Examples/CsoundQt and expanded a bit the
folders where the examples can be found.. The only example/csd that has to
be delivered within the resources with the binary is Eduardo's
AudioMidiTest.csd as I find it absolutely necessary to have it by the
program in all times.
The menu gets populated automatically quite fine, it needs some more work
(Getting Started submenus and Stria Synth), I moved all resources files to
Examples/SourceMaterials Next step is to change McCurdy and Floss examples
so that they would use the one path and would not duplicate the files.
Now I have to finish but hopefully I will put it out for testing soon.
2) Moving the examples to separate git repo is very good idea, I think.
Eduardo, did you have in mind that it is the CsoundQt program that does the
git pull or it the user/packager who pulls it via git submodules before
building? The first case won't probably work since most of users don't have
git installed.
Greetings,
tarmo
Kontakt Eduardo Moguillansky (<edu...@gm...>) kirjutas
kuupäeval R, 30. juuli 2021 kell 14:42:
> Another idea:
>
> Maybe the examples could be moved to their own repo. In linux (or in the
> other platforms as well) this repo could be cloned/pulled by csoundqt. Then
> the examples and their resources would be in predictable places and the
> resources can be accessed by relative paths.
>
> eduardo
> On 30.07.21 13:35, Tarmo Johannes wrote:
>
> Yes,
>
> I agree it makes sense to rework it. On MacOs and Windows with the
> installers it is no problem, on Linux we must make sure that the examples
> can be found, perhaps there should be an option in the configuration.
>
> Greetings,
> Tarmo
>
> R, 30. juuli 2021 13:43 joachim heintz <jh...@jo...> kirjutas:
>
>> thanks for the reply, tarmo!
>>
>> the inclusion of sound files into some of the csd examples is not only
>> an issue for ImitativeAdditive.csd. there are a couple of other
>> examples which i would like to change, too. so moving the examples to
>> another category is no solution.
>>
>> after your explanation i have two ideas:
>>
>> 1. would it be possible (and not too hard) to treat the current
>> /examples in the same way as src/Examples? this means that they are not
>> compiled, but just copied. i think this is actually also better because
>> then the users can access the csd files. and we could add the sound
>> files in a similar way i did it with the floss manual examples.
>> i think this would be the best solution.
>>
>> 2. if not possible, the method you described should be allright:
>> "Thus the fox.wav added this way should be copied (by Qt) to a temporary
>> location first and the path should be given to Csound via --env:SSDIR+=
>> or setting environment variable."
>>
>> let me know what you think; cheers -
>>
>> joachim
>>
>>
>> On 30/07/2021 11:34, Tarmo Johannes wrote:
>> > Hi!
>> >
>> > Sorry, I did see your email but waited for a good moment to try it out.
>> > I did not yet but for now I can explain the background:
>> >
>> > there are two places for examples - <CsoundQt source folder>/examples
>> > and and <source>/src/Examples
>> >
>> > The first gets compiled as binary code to CsoundQt as Qt resource, the
>> > second, the "extended examples" (Floss, McCurdy, Stria) gets installed
>> > to the system as normal folders.
>> >
>> > The problem is that Qt can read from the compiled-in resource but
>> Csound
>> > not. Thus the fox.wav added this way should be copied (by Qt) to a
>> > temporary location first and the path should be given to Csound via
>> > --env:SSDIR+= or setting environment variable. Quite some hassle.
>> >
>> > One solution is to add the material to the end of csd with the <CsFileB
>> > filename="fox.wav"></CsFileB> (I forgot which tool helps to do it)
>> (like
>> > in case of Synths/Scanned_Synthes_Sandbox.csd)
>> > but anyway - I think at some point Andés and René discussed it and
>> > decided that no large source materials are added to src/examples - it
>> > makes just the CsoundQt binary grow.
>> >
>> > Much simpler way would be to put ImitiativeAdditive.csd into the real
>> > folder under "src/Examples" where fox.wav is is in
>> > src/Examples/FLOSS Manual Examples/SourceMaterials/ and set the SSDIR
>> > relative to the csd. Perhaps it makes sense to do another folder like:
>> >
>> > src/Examples/Other (please think about a good name) and then
>> > --env:SSDIR+=../FLOSS Manual Examples/SourceMaterials
>> > should work.
>> >
>> > I am not sure at the moment if the Examples menu gets populated
>> > automatically or we need to create another entry. in the code.
>> >
>> > Please let me know what you think and if I can help somehow?
>> >
>> > tarmo
>> >
>> > Kontakt joachim heintz (<jh...@jo...
>> > <mailto:jh...@jo...>>) kirjutas kuupäeval R, 30. juuli 2021
>> kell
>> > 10:31:
>> >
>> > hi tarmo, hi eduardo -
>> >
>> > i wrote an email to the csoundqt dev list. think this would be
>> > great to
>> > include in csoundqt 1.0.0. can you help? the text below.
>> >
>> > i want to include "fox.wav" in
>> Examples/Synths/ImitiativeAdditive.csd.
>> >
>> > what is the best way to achieve this?
>> >
>> > in the McCurdy and FLOSS examples, i once inserted the option:
>> > --env:SSDIR+=../SourceMaterials
>> >
>> > i tried the same here (locally, no push to git):
>> > 1. i created a folder "SourceMaterials" in the examples/ directory,
>> > with
>> > fox.wav in it.
>> > 2. i inserted this around line 4600 in src/qutecsound.cpp:
>> > QStringList sourceMaterials;
>> > sourceMaterials << ":/examples/SourceMaterials/fox.wav";
>> > subMenus << sourceMaterials;
>> > subMenuNames << tr("SourceMaterials");
>> > 3. and in application.qrc:
>> > <file>../examples/SourceMaterials/fox.wav</file>
>> >
>> > after recompiling, the folder "SourceMaterials" shows up in the
>> menu,
>> > but the fox.wav is not found by csound.
>> >
>> > perhaps i forgot one step?
>> >
>> > but anyway, i think it is a nasty way to do it. so back to the
>> > question
>> > above: how can it be done better, properly?
>> >
>> > cheers -
>> > joachim
>> >
>>
>
|
|
From: Tarmo J. <tar...@ot...> - 2021-07-30 11:35:34
|
Yes,
I agree it makes sense to rework it. On MacOs and Windows with the
installers it is no problem, on Linux we must make sure that the examples
can be found, perhaps there should be an option in the configuration.
Greetings,
Tarmo
R, 30. juuli 2021 13:43 joachim heintz <jh...@jo...> kirjutas:
> thanks for the reply, tarmo!
>
> the inclusion of sound files into some of the csd examples is not only
> an issue for ImitativeAdditive.csd. there are a couple of other
> examples which i would like to change, too. so moving the examples to
> another category is no solution.
>
> after your explanation i have two ideas:
>
> 1. would it be possible (and not too hard) to treat the current
> /examples in the same way as src/Examples? this means that they are not
> compiled, but just copied. i think this is actually also better because
> then the users can access the csd files. and we could add the sound
> files in a similar way i did it with the floss manual examples.
> i think this would be the best solution.
>
> 2. if not possible, the method you described should be allright:
> "Thus the fox.wav added this way should be copied (by Qt) to a temporary
> location first and the path should be given to Csound via --env:SSDIR+=
> or setting environment variable."
>
> let me know what you think; cheers -
>
> joachim
>
>
> On 30/07/2021 11:34, Tarmo Johannes wrote:
> > Hi!
> >
> > Sorry, I did see your email but waited for a good moment to try it out.
> > I did not yet but for now I can explain the background:
> >
> > there are two places for examples - <CsoundQt source folder>/examples
> > and and <source>/src/Examples
> >
> > The first gets compiled as binary code to CsoundQt as Qt resource, the
> > second, the "extended examples" (Floss, McCurdy, Stria) gets installed
> > to the system as normal folders.
> >
> > The problem is that Qt can read from the compiled-in resource but Csound
> > not. Thus the fox.wav added this way should be copied (by Qt) to a
> > temporary location first and the path should be given to Csound via
> > --env:SSDIR+= or setting environment variable. Quite some hassle.
> >
> > One solution is to add the material to the end of csd with the <CsFileB
> > filename="fox.wav"></CsFileB> (I forgot which tool helps to do it) (like
> > in case of Synths/Scanned_Synthes_Sandbox.csd)
> > but anyway - I think at some point Andés and René discussed it and
> > decided that no large source materials are added to src/examples - it
> > makes just the CsoundQt binary grow.
> >
> > Much simpler way would be to put ImitiativeAdditive.csd into the real
> > folder under "src/Examples" where fox.wav is is in
> > src/Examples/FLOSS Manual Examples/SourceMaterials/ and set the SSDIR
> > relative to the csd. Perhaps it makes sense to do another folder like:
> >
> > src/Examples/Other (please think about a good name) and then
> > --env:SSDIR+=../FLOSS Manual Examples/SourceMaterials
> > should work.
> >
> > I am not sure at the moment if the Examples menu gets populated
> > automatically or we need to create another entry. in the code.
> >
> > Please let me know what you think and if I can help somehow?
> >
> > tarmo
> >
> > Kontakt joachim heintz (<jh...@jo...
> > <mailto:jh...@jo...>>) kirjutas kuupäeval R, 30. juuli 2021
> kell
> > 10:31:
> >
> > hi tarmo, hi eduardo -
> >
> > i wrote an email to the csoundqt dev list. think this would be
> > great to
> > include in csoundqt 1.0.0. can you help? the text below.
> >
> > i want to include "fox.wav" in
> Examples/Synths/ImitiativeAdditive.csd.
> >
> > what is the best way to achieve this?
> >
> > in the McCurdy and FLOSS examples, i once inserted the option:
> > --env:SSDIR+=../SourceMaterials
> >
> > i tried the same here (locally, no push to git):
> > 1. i created a folder "SourceMaterials" in the examples/ directory,
> > with
> > fox.wav in it.
> > 2. i inserted this around line 4600 in src/qutecsound.cpp:
> > QStringList sourceMaterials;
> > sourceMaterials << ":/examples/SourceMaterials/fox.wav";
> > subMenus << sourceMaterials;
> > subMenuNames << tr("SourceMaterials");
> > 3. and in application.qrc:
> > <file>../examples/SourceMaterials/fox.wav</file>
> >
> > after recompiling, the folder "SourceMaterials" shows up in the menu,
> > but the fox.wav is not found by csound.
> >
> > perhaps i forgot one step?
> >
> > but anyway, i think it is a nasty way to do it. so back to the
> > question
> > above: how can it be done better, properly?
> >
> > cheers -
> > joachim
> >
>
|
|
From: joachim h. <jh...@jo...> - 2021-07-30 10:43:34
|
thanks for the reply, tarmo!
the inclusion of sound files into some of the csd examples is not only
an issue for ImitativeAdditive.csd. there are a couple of other
examples which i would like to change, too. so moving the examples to
another category is no solution.
after your explanation i have two ideas:
1. would it be possible (and not too hard) to treat the current
/examples in the same way as src/Examples? this means that they are not
compiled, but just copied. i think this is actually also better because
then the users can access the csd files. and we could add the sound
files in a similar way i did it with the floss manual examples.
i think this would be the best solution.
2. if not possible, the method you described should be allright:
"Thus the fox.wav added this way should be copied (by Qt) to a temporary
location first and the path should be given to Csound via --env:SSDIR+=
or setting environment variable."
let me know what you think; cheers -
joachim
On 30/07/2021 11:34, Tarmo Johannes wrote:
> Hi!
>
> Sorry, I did see your email but waited for a good moment to try it out.
> I did not yet but for now I can explain the background:
>
> there are two places for examples - <CsoundQt source folder>/examples
> and and <source>/src/Examples
>
> The first gets compiled as binary code to CsoundQt as Qt resource, the
> second, the "extended examples" (Floss, McCurdy, Stria) gets installed
> to the system as normal folders.
>
> The problem is that Qt can read from the compiled-in resource but Csound
> not. Thus the fox.wav added this way should be copied (by Qt) to a
> temporary location first and the path should be given to Csound via
> --env:SSDIR+= or setting environment variable. Quite some hassle.
>
> One solution is to add the material to the end of csd with the <CsFileB
> filename="fox.wav"></CsFileB> (I forgot which tool helps to do it) (like
> in case of Synths/Scanned_Synthes_Sandbox.csd)
> but anyway - I think at some point Andés and René discussed it and
> decided that no large source materials are added to src/examples - it
> makes just the CsoundQt binary grow.
>
> Much simpler way would be to put ImitiativeAdditive.csd into the real
> folder under "src/Examples" where fox.wav is is in
> src/Examples/FLOSS Manual Examples/SourceMaterials/ and set the SSDIR
> relative to the csd. Perhaps it makes sense to do another folder like:
>
> src/Examples/Other (please think about a good name) and then
> --env:SSDIR+=../FLOSS Manual Examples/SourceMaterials
> should work.
>
> I am not sure at the moment if the Examples menu gets populated
> automatically or we need to create another entry. in the code.
>
> Please let me know what you think and if I can help somehow?
>
> tarmo
>
> Kontakt joachim heintz (<jh...@jo...
> <mailto:jh...@jo...>>) kirjutas kuupäeval R, 30. juuli 2021 kell
> 10:31:
>
> hi tarmo, hi eduardo -
>
> i wrote an email to the csoundqt dev list. think this would be
> great to
> include in csoundqt 1.0.0. can you help? the text below.
>
> i want to include "fox.wav" in Examples/Synths/ImitiativeAdditive.csd.
>
> what is the best way to achieve this?
>
> in the McCurdy and FLOSS examples, i once inserted the option:
> --env:SSDIR+=../SourceMaterials
>
> i tried the same here (locally, no push to git):
> 1. i created a folder "SourceMaterials" in the examples/ directory,
> with
> fox.wav in it.
> 2. i inserted this around line 4600 in src/qutecsound.cpp:
> QStringList sourceMaterials;
> sourceMaterials << ":/examples/SourceMaterials/fox.wav";
> subMenus << sourceMaterials;
> subMenuNames << tr("SourceMaterials");
> 3. and in application.qrc:
> <file>../examples/SourceMaterials/fox.wav</file>
>
> after recompiling, the folder "SourceMaterials" shows up in the menu,
> but the fox.wav is not found by csound.
>
> perhaps i forgot one step?
>
> but anyway, i think it is a nasty way to do it. so back to the
> question
> above: how can it be done better, properly?
>
> cheers -
> joachim
>
|
|
From: Tarmo J. <tar...@ot...> - 2021-07-30 10:40:41
|
Hi!
Sorry, I did see your email but waited for a good moment to try it out. I
did not yet but for now I can explain the background:
there are two places for examples - <CsoundQt source folder>/examples and
and <source>/src/Examples
The first gets compiled as binary code to CsoundQt as Qt resource, the
second, the "extended examples" (Floss, McCurdy, Stria) gets installed to
the system as normal folders.
The problem is that Qt can read from the compiled-in resource but Csound
not. Thus the fox.wav added this way should be copied (by Qt) to a
temporary location first and the path should be given to Csound via
--env:SSDIR+= or setting environment variable. Quite some hassle.
One solution is to add the material to the end of csd with the <CsFileB
filename="fox.wav"></CsFileB> (I forgot which tool helps to do it) (like in
case of Synths/Scanned_Synthes_Sandbox.csd)
but anyway - I think at some point Andés and René discussed it and decided
that no large source materials are added to src/examples - it makes just
the CsoundQt binary grow.
Much simpler way would be to put ImitiativeAdditive.csd into the real
folder under "src/Examples" where fox.wav is is in
src/Examples/FLOSS Manual Examples/SourceMaterials/ and set the SSDIR
relative to the csd. Perhaps it makes sense to do another folder like:
src/Examples/Other (please think about a good name) and then
--env:SSDIR+=../FLOSS Manual Examples/SourceMaterials
should work.
I am not sure at the moment if the Examples menu gets populated
automatically or we need to create another entry. in the code.
Please let me know what you think and if I can help somehow?
tarmo
Kontakt joachim heintz (<jh...@jo...>) kirjutas kuupäeval R, 30.
juuli 2021 kell 10:31:
> hi tarmo, hi eduardo -
>
> i wrote an email to the csoundqt dev list. think this would be great to
> include in csoundqt 1.0.0. can you help? the text below.
>
> i want to include "fox.wav" in Examples/Synths/ImitiativeAdditive.csd.
>
> what is the best way to achieve this?
>
> in the McCurdy and FLOSS examples, i once inserted the option:
> --env:SSDIR+=../SourceMaterials
>
> i tried the same here (locally, no push to git):
> 1. i created a folder "SourceMaterials" in the examples/ directory, with
> fox.wav in it.
> 2. i inserted this around line 4600 in src/qutecsound.cpp:
> QStringList sourceMaterials;
> sourceMaterials << ":/examples/SourceMaterials/fox.wav";
> subMenus << sourceMaterials;
> subMenuNames << tr("SourceMaterials");
> 3. and in application.qrc:
> <file>../examples/SourceMaterials/fox.wav</file>
>
> after recompiling, the folder "SourceMaterials" shows up in the menu,
> but the fox.wav is not found by csound.
>
> perhaps i forgot one step?
>
> but anyway, i think it is a nasty way to do it. so back to the question
> above: how can it be done better, properly?
>
> cheers -
> joachim
>
|
|
From: joachim h. <jh...@jo...> - 2021-07-27 20:55:16
|
hi -
i want to include "fox.wav" in Examples/Synths/ImitiativeAdditive.csd.
what is the best way to achieve this?
in the McCurdy and FLOSS examples, i once inserted the option:
--env:SSDIR+=../SourceMaterials
i tried the same here (locally, no push to git):
1. i created a folder "SourceMaterials" in the examples/ directory, with
fox.wav in it.
2. i inserted this around line 4600 in src/qutecsound.cpp:
QStringList sourceMaterials;
sourceMaterials << ":/examples/SourceMaterials/fox.wav";
subMenus << sourceMaterials;
subMenuNames << tr("SourceMaterials");
3. and in application.qrc:
<file>../examples/SourceMaterials/fox.wav</file>
after recompiling, the folder "SourceMaterials" shows up in the menu,
but the fox.wav is not found by csound.
perhaps i forgot one step?
but anyway, i think it is a nasty way to do it. so back to the question
above: how can it be done better, properly?
cheers -
joachim
|
|
From: Tarmo J. <trm...@gm...> - 2021-06-02 20:41:12
|
Hi!
Yes, sure at some point CsoundQt must be ported to Qt6. It does not work
out of the box. It makes sense to do it after Qt 6.2 LTS is out when they
eill have ported qtwebengine and other last modules.
Building with qt 5.15 should work but I have to try. Probably you just need
to install QtWebengine component? In the Qt you need to check it
separately.
Tarmo
K, 2. juuni 2021 22:37 joachim heintz <jh...@jo...> kirjutas:
> hi tarmo, hi eduardo -
>
> i have just built csoundqt on a new debian 11 system and want to report
> the results.
>
> 1. BUILDING WITH QT 5.15
> in general all fine, but CONFIG+=html_webengine does not work:
> Project ERROR: Unknown module(s) in QT: webenginewidgets
> is there any other html5 module for qt 5.15?
>
> 2. BUILDING WITH QT 6
> this does not work at all. it gives a lot of build errors; i paste a
> small snippet below.
> is there any plan to translate the code to qt6?
>
> cheers -
> joachim
>
>
> build/ui/ui_configdialog.h: In member function ‘void
> Ui_ConfigDialog::setupUi(QDialog*)’:
> build/ui/ui_configdialog.h:1985:73: error: ‘qOverload’ was not declared
> in this scope; did you mean ‘QOverload’?
> 1985 | QObject::connect(okButton, &QPushButton::clicked,
> ConfigDialog, qOverload<>(&QDialog::accept));
> | ^~~~~~~~~
> | QOverload
> build/ui/ui_configdialog.h:1985:83: error: expected primary-expression
> before ‘>’ token
> 1985 | QObject::connect(okButton, &QPushButton::clicked,
> ConfigDialog, qOverload<>(&QDialog::accept));
> | ^
> build/ui/ui_configdialog.h:1986:87: error: expected primary-expression
> before ‘>’ token
> 1986 | QObject::connect(cancelButton, &QPushButton::clicked,
> ConfigDialog, qOverload<>(&QDialog::reject));
> | ^
> src/configdialog.cpp: In member function ‘void
> ConfigDialog::onRtModuleComboBoxChanged(int)’:
> src/configdialog.cpp:405:50: warning: unused parameter ‘index’
> [-Wunused-parameter]
> 405 | void ConfigDialog::onRtModuleComboBoxChanged(int index) {
> | ~~~~^~~~~
> make: *** [Makefile:18062: build/doubles/obj/configdialog.o] Error 1
>
>
> _______________________________________________
> Qutecsound-devel mailing list
> Qut...@li...
> https://lists.sourceforge.net/lists/listinfo/qutecsound-devel
>
|
|
From: joachim h. <jh...@jo...> - 2021-06-02 19:36:55
|
hi tarmo, hi eduardo -
i have just built csoundqt on a new debian 11 system and want to report
the results.
1. BUILDING WITH QT 5.15
in general all fine, but CONFIG+=html_webengine does not work:
Project ERROR: Unknown module(s) in QT: webenginewidgets
is there any other html5 module for qt 5.15?
2. BUILDING WITH QT 6
this does not work at all. it gives a lot of build errors; i paste a
small snippet below.
is there any plan to translate the code to qt6?
cheers -
joachim
build/ui/ui_configdialog.h: In member function ‘void
Ui_ConfigDialog::setupUi(QDialog*)’:
build/ui/ui_configdialog.h:1985:73: error: ‘qOverload’ was not declared
in this scope; did you mean ‘QOverload’?
1985 | QObject::connect(okButton, &QPushButton::clicked,
ConfigDialog, qOverload<>(&QDialog::accept));
| ^~~~~~~~~
| QOverload
build/ui/ui_configdialog.h:1985:83: error: expected primary-expression
before ‘>’ token
1985 | QObject::connect(okButton, &QPushButton::clicked,
ConfigDialog, qOverload<>(&QDialog::accept));
| ^
build/ui/ui_configdialog.h:1986:87: error: expected primary-expression
before ‘>’ token
1986 | QObject::connect(cancelButton, &QPushButton::clicked,
ConfigDialog, qOverload<>(&QDialog::reject));
| ^
src/configdialog.cpp: In member function ‘void
ConfigDialog::onRtModuleComboBoxChanged(int)’:
src/configdialog.cpp:405:50: warning: unused parameter ‘index’
[-Wunused-parameter]
405 | void ConfigDialog::onRtModuleComboBoxChanged(int index) {
| ~~~~^~~~~
make: *** [Makefile:18062: build/doubles/obj/configdialog.o] Error 1
|
|
From: Tarmo J. <trm...@gm...> - 2020-09-07 15:41:38
|
HI, To let know - I dropped support for Qt4 and Csound5 in the code of CsoundQT to make space for Qt6 and Csound7 in the future. I am moving towards version 1.0.0, some small things to do but hopefully soon ready for release candidate. One old plan and wish - I am not sure if any packager reads this - as Felipe Sateler once suggested - it would be wise to move the extended examples (Floss/McCurdy/Stria) away from the main repository to a submodule. This would make the main source repo much lighter for cloning and building. I am not quite sure yet, how to do it, but I will figure it out. If anybody is reading this list - what do you think? Best! tarmo |
|
From: joachim h. <jh...@jo...> - 2020-08-09 21:33:19
|
hi all - i have written new build instructions for debian: https://github.com/CsoundQt/CsoundQt/wiki/Building-CsoundQt-with-Debian-10-and-11 in thses instructions, i explain (under 6.) how to build pythonqt for python3. it is actually only to change line 8 in pythonqt/build/python.prf. for python3, most of the python scripts need some adaption of code (mostly the print statements). i have done this, and pushed it as 'python3' branch. any time we switch to python3 (which i would suggest to do), this branch can be merged, and we should be fine. i have deleted some not fixable scripts. i found these other issues: 1. in general, the execution of python code inside the editor does not seem to work. in only works in the code pad. 2. Live Coding -> Byte song not really working 3. UI with QtDesigner not working for me ftable_editor and ftable_viewer also not (module 'csnd' not found) -> should probably all be removed cheers - joachim |
|
From: Tarmo J. <trm...@gm...> - 2020-07-02 21:17:17
|
Hi, OK, my proposal: I suggest more conservative way still - to delete the tag v0.10 and change it to v0.9.8.1, v0.9.8-1 or something, upload the binaries there, so people get the latest fixes. This is the most important. Then let's wait for more feedback and issue reports (we should benefit from feedback of many people - there were a lot of changes in the code, it is impossible to test everything by just couple of us). and release 1.0.0 after some time. Again - I believe it is not the number that matters, but this seems most logical to me. tarmo Kontakt joachim heintz (<jh...@jo...>) kirjutas kuupäeval N, 2. juuli 2020 kell 22:36: > yes it IS a big step, and i would consider this as birthday present to me > =) > (no my birthday is not today) > > thanks - > j > > > On 02/07/2020 20:57, Eduardo Moguillansky wrote: > > They say that while they talk to you through their macos 10.14 driven > > laptop... Anyway, these differences are meaningless to me and since > > there was a great effort to bring csoundqt forward we might make an > > exception and make the jump to 1.0.0 and start the proposed scheme from > > there, meaning: look, this is now usable, mature, etc. Even if it's > not... > > > > so, I go either way, but I would like to decide this since I need the > > new version to be downloadable now. > > > > --- > > eduardo > > > > On 02.07.20 20:48, joachim heintz wrote: > >> perhaps i have to represent the unreasonable part here: > >> i don't agree. > >> > >> i had a talk today with some students. to all this 0.10 number > >> appeared strange, and looked like many steps back (we did not count > >> 0.09. before as csound does). > >> > >> joachim > >> > >> > >> On 02/07/2020 20:38, Tarmo Johannes wrote: > >>> I agree. > >>> Tarmo > >>> > >>> N, 2. juuli 2020 21:30 Eduardo Moguillansky > >>> <edu...@gm... > >>> <mailto:edu...@gm...>> kirjutas: > >>> > >>> To go forward I would propose the following scheme: > >>> > >>> Major release, when major things happen: switching from qt5 to qt6, > >>> switching from csound6 to csound7, switching from a certain file > >>> format to another, etc. Most importantly, there is no backwards > >>> compatibility between major versions. > >>> > >>> Minor release for things that add core functionality, new widgets, > >>> etc. A .csd which worked in a previous version might need to be > >>> adapted, but there is certain respect for backward compatibility. > >>> > >>> Patch: these are bug fixes. If you are happy with how the program > >>> runs, you don't need to update. > >>> > >>> I would propose to start that scheme now. This is a minor release, > >>> in the sense that there is backwards comptability. So we use the > >>> next number in minor releases: 10 (these are numbers and not > digits) > >>> > >>> In order to not mess up more with the git history I would just > >>> release the bug fixes we have until now as 0.10.0 and upload the > >>> builds (I got to build the mac version correctly!) and any other > bug > >>> fixes will go as 0.10.1, 0.10.2, etc. Whenever the dark look > >>> redesign is ready that might be 0.11.0. > >>> > >>> eduardo > >>> > >>> > >>> On 02.07.20 20:02, Tarmo Johannes wrote: > >>>> Hi! > >>>> > >>>> There is also software that never goes above 0.x.y. Still, I > >>>> agree, would be good to change it. > >>>> > >>>> The current 0.9.8 introduced a lot of changes, I think it is good > >>>> to keep that in use for couple of months, do only bug fixes or > >>>> other minor changes to the code (and use other branches and > >>>> alternative builds for bigger things, if necessary) and then > >>>> release it as 1.0.0 when the current base seems well tested and > >>>> users happy. > >>>> > >>>> tarmo > >>>> > >>>> tarmo > >>>> Yes, it would be logical. > >>>> > >>>> Kontakt joachim heintz (<jh...@jo... > >>>> <mailto:jh...@jo...>>) kirjutas kuupäeval N, 2. juuli > 2020 > >>>> kell 12:08: > >>>> > >>>> hi tarmo - > >>>> > >>>> thanks for explaining. my surprise is simple: for my > >>>> everyday's > >>>> understanding, after 0.9 the 1.0 should follow. i understand > >>>> what you > >>>> and eduardo mean, but the zero in first place after more than > >>>> ten years > >>>> CsoundQt is strange for me. > >>>> > >>>> (Cabbage is now at 2.3.0 and is not older; Blue is at 2.8.0.) > >>>> > >>>> as this release is a major one, perhaps you and eduardo can > >>>> consider to > >>>> make now the step to 1.0.0. more intuitive for me (and i > >>>> assume for > >>>> some others), and more appropriate for the developement > >>>> state of > >>>> csoundqt, in my opinion. > >>>> > >>>> cheers - > >>>> joachim > >>>> > >>>> > >>>> On 01/07/2020 20:08, Tarmo Johannes wrote: > >>>> > Hi, > >>>> > > >>>> > Let's discuss the version policy a bit. > >>>> > I continued what Andrés Cabrera started (that does not seem > >>>> most > >>>> > logical to me nowadays) - > >>>> > the version tags in git history are: > >>>> > > >>>> > 0.7.0 > >>>> > 0.7.0-beta > >>>> > 0.7.1 > >>>> > 0.7.2 > >>>> > 0.7.3 > >>>> > 0.7.4 > >>>> > 0.8.0 > >>>> > 0.8.0-win > >>>> > 0.8.1 > >>>> > 0.8.2 > >>>> > 0.8.3 > >>>> > 0.9.0 > >>>> > 0.9.1 > >>>> > 0.9.2 > >>>> > 0.9.2.1 > >>>> > 0.9.2.2 > >>>> > 0.9.3 > >>>> > 0.9.3-beta > >>>> > 0.9.4 > >>>> > 0.9.4-beta > >>>> > 0.9.4-rc1 > >>>> > 0.9.5 > >>>> > 0.9.5-beta > >>>> > 0.9.6-rc1 > >>>> > 0.9.6-rc2 > >>>> > 0.9.7 > >>>> > 0.9.7-rc1 > >>>> > 0.9.8-beta > >>>> > 0.9.8-rc1 > >>>> > 0.9.8-rc3 > >>>> > v0.9.8 > >>>> > > >>>> > so far the the version has start always with 0 (as usually > >>>> in beta > >>>> > releases), minor version showed bing changes in API (as > >>>> like for > >>>> > support from Csound5 to Csound6 0.8->0.9) patch version > >>>> important new > >>>> > features or bug fixes. The small bug fixes were marked > >>>> sometimes with .1 > >>>> > or .2, sometimes I have uploaded builds with -1 or -2 in the > >>>> end. Not a > >>>> > very good and clear system. > >>>> > > >>>> > If we follow the old logic, the recent small fixes should > >>>> give an extra > >>>> > number to v0.9.8 since there were no significant new > >>>> implementations > >>>> > thus perhaps v0.9.8.1 or v0.9.8-1. v0.10 is OK for me, but > >>>> what is the > >>>> > new logic after that? > >>>> > > >>>> > Of course it would be better to use the major version, minor > >>>> version and > >>>> > patch version as usually, thus let's say we had 1.0.0 > >>>> released and this > >>>> > fix release would be now 1.0.1; when we will have something > >>>> new added, > >>>> > it would make 1.1.0, when we get to Csound7 support > >>>> (perhaps) it would > >>>> > make 2.0.0 etc > >>>> > > >>>> > But where to make the break to 1.0.0? After some patch > >>>> versions of the > >>>> > current until everybody seems happy? > >>>> > > >>>> > Anyway, it is just a number. > >>>> > > >>>> > Eduardo, whatever the number is, I guess I should make new > >>>> Mac, Windows > >>>> > and AppImage builds from develop and add them to 0.10? > >>>> > > >>>> > tarmo > >>>> > > >>>> > Kontakt joachim heintz (<jh...@jo... > >>>> <mailto:jh...@jo...> > >>>> > <mailto:jh...@jo... <mailto:jh...@jo...>>>) > >>>> kirjutas kuupäeval K, 1. juuli 2020 kell > >>>> > 16:14: > >>>> > > >>>> > why not 1.0.0?!? > >>>> > do you want to keep the 0.xx forever? > >>>> > > >>>> > cheers - > >>>> > joachim > >>>> > > >>>> > > >>>> > > >>>> > On 01/07/2020 14:22, Eduardo Moguillansky wrote: > >>>> > > > >>>> > > 0.10 > >>>> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> > >>>> > > > >>>> > > Repository: CsoundQt/CsoundQt > >>>> > <https://github.com/CsoundQt/CsoundQt> · > >>>> > > Tag: v0.10.0 > >>>> <https://github.com/CsoundQt/CsoundQt/tree/v0.10.0> · > >>>> > > Commit: e2576c5 > >>>> > > > >>>> > > >>>> < > https://github.com/CsoundQt/CsoundQt/commit/e2576c53d5acb6c678f857d88ee2582442459fd5> > > >>>> > >>>> > > >>>> > > · Released by: gesellkammer > >>>> <https://github.com/gesellkammer> > >>>> > > > >>>> > > > >>>> > > Changes since 0.9.8 > >>>> > > > >>>> > > > >>>> > > Bugs fixed > >>>> > > > >>>> > > * toolbar in mac fixed > >>>> > > * graph widget for tables now initializes correctly > >>>> and follows > >>>> > > negative indexes (to set the table number) as it > >>>> should > >>>> > > * table plot widget was upside down, now fixed > >>>> > > * Graph widget example fixed > >>>> > > > >>>> > > — > >>>> > > > >>>> > > This release has 2 assets: > >>>> > > > >>>> > > * Source code (zip) > >>>> > > * Source code (tar.gz) > >>>> > > > >>>> > > Visit the release page > >>>> > > > >>>> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> to > >>>> > download > >>>> > > them. > >>>> > > > >>>> > > — > >>>> > > You are receiving this because you are watching this > >>>> repository. > >>>> > > View it on GitHub > >>>> > > > >>>> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> or > >>>> > > unsubscribe > >>>> > > > >>>> > > >>>> < > https://github.com/CsoundQt/CsoundQt/unsubscribe_via_email/AAQYHKWDLXF645EPEIWT623RZMS75ANCNFSM4ANME2IQ> > > >>>> > >>>> > > >>>> > > from all notifications for this repository. > >>>> > > > >>>> > > >>>> > > >>>> > _______________________________________________ > >>>> > Qutecsound-devel mailing list > >>>> > Qut...@li... > >>>> <mailto:Qut...@li...> > >>>> > <mailto:Qut...@li... > >>>> <mailto:Qut...@li...>> > >>>> > > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > >>>> > > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Qutecsound-users mailing list > >>>> Qut...@li... > >>>> <mailto:Qut...@li...> > >>>> https://lists.sourceforge.net/lists/listinfo/qutecsound-users > >>> > |
|
From: joachim h. <jh...@jo...> - 2020-07-02 19:36:10
|
yes it IS a big step, and i would consider this as birthday present to me =) (no my birthday is not today) thanks - j On 02/07/2020 20:57, Eduardo Moguillansky wrote: > They say that while they talk to you through their macos 10.14 driven > laptop... Anyway, these differences are meaningless to me and since > there was a great effort to bring csoundqt forward we might make an > exception and make the jump to 1.0.0 and start the proposed scheme from > there, meaning: look, this is now usable, mature, etc. Even if it's not... > > so, I go either way, but I would like to decide this since I need the > new version to be downloadable now. > > --- > eduardo > > On 02.07.20 20:48, joachim heintz wrote: >> perhaps i have to represent the unreasonable part here: >> i don't agree. >> >> i had a talk today with some students. to all this 0.10 number >> appeared strange, and looked like many steps back (we did not count >> 0.09. before as csound does). >> >> joachim >> >> >> On 02/07/2020 20:38, Tarmo Johannes wrote: >>> I agree. >>> Tarmo >>> >>> N, 2. juuli 2020 21:30 Eduardo Moguillansky >>> <edu...@gm... >>> <mailto:edu...@gm...>> kirjutas: >>> >>> To go forward I would propose the following scheme: >>> >>> Major release, when major things happen: switching from qt5 to qt6, >>> switching from csound6 to csound7, switching from a certain file >>> format to another, etc. Most importantly, there is no backwards >>> compatibility between major versions. >>> >>> Minor release for things that add core functionality, new widgets, >>> etc. A .csd which worked in a previous version might need to be >>> adapted, but there is certain respect for backward compatibility. >>> >>> Patch: these are bug fixes. If you are happy with how the program >>> runs, you don't need to update. >>> >>> I would propose to start that scheme now. This is a minor release, >>> in the sense that there is backwards comptability. So we use the >>> next number in minor releases: 10 (these are numbers and not digits) >>> >>> In order to not mess up more with the git history I would just >>> release the bug fixes we have until now as 0.10.0 and upload the >>> builds (I got to build the mac version correctly!) and any other bug >>> fixes will go as 0.10.1, 0.10.2, etc. Whenever the dark look >>> redesign is ready that might be 0.11.0. >>> >>> eduardo >>> >>> >>> On 02.07.20 20:02, Tarmo Johannes wrote: >>>> Hi! >>>> >>>> There is also software that never goes above 0.x.y. Still, I >>>> agree, would be good to change it. >>>> >>>> The current 0.9.8 introduced a lot of changes, I think it is good >>>> to keep that in use for couple of months, do only bug fixes or >>>> other minor changes to the code (and use other branches and >>>> alternative builds for bigger things, if necessary) and then >>>> release it as 1.0.0 when the current base seems well tested and >>>> users happy. >>>> >>>> tarmo >>>> >>>> tarmo >>>> Yes, it would be logical. >>>> >>>> Kontakt joachim heintz (<jh...@jo... >>>> <mailto:jh...@jo...>>) kirjutas kuupäeval N, 2. juuli 2020 >>>> kell 12:08: >>>> >>>> hi tarmo - >>>> >>>> thanks for explaining. my surprise is simple: for my >>>> everyday's >>>> understanding, after 0.9 the 1.0 should follow. i understand >>>> what you >>>> and eduardo mean, but the zero in first place after more than >>>> ten years >>>> CsoundQt is strange for me. >>>> >>>> (Cabbage is now at 2.3.0 and is not older; Blue is at 2.8.0.) >>>> >>>> as this release is a major one, perhaps you and eduardo can >>>> consider to >>>> make now the step to 1.0.0. more intuitive for me (and i >>>> assume for >>>> some others), and more appropriate for the developement >>>> state of >>>> csoundqt, in my opinion. >>>> >>>> cheers - >>>> joachim >>>> >>>> >>>> On 01/07/2020 20:08, Tarmo Johannes wrote: >>>> > Hi, >>>> > >>>> > Let's discuss the version policy a bit. >>>> > I continued what Andrés Cabrera started (that does not seem >>>> most >>>> > logical to me nowadays) - >>>> > the version tags in git history are: >>>> > >>>> > 0.7.0 >>>> > 0.7.0-beta >>>> > 0.7.1 >>>> > 0.7.2 >>>> > 0.7.3 >>>> > 0.7.4 >>>> > 0.8.0 >>>> > 0.8.0-win >>>> > 0.8.1 >>>> > 0.8.2 >>>> > 0.8.3 >>>> > 0.9.0 >>>> > 0.9.1 >>>> > 0.9.2 >>>> > 0.9.2.1 >>>> > 0.9.2.2 >>>> > 0.9.3 >>>> > 0.9.3-beta >>>> > 0.9.4 >>>> > 0.9.4-beta >>>> > 0.9.4-rc1 >>>> > 0.9.5 >>>> > 0.9.5-beta >>>> > 0.9.6-rc1 >>>> > 0.9.6-rc2 >>>> > 0.9.7 >>>> > 0.9.7-rc1 >>>> > 0.9.8-beta >>>> > 0.9.8-rc1 >>>> > 0.9.8-rc3 >>>> > v0.9.8 >>>> > >>>> > so far the the version has start always with 0 (as usually >>>> in beta >>>> > releases), minor version showed bing changes in API (as >>>> like for >>>> > support from Csound5 to Csound6 0.8->0.9) patch version >>>> important new >>>> > features or bug fixes. The small bug fixes were marked >>>> sometimes with .1 >>>> > or .2, sometimes I have uploaded builds with -1 or -2 in the >>>> end. Not a >>>> > very good and clear system. >>>> > >>>> > If we follow the old logic, the recent small fixes should >>>> give an extra >>>> > number to v0.9.8 since there were no significant new >>>> implementations >>>> > thus perhaps v0.9.8.1 or v0.9.8-1. v0.10 is OK for me, but >>>> what is the >>>> > new logic after that? >>>> > >>>> > Of course it would be better to use the major version, minor >>>> version and >>>> > patch version as usually, thus let's say we had 1.0.0 >>>> released and this >>>> > fix release would be now 1.0.1; when we will have something >>>> new added, >>>> > it would make 1.1.0, when we get to Csound7 support >>>> (perhaps) it would >>>> > make 2.0.0 etc >>>> > >>>> > But where to make the break to 1.0.0? After some patch >>>> versions of the >>>> > current until everybody seems happy? >>>> > >>>> > Anyway, it is just a number. >>>> > >>>> > Eduardo, whatever the number is, I guess I should make new >>>> Mac, Windows >>>> > and AppImage builds from develop and add them to 0.10? >>>> > >>>> > tarmo >>>> > >>>> > Kontakt joachim heintz (<jh...@jo... >>>> <mailto:jh...@jo...> >>>> > <mailto:jh...@jo... <mailto:jh...@jo...>>>) >>>> kirjutas kuupäeval K, 1. juuli 2020 kell >>>> > 16:14: >>>> > >>>> > why not 1.0.0?!? >>>> > do you want to keep the 0.xx forever? >>>> > >>>> > cheers - >>>> > joachim >>>> > >>>> > >>>> > >>>> > On 01/07/2020 14:22, Eduardo Moguillansky wrote: >>>> > > >>>> > > 0.10 >>>> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> >>>> > > >>>> > > Repository: CsoundQt/CsoundQt >>>> > <https://github.com/CsoundQt/CsoundQt> · >>>> > > Tag: v0.10.0 >>>> <https://github.com/CsoundQt/CsoundQt/tree/v0.10.0> · >>>> > > Commit: e2576c5 >>>> > > >>>> > >>>> <https://github.com/CsoundQt/CsoundQt/commit/e2576c53d5acb6c678f857d88ee2582442459fd5> >>>> >>>> > >>>> > > · Released by: gesellkammer >>>> <https://github.com/gesellkammer> >>>> > > >>>> > > >>>> > > Changes since 0.9.8 >>>> > > >>>> > > >>>> > > Bugs fixed >>>> > > >>>> > > * toolbar in mac fixed >>>> > > * graph widget for tables now initializes correctly >>>> and follows >>>> > > negative indexes (to set the table number) as it >>>> should >>>> > > * table plot widget was upside down, now fixed >>>> > > * Graph widget example fixed >>>> > > >>>> > > — >>>> > > >>>> > > This release has 2 assets: >>>> > > >>>> > > * Source code (zip) >>>> > > * Source code (tar.gz) >>>> > > >>>> > > Visit the release page >>>> > > >>>> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> to >>>> > download >>>> > > them. >>>> > > >>>> > > — >>>> > > You are receiving this because you are watching this >>>> repository. >>>> > > View it on GitHub >>>> > > >>>> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> or >>>> > > unsubscribe >>>> > > >>>> > >>>> <https://github.com/CsoundQt/CsoundQt/unsubscribe_via_email/AAQYHKWDLXF645EPEIWT623RZMS75ANCNFSM4ANME2IQ> >>>> >>>> > >>>> > > from all notifications for this repository. >>>> > > >>>> > >>>> > >>>> > _______________________________________________ >>>> > Qutecsound-devel mailing list >>>> > Qut...@li... >>>> <mailto:Qut...@li...> >>>> > <mailto:Qut...@li... >>>> <mailto:Qut...@li...>> >>>> > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel >>>> > >>>> >>>> >>>> >>>> _______________________________________________ >>>> Qutecsound-users mailing list >>>> Qut...@li... >>>> <mailto:Qut...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/qutecsound-users >>> |
|
From: joachim h. <jh...@jo...> - 2020-07-02 18:49:09
|
perhaps i have to represent the unreasonable part here: i don't agree. i had a talk today with some students. to all this 0.10 number appeared strange, and looked like many steps back (we did not count 0.09. before as csound does). joachim On 02/07/2020 20:38, Tarmo Johannes wrote: > I agree. > Tarmo > > N, 2. juuli 2020 21:30 Eduardo Moguillansky > <edu...@gm... <mailto:edu...@gm...>> > kirjutas: > > To go forward I would propose the following scheme: > > Major release, when major things happen: switching from qt5 to qt6, > switching from csound6 to csound7, switching from a certain file > format to another, etc. Most importantly, there is no backwards > compatibility between major versions. > > Minor release for things that add core functionality, new widgets, > etc. A .csd which worked in a previous version might need to be > adapted, but there is certain respect for backward compatibility. > > Patch: these are bug fixes. If you are happy with how the program > runs, you don't need to update. > > I would propose to start that scheme now. This is a minor release, > in the sense that there is backwards comptability. So we use the > next number in minor releases: 10 (these are numbers and not digits) > > In order to not mess up more with the git history I would just > release the bug fixes we have until now as 0.10.0 and upload the > builds (I got to build the mac version correctly!) and any other bug > fixes will go as 0.10.1, 0.10.2, etc. Whenever the dark look > redesign is ready that might be 0.11.0. > > eduardo > > > On 02.07.20 20:02, Tarmo Johannes wrote: >> Hi! >> >> There is also software that never goes above 0.x.y. Still, I >> agree, would be good to change it. >> >> The current 0.9.8 introduced a lot of changes, I think it is good >> to keep that in use for couple of months, do only bug fixes or >> other minor changes to the code (and use other branches and >> alternative builds for bigger things, if necessary) and then >> release it as 1.0.0 when the current base seems well tested and >> users happy. >> >> tarmo >> >> tarmo >> Yes, it would be logical. >> >> Kontakt joachim heintz (<jh...@jo... >> <mailto:jh...@jo...>>) kirjutas kuupäeval N, 2. juuli 2020 >> kell 12:08: >> >> hi tarmo - >> >> thanks for explaining. my surprise is simple: for my everyday's >> understanding, after 0.9 the 1.0 should follow. i understand >> what you >> and eduardo mean, but the zero in first place after more than >> ten years >> CsoundQt is strange for me. >> >> (Cabbage is now at 2.3.0 and is not older; Blue is at 2.8.0.) >> >> as this release is a major one, perhaps you and eduardo can >> consider to >> make now the step to 1.0.0. more intuitive for me (and i >> assume for >> some others), and more appropriate for the developement state of >> csoundqt, in my opinion. >> >> cheers - >> joachim >> >> >> On 01/07/2020 20:08, Tarmo Johannes wrote: >> > Hi, >> > >> > Let's discuss the version policy a bit. >> > I continued what Andrés Cabrera started (that does not seem >> most >> > logical to me nowadays) - >> > the version tags in git history are: >> > >> > 0.7.0 >> > 0.7.0-beta >> > 0.7.1 >> > 0.7.2 >> > 0.7.3 >> > 0.7.4 >> > 0.8.0 >> > 0.8.0-win >> > 0.8.1 >> > 0.8.2 >> > 0.8.3 >> > 0.9.0 >> > 0.9.1 >> > 0.9.2 >> > 0.9.2.1 >> > 0.9.2.2 >> > 0.9.3 >> > 0.9.3-beta >> > 0.9.4 >> > 0.9.4-beta >> > 0.9.4-rc1 >> > 0.9.5 >> > 0.9.5-beta >> > 0.9.6-rc1 >> > 0.9.6-rc2 >> > 0.9.7 >> > 0.9.7-rc1 >> > 0.9.8-beta >> > 0.9.8-rc1 >> > 0.9.8-rc3 >> > v0.9.8 >> > >> > so far the the version has start always with 0 (as usually >> in beta >> > releases), minor version showed bing changes in API (as >> like for >> > support from Csound5 to Csound6 0.8->0.9) patch version >> important new >> > features or bug fixes. The small bug fixes were marked >> sometimes with .1 >> > or .2, sometimes I have uploaded builds with -1 or -2 in the >> end. Not a >> > very good and clear system. >> > >> > If we follow the old logic, the recent small fixes should >> give an extra >> > number to v0.9.8 since there were no significant new >> implementations >> > thus perhaps v0.9.8.1 or v0.9.8-1. v0.10 is OK for me, but >> what is the >> > new logic after that? >> > >> > Of course it would be better to use the major version, minor >> version and >> > patch version as usually, thus let's say we had 1.0.0 >> released and this >> > fix release would be now 1.0.1; when we will have something >> new added, >> > it would make 1.1.0, when we get to Csound7 support >> (perhaps) it would >> > make 2.0.0 etc >> > >> > But where to make the break to 1.0.0? After some patch >> versions of the >> > current until everybody seems happy? >> > >> > Anyway, it is just a number. >> > >> > Eduardo, whatever the number is, I guess I should make new >> Mac, Windows >> > and AppImage builds from develop and add them to 0.10? >> > >> > tarmo >> > >> > Kontakt joachim heintz (<jh...@jo... >> <mailto:jh...@jo...> >> > <mailto:jh...@jo... <mailto:jh...@jo...>>>) >> kirjutas kuupäeval K, 1. juuli 2020 kell >> > 16:14: >> > >> > why not 1.0.0?!? >> > do you want to keep the 0.xx forever? >> > >> > cheers - >> > joachim >> > >> > >> > >> > On 01/07/2020 14:22, Eduardo Moguillansky wrote: >> > > >> > > 0.10 >> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> >> > > >> > > Repository: CsoundQt/CsoundQt >> > <https://github.com/CsoundQt/CsoundQt> · >> > > Tag: v0.10.0 >> <https://github.com/CsoundQt/CsoundQt/tree/v0.10.0> · >> > > Commit: e2576c5 >> > > >> > >> <https://github.com/CsoundQt/CsoundQt/commit/e2576c53d5acb6c678f857d88ee2582442459fd5> >> > >> > > · Released by: gesellkammer >> <https://github.com/gesellkammer> >> > > >> > > >> > > Changes since 0.9.8 >> > > >> > > >> > > Bugs fixed >> > > >> > > * toolbar in mac fixed >> > > * graph widget for tables now initializes correctly >> and follows >> > > negative indexes (to set the table number) as it >> should >> > > * table plot widget was upside down, now fixed >> > > * Graph widget example fixed >> > > >> > > — >> > > >> > > This release has 2 assets: >> > > >> > > * Source code (zip) >> > > * Source code (tar.gz) >> > > >> > > Visit the release page >> > > >> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> to >> > download >> > > them. >> > > >> > > — >> > > You are receiving this because you are watching this >> repository. >> > > View it on GitHub >> > > >> <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> or >> > > unsubscribe >> > > >> > >> <https://github.com/CsoundQt/CsoundQt/unsubscribe_via_email/AAQYHKWDLXF645EPEIWT623RZMS75ANCNFSM4ANME2IQ> >> > >> > > from all notifications for this repository. >> > > >> > >> > >> > _______________________________________________ >> > Qutecsound-devel mailing list >> > Qut...@li... >> <mailto:Qut...@li...> >> > <mailto:Qut...@li... >> <mailto:Qut...@li...>> >> > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel >> > >> >> >> >> _______________________________________________ >> Qutecsound-users mailing list >> Qut...@li... <mailto:Qut...@li...> >> https://lists.sourceforge.net/lists/listinfo/qutecsound-users > |
|
From: Tarmo J. <trm...@gm...> - 2020-07-02 18:38:32
|
I agree. Tarmo N, 2. juuli 2020 21:30 Eduardo Moguillansky <edu...@gm...> kirjutas: > To go forward I would propose the following scheme: > > Major release, when major things happen: switching from qt5 to qt6, > switching from csound6 to csound7, switching from a certain file format to > another, etc. Most importantly, there is no backwards compatibility between > major versions. > > Minor release for things that add core functionality, new widgets, etc. A > .csd which worked in a previous version might need to be adapted, but there > is certain respect for backward compatibility. > > Patch: these are bug fixes. If you are happy with how the program runs, > you don't need to update. > > I would propose to start that scheme now. This is a minor release, in the > sense that there is backwards comptability. So we use the next number in > minor releases: 10 (these are numbers and not digits) > > In order to not mess up more with the git history I would just release the > bug fixes we have until now as 0.10.0 and upload the builds (I got to build > the mac version correctly!) and any other bug fixes will go as 0.10.1, > 0.10.2, etc. Whenever the dark look redesign is ready that might be 0.11.0. > > eduardo > > > On 02.07.20 20:02, Tarmo Johannes wrote: > > Hi! > > There is also software that never goes above 0.x.y. Still, I agree, would > be good to change it. > > The current 0.9.8 introduced a lot of changes, I think it is good to keep > that in use for couple of months, do only bug fixes or other minor changes > to the code (and use other branches and alternative builds for bigger > things, if necessary) and then release it as 1.0.0 when the current base > seems well tested and users happy. > > tarmo > > tarmo > Yes, it would be logical. > > Kontakt joachim heintz (<jh...@jo...>) kirjutas kuupäeval N, 2. > juuli 2020 kell 12:08: > >> hi tarmo - >> >> thanks for explaining. my surprise is simple: for my everyday's >> understanding, after 0.9 the 1.0 should follow. i understand what you >> and eduardo mean, but the zero in first place after more than ten years >> CsoundQt is strange for me. >> >> (Cabbage is now at 2.3.0 and is not older; Blue is at 2.8.0.) >> >> as this release is a major one, perhaps you and eduardo can consider to >> make now the step to 1.0.0. more intuitive for me (and i assume for >> some others), and more appropriate for the developement state of >> csoundqt, in my opinion. >> >> cheers - >> joachim >> >> >> On 01/07/2020 20:08, Tarmo Johannes wrote: >> > Hi, >> > >> > Let's discuss the version policy a bit. >> > I continued what Andrés Cabrera started (that does not seem most >> > logical to me nowadays) - >> > the version tags in git history are: >> > >> > 0.7.0 >> > 0.7.0-beta >> > 0.7.1 >> > 0.7.2 >> > 0.7.3 >> > 0.7.4 >> > 0.8.0 >> > 0.8.0-win >> > 0.8.1 >> > 0.8.2 >> > 0.8.3 >> > 0.9.0 >> > 0.9.1 >> > 0.9.2 >> > 0.9.2.1 >> > 0.9.2.2 >> > 0.9.3 >> > 0.9.3-beta >> > 0.9.4 >> > 0.9.4-beta >> > 0.9.4-rc1 >> > 0.9.5 >> > 0.9.5-beta >> > 0.9.6-rc1 >> > 0.9.6-rc2 >> > 0.9.7 >> > 0.9.7-rc1 >> > 0.9.8-beta >> > 0.9.8-rc1 >> > 0.9.8-rc3 >> > v0.9.8 >> > >> > so far the the version has start always with 0 (as usually in beta >> > releases), minor version showed bing changes in API (as like for >> > support from Csound5 to Csound6 0.8->0.9) patch version important new >> > features or bug fixes. The small bug fixes were marked sometimes with >> .1 >> > or .2, sometimes I have uploaded builds with -1 or -2 in the end. Not a >> > very good and clear system. >> > >> > If we follow the old logic, the recent small fixes should give an extra >> > number to v0.9.8 since there were no significant new implementations >> > thus perhaps v0.9.8.1 or v0.9.8-1. v0.10 is OK for me, but what is the >> > new logic after that? >> > >> > Of course it would be better to use the major version, minor version >> and >> > patch version as usually, thus let's say we had 1.0.0 released and >> this >> > fix release would be now 1.0.1; when we will have something new added, >> > it would make 1.1.0, when we get to Csound7 support (perhaps) it would >> > make 2.0.0 etc >> > >> > But where to make the break to 1.0.0? After some patch versions of the >> > current until everybody seems happy? >> > >> > Anyway, it is just a number. >> > >> > Eduardo, whatever the number is, I guess I should make new Mac, Windows >> > and AppImage builds from develop and add them to 0.10? >> > >> > tarmo >> > >> > Kontakt joachim heintz (<jh...@jo... >> > <mailto:jh...@jo...>>) kirjutas kuupäeval K, 1. juuli 2020 >> kell >> > 16:14: >> > >> > why not 1.0.0?!? >> > do you want to keep the 0.xx forever? >> > >> > cheers - >> > joachim >> > >> > >> > >> > On 01/07/2020 14:22, Eduardo Moguillansky wrote: >> > > >> > > 0.10 < >> https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> >> > > >> > > Repository: CsoundQt/CsoundQt >> > <https://github.com/CsoundQt/CsoundQt> · >> > > Tag: v0.10.0 <https://github.com/CsoundQt/CsoundQt/tree/v0.10.0> >> · >> > > Commit: e2576c5 >> > > >> > < >> https://github.com/CsoundQt/CsoundQt/commit/e2576c53d5acb6c678f857d88ee2582442459fd5 >> > >> > >> > > · Released by: gesellkammer <https://github.com/gesellkammer> >> > > >> > > >> > > Changes since 0.9.8 >> > > >> > > >> > > Bugs fixed >> > > >> > > * toolbar in mac fixed >> > > * graph widget for tables now initializes correctly and follows >> > > negative indexes (to set the table number) as it should >> > > * table plot widget was upside down, now fixed >> > > * Graph widget example fixed >> > > >> > > — >> > > >> > > This release has 2 assets: >> > > >> > > * Source code (zip) >> > > * Source code (tar.gz) >> > > >> > > Visit the release page >> > > <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> to >> > download >> > > them. >> > > >> > > — >> > > You are receiving this because you are watching this repository. >> > > View it on GitHub >> > > <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> or >> > > unsubscribe >> > > >> > < >> https://github.com/CsoundQt/CsoundQt/unsubscribe_via_email/AAQYHKWDLXF645EPEIWT623RZMS75ANCNFSM4ANME2IQ >> > >> > >> > > from all notifications for this repository. >> > > >> > >> > >> > _______________________________________________ >> > Qutecsound-devel mailing list >> > Qut...@li... >> > <mailto:Qut...@li...> >> > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel >> > >> > > > _______________________________________________ > Qutecsound-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/qutecsound-users > > |
|
From: Tarmo J. <trm...@gm...> - 2020-07-02 18:02:48
|
Hi! There is also software that never goes above 0.x.y. Still, I agree, would be good to change it. The current 0.9.8 introduced a lot of changes, I think it is good to keep that in use for couple of months, do only bug fixes or other minor changes to the code (and use other branches and alternative builds for bigger things, if necessary) and then release it as 1.0.0 when the current base seems well tested and users happy. tarmo tarmo Yes, it would be logical. Kontakt joachim heintz (<jh...@jo...>) kirjutas kuupäeval N, 2. juuli 2020 kell 12:08: > hi tarmo - > > thanks for explaining. my surprise is simple: for my everyday's > understanding, after 0.9 the 1.0 should follow. i understand what you > and eduardo mean, but the zero in first place after more than ten years > CsoundQt is strange for me. > > (Cabbage is now at 2.3.0 and is not older; Blue is at 2.8.0.) > > as this release is a major one, perhaps you and eduardo can consider to > make now the step to 1.0.0. more intuitive for me (and i assume for > some others), and more appropriate for the developement state of > csoundqt, in my opinion. > > cheers - > joachim > > > On 01/07/2020 20:08, Tarmo Johannes wrote: > > Hi, > > > > Let's discuss the version policy a bit. > > I continued what Andrés Cabrera started (that does not seem most > > logical to me nowadays) - > > the version tags in git history are: > > > > 0.7.0 > > 0.7.0-beta > > 0.7.1 > > 0.7.2 > > 0.7.3 > > 0.7.4 > > 0.8.0 > > 0.8.0-win > > 0.8.1 > > 0.8.2 > > 0.8.3 > > 0.9.0 > > 0.9.1 > > 0.9.2 > > 0.9.2.1 > > 0.9.2.2 > > 0.9.3 > > 0.9.3-beta > > 0.9.4 > > 0.9.4-beta > > 0.9.4-rc1 > > 0.9.5 > > 0.9.5-beta > > 0.9.6-rc1 > > 0.9.6-rc2 > > 0.9.7 > > 0.9.7-rc1 > > 0.9.8-beta > > 0.9.8-rc1 > > 0.9.8-rc3 > > v0.9.8 > > > > so far the the version has start always with 0 (as usually in beta > > releases), minor version showed bing changes in API (as like for > > support from Csound5 to Csound6 0.8->0.9) patch version important new > > features or bug fixes. The small bug fixes were marked sometimes with .1 > > or .2, sometimes I have uploaded builds with -1 or -2 in the end. Not a > > very good and clear system. > > > > If we follow the old logic, the recent small fixes should give an extra > > number to v0.9.8 since there were no significant new implementations > > thus perhaps v0.9.8.1 or v0.9.8-1. v0.10 is OK for me, but what is the > > new logic after that? > > > > Of course it would be better to use the major version, minor version and > > patch version as usually, thus let's say we had 1.0.0 released and this > > fix release would be now 1.0.1; when we will have something new added, > > it would make 1.1.0, when we get to Csound7 support (perhaps) it would > > make 2.0.0 etc > > > > But where to make the break to 1.0.0? After some patch versions of the > > current until everybody seems happy? > > > > Anyway, it is just a number. > > > > Eduardo, whatever the number is, I guess I should make new Mac, Windows > > and AppImage builds from develop and add them to 0.10? > > > > tarmo > > > > Kontakt joachim heintz (<jh...@jo... > > <mailto:jh...@jo...>>) kirjutas kuupäeval K, 1. juuli 2020 kell > > 16:14: > > > > why not 1.0.0?!? > > do you want to keep the 0.xx forever? > > > > cheers - > > joachim > > > > > > > > On 01/07/2020 14:22, Eduardo Moguillansky wrote: > > > > > > 0.10 <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0 > > > > > > > > Repository: CsoundQt/CsoundQt > > <https://github.com/CsoundQt/CsoundQt> · > > > Tag: v0.10.0 <https://github.com/CsoundQt/CsoundQt/tree/v0.10.0> > · > > > Commit: e2576c5 > > > > > < > https://github.com/CsoundQt/CsoundQt/commit/e2576c53d5acb6c678f857d88ee2582442459fd5 > > > > > > > · Released by: gesellkammer <https://github.com/gesellkammer> > > > > > > > > > Changes since 0.9.8 > > > > > > > > > Bugs fixed > > > > > > * toolbar in mac fixed > > > * graph widget for tables now initializes correctly and follows > > > negative indexes (to set the table number) as it should > > > * table plot widget was upside down, now fixed > > > * Graph widget example fixed > > > > > > — > > > > > > This release has 2 assets: > > > > > > * Source code (zip) > > > * Source code (tar.gz) > > > > > > Visit the release page > > > <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> to > > download > > > them. > > > > > > — > > > You are receiving this because you are watching this repository. > > > View it on GitHub > > > <https://github.com/CsoundQt/CsoundQt/releases/tag/v0.10.0> or > > > unsubscribe > > > > > < > https://github.com/CsoundQt/CsoundQt/unsubscribe_via_email/AAQYHKWDLXF645EPEIWT623RZMS75ANCNFSM4ANME2IQ > > > > > > > from all notifications for this repository. > > > > > > > > > _______________________________________________ > > Qutecsound-devel mailing list > > Qut...@li... > > <mailto:Qut...@li...> > > https://lists.sourceforge.net/lists/listinfo/qutecsound-devel > > > |
