Comulytic Note Pro Battery and Storage Performance Testing Guide Methods

Direct answer: Comulytic Note Pro has one of the stronger paper specifications in the card-recorder category. Comu lists a 400mAh battery, up to 45 hours of continuous recording, 107 days of standby, a 90-minute full charge and 64GB of local storage. Those figures are manufacturer maxima. A credible review should test continuous recording, mixed daily use, standby drain, charging time, transfer energy and measured audio file sizes.

This guide does not invent completed endurance results. It provides a controlled method, calculation tables and pass criteria that can be used when the device is physically tested.

The 45-hour claim compares favourably with Genspark SecondBrain Note's 35 hours and BOYA Notra's 24 hours. Plaud's current product page contains different 30-hour and 50-hour references in separate sections, so its official maximum should be clarified before declaring a category winner.

Test principle: Battery and storage claims are meaningful only when firmware, recording mode, transfer pattern, temperature, file format and device age are disclosed.

Official battery and storage specifications

The product can record independently and store audio locally. Bluetooth and Wi-Fi are used for connection and transfer. Transcription and summaries require software processing, so the energy cost of transfer belongs in real-world testing.

Why vendor battery claims differ from daily use

“Up to 45 hours” normally represents a favourable continuous test. Daily use creates more overhead:

• starting and stopping many sessions;
• waking the display;
• Bluetooth reconnection;
• Wi-Fi transfer;
• file indexing;
• firmware activity;
• idle time between meetings;
• low or high temperatures;
• battery ageing.

A user may record only three hours but transfer several large files and repeatedly open the app. That pattern can consume more battery per recorded hour than a single uninterrupted session.

Continuous-recording test

The continuous test measures the headline claim.

Equipment

• fully updated Comulytic Note Pro;
• supplied magnetic charging cable;
• USB power meter;
• calibrated room thermometer;
• continuous sound source;
• stopwatch or logged clock;
• phone with Bluetooth initially disabled after setup;
• test log.

Procedure

1. Update firmware and app.
2. Charge until the device shows full.
3. Leave it connected for 15 additional minutes to stabilise.
4. Record room temperature.
5. Disconnect power and begin one continuous ambient recording.
6. Do not use Wi-Fi transfer during the run.
7. Check status at fixed intervals without opening the app repeatedly.
8. Record the time at shutdown or automatic recording stop.
9. Reconnect power and preserve the resulting file.
10. Repeat the test three times.

Result table

Use the median rather than the single best run. Report if the device preserved the final file after power loss.

Pass and fail thresholds

A publication should define expectations before testing:

These thresholds are editorial rules, not industry standards. They make the conclusion consistent and visible.

Mixed-use workweek test

Continuous endurance does not answer how the device performs for a consultant or salesperson. A seven-day mixed test is more useful.

Record battery percentage at 08:00 and 20:00, transferred gigabytes, number of files and connection failures. Repeat until charge reaches 10%.

The mixed-use result should be reported as:

• recorded hours per charge;
• elapsed days per charge;
• transfers per charge;
• percentage drain per recorded hour;
• percentage drain per standby day.

This is more practical than saying the device “lasted all week.”

Standby test

Comu advertises 107 days of standby. A full direct test would take more than three months, so an accelerated estimate can be used carefully.

30-day method

1. Charge to full.
2. Confirm no recording is active.
3. Keep the device at a stable room temperature.
4. Avoid app connections except at weekly checkpoints.
5. Record percentage on days 1, 8, 15, 22 and 30.
6. Calculate average daily drain.

Estimated standby days = 100 ÷ average percentage drain per day

If the battery falls from 100% to 72% in 30 days:

Daily drain = 28 ÷ 30 = 0.933%

Estimated standby = 100 ÷ 0.933 = about 107 days

This extrapolation is not a completed 107-day test. Battery gauges can be nonlinear, so the article should label it an estimate.

Charging-time test

Comu lists 90 minutes. Charging speed can change with cable connection, adapter, temperature and battery level.

Run the device down until it stops. Then:

1. allow it to rest for 15 minutes;
2. attach the supplied cable;
3. use a stable 5V source;
4. log current through a USB power meter;
5. note times at 10%, 25%, 50%, 75%, 90% and 100%;
6. record when current tapers;
7. repeat three times.

A useful review should report a quick-charge figure, such as minutes needed for enough energy to cover a two-hour meeting, even if the product does not market formal fast charging.

