- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Intel IPP,
I had been thinking of extending some of my funtions of 3D, and was intending to use ippr functions (then we were using IPP 6.0). Now that I really have to get a 3D version, I read somewhere that the entire ippr suite is being deprecated? Is this true? Will 7.1 have no way of performing 3D warp affine and remap? There are the basic 2 that would have formed the bulk of my implementation.
Thanks,
Sid.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sid,
The 3D warp affine and remap functions were deprecated in version 7.1. You can still use them, but they will be going away in a future release. And yes, looking at the ippr header it looks as though the suite is being deprecated.
- Chuck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, thats sad... what is the alternative, then, for applications that have relied on the ippr suite with 6.0??Would like it if this is
also replied by someone from Intel.
Sid.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI, thanks for the reply. In case I go ahead and use static library as you suggested, can the rest of the code continue to use the latest IPP version, with just one component relying on 7.0 ?
Also, are IPP developers thinking of a new 3D libraries in the meantime, or 3D is completely deprecated? Or this there a way to perform 3D with available functionality, and ippr was appearing redundant? The reason mentioned for deprecating ippr was "low frequency of usage". How does intel know this or measure this? Also, in the applications that I have seen/used/coded, the most critical component of the code is definitely not the most frequent, and if speed is the design objective, it is the critical component that is IPP-ized.Hence I do not think that deprecation based on frequency is the right idea.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Sergey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ippR will be still available (with deprecated message) in the next major release - 8.0. In the future, if it is removed, it still will be compatible with the future IPP releases - I mean that for example IPP version N+1 will not contain ippRR domain, but this domain from IPP version N will be compatible with N+1 (with N+1 version of core library and dispatching mechanism)
regards, Igor
![](/skins/images/872293744008A34B36F8ABF94A46CC66/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page