Feature Request: Raw-Lite for the F5/F55

Hi Sony Staff, Here's a feature request that I've been pondering for a long time now. Raw Lite on the F5(5). Is it a possibility? I'm a huge fan of the conventional 3:1 compressed 4K 16-bit Linear Raw from the AXS-R5. It provides a supremely high quality digital negative, with as much detail and tonality as you could ever really need. However the file sizes are very large. 1TB yeilds roughly an hour of recording time. And the storage costs associated with that are enough to scare away MANY producers from shooting Sony Raw (even with all of the benefits that doing so offers). You guys have addressed this issue nicely with the F65 by offering Raw Lite with it's 6:1 compression (which coincidentally, is a compression rate that many, many producers are content to shoot with on the most prolific raw cameras out their - the Red Epic/Dragon/Scarlet cameras). Being able to offer producers the option to shoot Sony Raw Lite, with it's massively more managable file sizes would greatly increase the uptake of Sony Raw for production - and that benefits everyone. It benefits the camera department with a superior digital negative, it benefits post-production with greater latitude for grading and VFX, it benefits producers with a superior end product, and it benefits audiences with better looking images. Given that the F65 was able to be upgraded to offer this additional raw recording option, I assume (and hope) that it's not an impossiblity for the F5(5). So I'd urge you to strongly consider this feature request, and the added appeal it would bring to the cameras as a capture choice. Cheers, Mark

I disagree that there is little difference between 12bit and 16 bit linear raw. The difference is huge. Shadows and dark areas from the FS7/FS700 are pretty grim, lot's of noise caused by the data rounding. Besides, in terms of bit rate it's not a question of simply reducing the bit depth, you need to increase the compression. For linear raw you need 16 bits unless you do an extreme amount of data rounding. For Linear raw, if the first stop is represented by just 2 bits of data (which results in very blocky noise as noise will be one of 4 luma levels and cannot be smoothly reproduced): stop 1: 2 bitsstop 2: 4stop 3: 8stop 4: 16stop 5: 32stop 6: 64stop 7 128 (8 bit linear limit, 128 + 128 = 256 bits)stop 8: 256stop 9: 512 (10 bit linear limit)stop 10: 1024stop 11: 2048 (12 bit linear limit)stop 12: 4096stop 13: 8192 stop 14: 16384 bitsstop 15: 32768 bits (16 bit linear limit) If you move this scale up so that the first stop is represented by using 4 bits of data you will still have pretty coarse shadows and noise (one whole f stop will only have 16 posible luma values). So rather than just use binary math most linear raw systems use floating point math to make more bits available for the shadows. But with 12bit there just isn't anywhere near the same amount of "spare" bits that you get with 16 bit, so the shadows and low key areas really suffer. Just go and look at the FS7/FS700 boards and all the compliants about unusable, grainy and blocky shadow areas in the raw. Sure raw lite would be a welcome option, but it wouldn't be one for me. The whole point of raw for me is a robust, bomb proof format that you can expose and grade as you wish without worrying about artefacts etc.

Similar Messages

So... how long do we have to wait for a RAW update for the Nikon D600 camera?

So... how long do we have to wait for a RAW update for the Nikon D600 camera?

Adobe releases Camera Raw every 3 or 4 months. The D600 itself was launched only about 1 week ago. I'm sure its not included in ACR 7.2 RC yet. Nikon J1 is included though. I guess you're gona have to wait for it. Maybe 7.2 final release will have it or 7.3 should. Adobe employees/ product team will not commit to a time for Camera Raw releases.
However, you can use the software Nikon would've given you to convert your images as TIFF and import them into Lightroom/ Photoshop if you're in a hurry. It would be nice if your camera supports DNG conversion out of the box! This way, you wont need a Camera Raw from Adobe.
Anyway, you could file a 'Feature Request' to Adobe here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Good luck.

Feature Request - Please allow for a "classic" view option.

Please allow for a "classic" view option like you have in Mail. Miss the sidebar that had a list of all the calendars using. The pop up list is not nearly as functional. iCal in Lion may be great for touch screen users but is a step back on the intuitive scale for Mac users.
Also, the delete / revert button are too close to the done button. Too easy to hit on accident.

This is a good feature request and should be submitted here: Adobe - Feature Request/Bug Report Form
The team reviews all the requests that come in through that form. It is a guaranteed way to get your request seen while we do not always see everything that gets posted to the forums.

HT4757 RAW support for the SONY RX100?

