Announcement

Collapse
No announcement yet.

Using VituixCAD

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • GaryRoach
    replied
    Wow! Thank you trevordj. That treatise should cover my questions. I am still working through it. I think you should be rewriting the 2.0 manual. Thank you very much.

    GaryR

    Leave a comment:


  • trevordj
    replied
    Then, you should be able to see your simulated box in the crossover designer. You can do the same thing with your tweeter (using just free air parameters) and then start your sim. Make sure you are adding baffle diffraction to your sims until you actually measure. You can do this in Vituixcad as well but I find Jeff Bagby's Response Modeler better at doing that.

    Click image for larger version

Name:	Screenshot 2020-09-18 175850.jpg
Views:	415
Size:	394.4 KB
ID:	1451841

    Leave a comment:


  • trevordj
    replied
    Then just point to the file on your hard drive. Keep in mind that Vituixcad saves things with a txt extension (or you can choose frd which I always do). You may have to choose the filetype to make sure your file will show up if it is txt or frd.

    Click image for larger version  Name:	Screenshot 2020-09-18 174835.jpg Views:	0 Size:	388.5 KB ID:	1451836


    Do the same with the ZMA file unless you added it via the other option above

    Click image for larger version  Name:	Screenshot 2020-09-18 173551.jpg Views:	0 Size:	405.6 KB ID:	1451838

    Once you point to that frd and zma file you can hook a piece of wire from the amplifier to the speaker (add the speaker to the crossover and ground it if you haven't already). Then you should see your simulated enclosure frd in the six pack of images. Remember, for crossover design this does not have baffle diffraction simulated.



    Click image for larger version  Name:	Screenshot 2020-09-18 173002.jpg Views:	0 Size:	385.1 KB ID:	1451837

    Click image for larger version  Name:	Screenshot 2020-09-18 173029.jpg Views:	0 Size:	395.8 KB ID:	1451839
    Attached Files

    Leave a comment:


  • trevordj
    replied
    Originally posted by GaryRoach View Post
    OK. I now have pretty solid enclosure design using a Dayton DS215-8 woofer. See the attached screen shots. I have read over the instructions - several times - for using the main screen and am completely confused. How do I get my enclosure attached to my high pass filter to test the complete system. In addition, I have never figured out how to add actual driver data to replace the default Driver #1 in the cross over design window. Could anyone help?

    Click image for larger version

Name:	EnclosureDSA215-6Ported.jpg
Views:	1481
Size:	355.2 KB
ID:	1451823 Click image for larger version

Name:	VituixCAD-DSA215-8Ported.jpg
Views:	1400
Size:	290.3 KB
ID:	1451824

    GaryR
    I can help you with that Gary. Vituixcad has a unique UI, but once you get used to it it is pretty logical to work with.

    To get your simulated enclosure into the crossover editor you need to click on the button all the way at the top that has the arrow with SPL on it. The button next to it will export your simulated impedance file as well.





    Click image for larger version

Name:	Screenshot 2020-09-18 173339.jpg
Views:	448
Size:	398.7 KB
ID:	1451829



    Save it somewhere and save the ZMA file as well (option 1). Alternatively, you can drop your ZMA directly into your crossover sim by choosing the driver in your sim at the bottom of the enclosure simulator.

    Click image for larger version

Name:	Screenshot 2020-09-18 173248.jpg
Views:	431
Size:	486.8 KB
ID:	1451830

    Once you have either simulated or actual FRD or ZMA, adding them to your crossover simulation is easy. You can rename the default "Driver #1" just by clicking on it and typing whatever you want.

    Click image for larger version

Name:	Screenshot 2020-09-18 172327.jpg
Views:	415
Size:	380.8 KB
ID:	1451831

    You can add another driver by clicking on the green plus sign next to the driver


    Click image for larger version

Name:	Screenshot 2020-09-18 172411.jpg
Views:	422
Size:	381.5 KB
ID:	1451832

    Now you can add your frd file you saved in the enclosure simulator. Click on the file button

    Click image for larger version

Name:	Screenshot 2020-09-18 172528.jpg
Views:	414
Size:	384.6 KB
ID:	1451833

    Leave a comment:


  • GaryRoach
    replied
    OK. I now have pretty solid enclosure design using a Dayton DS215-8 woofer. See the attached screen shots. I have read over the instructions - several times - for using the main screen and am completely confused. How do I get my enclosure attached to my high pass filter to test the complete system. In addition, I have never figured out how to add actual driver data to replace the default Driver #1 in the cross over design window. Could anyone help?

    Click image for larger version

Name:	EnclosureDSA215-6Ported.jpg
Views:	1481
Size:	355.2 KB
ID:	1451823 Click image for larger version

Name:	VituixCAD-DSA215-8Ported.jpg
Views:	1400
Size:	290.3 KB
ID:	1451824

    GaryR

    Leave a comment:


  • GaryRoach
    replied
    No. You got it right the first time. I wasn't sure whether the voltage would do what you suggested. Looking at the power level graph is a great idea. Thanks

    GaryR

    Leave a comment:


  • LOUT
    replied
    Originally posted by GaryRoach View Post
    I'm not quite ready to tackle the crossover page but need to be able to test the enclosure design at full power. How do I do that?
    Is this what you're asking about or are you looking for something different?
    Originally posted by LOUT View Post
    In the Enclosure tool, you should have a voltage option near the middle/left called "Source" which will default at 2.83v (about 1watt into 8ohm or 2watts at 4ohms)...you can mouse-wheel up/down or type different numbers to increase or decrease the voltage here....the wattage should show in the graph labelled "Power" while the Vent velocity should show in the graph labelled "Velocity" and the excursion will on the Excursion graph.
    It'll also show the Peak Velocity when you click the "Info" tab next to the "Enclosure" tab....it'll be labelled "VmaxR m/s"....this is super handy since the graph seems to only go to 20m/s by default while I've heard a more realistic PeakVelocity to aim for is around 55m/s (though I could be wrong there).
    Or are you asking how to input measured real-world data from your enclosure into the sim/program? Sorry for my confusion.

    Leave a comment:


  • GaryRoach
    replied
    Thanks,everyone, for your replies. First: If you click the Enable button before you enter data in the filter window, the process doesn't work. That was my error. If done the other way around things work fine. Problem 1 solved.

    Boy tvrgeek wish we could get some of your rain. Souther California is dry as a bone and burning all over the place. The sun is bright orange most days.

    I'm not quite ready to tackle the crossover page but need to be able to test the enclosure design at full power. How do I do that?

    GaryR

    Leave a comment:


  • LOUT
    commented on 's reply
    I think I was using it about 1.5years ago. Do you know if that was more likely the new/current version or the older 0.5version?
    In my case it might've been a problem with Win7 or Win8.1 (not sure which I was using), or maybe something else...I don't want to blame the program too unfairly, more just explaining why I was so happy when I realized it was possible to consolidate over to the other software I was already using without losing major features.

  • tvrgeek
    replied
    I had more trouble with the new version of WinIsd. older version (.5) is solid

    Leave a comment:


  • LOUT
    replied
    Originally posted by tvrgeek View Post
    Which is why WinIsd for box design, Edge for baffle and diffraction, and PSD-lite for crossover have worked well enough for me. I threw away my Sound Easy for this very reason.
    Use OEM plots to pick drivers
    Use WinIsl to design a box. Advice from Edge on baffle design.
    Protorype box and measure far-field. ( I use 1M ) Measure 0, 15, and 30 degrees or whatever is likely to be the in-use angle. ( A DIY can actually measure in-position which an OEM can't ever guess)
    Use these .frs and .imp files into the Psd-lite. as they have true baffle, offset, position, and all reality included.
    Build the suggestion
    Measure reality.
    Tune.
    One of the mistakes I see beginners is to build the final box before they have measured anything in reality. MDF is cheap. PROTOTYPE! I prototype with cheap electrolytics.
    I don't know how to import simulated data from the diffraction+baffle into the cab or FR/XO model (don't know if my older versions of Vituix even CAN), and while you can import XO response into the cab model, I don't know if you can import cab response/impulse into the XO/RF model. So I basically treat VituixCAD like 3 different programs...a CAB sim, a rough diffraction modeller, and an XO/200-500hz+ sim.
    I used to use WinISD for cab modelling, but it was weirdly unstable for me (freezing and crashing despite a couple different installations) and I think Vituix does most/everything WinISD does inside its Eclosure/cab tool now. I haven't heard anyone else mentioned unstability in WinISD so I'm guessing that's just a me thing, but I don't need both programs anymore....I also prefer Vituix's Enclosure tool's multi-graph view compared to my experiences with WinISD needing to manually open multiple windows for important info, sometimes being forced to close one before being allowed to open another graph. Not sure if that was just a quirk of an old version though.
    The baffle-step sim in Vituix is pretty simplistic (in the diffraction tab of the Enclosure tool), but like you mentioned, measuring the true response is always going to be much more accurate...so the baffle/diffraction sim is just a nice rough starting-point.
    The current versions of Vituix switched over to what seems to be the more common drag+drop individual component (build your whole PCB from scratch) thingy, so I no longer needed the separate software for that flexibility anymore (can't remember which one I was using...found it here on the PETT forum I think).
    All of those features weren't much different or more/less complex between Vituix and their separate programs I was previously using, so I don't feel like I'm missing out on anything there. I can't speak to the measurement inputs on Vituix though...that might be super crappy compared to other software for all I know (though I suspect it's pretty much the same).
    Not sure if V has an actual parts/cut-list feature, but I'm used to doing the simple math with a calculator and paper anyway (then finding errors and feeling dumb, lol).
    Basically a Vituix apologist at this point.

    Leave a comment:


  • tvrgeek
    replied
    Originally posted by hongrn View Post
    One of the easiest tools for crossover design has got to be WinPCD, by David Ralph (dlr on TT here). If you like Jeff Bagby's PCD, you'll feel right at home with WinPCD. It does the job admirably, has a simple interface, and an easy learning curve. Why mess with anything complicated?

    https://www.speakerdesign.net/
    Which is why WinIsd for box design, Edge for baffle and diffraction, and PSD-lite for crossover have worked well enough for me. I threw away my Sound Easy for this very reason.
    Use OEM plots to pick drivers
    Use WinIsl to design a box. Advice from Edge on baffle design.
    Protorype box and measure far-field. ( I use 1M ) Measure 0, 15, and 30 degrees or whatever is likely to be the in-use angle. ( A DIY can actually measure in-position which an OEM can't ever guess)
    Use these .frs and .imp files into the Psd-lite. as they have true baffle, offset, position, and all reality included.
    Build the suggestion
    Measure reality.
    Tune.

    One of the mistakes I see beginners is to build the final box before they have measured anything in reality. MDF is cheap. PROTOTYPE! I prototype with cheap electrolytics.

    Leave a comment:


  • tvrgeek
    replied
    Originally posted by LOUT View Post
    I might be missunderstanding, but do you mean between two different sim programs, inputting all the same information into both gives two very different results?
    If so, might it be because one of them is missing something that the other accepts, or maybe some variable was forgotten in one but not the other (or a decimal point or imperial VS metric) or one defaults to a different preset for some things?

    It's just weird to hear of sims getting things different from each other (if I'm not missunderstanding in the first place)...different from real-world because of unknown or missed variables, sure...but not different from eachother when given the same info and left with the same gaps/defaults.
    Correct. I am sure it is due to the learning curve. My old tools are quite intuitive. The more complex are not. I am not even sure of it is actually using the baffle step data that did look good.

    Leave a comment:


  • hongrn
    replied
    One of the easiest tools for crossover design has got to be WinPCD, by David Ralph (dlr on TT here). If you like Jeff Bagby's PCD, you'll feel right at home with WinPCD. It does the job admirably, has a simple interface, and an easy learning curve. Why mess with anything complicated?

    Speakers Loudspeakers WinPCD Windows Passive Crossover Designer WinGraph DIY Do-It-Yourself frd zma

    Leave a comment:


  • LOUT
    replied
    Originally posted by tvrgeek View Post
    Just tried to copy my last project, a center channel into it. It is no where near either reality or my PSD-Lite sim. Might just stick with my old tools as I know them.
    I might be missunderstanding, but do you mean between two different sim programs, inputting all the same information into both gives two very different results?
    If so, might it be because one of them is missing something that the other accepts, or maybe some variable was forgotten in one but not the other (or a decimal point or imperial VS metric) or one defaults to a different preset for some things?

    It's just weird to hear of sims getting things different from each other (if I'm not missunderstanding in the first place)...different from real-world because of unknown or missed variables, sure...but not different from eachother when given the same info and left with the same gaps/defaults.

    Leave a comment:

Working...
X