Jump to content

Aishagain

Resident
  • Posts

    831
  • Joined

  • Last visited

Everything posted by Aishagain

  1. @Qie NiangaoYou ask "why?". I have asked them directly. I await their response. They do not appear to understand that by removing Somafm exposure to SL users they are most likely actually reducing the likelihood of them ever recovering any income from good intentioned users who then donate to Soma as per their occasional "begs". They also clearly do not understand the relationship between SecondLife audio streaming and Linden Lab, since the only involvement that SL actually has is the displaying of the stream in the region information. The stream is actually routed to the individual viewer directly from their server. Attempting to get royalties out of Linden Lab for streaming makes attempting to get blood from a stone appear child's play. Also it is just plain wrong. At best Linden Lab could be cited as a conduit for the streams and as such are no more liable to pay royalties to Soma as Soma are to pay them!
  2. I realise that I may have given the wrong impression about the Somafm streams and their playing of adverts. The only adverts that interrupt the music are adverts for the station (like a Station ID only a little more elaborate) and the occasional exhortation to support the station or channel. My error. Ashes and sackcloth are being donned as I speak (virtually).
  3. Agreed. The fact remains that a shared stream is not possible (though I gather that MOAP still works so maybe that gives us a workaround?).
  4. @WhirlyFizzleBingo. I didn't know that. I'd say that has a lot more to do with this than any of the specious reasons Soma have quoted to me thus far! However, how do we get around that block? It seems unlikely that simply disabling the metadata function would solve the issue and yet if an individual streams Soma via an external player or browser, they have stated that they "have no problem with that". Presented with that situation, it seems to me that Soma would have no case. Do we, in fact? It seems that Soma consider that they have a dominant position in streaming into SL and "they can no longer ignore this situation" . Put less prettily, they want to create a revenue stream from this. Unfortunately, by crudely targeting Linden Lab, they hit the wrong target, I suspect. The original artists get precious little from a stream, but now it seems the conduit wants a share of the pie.
  5. The above points are noted @bigmoe WhitfieldYour point is very interesting, I'll see how Soma respond to that. @Quistess Alpha You may not have noticed but the stream does, in fact, contain adverts for Somafm on a regular basis, they are just not very intrusive, being audio only. On your criteria no, it is not reasonable. It was a similar argument that was stated as their reason for blocking SL by DI.fm and was equally spurious for them, since the stream contained adverts, just not visual ones.
  6. @Qie NiangaoThat is the point I have made to Somafm and I am awaiting their reply. I am not holding my breath. @bigmoe Whitfield: pardon? I am not sure that I know what your comment means!
  7. It may not come as a surprise to some that SomaFM streams are no longer avaiable in Second Life. I have been in touch with SomaFM and the reason is simple. Soma have blocked Second Life because LL refused to pay any royalties on the music streams provided to SL by SomaFM. What your opinion of this will almost certainly vary, and of course the streams can still be played in external radio players, so the music is not unavailable to all, but for now the shared experience of music streaming to the region from SomaFM is no more. I do not hold out any hope of LL changing their attitude over this so we must, I guess, accept the situation. It is something that really needs to be addressed and it is the same for virtually (sic) all streaming services. The artists and the broadcasters need to be given due recompense for their medium
  8. It may not come as a surprise to some that SomaFM streams are no longer avaiable in Second Life. I have been in touch with SomaFM and the reason is simple. Soma have blocked Second Life because LL refused to pay any royalties on the music streams provided to SL by SomaFM. What your opinion of this will almost certainly vary, and of course the streams can still be played in external radio players, so the music is not unavailable to all, but for now the shared experience of music streaming to the region from SomaFM is no more. I do not hold out any hope of LL changing their attitude over this so we must, I guess, accept the situation. It is something that really needs to be addressed and it is the same for virtually (sic) all streaming services. The artists and the broadcasters need to be given due recompense for their medium.
  9. Going back a couple of years I had a similar issue...one DJ's stream simply would NOT play. Eventually I found out the the domain used by the stream rental operation had been classified as potentially malicious by my antivirus. I had to contact the AV support who shortly thereafter unblocked the domain.
  10. @RicDelMoro: OK so You are placing the blame for the microstuttering squarely on Firestorm's interpretation of EEP. I did not realise that it was not the same renderer as the Linden Lab viewer, I must admit I had assumed they had used the code as it had been provided by Linden Lab. In which case... @Beq Janus: what did you do ? If I am to assume that there is some difference, what IS different and please fix it! I cannot belive that Firestorm is so changed that such an obvious flaw cannot be corrected.
  11. This topic is of great interest to me since my system has a 1660Ti GPU (6GB vram) and 16GB system ram, an AMD Ryzen 9 CPU and yet some scenes slow my viewer to sub 10 FPS crawl. I use Firestorm 6.4.21 and I notice that this viewer is noticeably faster than the previous two EEP releases, water gives me no significant FPS hit (the previous two did), and while the viewer eats ram in crowded scenes, generally it runs well. One issue I do find is that if I am in a crowded location, even with reduced draw distance and quality, as low as mid, occasionally to get good FPS (above 25, say), I get micro-stutters regularly. I have "whitelisted" all the folders and .exe files I can, so I do not believe my AV is causing this. What IS causing this, I wonder and is Firestorm's EEP renderer significantly different to the LL viewer? As a 10 year FS user (or however long it is since Phoenix evolved into Firestorm), I am puzzled at what happens. EEP is a step-change in rendering, just as Windlight was all those years ago, but I did not expect it to hamstring my system as it does. So what am I doing wrong?
  12. @Mazidox Linden:Seeing as there was no post on the restart thread, is it safe to assume that the roll to the RC channels today was that intended for last week but postponed due to the AWS outage?
  13. But...but...but...it's raining outside!!
  14. Linden Support say there are undefined "database issues", affecting all accounts "intermittently". They were doing some maintenance earlier and it is now back up on the Grid Status Page. So basically the database cluster is SNAFU.
  15. Support says they have database issues (thought they'd "resolved that earlier". Looks like the elastic band broke. SNAFU.
  16. I must be a old fogey because for the life of me I do not see the point of 360 degree pictures.
  17. I stand corrected. I never realised that FS parcel Windlight could be altitude dependent. Seems I was also misled as to what the "shared Experience" rules were, I am now wiser.
  18. @Henri Beauchamp: Well you might well be correct, Henri, I won't argue. However since one of the changes that EEP addresses is parcel environment settings at different altitudes and this is something that could NOT be set with windlight rendering. That being unavailable, I would have thought that since eg I running a Windlight rendering viewer visit a friend's skybox, and this friend has set an altitude dependent environment, I would not see it: surely that breaks the shared experience rules? In the limit I don't care one way or the other, it was just how I had had it explained to me.
  19. You are, of course, right Solar. You always are, even when you are wrong. So it goes.
  20. I am aware of the commonly accepted interpretation of the term "rolling restart" . You refer to a literal interpretation of the term. I am also aware that LL rarely use the term to indicate a general restarting of region hosts.
  21. LL are jesting, surely? TheGrid status Page announces a Rolling Restart for Main Server this coming week. Rolling what?? Following on from the debacle of this past week's roll to the RC channels there IS nothing to roll! The new code was reverted; at least it was everywhere I go. Or will this be a revised version of that rolled to the RC channel last week, with a "Hail Mary" expectation that the changes they will have made cure the restarting issue that many regions suffered? What happened to QC testing via the RC channels first?
  22. I will just, and totally unofficially, restate that the use of EEP rendering was made mandatory by LL and any viewer significantly deviating from the default system is deviating from the "shared experience" that LL is so fond of restating. Firestorm undertook a "3 versions only" policy after the rules regarding the shared experience were forcibly restated by LLgovernance, but I am actually surprised that LL did not force the "retirement" of 6.3.9 earlier for the afore mentioned reasons. That "might" have been because they knew that early EEP viewers had significant performance penalties for even high-end systems. Like most folks I found 6.3.9 with Windlight rendering a far superior viewer in most ways even to 6.4.21, itself a big improvement on the previous two EEP versions.
×
×
  • Create New...