I am using OS X 10.8.4
I just purchased a USB Cassette Capture from amazon in order for me to transfer my music from Digital Audio Cassette to Mp3 or iTunes , I installed the cd on my pc and discover there is link for Macbook user, from there i link to the internet and downloaded the Mac latest version of Audacity 2.0.4 on my mac.
I followed all the tutorial and connected my usb cassette capture device by the accompany usb cable, but while the audacity showing recording and the tape is rolling. when i stop, and play the recorded track, the sound is not coming out.
Download Zip ☆ https://t.co/3GuR7SjVqX
Thanks a lot for going extra length to help me out. I understand your point very well now. I used my old dell laptop with my portable cassette recorder and an audio cable rather than the USB cable - connected to the microphone port, and it did work excellently.
If you don't want to make your user account have sudo privileges (because you worry about security), you can use applescript to solve this. In my case I am using screencapture indirectly as part of another program so I'm converting that to an example here to use screencapture directly as the OP did.
You can leave out the > daily_output.txt 2>&1 bit if you don't expect any output from the program you call (like screencapture). The && exit is on there to close the Terminal window when it's done. If your Terminal doesn't close when you run exit, check the Preferences->Settings->Profiles->Shell and check the When the shell exits setting.
Command-shift-5 is all I use now. It lets you capture the whole screen or part of the screen as a still image (to a file or the clipboard), and the whole screen or part of the screen as a video. You can choose whether to record audio, and where the audio comes from.
OBS is indeed streaming-oriented, and many of its parameters are here for that.
However, you can set up a screen recording (with or without sound, mic or internal) in a few minutes, and the result is not as heavy. Same parameters, 1 min fullscreen, 3,8bm (mp4 too)
I have two MacOS computers signed into the same dropbox account. Macbook1 stores captures in the Capture folder. Macbook2 does not, but its captures are saved to I want both computers to save locally to their respective Capture folders and to DropBox. Is this possible ? How to set this up on Macbook2 ?
Uninstall ( with AppZapper) and updated to latest version fixed the issue. It would be really great to know where to find or generate logs and also have control over the Capture Folder So I could separate these out for multiple computers
Did this post help you? If so, give it a Like below to let us know.
Need help with something else? Ask me a question!
Find Tips & Tricks Discover more ways to use Dropbox here!
Interested in Community Groups? Click here to join
The replacement doesn't contain a regex, it contains a string which could reference capture groups defined in the regex. To replace the first word by the last one, you need to capture the last word and the rest of the line:
I'm trying to figure out how to prevent users of my app from snapping a screenshot of any of my app's windows. I'm mainly concerned with users automating screenshots using /usr/sbin/screencapture with cron. At first I thought there was no way to prevent it but then I discovered that there are some apps that are doing something that causes the screenshot to be all black or the color of the desktop. If I could pull that off I would be golden. I've seen other posts that touch on the subject but nothing that actually works in my situation. I'm running catalina. Any and all insights would be greatly appreciated.
setSharingType: specifies whether the window content can be readand/or written from another process. The default sharing type isNSWindowSharingReadOnly, which means other processes can read thewindow content (eg. for window capture) but cannot modify it. If youset your window sharing type to NSWindowSharingNone, so that thecontent cannot be captured, your window will also not be able toparticipate in a number of system services, so this setting should beused with caution. If you set your window sharing type toNSWindowSharingReadWrite, other processes can both read and modify thewindow content.
Note: this question is intentionally very general (e.g. both Objective-C and Swift code examples are requested), as it is intended to document how to capture a window screenshot on macOS as accessibly as possible.
The Macintosh operating system has always made it easy to capture a screen shot. A screen shot is an image of your computer desktop or an active window. Here's a summary of all the keyboard shortcuts you can use to capture your screen in Mac OS X.
Computing Tips and Techniques are brought to you by the Information Technology Group for the purpose of sharing a wide variety of technology tips with its clients. The collection of these tips are protected by intellectual property rights, such as copyright. All intellectual property rights belong to the manufacturer of the software product in question.
Hi, I just got a GPCAM2 290C and am using Altair Capture on a Mac OS X 10.15.5 (Catalina)
Does this version have the same functionality as the Windows version? I can't seem to find how to do live stacking and don't have access to the top menu options visible in the Windows screenshots (Capture, Image, Process etc)
I have raised this question on Altair Astro's facebook forum but thought I'd check here to see if anyone has any experience of using this combo successfully (or suggestions for Mac compatible software that does something similar)?
I think all the rebranded versions of Touptek's software for MacOS and Linux are "Lite" versions of the Windows application (though I'm only going by what I've seen -- I've never used the Windows versions and rarely touched the MacOS/Linux versions).
I believe they should support your camera. Embarrassingly I've not got around to writing a manual for oalive yet. I'm happy to have feedback on ideas for improvements or if you find bugs (surely not! :)
2. Also working with KStars/INDi/EKOS. I have this running on my Mac and PHD2 also is fine using a ZWO guide cam and controlling my CEM40. But my 269c is not recognised and I am trying to find out from INDI and Altair why.
Frustrating for us Mac users isn't it. I tried a few different tools but finally resorted to using the family Windows laptop with dodgy USB. After a frustrating session last night with the camera disconnecting every time I went near it I'm back to considering Mac options. I know Mac isn't high priority for Altair having discussed with them via Facebook. They were working on a Mac SDK, and I was hopinh that it could get included in Firecapture which seems to have what I want in a Mac compatible tool. Don't think the sdk materialised though so will follow up with them again.
Oacapture looks good, Oalive also but doesn't support alignment in Live stacking. When I get time I'm going to try a combo of Oacapture to output FITS files and ALS to read the output folder and align and stack the images.
You could try Cloudmakers Astroimager which is a native MacOS app. It supports the Altair cameras but probably in the same way as INDI so might not recognise the camera if the problem is with the Altair driver.
The SDK does exist, kind of. It seems a bit haphazard to me though, and I don't really understand why it should be. Touptek presumably do all the work. All they'd really need to do would be to make the files available easily from their website (they didn't used to, but to be fair I've not checked very recently) and have some arrangement for reporting bugs.
I will add alignment in the live stacking for oalive. Probably not in the next release as I'd like to get that out relatively soon, but perhaps in the release after that when I have more time to do the coding.
ADDED: Capture seems to like GBRG in APP and DSS for the 269c. I think it must be to do with ROWORDER things on the Bayer Matrix. APP reads the FITS files as RGGB and wants to process them that way. You have to use tab 0, and force the CFA to GBRG and then the stacked files look sensibly coloured.
OK so here is an interesting fact about oacapture and oalive. As they download right now they do not see the Hypercam 269c. BUT - if you grab the libaltaircam.dylib file from the latest Altair Capture and stick it into the oalive/capture package directory then the oa stuff does recognise the 269c, and as far as I can tell it works well apart from not having the cooler controls. So it would seem to me that only a small amount of work recompiling with the latest SDK ought to enable it properly. Hint hint!
795a8134c1