Audiobus: Use your music apps together.

What is Audiobus? — Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.

Download on the App Store

Audiobus is the app that makes the rest of your setup better.

A BIT PISSED OFF

13»

Comments

  • addheadaddhead

    And i think it's easy possible now
    And I dont think its getting worser

    But yes i am stubborn
    Happy about that.
    :p

  • addheadaddhead

    @Fruitbat1919 said:

    @addhead said:

    @Fruitbat1919 said:

    @addhead said:
    This is an article from 2012

    Read it careful and you can understand me!!!!!!

    From sound on sound

    http://www.soundonsound.com/techniques/audiobus

    You are here

    Home
Techniques

    Audiobus
    Apple Notes

    Hardware > Computer

    Published July 2012
    By Mike Watkinson

    Virtual app-to-app connectivity with Audiobus (top right): SoundPrism Pro and Loopy HD are the first two apps to adopt the Audiobus protocol. Here, SoundPrism Pro has been selected as the input and Loopy HD as the output.
    Virtual app-to-app connectivity with Audiobus (top right): SoundPrism Pro and Loopy HD are the first two apps to adopt the Audiobus protocol. Here, SoundPrism Pro has been selected as the input and Loopy HD as the output.
    Audiobus
    Audiobus

    The future is here! Or at least some of it. In beta. You know how keen we are here at Apple Notes HQ to let you know what's in the pipeline? Well, this month it's all about pipelines! The potentials created by Apple's hardware and software developments are being realised to the benefit of musicians, and all that thinking is being, literally, joined up.
    Separation Anxiety

    With iOS apps being self-contained and iPads and iPhones being designed to be personal devices, the idea so far has been that you work one app at a time, and you work on your own. You can switch between apps, but getting apps to talk to each other, though possible, is frustrating. Some efforts to make apps talk to each other have been made, but virtual MIDI has been implemented differently from one app to another, and I think these problems undermine the convenience of an app and why we use them in the first place!

    I have reported previously on Sonoma Wireworks, who created a protocol that implements the clipboard in apps like StudioTrack, and AudioCopy and AudioPaste has been implemented in a wide range of apps, but copying and pasting from one app to another relies on the two projects being at exactly the same tempo. Whatever any iPad advocate tells you about creating new ideas when you're forced to work in different ways to those that you prefer, these problems can certainly hinder your workflow.
    Get On Board

    So what if you could just connect one app to another with a virtual cable? This idea's been around for quite a while on the Mac with Cycling '74's SoundFlower, but now the clever chaps at www.audiob.us have come up with an iOS equivalent which they call — yes — Audiobus. In the beta stage at the time of writing, the protocol requires apps to be Audiobus compliant, and at this point there are only two apps that fit the bill: Loopy HD by A Tasty Pixel and SoundPrism Pro by Audanika. Both apps are already established as favourites with iOS musicians, and are shining examples of how a touchscreen interface can be exploited to make music in intriguing and inspiring ways. But there are most definitely more in the pipeline. Audiobus is itself an app that allows you to choose an app as the input, passing live audio from that app to an app chosen as the output. **_Apps can be on the same device or different devices and Audiobus itself can be on any device, as long as they are all in the same Wi-Fi network. When I saw this working for the first time, I was impressed by how easy it was to set up, but it is the flexibility that gives rise to a multitude of possible collaborative opportunities._**

    Choosing SoundPrism Pro as the input and Loopy HD as the output in Audiobus, I was able to record the live audio output of the former into the latter, with the apps running on the same device as well as on different devices. Impressively, audio is captured in perfect sync, as Audiobus has a clever buffering system that passes the time-stamped audio to the output app in sync, whatever fluctuations take place in the wireless bandwidth. All apps running on any devices in the network are currently recognised, so I can imagine some confusion when multiple devices are being deployed, but if an appropriate interface is designed to cope with this, that issue could be resolved.
    En Route

    There is already provision for the user to insert an app in the signal path to perform filtering or other such manipulation in real time. The possibilities for live performance and capture of that performance are limitless, but, like all good protocols, its success will be driven by how many developers come on board and add Audiobus compatibility to their apps. Ideally, the big boys will also want a slice of the action: just imagine GarageBand for iOS capturing live output from your favourite synth apps. Finally, the iPad band looks like a reality!

    From this we can easily see:
    1. It was an idea once, but that it had some issues as shown in the posted piece from Sound on Sound.
    2. There are no promises or statements here that promise it would get resolved from the Audiobus team.

    You have an explanation of why it was not continued with by the Audiobus team, which to my mind seems fair and reasonable, as if you want Audio from one device to another, there is much better wired options.

    So from this I can see that in 2013 you get an idea that this app may do something that it later does not do. Did you actually use that feature when it was first in use? If not, you have not lost anything, as the app does not pretend to have that feature now.

    Then, we do have to question, why seriously are you complaining about a feature now in 2017 that must have been taken out of the app a very long time ago? Has Audiobus been promising its return? If so, then you have a case to be disgruntled.

    Did you even buy Audiobus at a time when it had this feature and have used it? Are you aware that changes were forced upon Audiobus anyway by Apple to fit in with their IAA plans (as far as I'm aware, as it was way before my iOS time lol).

    What are you really after here? You seem to be wanting something that was tried and failed and has not been accomplished (in a decent working order) by any other developer. Something that you say was promised, yet really I see little evidence that anything was promised, just something was tried....and failed.

    if someting failed than it's a succes in my opinion, and you can change it to get it to work,
    I think that if the wifi internal network is fast enough it will work, but i am a bit stubborn, Sorry about that.

    If something fails, it does not always equate to success, or be possible to make it work just by changing something. Often major changes only come about by changes in many areas. It may need lots of areas of technology to change to make this possible. It may never become possible in our lifetime. It definitely is not worth throwing your business away in trying to attain something that lacks real gain from such high risk.

    Yes, it seems you are stubborn lol :)

    The makers of audiobus were so close to that succes, why throw that away.
    Take the chance and risk to get even a beter succes, and dont be so negative about it.

    The first car looks much diference from the car's now.

    Or can't i make that comparison??

  • [Deleted User][Deleted User]

    @addhead said:

    @Fruitbat1919 said:

    @addhead said:

    @Fruitbat1919 said:

    @addhead said:
    This is an article from 2012

    Read it careful and you can understand me!!!!!!

    From sound on sound

    http://www.soundonsound.com/techniques/audiobus

    You are here

    Home
