They should be optimized for using audio programs and this is interesting for our hardware list too.
I know this can be a protected thing, but it would help to fine optimal hardware.
Dane & I talked about the hardware spec on this very forum, several times (until TTS gave up the ghost post-2018) so I donât think the specs are secret : back then, we were selling AMD-based configs built on Asus FM2A55-style motherboards. You can look that up in a search engine to get the rest of the details (onboard RealTek NIC, Realtek HDA and so on). We never managed to make them run reliably on Haiku in recent years, so if you insist on adding them to the HCL, I would add a big fat proviso, like âreboot Haiku a couple times a day to avoid KDLs, or avoid prolonged media/audio playbackâ⌠But itâs your site so itâs entirely your decision whether you want to be level with readers or not
The latest news is that they have stopped the sales due to stability issues, and are working on porting their software to Genode with some kind of compatibility layer thatâs reusing parts of Haiku sourcecode.
So, what is demanded prayerfully, there was for Haiku:
âA native applicationâ, in addition highly professional and commercial - in the positive sense!
So it becomes nothing - with Haiku!
The biggest problem is, once theyâve left, theyâll probably never come back, no matter what progress haiku makes. The last haiku legend is gone as well. The only, last professional company that worked with haiku.
I would have wished there had been better cooperation here. Of course Tune Tracker is a relic from the BeOS days but they still used Haiku with the alpha4. Couldnât they have found a solution together here, or shouldnât it have been better?
Many are calling for solid hardware that fully supports Haiku, this could have been done in cooperation with TTS.
But I guess Iâm thinking again specifically and differently from the rest.
@ ttcoder Nevertheless, I wish you the best of luck from Tune Tracker System and continue to insist, even if not on haiku.
If alpha4 was stable for their purposes, why not stick with it?
When I did maintenance on small, embedded pbx systems (AllWorx), I never installed the latest software - I had to test new builds and maintain my own âgenerally available listâ.
because the customers like to have the latest hardware and the hardware that was available at the time of alpha 4 is so old that it can no longer be procured. Canât sell anything used.
The workflow for TuneTracker is quite different to an embedded system - the radio station users would be using the Haiku boxes to import music to the system, arrange schedules etc; so there is lots of use of the actual terminal.
In larger radio stations with other playout systems you would have multiple machines but all running bits of the same overall package; none can really be cut down hugely.
Also, I donât think they even had particularly stable hardware for A4 anyway.
And a second also - there were constant reports of issues with soundcards. Radio stations of any scale at all do not use analogue soundcards anymore; they AES67 audio over IP⌠the continued focus on soundcard drivers on their Genode based OS port is very backward.
I donât think any version was stable enough, they always had various crashes and also trouble finding gompatible hardware that fit their needs (serial ports, working and reliable sound input and output, âŚ)
From my point of view, I think they could have gotten more involved in fixing bugs. They sent us bugreports for various problems, some test cases, but I donât remember any case where they sent us a patch to integrate.
So the outcome is that: if you want to run Haiku in a production system now, expect to run into many problems because itâs in beta stage and thereâs no commercial support. This can be counteracted by the fact that itâs opensource and willing to accept patches, so what youâd pay in support otherwise, you have to pay in hiring a developer to do things. Which I guess they couldnât or didnât want to do? Or not in a permanent way at least.
There is a documented psychological effect that people tend to be more upset over losing something than they are happy about finding something of equal value.
I think that is at play here. It is only one developer choosing to hedge their bets by making a compatibility layer so their software runs on a different platform. It can be argued that is totally sensible like having lifeboats on a ship.
I for one am glad that Tunetracker has decided to hedge its bets with another niche OS rather than just go with Windows, Macintosh, Linux. Similarly, those of us who support niche OS should be encouraging people to choose one that meets their needs best rather than saying it must be Haiku or Genode, MorphOS, or whatever. If we insist people can only be loyal to one OS, then we guarantee they will go with one of those that are seen as too big to fail.
Rather than worrying about the potential loss of one developer, imagine if one percent of the developers on Windows, Macintosh or linux were to spend time coding for any of the niche OS. That would dwarf the number of existing third party developers on any of these small players, and is what we should be aiming for.
Well⌠possibly a âquick fix solutionâ was alluringâŚ
Recently, Haiku updated the HDA driver and became more stable than it was 6-8 years ago, Hardware issues, like serial ports or SB Live, caused similar problems even on Linux/BSD/etc (so, these bugs reported were not Haiku specific).
I saw that clients can still buy the TT Command Center demo, user guide, and radio station software demo on a USB with Haiku for $19.95 USD.
Since @ttcoder is still available⌠maybe this is not as bad as it looksâŚ