![]() ![]() ![]() What I'd like to say is that DSD processing appears to not be that simple (any other experiences, anyone?) and thus an editing software in my guess could be "challenging". Then I've tried HQPlayer's DSD processing which even at low DSD resolutions (DSD64 & DSD128) to my ears has some qualities - however, my computer is far from fast enough to work with the processing required. I recently tried foobar's DSD solution and unless I made some kind of mistake it's quite noisy (like an FM carrier wave surrounding the sound). something like the Vinylstudio software is capable of a qualitatively superb processing of the DSD data. The issue - again from my perspective - is e.g. If the clock for all the USBPAL inputs is the same the sequence of data should be "aligned" and probably relatively easy to recombine. Multiplexing the signal prior to the USBPAL I don't find to be an issue, and I suppose a programmer could help de-multiplexing and combining the incoming DSD files inside the computer. So I can't test it, and the files I've generated with VS are rather useless for my purposes. From my perspective the main challenges are to get the data into the PC and have it stored & processed there. According to the VinylStudio website there is a way to increase the volume (in a 'batch' window for some reason) but that's all greyed out in the trial version. Third, and I may more or less have said that by now - the USBPAL works with up to 384/32 bit ADCs/DACs that are capable of communicating via I2S (I think another standard is also available, to expand. This, and the editing software, is what I'm looking for preferably up to DSD512 (or higher). Thus, DSD may be selected in USBPAL's setup but it requires an additional ASIO to actually make it work. ![]() Second, I spoke with Marcel Dasen (CEO, Rigisystems) some time ago about recording DSD via the USBPAL and it's capable of doing so up to DSD256 except that it takes an ASIO driver/software part (don't know what the technically correct term may be for an ASIO software part) to make it work. Sort of like the combo384 but with both ways communication. įirst, the USBPAL in an in/out I2S-to-USB interface card between any ADC/DAC and recording software in the computer. I would assume there are folks still having this issue.As it is I happen to also have a USBPAL and may be able to shed some light on its potential use for DSD recording. I've read through the above comments pretty thoroughly but let me know if there's something I'm missing. The level in question is not linked from a consultant model, it's on an active workset that's not hidden, I've associated the floor geometries to the new level and created a new room associated with the new level, checked that the new room is included in the daylight analysis in the schedule, I've closed Revit, made a new local file, moved the levels to and from a scope box - all to no avail. I've tried everything - just today am working in a model that will not refresh any new levels I've added. I'm still struggling with this issue - after probably 2+ years. Since we don't read Rooms and Floors in the linked model, it's safe to add copies of them to the main host model.įormer coworker of JDunn actually. We would have to create a new, standalone UI and data management system to do that independently of the Revit parameters. In future releases, we will be able to generate analysis points from Floors on shared Levels, but it's more difficult to use Rooms in shared models, as we use Room parameters to report results in the Room schedule, and we can't modify the parameters of Rooms in the linked model, which is how we store data with the model as well. So when running Lighting, be sure that the Floors, Levels and Rooms are in the main host model.Ĭheck the Lighting Analysis Model view for all geometry that will affect light in the model. However, all of the geometry in linked models is used to create the geometry for the analysis engine, so if you look at the Lighting Analysis Model View, this is what will be exported to analyze light for the analysis points that we do generate from Floors and Rooms and Levels in the main host model. Although we can access information about Floors and Rooms in a linked model, we can't generate schedules for Lighting results, so we don't use them to generate analysis surfaces or results. Lighting needs to access Floors and Rooms and Levels and to save data about them with the model. ![]()
0 Comments
Leave a Reply. |