Techniques

    Audiobus
    Apple Notes

    Hardware > Computer

    Published July 2012
    By Mike Watkinson

    Virtual app-to-app connectivity with Audiobus (top right): SoundPrism Pro and Loopy HD are the first two apps to adopt the Audiobus protocol. Here, SoundPrism Pro has been selected as the input and Loopy HD as the output.
    Virtual app-to-app connectivity with Audiobus (top right): SoundPrism Pro and Loopy HD are the first two apps to adopt the Audiobus protocol. Here, SoundPrism Pro has been selected as the input and Loopy HD as the output.
    Audiobus
    Audiobus

    The future is here! Or at least some of it. In beta. You know how keen we are here at Apple Notes HQ to let you know what's in the pipeline? Well, this month it's all about pipelines! The potentials created by Apple's hardware and software developments are being realised to the benefit of musicians, and all that thinking is being, literally, joined up.
    Separation Anxiety

    With iOS apps being self-contained and iPads and iPhones being designed to be personal devices, the idea so far has been that you work one app at a time, and you work on your own. You can switch between apps, but getting apps to talk to each other, though possible, is frustrating. Some efforts to make apps talk to each other have been made, but virtual MIDI has been implemented differently from one app to another, and I think these problems undermine the convenience of an app and why we use them in the first place!

    I have reported previously on Sonoma Wireworks, who created a protocol that implements the clipboard in apps like StudioTrack, and AudioCopy and AudioPaste has been implemented in a wide range of apps, but copying and pasting from one app to another relies on the two projects being at exactly the same tempo. Whatever any iPad advocate tells you about creating new ideas when you're forced to work in different ways to those that you prefer, these problems can certainly hinder your workflow.
    Get On Board

    So what if you could just connect one app to another with a virtual cable? This idea's been around for quite a while on the Mac with Cycling '74's SoundFlower, but now the clever chaps at www.audiob.us have come up with an iOS equivalent which they call — yes — Audiobus. In the beta stage at the time of writing, the protocol requires apps to be Audiobus compliant, and at this point there are only two apps that fit the bill: Loopy HD by A Tasty Pixel and SoundPrism Pro by Audanika. Both apps are already established as favourites with iOS musicians, and are shining examples of how a touchscreen interface can be exploited to make music in intriguing and inspiring ways. But there are most definitely more in the pipeline. Audiobus is itself an app that allows you to choose an app as the input, passing live audio from that app to an app chosen as the output. **_Apps can be on the same device or different devices and Audiobus itself can be on any device, as long as they are all in the same Wi-Fi network. When I saw this working for the first time, I was impressed by how easy it was to set up, but it is the flexibility that gives rise to a multitude of possible collaborative opportunities._**

    Choosing SoundPrism Pro as the input and Loopy HD as the output in Audiobus, I was able to record the live audio output of the former into the latter, with the apps running on the same device as well as on different devices. Impressively, audio is captured in perfect sync, as Audiobus has a clever buffering system that passes the time-stamped audio to the output app in sync, whatever fluctuations take place in the wireless bandwidth. All apps running on any devices in the network are currently recognised, so I can imagine some confusion when multiple devices are being deployed, but if an appropriate interface is designed to cope with this, that issue could be resolved.
    En Route

    There is already provision for the user to insert an app in the signal path to perform filtering or other such manipulation in real time. The possibilities for live performance and capture of that performance are limitless, but, like all good protocols, its success will be driven by how many developers come on board and add Audiobus compatibility to their apps. Ideally, the big boys will also want a slice of the action: just imagine GarageBand for iOS capturing live output from your favourite synth apps. Finally, the iPad band looks like a reality!

    From this we can easily see:
    1. It was an idea once, but that it had some issues as shown in the posted piece from Sound on Sound.
    2. There are no promises or statements here that promise it would get resolved from the Audiobus team.

    You have an explanation of why it was not continued with by the Audiobus team, which to my mind seems fair and reasonable, as if you want Audio from one device to another, there is much better wired options.

    So from this I can see that in 2013 you get an idea that this app may do something that it later does not do. Did you actually use that feature when it was first in use? If not, you have not lost anything, as the app does not pretend to have that feature now.

    Then, we do have to question, why seriously are you complaining about a feature now in 2017 that must have been taken out of the app a very long time ago? Has Audiobus been promising its return? If so, then you have a case to be disgruntled.

    Did you even buy Audiobus at a time when it had this feature and have used it? Are you aware that changes were forced upon Audiobus anyway by Apple to fit in with their IAA plans (as far as I'm aware, as it was way before my iOS time lol).

    What are you really after here? You seem to be wanting something that was tried and failed and has not been accomplished (in a decent working order) by any other developer. Something that you say was promised, yet really I see little evidence that anything was promised, just something was tried....and failed.

    if someting failed than it's a succes in my opinion, and you can change it to get it to work,
    I think that if the wifi internal network is fast enough it will work, but i am a bit stubborn, Sorry about that.

    If something fails, it does not always equate to success, or be possible to make it work just by changing something. Often major changes only come about by changes in many areas. It may need lots of areas of technology to change to make this possible. It may never become possible in our lifetime. It definitely is not worth throwing your business away in trying to attain something that lacks real gain from such high risk.

    Yes, it seems you are stubborn lol :)

    The makers of audiobus were so close to that succes, why throw that away.
    Take the chance and risk to get even a beter succes, and dont be so negative about it.

    The first car looks much diference from the car's now.

    Or can't i make that comparison??

    You can make whatever comparison you like, but under scrutiny I can pick more holes in that argument than my cullinder owns lol

  • addheadaddhead

    @Fruitbat1919 said:

    @addhead said:

    @Fruitbat1919 said:

    @addhead said:

    @Fruitbat1919 said:

    @addhead said:
    This is an article from 2012

    Read it careful and you can understand me!!!!!!

    From sound on sound

    http://www.soundonsound.com/techniques/audiobus

    You are here

    Home
