我正在开发 iOS 应用程序,我想在其中录制分段视频。我读过https://developer.apple.com/library/content/documentation/AudioVideo/Conceptual/AVFoundationPG/Articles/00_Introduction.html我有一个使用 AVCaptureVideoDataOutput 的工作解决方案,我在其中捕获帧并使用 AVAssetWriter 将它们写入文件。我将 AVCaptureVideoDataOutput 添加到 AVCaptureSession,如下所示:
// Setup videoDataOutput in order to capture samplebuffers
let videoDataOutput = AVCaptureVideoDataOutput()
videoDataOutput.videoSettings = [kCVPixelBufferPixelFormatTypeKey as AnyHashable : Int(kCVPixelFormatType_32BGRA)]
videoDataOutput.alwaysDiscardsLateVideoFrames = true
videoDataOutput.setSampleBufferDelegate(self, queue: CaptureManager.CAPTURE_QUEUE)
guard captureSession.canAddOutput(videoDataOutput) else {
return
}
captureSession.addOutput(videoDataOutput)
self.videoDataOutput = videoDataOutput
效果很好,我可以成功运行捕获 session 并获得可播放的电影文件。
现在我想插入音频。所以我想像这样做同样的事情:
// Setup audioDataOutput in order to capture audio
let audioDataOutput = AVCaptureAudioDataOutput()
audioDataOutput.audioSettings = ...
audioDataOutput.setSampleBufferDelegate(self, queue: CaptureManager.CAPTURE_QUEUE)
guard captureSession.canAddOutput(audioDataOutput) else {
return
}
captureSession.addOutput(audioDataOutput)
self.audioDataOutput = audioDataOutput
疯狂的是 AVCaptureAudioDataOutput 上没有属性 audioSettings!!!文档是这样说的:https://developer.apple.com/reference/avfoundation/avcaptureaudiodataoutput/1388527-audiosettings但是 Swift header 没有这样的成员(如下)。
这到底是怎么回事?我正在使用 XCode 8.1。以下类 AVCaptureAudioDataOutput 的 Swift header :
import AVFoundation
import CoreMedia
import Foundation
/*!
@class AVCaptureAudioDataOutput
@abstract
AVCaptureAudioDataOutput is a concrete subclass of AVCaptureOutput that can be used to process uncompressed or compressed samples from the audio being captured.
@discussion
Instances of AVCaptureAudioDataOutput produce audio sample buffers suitable for processing using other media APIs. Applications can access the sample buffers with the captureOutput:didOutputSampleBuffer:fromConnection: delegate method.
*/
@available(iOS 4.0, *)
open class AVCaptureAudioDataOutput : AVCaptureOutput {
/*!
@method setSampleBufferDelegate:queue:
@abstract
Sets the receiver's delegate that will accept captured buffers and dispatch queue on which the delegate will be called.
@param sampleBufferDelegate
An object conforming to the AVCaptureAudioDataOutputSampleBufferDelegate protocol that will receive sample buffers after they are captured.
@param sampleBufferCallbackQueue
A dispatch queue on which all sample buffer delegate methods will be called.
@discussion
When a new audio sample buffer is captured it will be vended to the sample buffer delegate using the captureOutput:didOutputSampleBuffer:fromConnection: delegate method. All delegate methods will be called on the specified dispatch queue. If the queue is blocked when new samples are captured, those samples will be automatically dropped when they become sufficiently late. This allows clients to process existing samples on the same queue without having to manage the potential memory usage increases that would otherwise occur when that processing is unable to keep up with the rate of incoming samples.
Clients that need to minimize the chances of samples being dropped should specify a queue on which a sufficiently small amount of processing is being done outside of receiving sample buffers. However, if such clients migrate extra processing to another queue, they are responsible for ensuring that memory usage does not grow without bound from samples that have not been processed.
A serial dispatch queue must be used to guarantee that audio samples will be delivered in order. The sampleBufferCallbackQueue parameter may not be NULL, except when setting sampleBufferDelegate to nil.
*/
open func setSampleBufferDelegate(_ sampleBufferDelegate: AVCaptureAudioDataOutputSampleBufferDelegate!, queue sampleBufferCallbackQueue: DispatchQueue!)
/*!
@property sampleBufferDelegate
@abstract
The receiver's delegate.
@discussion
The value of this property is an object conforming to the AVCaptureAudioDataOutputSampleBufferDelegate protocol that will receive sample buffers after they are captured. The delegate is set using the setSampleBufferDelegate:queue: method.
*/
open var sampleBufferDelegate: AVCaptureAudioDataOutputSampleBufferDelegate! { get }
/*!
@property sampleBufferCallbackQueue
@abstract
The dispatch queue on which all sample buffer delegate methods will be called.
@discussion
The value of this property is a dispatch_queue_t. The queue is set using the setSampleBufferDelegate:queue: method.
*/
open var sampleBufferCallbackQueue: DispatchQueue! { get }
/*!
@property audioSettings
@abstract
Specifies the settings used to decode or re-encode audio before it is output by the receiver.
@discussion
The value of this property is an NSDictionary containing values for audio settings keys defined in AVAudioSettings.h. When audioSettings is set to nil, the AVCaptureAudioDataOutput vends samples in their device native format.
*/
// (TARGET_OS_MAC && !(TARGET_OS_EMBEDDED || TARGET_OS_IPHONE))
/*!
@method recommendedAudioSettingsForAssetWriterWithOutputFileType:
@abstract
Specifies the recommended settings for use with an AVAssetWriterInput.
@param outputFileType
Specifies the UTI of the file type to be written (see AVMediaFormat.h for a list of file format UTIs).
@return
A fully populated dictionary of keys and values that are compatible with AVAssetWriter.
@discussion
The value of this property is an NSDictionary containing values for compression settings keys defined in AVAudioSettings.h. This dictionary is suitable for use as the "outputSettings" parameter when creating an AVAssetWriterInput, such as,
[AVAssetWriterInput assetWriterInputWithMediaType:AVMediaTypeAudio outputSettings:outputSettings sourceFormatHint:hint];
The dictionary returned contains all necessary keys and values needed by AVAssetWriter (see AVAssetWriterInput.h, -initWithMediaType:outputSettings: for a more in depth discussion). For QuickTime movie and ISO files, the recommended audio settings will always produce output comparable to that of AVCaptureMovieFileOutput.
Note that the dictionary of settings is dependent on the current configuration of the receiver's AVCaptureSession and its inputs. The settings dictionary may change if the session's configuration changes. As such, you should configure your session first, then query the recommended audio settings.
*/
@available(iOS 7.0, *)
open func recommendedAudioSettingsForAssetWriter(withOutputFileType outputFileType: String!) -> [AnyHashable : Any]!
}
/*!
@protocol AVCaptureAudioDataOutputSampleBufferDelegate
@abstract
Defines an interface for delegates of AVCaptureAudioDataOutput to receive captured audio sample buffers.
*/
public protocol AVCaptureAudioDataOutputSampleBufferDelegate : NSObjectProtocol {
/*!
@method captureOutput:didOutputSampleBuffer:fromConnection:
@abstract
Called whenever an AVCaptureAudioDataOutput instance outputs a new audio sample buffer.
@param captureOutput
The AVCaptureAudioDataOutput instance that output the samples.
@param sampleBuffer
A CMSampleBuffer object containing the audio samples and additional information about them, such as their format and presentation time.
@param connection
The AVCaptureConnection from which the audio was received.
@discussion
Delegates receive this message whenever the output captures and outputs new audio samples, decoding or re-encoding as specified by the audioSettings property. Delegates can use the provided sample buffer in conjunction with other APIs for further processing. This method will be called on the dispatch queue specified by the output's sampleBufferCallbackQueue property. This method is called periodically, so it must be efficient to prevent capture performance problems, including dropped audio samples.
Clients that need to reference the CMSampleBuffer object outside of the scope of this method must CFRetain it and then CFRelease it when they are finished with it.
*/
@available(iOS 4.0, *)
optional public func captureOutput(_ captureOutput: AVCaptureOutput!, didOutputSampleBuffer sampleBuffer: CMSampleBuffer!, from connection: AVCaptureConnection!)
}
最佳答案
AVCaptureAudioDataOutput.audioSettings 仅在 osx 上可用。您可以使用 AVAudioSession 修改采样率,但否则您将不得不安排任何您想要进行的转换。
有很多方法可以做到这一点,但是 AVAssetWriterInput.init(mediaType:, outputSettings:) 的 outputSettings 似乎是一个不错的起点。
关于ios - Swift header 中的 AVCaptureAudioDataOutput 中是否缺少 audioSettings 属性?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/41152448/
总的来说,我对ruby还比较陌生,我正在为我正在创建的对象编写一些rspec测试用例。许多测试用例都非常基础,我只是想确保正确填充和返回值。我想知道是否有办法使用循环结构来执行此操作。不必为我要测试的每个方法都设置一个assertEquals。例如:describeitem,"TestingtheItem"doit"willhaveanullvaluetostart"doitem=Item.new#HereIcoulddotheitem.name.shouldbe_nil#thenIcoulddoitem.category.shouldbe_nilendend但我想要一些方法来使用
我试图在一个项目中使用rake,如果我把所有东西都放到Rakefile中,它会很大并且很难读取/找到东西,所以我试着将每个命名空间放在lib/rake中它自己的文件中,我添加了这个到我的rake文件的顶部:Dir['#{File.dirname(__FILE__)}/lib/rake/*.rake'].map{|f|requiref}它加载文件没问题,但没有任务。我现在只有一个.rake文件作为测试,名为“servers.rake”,它看起来像这样:namespace:serverdotask:testdoputs"test"endend所以当我运行rakeserver:testid时
作为我的Rails应用程序的一部分,我编写了一个小导入程序,它从我们的LDAP系统中吸取数据并将其塞入一个用户表中。不幸的是,与LDAP相关的代码在遍历我们的32K用户时泄漏了大量内存,我一直无法弄清楚如何解决这个问题。这个问题似乎在某种程度上与LDAP库有关,因为当我删除对LDAP内容的调用时,内存使用情况会很好地稳定下来。此外,不断增加的对象是Net::BER::BerIdentifiedString和Net::BER::BerIdentifiedArray,它们都是LDAP库的一部分。当我运行导入时,内存使用量最终达到超过1GB的峰值。如果问题存在,我需要找到一些方法来更正我的代
Rails2.3可以选择随时使用RouteSet#add_configuration_file添加更多路由。是否可以在Rails3项目中做同样的事情? 最佳答案 在config/application.rb中:config.paths.config.routes在Rails3.2(也可能是Rails3.1)中,使用:config.paths["config/routes"] 关于ruby-on-rails-Rails3中的多个路由文件,我们在StackOverflow上找到一个类似的问题
给定这段代码defcreate@upgrades=User.update_all(["role=?","upgraded"],:id=>params[:upgrade])redirect_toadmin_upgrades_path,:notice=>"Successfullyupgradeduser."end我如何在该操作中实际验证它们是否已保存或未重定向到适当的页面和消息? 最佳答案 在Rails3中,update_all不返回任何有意义的信息,除了已更新的记录数(这可能取决于您的DBMS是否返回该信息)。http://ar.ru
我需要从一个View访问多个模型。以前,我的links_controller仅用于提供以不同方式排序的链接资源。现在我想包括一个部分(我假设)显示按分数排序的顶级用户(@users=User.all.sort_by(&:score))我知道我可以将此代码插入每个链接操作并从View访问它,但这似乎不是“ruby方式”,我将需要在不久的将来访问更多模型。这可能会变得很脏,是否有针对这种情况的任何技术?注意事项:我认为我的应用程序正朝着单一格式和动态页面内容的方向发展,本质上是一个典型的网络应用程序。我知道before_filter但考虑到我希望应用程序进入的方向,这似乎很麻烦。最终从任何
我希望我的UserPrice模型的属性在它们为空或不验证数值时默认为0。这些属性是tax_rate、shipping_cost和price。classCreateUserPrices8,:scale=>2t.decimal:tax_rate,:precision=>8,:scale=>2t.decimal:shipping_cost,:precision=>8,:scale=>2endendend起初,我将所有3列的:default=>0放在表格中,但我不想要这样,因为它已经填充了字段,我想使用占位符。这是我的UserPrice模型:classUserPrice回答before_val
我在我的项目中添加了一个系统来重置用户密码并通过电子邮件将密码发送给他,以防他忘记密码。昨天它运行良好(当我实现它时)。当我今天尝试启动服务器时,出现以下错误。=>BootingWEBrick=>Rails3.2.1applicationstartingindevelopmentonhttp://0.0.0.0:3000=>Callwith-dtodetach=>Ctrl-CtoshutdownserverExiting/Users/vinayshenoy/.rvm/gems/ruby-1.9.3-p0/gems/actionmailer-3.2.1/lib/action_mailer
我有一个包含模块的模型。我想在模块中覆盖模型的访问器方法。例如:classBlah这显然行不通。有什么想法可以实现吗? 最佳答案 您的代码看起来是正确的。我们正在毫无困难地使用这个确切的模式。如果我没记错的话,Rails使用#method_missing作为属性setter,因此您的模块将优先,阻止ActiveRecord的setter。如果您正在使用ActiveSupport::Concern(参见thisblogpost),那么您的实例方法需要进入一个特殊的模块:classBlah
刚入门rails,开始慢慢理解。有人可以解释或给我一些关于在application_controller中编码的好处或时间和原因的想法吗?有哪些用例。您如何为Rails应用程序使用应用程序Controller?我不想在那里放太多代码,因为据我了解,每个请求都会调用此Controller。这是真的? 最佳答案 ApplicationController实际上是您应用程序中的每个其他Controller都将从中继承的类(尽管这不是强制性的)。我同意不要用太多代码弄乱它并保持干净整洁的态度,尽管在某些情况下ApplicationContr