• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

spinorama.org

I am late but things are getting ready to move to the main site.
Code:
pytest tests/
=========================================== test session starts ===========================================
platform linux -- Python 3.10.12, pytest-8.1.1, pluggy-1.4.0
rootdir: /home/pierre/src/spinorama
configfile: pyproject.toml
plugins: cov-5.0.0, anyio-4.3.0
collected 81 items                                                                                        


tests/test_auto.py .                                                                                [  1%]
tests/test_cea2034.py ...............                                                               [ 19%]
tests/test_contour.py ...........                                                                   [ 33%]
tests/test_estimates.py .....                                                                       [ 39%]
tests/test_filter.py .                                                                              [ 40%]
tests/test_go.py ............                                                                       [ 55%]
tests/test_html.py ....                                                                             [ 60%]
tests/test_load.py ........                                                                         [ 70%]
tests/test_loss.py .                                                                                [ 71%]
tests/test_peq.py ..                                                                                [ 74%]
tests/test_ranges.py .....                                                                          [ 80%]
tests/test_scores.py ..                                                                             [ 82%]
tests/test_website.py ............                                                                  [ 97%]
tests/test_weigths.py ..                                                                            [100%]
=========================================== 81 passed in 44.20s ===========================================

and

Code:
 npx vitest 
 RUN  v1.6.0 /home/pierre/src/spinorama
 ✓ src/website/plot.test.js (12)
 ✓ src/website/search.test.js (19)

 Test Files  2 passed (2)
      Tests  31 passed (31)
   Start at  22:59:12
   Duration  4.71s (transform 186ms, setup 0ms, collect 148ms, tests 151ms, environment 3.83s, prepare 3.99s)

Test coverage is still low but it is time to play with it.

Let's go to https://dev.spinorama.org and find bugs.

P.S.: the most likely are old version / cache error etc, please cleanup your cache, try again and tell me that you add to. If you are a developper, then go into the developer tool and tell me what you see. Patches are welcome.
 
Hey Pierre, thanks for mainting this awesome website! Love browsing and being able to compare all the data so nicely.
One thing I couldn't find was the phase of a speaker. Would it be possible to add phase to the on-axis graph? It's quite important when it comes to integrating different speakers (e.g. with a sub or mixing different speakers for a surround sound system or a live sound system for example) and would give clues to whether a speaker is FIR corrected or not.
 
Hey Pierre, thanks for mainting this awesome website! Love browsing and being able to compare all the data so nicely.
One thing I couldn't find was the phase of a speaker. Would it be possible to add phase to the on-axis graph? It's quite important when it comes to integrating different speakers (e.g. with a sub or mixing different speakers for a surround sound system or a live sound system for example) and would give clues to whether a speaker is FIR corrected or not.

The issue is that most measurements do not included the phase. If I had it we could of course display it or do some FIR filters for ex.
 
The issue is that most measurements do not included the phase. If I had it we could of course display it or do some FIR filters for ex.
Ah, that is unfortunate. Would it be possible to include phase with the measurements that do, or would that break the system when it's missing?
 
Ah, that is unfortunate. Would it be possible to include phase with the measurements that do, or would that break the system when it's missing?
with some code, it is easy to support phase plots.

Both Amir and Erin do not include phase information in the data they share. I do not have the energy to scan all the pictures with the data inside. The NFS can generate the phase information with the measurements (it is just the output format that changes). For ex SunAudio or Ascend Acoustic provide the phase information. GLL files also usually have the phase information but I have not extracted it. In general it would be great if Amir and Erin could export more data; I would love to have:
= the phase per measurement
= more angles for better plots
= max SPL kind of data
= access to the raw measurements at all points (to see if we could emulate an NFS system for ex)
etc
 
with some code, it is easy to support phase plots.

Both Amir and Erin do not include phase information in the data they share. I do not have the energy to scan all the pictures with the data inside. The NFS can generate the phase information with the measurements (it is just the output format that changes). For ex SunAudio or Ascend Acoustic provide the phase information. GLL files also usually have the phase information but I have not extracted it. In general it would be great if Amir and Erin could export more data; I would love to have:
= the phase per measurement
= more angles for better plots
= max SPL kind of data
= access to the raw measurements at all points (to see if we could emulate an NFS system for ex)
etc
Agreed, if it's not in the data, it's not worth the effort to try to get it from somewhere else, e.g. by tracing some pictures.
Maybe @amirm can change some of the export settings to deliver more data, ideally with no extra effort :)
I'll see if I can get a hold of Erin for the same request.
 
