Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Comments

39 comments

Date Votes
  • WPNL
    Looks very promising but only in Polish, that's a shame.
    I've tried tonight and it's too difficult so I gave up, I'm confident if you'd translate it, the app will have more chance of usage for the rest of the world (non-Polish speaking people).

    I really hope you'll get this because it looks really great as far as I could see!
    0
  • John Doe
    Same here, I can't read Polish. ☹️

    Would this driver allow us to use e.g. Arturia's BeatStep device directly with Capture One? It would be fantastic.
    0
  • WPNL
    That's the point indeed! 😊

    Plus some extra features, he's got some great ideas in there
    0
  • John Doe
    Hell he could even licence it to Phase One for inclusion in future Capture One versions. 😊
    0
  • WPNL
    An addition to keyboard shortcuts for: Channel, controller, value would be great.
    Or even a preset(manager), anyway I'm pretty sure Phase One could provide such a thing.

    but... does it get in the way of Tangent... 😉
    0
  • Ryszard Stelmachowicz
    [quote="WPNL" wrote:
    Looks very promising but only in Polish, that's a shame.


    Since I wrote this software for myself, I do not plan other language versions (and I am not ashamed of this).

    "And let the other nations always know it well
    That the Poles are not geese, that they have their own tongue."
    Mikolaj Rej

    If someone is ill that he gets something for free, he can always just not use it.
    0
  • John Doe
    [quote="rstelmach" wrote:
    [quote="WPNL" wrote:
    Looks very promising but only in Polish, that's a shame.


    Since I wrote this software for myself, I do not plan other language versions (and I am not ashamed of this).

    "And let the other nations always know it well
    That the Poles are not geese, that they have their own tongue."
    Mikolaj Rej

    If someone is ill that he gets something for free, he can always just not use it.

    I don't think anyone here meant to insult you or that you should be ashamed of your language, of course! But indeed providing an english translation would be helpful to a lot of users, which is what you want to do, right: be helpful to people? Thx for your work anyway.

    PS: by the way English is not my native language either.
    0
  • WPNL
    [quote="John Doe" wrote:

    I don't think anyone here meant to insult you or that you should be ashamed of your language, of course!.

    Exact! I really respect the work he did, was only trying to inspire, unfortunatly words can be interpreted in more than one way... anyway, great app. (but for now I'm sticking with BOME)
    0
  • SFA
    FWIW Google Translate makes a great job of the Web pages - which suggests they are really well written to start with.

    I'm looking at translation to English but presumably other translations would be equally as good.

    The deal with most free (Or should I use the term "Open Source"?) software seems to be to find an enthusiast (or several) who can undertake the translations.

    Not too difficult for documentation (in theory) but a little more difficult for the application unless the text is somehow driven by reference tables that can be identified by language preference settings.

    Of course we all know that theory so I guess it is easy to discover how easy or challenging an application text translation might be.


    Grant
    0
  • Alain Decamps
    Nice

    But I suppose that it's only a translation midi-keypresses?

    Essentially something like Bome's, but specific for the -nice- arturia beatstep?

    BTW. Asking somebody to do an English translation can be very helpfull for you're application.
    0
  • Ryszard Stelmachowicz
    All you have to do is translate the [Etykiety] section in the 'Midi2Macro.ini' file (Midi2Macro label for all MIDI controllers and programs) and possibly the 'Opis' column in the Midi2Macro.m2k file (data only for Arturia BeatStep and Capture One). I just do not want to explain it and I do not need other languages. If someone can not survive just a few subtitles in a foreign language, he can get there whatever he likes.
    This is not specific to Arturia - it should work with any controller - only then you have to define yourself all the transcodes (I did for Arturia, for I only have such a MIDI controller).
    0
  • John Doe
    Do you think you could make a macOS version or is it out of the question?

    BTW could you be a bit nicer to people asking about translation or even offering to translate? Can't understand the way you're reacting to this, to be honest... 😭
    0
  • Ryszard Stelmachowicz
    Unfortunately, not because I do not have such a macOs computer.

    BTW The whole translation of the program consists in translating literally 46 short lines of text from the Midi2Macro.ini file - I will not understand where the problem is ?! The Midi2Macro.m2k file is a configuration of individual manipulators for Arturia - a file that anyone can create for themselves (in BOME it does not get it at all so there is no problem that something is untranslated - it has to write everything for itself). Such a configuration can be created for any program that is operated using the keyboard (Lightroom, Photoshop, Elements ... other programs not only graphics) - everything can be in the same file (Midi2Macro recognizes what program is running and selects the appropriate recoding). I created configurations only for Capture One because only that was needed for me at the moment. You can easily delete the help files (pictures) and the Midi2Macro.m2k file (there is the most language there) because this is just my example configuration that anyone can create for themselves. Only the Midi2Macro.exe file is needed to run the program - all the rest are additional (configuration) files.
    0
  • John Doe
    OK, understood. 😉

    Nice work, indeed.
    0
  • Ryszard Stelmachowicz
    The problem is in fact somewhere else than you see it. After configuration (and this is included in the zip file for Arturia) the language is completely irrelevant (when using the program it is not noticeable).

    The real problem, however, is the lack of keyboard handling in Capture One (and thus enabling support using the MIDI controller).
    I wrote a bit about it here:
    https://fotorys.wordpress.com/2018/01/1 ... one-braki/

    The point is that Capture One has a very cursory (even selectively) treated problem of using the keyboard. Apparently no one paid attention to this, but it does not reach the Lightroom (which, however, has it much more accurate). These are simply deficiencies in functionality. And as to whether this would hurt Tangent ... I do not think so. How many people will buy an expensive Tangent (how much will the company earn) and how many people would buy Capture One and a cheap console if it could be handled more conveniently than Lightroom (how many more licenses would Capture One then sold)? I think that there is a huge field for development - just to Capture One it was more convenient to use from Lightroom (because it is not so far). And Tangent ... it should just be better Hardware because cheap MIDI consoles are usually poor quality (artificially limiting the functionality of the application - if a direct competitor, i.e. Lightroom does not do it, it is a bad path).

    And here we come to the answer to the question "why did I make this software available for free"?
    The answer is simple ... I have a self-interest in the fact that I am not able to put pressure on the Phase One company to make good keyboard support in Capture One (at least as it is in Lightroom). I would like to be able to handle the entire Capture One program using the MIDI console (and this is currently not possible). Maybe if more people start to intervene in technical support that something does not work for them (something can not be handled with a MIDI console) it will be done. So the reason why I share this program are paradoxically shortcomings in the Capture One functionality because the support of the program using the MIDI console is really much faster than using a mouse or tablet.
    0
  • WPNL
    First attempt of translation:

    [Etykiety]
    etBrakAkcji=There was no action associated with this manipulator.
    etNieWybranoAplikacji=No application selected.
    etSepPolEd=,
    etLp=Lp
    etOpis=Description
    etKomentarz=Comment
    etAplikacja=Application
    etKanal=Channel
    etStan=State
    etKodMIDI=MIDI value
    etTypAkcji=Action type
    etKodWyjsciowy=Output code
    etParametr=Parameter
    etCtrl=Ctrl
    etAlt=Alt
    etShift=Shift
    etKolorOpisu=Description color
    etKolorTlaOpisu=Description background color
    etIkona=Icon
    etIkonaTyp=Type
    Plik=File
    etPrzekodowanie=Recoding
    etKonfiguracja=Configuration
    etOProgramie=About program
    etBankiZdjec=Photo stocks
    etDodaj=Add
    etEdytuj=Edit
    etUsun=Clear
    etPamietaj=Remember
    etWkopiuj=Paste
    etZapisz=Save
    etOK=OK
    etAnuluj=Cancel
    etPlikPrzekodowan=Recoding file
    etPlikINI=Ini file
    etKolortlaOknaTool=The background color of the tool window
    etKolorTekstuOknaTool=The text color of the tool window
    etInfoBrakAkcji=Notify about the lack of associated action with the used keypad
    etPokazTransmisji=Show the transmission diode
    etParametrHint=For State - target manipulator; for Mouse - jump; for others - multiple times
    etWklej=paste
    etZakoncz=Exit
    etPokazOknaTool=Show / hide the window
    etPokazTytuluTool=Show / hide window title
    etRozszerzEdycja=Extended edition of the item
    etListaZdarzen=List of assigned events
    etPomoc=Help

    I'll update this one if there are improvements 😊
    0
  • Ryszard Stelmachowicz
    There are some mistakes ... I need to translate each phrase separately because it is not so good.

    etTypAkcji=Action type
    etKodWyjsciowy=Output code
    ..
    etPrzekodowanie=Recoding
    ..
    etBankiZdjec=Photo stocks
    ...
    etWkopiuj=Paste
    ...
    etZakoncz=Exit
    or Close
    0
  • WPNL
    Thanks for the correction, you Polish seems to be much better than mine (and Google's) 😉
    0
  • Ryszard Stelmachowicz
    What is translated is a translation into the program itself ... as you can see, there is not much.
    If someone would like to use it Arturia, you can change the descriptions in the help images (which knob to which the slider responds can be seen simply in Capture One - sliders move when you use it).
    And possibly you can improve the descriptions in the Midi2Macro.m2k file - this is the most. This is a configuration file - but this is the least needed because you can see why the given knob or key does and the icon is displayed.
    0
  • WPNL
    The translation of the m2k file can be done really fast with 'find and replace' in notepad or Excel/Calc, I was only struggling a bit with the characterset, does changing this break things? Just wondering, I haven't got time to dig into this tonight unfortunatly...
    0
  • Ryszard Stelmachowicz
    I have no idea ... it would have to be checked (maybe on a smaller fragment). The English character set should be appropriate and not cause problems (Polish is simply extended). Bigger problems could be when translating into some other languages that contain their own specific characters.
    0
  • Alain Decamps
    [quote="rstelmach" wrote:
    The real problem, however, is the lack of keyboard handling in Capture One (and thus enabling support using the MIDI controller).
    I wrote a bit about it here:
    https://fotorys.wordpress.com/2018/01/1 ... one-braki/

    The point is that Capture One has a very cursory (even selectively) treated problem of using the keyboard. Apparently no one paid attention to this, but it does not reach the Lightroom (which, however, has it much more accurate). These are simply deficiencies in functionality. And as to whether this would hurt Tangent ... I do not think so. How many people will buy an expensive Tangent (how much will the company earn) and how many people would buy Capture One and a cheap console if it could be handled more conveniently than Lightroom (how many more licenses would Capture One then sold)? I think that there is a huge field for development - just to Capture One it was more convenient to use from Lightroom (because it is not so far). And Tangent ... it should just be better Hardware because cheap MIDI consoles are usually poor quality (artificially limiting the functionality of the application - if a direct competitor, i.e. Lightroom does not do it, it is a bad path).

    And here we come to the answer to the question "why did I make this software available for free"?
    The answer is simple ... I have a self-interest in the fact that I am not able to put pressure on the Phase One company to make good keyboard support in Capture One (at least as it is in Lightroom). I would like to be able to handle the entire Capture One program using the MIDI console (and this is currently not possible). Maybe if more people start to intervene in technical support that something does not work for them (something can not be handled with a MIDI console) it will be done. So the reason why I share this program are paradoxically shortcomings in the Capture One functionality because the support of the program using the MIDI console is really much faster than using a mouse or tablet.


    Unfortunately I have to agree with you that he keyboard support is not complete and lacking quite a few things.
    It should be rather easy to add extra commands that are configurable and have default no keypress to them attached.

    Sometimes it's rather strange: the step for brightness change is rather large.

    For me it's also very error prone that's there's no way to work certain things directly on the background layer and not on the current layer. It's even not possible to have a keypress that goes from the current layer to the background layer (and another to go back).
    0
  • Ryszard Stelmachowicz
    I think with such problems you have to turn to technical support. Contact with the service is very good - they respond very quickly. Only that it is not known whether they will correct something or not, and if so, when. But maybe as more people will write that there are such mistakes, something will improve. So far, the lawter's service was superficial, probably because only a few people used it. If more people would use it, I think that they should finally do it because they are probably simple things to implement and can greatly increase the comfort of work and the perception of the Capture One program by users as friendly.
    0
  • Ryszard Stelmachowicz
    I have configured the support for the most frequently used functions on channel 15.
    Unfortunately, some functions are missing, for which it is not possible to assign keyboard shortcuts after the proto. I wonder if it will ever be possible ?!
    0
  • Alain Decamps
    [quote="rstelmach" wrote:
    I think with such problems you have to turn to technical support. Contact with the service is very good - they respond very quickly. Only that it is not known whether they will correct something or not, and if so, when. But maybe as more people will write that there are such mistakes, something will improve. So far, the lawter's service was superficial, probably because only a few people used it. If more people would use it, I think that they should finally do it because they are probably simple things to implement and can greatly increase the comfort of work and the perception of the Capture One program by users as friendly.


    Already made a support case some time ago. They send some remarks to be considered for a change request. I hope those are added.
    0
  • Alain Decamps
    Has anybody some news from Phase one that they will solve some off the annoying absent keypress options?
    0
  • Alain Decamps
    Hi

    Has anybody completed the translation?

    Alain
    0
  • NNN636911764193277052
    yes i complete. do you want help. tell me
    Richestsoft
    0
  • Ryszard Stelmachowicz

    I made a new version of Midi2Macro. The biggest change at the moment is that the help displayed is not from a static image but was created dynamically from the configuration. The appearance of the help corresponds to the Arturia Beatstep MIDI console configuration. Some keyboard shots are set only for me in Capture One so not everything may work properly and you will need to complete these keyboard shortcuts a bit.

    0
  • Ryszard Stelmachowicz

    I improved the refreshing (flickering) of the tooltip help window when using the manipulators.

    0

Post is closed for comments.