Re: Windows 8 Iso Highly Compressed
Nuri Baggett
Power BI semantic models can store data in a highly compressed in-memory cache for optimized query performance, enabling fast user interactivity. With Premium capacities, large semantic models beyond the default limit can be enabled with the Large semantic model storage format setting. When enabled, semantic model size is limited by the Premium capacity size or the maximum size set by the administrator.
Large semantic models can be enabled for all Premium P SKUs, Embedded A SKUs, and with Premium Per User (PPU). The large semantic model size limit in Premium is comparable to Azure Analysis Services, in terms of data model size limitations.
While required for semantic models to grow beyond 10 GB, enabling the Large semantic model storage format setting has other benefits. If you're planning to use XMLA endpoint-based tools for semantic model write operations, be sure to enable the setting, even for semantic models that you wouldn't necessarily characterize as a large semantic model. When enabled, the large semantic model storage format can improve XMLA write operations performance.
Large semantic models in the service don't affect the Power BI Desktop model upload size, which is still limited to 10 GB. Instead, semantic models can grow beyond that limit in the service on refresh.
Power BI Premium does support large semantic models. Enable the Large semantic model storage format option to use semantic models in Power BI Premium that are larger than the default limit.
Large semantic models in Power BI Premium are not available in the Power BI service for U.S. Government DoD customers. For more information about which features are available, and which are not, see Power BI feature availability for U.S. Government customers.
Invoke a refresh to load historical data based on the incremental refresh policy. The first refresh could take a while to load the history. Subsequent refreshes should be faster, depending on your incremental refresh policy.
In supported regions, all new semantic models created in a workspace assigned to a Premium capacity can have the large semantic model storage format enabled by default. If the region doesn't support large semantic models, the large semantic model storage format option described below is disabled. You can see which regions are supported in the region availability section.
Semantic model eviction is a Premium feature that allows the sum of semantic model sizes to be significantly greater than the memory available for the purchased SKU size of the capacity. A single semantic model is still constrained to the memory limits of the SKU. Power BI uses dynamic memory management to evict inactive semantic models from memory. Semantic models are evicted so that Power BI can load other semantic models to address user queries.
On-demand load is enabled by default for large semantic models, and can provide significantly improved load time of evicted semantic models. With on-demand load, you get the following benefits during subsequent queries and refreshes:
On-demand loading surfaces additional Dynamic Management View (DMV) information that can be used to identify usage patterns and understand the state of your models. For example, you can check the Temperature and Last Accessed statistics for each column in the semantic model, by running the following DMV query from SQL Server Management Studio (SSMS):
For semantic models using the large semantic model storage format, Power BI automatically sets the default segment size to 8 million rows to strike a good balance between memory requirements and query performance for large tables. This is the same segment size as in Azure Analysis Services. Keeping the segment sizes aligned helps ensure comparable performance characteristics when migrating a large data model from Azure Analysis Services to Power BI.
Supported regions: Large semantic models are available in Azure regions that support Azure Premium Files Storage. Review the table in region availability to see a list of all the supported regions.
Refreshing large semantic models: Semantic models that are close to half the size of the capacity size (for example, a 12-GB semantic model on a 25-GB capacity size) may exceed the available memory during refreshes. Using the enhanced refresh REST API or the XMLA endpoint, you can perform fine grained data refreshes, so that the memory needed by the refresh can be minimized to fit within your capacity's size.
Pro isn't supported - Large semantic models aren't supported in Pro workspaces. If a workspace is migrated from Premium to Pro, any semantic models with the large semantic model storage format setting, will fail to load.
BM punted and sent it back to me (and Adobe). They said it is up to Premiere for how it wants to encode it once it enters the Premiere Capture function. Sorry if I'm not asking this right. I'm very new here and get lost easily (as you know from other ventures getting lost).
Although I will say, they can be a bit ... snooty ... in discussing Adobe stuff especially, and not always helpful for PC users in general. A couple years ago I was at their booth at NAB/Vegas. I was looking at the hardware to use a second screen as a full play-back monitor for Resolve, and asked if it would work running a second monitor through it for SpeedGrade also. (This is before the de-linking of PrPro/Sg.)
The counter person didn't know quite what program I was referring to ... so I requested his supervisor, actually wanting an answer. The super said he had no clue, as ... realistically, he'd never heard of the program. Clearly, he wasn't even expecting me to believe him, but just stood looking at me.
Adobe's booth was just kitty-corner across a big aisle intersection and ... it just so happened, that the Adobe "theatre" which faced diagonally right towards the BM booth was featuring a speaker on the wonders of the latest SpeedGrade to be rolled at the following June.
As they of course try and push Resolve, which needs a ton of spendy internal & external boxes to run, I don't think he felt it in his company's direct financial interest to mention a "competing" Adobe product. And as the counter person went to handle someone else, I just walked off myself.
I did go back this year to try and establish which bit of theirs I would need to run a playback monitor-out for Resolve from my PC. I spent over 45 minutes, was taken all over the booth by one employee after another, to another section which should know which bits worked with a PC to serve as a video-out for Resolve. Went though darn near every counter there, I was actually finding that experience rather amusing.
The intent is that you want a really high-quality file capture on the PC, which can then be edited and then exported to a delivery format of choice. These cards are not meant to capture direct for distribution.
I notice you did not say you wanted to edit the clips on the MacBook, but rather just to "show them". In that case, use Media Encoder and export to H.264 which will be universally viewable on PC, Mac, tablet, online.
EDIT: I should clarify, I'm talking about using the Black Magic Media Express capture utility. The BMD cards can actually act as input source for a variety of software apps, so it is possible that one could capture to other formats than those offered in Media Express. I was just using an Intensity Pro capture card the other night with a demo version of the vMix software and I believe there was an option to record to H.264 so something like that might be a workaround to capture to alternate formats.
I'm hoping to save a step in my workflow. That is, not have to reencode my base videos. I typically do my editing long after I record and it would be nice if I did not have a manual step after I record.
Actually, that I have a lot of experience with. Thousands of clips. It's a very tedious workflow. thats why I'm going down the hdmi capture path. i am confident there is an optimum solution in that space much better than "record to the card".
I have my camera (lumix g4) on a tripid that has a telepompter gizmo bolted to it (camera shoots through glass at 45 degrees, IPad sit's horizontally and shines on screen so I can read it while camera looks at me).
In a recording session (usually about 4 hours), I produce about 10 or so 2 minute clips (attaching a link to one below where I'm actually holding my iphone at belt level and recording myself being recorded).
Since I'm a horrible actor/script reader, I always do each clip over and over until I get it right. that means, record a clip, transfer it to PC, view it, repeat until acceptable. This is the hard part. The SD is hard to get out when on the tripod with telepompter. I always end up bumping the hec out of it, then have to readjust everything. So, I skip that and transfer by USB to my computer (slowwww). It also means I need to change camera mode from wifi (which I need for focusing on myself using the camera app) to file transfer mode. Then back again to wifi mode. Painful to do every time. I often do 4 or 5 clips and batch them but still a pain.
With the hdmi output, all those steps go away. I leave the camera on, I leave my iphone app running and I simply press start and stop on my bluetooth keyboard on my computer to start and stop recording. It's literally instant and I never have to touch my camera. (that's the plan anyhow).
This thread has been a big help. I think my best plan is to start my 4 hour recording session with the encoding set to one of the non-compressed settings. It will likely create 100's of gigs of data but that's OK. I'll put together what I need at the end of the four hours, encode it to h.264 and store that. Then throwaway the uncompressed stuff.
Thanks for sharing your workflow - what you are doing makes perfect sense, and I understand the desire for smaller files. Consider this though - the native recording in the camera is probably something like 25mbps with 4:2:0 color, inter-frame recording. Very highly compressed. From that compressed file, you then need to make highly-compressed deliverables.
d3342ee215