Hey there Piere,
Hope you're having a great day. First of all I'd like to thank you for the great website. I really appreciate it. With that said, I've come to see that a lot of the prices are wrong and to my knowledge there is no way to easily export the data? There are also some small UX issues. First things first is there anyway that someone like me or other volunteers could help you keep the database updated? I'm talking specifically about the price and availability since that is the one that changes all the time.

Thank you for all you do ^_^
 
Hey there Piere,
Hope you're having a great day. First of all I'd like to thank you for the great website. I really appreciate it. With that said, I've come to see that a lot of the prices are wrong and to my knowledge there is no way to easily export the data? There are also some small UX issues. First things first is there anyway that someone like me or other volunteers could help you keep the database updated? I'm talking specifically about the price and availability since that is the one that changes all the time.

Thank you for all you do ^_^
Hi,

help is welcome.

For UX issues: open bugs https://github.com/pierreaubert/spinorama/issues/new/choose
For metadata fixes, the easiest thing for me is if you do pull request on GitHub. A what?
In practice it is very easy to do:
Go to https://github.com/pierreaubert/spinorama/tree/develop/datas
You see a long list of metadata file one per letter in the alphabet. Let's suppose you want to fix a JBL speaker metadata:
Click in metadata_j.py and search for the speaker you are interested in, here JBL 3733, price is not in.
ex-jbl.jpg


Then you can edit with
ex-edit.jpg


Now just write the price:
Screenshot 2024-09-10 at 08.37.57.png



Then commit (aka send the new file to GitHub):
Screenshot 2024-09-10 at 08.38.33.png


Put a message of explanation and click:

Screenshot 2024-09-10 at 08.38.59.png


And you are done! You may see a slighlty different windows proposing you to recreate a pull request and that's fine too.

Pierre

P.S.: if that works and are motivated a lot of speakers are missing metadata; here are the possibilities:

Code:
    "": {
        "skip": True,
        "brand": "",
        "model": "",
        "type": "passive",
        "price": "",
        "amount": "pair",
        "shape": "bookshelves",
        "default_measurement": "eac",
        "measurements": {
            "eac": {
                "origin": "ASR",
                "origin": "ErinsAudioCorner",
                "format": "klippel",
                "reviews": {
                    "asr": "",
                    "eac": "",
                    "yt": "",
                },
                "review_published": "202404xx",
                "extras": {
                    "is_equed": False,
                },
                "specifications": {
                    "sensitivity": ,
                    "impedance": ,
                    "dispersion": {
                        "horizontal": ,
                        "vertical": ,
                    },
                    "SPL": {
                        "peak": ,
                    },
                    "size": {
                        "height": ,
                        "width": ,
                        "depth": ,
                    },
                    "weight": ,
                },
            },
        },
    },

and associated documentation is https://github.com/pierreaubert/spinorama/blob/develop/datas/__init__.py
 
I have been playing with filtering the Rankings and I am really impressed: since Ascend shared their spins, and the Fidelia review spin, the passive bookshelf speakers below 1.000 USD have incredible options in the top 3. :oops:


Spinorama.org is out of this world good. Like a Wikipedia body of knowledge to our audiophile hobby.
 
spinorama.org is moving to a real machine in a real datacenter. Copy is under way and should take a few hours with the current fabulous bandwidth available at home.

Monitoring will tell if it is more stable over time but we will see. For the curious, the last crash for a few hours was related to loss of power in Spain and the root cause for today's crash is unknown, most likely the server died for good. I was fed up to keep it running and I took a VPS.

OTO for developers, I am simplifying the code a lot to make it easier to install and then to use. The develop branch is unstable at the moment and should be avoided if you want a smooth experience.

P.
 
Thanks Pierre! Keep up the good work - I think you are doing a great service to the community! Cheers!
 
Today, spinorama fails to execute on Firefox. The error in JS console is:

Loading module from “https://www.spinorama.org/js3rd/fuse-7.0.0.min.mjs” was blocked because of a disallowed MIME type (“application/octet-stream”).

The file seems to be fine, but its server-provided datatype is not text/javascript which it probably should be.
 
Today, spinorama fails to execute on Firefox. The error in JS console is:

Loading module from “https://www.spinorama.org/js3rd/fuse-7.0.0.min.mjs” was blocked because of a disallowed MIME type (“application/octet-stream”).

The file seems to be fine, but its server-provided datatype is not text/javascript which it probably should be.
- Copy is not going well, connection keep breaking. It copied 20% in 12h.
- Yes error in nginx.conf and other small glitches in ssl configuration (fixed now, you need to reload and clear the cache for this file)

I will go after all of that after work.
 
Last edited:
Back
Top Bottom