Techniques

    Audiobus
    Apple Notes

    Hardware > Computer

    Published July 2012
    By Mike Watkinson

    Virtual app-to-app connectivity with Audiobus (top right): SoundPrism Pro and Loopy HD are the first two apps to adopt the Audiobus protocol. Here, SoundPrism Pro has been selected as the input and Loopy HD as the output.
    Virtual app-to-app connectivity with Audiobus (top right): SoundPrism Pro and Loopy HD are the first two apps to adopt the Audiobus protocol. Here, SoundPrism Pro has been selected as the input and Loopy HD as the output.
    Audiobus
    Audiobus

    The future is here! Or at least some of it. In beta. You know how keen we are here at Apple Notes HQ to let you know what's in the pipeline? Well, this month it's all about pipelines! The potentials created by Apple's hardware and software developments are being realised to the benefit of musicians, and all that thinking is being, literally, joined up.
    Separation Anxiety

    With iOS apps being self-contained and iPads and iPhones being designed to be personal devices, the idea so far has been that you work one app at a time, and you work on your own. You can switch between apps, but getting apps to talk to each other, though possible, is frustrating. Some efforts to make apps talk to each other have been made, but virtual MIDI has been implemented differently from one app to another, and I think these problems undermine the convenience of an app and why we use them in the first place!

    I have reported previously on Sonoma Wireworks, who created a protocol that implements the clipboard in apps like StudioTrack, and AudioCopy and AudioPaste has been implemented in a wide range of apps, but copying and pasting from one app to another relies on the two projects being at exactly the same tempo. Whatever any iPad advocate tells you about creating new ideas when you're forced to work in different ways to those that you prefer, these problems can certainly hinder your workflow.
    Get On Board

    So what if you could just connect one app to another with a virtual cable? This idea's been around for quite a while on the Mac with Cycling '74's SoundFlower, but now the clever chaps at www.audiob.us have come up with an iOS equivalent which they call — yes — Audiobus. In the beta stage at the time of writing, the protocol requires apps to be Audiobus compliant, and at this point there are only two apps that fit the bill: Loopy HD by A Tasty Pixel and SoundPrism Pro by Audanika. Both apps are already established as favourites with iOS musicians, and are shining examples of how a touchscreen interface can be exploited to make music in intriguing and inspiring ways. But there are most definitely more in the pipeline. Audiobus is itself an app that allows you to choose an app as the input, passing live audio from that app to an app chosen as the output. **_Apps can be on the same device or different devices and Audiobus itself can be on any device, as long as they are all in the same Wi-Fi network. When I saw this working for the first time, I was impressed by how easy it was to set up, but it is the flexibility that gives rise to a multitude of possible collaborative opportunities._**

    Choosing SoundPrism Pro as the input and Loopy HD as the output in Audiobus, I was able to record the live audio output of the former into the latter, with the apps running on the same device as well as on different devices. Impressively, audio is captured in perfect sync, as Audiobus has a clever buffering system that passes the time-stamped audio to the output app in sync, whatever fluctuations take place in the wireless bandwidth. All apps running on any devices in the network are currently recognised, so I can imagine some confusion when multiple devices are being deployed, but if an appropriate interface is designed to cope with this, that issue could be resolved.
    En Route

    There is already provision for the user to insert an app in the signal path to perform filtering or other such manipulation in real time. The possibilities for live performance and capture of that performance are limitless, but, like all good protocols, its success will be driven by how many developers come on board and add Audiobus compatibility to their apps. Ideally, the big boys will also want a slice of the action: just imagine GarageBand for iOS capturing live output from your favourite synth apps. Finally, the iPad band looks like a reality!

    From this we can easily see:
    1. It was an idea once, but that it had some issues as shown in the posted piece from Sound on Sound.
    2. There are no promises or statements here that promise it would get resolved from the Audiobus team.

    You have an explanation of why it was not continued with by the Audiobus team, which to my mind seems fair and reasonable, as if you want Audio from one device to another, there is much better wired options.

    So from this I can see that in 2013 you get an idea that this app may do something that it later does not do. Did you actually use that feature when it was first in use? If not, you have not lost anything, as the app does not pretend to have that feature now.

    Then, we do have to question, why seriously are you complaining about a feature now in 2017 that must have been taken out of the app a very long time ago? Has Audiobus been promising its return? If so, then you have a case to be disgruntled.

    Did you even buy Audiobus at a time when it had this feature and have used it? Are you aware that changes were forced upon Audiobus anyway by Apple to fit in with their IAA plans (as far as I'm aware, as it was way before my iOS time lol).

    What are you really after here? You seem to be wanting something that was tried and failed and has not been accomplished (in a decent working order) by any other developer. Something that you say was promised, yet really I see little evidence that anything was promised, just something was tried....and failed.

    if someting failed than it's a succes in my opinion, and you can change it to get it to work,
    I think that if the wifi internal network is fast enough it will work, but i am a bit stubborn, Sorry about that.

    If something fails, it does not always equate to success, or be possible to make it work just by changing something. Often major changes only come about by changes in many areas. It may need lots of areas of technology to change to make this possible. It may never become possible in our lifetime. It definitely is not worth throwing your business away in trying to attain something that lacks real gain from such high risk.

    Yes, it seems you are stubborn lol :)

    The makers of audiobus were so close to that succes, why throw that away.
    Take the chance and risk to get even a beter succes, and dont be so negative about it.

    The first car looks much diference from the car's now.

    Or can't i make that comparison??

    You can make whatever comparison you like, but under scrutiny I can pick more holes in that argument than my cullinder owns lol

    be my guest

  • [Deleted User][Deleted User]
    edited April 2017

    @addhead said:

    @Fruitbat1919 said:

    @addhead said:

    @Fruitbat1919 said:

    @addhead said:

    @Fruitbat1919 said:

    @addhead said:
    This is an article from 2012

    Read it careful and you can understand me!!!!!!

    From sound on sound

    http://www.soundonsound.com/techniques/audiobus

    You are here

    Home
