This is elementary logic. Is the West so bad with logic...
Nevertheless, in many Western countries there are still laws issued almost under king Arthur, and it does not bother anyone. So why are You confused by the use of "USSR" in the historical name of the community? For your information, all identity documents issued in the USSR are still considered valid by the decision of the constitutional Court of the Russian Federation.Alcoholics Anonymous wrote: ↑Sat Jun 29, 2019 12:13 amThe USSR didn't exist in 2005 either. It would be very strange if I started producing documents that originated from "the dominion of Canada", "Upper Canada", "Lower Canada", "Rupert's Land" (where I am sitting right now), "Kanata" and so on. They're historical names.
First, I have already given You an example with the name of great Britain. No one is interested in what it was called before. There is only a modern name, and only it matters.
Secondly all of the devices You mentioned are irrelevant to the discussion TurboSound Control Interface. These devices have a different design, a different principle of operation, and even the name is written differently - separately:"Turbo Sound".
The merged spelling of the name "TurboSound" has existed since the creation of this control interface. You can see this by looking at the schematic diagram of this device in 2005.Alcoholics Anonymous wrote: ↑Sat Jun 29, 2019 12:13 amI'm not sure how you think you can change what "TurboSound" means ten years later. At least change the name to what it is, as in "TurboSound FM" or "TurboSound 2.0" if you are concerned about any confusion. Or maybe the name is "TurboSound Control Interface". In that case, it should be clear from the name "TurboSound Next" that no control interface is involved.
It's Your problem, it's none of our business. The only thing we care about is your violation of the license agreement. This should be corrected no matter what losses You suffer.
This is written so that You can not claim that it is impossible to make changes to existing software. ZX Spectrum Next team on its own initiative refused to use ULA+, which necessitated the alteration of existing software. This precedent does not allow You to say that there is no possibility to change the existing software. This possibility exists, and You have demonstrated it in the case of ULA+.
You are mistaken, the IORQGE is just designed to disable ALL internal ports of the ZX Spectrum. In the original ZX Spectrum there was only one such port - #FE. Unfortunately, the developers of the Western slopes still do not understand this. In contrast to Western developers in Russia understand the ideas of Altwasser, and embodied them in the bus NemoBus. That is why our peripherals initially have access to all 64k I/O port address space, while You, 37 years old, are unable to overcome port conflicts.
We don't really have this problem because we solved it 29 years ago, and in ZX Spectrum Next this problem can't be for one reason only - its expansion interface doesn't support 5V TTL peripherals, i.e. all existing hardware. Since there is no hardware that can be connected to the ZX Spectrum Next extension interface, there is no problem with the port conflict! In this case, I do not understand Your stubbornness and unwillingness to make it possible to block ALL ports of ZX Spectrum Next, given that it is impossible to connect any existing external equipment to ZX Spectrum Next.
You are mistaken, IORQGE decides everything! Altwasser is a talented and inventive hacker who introduced a number of ingenious technical solutions to the architecture of ZX Spectrum, but Sinclair Research did not find anyone worthy who could at least understand the ideas of Altwasser! For 37 years, the West did not understand how to eliminate the conflicts of ports.
You're wrong about everything. Sinclair left no legacy, he sold his property, and received £ 5,000,000 in compensation. Other than ownership, Sinclair had nothing to leave as a legacy to the ZX Spectrum community. Altwasser left a legacy, and in the USSR this legacy was used, unlike Western developers, who have not yet understood anything about this legacy. At first our clones were exact copies of ZX Spectrum architecture, but then we optimized the architecture to use more modern element base, and faster memory of domestic production. This made it possible to simplify the architecture, improve reliability and reduce the cost of the computer, without significant loss of software compatibility. As a result, in the USSR the market value of the most common domestic clone based on the 48K "Leningrad" Board was 3-4 times less than the cost of the original ZX Spectrum in the UK. At the same time, "Leningrad" initially supported the simultaneous connection of three joysticks Sinclair 1, Sinclair 2, Kempston, had RGB and composite video outputs, but did not have an edge expansion connector and a PAL-modulator. The absence of the edge connector was compensated by the presence of a layout field on the Board for self-expansion of the computer, which was usually used to add AY and expand up to 128k.Alcoholics Anonymous wrote: ↑Sat Jun 29, 2019 12:13 amAs for ts-config, the former USSR does not care about the Sinclair legacy. It started by smuggling a few examples of the Sinclair line into the USSR in 1985/1986 or so which led to several copies being made (incorrectly). This led to a different path of chaotic development that occurred long after Sinclair was commercially dead in the West. As a result you have a different experience that branched off from 1985/1986 in our timeline as you were isolated from the goings on of the rest of the world.
We're not interested in whether the ZX Spectrum Next team will ever add TurboSound FM to FPGA, or not. We are concerned that the ZX Spectrum Next command, by violating the license to use the TurboSound Control Interface, encourages the creation of software that will not work properly with hardware that uses this control interface legally. The difference is that if You implemented the correct TurboSound Control Interface in ZX Spectrum Next, then working in the "ZX Next" sub-mode would have no effect on all other devices using this control interface. But since the command ZX Spectrum Next, contrary to the existing ban, changed the TurboSound Control Interface, the execution of programs that support these illegal changes will lead to unpredictable operation of other equipment using this control interface. This chaos, which the team creates a ZX Spectrum Next, breaking the licensing terms, we do not need. The people of the USSR ZX Spectrum Community spent a lot of time and effort creating content for this interface, and allowed everyone to use this content for free for non-commercial purposes, through devices using the TurboSound Control Interface. At the same time, the TurboSound Control Interface itself and the music content are intangible assets with a certain market value. The market value depends on the degree of ordering of this intangible asset, and the chaos that the ZX Spectrum Next team creates by violating the license reduces the ordering of our intellectual property, and as a result reduces its market value. These actions command the ZX Spectrum Next cause direct financial loss USSR ZX Spectrum Community. Imagine a large barrel of honey, which for a long time was collected by members of the USSR ZX Spectrum Community. This barrel of honey has a certain value. But if we allow the ZX Spectrum Next team to throw a small spoonful of shit into this barrel of honey, then this barrel of spoiled honey will cost nothing more.Alcoholics Anonymous wrote: ↑Sat Jun 29, 2019 12:13 amIf there were a compatibility issue I might be more concerned. Fortunately there is no compatibility issue - the zx next will be able to use external turbosound fm devices and run its software. Should this be added to the fpga at some time, it will be easily added as well, but probably in the reverse direction of your suggestion. In your suggestion you assume the turbosound interface is in "turbosound control interface" mode and must change to next mode whereas we'd likely assume the reverse. In the meantime, a turbosound fm implementation is not claimed and people will not be able to run turbosound fm software without an external turbosound fm device. This shouldn't be a surprise as there are no fm devices implemented on the fpga.
If you're concerned about zx next sound programs running on other systems - it's very likely zx next programs will be using special features of the machine that will not run on those systems anyway. Even if it's just the music, the Russian machines cannot select ABC/ACB stereo, mono per AY, panning left & right, a third AY chip and so on. So it's only really the turbosound subset that will work. If anyone cares, they could also implement a mode switch as you suggested to reach that compatibility.
We understand why the ZX Spectrum Next team is trying to bring chaos to other projects. The goal is to deprecate other people's assets to be able to capture impaired assets, and then use them as their own content, as well as to promote their own alternative brands. ZX Spectrum Next team has already created its own illegal brand - "Turbo Sound Next", an alternative to the legitimate brand "TurboSound". Therefore, we point to the illegality of these actions of the ZX Spectrum Next team, and demand not only the elimination of their illegal changes in the TurboSound Control Interface, but also the removal of the illegal brand "Turbo Sound Next", and use in the future the only legitimate brand name "TurboSound".
You should understand that using the TurboSound Control Interface, You actually came to our house, where using our hospitality, were able to use the content created by us for free. We are traditionally hospitable to kind guests and are ready to share our achievements for non-commercial purposes. But instead of behaving as it is accepted at owners of this house, the ZX Spectrum Next team began to behave not as guests, and as the invaders establishing own rules in someone else's house. Naturally, we did not like it! We do not like invaders, and in Russian traditions, we treat them always the same - we destroy them!
Unfortunately, I must say that the ZX Spectrum Next team is not very respectful of other people's copyrights. This is not only my opinion, the same opinion is shared by the ZX-Uno team, as well as the authors of ULA+ and music for TurboSound. Because of this disrespectful attitude to copyright, the ZX Spectrum Next team has already received a ban on the use of musical compositions for TurboSound in its promotional video. This was the first warning. How things will develop in the future depends on the cooperation of the team ZX Spectrum Next. We hope that we will not have to resort to a court ban on the distribution of computers ZX Spectrum Next due to violation of the license to distribute TurboSound Control Interface. We would be very sorry if due to the disrespectful attitude to copyright on the part of the team ZX Spectrum Next, will suffer 3000 people who paid for this kickstarter. If it is not possible to agree with the ZX Spectrum Next team to correct illegal changes made by them to the TurboSound Control Interface in the ZX Spectrum Next computer, we will be forced to take measures available to us to protect our rights and our property. This is a rather costly and time-consuming procedure, and most likely we will have to ask to seize the assets of the project ZX Spectrum Next, to ensure the possibility of compensation of our costs. It will make a very dubious chance of success, and the imminent implementation of the project ZX Spectrum Next. At the same time, we are very respectful of the people who paid for this project, and therefore inform them in advance about possible problems in case of failure of the team ZX Spectrum Next to eliminate the illegal changes. Understand us, we don't want anyone to get in trouble, it's not personal - it's just business. We protect intangible assets owned by the USSR ZX Spectrum Community from illegal actions of the ZX Spectrum Next team that lead to the depreciation of these assets.
We look forward to the cooperation of the ZX Spectrum Next team in resolving this conflict.