You have to try with the reference ISO on Native PC, or VM, without copying TinyAROS, only so we can be sure that it works for you !

--- Italiano ---

Devi provare con la ISO di riferimento su PC Nativo, o VM, senza copiare TinyAROS, solo così possiamo essere certi che a te funziona !

the reference iso is the only thing I install the Tiny Aros files are additional and necessary for the software to work

I repeat, I have re-installed everything and have not considered the SystemStuff folder

Did you read deadwood's post ? Bars&Pipes cannot work properly on AROS (it only works on Hosted Linux).

In this case tests with AROS One and with TinyAROS are not needed because they might give different results!

Tests must be done "Only" with the reference ISO on native PC and VM

SystemStuff folder if it exists I think you have to install it, if they are needed you should ask Alfred


--- Italiano ---

Hai letto il Post di deadwood ? Bars&Pipes non può funzionare correttamente su AROS (funziona solo su Hosted Linux)

In questo caso i test con AROS One e con TinyAROS non servono perchè potrebbero dare risultati diversi!

I test bisogna farli "Solo" con la ISO di riferimento su PC nativo e VM

SystemStuff folder se esiste credo bisogna installarla, se sono necessari dovresti chiedere a Alfred

I cannot test 100% because I do not have the necessary equipment

It's the other way around. The problem I mentioned is immediatelly visible on hosted, but might not be visible on native. If I can get pass this problem on hosted, I can check if there are any other crashes further on.

Sorry deadwood I had misunderstood, I did tests also on native (2 PCs) and the Guru always appears on closing Bars&Pipes

In my case, the crash happen at start after the initial window is opened.

I am trying to get some equipment to work with the software

Hi,

Just wondered if there was any news?

Tried again, still the same

3. Using MidiWatch to see output, started pipes and same illegal instruction
2. Not plugged midi in, started pipes, get output, complains no out or in, pipes starts, same illegal instruction
1. Plugged midi in, started pipes, get output, pipes starts, same illegal instruction

Hi,

Just seen the other instructions, here's some photos of the output (appears OK)

Try this:
-open a shell
-cd to the BarsnPipes directory
-start BarsnPipes with:
BarsnPipes debug

Normally any debug information is now printed.
In BarsnPipes, drag the icon from the Quantize tool into the pipeline and drop it there.
Double-click this icon in the pipeline. The window of the icon is opened.
Leave the window open and click in the track window (title becomes red).
Press the right AMIGA key and Q or select Quit in the menu.
Requester -> Save? -> Press No
If everything runs normally, a few debug messages will appear in the shell-window:

" ..."
"get entry for cowlist ..."

at the end:
Delete gui in RAM:
freelocalestrings
Done

For more information, please contact the developer Mr. Alfred Faust

alfred.j.faust@gmx.de

many thanks I don't know the program and I don't know how to use it

thanks to Mr. Franck Charlet we have usb midi support Alfred Faust many years ago wanted to bring Bars & Pipes but there was no usb midi drivers if there is a possibility to communicate any fixes and bugs of the program for those who know how to use it it would be great

Mr Faust may have made a mistake in the porting, let's hope for improvements in the next software versions Sorry for any inconvenience, we're doing our best Thanks to all the contributors to this project

Mr. Faust works bars&pipes without any problems so now I asked him what equipment he uses the problem could be the hardware at least the midi cable, stay tuned

i bought a fairly common midi cable well at start-up the programme detects it but the screen does not open for me do you have the same problem

Hi,

Have you tried opening a shell where Pipes has been extracted and running BarsNPipes debug mode in it as per the first part of the instructions a few posts higher #51 and getting the output to see if it is the same?

I have tried but nothing happens the programme does not open

at the end of the debugging process it tells me delete gui in ram:

Hi,

Delete gui in RAM:

is a few lines from the end of the output and according to Alfred should be OK
I suspect Alfred might be best to contact