Techniques

    Audiobus
    Apple Notes

    Hardware > Computer

    Published July 2012
    By Mike Watkinson

    Virtual app-to-app connectivity with Audiobus (top right): SoundPrism Pro and Loopy HD are the first two apps to adopt the Audiobus protocol. Here, SoundPrism Pro has been selected as the input and Loopy HD as the output.
    Virtual app-to-app connectivity with Audiobus (top right): SoundPrism Pro and Loopy HD are the first two apps to adopt the Audiobus protocol. Here, SoundPrism Pro has been selected as the input and Loopy HD as the output.
    Audiobus
    Audiobus

    The future is here! Or at least some of it. In beta. You know how keen we are here at Apple Notes HQ to let you know what's in the pipeline? Well, this month it's all about pipelines! The potentials created by Apple's hardware and software developments are being realised to the benefit of musicians, and all that thinking is being, literally, joined up.
    Separation Anxiety

    With iOS apps being self-contained and iPads and iPhones being designed to be personal devices, the idea so far has been that you work one app at a time, and you work on your own. You can switch between apps, but getting apps to talk to each other, though possible, is frustrating. Some efforts to make apps talk to each other have been made, but virtual MIDI has been implemented differently from one app to another, and I think these problems undermine the convenience of an app and why we use them in the first place!

    I have reported previously on Sonoma Wireworks, who created a protocol that implements the clipboard in apps like StudioTrack, and AudioCopy and AudioPaste has been implemented in a wide range of apps, but copying and pasting from one app to another relies on the two projects being at exactly the same tempo. Whatever any iPad advocate tells you about creating new ideas when you're forced to work in different ways to those that you prefer, these problems can certainly hinder your workflow.
    Get On Board

    So what if you could just connect one app to another with a virtual cable? This idea's been around for quite a while on the Mac with Cycling '74's SoundFlower, but now the clever chaps at www.audiob.us have come up with an iOS equivalent which they call — yes — Audiobus. In the beta stage at the time of writing, the protocol requires apps to be Audiobus compliant, and at this point there are only two apps that fit the bill: Loopy HD by A Tasty Pixel and SoundPrism Pro by Audanika. Both apps are already established as favourites with iOS musicians, and are shining examples of how a touchscreen interface can be exploited to make music in intriguing and inspiring ways. But there are most definitely more in the pipeline. Audiobus is itself an app that allows you to choose an app as the input, passing live audio from that app to an app chosen as the output. **_Apps can be on the same device or different devices and Audiobus itself can be on any device, as long as they are all in the same Wi-Fi network. When I saw this working for the first time, I was impressed by how easy it was to set up, but it is the flexibility that gives rise to a multitude of possible collaborative opportunities._**

    Choosing SoundPrism Pro as the input and Loopy HD as the output in Audiobus, I was able to record the live audio output of the former into the latter, with the apps running on the same device as well as on different devices. Impressively, audio is captured in perfect sync, as Audiobus has a clever buffering system that passes the time-stamped audio to the output app in sync, whatever fluctuations take place in the wireless bandwidth. All apps running on any devices in the network are currently recognised, so I can imagine some confusion when multiple devices are being deployed, but if an appropriate interface is designed to cope with this, that issue could be resolved.
    En Route

    There is already provision for the user to insert an app in the signal path to perform filtering or other such manipulation in real time. The possibilities for live performance and capture of that performance are limitless, but, like all good protocols, its success will be driven by how many developers come on board and add Audiobus compatibility to their apps. Ideally, the big boys will also want a slice of the action: just imagine GarageBand for iOS capturing live output from your favourite synth apps. Finally, the iPad band looks like a reality!

    From this we can easily see:
    1. It was an idea once, but that it had some issues as shown in the posted piece from Sound on Sound.
    2. There are no promises or statements here that promise it would get resolved from the Audiobus team.

    You have an explanation of why it was not continued with by the Audiobus team, which to my mind seems fair and reasonable, as if you want Audio from one device to another, there is much better wired options.

    So from this I can see that in 2013 you get an idea that this app may do something that it later does not do. Did you actually use that feature when it was first in use? If not, you have not lost anything, as the app does not pretend to have that feature now.

    Then, we do have to question, why seriously are you complaining about a feature now in 2017 that must have been taken out of the app a very long time ago? Has Audiobus been promising its return? If so, then you have a case to be disgruntled.

    Did you even buy Audiobus at a time when it had this feature and have used it? Are you aware that changes were forced upon Audiobus anyway by Apple to fit in with their IAA plans (as far as I'm aware, as it was way before my iOS time lol).

    What are you really after here? You seem to be wanting something that was tried and failed and has not been accomplished (in a decent working order) by any other developer. Something that you say was promised, yet really I see little evidence that anything was promised, just something was tried....and failed.

    if someting failed than it's a succes in my opinion, and you can change it to get it to work,
    I think that if the wifi internal network is fast enough it will work, but i am a bit stubborn, Sorry about that.

    If something fails, it does not always equate to success, or be possible to make it work just by changing something. Often major changes only come about by changes in many areas. It may need lots of areas of technology to change to make this possible. It may never become possible in our lifetime. It definitely is not worth throwing your business away in trying to attain something that lacks real gain from such high risk.

    Yes, it seems you are stubborn lol :)

    The makers of audiobus were so close to that succes, why throw that away.
    Take the chance and risk to get even a beter succes, and dont be so negative about it.

    The first car looks much diference from the car's now.

    Or can't i make that comparison??

    You can make whatever comparison you like, but under scrutiny I can pick more holes in that argument than my cullinder owns lol

    be my guest

    Ok:

    Cars have fundamentally stayed the same since their conception. They have improved in many ways. In some ways, they have not.

    Cars could fundamentally change and are doing so with the advent of electric cars though, and while they could possibly be the future, not one major car company is throwing everything into them in one go. Why? It's just not good business sense to throw all your eggs in one basket, unless you believe you will reap the reward within a certain time frame.

    So Audiobus tried something. It failed to be seen of viable working quality at that time. They are a small company with limited resources, so wisely decided to put money into other avenues of progression for their flagship app.

    Now technical aspects aside, I've not met one person who knows what those technical problems are, that thinks using wireless technology for uses that has strong timing needs is a good idea at this time. Music listening is fine. Music making on the other hand just does not work properly with any current wireless tech.

    Now back to cars. Why hasn't all car companies gone electric? Many reasons, but while it may be the future, it's pretty sound that at this time problems exist that even really large car companies don't have the resources to manage. So while it's easy for you to say to Audiobus to throw all their very limited resources into this one avenue and for you to believe the technical problems are easily solved, you don't really have the facts to make either assumption.

  • ksoundksound

    @addhead said:

    @ksound said:
    You're ridiculous. There's a chasm between having an idea and implementing it in a functional app. Please devs, keep stealing my ideaz.

    It was advertised by Audiobus, I only asked in 2013 When it's getting implemented.

    Yeah i am a ridiculous (hufter) "dutch word"

    This was not written by you?

    Now we have to pay for all kind of "IDEAS" from your "CUSTOMERS" that you GET for "FREE"

  • addheadaddhead

    I never say it's easy,
    I say they where very close to a breakthrough
    And the technic and speed comes with a short time.
    If they try and try and try,
    it wil hapen you will see.
    Maybe i am to optimistic about that,
    but look here:


    The same company,
    But more and more cristalized.

    Have a bit more faith

  • addheadaddhead

    @ksound said:

    @addhead said:

    @ksound said:
    You're ridiculous. There's a chasm between having an idea and implementing it in a functional app. Please devs, keep stealing my ideaz.

    It was advertised by Audiobus, I only asked in 2013 When it's getting implemented.

    Yeah i am a ridiculous (hufter) "dutch word"

    This was not written by you?

    Now we have to pay for all kind of "IDEAS" from your "CUSTOMERS" that you GET for "FREE"

    I wrote that, i am a hufter,
    Or what do you mean?
    i don't get it.

  • addheadaddhead

    @addhead said:

    @ksound said:

    @addhead said:

    @ksound said:
    You're ridiculous. There's a chasm between having an idea and implementing it in a functional app. Please devs, keep stealing my ideaz.

    It was advertised by Audiobus, I only asked in 2013 When it's getting implemented.

    Yeah i am a ridiculous (hufter) "dutch word"

    This was not written by you?

    Now we have to pay for all kind of "IDEAS" from your "CUSTOMERS" that you GET for "FREE"

    I wrote that, i am a hufter,
    Or what do you mean?
    i don't get it.

    or do you mean you get payed for your ideas?

  • RUST( i )KRUST( i )K

    al your implemented ideas are great

  • addheadaddhead

    @RustiK said:
    al your implemented ideas are great

    Thanks, but I don't know what ideas you mean.
    I have plenty ideas, but I don't talk so much about them.
    It's more there ideas they don't implement.

    Or do you mean that?

    Sorry my understanding isn't always at a high level.

Sign In or Register to comment.