Rune Update

dynobot

If or when the next update is released will there be an announcement via email, website, other... Or if it just going to be word of mouth?

Also I'd there any ETA?

domisol

+1 !
Same interest, same wonderings.
Good luck to the dev team.

Jean-David

Aquarius

The devs are busy as hell, and that is understandable.
So I guess no ETA is a good thing, I prefer to have a polished new version to have a rushed unfinished thing because of a deadline.

However, what would be nice to know is what will be included ? The Next and Dev branch on github have very little activity, so I guess the refactoring/modularity/evolution/surprises that the devs talk about is happening elsewhere on another non-public branch. THAT is not really in the spirit of openness. I mostly understand the reason why the alpha code is not yet public (no alpha tester whining about things broken/not working). But some kind of specification/change log/description would be nice.
(and don't forget things mostly work very well already, it's not like if there was a major bug somewhere that needed fixing ASAP).

ACX

Hi dynobot, all the updates are announced on the news in the website and also notified through social networks and newsletter, so there's a little chance you miss them if you follow RuneAudio

Aquarius wroteThe devs are busy as hell, and that is understandable.
So I guess no ETA is a good thing, I prefer to have a polished new version to have a rushed unfinished thing because of a deadline.

However, what would be nice to know is what will be included ? The Next and Dev branch on github have very little activity, so I guess the refactoring/modularity/evolution/surprises that the devs talk about is happening elsewhere on another non-public branch. THAT is not really in the spirit of openness. I mostly understand the reason why the alpha code is not yet public (no alpha tester whining about things broken/not working). But some kind of specification/change log/description would be nice.
(and don't forget things mostly work very well already, it's not like if there was a major bug somewhere that needed fixing ASAP).

We learned to avoid to talk about ETAs because we never manage to respect them

About the work in progress: I can confirm that we are temporarily working on private repositories. Although I agree with you that this could not be in the spirit of openness, we have some reasons to do so. One of them is the one you said, publishing something not yet usuable would only increase the hype and the pressure over us, and not help us in any way. Anyway our progress will be published soon, together with a couple of articles on the blog explaining the technical choices behind the rework.

domisol

Thanks ACX for having kept us informed, and once again, good luck for the next steps, we are all expecting to enjoy next version.

Jean-David

dynobot

ACX wroteHi dynobot, all the updates are announced on the news in the website and also notified through social networks and newsletter, so there's a little chance you miss them if you follow RuneAudio

Aquarius wroteThe devs are busy as hell, and that is understandable.
So I guess no ETA is a good thing, I prefer to have a polished new version to have a rushed unfinished thing because of a deadline.

However, what would be nice to know is what will be included ? The Next and Dev branch on github have very little activity, so I guess the refactoring/modularity/evolution/surprises that the devs talk about is happening elsewhere on another non-public branch. THAT is not really in the spirit of openness. I mostly understand the reason why the alpha code is not yet public (no alpha tester whining about things broken/not working). But some kind of specification/change log/description would be nice.
(and don't forget things mostly work very well already, it's not like if there was a major bug somewhere that needed fixing ASAP).
We learned to avoid to talk about ETAs because we never manage to respect them
About the work in progress: I can confirm that we are temporarily working on private repositories. Although I agree with you that this could not be in the spirit of openness, we have some reasons to do so. One of them is the one you said, publishing something not yet usuable would only increase the hype and the pressure over us, and not help us in any way. Anyway our progress will be published soon, together with a couple of articles on the blog explaining the technical choices behind the rework.

Thanks for the update ACX....

X-Mas is just around the corner....

dynobot

It also would be nice if Rune exploited the multi-core processors in the newer ARM Boards.

taskset -c -p 1 $(pidof mpd)

Been using it for years with x86 computers. Microsoft also now uses it by default on Windows 10 audio.

ACX

dynobot wroteIt also would be nice if Rune exploited the multi-core processors in the newer ARM Boards.

taskset -c -p 1 $(pidof mpd)

Been using it for years with x86 computers. Microsoft also now uses it by default on Windows 10 audio.

We will in the future.

waves

