Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Profile Information

  • Location
    Pittsburgh, PA
  • About
    Apps for an evolving world of film and television production
  • Interested in Sound for Picture

Recent Profile Visitors

2,544 profile views
  1. I think it helps to think about intermod like we do audio overload/clipping. When your audio signal is too hot, it sounds weird. The distorted sound is the extra frequency content that is generated. Intermod products are extra frequencies generated by overload. The overload occurs in any active circuitry: transmitters, receivers, active antennas, etc. A transmitter's circuitry can be overloaded by another nearby transmitter, and those transmitters can then transmit the intermod generated by that overload. Things that help intermod are the same things that help audio overload: less powerful signal and high dynamic range circuitry. In wireless, that means low power transmission and distance between devices. It also means passively filtering out frequency content that isn't the desired signal. Can you simply attenuate the signal? Yes, but in audioland, if you have two actors, one very close to the microphone and one far away, turning down the gain will make it hard to hear the one that's far away. So why can we coordinate channels for intermod? The extra frequency content is predictable. When your audio recorder gets overloaded, it sounds weird, but you can still understand the speech. That's because the original content is still there. The extra power just gets dumped into other frequencies. We avoid tuning to those frequencies. But the more extra power, the more extra frequencies are generated. What does it mean when a manufacturer says "No Intermodulation"? It usually means within their system, their transmitters run at a low enough power and their receivers have quality filtering and/or dynamic range that none of the devices can overload each other in normal operating circumstances. But every device that has an Op-Amp has a dynamic range. I personally have had a lot of trouble with walkies (1-5 watts) and the Sony 470 mhz digital system and would generally recommend systems that do not include that frequency range in their tunable range. Generally speaking, wideband devices have been detrimental to wireless performance. Fitting a large bandwidth into the same physical case means wider front end filters. Filtering out non-signal frequency content is one of the biggest weapons we have. The old Audio Ltd systems had 16 channels, each with a dedicated filter. Lectro 411s had an array of very narrow filters (tracking receivers). To answer your question: Zaxcom transmitters have a relatively low output power (25/50/75 mW). They shouldn't cause much trouble for the Lectrosonics transmitters or receivers. Zaxcom recently released their 214/414 receivers with increased RF dynamic range. I haven't used them, but RF dynamic range is one of the keys to performance. They are wideband though, which means wide filtering. And you might be running the Lectrosonics system at 100 mW. Usually the physical distance between devices is enough to make that power output fine. But that is when you want to coordinate channels.
  2. I've decided to make two of my apps: Open Callsheet and Timecard Buddy completely free to use until December. Both of them are meant to cut down on paper use, so maybe they'll play a small part in keeping people safe. opencallsheet.com timecardbuddy.com Video demonstrations: OpenCS - https://www.youtube.com/watch?v=I3NosM6ZO3I TCBuddy - https://www.youtube.com/watch?v=HxkxMsfPSAU (My apologies for excluding those outside of the US. These apps are designed specifically for film production members in the US and Canada)
  3. This is why we beta test. Yes, I can change that.
  4. I have figured out a way to fit Audio and Frequency in the Apple Watch screen. Take a look at the beta: https://testflight.apple.com/join/d9aopgN6
  5. I will pick your brains about some possible ways forward regarding the audio level. Apple Watch is limited in a lot of ways, but I do have some ideas. For now, I need to see what the interest is; how it's used; whether or not it really works as is. I don't even have an Apple Watch yet (Series 3 was on sale though on Amazon though, so I ordered one). "Audio level 90% of the time" is a perfectly valid thing to say. I hadn't invested the time or money into the idea before for a reason. Nevertheless, I was persuaded some people would find this useful. It is completely independent from the main app, and my plan is to make it $10. So it is not lost on me that the functionality is limited.
  6. Here's a rhetorical question for you: does your response reflect who you are? For everyone's information, I was asked to make this version, with or without audio level. I asked him what benefit he saw in it. He gave me a good reason. That's all I'm going to say. I'm not here to sell. I'm here to get real feedback so that the product works for the people who find it beneficial.
  7. I have an Apple Watch version of LectroRM coming. It'll do the LectroRM functions except Audio Level and Frequency for UI reasons. I don't use iPhone and only just ordered an Apple Watch. Here is a link to the beta: https://testflight.apple.com/join/d9aopgN6 Let me know if anything weird happens
  8. Timecard Buddy and Open Callsheet are dependent on the conventions used in the US. Timecard Buddy provides templates of the paper timecards we use in the US. I can support those because I am familiar with the accounting practices here. And when it comes to people's paychecks, I have to be very sure I can support the accounting practices of my app. Open Callsheet is in beta, so starting small is a natural part of that. But the app also uses AI to detect information from the callsheets emailed to us. The AI has to be trained on sample callsheets in order to work. I only have access to US callsheets to train the AI, so I have no idea whether it would work with Ireland's callsheets. Generally speaking though, it really should not be taken for granted how the idiosyncrasies of each country multiply the complexity in an app. There've been many bugs in FreqFinder related to the difference in number format. 512,000 in the US means something different than 512.000. The solution to that is to use the phone's locale setting to provide context. But I did have one user who wanted English language and French numbers. Still that's a relatively simple example. When dealing directly with a country's conventions is at the core of the app, I can only program what I know.
  9. Users can now import pdfs. Signing in with Google or Microsoft is no longer required
  10. Open Callsheet Beta on Android now does text selection that will also link to Maps, Phone, and Email https://play.google.com/store/apps/details?id=com.newendian.android.opencallsheet
  11. Update: Microsoft email support has been added (Outlook, Hotmail, etc) It seems people are suspicious that something so simple could be useful, so let me start again. I have gotten a lot of suggestions to make a "Callsheet App". It's a reasonable inquiry: the digital age, the digital callsheet. The problem with most callsheet app concepts is that it requires both the AD and the crew members to use the app in tandem. If the app doesn't do something the AD needs, then all support is lost. So this concept turns that around: don't depend on cooperation from the AD. Take all the varied forms that ADs distribute, and take what information from them we can. And for that, we turn to artificial intelligence. Which, believe it or not, is not so simple, but can do enough to detect what a callsheet looks like. Things get complicated when you have to do something like detecting which date (of the many things that look like dates) is the titular date of the callsheet. And way more difficult when detecting where basecamp is. Luckily, much of the utility of a digital callsheet comes merely from having the callsheet accessible at one's fingertips. We can all read. If we're about to approach a person whose name (but not title) we've forgotten, we don't need that name on a specially formatted menu screen. It's midway down page 2. And that situation happens so much - just need to check one thing, but I don't have the paper on me - it's worth creating an app for that. Most people use the built-in pdf reader, and at least on Android, file management is non-existent, so opening the callsheet at the spur of the moment means searching through one's email every time a person wants to open it. Even creating a shortcut to a downloaded file is a cumbersome experience. Now there are certainly integrations that people want to see in a digital callsheet, but without the cooperation of each individual person making the callsheets (and trust me, convincing people to use your app is not easy), you have to rely on AI. And that means that sometimes it won't detect the information, but you still have to have functionality to fall back on. So I need beta testers to make sure the foundation is solid. Because I do want to expand on this concept, but it has to start from a place where everyone can use it.
  12. So this app will do what you've done for yourself: keep your callsheet within a single button press, except without having to import it each day. The plan is to do tie-ins (maps, phone numbers), but no markings.
  13. It's about speed. One button access instead of searching through your email every time you need to look something up.
  14. Not at the moment, but possibly in the future Technically it is worse than a PDF reader because you can't select text, and that is something I plan to remedy. Still my hope is that there's a lot of utility there already.
  15. That is correct Olle. Though if you don't have a callsheet for the day, it should say "No Callsheet Found". I'll check on that. If for some reason you do have a callsheet but it wasn't detected, you can look at a list of pdf attachments with the lower left button. I should change the ads moment to only run when a pdf is about to be displayed (once per day is the plan, with a paid no-ads option) I have opened it up to Canada All important feedback
  • Create New...