Wi-Fi transfer energy

Wi-Fi transfer is faster than Bluetooth but can increase short-term battery drain. Measure it separately.

Create one 60-minute recording, then:

• record battery percentage before transfer;
• transfer over Bluetooth if supported for the full file;
• time the transfer and record percentage after;
• recharge;
• repeat over direct Wi-Fi;
• compare speed and energy use.

The fastest method may not be the best when the recorder must survive a long field day.

What does 64GB mean?

Storage capacity alone does not reveal recording hours. Audio duration depends on:

• codec;
• sample rate;
• bit depth;
• mono or stereo channels;
• compression;
• metadata;
• reserved system space.

Articles sometimes assume a bitrate and publish hundreds of hours as fact. That is unreliable unless the device's actual file output has been measured.

Measure real storage consumption

For each recording mode:

1. clear or export existing test files;
2. record exactly 60 minutes;
3. export the original audio;
4. measure file size in bytes;
5. repeat three times;
6. calculate the median size;
7. inspect codec and bitrate with a media-information tool.

Then calculate:

Estimated hours = Usable storage in MB ÷ Median MB per recorded hour

If usable capacity were 59,000MB and the measured file size were 60MB per hour:

59,000 ÷ 60 = about 983 hours

That is an illustration, not a Comulytic result. The finished article should replace it with measured values.

Reserve space

Never plan to fill storage completely. Firmware, file indexes and transfer operations may need free space. A conservative workflow reserves at least 10%.

The reviewer should also test what happens near capacity:

• Is there a warning?
• How early does it appear?
• Can a new recording begin?
• Is the oldest file overwritten?
• Is the active file safely closed?
• Does transfer continue?

Overwriting old audio without a clear warning would be a serious issue.

File management and metadata

Storage quality includes more than volume. The reviewer should inspect:

• file names;
• recording timestamps;
• session duration;
• mode labels;
• speaker metadata;
• highlight markers;
• export format;
• original quality;
• folder structure;
• bulk export;
• duplicate handling;
• deletion and recovery.

The return policy requires the user to erase personal data before sending a device back. A storage test should therefore verify factory reset and account unbinding.

Battery health over time

Lithium battery capacity declines with charge cycles, heat and long periods at full or empty charge. Comu lists a 12-month US warranty, but the reviewed product page does not publish a replaceable-battery programme.

A long-term review should retest after:

• 30 days;
• 90 days;
• six months;
• twelve months.

Use the same continuous and mixed-use protocols. Report retained capacity:

Retention = Current median runtime ÷ New-device median runtime × 100

If a new device runs 42 hours and later runs 37.8:

37.8 ÷ 42 × 100 = 90% retention

Again, this is an example calculation.

Comparison with leading alternatives

The table uses manufacturer data and should not be presented as a real-world battery ranking. Different test procedures can produce different outcomes.

Comulytic has the strongest combination of a clear 45-hour claim and unlimited core processing. TicNote publishes a longer figure, while Plaud needs to clarify its own page.

Workload calculations

Consultant

Four hours of meetings per workday:

45 ÷ 4 = 11.25 recording days

Student

Three hours of lectures per weekday:

45 ÷ 3 = 15 lecture days

Journalist

Six hours of interview and field recording daily:

45 ÷ 6 = 7.5 field days

These are theoretical maxima before transfer, display, connection and standby overhead. Real-world expectations should use the mixed-use result.

Buying implications

Battery matters most when:

• the user records away from power;
• meetings are unpredictable;
• phone battery must be preserved;
• files transfer only at day's end;
• travel creates long standby gaps.

Storage matters most when:

• cloud upload is delayed;
• recordings must be retained locally;
• sessions are long;
• internet access is unreliable;
• original audio must be preserved for audit.

A buyer who synchronises after every short meeting may never approach 64GB. A field researcher can depend on it.

Final assessment

Comulytic Note Pro has an excellent paper endurance profile. Its 45-hour continuous claim, 107-day standby claim, 90-minute charge and 64GB storage make it suitable for heavy meeting schedules.

The specification should not be converted into a final performance verdict without testing. A top-quality review must publish the median of repeated continuous runs, a realistic mixed-use week, 30-day standby drain, charge curve, transfer cost and measured megabytes per recording hour.

The combination of long battery life and unlimited core transcription is more valuable than either feature alone. The recorder can capture a heavy workload, and the owner is not immediately pushed into a small monthly transcription quota.