Not an ETA request. But I'm sure many would find it interesting to hear a little more elaborated status report. What major new changes have you added. Any benchmarks so far faster loading speeds? Anything that might feed our appetite for Rune news?

frengo

Scusatemi, so di essere fuori topic.
Solo un'informazione. E' possibile entrare in contatto, chattare o telefonare con qualcuno in lingua Italiana ? Chiedo troppo ?
Scusate se non ho sufficiente dimestichezza con l'inglese ma vi supplico di fornirmi un contatto telefonico o il contatto di qualche sviluppatore che possa parlare in italiano con me anche solo per tre minuti. Sono convinto di poter dare in cambio un mio contributo alle funzionalita' di Runeaudio, ma in inglese, anziche tre minuti, mi ci vorrebbe troppo tempo.

Grazie anticipate a chi possa accogliere la mia richiesta.

Francesco Pagliano. cell. 328 3384792

dynobot

frengo wroteScusatemi, so di essere fuori topic.
Solo un'informazione. E' possibile entrare in contatto, chattare o telefonare con qualcuno in lingua Italiana ? Chiedo troppo ?
Scusate se non ho sufficiente dimestichezza con l'inglese ma vi supplico di fornirmi un contatto telefonico o il contatto di qualche sviluppatore che possa parlare in italiano con me anche solo per tre minuti. Sono convinto di poter dare in cambio un mio contributo alle funzionalita' di Runeaudio, ma in inglese, anziche tre minuti, mi ci vorrebbe troppo tempo.

Grazie anticipate a chi possa accogliere la mia richiesta.

Francesco Pagliano. cell. 328 3384792

Se pensi di avere un contributo basta usare Google Translate per tradurre il vostro Itailian in inglese

frengo

Thank you, Dynobot. I think I managed to apply the advice.
Now the problem that I find with this excellent software is different in nature and I talk about it because it can be acceptable that a music lover could (should?) Be familiar with the English language. But I do not think it's normal that a music lover should become a programmer in order to use Linux Runeaudio the way you want. As a user (so I consider me) what should be the normal music lover, I saw that Runeaudio has already embedded some features of which I don't understand the indispensability while (by contrast) to enable other functions that I judge that it are reasonably necessary, to enable these features is needed to be an experienced Linux user, which for those who have no experience so far with Linux is somewhat tricky. For a music lover can be a normal thing to enable a TFT display instead of another, to make a search in a database of song titles, to switch a musical tank as a hard drive or an USB drive, to enable a DAC instead of the onboard outlet jack 3.5 mm (eg. of a Raspberry board), a remote control or something like that, but can't to be indispensable to become an expert user Linux to achieve and manage the device via SSH to enable these simple and obvious features. This may be acceptable only for ANY music lover who is also fond of computer science. I think it right if I conceive the use of RuneAudio (complete with DAC) only by the music lovers. To listen to the .mp3 there are already several years billions of devices from poor audio quality on sale a few euro. I hope to be understood for what I'm saying. Obviously will agree with me only purity music lovers, I don't hope to obtain understanding from those who use also Linux systems because for Linux users is easy to enable anything on a software ....
THANK YOU

waves

Not an ETA request. But I'm sure many would find it interesting to hear a little more elaborated status report. What major new changes have you added? Any benchmarks so far on faster loading speeds and UI? Screenshots from the in progress version? Anything that might feed our appetite for Rune news?

ACX

waves wroteNot an ETA request. But I'm sure many would find it interesting to hear a little more elaborated status report. What major new changes have you added? Any benchmarks so far on faster loading speeds and UI? Screenshots from the in progress version? Anything that might feed our appetite for Rune news?

Joking apart, we'll unveil soon our work. I also plan to write a couple of technical articles in the blog explaining all our choices.

waves

I choose to interpret the image as a hint that you devs are working on interplanetary laser mediated music streaming support for RuneAudio. Very cool! Looking forward to that and other new features.

BayleeWylie

I'm really looking forwards those explanations! I'm still new to this world so it's always nice to be able to understand what the changes are, what they mean and why they were made.

Keep up the great work!