Just tried Capture for the first time, successfully recorded some audio etc , transferred to Studio One a breeze, all good.
Now, looking at the help pages within Capture, I want to delete the session.
I can "edit" the list of sessions, then I get a red round button, which when I click on it turns into a red button with a bar across it. Click - done, nothing happens, session remains.
There must be a simple way to delete, I am following the user guide within the app exactly, it simply says, click on edit and delete.
I've tried swiping, clicking "done", double clicking the red bar etc. Nothing removes the session.
Simple? Not at all....!
Yes, it is the usual swipe from the right to left, but it seems to be a little haphazard in the exact place you swipe...be careful, but it will work from the list of songs, place finger to he right of the song you want to delete and swipe left, it may take a few goes to get it right! It's bad implementation of the iPad technique on the part of Capture I believe - if Im not the only one having trouble....!
I just receive my Audiobox itwo today, Sept 29.
Here is how I was able to delete a session in Capture Duo:
On the main menu Tap on Edit
Press with you finger the Session you want to delete
Once you see the Minus sign, Press on the PLUS sign on top of the Sessions listing
The deleted session should disapear
It worked for me!
Currently this seems to be the only way that works for me:
- Completely close Capture (double-tap iPad button and remove Capture form the list of running apps)
- Start Capture
- Press 'Edit'
- Put a finger in one of the red circles and drag it to the right (a horizontal bar must appear in the circle)
- Press the checkmark icon above the red circles
You can only delete one session at a time, and the app needs to be restarted again if you want to delete another one.
I don't know if this cumbersome procedure is intentional or a bug.
It's March 20, 2018 and this problem still hasn't been resolved. PreSonus, please look into this. Sessions cannot be deleted from within the app. Sometimes the app is wholly unresponsive.
iPad Mini 2
Capture 18.104.22.168667 iOS (Built on Jul 20 2016) <--- there's the problem
My Workaround for Deleting Files:
I've got a workaround that may help others, as I was having a multitude of issues with Capture for iPad that were driving me crazy until I discovered this "solution" by accident.
I found that most of Capture's functionality was a one-command-only operation, and in order to execute a second command I needed to re-start the application. Because that's a frustrating way to work, I decided to delete the application from my iPad but wanted to transfer all of my audio files first.
That's when I discovered that when the iPad was connected to a laptop with a lightning cable, the app works perfectly. When working this way, adding, deleting song and tracks works as expected. Not very mobile but at least it's a usable workaround that keeps Capture for iPad out of the trash bin.
Hopefully Presonus uses this info to determine the source of the issue and correct it.
I was pretty excited when the above solution was working. I did manage to get all of my songs exported to my laptop without restarting the Capture app, but the excitement was short-lived. I'm back to where I was before: One command, then re-start to get the app working again.
I've come to the conclusion that the Capture file data (plist or xml) must become corrupted after working with a relatively small number of files. My plan is to transfer my recordings out of Capture soon after creating them, and deleting the files from my iPad. Currently, I deleted and re-installed Capture from my iPad so that I could start with a fresh data file.
finngruwierlarsen wroteCurrently this seems to be the only way that works for me:
This one worked for me, but I could only do one session at a time...
Yes i m also facing same problem..Code worked for me but i could do only single source at a time..Any solutions to it?
The CameraDevice may be utilised to make a CameraCaptureSession, that is unique to this CameraDevice. A CameraDevice must get a frame configuration for every output raw framework through the CameraCaptureSession. 1 configuration in, just one raw framework out. The configuration defines camera attributes like aperture, autofocus, effects, and vulnerability. Because of hardware limitations, just a single configuration may be busy in the camera detector at any given moment; this can be known as the active setup .
A CameraCaptureSession explains all of the probable pipelines accessible to the CameraDevice. After a session is created, you can't remove or add pipelines. The CameraCaptureSession keeps a queue of CaptureRequests that turn into the active setup.
A CaptureRequest adds a configuration into the queue and selects one or more (or all) of those accessible pipelines to be given a frame from the CameraDevice. You're able to send many catch requests within the life span of a capture session. Each petition can alter the active configuration and place of output pipelines which will obtain the raw picture.
Users browsing this forum: No registered users and 1 guest