Anyone know when will Apple be adding RAW support for the SONY RX100?

Unfortunately this is a user forum, so no-one can answer that one for you. You can use the feedback option in aperture to request it though. More than likely it wont come until Canon or Nikon release some more DSLRs, which is usually what prompts an update. For what it's worth you can use the Adobe DNG converter which will convert the sony .arw file into a .dng file that Aperture can read. It is another step to your workflow but you can do it.

Selective XML Index feature is not supported for the current database version , SQL Server Extended Events , Optimizing Reading from XML column datatype

Team , Thanks for looking into this ..
As a last resort on optimizing my stored procedure ( Below ) i wanted to create a Selective XML index ( Normal XML indexes doesn't seem to be improving performance as needed ) but i keep getting this error within my stored proc . Selective XML
Index feature is not supported for the current database version.. How ever
EXECUTE sys.sp_db_selective_xml_index; return 1 , stating Selective XML Indexes are enabled on my current database .
Is there ANY alternative way i can optimize below stored proc ?
Thanks in advance for your response(s) !
/****** Object: StoredProcedure [dbo].[MN_Process_DDLSchema_Changes] Script Date: 3/11/2015 3:10:42 PM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- EXEC [dbo].[MN_Process_DDLSchema_Changes]
ALTER PROCEDURE [dbo].[MN_Process_DDLSchema_Changes]
AS
BEGIN
SET NOCOUNT ON --Does'nt have impact ( May be this wont on SQL Server Extended events session's being created on Server(s) , DB's )
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
select getdate() as getdate_0
DECLARE @XML XML , @Prev_Insertion_time DATETIME
-- Staging Previous Load time for filtering purpose ( Performance optimize while on insert )
SET @Prev_Insertion_time = (SELECT MAX(EE_Time_Stamp) FROM dbo.MN_DDLSchema_Changes_log ) -- Perf Optimize
-- PRINT '1'
CREATE TABLE #Temp
EventName VARCHAR(100),
Time_Stamp_EE DATETIME,
ObjectName VARCHAR(100),
ObjectType VARCHAR(100),
DbName VARCHAR(100),
ddl_Phase VARCHAR(50),
ClientAppName VARCHAR(2000),
ClientHostName VARCHAR(100),
server_instance_name VARCHAR(100),
ServerPrincipalName VARCHAR(100),
nt_username varchar(100),
SqlText NVARCHAR(MAX)
CREATE TABLE #XML_Hold
ID INT NOT NULL IDENTITY(1,1) PRIMARY KEY , -- PK necessity for Indexing on XML Col
BufferXml XML
select getdate() as getdate_01
INSERT INTO #XML_Hold (BufferXml)
SELECT
CAST(target_data AS XML) AS BufferXml -- Buffer Storage from SQL Extended Event(s) , Looks like there is a limitation with xml size ?? Need to re-search .
FROM sys.dm_xe_session_targets xet
INNER JOIN sys.dm_xe_sessions xes
ON xes.address = xet.event_session_address
WHERE xes.name = 'Capture DDL Schema Changes' --Ryelugu : 03/05/2015 Session being created withing SQL Server Extended Events
--RETURN
--SELECT * FROM #XML_Hold
select getdate() as getdate_1
-- 03/10/2015 RYelugu : Error while creating XML Index : Selective XML Index feature is not supported for the current database version
CREATE SELECTIVE XML INDEX SXI_TimeStamp ON #XML_Hold(BufferXml)
FOR
PathTimeStamp ='/RingBufferTarget/event/timestamp' AS XQUERY 'node()'
--RETURN
--CREATE PRIMARY XML INDEX [IX_XML_Hold] ON #XML_Hold(BufferXml) -- Ryelugu 03/09/2015 - Primary Index
--SELECT GETDATE() AS GETDATE_2
-- RYelugu 03/10/2015 -Creating secondary XML index doesnt make significant improvement at Query Optimizer , Instead creation takes more time , Only primary should be good here
--CREATE XML INDEX [IX_XML_Hold_values] ON #XML_Hold(BufferXml) -- Ryelugu 03/09/2015 - Primary Index , --There should exists a Primary for a secondary creation
--USING XML INDEX [IX_XML_Hold]
---- FOR VALUE
-- --FOR PROPERTY
-- FOR PATH
--SELECT GETDATE() AS GETDATE_3
--PRINT '2'
-- RETURN
SELECT GETDATE() GETDATE_3
INSERT INTO #Temp
EventName ,
Time_Stamp_EE ,
ObjectName ,
ObjectType,
DbName ,
ddl_Phase ,
ClientAppName ,
ClientHostName,
server_instance_name,
nt_username,
ServerPrincipalName ,
SqlText
SELECT
p.q.value('@name[1]','varchar(100)') AS eventname,
p.q.value('@timestamp[1]','datetime') AS timestampvalue,
p.q.value('(./data[@name="object_name"]/value)[1]','varchar(100)') AS objectname,
p.q.value('(./data[@name="object_type"]/text)[1]','varchar(100)') AS ObjectType,
p.q.value('(./action[@name="database_name"]/value)[1]','varchar(100)') AS databasename,
p.q.value('(./data[@name="ddl_phase"]/text)[1]','varchar(100)') AS ddl_phase,
p.q.value('(./action[@name="client_app_name"]/value)[1]','varchar(100)') AS clientappname,
p.q.value('(./action[@name="client_hostname"]/value)[1]','varchar(100)') AS clienthostname,
p.q.value('(./action[@name="server_instance_name"]/value)[1]','varchar(100)') AS server_instance_name,
p.q.value('(./action[@name="nt_username"]/value)[1]','varchar(100)') AS nt_username,
p.q.value('(./action[@name="server_principal_name"]/value)[1]','varchar(100)') AS serverprincipalname,
p.q.value('(./action[@name="sql_text"]/value)[1]','Nvarchar(max)') AS sqltext
FROM #XML_Hold
CROSS APPLY BufferXml.nodes('/RingBufferTarget/event')p(q)
WHERE -- Ryelugu 03/05/2015 - Perf Optimize - Filtering the Buffered XML so as not to lookup at previoulsy loaded records into stage table
p.q.value('@timestamp[1]','datetime') >= ISNULL(@Prev_Insertion_time ,p.q.value('@timestamp[1]','datetime'))
AND p.q.value('(./data[@name="ddl_phase"]/text)[1]','varchar(100)') ='Commit' --Ryelugu 03/06/2015 - Every Event records a begin version and a commit version into Buffer ( XML ) we need the committed version
AND p.q.value('(./data[@name="object_type"]/text)[1]','varchar(100)') <> 'STATISTICS' --Ryelugu 03/06/2015 - May be SQL Server Internally Creates Statistics for #Temp tables , we do not want Creation of STATISTICS Statement to be logged
AND p.q.value('(./data[@name="object_name"]/value)[1]','varchar(100)') NOT LIKE '%#%' -- Any stored proc which creates a temp table within it Extended Event does capture this creation statement SQL as well , we dont need it though
AND p.q.value('(./action[@name="client_app_name"]/value)[1]','varchar(100)') <> 'Replication Monitor' --Ryelugu : 03/09/2015 We do not want any records being caprutred by Replication Monitor ??
SELECT GETDATE() GETDATE_4
-- SELECT * FROM #TEMP
-- SELECT COUNT(*) FROM #TEMP
-- SELECT GETDATE()
-- RETURN
-- PRINT '3'
--RETURN
INSERT INTO [dbo].[MN_DDLSchema_Changes_log]
[UserName]
,[DbName]
,[ObjectName]
,[client_app_name]
,[ClientHostName]
,[ServerName]
,[SQL_TEXT]
,[EE_Time_Stamp]
,[Event_Name]
SELECT
CASE WHEN T.nt_username IS NULL OR LEN(T.nt_username) = 0 THEN t.ServerPrincipalName
ELSE T.nt_username
END
,T.DbName
,T.objectname
,T.clientappname
,t.ClientHostName
,T.server_instance_name
,T.sqltext
,T.Time_Stamp_EE
,T.eventname
FROM
#TEMP T
/** -- RYelugu 03/06/2015 - Filters are now being applied directly while retrieving records from BUFFER or on XML
-- Ryelugu 03/15/2015 - More filters are likely to be added on further testing
WHERE ddl_Phase ='Commit'
AND ObjectType <> 'STATISTICS' --Ryelugu 03/06/2015 - May be SQL Server Internally Creates Statistics for #Temp tables , we do not want Creation of STATISTICS Statement to be logged
AND ObjectName NOT LIKE '%#%' -- Any stored proc which creates a temp table within it Extended Event does capture this creation statement SQL as well , we dont need it though
AND T.Time_Stamp_EE >= @Prev_Insertion_time --Ryelugu 03/05/2015 - Performance Optimize
AND NOT EXISTS ( SELECT 1 FROM [dbo].[MN_DDLSchema_Changes_log] MN
WHERE MN.[ServerName] = T.server_instance_name -- Ryelugu Server Name needes to be added on to to xml ( Events in session )
AND MN.[DbName] = T.DbName
AND MN.[Event_Name] = T.EventName
AND MN.[ObjectName]= T.ObjectName
AND MN.[EE_Time_Stamp] = T.Time_Stamp_EE
AND MN.[SQL_TEXT] =T.SqlText -- Ryelugu 03/05/2015 This is a comparision Metric as well , But needs to decide on
-- Peformance Factor here , Will take advise from Lance if comparision on varchar(max) is a vital idea
--SELECT GETDATE()
--PRINT '4'
--RETURN
SELECT
top 100
[EE_Time_Stamp]
,[ServerName]
,[DbName]
,[Event_Name]
,[ObjectName]
,[UserName]
,[SQL_TEXT]
,[client_app_name]
,[Created_Date]
,[ClientHostName]
FROM
[dbo].[MN_DDLSchema_Changes_log]
ORDER BY [EE_Time_Stamp] desc
-- select getdate()
-- ** DELETE EVENTS after logging into Physical table
-- NEED TO Identify if this @XML can be updated into physical system table such that previously loaded events are left untoched
-- SET @XML.modify('delete /event/class/.[@timestamp="2015-03-06T13:01:19.020Z"]')
-- SELECT @XML
SELECT GETDATE() GETDATE_5
END
GO
Rajkumar Yelugu

@@Version : ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
   May 14 2014 18:34:29
   Copyright (c) Microsoft Corporation
   Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
(1 row(s) affected)
Compatibility level is set to 110 .
One of the limitation states - XML columns with a depth of more than 128 nested nodes
How do i verify this ? Thanks .
Rajkumar Yelugu

Camera RAW does NOT yet support raw files for the new Canon Sureshot S95

Camera RAW does NOT yet support raw files for the new
Canon Sureshot S95.
Adobe, please can you provide an update asap

Hello!
I think that you need to be patient.
There has not been any release of Camera Raw since the release of the camera.
I recommend to try the next version once it will be released, as there might be preliminary support (and therefore not listed).
Usually, Adobe is amongs the firsts to support a new camera.
Even though the Camera Raw team is fielded with wonderful coders, I do not think that they do have a time machine to allow support before they have their hands on a camera

When it will be the camera raw update for the nikon d750 in Lightroom 4?

When it will be the camera raw update for the nikon d750 in Lightroom 4?

Never. You'll need to upgrade to Lr 5.7, or convert your D750 files to DNG for Lr 4 to use.
As a site search would amply have indicated.
https://forums.adobe.com/search.jspa?q=d750&place=%2Fplaces%2F1383621&depth=ALL

HT4757 Does anyone know when we will get RAW compatablility for the great Fujiflim X10 camera? Please.

Does anyone know when we will get RAW compatibility for the great little Fujifilm X10?
Thank you.

No one outside of Apple knows when - or if - support will be added for any device. Just let them know you want it...
iPhoto menu -> Provide iPhoto Feedback

[Consolidation-Locked] Please add RAW support for the Nikon D600 to Lightroom as soon as possible!

My Fair Adobe,
Please add RAW support for the Nikon D600 to Lightroom as soon as possible!
ViewNX lets me get to the images, but come on!!! I know Lightroom, and you, ViewNX, are no Lightroom.
Yes, I see everyone else ASKING for D600 support. I'm here to beg for it! Don't make me wait much longer!
Message title was edited by: Brett N
Message title was edited by: Brett N

Rob, my reading of your site is that this plug-in copies settings from raw to jpeg, does it work the other way around as well?
Rob Cole wrote:
One of the great things about the new 0-based defaults and linear tone curve is:
You can develop the jpegs now, in Lightroom, and then sync the settings to the raws later (e.g. using RawPlusJpeg), and provided you select a matching camera profile, they will look almost the same (white balance won't translate over, but everything else will, more or less). Beware lens corrections applied to the raws might alter the registration of precision local adjustments.
Note: I recommend shooting with ADL off in order for this to work better, and consider turning sharpening off in camera as well, and noise reduction and everything else to whatever extent is possible.
Rob

When will Aperture 3 support RAW processing for the Canon 5D III?

When will Aperture 3 support RAW processing for the new Canon 5D III?

We are no phophets and also do not work for Apple - so we don't know.
See this thread to join into a discussion with others who also are waiting:
Canon 5D Mk III - RAW update?
Regards
Léonie

Lightroom 3 does NOT support raw files for the Canon Sureshot S95

Have just bought the new Canon Sureshot S95
after contacting Adobe support I am told Lightroom 3 does NOT support raw files for the
Canon Sureshot S95.
Come on Adobe.....please provide an update asap.

(1) Well Boss I did what you said and used Canon DPP to convert to TIFFs. Choices are 8-bit TIFF or 16-bit TIFF - I chose 16-bit because part (90% part) of the reason for wanting to work in RAW is to keep the bit depth of teh original. On my EOS 40D it is supposedly 14 bits, which gives great scope to play with the levels & curves without seeing poster effects. If I choose 16 bit TIFF then each S95 image becomes a 70MB file, parallel to my JPEG and RAW. Hardly a satisfactory solution.
(I realise, however, that I don't actually know the bit depth of the S95 RAW file - anybody? ).
(2) SUGGESTION- even if you are adding S95 support to the next update (which I dearly hope), be kinder to those with new cameras in general and allow LR to import JPEGs if it cannot import the RAWs (overriding if necessary the 'ignore JPEG' preference setting). I am sure users with that preference would still prefer a JPEG than no picture at all!
Since I discovered this compatibility problem, I switched the camera to record RAW+JPEG*. To my great irritation LR3 ignores the JPEGs even though it cannot load the RAWs. So if I want to import from one supported camera (EOS40D) and one unsupported camera (S95) I have to keep going into preferences to switch on and off the 'ignore JPEG' function.
JJ
* (this seems to be a setting that needs doing in the various different modes of the camera, by the way).

Would like to purchase PSE 12 to process Camera Raw files for the following cameras: Nikon D800, Nikon DF, Canon G9 and Pentax K-3 does the Raw Converter that comes with PSE 12 when purchased recognize the cameras listed in the question or do I need to

Would like to purchase PSE 12 to process Camera Raw files for the following cameras: Nikon D800, Nikon DF, Canon G9 and Pentax K-3 does the Raw Converter that comes with PSE 12 when purchased recognize the cameras listed in the question or do I need to download the camera Raw Version 8.3 ?

While the G9 RAW files can be read by Adobe Camera RAW and Lightroom, these file are unsupported at this time. Here is a link to Adobe's latest list of cameras that are supported and this list came out yesterday http://www.adobe.com/products/photoshop/cameraraw.html
I have not done a comparison between Lightroom and Canon's software but others have and say that Canon's software is clearly better. I am sure when Adobe updates their software again to include the G9 it will be a very good RAW converter as it is will most other cameras.

Is there a CS5 camera raw update for the Nikon D600?

is there a CS5 camera raw update for the Nikon D600

Not as yet. ACR 7.2 does have preliminary support for D600. Output may change in final release of D600 support in upcoming ACR 7.3.
http://blogs.adobe.com/lightroomjournal/2012/10/camera-raw-7-2now-available.html
ACR 7.3 will have complete support for D600.
But, if you're on CS5, I'm sorry to break it you cannot upgrade to ACR 7.x...
You may want to consider upgrading to CS6 or Lightroom 4 (cheaper alternative) to get ACR 7.x support.
Or, use the DNG converter, make TIFFs and open them with PS.

Does Aperture support NEF RAW files for the Nikon D810?

I am unable to open NEF RAW files for my new Nikon D810. Are there any updates of suggestions.

Apple has not yet reverse-engineered a RAW update for the d810. I would suggest that you shoot RAW +JPEG with all your NEF images on the CF card and put your JPEG optimal fine images on the SD card in slot 2. Save your NEF images and CF cards until the Aperture 3.5.1 RAW update for the d810 finally is available. In the meantime, you will have JPEG optimal images on your SD cards that you can import and process in Aperture. Good Luck.

Finance for Wire , Check request ,Fixed Assets for the Capital Expenditure

Hi,
We are trying integrate the Finance for Wire , Check request ,Fixed Assets for the Capital Expenditure with adobe forms.
Where would i find more information regarding the same?
what tables are used and what are related t-codes which can give more information?
any documentation is appreciated.
rgds
vara

Hi,
We are trying integrate the Finance for Wire , Check request ,Fixed Assets for the Capital Expenditure with adobe forms.
Where would i find more information regarding the same?
what tables are used and what are related t-codes which can give more information?
any documentation is appreciated.
rgds
vara

Feature Request: Raw-Lite for the F5/F55

Similar Messages

Maybe you are looking for