Jump to content

Search the Community

Showing results for tags 'Freqfinder'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Main Board
    • Current
    • The Daily Journal
    • General Discussion
    • Equipment
    • Cameras... love them, hate them
    • Recording Direct to Computer
    • Workflow
    • The Post Place
    • Images of Interest
    • Macs... and the other computer
    • All Things Apple
    • Technical Reference
    • Do It Yourself
    • Manufacturers & Dealers
    • Work Available - Available for Work
    • Post to the Host
    • Donate to Support JWSOUNDGROUP

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL








Found 6 results

  1. FreqFinder version 1.8 for Android has been released and iOS version 2.3 is soon to follow. And what is new to both is worthy of a little bit of explanation. Settings which will affect the intermodulation calculation have been added. iPhone users had the 3x3 and 2x7 settings previously. The transmitter spacing and intermod spacing factors will be added soon. A summary of each of the settings: - Enable 7th Order Products This setting was enabled by default. Turning it off will provide you with more compatible channels at the cost of the quality of those channels. 7th Order Products tend to be much less severe and therefore users may wish to disable their calculation. - Enable 3 TX 3rd Order Products This setting was also enabled by default. Turning it off will provide you with more compatible channels at the cost of the quality of those channels. 3 TX 3rd Order products occur mainly when you have large groups of radios in tighter spaces. One might disable this if he were reasonably sure that the transmitters will be rather spread out. - Intermodulation Spacing Factor The default for this setting has always been at its least conservative. This is the padding between a transmitter and any intermodulation product. Increasing this value will result in fewer compatible channels. ***Note that the number itself is rather arbitrary. I do ask that you play with different settings and if you come to any interesting conclusions, I would very much like to hear them*** - Transmitter Spacing Factor This factor determines the minimum spacing between transmitters according to their bandwidth. The calculation averages two transmitters' bandwidths and then multiplies by this factor to determine the spacing. The default for this setting has always been at its least conservative, however a couple of transmitters have built in alternative minimum spacings (Lectrosonics has 300khz). This setting will override that minimum if it calculates a larger spacing. Even with maximum settings, a user will still get 10 channels out of a single Lectrosonics block. These controls are meant to provide extra protection and still allow a users with larger transmitter counts the ability to squeeze more channels in. I would recommend for most cart setups dialing the settings to maximum and keeping them there. I want to note that for these settings, you can not dial down the settings midway through adding transmitters and expect the first set of transmitters to stay protected at the higher settings. When you change the settings, all of the transmitters are protected at those settings. On that note, hopefully everyone has noticed the "Protection" switch on the transmitter details page. That is meant to add transmitters which would contribute to intermodulation but for which you do not care about the performance of the transmitters. In the future I'd like to have three protection options (NONE, DEFAULT, and EXTREME) that would allow for extra protection to selected transmitters. I hope everyone is finding FreqFinder suitable to their needs, and as always I love to hear from you guys. Best, James
  2. I will be posting an iOS version update very soon, with a number of new features: - Substantially faster calculation (for the supporting of more transmitters and for future customization options) - Disable transmitter feature - Custom TX Types, implemented via our brand new - Import / Export feature Here's the deal with Import and Export: for right now it is implemented only using the built in Mail app, so you need to be configured to use the built in Mail app. I looked into the Gmail app; it is not possible to use the gmail app to open an attached file inside of another app. Turns out, it's not very user friendly in general to get files into and out of apps. The only other built in option is Apple's app file sharing which requires you to use iTunes on a computer. I didn't think that was very user friendly. If nothing else, I'll probably incorporate Dropbox file sharing in there in the future. Also, the import feature is moderately smart. While you can simply add all of the imported transmitters to the current or new list, I imagine people will want to be synchronizing lists frequently. For that purpose, each transmitter is assigned a UUID. Transmitters therefore can be updated with new information with each import. Granted, it is not as sophisticated as perhaps a cloud sharing service, but that's a conversation for another time... I have created a new file format called ".ffx". It is an xml document. It can be opened with a text editor (on a computer) and is human readable. And you are free to edit these files to create custom transmitters and custom transmitter types with custom channel lists. The file format should be mostly self explanatory, and I've done my best to make these files pretty idiot proof, but I fully anticipate that with enough people tinkering, somethings will go wrong. And as usual, I am (relatively) immediately accessible to work through whatever problems you have, and I want all of your input to continue to make the app better. And as usual, the Android version is behind on the programming. A lot of work went into these new features, and it will take time to implement them in the Android version. However the priority is the Import / Export, and since we don't have to wait a week or more to update, I'll post the new features incrementally. Cheers, James
  3. Hi again. I am happy to announce that the TV Station Add-On for FreqFinder is very nearly ready for primetime! Features include: - Look up station data for your current location (determined by gps, cell, or wifi) or for any location in the US - Relate station data to any specific location for approximation of the interference caused by TV transmitters at that location - Relate station data to multiple locations simultaneously for a "worst case scenario" estimate - Station data for the selected areas stays on your device for offline use - Sort TV stations by name, channel, and estimated field strength - Filter TV stations by license status and by the channels affecting your current transmitter list (fully customizable filtering to be added in the future) - Station transmitter detail screen featuring a map view of the station's polar pattern - Estimated field strength calculation provided directly by the FCC - Location Profiles allow for multiple location configurations - Easy map search functionality allows fast finding of locations by address The add-on will be an in-app purchase costing $15. I am going to release it early (before it is available for purchase) and extend the preview time until the end of October to give everyone a chance to play. Soon after this update, the in-app purchase will be available, extending the functionality indefinitely. After October, the preview will expire and the add-on will have to be purchased in order to access any station data. I'm sorry to say that for the moment, the v2.0 will only be available for iPhone users. The Android preview will continue to be available until I make the complete add-on available to Android users. *Current FreqFinder users: the FCC has changed the format of their TV data. This update is required to properly receive FCC data. Currently, FCC data is only downloaded upon major location changes (>20 miles) and fresh installs. An update for Android is already on the app store. The iPhone update will be available as soon as Apple approves the update. Thank you for your patience.
  4. Hi everyone, you may or may not have noticed I've been doing some updating of the FreqFinder Android app. After one or two emails about an update not working I decided to take advantage of Google's relatively new Beta program. I'd like to invite anyone who wishes to participate by joining this Google Group: https://groups.google.com/d/forum/new-endian-android-beta-testing The main mechanism here is that I can release updates and then those who chose to update to the beta version can and those who may be using FreqFinder more actively can wait until it has been more user tested. Also, it should allow users to roll back to the stable release version if there is a problem. And of course this will help me better keep in contact with all of my users. Please pass on the link and I hope to see everybody there. Sincerely, James
  5. Hello again. I submitted updates for both LectroRM and FreqFinder and wanted to let you know what they're all about. The majority of changes are purely cosmetic (as is iOS7). The UI for both incorporates iOS7's new stock widgets. Personally, I rather liked the old look, but the new look isn't so bad either (even though a lot needed to be updated to make the apps compatible with iOS7.) The biggest thing to know though is that before the app updates actually hit the app store, iOS7 users will have an issue with the naming and custom frequency dialogs in FreqFinder and the info dialog in LectroRM. iOS7 has a compatibility mode for most everything else, but not those custom dialog boxes. It was a pain to get it to work also. Anyway, if you can hold out on updating to iOS7, great. Otherwise hopefully the updates will be approved sooner than later. There are some bug fixes. I couldn't pinpoint the particular problem that lead to a few users experiencing rampant crashing, but I made some improvements to the code where it could be caused, so hopefully it helps. The only other thing to note is that LectroRM now has a memory for Audio Level and Channel! I was a bit wary of increasing the complexity of LectroRM, but I think I found a simple and elegant way to add it to the app without decreasing usability. Anyway, I hope you all enjoy.
  6. The latest version of Apple's development tools for iOS does not support armv6 devices. This means that I can't easily build for both iOS 6 and iOS 4.2.1 users. These are the devices that will be affected: iPhone 3G (not 3GS) iPod Touch 2nd Generation I can try to figure out a work around (not that there necessarily is one), but I wanted to hear from people still using those two devices. I may have to drop support for them. -James
  • Create New...