If I'm not completely wrong, the first variant saves image data in PNG format while the "write" version seems to use raw image data, hence the difference in size. PNG is compressed, the latter is uncompressed.
Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
rs2000
@rs2000
Knowledge and experience in:
Music composition
iOS app beta testing
GUI design
Workflow design
MIDI protocol conformity of apps
Ableton LINK
Embedded systems
Current WAN and wireless network technologies
Security
Test automation
DSP algorithms
Best posts made by rs2000
-
RE: difference in file-size when using share_image_data(bytesObj) vs. write(bytesObj)posted in Pythonista
Latest posts made by rs2000
-
RE: difference in file-size when using share_image_data(bytesObj) vs. write(bytesObj)posted in Pythonista
If I'm not completely wrong, the first variant saves image data in PNG format while the "write" version seems to use raw image data, hence the difference in size. PNG is compressed, the latter is uncompressed.
-
RE: Midiposted in Pythonista
I guess I have found a solution.
By MIDI we're talking about MIDI messages, not handling standard MIDI files (which isn't a problem in Pythonista).The most viable option I see atm is using a proxy app like MidiFire from Audeonic (available on the iOS App Store).
Open the "other app", run MidiFire and add an OSC module and a MIDI source or destination, depending on your use case.
Then connect the modules you've just added.To communicate with MIDI messages between Pythonista and your app of choice, all you have to do is send and/or receive UDP packets containing MIDI wrapped in OSC messages.
Have fun :)